SDR-led outbound

Once a company has scaled past founder-led outbound, cold email shifts to an SDR team. The playbook changes: volume goes up, personalization per email goes down, operational rigor goes way up. This is how SDR-led cold email actually runs.

Team structure

Typical SDR team running cold email:

• 1 SDR manager
• 4-12 SDRs
• 1 RevOps / cold email operator (tools, lists, infrastructure)
• 1 data analyst (for mid-to-large orgs)

Smaller orgs combine roles; larger split further (list builder, email writer, reply handler all distinct).

Quota reality

• 150-300 emails per SDR per day
• Across a 10-SDR team: 1500-3000 emails/day
• 50-100 meetings booked per SDR per month (target)
• Conversion meetings → opportunities: 30-50%

SDRs spend most of their day on list research, reply handling, and meeting booking, not on writing emails. Writing is a once-a-week batched task.

The ownership model

Option A: SDR owns list + copy + sends + replies

Full ownership per rep. Works for small teams. Breaks down at scale (copy quality varies, no shared learnings).

Option B: Centralized copy, SDR-specific lists

RevOps or marketing writes the emails. SDRs get assigned lists and send the approved copy. Standard for mid-to-large teams.

Option C: Full specialization

List builder → copy team → send + reply specialists → AE handoff. Enterprise model.

Infrastructure for scale

• 50-150 sending mailboxes
• 10-30 sending domains
• Instantly / Smartlead / Salesloft / Outreach as core tool
• Apollo / ZoomInfo + Clay for data
• CRM (Salesforce) for pipeline
• Call tracking if phone is in the mix

The copy reality at scale

SDR-led cold email can't do deep per-prospect personalization at 300/day. Compromise:

• Heavily templated body with 2-3 merge fields
• AI-generated first lines (per-prospect) via Clay
• Segmented templates (different copy per ICP segment)

Reply rates are lower per email than founder-led (1-3% vs 3-8%) but total volume produces more meetings.

The cadence discipline

SDR teams need rigid cadences or the system collapses:

• Monday AM: list review, ICP validation
• Monday-Friday: 150-300 emails/day sent on schedule
• Continuous reply handling (within 24 hours)
• Friday: weekly performance review, copy iteration

Common failure modes

SDR burnout

Cold email is psychologically tough. Rep turnover in SDR roles is notoriously high (12-18 months). Mitigate with career progression, training, manageable quotas.

Copy decay

Same email template for 6 months → reply rate drops 50%. Mandate monthly copy refresh.

Deliverability death spiral

No one owns deliverability → sender reputation degrades → replies drop → team panics → volume increases → reputation worsens. Need dedicated RevOps ownership.

Bad handoffs

SDR books meeting, AE doesn't read notes, prospect feels dropped. Standardize handoff process: structured notes, briefing time, joint AE+SDR calls for critical prospects.

Measurement

Weekly per-SDR metrics:

• Emails sent
• Positive reply rate
• Meetings booked
• Meetings held (shows reliability of bookings)
• Meetings → opportunities
• Opportunities → closed (lagging but matters)

Compensation

• SDR base: $45K-$75K depending on region
• Variable: $15K-$30K tied to meetings booked + meetings held
• Accelerators on meetings that convert to closed deals

Variable should weight meetings-held and meetings-converting, not just bookings (prevents booking junk meetings to hit quota).

What to do with this

• Weight SDR comp toward held + converted meetings, not just booked, pure booking quotas produce junk meetings that burn AE time
• Set up Lead Gen Forms or meeting auto-booking so SDR doesn't manually schedule, reduces the friction that kills reply-to-meeting conversion
• Cap SDR at 1 campaign per week maximum, more than that fragments attention and quality drops fast
• Review call recordings weekly with each SDR, copy + cadence tweaks come from what prospects actually say on the first call
• Don't launch SDR-led until you have validated offer, predictable conversion, and a documented playbook, otherwise you're paying someone to replicate a broken process