Key takeaways
- Roughly 70–80% of pricing problems in the $5–50M range have a cost-per-person error underneath them. The most consistently missed line items are employer payroll taxes and per-seat software costs.
- A realistic utilization rate for most SaaS roles sits between 65–80%. Pricing off 2,080 FTE hours instead of actual productive hours is one of the most common ways margin disappears quietly.
- Before you price a single engagement, calculate your fully burdened rate: not salary, not salary plus benefits, but every cost that disappears when that person leaves.
- If you're not sure what your team actually costs to deploy, book a 30-minute working session — we'll run the numbers and check your pricing against the real floor.
A mid-level engineer has a salary line of $90,000. The actual cost to employ that person (once you add payroll taxes, benefits, tools, training, and admin overhead) is $124,120. That's 38% higher than what most founders use when they price services or approve headcount.
If your team was pricing that role's work at 2x salary, you were charging roughly $86/hour. The fully burdened break-even is $85.25. You were covering the cost by a dollar. No margin, no room for error.
BLS data for private industry workers confirms why: benefits alone account for nearly 30% of total employer compensation cost, on top of wages. This is a structural gap that appears in every hire.
Most teams know some version of this, but very few have calculated the actual number. This guide walks through how to do it in five steps, and more importantly, how to use it to make three decisions that most founders are currently getting wrong: how to price billed work, when to approve a hire, and how to protect margin as headcount grows.
Step 1: Understand What ‘Fully Burdened’ Actually Means
The fully burdened labor rate is the total annual cost of employing one person, divided by the number of productive hours they work in a year. It is not their salary, or salary plus benefits: it’s every cost that disappears when that person leaves.
The five categories that make up a fully burdened rate:
And here’s a common miss: companies include SaaS seat costs but forget that a new hire also consumes manager bandwidth — typically 10–20% of a manager’s time in the first 90 days. That cost is real and recurs with every hire.
Research across enterprise engineering teams found that new hires without AI tooling took an average of 91 days to reach consistent contribution — a useful proxy for how long the onboarding cost runs on the manager. That’s three months of shared overhead before the hire is delivering at full capacity.
Step 2: Use the Right Formula
The basic structure looks like this:
Formula:
Fully Burdened Rate (hourly) =(Salary + Benefits + Payroll Taxes + Tools + Training + Admin) ÷ Billable Hours
Where billable hours = (Total FTE hours) × (Utilization rate)
A standard FTE year is 2,080 hours (52 weeks × 40 hours). But no one is productive for all 2,080. Account for:
- Paid time off: 10–15 days standard, up to 20+ for senior roles
- Sick and personal leave: 5–8 days average
- Internal meetings, admin tasks, non-billable work: typically 15–25% of total hours
A realistic utilization rate for most SaaS and services roles sits between 65% and 80%. At 70% utilization, your effective productive hours drop to around 1,456/year — not 2,080.
Let’s go back to our example from the beginning: a mid-level software engineer.
* Employer FICA is 7.65% — 6.2% Social Security + 1.45% Medicare — on every dollar of wages. Source: IRS Topic No. 751 (irs.gov/taxtopics/tc751)
The salary line read $90K. The actual cost is $124K — 38% higher. If the team was pricing services at 2× salary, they were charging roughly $86/hour. The actual break-even cost is $85.25/hour — meaning they were just barely covering cost, not generating margin.
Here's what this looks like when the gap goes unnoticed at scale.
A B2B SaaS company at around $18M ARR was pricing implementation packages based on a $95K "cost" for their senior solutions engineer.
The fully burdened number — salary, payroll taxes, benefits, equity amortization, laptop, SaaS tools, a share of people ops overhead — came to $147K. They were billing that role at 1.4× what they thought was cost. The actual multiple over true cost was 0.9×. They were losing money on every implementation engagement and attributing the margin erosion to "sales inefficiency."
Step 3: Benchmark, But With the Right Context
The industry rule of thumb is that fully burdened costs run 25–40% above base salary. That range is wide for a reason: it varies by location, employment model, seniority, and benefits generosity.
Location alone moves total employer cost by 30–40%. BLS regional data for the US shows the Northeast-to-South gap in total hourly compensation runs over $16, which is a difference that has nothing to do with productivity and everything to do with geography.
Source: SHRM: The Myth of Replaceability — Preparing for the Loss of Key Employees, January 2025
The benchmark is a starting point. Your actual number may differ. What matters is that you calculate it for your own team and use it as an input, not an assumption.
Step 4: Don’t Treat Remote as Structurally Cheaper
Remote teams have lower real estate costs, but several cost categories shift rather than totally disappear. Three of them come up almost every time.
First, home office and equipment stipends — real cash costs that simply don't exist for in-office roles where the desk, monitor, and internet are already sunk costs.
Second, async collaboration tooling: Notion, Loom, Slack premium, Zoom — the per-seat costs add up faster than most founders track them.
Third, and most underestimated: travel. Quarterly offsites, annual kick-offs, and occasional client visits for "remote" employees often run $3–6K per person per year.
On a 20-person remote team, that's $60–120K that doesn't show up in a salary-based cost model.
This is why you should track remote-specific costs as a separate category. The overhead doesn’t disappear, but rather redistributes. A fully burdened model should capture where it lands.
Step 5: Use the Number to Make Three Decisions
Calculating the fully burdened rate is not the goal. Using it to change how you price, hire, and plan margin — that's the point. Here are the three places it should show up in your operating model.
Decision 1: Pricing
If you bill for your team's time, through services, implementation, customer success, or consulting, your floor is the fully burdened rate. Anything below that rate means the work costs you money to deliver.
Target: price at a minimum of 2.0–2.5× the fully burdened hourly rate to generate a serviceable margin after direct costs. Higher-complexity or higher-leverage work should carry a higher multiplier.
Industry benchmarks show professional services gross margins running around 30% at healthy SaaS companies — and when services gross margin falls below that threshold, total gross margin follows. The 2.0–2.5× multiplier is the floor, not an aspiration.
Don't do: Price at "2x salary." That ignores 30–40% of the actual cost base.
Do instead: Calculate the fully burdened rate, set a minimum margin threshold, and build that into your rate card.
Note: Retainer work can tolerate a slightly lower multiple because utilization is predictable; project work needs a higher multiple to absorb the bench time between engagements.
Decision 2: Headcount Planning
Every hire has a margin impact before they generate a dollar of output. A $90K engineer costs $124K/year from day one, and may take 60–90 days before they're contributing at full utilization.
The right question before approving a hire: at what revenue or output does this role become margin-neutral?
The basic structure looks like this:
The break-even formula:
Break-even revenue = Fully burdened annual cost ÷ Gross margin %
For that $124K engineer at a 75% gross margin:
$124,120 ÷ 0.75 = $165,493 in revenue this role needs to support before it stops being a drag on the business.
Now add the ramp period. If the hire takes 90 days to reach full productivity (averaging 50% output during ramp), the first-year effective cost is still $124K, but the first-year effective output is only ~9.5 months of full contribution. That pushes the real break-even revenue higher — closer to $190K for year one.
Run that number against your pipeline or projected output before signing the offer. If you can't point to the specific revenue or output that gets the role to margin-neutral within the first year, the hire isn't ready to approve.
Don't do: Approve headcount based on "we need more capacity." That's a signal, not a plan.
Do instead: Model the break-even point. Present the number alongside the hire request. Make the approver sign off on both the role and the revenue assumption.
Decision 3: Margin Planning
Your team's fully burdened cost is the most controllable input in your margin model. But most companies manage it reactively — they notice the margin problem after headcount has grown, not before.
Two levers that move the number without adding headcount:
Utilization improvement: A team running at 65% that moves to 75% produces more output at the same cost. Using the $124K engineer example — at 65% utilization, the hourly rate is $92.37. At 75%, it drops to $80.05. Same person, same salary, $12/hour less expensive per productive hour.
Role-mix management: Not all roles carry the same burdened rate. Understanding the spread lets you make smarter decisions about where to hire and where to contract.
The basic structure looks like this:
The ARR per FTE calculation:
ARR per FTE = Annual Recurring Revenue ÷ Total full-time employees
At $50M ARR and above, the benchmark is $200K+ ARR per FTE. If your company is at $25M ARR with 150 employees, your ARR per FTE is $166K — below the benchmark and a signal that either utilization or role mix needs attention before the next hire.
The companies improving that ratio fastest are doing it through utilization gains and AI-assisted workflows, not headcount cuts.
Don't do: Treat margin improvement as a headcount reduction problem. Cutting roles is one lever. Improving utilization and output per person is a better one.
Do instead: Run ARR per FTE quarterly. If it's flat or declining while headcount grows, that's the signal your cost model needs attention before your next hire.
Common Mistakes And How to Avoid Them
Most of the margin damage from an inaccurate full burdened rate doesn't come from a single wrong number, but from the same calculation errors repeating across every hire, every pricing decision, and every headcount review.
None of these are difficult to fix once you've identified them, but each one left unaddressed compounds quietly, showing up as margin variance you can't explain and pricing decisions you can't defend.
Fully Burdened Rate: A Quick Audit Checklist
This is the most useful thing in this article. Print it. Run it quarterly. Share it with your finance lead.
Use this to check whether your current pricing and headcount model is built on accurate numbers:
- List every employee. For each, record base salary, bonus target, and benefits cost.
- Add employer payroll taxes (typically 7–10% of salary — FICA alone is 7.65%).
- Tally per-seat tool costs across your tech stack and allocate per employee.
- Estimate onboarding, training, and admin overhead per employee per year.
- Divide total by (2,080 hours × utilization rate) to get the hourly rate.
- Check your current pricing: are you charging at least 2× this rate for billed work?
- Run the break-even model on your last hire: Break-even revenue = fully burdened annual cost ÷ gross margin %. At what output did they become margin-neutral?
- Run ARR per FTE: Is the ratio improving, flat, or declining quarter over quarter?
This exercise takes 2–3 hours the first time. After that, it's a quarterly update.
Stop Pricing Off Salary, Start Pricing Off Cost
The fully burdened labor rate is a decision input, and once you have it, three things get easier: you know the floor your pricing has to clear, you know what a new hire actually costs before you approve it, and you know where margin is leaking before it shows up as a problem at the board level.
Most founders get here eventually. The ones who get here early stop having the "we think we're profitable on services" conversation and start running the business on the actual numbers.
Calculate it once, correctly. Update it quarterly. Use it every time you price a contract or approve a headcount request.
If you want to run this exercise with a fractional CFO who has done it across dozens of SaaS companies in the $5–50M range, book a growth call today. We'll calculate your fully burdened rate by role, check your current rate card against the margin floor, and build the break-even model for your next two hires.
