The AI build-out is changing the shape of electricity demand. Data centres were once treated as a specialist real-estate or cloud-infrastructure issue. They now sit inside national energy planning, corporate site selection, industrial policy, and grid investment. For leaders, the practical question is not whether AI demand will grow. It is where the bottleneck shows up first and who owns the decision before it becomes urgent.

This report reads the power question as an operating constraint. It draws on the International Energy Agency's electricity and energy-technology outlooks, public grid-connection evidence, and Kaya Development's work on infrastructure sequencing. The conclusion is simple: AI infrastructure decisions need to move upstream. If power is handled after the business case is written, the strategy is already late.

In this report
  1. The demand curve is steepening
  2. Connection time is the real bottleneck
  3. The strategic choices leaders need to make
  4. What to do in the next 12 months

1. The demand curve is steepening

AI demand does not add evenly to the power system. It concentrates in specific campuses, grid nodes, transmission corridors, and regions with fibre, land, cooling, and permitting advantages. That makes the issue more difficult than a simple national-demand forecast. A country can have enough annual generation on paper and still have the wrong capacity in the wrong place at the wrong time.

Exhibit 1
Data-centre power demand: strategic pressure points
Indicative pressure index by decision area, 2026-2030
Grid connection capacity
Very high
Transmission reinforcement
High
Firm low-carbon supply
High
Permitting and land readiness
Rising
Water and cooling constraints
Market-specific
Source: Kaya Development synthesis of IEA Electricity 2026, IEA Energy and AI, and public grid-capacity disclosures

2. Connection time is the real bottleneck

Most executive AI strategies still assume that compute can be bought when the use case is ready. That assumption is weakening. In several markets, power procurement, interconnection, transmission reinforcement, and local permitting now move on infrastructure timelines rather than software timelines. This matters because AI pilots scale unevenly: a model that is cheap to test can become expensive to host once it is embedded in thousands of decisions.

Exhibit 2
Typical lead-time stack for a large AI compute site
Indicative months from strategic decision to reliable capacity
Demand case and site screenWorkload, latency, growth scenarios
2-4 months
Power availability assessmentGrid node, queue, reinforcement need
4-9 months
Commercial power strategyPPA, firming, backup, carbon position
6-12 months
Permitting and interconnectionLocal approvals, utility agreements
12-30 months
Grid and site deliverySubstation, redundancy, commissioning
24-48 months
Source: Kaya Development analysis of public interconnection evidence, utility disclosures, and infrastructure delivery benchmarks

3. The strategic choices leaders need to make

The power bottleneck creates three different strategy paths. Some organizations should buy cloud capacity and avoid infrastructure ownership. Some should secure long-term capacity through strategic partnerships. A smaller set should treat compute and power as a core asset and build the capability directly. The wrong choice is to drift between the three.

Exhibit 3
Power constraint decision matrix
How leaders should match AI ambition to power strategy
Secure partnersHigh AI ambition, limited infrastructure appetite. Lock capacity through cloud, colocation, and energy partners.
Build capabilityAI is strategic infrastructure. Treat power, compute, and resilience as board-level assets.
Buy flexiblyKeep optionality. Use external capacity and avoid fixed assets until use cases prove durable.
Sequence firstInfrastructure appetite is high, but AI demand is unclear. Start with modular pilots and staged capacity.
Infrastructure ownership appetite →
AI workload criticality →
Source: Kaya Development AI infrastructure strategy framework

4. What to do in the next 12 months

Leaders do not need to become utility planners. They do need a single view of AI workload growth, hosting architecture, power availability, carbon commitments, and resilience requirements. The first move is to stop treating these as separate conversations. The second is to put a capacity owner in the operating model.

Three moves now
  1. Build a workload-to-power map. Link AI use cases to compute location, capacity, latency, resilience, and carbon requirements.
  2. Screen grid nodes before sites. The best real estate is not useful if the connection queue breaks the timeline.
  3. Name the capacity owner. Make one executive accountable for power, compute, and infrastructure sequencing.
Download the full PDF (PDF coming soon)

HTML report. Citation-ready source notes included.