Owners and finance leaders often ask the same thing: "What is this actually costing us?" It's a fair question. Payroll is usually the biggest line on a small business budget, and time that isn't producing work is part of that cost. The math is simple. The judgment around it is where most people go wrong.
The basic formula
The calculation has four inputs:
- Hourly cost per employee. Annual salary divided by 2,080, the number of hours in a standard full-time year (40 hours times 52 weeks).
- Your productive-hours goal per day. What a realistic, well-run day looks like for the role.
- Actual average productive hours per day. What your team is doing now.
- Number of employees and workdays per month. We use 21.67, which is 260 workdays divided by 12.
Then:
Monthly cost of the gap = (goal hours minus actual hours) × hourly cost × employees × 21.67
Multiply by 12 for an annual figure.
A worked example
This is an illustrative example, not data from a real company. Say you have 20 employees with an average salary of $52,000.
- Hourly cost: $52,000 ÷ 2,080 = $25.00
- Goal: 6.0 productive hours per day
- Actual average: 5.5 productive hours per day
- Gap: 0.5 hours per person per day
Monthly cost: 0.5 × $25.00 × 20 × 21.67 = $5,417.50
Annual cost: $5,417.50 × 12 = $65,010
You can try your own numbers in our cost of lost time calculator. It uses the same formula.
Turning hours into FTE
Dollars are one way to see the gap. Capacity is another, and often more useful for planning. Divide the total daily gap by the goal hours to get untapped capacity in full-time equivalents (FTE).
In the example: 0.5 hours × 20 people = 10 hours per day. Divided by a 6-hour goal, that's about 1.7 FTE. Put another way, the team has roughly the capacity of one and a half to two more people already on payroll, if the gap could be closed.
That framing changes the hiring conversation. Before you add headcount, you can ask whether existing capacity can absorb the work.
The inputs that matter most
Your goal must be realistic
The result depends heavily on the goal. Set it at eight hours and nearly every team will look like it's wasting a fortune. Set it from what your steady performers actually do, as described in our post on what productive time really means. A realistic goal gives you a number you can defend.
Your actual hours must be measured
Guessing at actual productive time makes the whole exercise a guess. That's why the free trial exists: measure your real numbers for a few weeks before you draw conclusions.
Your categories must be right
If your main business app is uncategorized, real work lands in neutral and the gap looks bigger than it is. Review categories by team before trusting the result.
Salary is only part of the cost
Salary divided by 2,080 understates the true cost of an hour, because benefits, payroll taxes and overhead add to it. Using salary alone keeps the estimate conservative, which is usually what you want when presenting it.
What the number does not tell you
A cost figure is a starting point. It does not tell you why the gap exists. Common causes include:
- Work that happens away from the computer, such as phone calls or site visits.
- Not enough work assigned to some roles.
- Slow or broken systems causing waiting time.
- Unclear priorities or too many meetings.
- Disengagement or personal issues for specific people.
Only the last one is about individual effort, and even then it calls for a conversation, not an accusation. The first four are management problems you can often fix quickly.
Break it down by team and by shortfall
A single company-wide number hides the useful detail. Break the gap down two ways:
- By team. Is one department responsible for most of the gap? That points to a workload or process issue in that team.
- By shortfall band. How many people are slightly under goal, and how many are far under? A few people far under goal is a different problem from everyone being a little under.
The CyberWall Insights workforce utilization and financial loss report does this automatically. You enter an average salary, and it shows users under goal, untapped capacity in FTE, monthly and annual cost, and breakdowns by team and by shortfall band.
Presenting the number
If you're sharing this with partners, a board or a finance team:
- State your assumptions: salary, goal, workdays.
- Say that the figure is an estimate based on computer activity.
- Show the range. What does it look like if the goal is half an hour lower?
- Pair it with a plan. "Here is the gap, and here are three things we'll try first."
Put it in context with the tool cost
It's reasonable to compare the cost of the gap with what it costs to measure it. CyberWall Insights is $4 per active user per month, so for the 20-person example that's $80 a month. Recovering even a small part of the gap usually covers that many times over. Just be honest that the gap won't close to zero, and that some of it reflects real work the computer can't see.
Summary
- Cost of the gap = (goal minus actual) × hourly cost × employees × workdays.
- Convert to FTE for a planning view.
- Use a realistic goal and measured actuals.
- Break the result down by team and shortfall.
- Treat the number as the start of a conversation about causes.