TL;DR. The best controlled evidence on generative AI at work shows real but modest gains: customer-support agents resolved 15% more issues per hour, developers in three company field experiments completed 26.08% more tasks, and BCG consultants finished 12.2% more tasks on work inside the AI “frontier”. On one task outside that frontier, consultants using AI gave correct answers 60% and 70.6% of the time against 84.5% without AI, and experienced open-source developers took 19% longer with AI tools. As output multipliers, the measured effects run from 0.84x to 2.26x on the task studied, nowhere near 10x. The CEO move: augment the delivery stages where output is cheap to check, put a named human gate in front of every stage where errors are expensive, and move pricing away from hours before the hours shrink. The student move: build the evaluation skill, because the gains are largest for less experienced people, the ones least equipped to spot a confident error.
This guide sits next to three CEOtudent pieces: the economics of selling AI automations as a one-person agency, the productized service pricing framework for fixed-price offers, and the evaluation skill for judging AI output. Adoption data sits in the first.
Why is “10x output” the wrong planning number?
The promise that AI lets one person deliver what used to take ten circulates widely in tool marketing. It tempts a solo operator because it suggests the hiring decision has gone away. No controlled study opened for this article measured anything close to it, and the studies that measured output found three patterns that matter more:
- Gains are real but measured in tens of percent, not multiples, once the unit is completed work rather than one sprint on one task.
- Gains are uneven. They are largest for less experienced and lower-skilled workers and smallest, sometimes slightly negative on quality, for the most experienced.
- Gains can turn negative on tasks outside what the model does well, and people are poor at telling which side of that line they are on.
Planning for 10x leads to underpricing, overbooking and under-reviewing. Planning for the measured range still grows capacity without hiring, if AI goes to the right stages and pricing follows.
What do controlled studies of generative AI at work actually measure?
The table lists the strongest-design studies that could be opened in full or as published abstracts. Figures are as printed in the version named.
| Study (version opened) | Setting and sample | Task | Measured effect, as published | Who gained most |
|---|---|---|---|---|
| Brynjolfsson, Li and Raymond, QJE 2025 (arXiv v2, November 2024) | One customer-support firm, 5,172 agents, staggered rollout | Chat-based customer support | Issues resolved per hour up 15% on average | Less experienced, lower-skilled agents (about 30%); the most experienced saw small quality declines |
| Noy and Zhang, Science 2023 | Online experiment, 453 college-educated professionals | Occupation-specific writing tasks | Average time taken down 40%; output quality up 18% | Low-ability workers benefited more (working paper) |
| Peng et al., 2023 (arXiv) | 95 professional programmers recruited through Upwork | Implement an HTTP server in JavaScript | Task completed 55.8% faster (95% confidence interval 21-89%) | Less experienced and older programmers |
| Cui, Demirer et al., Management Science 2026 | Field experiments at Microsoft, Accenture and a Fortune 100 company; 4,867 developers | Ordinary software work with a code-completion assistant | Completed tasks up 26.08% (standard error 10.3%) | Less experienced developers; recent hires and more junior positions |
| Dell’Acqua et al., Organization Science 2026 | 758 BCG consultants | 18 realistic consulting tasks inside the frontier | 12.2% more tasks, completed 25.1% more quickly, with significantly higher quality | Bottom-half-skill subjects gained most; the top half also gained |
| Same study | Same | One complex task selected to be outside the frontier | Correct answers 84.5% without AI against 60% and 70.6% in the two AI groups | No group: AI users did worse |
| Dell’Acqua et al., “The Cybernetic Teammate”, NBER WP 33641 (2025) | 776 Procter and Gamble professionals (791 in the published version) | Real product-innovation challenges, alone or in pairs | Individuals with AI matched the performance of teams without AI; 16.4% less time; quality up 0.37 standard deviations | Individuals working alone, who reached team-level quality |
| Becker et al. (METR), 2025 | 16 experienced open-source developers, 246 tasks in mature repositories | Real issues in projects they already maintain | Tasks took 19% longer with AI allowed (confidence interval +2% to +39%) | No group on average; developers had forecast a 24% time reduction |
Sources: items 1 and 3-9 in the Sources list, in the versions named there.
Two cautions. First, headline figures move between versions. The 2023 NBER working paper of the support study reported 14% on average and 34% for novice and low-skilled workers; the version matching the published article reports 15% and about 30%, which the table uses. The P&G study grew from 776 to 791 participants between versions; its time and quality figures come from the working paper, because the published full text was not open.
Second, the units differ. A 55.8% time reduction on one standardized coding task and a 26.08% increase in weekly completed tasks across thousands of developers are different kinds of evidence, and the second is closer to what a service business sells.
What do those effects look like as output multipliers?
To compare the studies with the 10x claim, each effect converts into an output multiplier for the task studied: a 15% gain becomes 1.15x, and a time reduction of r becomes 1 divided by (1 minus r).
| Study | Measured effect | Output multiplier on that task | 10x is this many times larger |
|---|---|---|---|
| Brynjolfsson et al., all agents | +15% resolutions per hour | 1.15x | 8.7 |
| Brynjolfsson et al., less-skilled agents | about +30% | 1.30x | 7.7 |
| Cui et al. | +26.08% completed tasks | 1.26x | 7.9 |
| Dell’Acqua et al., inside the frontier | +12.2% tasks completed | 1.12x | 8.9 |
| Dell’Acqua et al., P&G working paper | 16.4% less time | 1.20x | 8.4 |
| Noy and Zhang | 40% less time | 1.67x | 6.0 |
| Peng et al. | 160.89 vs 71.17 minutes | 2.26x | 4.4 |
| Becker et al. (METR) | 19% more time | 0.84x | 11.9 |
CEOtudent analysis of the previous table. Multipliers describe the task measured, are not additive and do not describe a whole job.
The highest multiplier, 2.26x, comes from one well-specified programming task done as fast as possible. The two field studies that count real work over months, in customer support and software, sit between 1.15x and 1.30x.
Why does a faster task not make a 10x business?
A large speedup on one stage has a ceiling, because the rest of the project does not speed up. If a share s of project hours runs k times faster, the whole project runs 1 divided by ((1 minus s) plus s divided by k) times faster.
| Share of project hours augmented | Overall multiplier if that share runs 2.26x faster | Overall multiplier if that share took no time at all |
|---|---|---|
| 25% | 1.16x | 1.33x |
| 40% | 1.29x | 1.67x |
| 50% | 1.39x | 2.0x |
| 75% | 1.72x | 4.0x |
CEOtudent analysis; 2.26x is the highest multiplier in the previous table.
For a whole service to run 10x faster, at least 90% of its hours would need to disappear. At a 20x speedup on the augmented share, the requirement is 94.7%; at 2.26x, 10x is arithmetically impossible. Delivery always keeps hours that barely compress: scoping, client decisions, review, revisions and relationship work.
Population-level evidence agrees. Nationally representative US surveys by Bick, Blandin and Deming found that between 1 and 5 percent of all work hours are assisted by generative AI, with reported time savings equivalent to 1.4 percent of total work hours. In Denmark, Humlum and Vestergaard linked adoption surveys to administrative records and estimated precise null effects on earnings and recorded hours, ruling out effects larger than 2% two years after ChatGPT’s launch; 85% of chatbot users report reallocating time savings to other tasks. Time saved is not automatically output sold.
Self-assessment does not replace measurement. In the METR trial, developers forecast that AI would cut completion time by 24%, estimated afterwards that it had cut time by 20%, and were in fact slowed down by 19%. METR’s follow-up experiment, started in August 2025, gives an unreliable signal because developers increasingly declined to work without AI; METR believes developers are likely more sped up in early 2026, but calls its data “only very weak evidence” for the size of the change. The slowdown result is dated; the speedup since then is not yet measured well.
What is happening to demand for freelance services?
Productivity is half the picture; the other half is what clients buy once they have the same tools. Two studies of large freelancing platforms looked at that.
- Hui, Reshef and Zhou found that after ChatGPT’s release, freelancers in more affected occupations saw a 2% decrease in monthly jobs and a 5.2% decrease in monthly earnings, relative to less affected occupations. High-quality service, measured by past performance, did not protect them, and top freelancers were, suggestively, disproportionately affected.
- Demirci, Hannane and Zhu found a 21% decrease in job posts for automation-prone writing and coding jobs, compared with manual-intensive jobs, within eight months of ChatGPT’s introduction, and a 17% decrease in image-creation posts after image generators arrived. The remaining jobs were more complex and paid more, while competition among freelancers increased.
The routine first-draft layer of many services is the part clients can now do themselves, so it is being priced down, and remaining demand concentrates in complexity, judgment and accountability. Augmenting delivery is not optional, but selling the time AI saves at the old hourly rate is not a strategy. The Leverage Ladder describes the longer move from selling time to selling outcomes; this guide covers the delivery side of that move.
Which delivery stages should a service business augment, and where does the human gate sit?
The map applies one rule from the evidence: augment where output is cheap to check, and keep a human decision wherever an error is costly and hard to see. The general stakes-and-reversibility test is in Augment, Don’t Automate; this table applies it to client delivery.
| Delivery stage | Default AI role | Keep human | Quality-control gate before the next stage | Evidence that shapes the call |
|---|---|---|---|---|
| 1. Intake and scoping | Summarize the brief, list open questions, draft a scope outline | Decide scope, exclusions and price | Client confirms a written scope; exclusions are named | The task where AI users did worse was a complex managerial judgment |
| 2. Research and discovery | Collect, summarize and compare material | Choose sources and judge relevance | Every fact used traces to a source a person opened | Inside-frontier gains in speed and quality are well documented |
| 3. First draft or build | Generate drafts, code, layouts and variants | Set the structure and the acceptance standard | Draft checked against a written acceptance checklist | Largest measured time savings sit here (writing and coding studies) |
| 4. Analysis and recommendation | Propose options, argue against the draft, test assumptions | Make the recommendation and own it | A person writes the reasoning in their own words; any number gets a second-source check | On the outside-frontier task, correct answers fell from 84.5% to 60% and 70.6% |
| 5. Review and QA | Run checklists, consistency checks and test cases | Accept or reject the deliverable | Line-by-line review of a sample; every error caught goes in a log | The most experienced support agents saw small quality declines with AI |
| 6. Client communication | Draft updates, agendas and meeting notes | Relationship, bad news, negotiation | Nothing reaches the client unread | No study above measured this stage; treat it as human by default |
| 7. Handoff and knowledge capture | Draft documentation and reusable procedures | Decide what becomes a standard | The procedure is tested on the next project | AI assistance facilitated worker learning in the support study |
CEOtudent editorial framework. The evidence column cites the studies in the first table; the stage boundaries and gates are editorial judgment, not research findings.
Three operating rules follow from the map:
- Gates are named, not implied. Each stage needs a person and a pass condition. Briefing the AI per stage is covered in the Manager-of-AI Playbook.
- The draft stage is the biggest lever and the biggest trap. Its time savings are largest, and its output looks finished before it has been checked.
- Review time goes up, not down. A plan that cuts drafting and review time at once is planning to ship unchecked work.
How should you price when the hours shrink?
Every input below is an illustrative assumption chosen to show the mechanics, not a benchmark. Replace each with your own time records.
- Rate: $100 per hour (illustrative assumption).
- A project takes 20 hours: scoping 2, research 4, drafting or build 8, review and revision 4, client communication 2 (illustrative assumption).
- With AI, research takes 30% less time and drafting 40% less, and review gains 1 extra hour of verification (illustrative assumptions).
- AI tools cost $200 per month; the business sells 5 projects per month and has 100 delivery hours available (illustrative assumptions).
A project then falls from 20.0 to 16.6 hours, a saving of 3.4 hours or 17.0%: a capacity multiplier of about 1.2x, room for one more project a month, not ten. Even if drafting, 40% of the original hours, took no time at all, the ceiling would be 1.67x.
| Scenario (all inputs illustrative assumptions) | Hours per project | Price per project | Projects per month | Net monthly revenue after tool cost | Net revenue per delivery hour | Delivery hours left of 100 |
|---|---|---|---|---|---|---|
| A. Hourly billing, no AI | 20.0 | $2,000 | 5 | $10,000 | $100.00 | 0.0 |
| B. Hourly billing, with AI, same rate | 16.6 | $1,660 | 5 | $8,100 | $97.59 | 17.0 |
| C. Fixed price kept at the old price | 16.6 | $2,000 | 5 | $9,800 | $118.07 | 17.0 |
| D. Fixed price cut 10% to share the gain | 16.6 | $1,800 | 5 | $8,800 | $106.02 | 17.0 |
| E. Fixed old price, freed hours sold as a sixth project | 16.6 | $2,000 | 6 | $11,800 | $118.47 | 0.4 |
CEOtudent analysis; arithmetic in calc.py.
What the table shows:
- Hourly billing hands the gain to the client and the tool cost to you. Scenario B earns $1,900 less per month than A for the same five projects. That is the reason to move to a fixed price before augmenting; the productized pricing framework above and the worked value-based price formula cover how.
- A fixed price keeps the gain only if scope holds. Scenario C raises net revenue per delivery hour to $118.07; unbilled revision rounds eat that first, as scope creep economics shows.
- Selling the freed hours needs demand. Scenario E adds $1,800 a month, 18.0% more than A, only if a sixth client exists. Given the platform evidence, that project is likelier to be complex work than routine drafting.
- Sharing some of the gain can be deliberate. Scenario D still beats A per hour, and a modest cut can win the sixth project. Record the tool cost and effective rate in the one-person business P&L template.
The augmentation readiness scorecard
Use this before adding AI to any delivery stage. Score each question 0 (no), 1 (partly) or 2 (yes).
| # | Question | Why it matters |
|---|---|---|
| 1 | Can a wrong output be detected in minutes against a written checklist? | Cheap checking is what makes augmentation pay |
| 2 | Is a missed error at this stage cheap and reversible for the client? | Expensive, hidden errors need a human decision |
| 3 | Has the tool been tested on several past examples of this task with known correct answers? | The frontier is jagged; only testing shows where it runs |
| 4 | Could you do this stage well without AI? | Evaluating output requires the skill the output replaces |
| 5 | Does the stage take a meaningful share of project hours? | Small stages cannot move total capacity much |
| 6 | Is the work priced per deliverable rather than per hour? | Otherwise the time saved is revenue lost |
| 7 | Does the client contract allow AI tools on client material? | Confidentiality terms come before efficiency |
| 8 | Will every error caught be logged and reviewed monthly? | The log turns review into a better process |
How to read the total (CEOtudent editorial framework; the bands are starting points, not research thresholds):
- 13-16: augment now, with the gate from the stage map in place.
- 8-12: pilot first on internal or low-stakes work, and fix the lowest-scoring questions.
- 0-7: keep the stage human for now, and rescore in a quarter.
A 0 on question 4 or 7 overrides the total: without the skill to judge the output, or permission to use the tool, the stage stays human.
What is the student skill that makes augmentation safe?
The pattern is consistent: the less experienced gain most, and people who rely on their own sense of how it went misjudge AI most. The METR developers believed they had been sped up when they had been slowed down. The BCG consultants on the outside-frontier task produced worse answers with AI than without it. The published P&G study concludes that AI mainly improves the quality of generated ideas, while human judgment retains value in evaluative selection.
That makes evaluation the skill that protects the business: knowing what a correct answer looks like before reading the AI’s, checking numbers against primary sources, and noticing when a task has left the frontier. The evaluation guide linked above sets out how to build it. Three habits keep it in practice:
- Keep an error log by stage: what the AI got wrong, how it was caught, how long the check took. After a month it shows which stages are inside the frontier for your work.
- Time a sample of tasks with and without AI for a few weeks. In the METR trial, the felt speedup and the measured one pointed in opposite directions.
- Work the hardest judgment call of each month without AI first, then compare. This keeps the skill the review gate depends on.
What this does not mean
- It does not mean the gains are trivial. A 26.08% increase in completed tasks, sustained for a year, is large for a one-person business; it is a percentage, not a multiple.
- It does not mean the 2025 slowdown still holds. METR believes developers are likely faster in early 2026; a reliable measurement is missing.
- It does not mean hiring is never the answer. The P&G study found AI can stand in for some benefits of a teammate, but it measured a one-day virtual product development workshop, not client accountability over months.
- It does not mean every saving goes to the client. Pricing is a decision; scenario D is one option.
- It does not mean these studies describe your service. Each covers one task, tool generation and population; your own timed sample and error log count most.
Frequently asked questions
Can AI really let one person deliver 10x more client work?
No study opened for this article measured that. Measured effects convert to 0.84x-2.26x on the tasks studied, and the two months-long field studies sit at 1.15x-1.30x.
Which part of a service project gains most from AI?
First drafts and well-specified build tasks: a 40% time reduction in professional writing tasks and 55.8% faster completion of a standardized coding task. They also need the strictest review gate.
Why do less experienced people gain more?
In the support, writing, consulting and developer studies, less experienced workers gained more; the support study offers suggestive evidence that the tool spreads the practices of more able workers. That is why novices need the evaluation skill most.
Should a freelancer lower prices because AI saves time?
Not automatically. Under hourly billing the saving goes to the client; under a fixed price it stays with the business, as the worked example shows.
Is demand for freelance work falling because of AI?
Two platform studies found declines in affected categories: 2% fewer monthly jobs and 5.2% lower monthly earnings in one, and 21% fewer job posts for writing and coding work in the other. The remaining jobs were more complex and paid more.
How can a task be checked for fit with the “jagged frontier”?
Test it. Run the tool on several past tasks where the correct answer is known, log every error, and score the stage with the readiness scorecard before using AI on client work.
Sources
- Brynjolfsson, E., Li, D. and Raymond, L. (2025). Generative AI at Work. The Quarterly Journal of Economics 140(2), 889-942. Version opened: arXiv 2304.11771v2 (November 2024) and the published abstract.
- Brynjolfsson, E., Li, D. and Raymond, L. (2023). Generative AI at Work. NBER Working Paper 31161. Earlier version, cited only for the revised figures.
- Noy, S. and Zhang, W. (2023). Experimental evidence on the productivity effects of generative artificial intelligence. Science 381(6654), 187-192 (abstract only, via PubMed); March 2023 working paper version opened in full.
- Peng, S., Kalliamvakou, E., Cihon, P. and Demirer, M. (2023). The Impact of AI on Developer Productivity: Evidence from GitHub Copilot. arXiv 2302.06590. Three of four authors are from Microsoft Research and GitHub, the tool’s maker.
- Cui, K. Z., Demirer, M. et al. (2026). The Effects of Generative AI on High-Skilled Work: Evidence from Three Field Experiments with Software Developers. Management Science 72 (abstract via Crossref); February 2025 working paper version opened in full.
- Dell’Acqua, F., McFowland III, E., Mollick, E. et al. (2026). Navigating the Jagged Technological Frontier: Field Experimental Evidence of the Effects of Artificial Intelligence on Knowledge Worker Productivity and Quality. Organization Science 37(2), 403-423. Open access; originally HBS Working Paper 24-013 (2023).
- Dell’Acqua, F., Ayoubi, C., Lifshitz, H. et al. (2025). The Cybernetic Teammate: A Field Experiment on Generative AI Reshaping Teamwork and Expertise. NBER Working Paper 33641.
- Dell’Acqua, F. et al. (2026). The Cybernetic Teammate: A Field Experiment on Generative AI and Teamwork. Organization Science (abstract only, via Crossref).
- Becker, J., Rush, N., Barnes, B. and Rein, D. (2025). Measuring the Impact of Early-2025 AI on Experienced Open-Source Developer Productivity. Model Evaluation and Threat Research (METR), arXiv 2507.09089v2.
- Becker, J., Rush, N. et al. (2026). We are Changing our Developer Productivity Experiment Design. METR, 24 February 2026.
- Hui, X., Reshef, O. and Zhou, L. (2024). The Short-Term Effects of Generative Artificial Intelligence on Employment: Evidence from an Online Labor Market. Organization Science 35(6), 1977-1989 (abstract via Crossref); CESifo Working Paper 10601 (August 2023) opened in full.
- Demirci, O., Hannane, J. and Zhu, X. (2025). Who Is AI Replacing? The Impact of Generative AI on Online Freelancing Platforms. Management Science 71(10), 8097-8108 (abstract only, via Crossref).
- Bick, A., Blandin, A. and Deming, D. J. (2025). The Rapid Adoption of Generative AI. NBER Working Paper 32966, revised February 2025; published in Management Science 72(10), 2026 (abstract only, NBER page).
- Humlum, A. and Vestergaard, E. (2026). Still Waters, Rapid Currents: Early Labor Market Transformation under Generative AI. Working paper, 13 March 2026; previously circulated as Large Language Models, Small Labor Market Effects.
Note on methods: the output-multiplier table, the capacity-ceiling table and the pricing scenarios are CEOtudent analyses of the figures in the verified-data table, recomputed in a script; the delivery-stage map and the readiness scorecard are CEOtudent editorial frameworks. Every input in the pricing example is an illustrative assumption. The 2023 working-paper figures for the customer-support study (14% and 34%) were replaced with the later published-version figures (15% and about 30%). Widely repeated percentage gains for below- and above-average BCG consultants were not used, because they do not appear in the published version opened. No study opened reported a “10x” effect.
This content was compiled with the support of AI following in-depth research, then written and prepared for publication by the CEOtudent editorial team.
This post is also available in:
















