The Definitive Guide toAI Data Centers
Ask the Guide

Chapter 16.5

Scenarios for 2030

2030 is not one future but a small set of structurally distinct ones — supercycle, digestion, or bubble; centralized mega-campus or distributed inference; firm clean power on time or not — and the decisions you make in 2026 are bets on which of them arrives, with stranded silicon, stranded substations, and stranded balance sheets as the price of betting wrong.

POWER-BOUNDGOODPUTDENSITY-RAMP

What you'll decide here

  1. Which demand scenario you underwrite the build against — supercycle (demand outruns supply through 2030), digestion (capex decelerates as a hard base is absorbed), or bubble (a revenue gap forces write-downs) — because that single belief sets your contracted-vs-merchant mix, your debt capacity, and how much optionality you pay for.
  2. Whether you are building the centralized gigawatt training campus or the distributed inference fleet — the architectural fork that determines whether your siting search is power-first-and-remote or latency-first-and-metro, and whether your fleet survives the shift to inference-dominant compute.
  3. Which industry structure you are positioning for — neocloud, hyperscaler, or sovereign/enterprise — and therefore whose cost-of-capital, utilization risk, and obsolescence exposure you inherit as the sector consolidates.
  4. Which power-supply endgame you are betting time-to-megawatt on — firm CFE / existing nuclear now, SMR or fusion as 2030+ optionism, or gas-and-grid as the default bridge — knowing the clean-and-firm options that look cheapest on a spreadsheet are the slowest to energize.
  5. Which downside you are designed to survive — a demand air-pocket, a power-delivery slip, an efficiency shock that deflates token demand, or a generational density step that strands current racks — and whether the flexibility you paid for actually hedges the one that lands.

Every chapter before this one decides something about a building you can draw. This one decides which world the building lives in. The same 200 MW campus is a brilliant asset in one 2030 and a stranded liability in another, and the difference is which of a few structurally distinct futures actually arrives. The scenario is the largest uncontrolled variable in any AI-infrastructure thesis, and the one most often smuggled in as an unexamined assumption.

We frame 2030 along three axes that move semi-independently. First, the demand-and-capital regime: supercycle, digestion, or bubble — distinct from the firm-level economics of Chapter 1.8; here it is the sector-wide structural lens. Second, the architectural shape: centralized mega-campus versus distributed inference, the fork that decides where the megawatts go. Third, the industry structure and geographic re-map: who owns the capacity and where it lands. We then confront the power-supply endgame — CFE, SMR, fusion optionism, and the demand-side wildcards that could invalidate the whole demand curve — and close on stranded-asset and systemic risk, the downside each scenario hides.

The three scenarios: supercycle, digestion, bubble

Start with the demand-and-capital regime, because it sets the boundary conditions for everything else. The three scenarios are not optimist/realist/pessimist moods — they are different beliefs about a single mechanism: does AI revenue grow fast enough to service the capital being deployed before the assets depreciate? McKinsey's own framing spans a $3.7T-to-$7.9T range of AI-capable capex to 2030 against a ~$5.2T midline — a spread wide enough that the constrained and accelerated cases describe genuinely different industries (McKinsey, 2025).

Supercycle is the case where demand keeps outrunning supply: reasoning and agentic workloads inflate tokens-per-task, inference compute compounds, and power — not chips, not capital — stays the binding constraint through 2030. In this world the scarce asset is an energized megawatt, time-to-power is the master variable, and the operators who locked firm power and long-lead gear early win. Digestion is the soft-landing case: the extraordinary base is absorbed, capex growth decelerates sharply (one widely-cited path: ~51% growth in 2026 falling to ~13% in 2027 and ~5% in 2028) without a crash, and the winners are the disciplined operators who did not over-commit at the top. Bubble is the case where the revenue gap wins: the spend behaves like a utility build-out while revenue still behaves like software subscriptions, and the mismatch forces write-downs, cancelled announcements, and a depreciation reckoning. Sequoia's framing put the annual revenue that must materialize to justify the spend in the hundreds of billions and widening; Bain sized a ~$800B annual shortfall by 2030 even after AI-driven savings (Bain, 2025).

