What are the first 10 concrete steps to build an SDR team from scratch in 2027?

Why the first two hires decide everything

The most common failure in building an SDR team from scratch is hiring three or four reps at once because a board deck said "build pipeline." A cold-start SDR org has no playbook, no objection library, no known conversion rates, and no one who has personally booked a meeting into the specific ICP. Adding four unmanaged juniors to that vacuum produces four different interpretations of the job, none of which can be diagnosed when they fail.

Hire two. Two is the smallest number that gives you signal separation. With one rep you cannot distinguish "the rep is bad" from "the motion is bad" — every result is confounded. With two, you get a crude control: if both reps hit similar activity volumes and both produce near-zero meetings, the problem is upstream (list quality, ICP, message, offer). If one produces four meetings a month and the other produces zero on identical inputs, the problem is execution and coachable. That single diagnostic distinction is worth more in month three than two extra bodies.

Two reps is also the largest number a founder or first sales leader can genuinely coach while still selling. Real SDR coaching is not a weekly one-on-one; it is listening to recorded calls, reading sent emails, and rewriting them line by line. Budget roughly 3–5 hours per rep per week for the first 90 days. At four reps that is most of a full-time job, and whoever is doing it is usually also the person carrying the closing number. Something gives, and it is always the coaching.

The sequencing consequence is that steps one through five all happen before a single job description is posted. You are not hiring people to figure out the motion. You are hiring people to run a motion you have already proven at small scale — even if "proven" means the founder personally booked eleven meetings in six weeks and can describe exactly which list, which opener, and which objection pattern produced them. That founder log becomes the first version of the playbook, and it is the single highest-leverage artifact in the entire build.

One more thing the first two hires decide: whether you are building an outbound team or a follow-up team. Those are different jobs with different candidate profiles, different tooling, and different quota math. An SDR working inbound MQLs from content and events needs speed, qualification discipline, and calendar hygiene. An SDR working cold outbound into a named account list needs research stamina, writing ability, and tolerance for a 95%+ non-response rate. Hiring an inbound-shaped person into a cold outbound seat is the most expensive mis-hire in this function, and it is almost always discovered in month four when it costs a full ramp cycle to correct.

What changes by company stage

The ten steps stay the same in order, but their content changes materially depending on where the company sits. Treating a Series B playbook as advice for a pre-revenue company is how teams burn eighteen months.

Pre-revenue and pre-product-market-fit. Do not build an SDR team. This is the honest answer and it is unpopular. If you cannot name ten customers who bought, why they bought, and what they almost bought instead, an SDR has nothing to sell. What you build instead is step one through three only: an ICP hypothesis, a founder-led outbound log, and a set of conversion numbers. The founder does 150–300 touches personally and records what happened. That is the raw material. Hiring an SDR to substitute for founder learning does not transfer the learning; it just puts a junior person between you and the market at the exact moment you most need direct contact with it.

Early revenue, roughly $1M–$5M ARR. This is the window where the first two SDRs make sense. You have a repeatable segment, at least a rough sense of deal size, and someone — founder or first AE — who has closed enough to describe the buying pattern. At this stage the SDR team is a two-person unit reporting to whoever owns revenue, with no dedicated manager, no enablement function, and a stack that is deliberately minimal. The primary goal is not pipeline volume. It is converting one person's tacit knowledge into a written, teachable process. Pipeline is the byproduct.

Scaling, roughly $5M–$20M ARR. Now the constraint shifts from "does the motion work" to "can we run it consistently across more people." This is where you add a dedicated manager — usually at the fifth or sixth rep, sometimes the fourth if the AE-to-SDR ratio is tight. The management span that actually works for SDRs is 6–8 reps; above eight, coaching degrades to status-checking. This is also where the stack gets real: you can no longer run the team on a CRM plus a sequencing tool plus spreadsheets, because you now need territory rules, routing logic, and reporting that survives someone leaving.

Post-scale, $20M+. The build-from-scratch question stops applying. You are now optimizing an existing function: specialization by segment, dedicated enablement, separate inbound and outbound pods, career ladders with defined SDR-to-AE promotion criteria. The ten steps still describe how you would stand up a new segment team or a new geography, but the company-level answer is different.

The trap in 2027 specifically is that AI tooling makes it feel cheap to skip stages. It is genuinely possible for one person plus modern research and drafting tooling to produce the outbound volume that took three people in 2022. That does not mean you can skip the proving step — it means the proving step is faster and the volume floor is higher. The teams that get burned are the ones that interpret cheap volume as permission to skip ICP validation, then send twelve thousand well-written emails to the wrong people and torch their sending domains in the process.

Stage-by-stage playbook

Here is the concrete sequence, with what "done" actually looks like at each step.

