Outsourced SDR Services: A Line-by-Line Breakdown of What You're Paying For

Outsourced SDR services get sold as a single monthly figure and delivered as about eleven separate activities, each with its own cost, its own owner, and its own failure mode. The figure is what buyers compare. The eleven activities are what they actually receive.

This gap is why two proposals at similar retainers can produce wildly different bills by month four, and why the cheaper one is often the expensive one. Taking the fee apart is not an exercise in haggling. It is the only way to know whether you are buying capacity, outcomes, infrastructure, or a well-designed invoice.

The Eleven Lines Behind One Number

Not every engagement has all eleven. Any engagement missing one has either absorbed it, excluded it, or quietly assigned it to you. Those three outcomes cost very different amounts, and the proposal rarely says which applies.

Sort Every Line Into One of Three Buckets

Work through the list above and force each line into a category.

Included. The vendor absorbs it inside the retainer. Fine, provided you know it is happening. Included data and included mailboxes both have real cost, so a retainer that absorbs them is either thinner on labour than you assumed or running on cheaper inputs than you assumed.

Pass-through. Billed to you at what the vendor pays. This is the healthiest arrangement for anything consumable, because your interests align: neither party profits from burning credits. Ask for the receipts, not a summary line. A vendor passing through data costs at cost will show you the invoice without hesitating.

Marked up. The vendor buys at one price and bills at another. Sometimes reasonable, since procurement and management have real value. Only reasonable when disclosed. An undisclosed markup on mailbox seats creates a vendor who benefits from a larger sending pool than your volume needs, which is a bad incentive to introduce into a deliverability decision.

The sorting exercise matters more than the totals. A proposal you cannot sort is a proposal where the economics are deliberately unreadable.

The Three Costs No Proposal Contains

Your own hours. Approvals, product training, objection walkthroughs, list reviews, CRM access, weekly calls, and answering the questions a new team asks in its first eight weeks. This is real payroll spent on the engagement. Estimate it honestly during selection, because a vendor that needs six hours of your week is meaningfully more expensive than one that needs one.

Replacement. Meetings get rejected, prospects no-show, and some booked calls turn out to be the wrong company entirely. Under most contracts the vendor replaces these. Replacement is not free to you: it consumes calendar slots, rep attention, and pipeline weeks. Price the engagement on meetings your sales team accepts, not on meetings that appeared.

Exit. The cost of leaving is set on the day you sign. If domains sit in the vendor's registrar, mailboxes in the vendor's tenant, sequence history in the vendor's platform, and suppression lists in a spreadsheet the vendor exports, then cancelling means rebuilding sender reputation from zero and re-learning what already worked. That rebuild has a price, and it belongs in the comparison.

Turning the Fee Into a Comparable Unit

Retainer comparison is close to meaningless because the boundaries differ. Cost per booked meeting is worse, because it rewards whoever writes the loosest definition of a meeting.

Build one denominator and apply it to every vendor: a meeting with an agreed company profile, an accepted job title, a relevant problem or active initiative, attendance, and formal acceptance by your sales team. Then compute total monthly outlay, including pass-throughs, internal hours, and performance fees, divided by sales-accepted meetings.

Run the same calculation at three volumes. Some models look strong at low volume and stop improving, because the fee is mostly management. Others need scale before the per-meeting figure becomes competitive, because the fee is mostly infrastructure. Knowing where your intended volume sits on each curve tells you more than any case study will.

What a Setup Fee Should Buy

Setup fees are defensible and often correct. The test is what exists afterward that did not exist before, and whose name it is in.

A good setup fee produces registered domains in your account, mailboxes in a tenant you administer, a verified and segmented contact base, a documented ICP definition, messaging variants with the reasoning recorded, CRM fields and routing rules, and a suppression list. Every one of those survives the relationship ending.

A poor setup fee pays for onboarding into the vendor's system: their sending pool, their platform, their data licence, their playbook. When the contract ends you hand it all back and start again. Our position is blunt on this. Paying to build assets you keep is investment. Paying for access to assets you rent is a deposit you will not get back.

A Reasonable Structure

Itemised retainer covering labour and management. Consumables passed through at cost with receipts attached. A setup fee tied to a named list of assets in your accounts. A performance component only where the meeting definition is written down and enforced. Software either in your accounts or clearly identified as the vendor's licence.

None of this makes an engagement cheap. It makes it legible, which is the property that determines whether you can tell a good month from a bad one before the quarter ends.

Want Outbound Priced Like a System You Own?

We build the data, sending infrastructure, sequencing, reply handling, and CRM workflow inside your accounts, itemise what the work costs, and operate it against a meeting definition your sales team signs off on. What gets built stays with you, which is the only way outbound spend compounds instead of resetting.

Book your free pilot →