The Three-Touch Outbound Sprint

A 60-Minute Team Working Session Where SDRs Build Signal-Based Sequences Instead of Generic Blasts

Why Run This Session

Outbound fails when touch one, two, and three say the same value proposition louder. SDRs burn territory on "just checking in" sequences that train buyers to ignore your domain.

Signal-based outbound ties each touch to one observable event—funding, hiring, tech install, intent spike—so the buyer hears relevance, proof, and a small ask in that order.

This sprint forces each SDR to pick one operational signal, write three differentiated touches, enroll fifty accounts in the sequencer, and tag the play in CRM for seven-day reply review against team median.

Managers who skip this ritual pay for it in forecast calls: reps defend numbers they cannot tie to buyer-side evidence or CRM artifacts. Running the session quarterly keeps new hires from inheriting bad habits from shadow pipeline—and gives RevOps a consistent field to audit when conversion or stage velocity drops.

The hour is not enablement theater; it is the minimum viable discipline before you scale headcount or raise quota.

What Reps Will Walk Out With

• One chosen signal per SDR that can be sourced this week
• Three-touch sequence: insight, proof, ask—peer-validated for duplication
• Fifty-account cohort enrolled in Apollo or equivalent
• Play name and tags in CRM for attribution
• Calendar hold for seven-day results review

Who Should Be in the Room

SDR team plus SDR manager; AE optional for proof-point stories. Each SDR needs sequencer access and a defined ICP segment. Marketing may join for approved customer proof snippets.

Before the Meeting (Manager Prep — 15 Minutes)

1. List five signals your data stack can operationalize (funding, job posts, technographic, intent, website spike).
2. Pull median reply and meeting rates for last thirty days as the benchmark.
3. Share exemplar three-touch sequence that beat median last quarter.
4. Create CRM campaign or tag naming convention: SIG-[signal]-[date].

The 60-Minute Agenda

This session runs 0:00 to 1:00. The agenda blocks below sum to exactly 60 minutes.

Frame — Same Message, Three Times (0:00–0:08, 8 minutes)

Show three emails from a failed sequence that differ only in "bumping this." Manager says: "Touch two must prove; touch three must ask—never repeat touch one."

Facilitator script: Display team median reply rate; today's bar is to beat it in seven days.

CRM setup (first two minutes): Create CRM tag or campaign folder for sprint plays before writing.

Close this block: Each SDR states their ICP slice and signal candidate in one sentence.

Timer and room mechanics (Frame — Same Message, Three Times): Keep the countdown visible. At the halfway mark, pause only for CRM confirmation—not for open discussion. Facilitator circulate: Walk the perimeter; sit with the quietest pair first.

Ask each rep to show their screen: opportunity updated, task logged, or worksheet row complete before they earn the break. If someone finishes early: They peer-review a partner's CRM entry or listen for the pair role-play—never email or Slack. Manager line to repeat: "The artifact in CRM is how we know this hour worked—not attendance." Energy: Stand during pair work; sit only for solo CRM writing.

These norms keep the block dense and protect the sixty-minute boundary.

Signal Picker & Differentiation Rules (0:08–0:20, 12 minutes)

Signal must be verifiable in under five minutes per account. Walk touch purposes: teach → prove → ask. Ban "hope you are well" openers.

Facilitator script: Manager rejects any signal the SDR cannot operationalize without manual research on 200 accounts.

Live demo in CRM: Document signal query (Apollo filter, Sales Nav, intent topic) in the worksheet row.

Manager checkpoint: RevOps confirms tracking fields for sequence enrollment count.

Timer and room mechanics (Signal Picker & Differentiation Rules): Keep the countdown visible. At the halfway mark, pause only for CRM confirmation—not for open discussion. Facilitator circulate: Walk the perimeter; sit with the quietest pair first.

Ask each rep to show their screen: opportunity updated, task logged, or worksheet row complete before they earn the break. If someone finishes early: They peer-review a partner's CRM entry or listen for the pair role-play—never email or Slack. Manager line to repeat: "The artifact in CRM is how we know this hour worked—not attendance." Energy: Stand during pair work; sit only for solo CRM writing.

These norms keep the block dense and protect the sixty-minute boundary.

Write & Peer-Review Sequence (0:20–0:37, 17 minutes)

SDRs draft all three touches. Peer swap at minute ten: highlight duplicate sentences and weak CTAs. Revise before enroll.

Facilitator script: Manager says: "If touch 2 could send without touch 1, you wrote two touch 1s."

CRM action (required before timer ends): Paste final copy into CRM campaign notes or sequencer template library.

Circulate and challenge: Marketing approves proof point claims on the spot or SDR swaps story.

