What is one repetitive task costing your team?

Pick a task your team does over and over. Enter how often it happens, how long it takes and how often it needs fixing. You will see the hours it uses today and how many a system could give back. Every formula is shown.

1 The task
/ week
min
people

If you only know the team total per week, enter that total above and set this to 1.

2 Cost of their time
$/ hr

Salary plus benefits, taxes and overhead, divided by hours worked. Your finance team will have this figure. We leave it blank on purpose.

3 Mistakes and rework
%
min

A typo, a missed field, a wrong total. Count the time to notice it, find it and put it right.

4 What a system could take over

A person still reviews the output and handles the odd cases, so 100% is rarely right. Lower this if the task needs a lot of judgment.

Calendar assumptions
weeks
hrs

Starting points after holidays and leave. Change them to match your calendar.

The starting values are examples. Replace them with your own.

Hours a system could give back each year

0 hours a year

Cost of the time saved
Add your hourly cost
Full-time equivalent
0
Mistakes avoided a year
0
Hours a week today
0
Hours a year today
0

Estimates from your inputs, not a promise. Read what this leaves out below.

How each number is worked out

Plain arithmetic on the numbers you entered. It updates as you type.

  1. Times a week
  2. Hours doing the task each week
  3. Hours fixing mistakes each week
  4. Hours a week today
  5. Hours a year today
  6. Hours saved a year
  7. Cost of the time saved
  8. Mistakes avoided a year
  9. Full-time equivalent

We assume mistakes shrink in step with the work a system takes over, since most of them come from retyping and copying between tools.

Read this before you share it

What this leaves out.

The calculator counts the routine part of the work. Real projects have a few costs it cannot see.

Exceptions

Every task has odd cases: the invoice with no PO, the form filled in by hand. A system flags those for a person instead of guessing. If a lot of your volume is odd cases, the real share a system can take is lower.

Review time

Someone still checks what the system did, at least at first. Checking is faster than doing, but it is not free. Plan for it in the first few months, then trim it as trust builds.

Change takes time

People need to learn the new way, and old habits stick around for a while. Savings usually build over weeks, not on day one. Hours saved also only count if the team uses them for other work.

Building and running it

This page does not include what a system costs to build or keep running. That depends on the task and your tools. A process audit measures the task properly and scopes the work.

FAQ

Questions about the calculator.

Want help with the numbers? Ask us.

What is a loaded hourly cost?

It is what an hour of someone's time really costs you: pay plus benefits, payroll taxes and a share of overhead, divided by the hours they work. It is usually well above their hourly wage. Use a blended figure if several roles do the task.

Why does the share a system takes over start at 70%?

It is a starting point, not a benchmark. Most routine tasks still need a person to review the output and handle the cases that do not fit. Set it to what you think is true for your task. A process audit measures it.

Does saving hours mean cutting jobs?

Not usually. Most teams use the time for work that needs a person: customers, judgment calls and the backlog they never get to. The full-time equivalent number shows the size of the time saved, not a headcount plan.

Do you store what I enter?

No. The math runs in your browser. We record that the calculator was used, with the totals, to see whether it is useful, but not the task name or anything that identifies you. Your numbers only reach us if you choose to send them with an inquiry.