The Modern SDR Playbook

Fatal Mistake #1: Random Activity Without Strategy

SDRs are sending emails, making calls, tracking activity in the CRM—but there's no clear ICP, no messaging framework, and no process for iteration. It's just... activity.

The result? SDRs burn through lists, prospects don't respond, and nobody can figure out what's working because nothing is consistent enough to measure.

Fatal Mistake #2: Wrong Tools for Your Stage

Early-stage teams either:

• Overspend on enterprise tools they don't need
• Underspend on tools that actually drive output

The result? Either hemorrhaging cash on underutilized tools, or SDRs spending 80% of their time on manual work that could be automated.

Fatal Mistake #3: No Process for Iteration

A sequence was launched 6 months ago. It's... fine. 2-3% reply rate. But it hasn't been touched since. Same templates, same personas, no testing, no analysis.

The result? Plateau at mediocre performance. Competitors who iterate weekly 10x past you.

What You'll Learn in This Playbook

This playbook provides frameworks and processes for building a repeatable outbound motion:

• Tool stack selection criteria at every budget level
• ICP definition framework with template worksheets
• Messaging structure templates for emails and calls
• Metrics benchmarks for every stage
• Objection handling frameworks (not scripts)
• 90-day implementation roadmap from zero to pipeline

Let's get started.

The 3 Tiers of SDR Tool Stacks

There are three distinct tiers, each optimized for different stages and budgets:

• Budget Tier ($150-250/mo): Bootstrapped or pre-seed teams testing outbound for the first time
• Growth Tier ($400-600/mo): Series A teams scaling efficiently without overspending
• Scale Tier ($700-1,000/mo): Series B+ or AI-native teams that want maximum leverage

Budget Tier: $150-250/mo

Who this is for: Pre-seed or bootstrapped companies. Testing outbound for the first time and need to prove ROI before investing heavily.

The philosophy: Free/cheap tools can get you to 12-15 meetings/month—enough to validate ICP and messaging.

Category Breakdown

Total: $150-250/month

Expected Output

With 1-2 SDRs using this stack:

• 500-750 emails/week per SDR
• 50-100 dials/week per SDR
• 12-18 meetings/month total

Growth Tier: $400-600/mo

Who this is for: Series A companies with product-market fit. Need to scale efficiently without enterprise pricing.

The philosophy: New-gen tools give you 80% of enterprise capability at 20% of the cost. AI-assisted workflows, better data quality, parallel dialing.

Category Breakdown

Total: $541-1,067/month (varies by headcount)

Expected Output

With 2-3 SDRs using this stack:

• 1,000-1,500 emails/week per SDR
• 100-150 dials/week per SDR
• 20-30 meetings/month total

Scale Tier: $700-1,000/mo

Who this is for: Series B+ or AI-native companies that want maximum leverage. Goal: 1-2 SDRs performing like 10.

The philosophy: AI handles 80% of manual work (research, email writing, inbound qualification). Humans focus only on high-value activities.

Category Breakdown

Total: $777-1,150/month

Expected Output

With 1-2 SDRs using this stack:

• 2,000+ AI-generated emails/week
• 150-200 high-quality dials/week (warm leads only)
• 40-60 meetings/month total

Tool Selection Framework

Use this decision matrix when evaluating tools:

Layer 1: Firmographics

Define observable company attributes:

• Industry: [Your vertical] (e.g., B2B SaaS, Dev Tools, Data Platforms)
• ARR: [Revenue range] (e.g., $3M-$20M for Series A/B)
• Employees: [Headcount range] (e.g., 20-150 for post-PMF scaling)
• Funding: [Stage] (e.g., Series A/B or equivalent bootstrapped revenue)
• Geography: [Markets you serve] (e.g., North America, EMEA)

Layer 2: Technographics

Define tech stack signals that indicate fit:

• CRM: [Platforms that indicate your ICP] (e.g., HubSpot/Attio = SMB/mid-market, Salesforce = enterprise)
• Hosting: [Infrastructure preferences] (e.g., AWS/GCP = cloud-native, on-prem = traditional)
• Collaboration: [Tools used] (e.g., Slack/Notion = modern, email-centric = traditional)
• Customer Type: [Who they sell to] (e.g., developers, data teams, technical buyers)

Layer 3: Buyer Personas

Define decision-makers and influencers:

Primary Persona Template

Common Persona Patterns:

• Economic Buyer: VP/Director level, controls budget, measures ROI
• Champion: Manager/IC level, uses the tool daily, advocates internally
• Influencer: Ops/Enablement, evaluates tools, provides recommendations

Layer 4: Pain Signals

Define observable triggers that indicate buying intent:

Signal Categories

• Funding Events: Recent funding announcement (creates urgency to scale)
• Hiring Signals: Job postings for [relevant roles] (indicates growth/gaps)
• Leadership Changes: New [persona] hired (building new systems)
• Public Statements: Social posts about [relevant challenges]
• Technology Changes: Recently adopted [complementary tool]

