Base salary vs. fully loaded cost — the multiplier most CROs get wrong

Ask a CRO what an SDR costs and you will get the base salary times a polite loading factor — usually 1.25×, sometimes 1.4× if finance insisted. Ask the CFO to reconcile what the sales development function actually consumed at year end, and a different number appears: close to double the base, every seat, every year.

Neither person is lying. They are counting different things. The loading factor in most planning models was built for salaried back-office roles: it covers statutory taxes and benefits and nothing else. A quota-carrying seat breaks that model in four places at once — variable comp, equity, turnover, and ramp — and each omission compounds the others.

This article decomposes the multiplier line by line, from the $62K offer letter to the $127K+ reality. It is the compensation layer of the full model in The True Cost of a Seven-Person SDR Team; the tooling layer lives in The tech stack tax.

Where does the standard loading factor come from — and why is it wrong here?

The 1.25–1.4× factor is a back-office artifact. It was derived for stable salaried roles where taxes and benefits are the only meaningful additions to base pay. Apply it to a quota-carrying, high-turnover, slow-ramping role and it fails on all three properties at once.

The statutory portion it covers is real and predictable: employer FICA at 7.65%, federal and state unemployment insurance, workers' compensation — call it $7,600 on our benchmark seat. Benefits add the next tranche: employer share of health, dental, and vision premiums plus a 3% 401(k) match — about $14,200. Base plus those two categories is $83,800, or 1.35× base. This is the number most models stop at, and it is the last point in the calculation where the model still feels defensible.

Everything after this point is what separates a planning artifact from a cost model.

What do the missing categories add?

Roughly $44K a year per seat, in four categories the standard factor never touches. Each one is defensible to exclude in isolation; excluding all four is how a plan misses by a third.

1. Variable compensation — $23,000

An SDR is hired against an $85K OTE, and a functioning team pays most of it: that is the point of the plan. Budgeting the base and treating commissions as "self-funding from pipeline" double-counts the pipeline — the meetings were the job, not a bonus surprise. At plan, variable comp is the single largest gap between the offer letter and the truth.

2. Equity — ~$3,800/year

A typical mid-market SDR grant of ~$15K vests over four years: $3.8K a year of stock-based compensation. It never touches payroll, so it never enters the sales budget — but it dilutes the cap table and lands on the P&L all the same. Multiply by every seat on the go-to-market org and the "invisible" line becomes material.

3. Recruiting and backfill — ~$7,600/year amortized

A recruited SDR costs $12–15K to land — agency fee or the loaded cost of internal recruiting — and stays under two years. Amortize acquisition cost over realistic tenure, not over an assumed forever, and each seat carries ~$7,600 a year in perpetual re-hiring cost. This is not a one-time expense; at SDR turnover rates it is an annuity.

4. Ramp drag — ~$9,200/year amortized

A new SDR takes roughly three months to reach full productivity, producing at about half rate while drawing full compensation. That is ~$16K of paid-but-unproductive cost per hire — re-purchased at every backfill. Spread across the tenure of the average seat: ~$9,200 a year.

What is PTO drag — and why does every model miss it?

PTO drag is the gap between days you pay for and days you get output from — and it hides because it is a divisor on productivity, not a line item on a budget. Nothing gets added to the cost; the output the cost buys quietly shrinks.

The benchmark seat is paid for 260 working days. Subtract 15 PTO days, 10 company holidays, and 5 sick days, and the business receives about 230 productive days — 88.5% of what it paid for. Every meeting, every SQL, every dollar of sourced pipeline therefore costs ~13% more than a naive per-day calculation implies.

This matters most exactly where planning models are most confident: capacity math. A model that staffs "seven SDRs × 15 meetings a month" has silently assumed 260 productive days per seat. Layer PTO drag under the ramp and turnover effects from the pillar model and theoretical capacity erodes to roughly three-quarters of what the plan promised — while cost stays at 100%.

"When midmarket enterprises embed AI into their core operations, they eliminate bureaucratic drag, allowing them to out-maneuver larger competitors who are constrained by legacy silos." » George Schildge · CEO & Chief AI Officer, MatrixLabX

How should a CRO use the corrected multiplier?

Three ways: budget with it, benchmark with it, and buy with it. A corrected loading factor is not an accounting curiosity — it changes real decisions.

1. Budget with it. Any headcount request below 2× base for quota-carrying roles is understated. Present the fully loaded number to finance first; credibility compounds.
2. Benchmark with it. Cost per meeting and cost per SQL must divide the fully loaded run rate by effective output. On the benchmark seat that is ~$1,250 per held meeting — not the $344 the base-salary math suggests.
3. Buy with it. Every make-vs-buy comparison — agency, outsourced SDR firm, or a governed AI SDR — is distorted when the in-house column shows 1.25× base. Compare against 2.05×, and the alternatives reprice dramatically. Most AI SDR vendors don't publish a number; the one that does is on the Sales Accelerator pricing page.

The third use is where the multiplier earns its keep. Governed autonomous agents carry none of the loading stack — no payroll tax, no benefits, no equity, no PTO, no recruiter, no ramp. Labor as a Service pricing maps spend to executed workflows and outcomes, so the number in the plan is the number on the invoice. The loading-factor error class simply does not exist.