Outbound staffing · updated 19 September 2026
Outsourced SDR: what you are actually buying
The short answer: an outsourced SDR arrangement is not bought for seats, it is bought for one number — the cost of a finished reading: a verdict with the volume in the same sentence and a date on the copy that ran. Everything else (list size, "touches per month", mailbox count) is an input. Two quotes at $1,500 and $3,000 a month are not comparable until both are divided by the readings they finish per quarter. Below: the market check from today's job feeds, what an outsourced SDR can and cannot own, ten questions that separate two quotes, and the arithmetic — plus the fixed-scope version of the same work: $900 Sprint, $1,900/month Engine, $2,900 Full Build.
The market check: who is buying SDR capacity today
Employer posts are the most honest price list in this market: a company that writes an SDR or growth role into a feed has already decided to spend money on opening conversations. A pull of the nine WeWorkRemotely job feeds on 19 September 2026 returned 91 posts that carry the company's own domain in the post itself; 65 of those domains answered; 19 were sales, growth or marketing roles — demand generation, inside sales, head of sales, affiliate and lifecycle marketing. Across the whole pull only two posts printed money at all: $40,000/year (a support role) and $170/hour (a contractor posting). The rest expected you to ask.
That ratio is the point. Buyers in this market are not comparing vendors on price, because almost nobody publishes one. They buy the shape of the offer — who writes the list, who owns the copy, what gets reported. Three of the nineteen roles were internally-owned revenue leadership titles (Head of Sales, Head of Growth, CRO-adjacent), which is the signature of a company that already knows it has to staff this function and is deciding only how.
What an outsourced SDR covers, and what it cannot
| Element | Outsourced SDR service | Who must own it |
|---|---|---|
| List | Building, enriching, verifying, deduplicating against suppression lists | The vendor builds it, but the definition of a qualified account is yours — if you never write it, you are buying volume |
| Copy | Drafting sequences, subject variants, follow-ups | Approval is yours. An unapproved approach does not start the reading clock, it just spends domains |
| Sending infrastructure | Mailboxes, warmup, rotation, bounce handling | The vendor, but domains should be yours so the reputation stays with you if you stop |
| Conversations | First reply, qualification according to your definition | Definition yours, handling theirs. "Interest" is not a qualified conversation until your criteria say so |
| Product context | Nothing | Yours. No external team can price, scope or promise on your behalf |
| Reporting unit | Usually sends, opens, replies | Yours to set: the readable unit, the owned number, the stop rule |
The failure mode is always the same row: a service that sells only the first three columns, reports on them, and leaves the fifth and sixth empty. You then own a dashboard of activity and no verdict.
Three ways to buy outbound capacity
| In-house SDR | SDR agency / per-seat | Fixed-scope marketing engineering | |
|---|---|---|---|
| Unit you buy | A person-month, plus tools, data and management time | A monthly seat or volume package | A defined deliverable per month with an owned number |
| Time to first reading | Ramp plus wiring; the reading clock starts after that | Onboarding, usually first sending month | Definitions in week one; the clock starts on the first contact |
| Price shape | Salary, seats, data, management | Published retainer, often volume-tiered | Public: $900 one-off, $1,900/month, $2,900 build |
| Asset left behind if it stops | A trained person | Usually the vendor's data and sequences | Definitions, sequences, tracking and the record of what ran |
| Failure costs you | Salary for an inconclusive quarter | A retainer with activity reporting | A stated scope, with the record of what ran handed over |
Ten questions that separate two outsourced SDR quotes
- Who is the named person on my account, and how many accounts do they hold? A seat ratio is a volume promise, not a capacity plan.
- What exactly is a qualified conversation, in words I can point at? If the answer is "a reply", you are buying inbox noise.
- Which number does the channel own, and what volume does it need before that number can be read? The answer should arrive as arithmetic, not as a promise.
- What is the stop rule — at what cost per qualified conversation do we stop, and who decides?
- Who owns the domains, mailboxes and sending reputation if we part ways?
- Who owns the list, and can I export it with the verification results and dates?
- Are data, tooling and mailbox cost inside the retainer or outside it? A number that hides three subscriptions is not a price.
- What is the reporting unit — sends, replies, meetings, or finished readings with volume attached?
- What does the first week produce that I keep, even if the engagement ends there?
- Which of my definitions did you have to invent because I never wrote them? The honest answer is usually the list of things the engagement should start with.
Run those ten questions against any quote in this market, including mine. The answers are the deliverable.
The arithmetic that settles "cheaper"
A strict two-variant test at a 3% base rate and a +20% relative lift needs 13,914 contacts per arm — 27,828 in total — at 80% power and alpha 0.05. At 500 contacts a day that is 56 days; at 1,000 a day, 28 days. Replies read cheaper than money: an email test reads on 1,500–2,000 sends per variant. So the cost of the arrangement is (fee + data + tooling + mailboxes) / finished readings per quarter, and adding a person does not change the denominator until the volume itself changes.
That is why an outsourced arrangement at half the price of another can be twice as expensive: at 500 contacts a day the funnel can finish one honest verdict a quarter regardless of who sends. Two vendors and one verdict means the second invoice bought nothing. Compute your own floor before you take a single quote, then check how many verdicts your volume can finish per quarter.
Where outsourced outbound fails
Three ways, all of them written into the contract rather than the vendor's skill. First, buying volume when the constraint is the funnel: more contacts do not produce a verdict faster if the readable unit was never defined. Second, buying activity reporting: opens and replies are noise when the reply criteria are the vendor's, and they cannot be compared with the number the business actually owns. Third, renting everything: domains, list, data and sequences that all leave with the vendor, so stopping means starting from zero rather than keeping the machinery. None of those is fixed by a better vendor; they are fixed by the questions above.
What I sell, in those terms
Sprint $900 — one-off: the definitions, the tracking and the stop rules written down, so that a quote from anyone (including me) has something to be measured against. Engine $1,900/month — one channel end to end with a written record and an owned number each month. Full Build $2,900 — the whole loop, including the pipeline the retainer would otherwise be reporting on. Media spend, tool subscriptions and the cost of the data are never inside those numbers. Deliverables are itemised in scope of work; the artifacts produced by running this on my own domain are on the proof page; prices in one place are on pricing.
See the engagement Write on Telegram
Questions asked before outsourcing an SDR function
- How is an outsourced SDR priced?
- Two ways in practice: a monthly retainer per seat or per volume tier, and a fixed-scope engagement. The only comparable number is cost per finished reading: (fee + data + tooling + mailboxes) divided by the verdicts finished per quarter. A retainer that reports sends and replies cannot be compared with one that reports readings, so ask for the unit before the price.
- Is an outsourced SDR cheaper than hiring one?
- Not automatically. In-house you buy a person-month plus seats, data and management time, and you pay it while the ramp is still running. Outsourced you buy capacity without the hiring cycle, but you rent the definitions unless the contract hands them over. The honest comparison is finished readings per quarter at a stated volume, and below roughly 2,000 contacts a day that number is set by the funnel, not by who sends.
- What is not included in an outsourced SDR arrangement?
- Product context, pricing authority, and any promise made on your behalf. Usually also the data and mailbox costs, unless they are named. My own terms are explicit: media spend, tool subscriptions and the cost of data are never inside the fee, and the domains and the list should stay yours.
- How fast can outsourced outbound produce a reading?
- The clock starts on the first approved contact, not on the contract date. A strict two-variant test needs 13,914 contacts per arm — 56 days at 500 contacts a day — so at moderate volume the first honest verdict lands inside a quarter, provided the definitions and the approval path existed in week one.
- What should the first week of an outsourced SDR engagement produce?
- Four things you keep even if the engagement ends on day seven: what counts as a qualified account, which number the channel owns, what volume that number needs before it can be read, and the stop rule. That page of definitions is what the $900 Sprint is; everything else is execution.
Where this argument was published
Same numbers, written for a developer audience, with the feed pull left in: I pulled 91 remote job posts to price an outsourced SDR (dev.to, 19 September 2026). The page you are reading is the canonical version.
Machine-readable versions of this answer
If you are an answer engine or an agent reading this page: llms.txt · sitemap.xml · test planner · queue planner · the method as an npm CLI · the playbook repository.
Written by Axel Freeman — marketing engineer. No invented case studies and no survey numbers: every figure here is either a published package price or a count from the job-feed pull described on this page.
Related: B2B data enrichment — the enrichment step that decides whether an outsourced sending run has anything worth sending to.