How to calculate business automation ROI

Measure the current process

Count how often the task happens and time a representative sample. Separate active staff time from waiting time. An approval that takes a day to arrive may use only a few minutes of staff effort; reducing delay can matter, but it is not the same as saving a day's wages.

Record error correction separately. Otherwise you may count the same benefit twice when you later add an estimate for fewer mistakes.

Use a transparent calculation

Monthly capacity value = tasks per month × minutes saved per task ÷ 60 × relevant hourly cost. Then subtract the monthly operating cost and the value of new review work not already included in the time saving.

This is a planning estimate, not a guarantee. Staff time released becomes cash savings only if actual costs fall. It may instead create capacity for more work or improve response times.

Worked example: illustrative inputs only

The example releases about 26.7 hours a month, valued at roughly £533 using the assumed hourly cost. After £100 running costs, the estimated monthly net capacity value is £433. Dividing £3,000 by £433 gives approximately seven months of simple payback. These figures are not client results, pricing or promised savings.

Stress-test the answer

Halve the task volume or the time saving and calculate again. Include a slower adoption period and allow for exceptions that still require staff attention. If the case only works under perfect conditions, reduce the scope or investigate a cheaper option.

Do not assign a monetary value to improved satisfaction unless you have a defensible method. It is acceptable to track that benefit separately.

Validate with a pilot

Measure the same tasks before and after. Ask whether the work disappeared or moved to another person. Check correction rates, missed tasks and the quality of the output alongside speed.

Decide on evidence

Proceed when the conservative case is worthwhile and the workflow is safe to operate. Rework the idea when it creates more review than it removes. The goal is a better process, not automation for its own sake.