Outsourced SDR vs In-House — which should you choose?

The question usually arrives in one of two forms. Either "should we hire an SDR or use an agency?", or the more honest version: "who should I hire to run outbound for my SaaS, because nobody here has done it before?"

Most comparisons of this are written by agencies and conclude, remarkably, that you should hire an agency. We are one, so treat the bias as read. But the version that's actually useful says where each option genuinely wins — and there are real cases where hiring is the right answer and we'd say so on a first call, because an engagement that was never going to fit costs us more in a wasted quarter than the fee was worth.

It also helps to start from three answers rather than two. You can run outbound yourself on self-serve tools; you can hire someone in-house to run it; or you can buy it done-for-you, where an outside team runs it as a service. That third option is where most of the confusion lives, because it covers two things that behave nothing alike — a black box that takes a brief and reports back monthly, and a team that works inside your business. Lumping those together is what makes this decision feel like a coin flip. We compare the same three models on pricing and what's included in how much B2B lead generation costs; this page asks the other half of the question — which of them should be doing this work for you at all.

The real question isn't cost. It's who owns the ramp.

People frame this as a budget comparison — SDR salary versus what an agency invoices — and then get surprised when the numbers come out closer than expected and the decision still feels unclear. That's because cost isn't the variable that decides it. Nor, in our experience, is the choice as binary as the framing suggests.

The third option is also why the binary framing misleads. "Done-for-you" spans everything from an arm's-length supplier who takes a brief and sends email, to a team that sits inside yours: in your pipeline meetings, listening to your sales calls, talking to your AEs about which objections keep coming up. The second behaves far more like a hire than like a vendor — it's where we operate, and it's the version this page argues for. Most comparisons pretend the distinction doesn't exist, which is how you end up weighing an employee against a black box and concluding, reasonably, that the employee wins.

You're not choosing between two prices. You're choosing who absorbs the months before outbound works, and who carries the risk if it doesn't.

Outbound has a long, unglamorous run-up: research, list building, domains, warm-up, message testing, and several rounds of getting it wrong before the replies start. Someone pays for that period. Hire in-house and you pay for it in salary and management attention while producing very little. Outsource and you pay for it in fees, but you're renting a team that has done the run-up before and won't spend your quarter discovering that catch-all domains exist.

1 · What an in-house SDR actually costs

The salary is the part everybody budgets and the smallest part of the real number. What gets missed:

• Finding them. Recruiter fees if you use one, and weeks of your own time if you don't. Good SDRs are competitive to hire; the ones available immediately are often available for a reason.
• Base plus variable. The on-target number is the one to plan against, not the base.
• The stack. A data provider, a verification tool, a sending platform, domains and inboxes, a CRM seat. Individually small, collectively a real line, and mostly billed annually whether the SDR works out or not.
• Management time. The biggest hidden cost and the one nobody prices. An SDR without coaching doesn't become a good SDR; they become an expensive person sending mediocre email. If nobody on your team can review their sequences weekly and tell them what's wrong, you haven't hired a solution.
• The risk it doesn't work. First sales hires fail often. If it does, you've spent the money, lost the months, and start again — and the domains you burned along the way don't recover instantly.

We deliberately don't publish figures for any of this, for the same reason our cost guide doesn't: the honest number depends on your market, your seniority band and your geography, and a made-up range would be worse than none. What's transferable is the shape: salary is the line everyone budgets, and it's the one that surprises people least. Recruitment, tooling, domains and management hours are not rounding errors against it.

2 · Ramp is the number that decides most of this

Here's the part that catches people out, because the clock starts long before anyone sends an email.

You have to find the person. Then they work a notice period. Then they learn your product, your market and your buyer — which for a technical or regulated product is not a two-week exercise. Then they build lists and warm domains, which is itself weeks before volume is safe. Then they start testing messages, and the first several rounds won't work, because the first several rounds never do. And then your sales cycle adds its own lag between a booked meeting and anything you'd call revenue.

Stack those honestly and you're looking at the better part of two quarters between deciding to hire and having dependable pipeline. Not because SDRs are slow — because that's how long the sequence takes.

The comparison that matters, then, isn't salary versus invoice. It's: when do you need pipeline? If the answer is "this quarter", hiring doesn't solve it whatever you spend. If the answer is "we're building for next year", the calculus flips entirely.

3 · When hiring in-house is the right answer

Genuinely, and we'll say this on a call rather than pitch against it:

• Outbound is core to how you sell, permanently. If it's the main channel and always will be, the capability belongs inside. Renting a core competence forever is bad economics.
• You have someone who can manage them. A sales leader who has run outbound, has opinions about sequences, and will actually review the work weekly. This is the single strongest predictor of an in-house hire succeeding.
• Your product needs deep knowledge and you can't give an outside team access to it. Some products can't be pitched credibly without real context — highly technical, heavily regulated, or sold to a small expert community that spots an outsider instantly. That's a genuine argument for in-house, but only against an arm's-length supplier. An embedded team learns the same way a new hire does: by sitting in the meetings and listening to the calls. If you're not willing to open that up, hire.
• Your deal sizes justify a dedicated person. If a handful of wins pays for the seat several times over, the maths stops being tight and the argument for control gets stronger.
• You're building a team, not filling a gap. The first SDR is rarely worth it in isolation. The first of five, with a manager and a system, is a different proposition.

4 · When outsourcing is the right answer

