Outbound Sales Engine Playbook
Outbound Sales Engine Playbook
Outbound is no longer a numbers game. It is 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. The rep edits for nuance. The reply rate goes from 2 percent to 12 percent. 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 | AI Leverage |
|---|---|---|
| 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 cannot. |
| Reference Density | Buyers talk to each other. One closed deal warms ten. |
| Specific Pain Points | A message about labor scheduling in QSR converts; a message about productivity does not. |
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 highest-leverage outbound activity is account selection. A great message to a wrong-fit account is wasted. A mediocre message to a high-intent account converts. Front-load the research.
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: Knowledge Architecture).
Vertical Example: Toast's BDR team built its target list off restaurant trade-association directories plus job-posting signals for "kitchen manager" hires. ServiceTitan ranked HVAC and plumbing shops by truck count pulled from public licensing data. Both teams started with research, not sequences.
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. AI lets you produce relevance 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: Anatomy of a Skill).
Vertical Example: Procore's outbound reps open every Tier A email with a reference to a specific job site, project bid, or public permit. Veeva's life-sciences team references the prospect's most recent FDA filing. The signal is: I did the work before I asked for your time.
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. Separate outbound domain, slow warmup, conservative daily limits, weekly deliverability review. Stop sending the moment open rates dip below 30 percent.
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: Operating Scorecard).
Vertical Example: Vagaro and Mindbody both run dedicated outbound domains separated from their corporate domain, with 4-week warmup cycles before any new sender goes live. Neither team has ever had a deliverability incident take down outbound for more than a week.
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 percent rolling 7-day open rate |
⚡ Execution Kit Gate: The remaining plays, the Operating Scorecard, the 30-day activation path, deliverability runbook, and the 14-day sequence templates unlock with the Execution Kit.
Play 4: Run the Daily Rep Rhythm as a Command Stack
The Move: Every SDR runs the same daily command stack: research the day's Tier A list, draft personalized opens, execute the cadence, log call notes, hand off SQLs. The rhythm is non-negotiable and timeboxed.
Why It Works: Reps drift. Without a daily command stack they 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: ranks the next day's Tier A list, drafts personalization tokens, surfaces trigger events. The rep starts the day with a curated queue, not a blank screen (see Module 3: Command Stacking).
Vertical Example: ServiceTitan's SDR org runs a 5-block daily stack: 7am list review, 8am-10am email and LinkedIn, 10am-12pm cold calls, 1pm-3pm meeting prep and discovery, 3pm-4pm CRM hygiene and handoff. Activity quality stays high because the structure does the discipline.
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: trigger event, qualification notes, decision-makers, observed pain, competitor mentions, 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: Toast's SDR-to-AE handoff template was templatized after their AE team complained the original notes were too thin. Within a quarter, first-meeting conversion to opportunity rose materially because every AE walked in prepared with the same brief structure.
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 percent or higher | SDR manager |
| Connect Rate on Cold Calls | Leading | Weekly | 10 percent or higher | SDR |
| SQLs Per Rep Per Week | Lagging | Weekly | 5 or higher | SDR manager |
| SQL to Opportunity Conversion | Lagging | Monthly | 40 percent or higher | AE team + RevOps |
Link this to the Module 4 Operating Scorecard template. The discipline is the constraint, 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 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 percent 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: 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. The full 90-day extension lives in the Execution Kit.
- 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: Skills Layer (account research, message drafting, objection handling skills)
- Module 2: Context OS (account graph and trigger event monitoring)
- Module 3: Operations Playbook (daily SDR command stack)
- Module 4: Measurement System (outbound Operating Scorecard)
- Module 5: AI-Native Org (SDR hiring sequence)
- Templates: 14-day sequence library, deliverability runbook, SQL handoff brief, daily SDR command stack (all in the Execution Kit)