Step 1 — Write the ICP down to the account level. Not "mid-market SaaS." A list of 200–400 named companies with the specific trigger that makes them relevant: headcount band, tech stack signal, funding event, org change, regulatory deadline. If you cannot produce that list, you do not have an ICP, you have a category. Done means: a spreadsheet with company name, why-now trigger, and named target persona for at least 200 accounts.

Step 2 — Run founder-led outbound for 4–6 weeks. Whoever owns revenue personally works 150–300 accounts from that list. Every touch is logged. Every reply, including the rude ones, is saved verbatim. Done means: a documented count of touches sent, replies received, meetings booked, and a file of the actual objections people gave.

Step 3 — Convert the log into a playbook. Take what worked and write it as instructions someone else can follow: the list-building criteria, the sequence structure and cadence, three opener variants, the qualification framework you will actually use, the top eight objections with responses. Done means a document a new hire can read on day two and execute on day five.

Step 4 — Do the quota math before you write comp. Work backward from the revenue number. If the company needs $2M in new ARR next year, and average deal size is $40K, that is 50 closed deals. At a 20% opportunity-to-close rate you need 250 qualified opportunities. If 60% of SDR-booked meetings convert to accepted opportunities, that is roughly 417 meetings. Split across two ramped reps over the productive months, that is a per-rep monthly target you can sanity-check against reality. If the number comes out at 40 meetings per rep per month, your assumptions are wrong somewhere — go back and fix them, do not hire against fantasy math.

Step 5 — Pick the minimum stack. CRM, a sequencing and dialing tool, a data/enrichment source, call recording, and a calendar/routing tool. That is it. Five categories. Resist buying an intent platform, a conversation-intelligence add-on, and an AI SDR agent before you have two humans producing consistent output — you will not be able to attribute anything.

Step 6 — Write comp and hire two reps. Comp structure and the actual hiring process are detailed in the sections below.

Step 7 — Run a structured 30-day onboarding. Week one: product, ICP, and shadowing. Week two: list building and writing, with every email reviewed before send. Week three: live calling with reduced volume targets and daily call review. Week four: full activity volume, first meetings expected. Done means the rep has booked at least one meeting by day 30 and can articulate the qualification criteria without notes.

Step 8 — Instrument the funnel end to end. You need clean numbers on touches per rep, contacts reached, replies, meetings booked, meetings held, meetings accepted as opportunities, and opportunities closed. The single most common instrumentation failure is not tracking meetings *held* separately from meetings *booked* — no-show rates of 20–35% are normal and invisible if you only count bookings.

Step 9 — Install the weekly coaching rhythm. One recorded call reviewed per rep per week, line-by-line. One email sequence reviewed per rep per week. A pipeline review with the AEs so SDRs hear what happened downstream to the meetings they booked. This is non-negotiable and it is the first thing that gets dropped when things get busy.

Step 10 — Only then, scale. Add reps three and four when both original reps are consistently at or above target for two consecutive months, the playbook has been revised at least twice based on real data, and you know your cost per meeting.

Numbers that matter at each stage

Every number below should be treated as a starting assumption to be replaced by your own data within 90 days. The point is not that these are universal — it is that you need a specific number to plan against, and a wrong specific number that you correct in month two beats a vague one you never test.

Ramp time. Plan 3–4 months to full productivity for an SDR with prior experience in a comparable motion, and 5–6 months for someone new to the role. This matters enormously for the first hires because it means a January start date produces meaningful pipeline in April or May, and pipeline that closes in Q3. Every plan that assumes SDRs produce in month one is wrong, and the downstream effect is a comp plan that pays out almost nothing during ramp, which causes attrition at exactly the moment the rep was about to become useful. Guarantee or heavily draw the commission for the first two to three months.

Activity volume. In 2027, with modern research and drafting tooling, a full-time outbound SDR working a named-account list can realistically sustain 40–60 personalized touches per day across email, phone, and social, working 25–40 accounts per day in a multi-touch cadence. The old 150-dials-a-day number belongs to a spray motion into a large undifferentiated list; it is not the same job. If you are running high-volume into SMB, the numbers change and so does the personalization depth. Pick one motion. Reps who are told to do both do neither well.

Conversion benchmarks to plan against. Cold email reply rates in the low single digits are normal — 1–3% for a decent sequence into a well-built list, higher for tight ICPs with a strong trigger. Positive-reply-to-meeting-booked runs somewhere around 30–50%. Meeting-booked-to-meeting-held is where the leakage lives: expect 65–80% held. Meeting-held-to-accepted-opportunity depends entirely on how strict your qualification bar is, and 50–70% is a common band. Multiply those and you understand why the touch volume has to be what it is.

