Your Loaded Hourly Cost Is Higher Than You Think

Most owners evaluating an automation use the wrong number. They look at the employee's hourly wage, multiply by hours saved, and call that the return. That math is wrong by a factor of roughly 1.5 to 2x. The number you should be using is the loaded hourly cost, and once you have it, every automation decision gets simpler.

Here is why this matters: if you think your bookkeeper costs you $28/hour because that is her wage, an automation that saves her four hours a week looks like $5,800/year of value. The real number is closer to $11,000. That is the difference between a project that pays back in 14 months and one that pays back in 7. Same automation. Same hours saved. Different decision.

The formula#

Loaded hourly cost is the total annual cost of employing someone, divided by the productive hours they actually work. Both halves of that equation get fudged in standard calculations.

Total annual cost = base wages + payroll taxes + benefits + paid time off + indirect costs.

Productive hours = paid hours − PTO − sick days − holidays − meetings − admin overhead.

Write both numbers out. Then divide. The result will surprise you.

A worked example#

Let's take a $58,000/year office manager at a 12-person services firm. The owner thinks of her as costing roughly $28/hour ($58,000 ÷ 2,080 hours).

Now the real math.

Total annual cost:

• Base salary: $58,000
• Payroll taxes (FICA, FUTA, SUTA, workers comp): roughly 11% = $6,380
• Health insurance contribution: $7,200/year ($600/month employer share)
• Retirement match (3%): $1,740
• Other benefits (dental, vision, life): $900
• Equipment and software (laptop, phone, SaaS seats amortized): $2,400
• Office space allocation (rent, utilities, insurance per seat): $4,800
• Training, recruiting amortized, payroll processing fees: $1,200

Total: $82,620

Productive hours:

• Paid hours: 2,080
• Less 15 PTO days: −120
• Less 8 holidays: −64
• Less 5 sick days (average): −40
• Less 1 hour/day of meetings, breaks, admin overhead: −230

Productive hours: 1,626

Loaded hourly cost: $82,620 ÷ 1,626 = $50.81/hour

That is 81% higher than the $28 figure the owner was using. Not 10% higher. Not 20%. Eighty-one percent.

What gets missed and why#

The gap between $28 and $50.81 lives in the line items owners reflexively exclude from "labor cost." A few worth flagging.

Benefits load. Bureau of Labor Statistics data puts benefits at roughly 30% of total compensation for private-sector workers. If you offer health insurance, you are in that zone. If you do not, you are still paying payroll taxes, which alone add 10-12%.

Allocated overhead. Every employee consumes office space, software seats, IT support, management attention, and HR cycles. These are real costs caused by that headcount. Spread your total operating overhead across your team and the per-employee number is rarely under $5,000/year.

The productive hours denominator. This is where the biggest distortion hides. Paid hours are not productive hours. A salaried employee at 2,080 paid hours is probably delivering 1,500-1,700 hours of actual focused output. Dividing by 2,080 makes the hourly cost look lower than it is.

Replacement cost risk. Not in the per-hour number, but worth holding in mind: if a key employee leaves, recruiting and ramping a replacement typically costs 50-200% of annual salary. Automation that reduces dependency on any single role buys you insurance against that.

How to run your own number#

Do this exercise once for each role you are considering automating around. It takes 20 minutes per role.

1. Pull the actual W-2 or 1099 figure for last year. That is your base.
2. Add your specific tax burden. Your accountant can give you the percentage in one email.
3. Add real benefits dollars, not what you offered — what you actually paid.
4. Add a per-seat overhead figure. If you have never calculated this, take total operating overhead minus owner compensation, divide by headcount. Crude but directionally right.
5. Subtract PTO, holidays, sick days, and a realistic meeting/admin estimate from 2,080.
6. Divide.

Keep the number written down. Put it next to the role on a spreadsheet. When a vendor pitches you a $400/month tool that saves five hours a week, you now have the answer in 10 seconds: 5 hours × 52 weeks × $50.81 = $13,210/year of value against $4,800 of cost. That is a 2.75x return before you have even thought about quality improvements or capacity unlocked.

The decision this changes#

Once you have loaded hourly cost, three things shift.

First, more automations clear the bar. Projects you previously dismissed as marginal become obvious wins. The $400/month tool that looked like a 1.4x return at the wage rate is a 2.75x return at the loaded rate.

Second, the conversation about which hours to automate gets sharper. Not all hours are worth $50.81. Some of your office manager's time is high-leverage relationship work that you would not automate at any price. Some is data entry that a $50/month tool can do. Knowing the rate lets you ask: would I rather pay $50.81/hour for a human to do this, or $2/hour for software? The answer is usually obvious once framed that way.

Third, you stop confusing "we already pay her salary" with "this work is free." Salaried hours have an opportunity cost. Every hour your office manager spends reconciling invoices is an hour she is not spending on the work only she can do. The loaded rate is the price of that tradeoff.

If you want help running this calculation across your team and identifying which automations actually pay back at your real labor cost, that is what our diagnostic process is built for.