Skip to content

Automation

Automation savings calculator

Estimate the time and money a repetitive task costs each year, what automating it could save, and how long a build would take to pay back.

  • Free
  • No signup
  • Nothing stored

Total across everyone who does it.

Loaded cost of the person’s time.

How much of the work automation removes. 50–80% is common.

Errors, build and running costs

Hosting, subscriptions, API usage.

Estimate

Enter how often the task happens and how long it takes to see the estimate. Or load the example.

Why use it

Before automating a process, it helps to know what it costs today. Small tasks add up: ten minutes, twenty times a day, across a working year is a lot of hours.

This calculator shows every formula and lets you change every assumption, so the result is yours to defend, not a sales number.

How to use it

  1. Describe the task and how often it happens (per day, week or month, across everyone who does it).
  2. Enter how long one run takes and what an hour of that person’s time costs, including overheads if you know them.
  3. Set how much of the work automation would realistically remove. Few processes reach 100%.
  4. Optionally add errors avoided, a one-off build cost and a monthly running cost to see the payback period.

How it works and its limits

  • Runs per year: per day × working days per week × working weeks; per week × working weeks; per month × 12.
  • Hours saved: runs per year × minutes ÷ 60 × share automated.
  • Errors avoided: errors per month × 12 × cost per error × share automated.
  • Net per year: value of hours saved + errors avoided − monthly running cost × 12.
  • Payback: build cost ÷ (net per year ÷ 12).
  • Time saved only becomes money if it is used for other work. This is an estimate, not a quote or a guarantee. Nothing you enter is stored.

Questions

What hourly cost should I use?

Use the loaded cost of the people doing the task: salary plus employer costs, divided by working hours. If you are unsure, start with the default and try a higher and a lower value.

Why not assume 100% automation?

Most processes keep some human steps: exceptions, approvals or checks. A realistic share gives a result you can rely on. 50–80% is common for well-defined tasks.

Does this include the cost of building the automation?

Only if you enter it. Add a one-off build cost and any monthly running costs (hosting, subscriptions, API usage) to see the payback period.

More tools