Capacity is not cash: how to read a cost-of-inefficiency estimate

Our cost-of-inefficiency calculator turns a few inputs into a large number. Twelve hours a week of repetitive work at $45 an hour comes to $27,000 a year. That figure is useful, but it needs to be read carefully, because it is easy to misuse.

Five numbers that are often treated as one

Employee capacity. Hours your team spends on a task. Twelve hours a week across a year is about fifteen full workweeks. This is the most reliable figure because it describes time, not money.

Labor-time value. Those hours multiplied by what an hour of employee time costs. It tells you what the work is worth at today's cost, not what you would save by changing it.

Payroll savings. Actual reductions in wages paid. These happen only if hours are genuinely removed from payroll, which is rare and often not the goal. Most organizations redirect freed time rather than cut it.

Opportunity cost. What your people could have done with that time instead: serving more customers, following up on leads, improving quality. Often this is where the real value is, but it's the hardest to measure.

Software cost. Money you are already spending on tools, some of which may be underused or redundant. This is real cash, but it isn't automatically recoverable — the software may still be needed even after the process improves.

Why the distinction matters

If a business case presents labor-time value as "savings", leaders will reasonably expect to see that money on the bank statement. When it doesn't appear — because the freed hours went into other work — the project looks like it failed, even if it made the team substantially more productive.

A credible business case says which kind of value it expects:

• "This frees roughly 300 hours a year, which we plan to redirect to client follow-up." (capacity, with a stated use)
• "This lets us retire one subscription costing $4,200 a year." (cash, specific and verifiable)
• "This avoids hiring an additional coordinator as volume grows." (cost avoidance, with a stated condition)

How to use the calculator

Use it to size the problem, not to promise a return. If a process ties up the equivalent of several workweeks a year, it is probably worth understanding properly. Whether it should be simplified, redesigned, automated, integrated or eliminated is a separate question, and the answer determines what value is actually realistic.

That's also why the reduction scenario in the calculator is labelled as illustrative. Some processes can be cut by 75%; others by 10%; some shouldn't be changed at all. Knowing which takes a closer look at the work itself.