Cost per meeting. This is the number that tells you whether the team is working. Take fully loaded rep cost — salary, commission, benefits, tooling, data, and management time — divide by qualified meetings produced. A team that produces meetings at a cost that exceeds a healthy fraction of gross profit per closed deal is not a pipeline engine, it is a subsidy. Calculate it monthly starting in month four, once at least one rep is ramped.

Ratios. The AE-to-SDR ratio that works depends on deal cycle and AE capacity. A common starting point is one SDR per two AEs in a mid-market motion, moving toward 1:1 in enterprise where account research depth is higher and meeting volume per rep is lower. Do not set this ratio in the abstract — set it by asking how many qualified opportunities each AE can actually work simultaneously without dropping them.

Comp shape. SDR comp is typically 60–70% base and 30–40% variable. The variable component should be tied to qualified meetings held or opportunities accepted, not meetings booked — paying on bookings reliably produces booked meetings with unqualified people who never show. Add a small kicker on closed-won from SDR-sourced pipeline so reps care about quality downstream. Keep the plan simple enough that a rep can compute their own commission on a napkin; complexity in an SDR plan produces confusion, not motivation.

Attrition. Assume 12–24 months average tenure in seat. This is a role people leave, usually by promotion into AE or by leaving for a bigger SDR seat elsewhere. Build for it: document the promotion criteria on day one, and assume you are backfilling continuously once the team exceeds four people. A written SDR-to-AE promotion path — typically 12–18 months at or above target plus demonstrated discovery skill — is a genuine retention lever and costs nothing to write.

Decision framework for what to do next

Most of the hard calls in a from-scratch build are sequencing calls, not strategy calls. The framework below is the one to run whenever you are tempted to skip forward.

The first gate is always: has anyone at this company personally booked meetings into this ICP in the last 90 days? If no, stop and do that. No amount of hiring substitutes for it. If yes, you have raw material and can proceed to writing the playbook.

The second gate is whether the quota math survives contact with the pipeline. Run the backward calculation, and then ask whether the resulting per-rep meeting target is something the founder actually achieved during the proving period. If the founder booked six meetings a month working part-time on outbound and the plan requires each SDR to book eighteen, either the plan is wrong or you are assuming a productivity multiple you have no evidence for.

The third gate is the hiring one: do you have a manager for these people? Not a title — a person with actual calendar time to review calls and rewrite emails weekly. If nobody has 6–10 hours a week for two reps, hire one rep, not two, or delay the hire until someone does. Unmanaged SDRs do not slowly underperform; they quietly invent their own job and you find out in month five.

The fourth gate is the scale one, and it is where discipline usually breaks. The temptation at month four, with one rep doing well and one struggling, is to hire two more on the theory that you will average out. What you actually do is double the coaching load while the playbook is still unstable, and the new hires learn from a process that is about to change. Wait for both reps at target for two consecutive months. If one rep is consistently at target and one is consistently not, the correct move is to fix or replace the underperformer before adding headcount, because you have just learned that your onboarding does not reliably produce a productive rep — and hiring more people into an unreliable onboarding process scales the failure.

Where AI tooling actually helps in 2027 — and where it doesn't

The honest 2027 answer is that AI meaningfully compresses two of the ten steps and changes almost nothing about the other eight.

It compresses step one, list building and account research. What used to be a week of manual account qualification is now hours: pulling trigger signals, summarizing recent company events, and drafting a why-now hypothesis per account is genuinely faster and better than a junior person doing it by hand. Use it there aggressively.

It compresses step three's first draft, the writing. Generating sequence variants, rewriting an opener six ways, and producing objection-response drafts from your own recorded calls is real leverage. The critical constraint is that the input has to be your actual call recordings and your actual replies — generic AI-generated outbound reads as generic AI-generated outbound, and buyers in 2027 have a very well-trained filter for it.

It does not help with the things that actually determine whether the team works: whether the ICP is real, whether the quota math is honest, whether someone is coaching, and whether reps are qualifying rather than booking. Those are judgment and management problems.

The specific 2027 failure mode to avoid is deliverability collapse. Cheap volume plus loose targeting equals spam complaints, and spam complaints equal domain damage that takes months to repair. Concrete guardrails: use separate sending domains from your corporate domain, warm them for at least three to four weeks before volume, keep per-mailbox daily send volume conservative, authenticate properly with SPF, DKIM, and DMARC, and monitor bounce and complaint rates weekly with a hard stop threshold. One rep sending five hundred emails a day from the company domain can do more damage to revenue in a month than the entire team produces in a quarter.

The other failure mode is attribution fog. If you deploy an AI outbound agent alongside two human SDRs in month one, you will never know which produced what, and you will make the scaling decision on noise. Prove the human motion, get clean baseline numbers, then layer automation on top of a process you already understand.

