Free tool

Automation ROI calculator

Enter how many people touch a process, how many hours a week it takes them and what that time costs. You get the annual cost today, a conservative and an expected savings figure, and the payback period on a build. Every assumption is on screen and you can change it.

Salary x 1.3, divided by about 1,900 hours. $90,000 is roughly $62.

Optional. Leave at 0 if you are not sure.

Assumptions, change them

Our engagements run $12K to $100K or more. Use your own quote if you have one.

This process costs you, per year

$69,120

Savings per year, conservative to expected

$24,192 to $34,560

Payback on the build

8.7 months

That is 4 hours a week each of your 3 people stop spending on this.

Based on 48 working weeks a year. Conservative uses 35% automation.

How it works
  1. Enter the number of people involved and the hours each spends on the process per week.
  2. Enter a loaded hourly rate: salary plus benefits and overhead, divided by working hours.
  3. Adjust the automation share and build cost if you have better numbers than our defaults.
  4. Read the annual cost, the savings range and the payback period.

What the calculator leaves out

It does not count errors that reach clients, deals lost to slow turnaround, or the person who quits because their week is all copy and paste. Those costs are real and often bigger than the labour number. They are also hard to estimate honestly, so we leave them for the conversation instead of inflating the result.

When automation is the wrong answer

If the process changes every month, if nobody can describe the rules, or if it takes two hours a week in total, a build will not pay back. Fix the process first, or leave it alone. The readiness checklist helps you tell which case you are in.

Questions

Questions about this tool.

How is the ROI calculated?

Annual cost is people times weekly hours times 48 working weeks times the hourly rate, plus any rework time you enter. Expected savings apply your automation share to that cost. The conservative figure uses a share 15 points lower, never below 30%. Payback is build cost divided by monthly expected savings.

Why does it default to 50% automation and not 80% or 90%?

Most real processes keep a human step: a review, an exception, a judgment call. Calculators that assume 80% or more produce numbers nobody believes a month in. 50% is a defensible starting point. If your process is mostly rules and data entry, move the slider up.

What should I use for the hourly rate?

Use loaded cost, not salary. A rough rule: annual salary times 1.3 for benefits and overhead, divided by about 1,900 working hours. A $90,000 salary works out to roughly $62 an hour.

Where does the $25,000 build cost come from?

Our engagements run $12K to $100K or more, scoped in writing before we start. $25,000 is a typical figure for automating one well-defined process. If you already have a quote, use that.

Is this a number I can take to my CFO?

It is a first pass that tells you whether a process deserves a closer look. A real number needs someone to watch the work and count the exceptions, which is what the first weeks of any engagement are for.

Tell us what's broken.

30 minutes. No deck, no intake form. You describe what's not working; we tell you whether it's ours to fix.