What is the real ROI math of AI for a small business?
Start with an opportunity assumption, apply a realistic captured share, then subtract operating and implementation costs. At the calculator’s defaults for a 25-person professional-services firm, first-year net is −$987: $18,750 of captured value minus $1,737 running costs and an $18,000 build. This is a sensitivity case, not a prediction.
These are the exact numbers behind our ROI calculator, laid out in prose instead of a widget. Read them as what they are: a model — our published planning assumptions, useful for a first read of whether AI is worth investigating at your size, and built to be replaced by your measured numbers the moment you have them. Nothing on this page is a promise, and the last two sections explain why we refuse to make one.
What does the “manual work” line actually measure?
The modeled cost of hours your team spends on repetitive, rule-following work a machine could carry: re-keying data between systems, drafting routine emails and documents, chasing statuses, reconciling records, copying answers from one place to another. We model it at $4,000 per employee per year in professional services, with different rates by industry.
Two things about that number matter more than the number. First, it is an average across your whole headcount, not a claim about any individual — some employees do almost none of this work, and a few do ten times the average; spread over the team, the modeled figure is what survives. Second, it is deliberately unspectacular. At a $50 loaded rate, $4,000 a year is roughly an hour and a half per person per week — the arithmetic of ordinary friction, not a story about robots replacing anyone. The average includes the owner, whose re-keying hour is the most expensive one in the building. If your reaction is “our people lose more than that,” you may be right, and that is exactly what an audit measures rather than assumes.
What does the “lost capacity” line mean?
The revenue the model says you do not pursue because your people are busy with the manual work: proposals that never get written, callbacks that never happen, jobs that never get quoted, follow-ups that die in a full inbox. We model it at $2,000 per employee per year in professional services, again varying by industry.
This is the softer of the two lines, and we treat it that way. Manual work is a cost you are already paying and could in principle time-and-motion study next week. Lost capacity is a counterfactual — an estimate of what freed hours would earn if they were redirected at revenue, which requires that there is revenue to chase and someone who redirects the hours. In some businesses that line is conservative; a retail operation that answers product questions an hour faster genuinely sells more. In others it is generous. When the two lines are added, remember which one stands on observed hours and which one stands on an assumption about what you would do with them.
What are the per-industry rates, exactly?
Five industries, two rates each, exactly as published in the calculator. They differ because the mix of paperwork, margins, and hourly economics differs by industry — a law firm’s hour is not a restaurant’s hour.
| Industry | Manual work / employee / yr | Lost capacity / employee / yr | Combined |
|---|---|---|---|
| Professional services | $4,000 | $2,000 | $6,000 |
| Healthcare | $3,600 | $2,800 | $6,400 |
| Retail | $3,200 | $2,400 | $5,600 |
| Construction | $3,000 | $1,800 | $4,800 |
| Hospitality | $2,400 | $2,200 | $4,600 |
Our published model assumptions — the same rates behind the calculator. Team-wide averages, not per-person promises; an audit replaces them with your measured numbers.
If you want the operational detail behind any row — which workflows drive the number in your world — the industry pages walk through it: professional services is the deepest of the five. Two notes on using the table. If your business straddles categories — a design-build firm that is half construction and half professional services — blend the rows by headcount rather than picking the flattering one. And if any rate strikes you as too high for your operation, cut it in half and rerun the math; a model you have deliberately discounted and that still clears is telling you more than one you swallowed whole.
What do the default costs mean?
The starting investment is min($60,000, max($18,000, $720 × employees)). This is a headcount-based planning proxy within the published Implementation Sprint range, not a quote or a claim that headcount determines project complexity. Replace it with the actual scoped investment.
The default running-cost assumption scales linearly from $50 per month at five employees to $500 at one hundred, then rounds the annual total to the nearest dollar. For 25 employees it is $1,737 per year; for ten it is $884. This relationship is a modeling convenience, not usage research. The calculator lets you edit monthly cost, investment and captured share.
How are annual net, first-year net and payback different?
Annual captured value = modeled opportunity × capture percentage. Annual net = captured value − twelve months of running costs. First-year net = annual net − one-time investment. Simple payback = investment ÷ positive annual net. If annual net is zero or negative, the modeled build does not pay back.
The first year here is twelve months of operation, with the full initial investment subtracted. It excludes the pre-launch period. Audit fees, managed services, hardware not included in your investment, internal review and training time, taxes and financing are excluded unless you enter them in the cost inputs. Use a full cash-flow model for a purchase decision.
How does the math work for a 25-person firm?
The professional-services baseline is 25 × $4,000 of manual-work opportunity plus 25 × $2,000 of capacity opportunity: $150,000 per year. At the default 12.5% capture, modeled value is $18,750. Running costs of $1,737 leave $17,013 annual net. Subtract the $18,000 investment and first-year net is −$987; simple payback is about thirteen operating months.
The 12.5% setting comes from the earlier sensitivity example: halve the opportunity and capture one quarter of that reduced figure. It is an illustrative downside scenario, not a proven minimum. Actual capture can be zero. At 100% capture, first-year net would be $130,263, but recovering every dollar is a theoretical ceiling, not a typical result or a forecast.
A 10-person construction firm starts at $48,000 opportunity. At 12.5% capture it yields $6,000 before costs. Subtract $884 running costs and $18,000 investment: annual net is $5,116, first-year net is −$12,884, and simple payback is about 42 operating months. Changing the inputs can make either example better or worse; a positive answer is not assumed.
When does saved time become financial value?
Recovered hours do not automatically reduce payroll. A cash return needs evidence such as avoided overtime, a deferred hire, lower contractor cost or additional work sold at a measured gross margin. Count additional gross profit, not sales revenue, and do not count the same hour once as saved labor and again as revenue capacity. The baseline is an opportunity estimate until those assumptions are validated.
What breaks the model?
Three things, and at least one of them applies to most businesses. The workflows are not actually repetitive; adoption fails; or the estimate counts work you would never have staffed anyway.
First: the model assumes the manual hours are rule-following hours. If the work that eats your week is judgment dressed in paperwork — pricing oddball jobs, handling exceptions, soothing a particular client — a machine drafts it badly and a person redoes it, and the “saved” hours come back with interest. The Ampersand essay The Currency of the Machine is about exactly this distinction, and it is the first thing an audit checks.
Second: a system nobody uses returns zero, regardless of what the spreadsheet said. Adoption does not fail loudly — the approval seat goes empty for a week, the old habit creeps back because it was faster that day, and by month four the build is a login nobody remembers. The model assumes the hours flow back; adoption is the pipe they flow through, and it is a human pipe.
Third, the subtlest: saved time is not captured value. “Lost capacity” only converts to dollars if someone redirects the freed hours at revenue — and if the manual work was being absorbed into slack you would never have staffed anyway, eliminating it improves morale, not the bank balance. A model that counts those hours as dollars is double-counting, and most vendor ROI slides do. Any pitch that ignores all three of these failure modes is showing you the model’s best day and calling it a forecast.
Why won’t we promise ROI numbers?
Because everything above is our published set of assumptions, not your measured facts, and a promise built on assumptions is fiction with a signature. That is why no page on this site quotes a guaranteed return — this one included.
What we do instead is stage the certainty. The calculator gives you a free first read using the rates in this guide — run your own headcount through it. The same model does heavier work in the build-versus-hire comparison, if your alternative is a full-time hire. And when the first read looks worth testing, an AI Readiness Audit — we call it The Blueprint — $3,500–$8,500, 2–4 weeks, tests the assumptions against your workflows, hours, and rates, and supports a scoped build decision. A fixed quote follows an agreed scope. Sometimes the audit’s answer is that the drag is real but the workflows are not automatable yet, and the recommendation is to wait. If you would rather start smaller than that, the free 30-minute assessment is a conversation about which of your numbers would survive the audit — we reply within 24 hours.
Set up the measurement log before launch to put this guide into practice.