← back to the archiveCover illustration for “AI ROI headlines choose their denominator”
POSTday 52·1 week ago·by Andy Padia

AI ROI headlines choose their denominator

Only 12% of CEOs see AI returns — and about 44% report a financial gain. Both come from the same PwC table; which cut a speaker quotes tells you their agenda, not AI's ROI.

A boardroom-AI newsletter landed in my inbox on July 22 leading with a familiar stat: only 12% of CEOs see returns from AI. The number comes from PwC's 2026 Global CEO Survey — 4,454 CEOs across 95 countries, published January 27, 2026. Six months old, and still headlining. At this age a survey stat is no longer reporting; it is doing framing work.

So look at the actual table. Per the survey, 12.5% of CEOs report both revenue and cost benefits from AI. Separately, 30% report increased revenue, 26% report lower costs, and 56% report neither. One caveat before anything else: I could not reach PwC's primary pages — pwc.com returned 403 on both the global and regional press releases in my run — so these figures are carried via ITChannelOxygen's coverage and consistent excerpts of PwC's own regional pages. If you are going to quote them in a deck, chase the primary first.

Now do the arithmetic the headlines skip. If 30% saw revenue gains, 26% saw cost gains, and 12.5% saw both, then the union — CEOs reporting at least one financial benefit — is 30 + 26 − 12.5, roughly 44%. "Only one in eight sees returns" and "nearly half report gains" describe identical data. Both sentences are honest. Quoting one without the other is a choice.

The number reveals the speaker

My rule for reading any AI ROI statistic: identify the denominator and the cut before you accept the adjective. The intersection cut (both revenue AND cost) is the hardest test available in that table, so it produces the crisis number. The union cut (either benefit) is the softest, so it produces the momentum number. A consultant selling transformation quotes 12%. A vendor selling adoption quotes 44%. Neither is lying; both are selecting.

PwC's own gloss makes the ambiguity worse, not better: CEOs with "strong AI foundations" are roughly three times more likely to report returns. Read as a skeptic, that says most deployments are too shallow to pay. Read as a booster, it says embedding works and the laggards just need to catch up. The same sentence funds both keynotes — which is exactly why this survey will still be headlining next January.

The budget meeting where this played out

A client executive opened a budget review by quoting "88% of AI fails to deliver" — the 12% stat, inverted for drama. I did not argue the number. I drew the two-by-two on the whiteboard: revenue benefit yes/no, cost benefit yes/no, filled in 30, 26, 12.5, and let the union fall out at about 44. The room's mood changed less because of the bigger number and more because the trick was now visible.

Then I asked the question that mattered: if we ran this survey on your organisation, which cell would you even be able to prove you were in? They had no revenue attribution tied to any AI deployment and no cost baseline from before the rollout. That is the honest finding hiding under the framing fight — most organisations quoting these surveys could not generate their own row in the table.

Steal this for the next time a single AI ROI number enters a meeting: ask three questions in order. What is the denominator? Is this the intersection or the union cut? And what would our own number be, measured the same way? The first two defuse the rhetoric. The third usually reveals that the real gap is not AI performance but measurement machinery — and that is a fixable, fundable problem, unlike a vibes war over someone else's survey.

A survey table is a menu of honest numbers; whoever picked the 12% — or the 44% — is telling you what they are selling.

#roi#surveys#executive-communication#ai-strategy#statistics
← older drop
AI feature news needs changelog provenance
newer drop →
Free LLM routers are paid for in telemetry

related drops

explore all 78 drops →
← back to the archiveday 59