To calculate automation return on investment, compare the value of work it can reliably remove with the full cost of building and running it. Include checking, exceptions and support. Then separate capacity value from cash savings: they answer different questions.
A workflow that frees ten hours each week may give your existing team more time for customers. That is valuable, but it does not automatically reduce payroll by ten hours. A credible business case says what will actually happen to the time and money.
Our before you hire workflow review uses this distinction when assessing whether automation could ease pressure on your team.
Measure the current process
Choose a defined task, such as entering enquiries into a CRM. Measure a representative period and include awkward cases. Record the number processed, total handling time, correction time and any missed or delayed work.
Do not start with the employee’s entire salary. Start with the task. If three people each spend 20 minutes a day on it, measure their combined time without counting the same activity twice. Ask the people doing the work to check the baseline before treating it as a fact.
Seasonality matters. A busy week multiplied by 52 can exaggerate the opportunity. Use a working-year assumption that reflects actual task volume, holidays and quieter periods.
Estimate the time that remains
An automated process still needs attention. Someone may check extracted information, approve replies, handle exceptions and resolve failed transfers. Training and monitoring also take time.
Calculate net hours released as current handling time minus the time needed to operate the new process. If the task currently takes 15 hours a week and reviewing the automated output takes five, the potential capacity gain is ten hours, not 15.
Treat an estimate as provisional until a trial demonstrates it. Straightforward examples from a sales demo are not a representative sample of your inbox.
A worked first-year example
These figures are illustrative assumptions, not a Happy Webs quote or a client result. Assume a workflow releases ten net hours per week, after routine checking and exceptions. Value that capacity at £20 per hour across 46 working weeks.
| Item | Calculation | Annual value or cost |
|---|---|---|
| Capacity released | 10 hours × £20 × 46 weeks | £9,200 |
| Initial setup | One-off assumed cost | £3,000 |
| Running costs | £150 × 12 months | £1,800 |
| Total first-year cost | £3,000 + £1,800 | £4,800 |
| Capacity value after costs | £9,200 minus £4,800 | £4,400 |
On those assumptions, capacity-based return is £4,400 ÷ £4,800 × 100, or about 92%. This values released working time. It is not a claim that the bank balance improves by £4,400.
The example assumes the £150 monthly allowance covers all recurring software, usage and support costs, with no additional change fees. Confirm this for a real proposal. If training or implementation also takes internal staff time, value and add it to the first-year cost.
Separate three kinds of benefit
Cash savings mean spending actually stops or falls. Examples could include reduced paid overtime or a subscription you genuinely cancel. Count only the amount removed, and confirm that the business can operate without it.
Capacity value means paid time becomes available for other work. Decide where those hours will go: quicker customer responses, better quality checks or less evening admin. Wages may stay exactly the same.
Additional profit could come from handling more work, but it needs evidence. Do not count the entire value of an extra sale as profit. Allow for delivery costs, and avoid counting both the time value and extra profit from those same hours as independent benefits.
If there is no actual cash saving or measurable extra profit, a cash-based ROI may be negative even when the capacity-based case is attractive. Label the result honestly.
Test a less optimistic version
In the same example, five hours released per week would be worth £4,600 annually. Against £4,800 of first-year costs, that leaves a £200 shortfall on a capacity basis.
That sensitivity is useful. It tells you to validate the hours before committing. Also test higher usage charges, slower adoption and periods when the process needs manual cover. Ask what happens if an integration changes or the supplier stops supporting a feature.
Agree the evidence before you buy
A proposal should name the workflow, data access, approvals, exception owner and success measure. It should distinguish setup from subscriptions and support, explain what changes cost and provide a manual fallback.
Protecting customer information and reviewing consequential actions are part of the operating cost. They should not disappear from the calculation to make the return look stronger. Our AI agents service covers workflows with these boundaries; custom AI software suits cases that need a dedicated application around them.
Choose a candidate from our admin automation checklist, then use the hiring decision guide to assess the remaining staffing need. If you have a recurring task and a rough time estimate, bring it to a workflow review. The first useful result is a business case you can check.
Before adding another admin role, look at the work filling the day. We build AI agents and automations for enquiries, follow-ups, documents and connected systems. Start with one repeated task, measure the time it takes today and keep your team in control of important decisions.
Explore the service
