brianletort.ai
Back to Issue 14

Capital flow drill-down

Money in, revenue out — the full breakdown.

Issue 14 · Week 30 of 2026.

The four-category capital scorecard expanded with named transactions, burn-to-revenue context, and a per-category trend across recent issues. Each row corresponds to a row in the summary table on the issue page.

Category

Frontier Labs.

OpenAI, Anthropic, Google DeepMind, xAI

Capital in

~$95B

vs ~$95B

Revenue out

~$21B

vs ~$21B

Burn / rev

~4.5x

Lower means more capital out than in.

The read

The capital position did not change, but the obligation did. Camellia turns the abstract infrastructure plan into a utility-backed schedule with full infrastructure-cost recovery and up to 1 GW of curtailment; runway analysis that ignores contracted infrastructure commitments is increasingly incomplete.

This week’s transactions

  • 2026-07-22

    AMD and Anthropic announced up to $5B of AMD equity investment and deployment of up to 2 GW of MI450-series GPUs and Helios systems

    AMD

    Up to $5B / 2 GW
  • 2026-07-22

    Project Camellia in Effingham County, Georgia: $20B campus, 3.2 GW staged service from 2028-2032, customer-funded infrastructure, up to 1 GW peak curtailment

    OpenAI; secondary reporting on aggregate plan

    $20B

Trend across recent issues

W23W24W25W26W27W28W29W30
Capital inRevenue out/$B per issue

Category

Hyperscaler-Hosted.

Azure-OpenAI, AWS-Anthropic, Google Cloud-Gemini, Oracle-OCI

Capital in

~$230B

vs ~$210B

Revenue out

~$62B

vs ~$62B

Burn / rev

~3.7x

Lower means more capital out than in.

The read

The ratio moved the wrong way for near-term returns but the utility structure is more mature: OpenAI pays the infrastructure cost and offers dispatchable load. Expect large campuses to be financed and permitted as grid partnerships rather than ordinary commercial-load connections.

This week’s transactions

Trend across recent issues

W23W24W25W26W27W28W29W30
Capital inRevenue out/$B per issue

Category

Neoclouds.

CoreWeave, Nscale, Crusoe, Lambda, Fluidstack, IREN

Capital in

~$17B

vs ~$17B

Revenue out

~$5B

vs ~$5B

Burn / rev

~3.4x

Lower means more capital out than in.

The read

A credible AMD rack can reduce both supply concentration and equipment financing risk, but only after deliveries exist. Neoclouds should negotiate Helios options now while keeping revenue commitments tied to measured availability and customer demand, not vendor performance projections.

This week’s transactions

  • 2026-07-20

    Hut 8 Beacon Point Phase 2: 15-year, 352 MW agreement with $9.8B of base-term revenue

    Hut 8 SEC Form 8-K

    $9.8B base term / 352 MW
  • 2026-07-23

    AMD cited multi-gigawatt OpenAI and Anthropic commitments in Helios coverage; delivery timing and realized rack economics remain the evidence to watch

    AMD

    Multi-GW commitments referenced

Trend across recent issues

W23W24W25W26W27W28W29W30
Capital inRevenue out/$B per issue

Category

On-Prem / Hybrid.

Enterprise GPU clusters, sovereign and national programs, Cisco / Dell / HPE

Capital in

~$101B

vs ~$101B

Revenue out

~$36B

vs ~$36B

Burn / rev

~2.8x

Lower means more capital out than in.

The read

The facility envelope is now part of accelerator procurement. Private-cluster buyers should compare complete rack power, cooling, fabric, support, and software maturity across Helios and Rubin; component-level benchmark wins are not enough to underwrite a 246 kW deployment.

This week’s transactions

  • 2026-07-24

    Schneider Electric published a 246 kW facility reference design for AMD Helios

    Schneider Electric

Trend across recent issues

W23W24W25W26W27W28W29W30
Capital inRevenue out/$B per issue

Methodology

Capital-in and revenue-out figures are quarterly or annualized as noted in the row, sourced from public earnings disclosures, SEC filings, and lab and vendor announcements. Burn-to-Revenue is revenue divided by committed capital. The trend chart shows up to eight prior issues. Data is updated weekly; revisions in future issues do not retroactively edit this one.

Back to the full issue