Blog AI productivity
AI value in the real world
Why AI Productivity Gains Do Not Automatically Become Business Results
AI can make individual tasks faster. But the business benefit depends on what happens after the first draft: review, usable capacity and measurable outcomes.

15 / 20
Baseline or comparison (sources that compare AI-assisted work with a control, earlier period, or non-adopter group)
1 / 20
Review cost captured (sources that measure realistic end-to-end time against a quality threshold that includes checking and correcting AI)
8 / 20
Business result tracked (sources that connect AI to revenue, cost, customer operations, labor, or another outcome beyond individual speed or output quality)
The thesis
The productivity chain has four links: faster task → accepted work → freed capacity → business result. Most public evidence measures the first link. Very little measures all four.
The scene
The green dashboard that could not answer for pipeline
Faster drafts are real. So is the conversion gap.
It is Friday afternoon on a lean B2B marketing team. The AI dashboard looks green. Draft time is down. More emails left the building this week than last month. Someone asks the obvious question in standup: “So… did any of that move pipeline?”
Silence. Then a shrug. Then a slide that shows activity, not outcomes.
That is the conversion gap in one meeting. A faster first draft is real. So is the follow-on work the dashboard does not show: source checks, brand corrections, handoffs, and rework. Even when the asset is accepted, the freed minutes may vanish into more low-priority production. More activity still does not guarantee demand, conversion, retention, or margin.
The practical question is not “Does AI make people faster?” It is: where does the productivity claim break before it becomes a business claim?
The chain
Four links from faster task to business result
Local efficiency can improve while the business result stays flat.
The conversion chain
The proof
What 20 public sources actually measure
Counts reflect reported measurement, not a pooled ROI.
Teamulate coded 20 experiments, field studies, surveys, and public enterprise cases against three questions using only what each source reports publicly: baseline or comparison, review cost inside the measured workflow, and a business or operational result beyond individual speed or output quality.
15 / 20 include a baseline or comparison. 1 / 20 clearly captures verification inside the measured workflow. 8 / 20 track a business or operational outcome.
The rarest measurement is the most important one. Without review and correction time, a productivity study may measure how quickly AI creates something, not how quickly a business receives work it can safely use. The percentages are not averaged: tasks, tools, samples, and outcome definitions are too different for a defensible universal ROI number.
Task gains
Strong gains exist, and so do zero or negative ones
Capability is not a universal rate of return.
Controlled studies show material gains on clearly scoped tasks: roughly 40% less completion time and 18% higher rated quality on professional writing (Noy & Zhang); a 15% average increase in issues resolved per hour across 5,172 support agents (Brynjolfsson, Li & Raymond); consulting gains of 12.2% more tasks, 25.1% faster, and more than 40% higher quality inside the frontier (Dell’Acqua et al.); and 55.8% faster completion on a defined coding task with GitHub Copilot (Peng et al.). Seven online-retail field experiments produced sales effects from 0% to 16.3%.
The evidence changes when work is complex or outside the model’s frontier. METR found experienced open-source developers took 19% longer with early-2025 AI tools on real issues in repositories they knew well, after expecting to be 24% faster, and still believing they had been 20% faster despite the measured slowdown. Consultants using AI were 19 percentage points less likely to reach the correct answer outside the frontier. A 2026 programming meta-analysis found a moderate positive average effect with substantial heterogeneity and smaller gains in open-source and enterprise settings.
Enterprise gap
More activity is not automatically more value
Adoption is broad. Financial results remain concentrated.
Three widely cited signals answer three different questions: +21.2% more productivity-app actions among high-use AI adopters in M365 trace data (changed behavior); 1.4% of total work hours reportedly saved in a national worker survey (perceived efficiency); and 0% measured productivity difference in an S&P 500 deep-adoption analysis (organizational output). They can all be accurate while pointing different ways because they sit at different points in the conversion chain.
McKinsey’s 2026 survey reports that 80% perceive individual productivity improvement, while 37% report at least some EBIT impact. In PwC’s survey of 4,454 CEOs, 56% report neither higher revenue nor lower costs from AI in the prior 12 months; only about 12% report both. A national U.S. adoption study estimates that only 1% to 5% of total work hours were AI-assisted despite broad awareness.
Public enterprise cases (Klarna, Morgan Stanley, Moderna, RB2B / Intercom) are useful leads for mechanisms and metrics, not transferable ROI forecasts. They rarely disclose full counterfactuals or implementation cost.
Where ROI breaks
Four gaps between claimed productivity and business value
The handoff between metrics is where claimed ROI usually disappears.
Gap 1
Speed without acceptance
A draft is faster, but reviewer time and correction are missing.
Gap 2
Acceptance without capacity
The asset passes, but no one verifies that usable hours were released.
Gap 3
Capacity without redeployment
Time is saved, but it is not assigned to a higher-value activity.
Gap 4
Activity without outcome
More work is produced, but customer or financial metrics do not move.
How to measure
A measurement model for B2B marketing
Track one recurring workflow through all four links.
Keep the brief, sources, quality gate, and reviewer comparable. For a B2B campaign email, measure human minutes to approved email, first-pass acceptance, factual or brand corrections, and variable AI cost. Then verify whether released time went to list quality, offer testing, or sales follow-up. The downstream metric might be qualified replies or meetings, not email volume.
| Layer | Primary metric | Required companion | Decision |
|---|---|---|---|
| Task | Active human minutes | Tool cost | Is the task faster? |
| Quality | First-pass acceptance | Rework + issue log | Is the result usable? |
| Capacity | Hours released | Hours redirected | Did work actually change? |
| Business | One downstream KPI | Baseline + time window | Did the business benefit? |
Minimum credible claim: “For this workflow, under these conditions, AI reduced human time to accepted work by X%, while first-pass acceptance changed by Y points and the selected business KPI changed by Z.”
Takeaways
What to do Monday
1. Measure the chain, not the demo
Faster task work is an input. Business value appears only when quality holds, freed capacity is redeployed, and a downstream outcome changes.
2. Review cost is the rarest measurement
Only 1 of 20 coded sources clearly priced verification inside the workflow (the step most teams skip when they claim ROI).
3. Expect strong gains and zero/negative gains
Task fit, frontier fit, and real-work context decide which result you get. Perception can still overstate speed after a measured slowdown.
4. Do not average unlike studies into one ROI
Track one workflow through task, quality, capacity, and one business KPI. Treat vendor cases as leads to test, not forecasts to copy.
AI productivity is a task-level input. Business value appears only when quality holds, freed capacity is deliberately redeployed, and a downstream outcome changes.
Teamulate publishes this research for lean B2B teams who want controlled, measurable marketing work: the logical next step after you stop mistaking faster drafts for business results.
Sources
Named sources
- Noy & Zhang, Experimental Evidence on the Productivity Effects of Generative Artificial Intelligence (Science, 2023)
- Brynjolfsson, Li & Raymond, Generative AI at Work (NBER / arXiv, 2023)
- Dell’Acqua et al., Navigating the Jagged Technological Frontier (SSRN, 2023)
- Peng et al., The Impact of AI on Developer Productivity: Evidence from GitHub Copilot (arXiv, 2023)
- Becker et al. / METR, Measuring the Impact of Early-2025 AI on Experienced Open-Source Developer Productivity (2025)
- Dell’Acqua et al., The Cybernetic Teammate (HBS Working Paper / SSRN, 2025)
- Cruces et al., Does Generative AI Narrow Education-Based Productivity Gaps? (arXiv, 2026)
- Maier et al., A Meta-analysis of the Effect of Generative AI on Productivity and Learning in Programming (arXiv, 2026)
- Fang et al., Generative AI and Firm Productivity: Field Experiments in Online Retail (arXiv, 2025)
- Humlum & Vestergaard, Large Language Models, Small Labor Market Effects (NBER, 2025)
- Bick, Blandin & Deming, The Rapid Adoption of Generative AI (Management Science / NBER, 2026)
- Yu et al., Adoption of Generative AI in the Workplace; AI Adoption in S&P 500 Firms (arXiv, 2026)
- McKinsey, The State of AI in 2026
- Microsoft, 2026 Work Trend Index
- PwC, 29th Global CEO Survey (2026)
- OpenAI, Klarna, Morgan Stanley, and Moderna customer cases
- Intercom, How RB2B Created a Lean, Scalable Support System (2025)
- Teamulate, AI Productivity and Business Value: 20-source coding and measurement model (September 2026)
Full report
Download the research
Teamulate AI Productivity and Business Value Report
The full 20-source coding, conversion chain, evidence matrices, missing-measurement map, and B2B measurement model, published as Teamulate research.