Adoption and strategy
How to measure ROI on AI automation, with a worked example
AI ROI is not mysterious. It is hours saved times loaded cost, plus errors removed, plus capacity freed. Here is the framework we use, and a worked example that shows the maths on a real-shaped workflow.
By Seb Lawson · 2 June 2026 · 4 min read
AI ROI is simpler than the market wants you to believe. Three things move the number: hours saved, errors removed, and capacity freed. Put a figure on each, subtract what the system costs to build and run, and you have your answer. If you cannot do that sum for a given workflow, you are not ready to build it yet.
The reason ROI feels slippery is that most firms measure the wrong thing. They count licences and forget loaded cost. They count the demo and forget the run rate. They talk about time saved but never actually time the task before and after. Measure properly and the picture is usually clear within the first month of a workflow going live.
The three levers
Every credible AI business case pulls on at least one of these. The best pull on all three.
- Hours saved. The time a task took by hand, minus the time it takes with the system and its human check, multiplied by the loaded hourly cost of the person doing it. Loaded cost, not salary. Salary plus employer costs, plus overhead, is usually 1.3 to 1.5 times the headline figure.
- Errors removed. The cost of the mistakes the old process made: rework, corrections, an apology to a client, in the worst case a breach to report. Harder to price precisely, but real. Estimate a per-error cost and a rate, and be conservative.
- Capacity freed. The work your team can now take on without hiring, or the growth you can absorb without adding headcount. This is often the largest number and the one firms forget, because it does not show up as a cost line, it shows up as a hire you did not make.
The formula
Annual benefit is hours saved per year times loaded hourly cost, plus errors removed per year times cost per error, plus the value of any capacity freed. Annual cost is the build cost amortised over its useful life, plus the running cost: model usage, tooling, and the maintenance the system needs to stay honest. Net benefit is the first minus the second. Payback is the build cost divided by the monthly net benefit. Keep it that plain.
A worked example
Take a trust and corporate services team drowning in client take-on. Gathering and checking KYC documents for new entities takes an administrator about eight hours per case, and the team onboards roughly ten cases a month. That is 80 hours a month, or 960 hours a year, on one workflow.
Build an assisted pipeline: documents extracted and checked against a checklist automatically, gaps flagged, a first-pass summary drafted, and a human reviewing and signing off every case. In our experience this kind of workflow takes the eight hours per case down to about three, because the person is now checking and approving rather than gathering and typing. Call it five hours saved per case, fifty hours a month, 600 hours a year.
Now the maths. At a loaded cost of £45 an hour, 600 hours saved is £27,000 a year. The old process missed a required document or logged something wrong on maybe one case in ten, each costing a few hours of rework and the occasional awkward client email; call that conservatively £4,000 a year avoided. And the freed capacity lets the team take on more onboarding without a new hire, which was the actual bottleneck. Ignore that entirely and you are still at £31,000 a year of hard benefit.
Against that, a build of this shape sits in the region of £40k, plus running costs of a few hundred pounds a month for model usage and tooling. Amortise the build over three years and add the run rate, and net benefit lands comfortably in five figures a year, with payback inside the first eighteen months and often sooner once freed capacity is counted. That is the pattern behind our KYC and client take-on work.
The mistakes that flatter or wreck the number
Two errors show up constantly. The first is counting time saved that nobody actually recovers, because the freed hours just evaporate into slack rather than into more work or fewer hours. If you cannot say where the saved time goes, discount it. The second is forgetting the human check in the cost. Oversight takes time, and a business case that assumes zero review is measuring a system you should not run. Price the checkpoint in. It is cheaper than the alternative.
Measure it after, not just before
A business case is a forecast. The number that matters is the one you confirm a month after go-live, by timing the task again and counting the errors again. Build the measurement in from day one: log every run, every human override, every correction. That same log is your audit trail, which is why we treat measurement and governance as the same job, covered in building an AI audit trail.
If you want it built and proven, we ship the workflow and the measurement together. And if you would rather just talk it through, book a review and we will put a real number on your most painful workflow.