REALISTIC VALUE
What ROI can a business AI agent realistically deliver?
There is no defensible universal low and high return for a business AI agent. The strongest direct field experiment found 16.8% faster eligible chats, but only 5.8% of chats were eligible, so the effect across all chats was 3.2% and customer ratings fell on eligible chats. Enter a low and high hypothesis for your workflow, multiply by observed eligibility, then deduct supervision, exceptions, incidents, maintenance, and model costs.
Key takeaways
What ROI can a business AI agent realistically deliver?
- 01
Apply the gain only to eligible work, never to the whole workload by default.
- 02
Count corrections, approvals, exceptions, and maintenance as real labor.
- 03
Separate released capacity from cash savings and new revenue.
Three different results, not one universal range
| Evidence | Measured setting | Observed result | Correct interpretation |
|---|---|---|---|
| Small-business RCT | Open-ended business advice | 0% average; about −8% to +15% by baseline skill | Judgment and implementation determine the sign |
| Business-agent RCT | Standardized customer-service chats | −16.8% eligible duration; −3.2% across all chats | Eligibility and quality limit the headline gain |
| Agency benchmark | 46 concurrent simulated corporate tasks | 15.2% completed; 3.5x relative to 4.3% | Capability signal, not a production ROI |
Use the full denominator
If 70% of requests are eligible and the agent reduces human time by 60% on those requests, the gross reduction across all requests is 42% before operating costs. Excluded, failed, and escalated requests must remain visible.
This prevents a common reporting error: publishing a strong rate on accepted cases while hiding the cases that never entered the system.
Measure an outcome that the organization values
Time saved is useful only when it changes capacity, cost, service, quality, or revenue. Record accepted cases per owner-hour, major corrections, critical errors, cost per accepted result, and the downstream result. Keep each measure separate.
WORKED EXAMPLE
Example: 40 monthly cases
At 60 manual minutes per case and 70% assumed eligibility, editable challenge hypotheses of 20% and 50% produce 5.6 to 14 gross hours per month. A 40-hour setup would take about 2.9 to 7.1 months to absorb before recurring costs. These are scenario inputs, not an evidence range; the pilot must replace them with observations.
- 28 assumed eligible cases
- 5.6 to 14 gross hours
- 2.9 to 7.1 months before recurring costs
Sources and limits
Sources and limits
These sources bound the answer. They do not turn one published case into a promise for your organization.
- 01Agentic AI in customer service ↗
Direct randomized field evidence for a bounded business agent.
- 02The Uneven Impact of Generative AI ↗
Randomized small-business evidence with an average null and heterogeneous effects.
- 03Writing Code vs. Shipping Code ↗
Activity gains attenuate at projects, releases, and downstream usage.