OpenAI's Run-Rate Miss Exposes How AI Revenue Gets Measured
The error was arithmetic, not demand. Every mark built the same way carries it, and the two benchmark labs don't even define revenue alike.
Where the $20B went
A run-rate is one month of revenue multiplied by twelve. On the corrected figure, OpenAI's implied monthly revenue is about $4.2B, not the ~$5.8B the $70B headline implied. That is a gap of roughly $1.7B a month, using The Information's arithmetic on the FT report. OpenAI restated nothing. The Information's Martin Peers blames "clunky calculations" by investors and reporters working from second-hand investor communications.
The valuation effect is mechanical. Take an illustrative price struck at 20x the $70B figure: it is 28x the corrected figure. Anyone bidding on OpenAI secondaries against the old number is working with a denominator that fell about 29%.
The two benchmark numbers aren't comparable
The Information reports that OpenAI and Anthropic treat the cloud partners' cut differently when they count revenue. The reporting does not say which lab reports gross revenue and which reports it net of that cut. Neither figure is audited or disclosed on a schedule. Any relative-value comparison between the two labs therefore starts with a definitional error, before a multiple is even applied.
The same gross-versus-net ambiguity runs down to the application layer. Startups that resell model capacity can book pass-through inference spend as top-line revenue.
Public infrastructure is priced on private leaks
Nvidia, CoreWeave and Nebius sold off on a correction to one unaudited number for one customer. Demand did not change; only the market's knowledge of it did. That shows how much of the listed AI-infrastructure story rests on a single lab's revenue. It also shows how exposed private neocloud and infrastructure rounds with concentrated OpenAI backlog are to the next leak, in either direction.
Peers expects IPOs to ease the problem once real numbers become visible. He also notes that some public companies have started issuing annualized estimates themselves. The run-rate convention is moving into public markets, not dying there. Companies that report audited, consistently defined revenue on a schedule should earn a disclosure premium.
OpenAI's business didn't change on Thursday; only the market's knowledge of it did, and that was enough to move listed AI infrastructure.
Governance landed the same week
The Information reports that three OpenAI safety researchers fired last week now publicly allege they were punished for raising safety concerns. Separately, Last Week in AI reports that safety lead David Robinson resigned. Writing in The Atlantic, he called OpenAI's culture broken and cited a breach of Hugging Face systems by OpenAI agents. Common Sense Media also rated ChatGPT for Teens an "unacceptable risk." None of this changes revenue. It does mean diligence on OpenAI paper now has open questions about both the numbers and the governance behind them.
The smart move
The edge this quarter belongs to investors with direct access to real financials. For marks, ask each AI portfolio company to reconcile its latest month × 12 against trailing-three-month recognized revenue × 4. The Information suggests flagging any gap above 15% for review. For new paper, write the revenue definition into the term sheet: recognized rather than annualized, net of cloud and model pass-through, with a representation on how it was calculated.
What to do
Require every AI portfolio company to submit a reconciliation of month×12 run-rate against trailing-three-month recognized revenue ×4, with a gross-vs-net statement on cloud pass-through, before Q3 marks go to LPs
Re-underwrite any pending OpenAI or AI-lab secondary or tender bid anchored to the $70B figure this week, and confirm gross vs. net treatment before comparing it with Anthropic paper
Map how much of the contracted backlog at each infrastructure and neocloud holding traces to OpenAI, and present the concentration to your IC this quarter