• You need pipeline sooner than a hire can produce it. The ramp argument, in reverse. An experienced team skips the run-up because they've already done it.
• You're testing whether a market responds at all. Entering a new country or a new segment is exactly the case where you don't want to hire against an unproven thesis. Test first, hire against evidence.
• Nobody on the team has run outbound before. An unmanaged SDR is the most expensive of the three options — you pay full price for the seat and get the output of someone learning alone.
• The work is bursty. A launch, a conference season, a push into one vertical. You can scope a campaign to the burst and stop; you can't scale a person down. This is worth asking about explicitly, because it depends entirely on how the work is priced — a scope quoted per contact flexes with the burst, a fixed monthly commitment doesn't.
• The infrastructure is the barrier. Domains, warm-up, deliverability and data hygiene are where first-time outbound quietly dies — see deliverability and B2B data for outbound. Buying that setup already working is often the actual value, more than the sending itself.

5 · When the answer is neither

Worth saying because it applies more often than either side of this debate admits: if you're pre-product-market-fit, or your first customers came from your own network and you haven't yet found a repeatable message, the right answer is usually you, doing it by hand, for a while longer.

Founder-led outreach at that stage isn't a stopgap — it's research. The first hundred conversations tell you what actually resonates, and that knowledge is what makes any later hire or agency effective. Delegate it too early and you're paying someone to guess at a message you haven't found yet. We've written the lean version of this in how to start outbound as a founder.

6 · What done-for-you looks like when it's done properly

The word "outsourced" does a lot of damage here. It suggests a black box: you send a brief, meetings appear, nobody learns anything. That version exists, it's what most people picture, and it's why the comparison feels so stark.

The version we run looks different. We're in the pipeline meetings. We listen to sales calls — not a summary of them, the actual calls. We talk to the AEs about which objections come up again and again, and to customer success about why people actually stay. When a message stops working, we hear about it in the same meeting your team does, rather than in a monthly report.

That matters because the raw material of good outbound isn't in a brief. It's in the sentence a customer used on a call last Tuesday, the objection your AE is tired of hearing, the reason the last three deals stalled. A team that isn't in the room can't get at any of it, and no amount of research replaces it.

There's a second reason distance fails, and it's about timing rather than knowledge. Outbound is coupled to what's happening inside the business. A feature shipping next month changes what's worth leading with. A funding round changes how you describe your stage — and if you're raising, and the outreach is to investors rather than customers, that coupling is the whole job. A pricing change, a new integration, a segment you've quietly decided to stop serving: each of those should change the message the week it happens, not the quarter after. A team that finds out about a launch when the newsletter goes out is always describing last quarter's company.

It's also structural in how the first month runs. Before any campaign goes out at scale, we run live conversations with people who match the ICP — found and approached by hand — and the output is a dictionary of how buyers describe their own problems: their vocabulary, their objections, the triggers that make them start looking. Somewhere between forty and a hundred of those conversations. You cannot hold one of them credibly, let alone a hundred, without understanding the product properly. The depth isn't a courtesy in the relationship; it's a precondition for doing the work at all. It's week two of what we build, before a single campaign email goes out.

It also collapses most of the "control" argument. The reason people reach for in-house is usually context and visibility — knowing what's being said in their name, being able to change it this week rather than next quarter. Those are properties of how a team works, not of who signs their payslip.

7 · The sequence almost nobody plans for

The framing as a binary is the weakest part of how this decision usually gets made. The sequence that works well, and gets used less than it should:

Outsource to prove the market, then hire against what you learned. Run outbound with a team that already has the infrastructure, find out whether your segment responds and which message does it, and then — if outbound is going to be permanent — hire an SDR who inherits a proven message, a working list, warmed domains and a set of sequences that already book meetings.

That person ramps in a fraction of the time, because the hard part is done. And you're writing the job description with evidence about what good looks like in your market, rather than copying one from a company that sells something else. Handing over properly should be part of the arrangement — ask about it before you sign, not at the end.

8 · What to ask, whichever way you go

The same diligence applies to a candidate and to a supplier — you're buying judgement in both cases.

• Where does the list come from, and how is it verified? Ask a candidate this in the interview. The answers separate people who have run outbound from people who have watched it.
• What happens in the first 30 days, before any email goes out? Anyone who plans to start sending in week one is skipping something you'll pay for later.
• Who owns the sending domains? Applies to both. Warmed domains are an asset, and you want to know whose it is.
• What would you change first if month two produced nothing? The order of the answer — usually targeting before copy, copy before channel — tells you whether they've been through it.
• What have you stopped doing in the last year? Everyone with real experience has abandoned something.

The longer version, aimed at agencies but just as useful in an interview, is in questions to ask a lead generation agency.

The takeaway

Hire in-house when outbound is permanent, someone can manage the person, and you can fund the months before they produce. Outsource when you need pipeline faster than a hire can deliver it, when you're testing whether a market responds, or when nobody internally has done this before. Do it yourself a while longer if you haven't found the message yet.

But don't take the binary too seriously. The gap between a good agency and a hire is much narrower than the words suggest — an embedded team sits in your meetings, hears your calls and learns your product the same way an employee would, without the recruiting, the notice period or the ramp. The real question isn't employee versus supplier. It's whether whoever does this work is close enough to your customers to say something true about them.

The one answer that's reliably wrong is hiring an SDR into a company where nobody can coach them, because it's the most expensive way to discover that outbound is harder than it looks.