Guide
How to estimate what automating a manual process is worth
A simple, transparent way to put a number on a repetitive task, decide whether automating it pays off, and avoid the most common estimating mistakes.
Automation is easy to justify in general and hard to justify in particular. A clear estimate of one specific process lets you decide whether it is worth automating, and which process to start with.
Start with what it costs today
You need four numbers, and rough ones are fine:
- How often the task happens, across everyone who does it (per day, week or month)
- How long one run takes, including switching between tools
- The hourly cost of the people doing it, including employer costs if you know them
- How much of the work automation would remove. It is rarely all of it.
Multiply them out and you have the yearly time and cost of the task as it runs today.
Be realistic about the share automated
Most processes keep human steps: handling exceptions, approving payments, checking unusual cases. Assuming 100% automation makes every project look like a bargain. A realistic share, often somewhere between half and most of the work for a well-defined task, gives a number you can defend.
Count errors separately
Manual re-typing produces mistakes, and some mistakes are expensive: a wrong invoice, a missed order, an unhappy customer. If you can estimate how often errors happen and what a typical one costs, add it. If you cannot, leave it out rather than guess. The estimate is then conservative.
Include the cost of the automation
An automation has a one-off build cost and usually a running cost: hosting, subscriptions or API usage. The useful question is not "does it save time?" but "how many months until it pays back?":
payback in months = build cost ÷ (net yearly value ÷ 12)
Common mistakes
- Counting time that will not be reused. Saved hours only become money if people spend them on other work.
- Automating an unstable process. If the steps change every month, document and stabilise the process first.
- Ignoring maintenance. Integrations break when the tools on either side change, so budget for upkeep.
Try it with your numbers
The automation savings calculator on this site uses exactly these formulas, shows each assumption, and lets you change all of them. Use it to compare two or three candidate processes before choosing where to start.
- Automation
Try it yourself
Found a process worth automating?
Tell us how it works today. We will suggest what to automate first and what to leave alone.