Outbound Sales Engine Playbook
Outbound Sales Engine Playbook
Outbound isn't a numbers game anymore. It's a relevance system powered by industry context and AI augmentation. This playbook gives you the operating model to build an outbound engine that produces qualified pipeline weekly in a defined vertical, without the spray-and-pray habits that destroy domains and brand.
1. The Shift: From Volume to Relevance at Scale
The classic outbound motion sent 1,000 emails to get 10 meetings. Reps lived in Salesloft, copy-pasted templates, and burned through total addressable market in 90 days. Open rates collapsed, domains got penalized, and the next rep started over.
The AI-native motion inverts the equation. Reps send 50 deeply-personalized touches per day, sourced from a Context graph that knows every account's tech stack, trigger events, competitor relationships, and decision-makers. AI drafts the first pass and the rep edits for nuance, and the reply rate climbs well past what the old motion got. The engine runs without burning the TAM.
Outbound for vertical SaaS is now a research function with a sequencing layer attached, not the other way around.
2. The Operating System: Research, Sequence, Instrument
| Layer | What It Does | Where AI Helps |
|---|---|---|
| Skills | Account research, message drafting, objection handling, call openers | Skill packs per persona and per vertical (Module 1) |
| Context | Firmographics, tech signals, trigger events, competitive landscape | Account knowledge nodes refreshed weekly (Module 2) |
| Operations | Cadence, sequence performance, channel mix, deliverability | Command stacks for daily SDR rhythm (Module 3) |
The Vertical Outbound Advantage
| Lever | Why It Matters in Vertical SaaS |
|---|---|
| Defined Universe | You know exactly who to target. ICP error margin is small. |
| Industry Credibility | Domain language opens doors that generic copy can't. |
| Reference Density | Buyers talk to each other. One closed deal warms ten. |
| Specific Pain Points | A message about labor scheduling in QSR converts, and a message about productivity doesn't. |
3. The Plays
Play 1: Build the Target Account Graph
The Move: Compile 500 to 1,000 ICP accounts into a living Context graph. Every account carries tier (A, B, C), firmographics, tech signals, trigger events, decision-makers, and reference paths.
Why It Works: The single outbound activity with the most riding on it is account selection. A great message to a wrong-fit account is wasted, and a mediocre message to a high-intent account converts, so don't leave the research for later.
AI Integration: Use the account graph to auto-rank tier and surface trigger events daily (funding, hiring, product launches, exec moves). Reps work from a ranked daily list, not a static spreadsheet (see Module 2, The Context OS).
Vertical Example: Picture a restaurant-software team building its target list from trade-association directories and from job postings for a kitchen manager hire, which often signals a new location. A field-service software team ranks HVAC and plumbing shops by fleet size from public licensing records, and they start with research, not sequences. On your own team, compare meetings booked per 100 accounts for a pilot pod working the research-built list against the rest of the team, over one quarter.
Account Tiering:
| Tier | Criteria | Touch Cadence |
|---|---|---|
| Tier A | Perfect ICP fit, active trigger event, warm path available | Personalized 1:1, weekly touches across 3 channels |
| Tier B | Strong ICP fit, no active trigger | Semi-custom sequence, biweekly touches |
| Tier C | ICP-adjacent, monitor for triggers | Nurture sequence only, monthly value drops |
Play 2: Write Sequences That Read Like Research, Not Marketing
The Move: Build a 14-day, multi-channel sequence where every touch references something specific to the account. No template should be sendable without 30 seconds of account research embedded.
Why It Works: The reason outbound reply rates collapsed is that buyers can spot a sequence in two seconds. Relevance is the only thing that beats the pattern-match, and AI lets you produce it at scale.
AI Integration: Generate first-draft personalization tokens from the account Context node (trigger event, observed pain, competitor mention). Rep reviews, adjusts tone, sends. Track which token types correlate with reply rate and feed back into the Skill (see Module 1, The Skills Layer).
Vertical Example: A construction-software rep can open every Tier A email with a reference to a specific job site, a project bid, or a public permit, and a life-sciences rep can reference the prospect's most recent regulatory filing. The signal is that I did the work before I asked for your time. On your own team, compare reply rate on Tier A emails that cite a live account signal against Tier A emails sent without one, over one month of sends.
14-Day Multi-Channel Sequence:
| Day | Channel | Touch Type | Personalization Anchor |
|---|---|---|---|
| Day 1 | Problem framing | Specific trigger event or observation | |
| Day 3 | Connect, no message | Profile mention if relevant | |
| Day 5 | Value drop with proof point | Named peer or competitor outcome | |
| Day 7 | First message | Reference shared connection or post | |
| Day 10 | Phone | Live call attempt | Tied to email engagement signals |
| Day 12 | Reframe with case study | Industry sub-segment specific | |
| Day 14 | Breakup with resource | Open-handed offer of value |
Play 3: Protect Deliverability Like a Production Asset
The Move: Treat your sending domain as critical infrastructure, with a separate outbound domain, a slow warmup, conservative daily limits, and a weekly deliverability review. Stop sending the moment open rates dip below 30%.
Why It Works: Most outbound engines die from domain damage, not bad messaging. A burned domain takes 90 days to recover and costs every rep on the team. Discipline at the infra layer is the highest-ROI outbound work nobody does.
AI Integration: Monitor send/reply/bounce/spam metrics in your Operating Scorecard. Trigger automated alerts when any metric breaches threshold. Pause sequences automatically before damage compounds (see Module 4, The Measurement System).
Vertical Example: A booking-software company can run outbound from a dedicated domain, separate from its corporate domain, with a 4-week warmup before any new sender goes live. On your own team, track open rate for each new sender week by week through the first month, and compare it with the senders that have been live longest.
Deliverability Discipline:
| Practice | Standard |
|---|---|
| Outbound Domain | Separate from corporate (e.g. mail.company.com) |
| SPF / DKIM / DMARC | All three configured before sender goes live |
| Warmup Period | 4 weeks minimum, capped at 20 to 30 sends per day in week 1 |
| Daily Limit (Warmed) | 100 to 150 per sender, never exceed |
| First Email | Text only, zero images, one link maximum |
| Open-Rate Floor | Pause sender below 30% rolling 7-day open rate |
Play 4: Run the Daily Rep Rhythm as a Command Stack
The Move: Every SDR runs the same daily command stack, which covers researching the day's Tier A list, drafting personalized opens, executing the cadence, logging call notes, and handing off SQLs. The rhythm is non-negotiable and timeboxed.
Why It Works: Reps drift, and without a daily command stack they'd default to easy work (LinkedIn scrolling, list cleanup) and avoid hard work (cold calls, custom opens). Codifying the rhythm protects activity quality.
AI Integration: AI runs the prep work overnight, ranking the next day's Tier A list, drafting personalization tokens, and surfacing trigger events. The rep starts the day with a curated queue, not a blank screen (see Module 3, The Operations Playbook).
Vertical Example: A field-service software SDR team can run the same five-block day every morning, starting with list review, then email and LinkedIn, then cold calls, then meeting prep and discovery, and finally CRM cleanup and handoff. On your own team, compare reply rate per rep between reps who run a fixed block schedule and reps who set their own day, over one quarter.
The 5-Block SDR Day:
| Block | Activity | Time |
|---|---|---|
| Block 1: Prep | Review AI-ranked Tier A list, validate triggers, edit drafts | 60 min |
| Block 2: Async Touches | Email and LinkedIn cadence execution | 120 min |
| Block 3: Phone Block | Cold calls, warm callbacks | 120 min |
| Block 4: Meetings + Discovery | First meetings, qualification calls | 90 min |
| Block 5: Hygiene + Handoff | CRM updates, SQL handoff, tomorrow's prep | 60 min |
Play 5: Hand Off SQLs With Context, Not Just Calendar Invites
The Move: Every SQL handoff to an AE includes a structured briefing covering the trigger event, qualification notes, decision-makers, observed pain, competitor mentions, and the AE objective for the call. No bare calendar invites.
Why It Works: AEs win deals they walk into prepared. A weak handoff turns a great meeting into a re-discovery slog and signals to the AE that SDR work is low quality. A strong handoff is how SDR-to-AE trust gets built.
AI Integration: Auto-generate the handoff brief from the account Context node plus the SDR call transcript. AE reviews in 90 seconds before the meeting. The Skill for handoff briefs gets refined based on AE win rate (see Module 1).
Vertical Example: At a restaurant-software team, the AEs say the SDR notes are too thin. The team replaces free-form notes with one brief template that every AE reads before the first meeting. On your own team, compare first-meeting-to-opportunity conversion for SQLs handed off with the brief against SQLs handed off with free-form notes, over two quarters.
SQL Handoff Brief Structure:
| Field | Content |
|---|---|
| Trigger Event | What put this account in motion now |
| Qualification Status | BANT or MEDDICC summary, with gaps flagged |
| Decision Map | Named buyer, named influencer, named blocker |
| Observed Pain | Specific quotes from the discovery call |
| Competitive Context | Incumbent, evaluation set, switching cost |
| AE Objective | Primary outcome the AE should drive in the first meeting |
4. The Operating Scorecard
Five metrics. Leading first, lagging second. Reviewed weekly by the SDR manager with the team.
| Metric | Type | Cadence | Target | Owner |
|---|---|---|---|---|
| Personalized Touches Per Rep Per Day | Leading | Daily | 40 to 60 | SDR |
| Email Reply Rate (7-day rolling) | Leading | Weekly | 8% or higher | SDR manager |
| Connect Rate on Cold Calls | Leading | Weekly | 10% or higher | SDR |
| SQLs Per Rep Per Week | Lagging | Weekly | 5 or higher | SDR manager |
| SQL to Opportunity Conversion | Lagging | Monthly | 40% or higher | AE team + RevOps |
Link this to Module 4, The Measurement System. The constraint is the discipline, not the metrics.
5. Hiring and Org Implications
The outbound function only works once the founder-led motion and first 50 have produced a repeatable message. Hiring SDRs before that point doesn't work, because it hands a script with no proof to a rep with no credibility.
| Stage | Hire | Retire | Comp Shift |
|---|---|---|---|
| Pre 50 Customers | No SDRs. Founder runs outbound personally. | Any SDR conversation. | Founder equity. |
| 50 to 150 Customers | First SDR. Industry-experienced. Pair with founder for first 90 days. | Founder spending more than 25% of week on outbound. | Base plus per-SQL variable. |
| 150 plus Customers | Second and third SDRs. First SDR manager promoted from within. | One-person SDR org with no pipeline visibility for the team. | Standard SDR OTE with team kicker. |
See Module 5, The AI-Native Org, for hiring sequence, comp structures, and ramp expectations.
6. 30-Day Activation Path
A focused 30-day sprint to install the outbound engine.
- Day 1 to 5: Stand up the account graph (Module 2). 500 accounts minimum, tiered.
- Day 6 to 10: Set up dedicated outbound domain, SPF/DKIM/DMARC, begin warmup.
- Day 11 to 15: Draft Tier A sequence with AI personalization tokens. Test on 25 accounts.
- Day 16 to 20: Codify the 5-block SDR day. Run it personally for one week before hiring.
- Day 21 to 25: Launch full Tier A cadence at warmup-safe volume. Daily scorecard review.
- Day 26 to 30: First weekly Operating Scorecard meeting. Lock cadence. Document handoff brief.
7. Resources
- Module 1: The Skills Layer
- Module 2: The Context OS
- Module 3: The Operations Playbook
- Module 4: The Measurement System
- Module 5: The AI-Native Org
- The worksheet version of this playbook is the Notion template in the download box on this page.