Return on automation: how to estimate it honestly
Most automation cases count hours saved and stop. The honest version counts what the hours were worth, what the system costs, and when it pays.
The short answer
Most automation business cases multiply hours saved by an hourly rate and stop. The honest version asks four more questions. What actually happens to the hours: are they redeployed, removed, or absorbed into a slightly easier day? What does the system cost in full: build, running, monitoring, the people who review exceptions, and the disruption of changing how work is done? What does it break or improve besides time: errors, speed, consistency, customer experience? And when does the saving appear: at launch, or over months as trust and the straight-through lane grow? Answer those against a baseline measured before building, and the return is a number. Skip them, and it is a story.
The honest ledger
| Line | Optimistic version | Honest version |
|---|---|---|
| Hours saved | Estimated hours times rate | Hours actually redeployed or removed, times what that time produces |
| Speed | Not counted | Faster response measured against conversion, cash flow or service levels |
| Errors | Not counted | Rework, refunds, complaints and corrections avoided, measured |
| Build cost | The quote | The quote plus your people’s time on data, labelling and testing |
| Running cost | Model usage | Usage, hosting, monitoring, monthly review, document refresh, retests |
| Review cost | Zero | Hours per month a person spends on exceptions |
| Change cost | Zero | Training, procedure changes, the productivity dip in the first weeks |
| Timing | Saving from launch | Ramp over months as the gate widens |
Estimating it in five steps
- Measure the baseline for two to four weeks: time, volume, errors, response speed, rework.
- Name what the freed time will be used for, specifically, and who decides.
- Estimate the full cost, including the monthly line and your people’s review hours.
- Model the ramp: month one mostly reviewed, month three half straight-through, month six steady state.
- Pick the two or three metrics you will check at three and six months, and put the dates in the calendar.
Where returns usually come from
Response speed on leads and enquiries, which changes conversion. Same-day processing of documents that used to wait for month end. Consistency in tasks that generated corrections and complaints. Capacity to handle growth without hiring for repetitive work. Removal of a bottleneck that held other work back. In most small business automations we have measured, one of these outweighed the hours, and it was measurable from the baseline.
What this means for you
Estimate return the way you would judge it afterwards: against a baseline, with the freed time assigned, the full cost counted, speed and errors valued, and the ramp modelled. Pick the metrics and the review dates before building. The automations that pay back are the ones somebody was going to measure, and everyone knew it from the start.
Frequently asked questions
How do we value an hour saved?
By what happens to it. If the person is redeployed to work that produces revenue or removes a cost, value it at that. If the hour disappears into a slightly less busy day, value it at close to nothing until you can show what was done with it. Honest business cases name what the freed time will be used for and check afterwards.
What returns are usually underestimated?
Speed and consistency. Replying to a lead in five minutes instead of a day changes conversion. Processing an invoice the day it arrives instead of at month end changes cash flow and supplier relationships. Doing a task the same way every time removes rework, refunds and complaints. These are often larger than the hours and easier to measure.
When does the return start?
Later than the plan says. There is a build period, a pilot with a person checking most cases, and a ramp as the straight-through lane widens. Model the saving as growing over months, not switching on at launch, and include the cost of the people's time during the ramp.