“That being said, we're yet to see this actually happen, outside of OpenAI's alleged $3.4 billion of yearly revenue (it still loses $5 billion a year), and generative AI's multi-billion dollar contribution to Amazon Web Services revenue over an indeterminate amount of time.”
Our reading, the sentence that was checked:
Outside of OpenAI's alleged $3.4 billion of yearly revenue (while it still loses $5 billion a year) and generative AI's multi-billion dollar contribution to AWS revenue over an indeterminate period, we have yet to see revenue growth for cloud providers from organizations building their own AI integrations.
Assessment: Contradicted Evidence as of
Where and when Ed Zitron wrote it
Where's Your Ed At, The Other Bubble, paragraph 18.
- Said
- Source observed
- live page, full text, public
- Evidence as of
- the cutoff for this assessment
- Assessment recorded
- assessment wyea-saaspocalypse-now-e607df-a2
We recorded 27 claims from this post. See every claim from this post.
The wording above is the version this site observed on 2026-10-28. The source may have been edited after 2024-09-26. This page does not claim the wording was captured then.
What the claim commits to
- Kind
- Observation
- Deadline, as the speaker wrote it
- None stated. This site does not add one.
- Deadline state when assessed
- No horizon
- Deadline state on 2026-10-29
- No horizon (the release’s reference date)
Conditions
- outside of OpenAI's alleged revenue and generative AI's contribution to AWS revenue (qualifier, stated by the speaker)
From the speaker
- we're yet to see this actually happen
- outside of OpenAI's alleged $3.4 billion of yearly revenue
- it still loses $5 billion a year
- generative AI's multi-billion dollar contribution to Amazon Web Services revenue
Our interpretation
- The proposition being assessed is the absence of observable cloud-provider revenue growth from customer AI integrations, beyond the stated exceptions.
- OpenAI's revenue and loss figures are embedded exceptions, not separate claims being graded here. No annualized figure is treated as realized annual revenue.
- The ordinary reading includes revenue from cloud AI services through which organizations build applications and integrate models.
- The OpenAI exception concerns OpenAI's own stated revenue; it does not exclude Microsoft's Azure AI services simply because some use OpenAI models.
- The target is April–June 2024, the latest completed quarter publicly reportable before the post.
- Microsoft Azure is an in-scope test of the general negative assertion. The metric scope records that counterexample and the company's reported attribution, without imposing a dollar threshold.
Counts as supported if: Adequately comprehensive disclosures show no realized AI-services contribution to cloud revenue growth outside the stated exceptions during the target period.
Counts as contradicted if: An in-scope cloud provider publicly reports a positive realized revenue-growth contribution from AI services used for customer applications or integrations during the target period.
Retrospective: these criteria were written after the outcome was public.
Current assessment
Was it true for the period described?
Outcome: Contradicted
The dated evidence goes against what the claim committed to, under the criteria frozen before grading.
Scored on a plain reading. The speaker named no measure for this claim, so it was judged on the reading an informed reader would take, stated below under our interpretation. Both reviews had to find that reading fair.
- Evidence as of
- Deadline state when assessed
- No horizon
- Assessment recorded
- Policy version
- 2026-10-28.7
Rationale
On July 30, 2024, Microsoft reported that AI services contributed eight percentage points to Azure revenue growth for the April–June 2024 quarter [e1, e2]. This was a reported contribution to realized quarterly growth, not an annualized revenue estimate [e1, e2]. Under the contract's reading that customer AI integrations include cloud AI services, Azure supplies a counterexample outside the exceptions for OpenAI's own revenue and AWS [e1]. The disclosure therefore contradicts the claimed absence of observable growth under that reading, while leaving the contribution from customer-built integrations alone unquantified [e1].
Limitations
- Microsoft's reported AI-services contribution does not separately quantify customer-built integrations; the assessment depends on the contract's broader reading [e1].
- The growth attribution does not establish AI-services profitability [e1].
- These disclosures do not verify the embedded OpenAI revenue and loss figures or the AWS revenue description; those exceptions are not separately assessed [e1, e2].
Evidence (2 items)
Goes against the claim: Microsoft,
8 points from AI services
Why it matters here: Microsoft publicly attributed eight percentage points of Azure growth to AI services before the post. The same call describes organizations using Azure's model services, making this a counterexample under the ordinary reading of customer AI integrations.
- Publisher
- Microsoft
- Kind of source
- Company disclosure: the company describing itself, not an independent finding
- Measures
- Microsoft, AI services contribution to Azure revenue growth percentage points, company reported, 2024-04-01 to 2024-06-30
- Describes events of
- Public from
Context only: Microsoft,
as of June 30, 2024
Why it matters here: The associated release identifies the reporting cutoff. It is used to check timing, not as a separate AI-revenue measurement.
- Publisher
- Microsoft
- Kind of source
- Company disclosure: the company describing itself, not an independent finding
- Describes events of
- Public from
Where it was said (1)
Said once in the sources this register covers.
: Where's Your Ed At, The Other Bubble
That being said, we're yet to see this actually happen, outside of OpenAI's alleged $3.4 billion of yearly revenue (it still loses $5 billion a year), and generative AI's multi-billion dollar contribution to Amazon Web Services revenue over an indeterminate amount of time.
- Where
- paragraph 18
- Published
- 2024-09-26
- Source observed
- , live page
- Access
- full text, public
History
Assessment versions
- Assessment wyea-saaspocalypse-now-e607df-a2: Current. Outcome: Contradicted. Evidence as of 2026-10-28. Public date not recorded.
Recorded events
Assessment publishedBy this site
First assessment published after both reviews and the final-text check passed.
HeldBy this site
The final-text check failed: rationale_supported_by_evidence, citations_correct; overclaims: Its earnings call also described organizations using Azure's model services..
About assessment wyea-saaspocalypse-now-e607df-a1, which was not published.