Related questions

How long before a new SDR team produces closed revenue?

Add ramp to sales cycle. With a 3–4 month ramp and a 60–90 day sales cycle, the first SDR-sourced closed deals typically land 5–7 months after start date. Plan cash and expectations against that, not against first-meeting dates.

Should the first SDRs report to the founder or an AE?

Whoever proved the motion and has genuine weekly coaching capacity. Usually the founder or head of revenue at the first two hires. Reporting to an individual AE creates a conflict — the AE optimizes for their own pipeline, not team-wide quality.

Is it better to hire experienced SDRs or train juniors?

For the first two, prefer someone who has done outbound in a comparable motion — you need less onboarding infrastructure than you have. Juniors work well once the playbook, onboarding, and coaching rhythm exist, which is roughly hire five onward.

What should an SDR's quota be in month one?

Activity-based, not meeting-based. Touches sent, accounts researched, calls made, with meeting targets phasing in around week four and full target at month three or four. Meeting quotas during ramp produce desperate, unqualified bookings.

When do you need a dedicated SDR manager?

Around the fifth or sixth rep, sometimes the fourth. The signal is coaching quality degrading — if call reviews are being skipped or one-on-ones have become status updates, you passed the threshold already.

FAQ

How much does it cost to stand up a two-person SDR team?

Budget fully loaded rep cost including base, target variable, payroll taxes, and benefits, plus per-seat tooling across the five stack categories and a data/enrichment budget. Tooling and data typically run a few hundred to low four figures per rep per month depending on vendor and contract terms. The larger hidden cost is management time — 6–10 hours a week from someone senior — which almost never appears in the budget and is the resource most likely to be missing.

Can one person do this instead of two?

Yes, and sometimes it is the right call — specifically when coaching capacity is thin or cash is tight. The trade-off is diagnostic: with one rep you cannot separate rep performance from motion quality, so a bad quarter leaves you guessing. If you hire one, compensate by having the manager run parallel outbound personally so there is a comparison point.

What is the single most common mistake in a from-scratch build?

Hiring before the motion is proven, then blaming the reps. It shows up as three or four simultaneous hires, no written playbook, no documented objection library, and a manager who is also carrying a closing number. Every symptom that follows — low meeting volume, poor qualification, fast attrition — traces back to that one decision.

Should SDRs be paid on meetings booked or opportunities accepted?

Accepted opportunities, or meetings held with a qualification standard attached. Paying on bookings creates a direct incentive to book anyone with a calendar, which produces no-shows and unqualified discovery calls that burn AE time. A small closed-won kicker on SDR-sourced pipeline aligns the rep with what actually matters.

How do you know whether the problem is the rep or the playbook?

Compare reps on identical inputs. If both reps hit similar activity volume and both produce near-zero meetings, the problem is upstream — list, message, offer, or ICP. If output diverges sharply on the same list and same sequence, it is execution and coachable. This is precisely why the first hire count is two rather than one.

Does an AI SDR agent replace any of these steps?

Not the ones that matter. It accelerates account research and first-draft copy meaningfully. It does not validate your ICP, do your quota math, coach anyone, or enforce qualification. Deploying one before you have clean human baseline numbers also destroys your ability to attribute results, which makes the scaling decision guesswork.

Sources

• https://blog.hubspot.com/sales — HubSpot Sales Blog: prospecting, cadence, and SDR role guidance
• https://www.saastr.com/ — SaaStr: SaaS go-to-market benchmarks, ramp, and sales hiring commentary
• https://www.gartner.com/en/sales — Gartner Sales research on B2B buying behavior and seller productivity
• https://openviewpartners.com/blog/ — OpenView: SaaS metrics, sales efficiency, and expansion benchmarks
• https://www.bridgegroupinc.com/blog — The Bridge Group: SDR metrics research, ramp times, quota, and tenure
• https://www.salesforce.com/resources/research-reports/state-of-sales/ — Salesforce State of Sales research reports
• https://support.google.com/a/answer/81126 — Google Workspace bulk sender guidelines (SPF, DKIM, DMARC, complaint rates)
• https://senders.yahooinc.com/best-practices/ — Yahoo sender best practices for bulk email authentication and reputation
• https://www.gong.io/resources/ — Gong Labs: conversation-data research on outreach and discovery calls
• https://hbr.org/topic/subject/sales — Harvard Business Review sales topic archive

Related on PULSE

• How to write an SDR comp plan that rewards qualified pipeline
• SDR-to-AE promotion criteria: what to require before the move
• Cold email deliverability: warming domains and protecting sender reputation
• Quota capacity planning: working backward from an ARR target
• Inbound vs outbound SDR roles — why the profiles are different hires
• What to instrument in an outbound funnel before you scale headcount