White-label vs in-house SDR: the real cost of offering outbound

When an agency prices up building an outbound capability, the spreadsheet usually starts and ends in the same place: what does an SDR cost, how many do we need, what do we charge. That model is easy to build and it’s almost always too kind.

The costs that actually decide whether a built team pays off are the ones that don’t appear as a line item — utilization across lumpy client demand, and the management overhead of keeping people staffed, trained and busy. This guide is the honest version of that math, with no invented numbers: the frame is ours, the rates are yours to plug in.

Start with what’s true about building, because it’s a real option and plenty of agencies should take it. You own the capability. You control the quality directly, you shape how people sell, and the knowledge stays in the building — a team that learns your clients’ categories gets better at them every quarter. For an agency where outbound is a core, high-volume service, that ownership is worth real money.

So the argument here isn’t against building. It’s about which number decides it — because the comparison almost always starts on the wrong one. Someone looks up an SDR salary, sets it against a vendor’s monthly fee, and decides from there. The salary is the visible cost. It’s also the smallest part of the real one.

A seat costs the same in the month a client pauses as in the month three campaigns run at once. Agency demand is lumpy by nature — clients start, stop, renegotiate, go quiet over a quarter — and a fixed team is the one part of the business that can’t flex with them.

Start with the seat itself. A seat is never just the base pay: add payroll taxes and benefits, the tools and data an SDR needs to work, the time it takes to hire the right person, and the weeks or months before a new hire is actually productive. Fully loaded, a seat costs a good deal more than the salary line suggests.

Even the fully loaded number isn’t the real problem, though. The real problem is what that seat does when there’s no work for it. A team sized for your good months sits partly idle in your slow ones, and you carry the idle time. A team that’s 60% utilized across the year costs you nearly what a fully utilized one does; you just get less for it.

That idle time is the true cost of building, and it’s the one the salary comparison completely hides. We’re not going to put a figure on it, because there isn’t a defensible one to borrow. You can put your own on it, and the last section shows you how.

Then there’s the cost that never shows up on a spreadsheet but runs the whole time: your own attention. Someone has to hire, onboard, coach and QA the messages going out under your clients’ names, and keep every person on target. That someone is usually you, or a senior person whose hour is worth considerably more than the SDR’s.

It compounds with churn. The role turns over quickly, so a ramp you paid for once you pay for again, and the category knowledge you were building leaves with the person. None of this is a reason not to build. It’s simply part of the cost, and it belongs in the model rather than in your evenings.

This is the reason idle time hurts more here than in most service lines. Booking a first meeting takes roughly eight touches (RAIN Group) — so a team needs steady, continuous work across clients to reach the point where the effort turns into meetings. Stop-start campaigns pay the cost of persistence without collecting the return.

The connection back to utilization is direct. Outbound rewards sustained effort, so results come from campaigns you run consistently rather than ones you switch on and off. You can’t idle a team through a slow month and expect it to pick up mid-sequence at no cost — the work wants continuity.

Continuity is exactly what a fixed team across lumpy demand can’t cheaply provide. The thing that makes outbound work is the same thing that makes a built team expensive when your demand swings, which is why utilization, not salary, is the number that decides this.

This is where a white-label engine reads differently on the same spreadsheet. You’re not carrying a seat. You pay for outreach when a client is active and you don’t when they’re not, per client, with no bench to feed in between.

The effect isn’t that it’s always cheaper per hour of work — a fixed team, fully utilized, can be efficient. The effect is that you stop paying for the gaps. Your cost tracks your revenue instead of running ahead of it, and you can take on a client’s outbound the week they ask instead of the quarter after you finish hiring.

What you give up is real and worth naming. You don’t own the capability, you’re renting it, and the quality of the work is someone else’s to maintain while your brand is on it either way. The diligence you’d otherwise spend on hiring goes into choosing the partner instead.

Don’t take a figure from a guide like this one. Plug in your own three numbers below — the math runs live, and nothing here is our data. The example values are just that: replace them with yours.

That idle-cost line is the one nobody puts on the salary comparison, and it’s the one that decides this. If it’s small next to what variable delivery would cost across the same year, build — you have the demand to feed a team. If it’s large, your demand is lumpier than the spreadsheet assumed.