Revenue
Service already delivered and recognized in the period.
Contract-quality deep dive · August 2026
Backlog Is Not Revenue: Reading AI Infrastructure Contract Quality
$104 billion is an impressive number. It is also not $104 billion of revenue sitting in an account. CRWV's backlog is real evidence of demand; the investor's job is to determine how much becomes revenue, when it arrives, what it costs to deliver, and who finances the trip.
By Aydin AliPublished August 20, 2026Data through Q2 20269-minute read
My conclusion
I used to read backlog as proof. Now I read it as a set of questions. A contract can be committed and still be delayed, concentrated, capital intensive, or low-return after depreciation and interest.
Five nouns I will not use interchangeably
Deferred revenue
Customer consideration billed or collected before the related service is recognized.
RPO
Transaction price assigned to performance obligations that remain wholly or partly undelivered.
Revenue backlog
A management-defined measure that may include RPO plus other estimated future amounts.
Total contract value
The headline value of an agreement, sometimes including options or conditional capacity.
Cash
The part that can actually fund GPUs, data centers, interest, and payroll today.
What CoreWeave actually disclosed
CRWV reported $103.7 billion of unsatisfied remaining performance obligations at June 30, 2026. Its definition includes billed and unbilled consideration, net of estimated variable consideration such as service credits, delivery delays, and capacity the company has the right to resell. The filing also gives a recognition schedule. Q2 filing, p. 15 ↗
First 24 months41% · $42.5B*
Months 25–4839% · $40.4B*
Months 49–7820% · $20.7B*
*AEA calculation. I multiplied the company's disclosed percentages by $103.7 billion. This is not quarterly guidance and should not be assumed to convert evenly. Large contracts arrive in steps, and delivery timing matters.
The demand signal is strong. So is the delivery bill.
$2.58BQ2 revenue, reported
$6.42BQ2 capital expenditures, reported
$640MQ2 net interest expense, reported
72%Revenue from top three customers, reported
For the first half, CRWV spent $14.12 billion on capital expenditures against $4.65 billion of revenue. My simple operating-cash-flow-minus-capex calculation is negative $10.45 billion. I am deliberately not calling that company-reported free cash flow; it is a stress test showing the size of the funding gap while capacity is being built.
The contracts have real protection. The company says take-or-pay committed contracts produced 98% of second-quarter revenue, and active contracts commonly included prepayments equal to 15%–25% of total contract value. But service-level failures can still produce credits, refunds, termination, or the loss of future payments. “Committed” is not the same word as “unconditional.”
Same headline, different contract quality
NBIS / Meta agreement
$12B + up to $15BThe first portion covers five-year dedicated GPU-cluster orders. The second is a backstop for specified capacity that remains unsold; NBIS intends to sell that capacity elsewhere first. The two dollars should not receive the same certainty weight.
ORCL customer-funded hardware
$75BOracle said much of its fiscal 2026 RPO increase came from large AI contracts where customers prepaid for GPUs or supplied them. Backlog backed by customer-funded hardware carries a different financing burden from provider-funded construction.
My six-part contract-quality test
- DefinitionIs the number GAAP RPO, management-defined backlog, or an “up to” contract value?
- ConditionalityWhat can be cancelled, delayed, credited, resold, or terminated?
- TimingHow much converts inside 12 or 24 months, and how much sits five years away?
- ConcentrationHow much revenue and receivables depend on the largest customers?
- FundingDid the customer prepay or supply hardware, or must the provider raise debt and equity?
- Unit economicsWhat remains after depreciation, power, leases, and interest—not just adjusted EBITDA?
The fair bull case
This is not an argument that backlog is fake. CRWV's RPO is defined in a filing, net of estimated variable consideration, supported by take-or-pay contracts, and accompanied by a conversion schedule. Revenue more than doubled year over year. Long-duration commitments can provide unusually strong visibility and support asset-backed financing.
The point is narrower: visibility into future demand is not the same as visibility into future returns. The provider still has to deliver the capacity on time and earn more on the assets than the assets cost to build and finance.
The rule I am keeping
Backlog earns a place in the thesis only after I discount it for time, delivery risk, concentration, financing, and margin. A reservation book is useful. It is not a cash register.
Primary-source ledger
Figures are reported unless marked as an AEA calculation.