Hours released and money saved are different claims, and presenting one as the other is the fastest way to lose a finance stakeholder. Here is how to calculate both, and how to say which one you have.
An automation business case usually contains a large number and a small amount of arithmetic connecting it to reality.
The arithmetic is normally right. Volume times handling time times an hourly rate produces a figure, and the figure is genuinely the value of the time being released. The problem is the word used next.
Two different claims
Released hours are hours the team no longer spends on a task. That is measurable, and if you took a baseline you can prove it.
A cash saving is a cost line that goes down. That requires something else to happen: a role not backfilled, a contract renegotiated, overtime that stops, an outsourced volume reduced.
Both are real. Only the second one shows up in a budget, and finance stakeholders can tell the difference immediately. Presenting released hours as a saving is how a credible case loses its audience in the first five minutes.
What released capacity is actually worth
Quite a lot, if you are honest about it.
If the team is behind, released capacity clears a backlog. If volume is growing, it absorbs growth without hiring — which is a cost avoided, and worth stating as such. If the work released was the part everyone dreads, it may show up in retention.
What it is not worth is nothing, and the answer to “we cannot claim it as cash” is not to inflate it into cash. It is to say what it is.
A worked example
A team of six spends about 40 percent of its time on manual data entry between two systems. That is roughly 2.4 full-time equivalents of effort.
An automation removes 70 percent of it, releasing about 1.7 FTE of capacity. At a loaded cost of £45,000 that is about £76,500 of time.
Three honest ways to present that, depending on what is actually going to happen:
- If two roles are genuinely not being backfilled, it is a cash saving of roughly that amount, arriving when those roles leave.
- If headcount stays flat and volume is growing 20 percent a year, it is cost avoidance: the team absorbs the next two years of growth without hiring.
- If headcount stays flat and volume is flat, it is capacity released for work currently being deferred. Name that work, or the case is weaker than it looks.
The third is the most common and the least often stated. It is still a good case, provided the deferred work is worth doing.
What to net off
Whatever the claim, subtract the other side of the ledger:
- Build and integration cost
- Licences or compute the workflow consumes
- Exception handling, which does not go to zero and has its own handling time
- Maintenance when the source systems change
An automation with a 15 percent exception rate is not 85 percent free. Exceptions are usually the harder cases, and they often take longer per item than the average did before.
The assumptions to write down
- Handling time, measured over a representative period rather than recalled
- The proportion genuinely automatable, tested rather than estimated
- The loaded hourly or annual cost, agreed with finance
- The exception rate and its handling time
- Whether a cost line is actually changing, and which one
Key takeaways
- Released hours and cash savings are different claims; say which one you have
- Capacity and cost avoidance are legitimate outcomes, worth stating in their own terms
- Net off build, licences, exceptions and maintenance before quoting a figure
- If no cost line changes, the value is capacity — name what it will be used for
- Take the baseline before you build, or none of this is provable
Our automation readiness assessment applies this method to your own numbers and shows every assumption it used. It takes around four minutes and the output is indicative, which is exactly what it says on the results.