A transparent ROI and payback guide with a free small-business calculator
To calculate automation ROI, first measure the cost of the current workflow, then estimate only the benefits the new workflow can realistically create. Subtract setup, software, support, training and internal change costs. Divide the net benefit by total cost and multiply by 100. Also calculate payback time, test conservative assumptions and keep quality, customer and staff measures beside the financial result.
A percentage on its own can hide a weak business case. The strongest decision shows the baseline, assumptions, cash effects, capacity returned, risks and evidence that will be checked after launch. This guide provides that structure for a UK small business without relying on a supplier's headline benchmark.
The automation ROI formula
Use one stated period for both sides of the calculation. For a first-year ROI, include all benefits and costs expected during the first 12 months. Keep the initial build separate from ongoing software, monitoring and support so the decision maker can also see the recurring position.
- Current annual process cost = cases per month x minutes per case / 60 x loaded hourly cost x 12.
- Net first-year benefit = measured first-year benefits - setup cost - 12 months of running costs.
- First-year ROI = net first-year benefit / total first-year cost x 100.
- Payback months = setup cost / expected monthly benefit after monthly running cost.
Start with a measured baseline
Observe a representative sample of the work before changing it. Record volume, active handling time, waiting time, rework, missed steps, exceptions and the result customers or colleagues receive. Use several normal weeks if demand varies. A remembered estimate from one unusually busy day is not a dependable baseline.
The 2026 HM Treasury Magenta Book explains why comparison data should be planned before an intervention. For a small workflow pilot, that principle can be applied proportionately: agree the measures first, keep the before data and compare like-for-like work after launch.
Separate four kinds of value
| Value type | What it means | How to treat it |
|---|---|---|
| Capacity returned | People spend less time on repeated handling and can apply it elsewhere. | Value at a loaded hourly cost, then reduce by a realistic utilisation factor. Do not call it cash saved. |
| Cash saved | A real outgoing falls, such as outsourced processing, overtime or a duplicate licence. | Count only when the spending is genuinely removed and evidenced. |
| Cost avoided | Growth is handled without adding an expected cost at the same rate. | Document the expected cost, timing and evidence. Keep it distinct from an immediate saving. |
| Revenue or cashflow influenced | Faster response, fewer missed leads or steadier follow-up may improve an outcome. | Use the incremental gross contribution, not total revenue, and apply a cautious attribution rate. |
This distinction matters because productivity and revenue do not move together automatically. In DSIT's 2026 AI Adoption Research, 56% of AI-using businesses self-reported higher employee productivity, while 77% reported no revenue change yet. The research also warns that these impacts are self-reported estimates. For your business case, use your own measured workflow evidence.
Free automation ROI calculator
Change the example assumptions below. The calculator runs in your browser and does not submit the figures. It values realistic capacity returned and any separate annual benefit you can evidence; it does not predict sales or guarantee a return.
Important: capacity value is not the same as cash saved. Confirm where the returned time will be used, test actual adoption and replace every estimate with measured evidence after the pilot.
Include the costs that are easy to miss
| Cost | Examples |
|---|---|
| Discovery and design | Process mapping, requirements, data review, risk decisions and success measures. |
| Build and integration | Configuration, connections, permissions, testing and error handling. |
| Internal time | Owner input, staff workshops, sample review, training and change support. |
| Running cost | Software, usage, hosting, monitoring, support and supplier management. |
| Control and assurance | Human review, quality checks, records, security, data protection and periodic testing. |
| Maintenance and change | Updating rules, approved knowledge, integrations and workflow steps as the business changes. |
| Transition and exit | Parallel running, migration, contingency and a safe manual route if the automation stops. |
The UK Digital and Data Benefits framework was created to help quantify benefits from digital programmes alongside the Green Book. The wider 2026 Green Book recommends comparing options, including costs and risks, correcting for optimism and testing how results change when important assumptions move.
Worked example: a 300-case monthly workflow
The calculator begins with an illustrative service-business workflow. It receives 300 cases each month, currently takes eight active minutes per case and has a loaded hourly cost of £25. The business expects 60% of that handling capacity to be returned after allowing for human review and exceptions.
| Step | Calculation | Illustrative result |
|---|---|---|
| Current process cost | 300 x 8 / 60 x £25 x 12 | £12,000 a year |
| Capacity value | £12,000 x 60% | £7,200 a year |
| Other evidenced benefit | Lower rework or an existing cost that can be supported by records | £1,200 a year |
| First-year cost | £3,600 setup + (£250 x 12) | £6,600 |
| Net first-year benefit | £8,400 benefits - £6,600 costs | £1,800 |
| First-year ROI | £1,800 / £6,600 x 100 | 27.3% |
| Payback | £3,600 / ((£8,400 / 12) - £250) | 8.0 months |
These figures are an example, not an Ostina promise or an industry benchmark. If the team cannot use the returned capacity, if handling falls by less than expected or if support costs rise, the result changes. That is why a scenario range is more honest than one confident percentage.
Run conservative, expected and upside cases
| Scenario | What to change | Decision use |
|---|---|---|
| Conservative | Lower the capacity returned and other benefits; increase build time, support and adoption effort. | Can the project still be acceptable if progress is slower? |
| Expected | Use observed volumes, supplier costs and a cautious benefit supported by the pilot design. | The working budget and measurement plan. |
| Upside | Include improvements that are plausible but not yet proven, clearly labelled. | Shows opportunity without using it to justify the minimum case. |
Ask for the switching point too: how far can volume, benefit or cost move before the return becomes unacceptable? This sensitivity check is often more useful than debating whether an input should be £23 or £25 per hour.
Measure value and control together after launch
Financial return is only credible if the workflow remains useful and safe. Track handling time, completion, overdue work, corrections, exceptions, customer outcomes and staff experience. Keep a named owner and a route to stop, correct or manually complete the work.
The NIST AI Risk Management Framework Core treats measurement and management as ongoing work, including performance benchmarks, uncertainty, human-AI arrangements and monitoring after deployment. The UK government's portfolio of AI assurance techniques similarly frames assurance as measuring, evaluating and communicating whether a system meets relevant criteria.
Frequently asked questions
What is a good ROI for automation?
There is no universal percentage that makes every project good. Compare the return with the business's alternatives, cash position, risk, payback requirement and strategic need. A modest, dependable return on a low-risk workflow may be better than a large forecast built on uncertain revenue assumptions.
How do I calculate the cost of a manual process?
Multiply the number of cases by active minutes per case, divide by 60 and multiply by the loaded hourly cost. Add identifiable rework, external processing and error costs separately. Use observed samples and do not value waiting time as staff cost unless it genuinely consumes working time.
Does time saved count as a cash saving?
Usually not by itself. It is capacity returned. It becomes cash saved only when an outgoing such as overtime, outsourcing or planned recruitment is genuinely reduced. Record how the capacity will be used, such as serving more customers, completing higher-value work or lowering pressure on the team.
Should revenue be included in automation ROI?
Only when there is a defensible link. Use incremental gross contribution rather than total revenue, allow for other causes and use a conservative attribution rate. If the evidence is weak, show revenue as a separate upside scenario instead of making it essential to the core business case.
How soon should we review the business case?
Review during assisted testing, at the end of the pilot and at an agreed interval after launch. Replace assumptions with actual volume, handling, correction, support and outcome data. Continue, change or stop based on that evidence rather than treating approval as permanent.
Sources and further reading
- HM Treasury: The Green Book (2026).
- UK Government Digital Service: Digital and Data Benefits framework.
- HM Treasury: Magenta Book evaluation guidance.
- Department for Science, Innovation and Technology: AI Adoption Research.
- NIST: AI Risk Management Framework Core.
- UK government: Portfolio of AI assurance techniques.
The practical next step
Choose one candidate with our first-process scorecard, measure the baseline and put conservative assumptions into the calculator. Ostina's AI readiness assessment and automation audit turns that evidence into a prioritised opportunity map, our AI automation consultancy develops the business case and roadmap, and our AI automation services support controlled delivery and measurement.
