How to Calculate the True Cost of an Employee

A salary number is the smallest piece of what an employee actually costs a business, and treating it as the whole number is one of the more common budgeting mistakes small businesses make when planning a hire. The fully loaded cost — salary plus taxes, benefits, and overhead — is routinely 25 to 40% higher than the number on the offer letter.

The formula

Fully loaded cost = Base salary + Employer payroll taxes + Benefits + Overhead

Each piece is worth breaking out on its own, since they vary independently and a rough combined percentage can hide which part is actually driving the number.

Employer payroll taxes

Employer-side Social Security and Medicare contributions, plus federal and state unemployment insurance, typically add somewhere around 7-10% on top of base salary, varying by state and by wage base thresholds. This piece is the most predictable and the least within a business's control.

Benefits

Health insurance, retirement matching, and other benefits are the most variable piece, and often the largest. What a small business chooses to offer directly drives this number — a role with a modest benefits package might add 10-15% here, while a full group health plan and retirement match can push it considerably higher.

Overhead

Equipment, software licenses, a share of workspace or utilities if applicable, and any tools specific to the role. Often underestimated because it's spread across many small line items rather than showing up as one visible cost, but it's real and adds up — a laptop, standard software seats, and a share of office costs commonly land somewhere in the range of a few thousand dollars a year per employee, more for specialized equipment or software.

A worked example

A role with a $60,000 base salary:

• Base salary: $60,000
• Employer payroll taxes (~8%): $4,800
• Benefits (health insurance + modest retirement match, ~18%): $10,800
• Overhead (equipment, software, workspace share, ~7%): $4,200

Total fully loaded cost: $79,800 — roughly 1.33 times the base salary.

That gap — nearly $20,000 on a $60,000 role — is exactly the part that gets missed when a hiring decision is budgeted against salary alone.

Why this matters for hiring decisions

Comparing a new hire's cost against the revenue or value they're expected to generate is a common and reasonable exercise, but it only works if the cost side of that comparison is the real, fully loaded number rather than the salary line. A role that looks comfortably affordable at $60,000 against a book of business or a workload estimate can look considerably tighter at $80,000 — the actual number the business is on the hook for.

This is also where hiring decisions sometimes go wrong in the other direction: treating the fully loaded cost as fixed and unavoidable, rather than recognizing that the benefits and overhead pieces are genuinely adjustable levers, not laws of nature.

Where this connects to PTO and time off

Base salary already implicitly covers paid time off — an employee earning $60,000 a year is paid that amount whether or not they take their allotted vacation, since PTO doesn't reduce salary. What's worth being conscious of is the relationship between fully loaded cost and actual working days: a role costing $79,800 a year that includes, say, 15 PTO days and 10 holidays is effectively being paid at a slightly higher true daily rate on the days actually worked than the raw annual-cost-divided-by-365 math would suggest. This isn't a reason to discourage PTO — it's simply the honest arithmetic behind why unused, uncompensated overtime or an unusually low PTO allowance doesn't meaningfully change the fully loaded cost calculation on its own.

Using this for contractor-versus-employee comparisons

Fully loaded cost is also the right basis for comparing a W-2 hire against a contractor engagement, since a contractor's rate already reflects that they're covering their own equivalent of taxes and benefits. Comparing a contractor's hourly or project rate against an employee's bare salary — rather than their fully loaded cost — consistently makes the contractor look more expensive than the comparison actually supports. Getting worker classification right matters here too, since the choice between the two isn't purely a cost decision to begin with.

A simple way to calculate your own number

For any role, add: base salary, roughly 7-10% for employer payroll taxes, your actual benefits cost for that role (not a guess — pull the real numbers from your health insurance and retirement plan), and a reasonable overhead estimate based on what the role actually requires. The result is specific to your business rather than a generic multiplier, which matters more the larger or more unusual a hire's compensation or benefits package is relative to the rest of the team.

Using this number in a hiring budget, not just after the fact

The most useful moment to calculate fully loaded cost is before a role is approved, not after someone's already been hired and the real number shows up in the first few payroll cycles. Building the fully loaded estimate into the initial hiring request — rather than a salary figure alone — means whoever approves the hire is actually weighing the real cost against the expected value of the role, not an understated one that makes almost any hire look easy to justify on paper.

A quick sanity check for an existing team

Applying this same math across an existing team's total headcount gives a more accurate total payroll and benefits cost than summing base salaries alone — often a meaningfully larger number than what shows up when someone informally estimates "how much do we spend on people" using salary figures from memory. This total is worth having accurately on hand for budgeting, fundraising conversations, or simply understanding where a business's largest cost category actually stands relative to everything else.

The short version

The fully loaded cost of an employee is routinely 25-40% above base salary once payroll taxes, benefits, and overhead are included — a gap that's easy to underestimate when a hiring decision is budgeted against salary alone. Calculating the real number for a specific role, rather than relying on a generic rule of thumb, is the difference between a hiring decision that holds up once payroll starts and one that quietly strains the budget from month one.