Why so many automation programmes report weak ROI
Most automation business cases stop at "hours saved times fully loaded cost". That number is easy to build and easy to dismiss. Serious programmes measure return across four layers, only one of which is cost.
The four ROI layers
1. Hard cost savings
Direct reductions in run cost: licences retired, vendor spend cut, contractor hours removed, overtime eliminated. Measurable in the ledger within one quarter.
2. Capacity release
Hours returned to employees. Only counts if the recovered capacity is redeployed to specified higher-value work with a named owner. Otherwise it silently reabsorbs into meetings.
3. Quality and risk
Reduction in error rate, rework, compliance findings, and customer complaints. Often the largest financial component and the one that most programmes fail to quantify because the baseline was never captured.
4. Revenue impact
Faster cycle time enabling more deals, higher conversion from better follow-up, improved customer retention from faster resolution. This is where automation stops being a cost play and becomes a growth lever.
The metrics that matter
- Cycle time per transaction before and after.
- Cost per transaction fully loaded.
- Error rate and rework rate tracked continuously.
- First-contact resolution for service workloads.
- Capacity redeployment tracked to a named use case.
- Revenue attribution for customer-facing processes.
- Payback period and NPV using conservative assumptions.
Building the baseline
You cannot claim ROI without a pre-automation baseline. Spend the first two to four weeks of any programme instrumenting the current process: cycle time, error rate, cost per transaction, throughput, customer satisfaction. Publish it. Get finance to sign off. Then measure the same things weekly after go-live.
A worked example
An insurance operations team automated claims first-notice-of-loss triage. The cost saving alone was £480k a year. Once they added capacity redeployment (adjusters moved to complex claims), quality (a 62% drop in mis-routing), and revenue impact (faster resolution improving retention), the defensible ROI over 18 months was 6.4x. The cost saving was 22% of the total.
Common ROI mistakes
- Counting hours saved that were never redeployed.
- Ignoring the run cost of the automation itself (models, hosting, monitoring, governance).
- Skipping the risk-adjusted view: what happens if the automation is wrong.
- Declaring victory before the change has survived a full business cycle.
Combine this with our process optimisation approach and the 90-day framework so measurement is designed in from day one.