The decision that follows is not which scenario you predict — nobody knows — but which one your balance sheet is structured to survive. A supercycle bet is contracted, levered, and over-built on power; a bubble hedge is merchant-light, opex-flexible, and short on irreversible commitments. You cannot be optimized for both at once, and pretending you are is how operators get caught.

The three 2030 scenarios — structural signatures and what survives
ScenarioCore mechanismBinding constraintCapex trajectory to 2030What winsWhat strands
SupercycleAI revenue compounds with reasoning/agentic demand; tokens-per-task explodePower and long-lead equipment (chips/capital ample)Sustained ~20%+ CAGR; midline-to-accelerated ($5-8T)Early firm-power lockers; time-to-megawatt leaders; contracted+leveredLatecomers stuck in the queue; under-provisioned cooling/power substrates
DigestionExtraordinary base absorbed; growth decelerates without a crashUtilization and unit economics; filling what was builtSharp decel (51% to 13% to 5% on a cited path); flat-to-modestDisciplined operators who did not over-commit at the top; high-utilization fleetsSpeculative greenfield; over-levered merchant capacity
BubbleRevenue gap wins; spend behaves like a utility, revenue like SaaSMonetization; willingness-to-pay per query/seat/API callSharp cuts; cancelled announcements; write-down waveOpex-flexible, merchant-light hedgers; those who kept optionality cheapLong-lived debt on short-lived silicon; under-depreciated fleets; idle substations
A decision lens, not a forecast. Probabilities deliberately omitted; the point is to identify which posture survives each world, not to handicap them. Capex/gap figures are 2025-2026 vintage and contested (McKinsey, Bain, Sequoia/Dell'Oro).

Centralized mega-campus vs distributed inference

The second axis is architectural, and it is orthogonal to the demand regime: even a supercycle splits between two physically different build-outs that pull siting and design in opposite directions. Centralized mega-campus is the gigawatt-scale training factory — one tightly-coupled supercomputer chasing the cheapest firm power and the coldest climate, indifferent to user proximity, with the gigawatt campus as the unit of compute (→ Chapter 16.1). Distributed inference is the fleet of smaller, latency-first sites pushed toward users — metro colos, edge nodes, 5G MEC, branch and venue deployments — because for most inference, latency, privacy, and egress cost dominate, and a small site near the user beats a remote gigawatt campus.

The forecast that makes this fork decisive is the inference transition: by the end of the decade the majority of AI compute is inference, not training, even as frontier training concentrates into 1 GW-plus campuses that become standard (Bain, 2025). That bifurcation is the whole point. If you build only the centralized campus, you have optimized for the shrinking-share workload and a power-first remote site; if you build only the distributed fleet, you cannot host frontier training and you pay a latency-first energy premium of 2-4x. The two design bases share almost nothing — density, redundancy, fabric blocking, and siting driver all invert — which is why this is a fork to decide at scoping, not a dial to tune later. Reasoning and test-time compute, which inflate the decode-heavy share, push the center of gravity toward the distributed-inference side over the decade (→ Chapter 16.3).

Industry structure and the geographic re-map

Who owns the 2030 capacity is a third axis. Three operator archetypes are consolidating, each carrying a different cost-of-capital and obsolescence exposure. Hyperscalers self-fund the largest share — the top-four US hyperscalers alone are tracking toward roughly $600B of data-center capex in 2026 (CreditSights/Dell'Oro), with the big-five-plus-Oracle cluster cited as high as ~$725B — financing from cash flow and carrying the depreciation debate on their own books. Neoclouds are the pure-play GPU landlords: capital-intensive, debt-financed, margin-pressured, and the most exposed to a utilization or residual-value shock because their entire asset is the depreciating silicon. Sovereign and enterprise buyers — nation-states pursuing compute independence, regulated industries pursuing data residency — are the fastest-broadening demand source, and the one least governed by pure unit economics.

The geographic re-map follows from where firm power and permissive policy actually exist. Power-first training campuses migrate to stranded-generation and cold-climate regions; latency-first inference clusters stay in the metros. Sovereign demand and export controls re-map the map again: the (later rescinded) US AI-diffusion tiering, Gulf-state build-outs converting energy wealth into compute, and the empirical reality that residency is not control — a study of 775 non-US data centers found sovereignty depends on control-of-stack, not just where the concrete sits (arXiv, 2025). The consequence for a 2026 siting decision: the cheapest-power, fastest-permit jurisdiction may carry a geopolitical or export-control tail risk that a spreadsheet does not price. → grid integration in Chapter 15.8.

The power-supply endgame

Every 2030 scenario eventually collides with the same wall: where do the firm, clean megawatts come from, and when? Global data-center electricity demand is on track to roughly double from ~485 TWh in 2025 to ~950 TWh by 2030 (~3% of global electricity), with AI-specific load tripling (IEA, 2026). In the US, data centers move from ~4-5% of electricity today toward 9-17% by 2030 on EPRI's scenarios. The endgame is a ranking of supply options by the one variable that actually gates a build: time-to-megawatt, not headline LCOE.

The ordering that matters is that the clean-and-firm options that look best on a carbon spreadsheet are the slowest to energize. Existing nuclear and restarts are the only firm-clean option available now — the Three Mile Island/Crane restart for Microsoft (835 MW), Amazon-Talen (~2 GW) — but the fleet is finite and largely spoken for. SMRs are real but late: Google-Kairos and Amazon-X-energy deals target first units around 2030 and full build-out toward 2035, and the 2030 dates are widely judged optimistic. Fusion is optionism: Commonwealth Fusion targets grid power by 2030 with SPARC/ARC, but no one should underwrite a 2030 build on a fusion megawatt. That leaves gas-and-grid — behind-the-meter gas (~82-101 GW announced cumulatively, though only single-digit GW under construction) and grid interconnection (3-7+ years, up to ~10 in the worst queues) — as the default bridge that actually carries the load this decade, at a carbon cost the CFE commitments must then offset. → speed-to-power mechanics in Chapter 3.2.

Power-supply endgame — ranked by time-to-megawatt, not LCOE
Supply optionRealistic availabilityFirm?Clean?Role in a 2030 buildKey risk
Existing nuclear / restartsNow (PPA-dependent)YesYesAnchor firm-clean load; scarce and largely contractedFinite fleet; megadeals already taken
Grid interconnection (new)3-7+ yr (to ~10 in worst queues)Yes (grid)Grid mixThe default firm supply; the queue is the real gateQueue length; transformer lead times (~128+ wk)
Behind-the-meter gas18-36 mo (turbines), faster if refurbYesNoThe bridge that actually carries the decadeCarbon exposure; only single-digit GW under construction
SMR~2030 first units, ~2035 fleetYesYes2030+ optionism; do not underwrite a build on it yetLicensing/NRC timeline; first-of-a-kind cost
Fusion2030s+ (uncertain)YesYesPure optionism; a hedge, not a planUnproven at commercial scale; timeline risk
Decision lens for a 2026 siting/power commitment. Lead times and capacities are 2025-2026 practitioner ranges (IEA, EPRI, SemiAnalysis, SMR Intel, DCD); SMR/fusion dates are announced targets widely regarded as optimistic.
$3.7T-$7.9T
range of AI-capable data center capex to 2030 (~$5.2T midline) — the scenario spread itself
the range is so wide that betting on any single point estimate is a coin-flip
2025McKinsey, 'The cost of compute'
~$800B
annual AI revenue shortfall by 2030 even after AI-driven savings (the bubble-case gap)
the gap that has to close for the build-out to pay off — if it doesn't, this was a bubble
2025Bain & Company, Global Technology Report
~$600B
top-4 US hyperscaler data center capex in 2026 (~+36% YoY; big-five-plus cited to ~$725B)
a commitment so large the giants can't quietly walk it back without a reckoning
2026CreditSights / Dell'Oro Group
~485 → ~950 TWh
global data center electricity demand 2025 → 2030 (~doubling; ~3% of global electricity)
power doubling on a grid that can't keep pace is the constraint every scenario hits
2026IEA, Electricity 2026 / Energy and AI
9-17%
data centers as share of US electricity by 2030 (from ~4-5% today)
at this share you become a political target for rate-payer backlash and siting moratoria
2026EPRI, Powering Intelligence 2026
~2030 / ~2035
SMR first units / full build-out targets (Google-Kairos, Amazon-X-energy); 2030 dates widely judged optimistic
don't bank on nuclear arriving in time to relieve your power constraint this decade
2026SMR Intel / DCD / TechCrunch synthesis
~70%
breakeven utilization for a debt-financed neocloud cluster (swings -$330k to +$340k/mo, 55% → 85%) (contested — single-source)
below this the same hardware that prints money bleeds cash
2025AM Compute / SemiAnalysis
2-3 yr
frontier-economic GPU life vs 5-6 yr book life — the obsolescence clock under every scenario (CONTESTED)
if chips obsolete before they're paid off, the sector's reported profit is suspect
2026CNBC / SemiAnalysis synthesis

Demand-side wildcards

The entire demand curve rests on assumptions that a single shock could invalidate — and the wildcards cut both ways, which is what makes them dangerous to ignore. On the downside: an algorithmic-efficiency step (a DeepSeek-style training- or inference-cost collapse) that deflates the compute needed per unit of value; an enterprise-adoption air-pocket (the MIT NANDA study found ~95% of enterprise GenAI pilots produced no measurable P&L impact on $30-40B of spend); or a regulatory/energy backlash that caps siting. On the upside, the same efficiency gains can increase total compute via the Jevons paradox — cheaper inference begets more inference — and reasoning/agentic workloads are a structural demand multiplier that could keep the supercycle alive longer than the bears expect (→ Chapter 16.3).

The decision consequence is asymmetric. A pure-play, single-generation, debt-financed asset is fragile to every downside wildcard and only benefits from the upside ones if it is already full. A flexible substrate — over-provisioned floor loading and water, modal procurement, contracted-not-merchant revenue, a power deal that flexes — is the cheapest insurance against the wildcard you cannot predict. You are not buying a forecast; you are buying the right to be wrong about the forecast.

Deep dive: why the efficiency wildcard is the hardest to scenario-plan

The efficiency wildcard is uniquely hard because it is genuinely two-sided and the sign is unknowable in advance. The bear reading: a frontier algorithmic advance — sparser models, better quantization, a cheaper attention mechanism, distillation that closes the gap to a frontier model at a fraction of the FLOPs — collapses the compute needed per unit of delivered value, the demand curve undershoots, and a wave of capacity built against the old efficiency assumption strands. The DeepSeek episode was the proof-of-concept that a single release can re-price the entire compute-demand thesis overnight.

The bull reading is the Jevons paradox: when a resource gets cheaper, total consumption rises rather than falls. Cheaper inference makes more applications economically viable, reasoning models that were too expensive to run at scale become default, and aggregate token demand increases even as cost-per-token falls (market-average inference fell from roughly $10 to ~$2.50 per million tokens in a year, and demand exploded over the same window). Both readings have empirical support, and they can be true sequentially: a sharp efficiency gain strands the operators positioned for the old curve while rewarding those who can absorb the new, higher-volume, lower-margin demand. The only robust posture is to design the asset so it earns under both — high utilization, low unit cost, and a fleet that can pivot from training-shaped to inference-shaped as the mix shifts. The operators who scenario-planned only the bull case are exposed to the bear shock, and vice versa; the survivors planned the transition between them. → the efficiency-vs-demand treatment in Chapter 16.3.

Stranded assets, obsolescence and systemic constraints

Each scenario hides a different stranded-asset failure mode, and naming them is the point of the whole exercise. Stranded silicon is the obsolescence risk: the 2-3 year frontier-economic life vs the 5-6 year book life (CONTESTED) means a generational density step — the ramp from ~132 kW NVL72 racks toward ~600 kW Kyber-class racks — can leave current-generation fleets uneconomic against newer parts and uncompetitive against grid power before they are depreciated. Stranded substations is the power-delivery mirror image: an interconnection slot energized for a campus whose demand never materializes, or a behind-the-meter gas plant carrying carbon liability for a load that digested. Stranded balance sheets is the financial endgame: long-lived debt underwritten against short-lived silicon, the under-depreciation question that turns reported earnings into borrowed future write-downs (→ Chapter 1.8).

The systemic and societal constraints are the outer boundary on all three scenarios. Grid reliability is now a planning constraint, not a footnote — NERC issued a rare Level 3 alert after large-load loss events (~1.5 GW dropped in 82 seconds in one Virginia event), and ride-through is now mandatory. Water, community social license, and the concentration of load in a handful of jurisdictions (Virginia alone projected at 39-57% of state power) are real ceilings that a demand curve cannot wish away. The deepest systemic risk is correlation: every scenario assumes the constraints relax independently, but a power slip, a residual-value shock, and a demand air-pocket are correlated — they tend to arrive together in a downturn, which is exactly when a levered, single-generation, merchant-exposed asset has the least room to survive them. The dual-use framing matters here too: the same failure modes that random faults trigger are attacker-induceable (→ Chapter 11.10).

Deep dive: how to build an asset that is robust across scenarios rather than optimal for one

The instinct under uncertainty is to forecast harder and optimize for the most-likely scenario. That is the wrong instinct, because the cost of being optimized for the scenario that does not arrive is catastrophic and the cost of being merely robust across all three is modest. The robust posture has five concrete moves, each trading a little day-one efficiency for survival across worlds.

One: over-provision the irreversible substrate, defer the reversible fit-out. Floor loading, water availability, electrical headroom, and pipe-rack space accommodate the density ramp toward 600 kW racks; the IT fit-out stays matched to the current generation. You buy the option to ramp without committing the spend (→ Chapter 14.9). Two: keep procurement modal. A powered shell and colo/neocloud overflow preserve the option to exit that a full greenfield build forecloses — the difference between a digestion soft-landing and a stranded-asset write-down. Three: contract revenue, not merchant it. Take-or-pay and credit-tenant leases set debt capacity and survive the bubble; merchant exposure is a leveraged bet on the supercycle. Four: make the power deal flex. Grid services, curtailable load, and demand-response convert a fixed power liability into a hedge that earns in digestion and survives in bubble (→ Chapter 15.8). Five: design the fleet to pivot from training-shaped to inference-shaped as the compute mix shifts toward inference-dominant, so the same asset earns whether the centralized or distributed architecture wins. None of these is free; all of them are cheaper than being precisely optimized for the 2030 that did not come.

This chapter sits atop Part 16 and pulls the threads together. The power-bound framing that makes time-to-megawatt the master variable is Chapter 16.1; the subsystem roadmaps that drive the density ramp (415 VAC → 800 VDC, NVL72 → Kyber, HBM4) are Chapter 16.2; the efficiency-vs-demand and Jevons dynamics that govern the demand-side wildcards are Chapter 16.3; and the macro economics of the build-out — capex wave, financing, revenue-vs-capex gap — are Chapter 16.4. The firm-level economics and depreciation debate that the bubble scenario rests on live in Chapter 1.8; the inference-distribution argument in Chapter 1.3; speed-to-power mechanics in Chapter 3.2; grid integration and flexibility in Chapter 15.8; the reliability rethink that goodput-survives-failure depends on in Chapter 12.2; refresh and decommissioning economics in Chapter 14.9; and the cyber-physical dual-use of every failure mode in Chapter 11.10.