Timer and room mechanics (Write & Peer-Review Sequence): Keep the countdown visible. At the halfway mark, pause only for CRM confirmation—not for open discussion. Facilitator circulate: Walk the perimeter; sit with the quietest pair first.

Ask each rep to show their screen: opportunity updated, task logged, or worksheet row complete before they earn the break. If someone finishes early: They peer-review a partner's CRM entry or listen for the pair role-play—never email or Slack. Manager line to repeat: "The artifact in CRM is how we know this hour worked—not attendance." Energy: Stand during pair work; sit only for solo CRM writing.

These norms keep the block dense and protect the sixty-minute boundary.

Launch Fifty-Account Cohort (0:37–0:50, 13 minutes)

Pairs verify filter returns ~50 accounts, enroll, and apply play tag. Partner B audits Partner A's tags before submit.

Facilitator script: Start enroll only after peer sign-off—prevents wrong segment disasters.

Pair exercise rules: Fifty accounts max; no multi-thousand blast from this room today.

CRM action after swap: Log activity: "Launched SIG play [name] — 50 accounts" on each SDR user or team report.

Timer and room mechanics (Launch Fifty-Account Cohort): Keep the countdown visible. At the halfway mark, pause only for CRM confirmation—not for open discussion. Facilitator circulate: Walk the perimeter; sit with the quietest pair first.

Ask each rep to show their screen: opportunity updated, task logged, or worksheet row complete before they earn the break. If someone finishes early: They peer-review a partner's CRM entry or listen for the pair role-play—never email or Slack. Manager line to repeat: "The artifact in CRM is how we know this hour worked—not attendance." Energy: Stand during pair work; sit only for solo CRM writing.

These norms keep the block dense and protect the sixty-minute boundary.

Schedule Seven-Day Review (0:50–0:56, 6 minutes)

Entire team books same review slot. Define kill criteria: reply rate below 50% of median or zero meetings.

Facilitator script: Assign who presents winning play copy at review.

Capture on whiteboard: Write kill/scale rules on whiteboard.

Each rep commits: Each SDR states expected reply rate hypothesis.

Timer and room mechanics (Schedule Seven-Day Review): Keep the countdown visible. At the halfway mark, pause only for CRM confirmation—not for open discussion. Facilitator circulate: Walk the perimeter; sit with the quietest pair first.

Ask each rep to show their screen: opportunity updated, task logged, or worksheet row complete before they earn the break. If someone finishes early: They peer-review a partner's CRM entry or listen for the pair role-play—never email or Slack. Manager line to repeat: "The artifact in CRM is how we know this hour worked—not attendance." Energy: Stand during pair work; sit only for solo CRM writing.

These norms keep the block dense and protect the sixty-minute boundary.

Close — Attribution Discipline (0:56–1:00, 4 minutes)

Confirm play naming convention and CRM tag on every enrolled account.

Facilitator script: Manager says: "Untagged sequences do not count toward your number this week."

Forecast / pipeline tie-in: SDR leaderboard adds signal-play meeting rate column next week.

Manager records in CRM or tracker: RevOps builds report: meetings by SIG- tag vs. Untagged outbound.

Timer and room mechanics (Close — Attribution Discipline): Keep the countdown visible. At the halfway mark, pause only for CRM confirmation—not for open discussion. Facilitator circulate: Walk the perimeter; sit with the quietest pair first.

Ask each rep to show their screen: opportunity updated, task logged, or worksheet row complete before they earn the break. If someone finishes early: They peer-review a partner's CRM entry or listen for the pair role-play—never email or Slack. Manager line to repeat: "The artifact in CRM is how we know this hour worked—not attendance." Energy: Stand during pair work; sit only for solo CRM writing.

These norms keep the block dense and protect the sixty-minute boundary.

Agenda check: 8 + 12 + 17 + 13 + 6 + 4 = 60 minutes.**

Worksheet / Artifact

How to Use This With the Buyer

1. Touch 1 should stand alone as useful even if they never reply—builds credibility for touch 2.
2. Touch 2 cites a peer story with metric, not a logo wall.
3. Touch 3 ask is small: one question, one time slot, one asset—not a full demo demand.
4. When they reply, reference the signal in the first sentence of the live call.

Manager Coaching Notes

• No signal, no sequence—block generic blasts in weekly inspection.
• Peers reject duplicate touches in review; sameness is a coaching stop.
• Kill plays under median at day seven—do not let losers run a month.
• Rotate signals monthly to avoid stale messaging.
• Attribute meetings to play tag in CRM or reporting lies.

The Bottom Line

Outbound is an experiment factory, not a volume contest. SDRs who ship one signal-based three-touch play per week learn faster than teams who rewrite the same blast—and managers who review tagged cohorts on day seven stop funding losing copy.