A field guide for business owners
The demo is the beginning. The real opportunity is a system your business can depend on.
Explore the reportreport improved
personal productivity
report positive impact
on company earnings
Share of survey respondents. Different questions, not a conversion funnel. Earnings = EBIT.
McKinsey, August 2026. [1]
01 / The execution gap
An employee can finish a task faster while the business still waits on the same approval, missing document, or broken handoff.
That is the central distinction in this report: making an individual task easier and improving an entire business process are different achievements. McKinsey’s latest survey reports personal productivity gains much more often than positive company-level earnings impact. It also finds workflow redesign more common among high performers. These associations do not establish what caused their results. [1]
Recent worker-level research adds another useful caution: AI adoption varies substantially even among people doing similar work. A tool being available is not the same as a team routinely using it. [8]
XT3’s recommendation: start with one recurring business outcome, then follow it from the first input to the last handoff. Choose where AI belongs only after you can see where the work actually gets stuck.
“Which part of the business should work better by next month?”
01Define the outcome.Measure completed work, not generated output.
02Own the whole flow.Include people, permissions, and exceptions.
03Keep improving.Leave someone responsible after launch.
02 / Read the evidence carefully
“Does AI improve productivity?” is too broad to guide a buying decision. Ask whose work, which task, which tools, and what was measured.
Measured in customer support
+15%
A published study of 5,172 support agents found an average productivity improvement with AI assistance. Effects varied across workers; people retained control of customer conversations. [2]
One firm, a specific tool and workflow. This is evidence that assistance can help, not a forecast for your business.
METR’s trial found experienced developers took 19% longer with early-2025 AI tools on tasks in familiar repositories. [3]
Follow-up results suggested faster work, but selection and measurement problems made the size of the effect unreliable. [4]
METR examined self-reported gains while highlighting response bias and the difficulty of translating perceptions into measured value. [5]
These studies use different settings and methods. They are not points on a single productivity trend.
Run a bounded trial on your own recurring work. Compare completion time, corrections, and accepted outcomes against a baseline. Include review time. Keep the version that improves the whole result, even if it uses less AI.
03 / Life after the demo
Bubble’s analysis found far more deployment activity among apps with payment activity than those without it during their first six months. [7]
It is an association, not a recipe. Paying users might encourage improvements; stronger products might attract paying users; other differences may influence both. Deploying more often does not, by itself, prove value.
The useful operating habit: make a small change, check the customer outcome, and decide what to change next. Leave time and ownership for that loop in the original plan.
One square = one deploy. Bubble’s platform data; payment activity does not mean profitability. [7]
DORA’s 2025 research describes AI as amplifying an organization’s existing strengths and weaknesses. For an owner, that makes clear priorities, useful feedback, and dependable delivery part of the investment. [6]
04 / Put the research to work
These are proposed starting points, not measured client results. Choose a recurring problem you can observe, with a useful outcome and a safe fallback.
Start with: a qualified inquiry sitting in an inbox while someone finds the context, assigns an owner, and drafts a reply.
Use the simplest tool. Let ordinary rules handle routing and deadlines. AI may help summarize the inquiry or draft a response from approved information.
Keep the boundary. A person approves prices and commitments. Missing details go to a review queue; duplicate inquiries do not trigger duplicate messages.
Measure the result. Track time to the first useful reply, qualified inquiries handled, and corrections. Do not count automated acknowledgments as meaningful responses.
Start with: a recurring client update assembled by copying numbers between tools.
Use the simplest tool. Calculate totals with ordinary code or spreadsheet formulas. Use AI for a draft explanation only after the numbers reconcile.
Keep the boundary. Mark stale and missing inputs. Preserve source links. Client access must stay limited to the correct client’s information.
Measure the result. Compare preparation time including review, late reports, and corrected figures. Keep a manual version available during the pilot.
Start with: the same internal question repeatedly interrupting a senior employee.
Use the simplest tool. Improve the document or search first. Add an assistant when questions genuinely need synthesis across maintained sources.
Keep the boundary. Apply the reader’s permissions before retrieving content. An unsupported answer should become a question for the owner, not a confident invention.
Measure the result. Review correctness, successful self-service, and interruptions avoided. Give outdated guidance an owner and a review date.
Buy when an existing product covers the important job and its limits are acceptable.
Connect when the tools work but information gets lost between them.
Build when a distinctive workflow justifies ongoing ownership, testing, and maintenance.
XT3 judgment: compare candidates by observed friction, expected benefit, reversibility, and total effort. Validate the strongest candidate first. No universal “80/20” split or fixed savings rate is assumed.
The economics of useful work
A faster draft can still mean an expensive process if someone has to inspect, repair, and re-enter every result.
Agree on what “better” means before the pilot starts. Include review and exception handling in the comparison. Count cash savings only when spending actually falls; reclaimed capacity is valuable, but it is a different benefit.
A decision framework, not a financial forecast. Use your actual costs and measured pilot results; avoid counting the same benefit twice.
05 / Before the business depends on it
Use this as a conversation with the person building your system. Check an item when you can point to evidence.
A working checklist, not a certification. Checkmarks are temporary and are not saved or submitted.
A practical first month · suggested sequence
Week 1Observe the work. Set a baseline and choose one outcome.
Week 2Build or configure the smallest usable flow. Test awkward cases.
Week 3Run a limited pilot with a person reviewing consequential actions.
Week 4Compare results. Expand, revise, or stop. Name the ongoing owner.
Planning guidance, not a delivery promise. Access, integrations, data quality, and risk may require a longer schedule.
The XT3 point of view
You run the business. I handle the technology. Bring the workflow that keeps getting stuck; I’ll help you question the solution, choose a useful first step, and work out what it takes to own it properly.
Ian Dikhtiar · Hands-on fractional CTO · XT3
06 / Sources & methodology
This report synthesizes public research available on September 8, 2026. It is written for owners considering business software and automation. XT3 did not run a new survey, audit these datasets, or measure client outcomes for this report.
Survey findings, field research, and vendor observations answer different questions. They are not pooled into a single success rate. All chart values come from the named sources; the workflows, checklist, and operating sequence are XT3 recommendations. None predicts the reader’s return.
Bubble’s report informed the editorial format. Its data remains attributed to Bubble. McKinsey’s findings describe a global company sample; the support-agent study is one organization; METR’s experiments concern particular developers and tools. Findings may not transfer to a smaller business or newer system.
McKinsey · August 25, 2026
Global, self-reported survey: 1,719 respondents in 97 nations, fielded May 4–June 8, 2026. GDP-weighted; 36% work at companies above $1B revenue. These are not representative small-business benchmarks.
Erik Brynjolfsson, Danielle Li & Lindsey R. Raymond · The Quarterly Journal of Economics · May 2025 · 140(2), 889–942
Published study of a staggered rollout to 5,172 customer-support agents at one firm. Uses the published 15% result, rather than the earlier working paper’s 14%. Historical technology and a specific work setting.
Joel Becker, Nate Rush, Beth Barnes & David Rein · METR · July 10, 2025
Randomized trial: 16 experienced developers, 246 tasks in familiar repositories, February–June 2025 tools. The result is bounded to that setting and period.
Joel Becker and colleagues · METR · February 24, 2026
Follow-up evidence suggests improvement, but selection effects and time-measurement problems prevent a reliable estimate of the current productivity effect.
METR · May 11, 2026
Self-reported productivity research. Low response rates and potential selection bias limit generalization; perceived gains are not independently measured business returns.
DORA · Google Cloud · 2025
Software-delivery research: AI can amplify the strengths and weaknesses of the surrounding organization. Used for operational context, not as causal proof of a specific intervention.
Bubble · 2026 · data through mid-August
Vendor analysis of 250,000+ live, deployed Bubble apps. Six-month comparisons use matched observation windows. “Monetizing” means running a payment workflow or calling a payment API; it does not establish profit. Observational, platform-specific evidence.
Alexander Bick, Adam Blandin, David J. Deming & Tyler R. Schumacher · NBER · August 2026 · Working Paper 35677
Nationally representative worker survey linking adoption to occupations and tasks. Working paper; adoption measures do not establish productivity or returns.
Notes on this report