Insights · ROI & Productivity
Understanding the ROI of Business Process Automation
Most automation ROI figures in sales material are inflated, usually by the same few mistakes. A careful estimate is less impressive and far more useful. Here is how to build one.
Start with a baseline
Measure what the process costs now: transactions per month, minutes per transaction, who does it and at what loaded cost, plus the cost of errors and rework and any software you would retire. Without a baseline, any claimed saving is a guess.
Hours released are not cash
If automation frees 100 hours a month, that is not automatically 100 hours of salary saved. The hours are real capacity. They become cash only if you act: fewer overtime hours, a hire avoided, a contract not renewed. Otherwise they become spare capacity, which has value but is a different kind. A credible estimate states what share of freed time it assumes turns into cash.
Count the running costs
Automation is not free to operate. Include hosting, support, licences, monitoring and the time someone spends supervising it. For AI agents, add model usage and messaging fees, and the human time spent on escalated or failed requests.
Allow for ramp-up
Benefits do not start on day one. Implementation takes time, and adoption builds gradually as staff and customers change habits. Model a delay before launch and a ramp after it, rather than assuming full benefit immediately.
Do not count revenue as profit, or the same benefit twice
Extra capacity may let you serve more customers. If so, count the contribution margin on the extra volume, not the revenue. And do not count the same hours both as a payroll saving and as capacity used for new work. Faster invoice collection is a one-time cash-flow improvement, not recurring income.
Use scenarios
Show a conservative, an expected and an optimistic case. If the project only pays back in the optimistic case, that is worth knowing before you commit. The spread between scenarios is a measure of how uncertain the benefits really are.
Then measure afterwards
Agree before the project what you will measure, and over what period. A model is a plan; measured results are evidence. Only measured results, approved for sharing, should be called results.
Try it
Our ROI calculators follow these rules: hours and cash are separate, running costs are deducted, ramp-up is modelled and three scenarios are shown. They are models for your own assumptions, not predictions.
Talk to an engineer
If this is relevant to something you are planning, we are happy to talk it through, with no obligation.
Discuss a project