What an SDR actually costs once you stop looking at salary
A $65,000 SDR does not cost $65,000. Here’s the part of the spreadsheet everyone conveniently forgets.
Short Answer
A $65,000 SDR can easily become a roughly $120,000 annual sales-development function once you add variable compensation, benefits and payroll burden, management time, software, and data. That is about $10,000 per month before recruiting costs, ramp time, or the cost of a bad hire. Compare the cost of the entire function, not salary against an outsourced retainer.
A $65,000 SDR does not cost $65,000.
It costs $65,000 plus commission, benefits, payroll tax, software, data, management time, recruiting, onboarding, and several months of paying someone while they figure out what the hell they are supposed to say.
Salary is just the easiest number to put in the spreadsheet.
Here is a pretty normal planning model for one junior business-development hire:
* Base salary: $65,000 * Variable compensation: $15,000 * Benefits and payroll burden: $18,000 * Management overhead: $12,000 * Sales technology and data: $10,000
Annual cost: $120,000
That is $10,000 a month.
And that is the relatively clean version.
It does not price in a recruiter. It does not price in a bad hire. It does not price in replacing someone nine months later. It definitely does not price in the founder spending every Tuesday afternoon rewriting cold emails because nobody can explain why the sequence is getting ignored.
The rep is only one part of the outbound function
Hiring an SDR solves one problem:
You now have an SDR.
It does not automatically give you a functioning outbound motion.
Somebody still has to decide:
* Which companies should we target? * Which people inside those companies matter? * Where does the data come from? * How do we score the accounts? * What should we say? * Which channels should we use? * How much volume is safe? * What happens when someone replies? * What gets changed when nobody replies? * Who is listening to calls? * Who owns deliverability? * Who maintains the CRM? * Who decides whether the problem is the rep, the list, the message, or the offer?
A good SDR can execute a good system.
Expecting a junior hire to invent the system, run it, diagnose it, and hit quota at the same time is how companies end up hiring another SDR six months later.
Tooling gets stupid quickly
You do not need every sales tool on earth.
You will probably end up paying for more of them than you expected.
CRM.
Sales Navigator.
Contact data.
Enrichment.
Email infrastructure.
Sequencing.
A dialer.
Call recording.
Maybe intent data.
Maybe a second data provider because the first one thinks the VP of Sales at a 12-person company is named NULL.
None of these costs look catastrophic individually.
Together, they turn into a real line item.
Then someone has to know how the pieces work.
Management is a cost even when nobody puts it in the budget
This is the sneakiest number.
A junior SDR needs management.
That is normal.
Someone needs to review the work, coach calls, check lists, fix messaging, answer questions, inspect pipeline, and decide what changes next.
If your VP of Sales earns $180,000 and spends 10% of their working time managing one SDR, that time is not free because QuickBooks does not send you an invoice for it.
If the founder is doing the management, it is arguably more expensive.
It just hides better.
Ramp matters too
The first month is rarely full productivity.
Nor should it be.
The rep is learning your product, buyer, market, objections, CRM, tools, messaging, qualification criteria, and all the strange little facts that make someone useful in a sales conversation.
If the underlying outbound motion is already proven, ramp is mostly a training problem.
If the motion is not proven, ramp turns into experimentation.
Now your new SDR is simultaneously learning the company and helping the company figure out whether the outbound strategy works at all.
That is a much harder job.
None of this means you should not hire an SDR
An in-house SDR can be a great hire.
Especially when:
* your ICP is already clear * messaging has evidence behind it * the market is large enough to support sustained prospecting * someone competent can manage the rep * the infrastructure already exists * you expect sales development to remain a permanent internal function
At that point, hiring makes a lot of sense.
You are hiring a person into a machine that already knows roughly where it is going.
The mistake is hiring the person because you do not have the machine.
The better question is cost per useful conversation
Annual headcount cost is useful for budgeting.
It is not how I would judge whether outbound is working.
I would rather know:
How much are we spending to create a held conversation with somebody who could realistically buy?
Not an email reply.
Not a connection request.
Not a meeting with somebody who accepted because the SDR offered them an Amazon gift card.
A real conversation.
If you spend $10,000 a month on an internal function and create 10 qualified held meetings, that is roughly $1,000 per conversation.
If you spend $6,250 on outsourced outbound and create the same 10, that is $625.
If you spend $3,000 and create two, the supposedly cheaper option costs $1,500.
That is the math worth watching.
Run the whole number before you hire
There is nothing wrong with building sales development internally.
Eventually, many companies should.
Just compare the right numbers.
Do not compare a $65,000 salary against a monthly outbound retainer and declare the case closed.
Compare the function against the function.
People.
Management.
Data.
Software.
Infrastructure.
Ramp.
And the actual conversations that come out the other side.
The salary was never the whole price.
It was just the number printed on the job posting.