Layer 5: Anti-ICP (Disqualifiers)

Define who to actively avoid:

• Too Large: [Size threshold where you lose] (e.g., F500 = too slow, too many stakeholders)
• Too Early: [Stage criteria] (e.g., pre-seed with no revenue = not ready)
• Too Mature: [Threshold where they don't need you] (e.g., Series C+ with full team in place)
• Wrong Industry: [Verticals you can't serve] (e.g., highly regulated = slow procurement)
• Tech Mismatch: [Stack signals that indicate bad fit]

ICP Definition Template (Fill-in-the-Blank)

Testing Your ICP

Use this framework to validate your ICP definition:

The 10/100 Test

1. Build a list of 100 companies that fit your ICP criteria
2. Manually research 10 of them (their tech stack, recent activity, pain points)
3. Ask: "Would I pay to meet with their [persona]?"
4. If <7 out of 10 are strong yes → your ICP is too broad
5. If 9-10 are strong yes → your ICP is well-defined

The Pain-Before-Solution Framework

Prospects don't care about your product. They care about their problems. The messaging structure:

1. Identify the pain your product solves (be specific)
2. Reference that pain in your messaging (first, not last)
3. Hint at the solution without explaining your product

Bad Structure (Feature-First)

Why this fails:

• Leads with "us" not "them"
• No acknowledgment of prospect's situation
• Asks for time before establishing relevance

Good Structure (Pain-First)

Why this works:

• Leads with their pain (relevant immediately)
• Uses specifics/numbers (makes it concrete)
• Hints at solution (creates curiosity)
• Low-friction ask (15-min call, not "demo")

The 3 Message Types (Based on Awareness Stage)

Type 1: Problem Aware (Actively Looking)

When to use: Prospect knows they have a problem, actively seeking solutions

Type 2: Problem Unaware (Has Problem, Doesn't Know It's Solvable)

When to use: Prospect has the problem but doesn't realize there's a better way

Type 3: Trigger Event (Something Just Happened)

When to use: Recent event (funding, hire, product launch) creates urgency

Subject Line Framework

The Formula: 3-5 words, specific to their situation, creates curiosity (not announcement)

Message Personalization Framework

Personalization isn't mentioning their company name. It's demonstrating you understand their specific situation.

3 Levels of Personalization

• Level 1 (Basic): Company name, role, industry [Everyone does this - table stakes]
• Level 2 (Contextual): Recent event, tech stack, team size [Shows you did research]
• Level 3 (Insight): Specific pain based on observable data [Proves you understand their world]

Example Progression:

• Level 1: "I noticed you work at [Company] in [Industry]"
• Level 2: "Saw [Company] raised Series A and is scaling the sales team"
• Level 3: "Most Series A SaaS companies scaling from 5→15 reps hit the same pipeline gap—you're hiring AEs faster than SDRs can generate meetings, creating a 6-month lag"

Pain Discovery Worksheet

Use this framework to identify and articulate pain points for your messaging:

The 7-Touch Cadence Framework

Research shows 7-12 touches drive maximum response. Here's the structure:

Channel-Specific Strategies

Email Touches (Days 0, 4, 10, 21)

Structure Rules:

• Keep under 100 words (75 ideal)
• One clear CTA per email
• Subject line must work independently (recipients didn't see previous emails)
• Each email addresses different angle of same pain

Phone Touches (Day 7)

Voicemail Structure:

LinkedIn Touches (Days 2, 14)

Day 2 (Silent View): View their profile. No message. Creates awareness in their notifications.

Day 14 (Connection Request):

Sequence Content Variation

Each touch must provide NEW information or angle. Here's the framework:

Touch 1 (Day 0): Problem Identification

• Angle: "Here's a problem you might have"
• Content: Observable pain + impact
• CTA: "Worth exploring?"

Touch 3 (Day 4): Value-Add

• Angle: "Here's something useful regardless of whether we work together"
• Content: Link to resource, insight, data point
• CTA: "Thought this might be relevant"

Touch 5 (Day 10): Social Proof

• Angle: "Here's how others solved this"
• Content: Brief case reference (no pitch)
• CTA: "Happy to share details if relevant"

Touch 7 (Day 21): Break-Up

• Angle: "I'll stop bothering you"
• Content: Acknowledgment this might not be relevant now
• CTA: "Let me know if timing changes"

Cadence Timing Framework

Standard Spacing:

• Touch 1 → Touch 2: 2 days
• Touch 2 → Touch 3: 2 days
• Touch 3 → Touch 4: 3 days
• Touch 4 → Touch 5: 3 days
• Touch 5 → Touch 6: 4 days
• Touch 6 → Touch 7: 7 days

Timing Considerations:

• Skip weekends (no touches on Sat/Sun)
• Best send times: Tuesday-Thursday, 8-10am or 2-4pm in prospect's timezone
• Avoid Monday mornings (inbox overload) and Friday afternoons (mentally checked out)
• If targeting enterprise: avoid month-end, quarter-end (busy with internal meetings)

Sequence Variants by Persona

Adjust cadence structure based on seniority:

C-Level/VP (Harder to Reach)

• Extend to 10-12 touches over 6 weeks
• Add more phone attempts (3-4 total)
• Increase value-add ratio (more insights, fewer asks)
• Reference business outcomes, not features

Director/Manager (Responsive)

• Standard 7-touch over 3 weeks
• Balance of email and phone
• Mix of pain and tactical value

Individual Contributor (Evaluation Role)

• Shorter 5-touch over 2 weeks
• Heavier email, lighter phone
• More product-focused (they evaluate tools)

Sequence Design Worksheet

The 8 Core Metrics

Red Flags in Your Metrics

🚩 Open Rate <30%

Problem: Deliverability issues or bad subject lines
Diagnosis: Check spam score, domain reputation, subject line length
Fix: Warm up email domains, reduce send volume, A/B test subject lines

🚩 Reply Rate <2%

Problem: Wrong ICP or generic messaging
Diagnosis: Review who you're targeting vs. who responds
Fix: Narrow targeting criteria, add personalization, test pain-focused copy

🚩 Positive Reply Rate <25% of Total Replies

Problem: Too broad targeting (getting "not interested" replies)
Diagnosis: Most replies are "not a fit" or "wrong timing"
Fix: Tighten ICP criteria, improve pre-qualification signals

🚩 Show Rate <60%

Problem: Booking unqualified meetings
Diagnosis: Meetings getting cancelled/no-showed frequently
Fix: Add qualification questions before booking, send reminder emails 24hr before

Weekly Review Framework

Conduct this review every Friday with each SDR:

Metric Relationships (What to Watch)

Metrics don't exist in isolation. Watch these relationships:

The 3-Step Objection Framework

Most people panic when they hear an objection. Use this systematic approach:

1. Acknowledge: Show you heard them (don't argue or steamroll)
2. Reframe: Shift perspective or add context
3. Advance: Move to next step (don't re-pitch)

The 10 Most Common Objections (Framework Approach)

Objection Type 1: "We're not interested"

What it really means: "You haven't proven relevance yet"

Objection Type 2: "We don't have budget"

What it really means: "I don't see the ROI / This isn't a priority"

Objection Type 3: "Send me some information"

What it really means: "I'm not sure this is relevant / Brush-off"

Objection Type 4: "We're already working with [Competitor]"

What it really means: "Why should I consider switching / adding another vendor?"

Objection Type 5: "We're too early for this"

What it really means: "I don't think we're ready / This feels premature"

Objection Type 6: "We're handling this in-house"

What it really means: "We have resources dedicated to this already"

Objection Type 7: "I need to talk to my team first"

What it really means: "I'm not the only decision-maker / Need buy-in"

Objection Type 8: "We tried this before and it didn't work"

What it really means: "I'm skeptical because of past failure"

Objection Type 9: "Call me back in 3-6 months"

What it really means: "Not a priority now / Brush-off"

Objection Type 10: "How is this different from [Competitor]?"

What it really means: "Prove you're worth evaluating"

The "Hidden No" Detection Framework

Sometimes prospects say "yes" to a meeting but have no intention of buying. Use this to uncover the hidden no:

Objection Tracking Framework

Track objections to identify patterns:

If one objection appears >50% of the time: Your targeting or messaging needs adjustment. You're reaching the wrong people or failing to establish relevance.

Common Failure Modes (And How to Avoid Them)

🚩 Failure Mode #1: Analysis Paralysis

What it looks like: Spending 4 weeks researching tools, building perfect templates, never actually sending anything.

The fix: Launch with "good enough" by Week 2. Iteration beats perfection. Your first email will never be your best email.

🚩 Failure Mode #2: No Iteration Process

What it looks like: Send 1,000 emails, get 2% reply rate, keep doing the same thing for 3 months.

The fix: Weekly metric reviews. A/B test one variable per week. Change ICP, messaging, or timing every 2 weeks based on data.

🚩 Failure Mode #3: Wrong ICP

What it looks like: Getting replies, but they're all "not interested" or "wrong timing."

The fix: Tighten ICP. If <30% of replies are positive, your targeting is too broad. Narrow the criteria.

🚩 Failure Mode #4: Tool Overinvestment

What it looks like: Spending $2K/month on tools before proving the model works.

The fix: Start with Budget Tier. Prove 12-15 meetings/month is achievable. Then upgrade tools as needed.

Success Criteria by Month

Weekly Iteration Checklist

Run this process every Friday: