| name | follow-up-sequencer |
| description | When managing SDR or sales sequences where you need to route prospect interactions through deterministic branches based on reply type, apply standa... |
Follow-Up Sequencer
When to activate
When managing SDR or sales sequences where you need to route prospect interactions through deterministic branches based on reply type, apply standardized follow-up cadences, and make re-engagement decisions. Trigger: (1) initial outreach email sent and tracked, (2) reply detected (positive, negative, or null), or (3) re-engagement decision point at 60+ day mark. Use this to replace ad-hoc follow-up logic and ensure consistent timing, messaging, and objection handling across pipeline volume.
When NOT to use
Do not use this for: single-threaded one-off interactions, internal team communication, post-meeting nurture sequences (those use different logic — see post-discovery workflows), or "always active" broadcast campaigns. Do not apply sequencing logic to warm inbound leads or SQLs already qualified by sales development. Do not compress timelines or skip branches because "we want faster conversion" — branch timing is calibrated for deliverability, engagement, and objection conviction.
Instructions
Core Sequencing Logic: Three Branches
Branch A: Positive Reply (Action Required Same Day)
When a prospect replies with interest, engagement signal, or question:
-
Exit the sequence immediately — remove prospect from automated follow-ups.
-
Classify reply temperature (hot/warm/cold):
- HOT: Explicit meeting request, budget mention, urgent pain signal, executive tone, specific use case question → meeting intent is clear.
- WARM: Interested but conditional ("Tell me more about X", "How does this compare to Y?", "Send me info"), timeline unspecified, or testing your knowledge → needs clarification call or value demo.
- COLD: Polite no ("thanks but not right now"), objection stated, misdirect ("talk to my team"), or generic courtesy → classify objection branch (Branch C).
-
Same-day response cadence:
- HOT reply: Respond within 2 hours. Message: confirm meeting time, remove friction (calendar link, Zoom), restate their problem in your words, one-liner on mutual benefit. Aim for book-within-48-hours. Do not over-explain or pitch.
- WARM reply: Respond within 4 hours. Message: answer their specific question in 1–2 sentences, add one proof point (case study snippet, stat, or feature demo), soft CTA ("I'll send a quick Loom" or "let's jump on a call to explore"). Schedule discovery call for 3–7 days out.
-
Post-reply nurture:
- HOT → Meeting booked: Move to meeting prep workflow. Pause follow-up sequencing until post-meeting.
- WARM → Follow-up in 30 days: If no meeting booked after initial discovery call or response, re-engage in exactly 30 days with specific context note: "Last time we spoke, you asked about [X]. Here's what I've learned..." This keeps the conversation warm without churn.
Branch B: No Reply (Multi-Touch, Cadenced Decline)
When prospect does not reply within the monitoring window:
Day 0: Initial email sent (Email 1: Problem recognition hook).
Day 3: Send Email 2 — Pain Framing.
- Premise: Your Day 0 email reached inbox but didn't trigger reply (low engagement threshold).
- Message: Shift from "you should care" to "here's what's breaking for companies like you." Use data, problem statement, or process gap tied to their company/role. Introduce social proof (customer testimonial, trend, stat). Keep subject line different from Day 0 (avoid "follow-up" language).
- CTA: Softer than Day 0 — "If this resonates, let's chat" rather than "let's schedule a call."
Day 7: Send Email 3 — Delegation Ask.
- Premise: Two touches, no reply. Prospect may be interested but not the right person, or too busy.
- Message: "I may have the wrong contact—who on your team owns [process/budget/decision] for [specific outcome]?" Removes you from the equation and provides an easy out (forward to peer).
- CTA: None. Expect either forwarding, misdirect, or continued silence.
Day 12: Send Email 4 — Break-Up (Final Sequence Email).
- Premise: Four touches over 12 days signals low intent or poor fit.
- Message: Non-salesy, genuine-sounding goodbye. "I'll step back—doesn't seem like the right time. If [specific trigger] changes (new hire, budget review, technical debt spike), I'd love to reconnect."
- CTA: No ask. Close loop gracefully.
After Day 12: Park prospect for 60 days.
- Set a task to not email. Move prospect to "cold" segment in CRM.
- Set re-engagement checkpoint at Day 72 (60 days + 12 days elapsed).
Branch C: Negative Reply (Objection Routing)
When prospect explicitly says no, objects, or signals negative intent:
-
Classify objection:
- "No thanks" / "Not interested": Polite deflection, low conviction signal.
- "We're already using [competitor]": Legitimate alternative in place.
- "Our budget is frozen": Timing objection (may unfreeze).
- "Not a priority right now": Low urgency, not active pain.
- "You're not the right fit": Explicit mismatch on product/market.
- "Reached out at wrong time/person": Routing issue, not product issue.
-
One reframe attempt only:
- Respond within 24 hours.
- Pick the objection's core and reframe: "That makes sense you're using [competitor]. We work differently because [key difference tied to their use case]."
- Add proof: customer quote from someone in same situation, or specific outcome difference.
- Do not argue. Do not pitch harder.
- Single CTA: "No pressure—if [specific condition changes], I'll send you what I've learned. Sound okay?"
-
Final decision after reframe:
- Prospect agrees to re-engage condition: Set task for re-engagement checkpoint (60 days).
- Prospect rejects reframe or ignores it: Retire prospect for 6 months.
- Tag in CRM with reason (competing solution, budget, not a fit, timing, etc.).
- Set task: "Revisit if [trigger condition]" (e.g., "if Series B announced", "if replace [competitor]", "if hire sales leader").
- Do not contact until that trigger fires or at 6-month mark (whichever is first).
Re-engagement Rules
Apply these rules only for prospects in the 60+ day park or 6-month retirement phase:
-
Minimum elapsed time: 60 days since last touch (Branch B) or 6 months (Branch C). Do not compress.
-
New signal requirement — One of:
- Funding announcement (Series A, B, or growth round).
- Job change (prospect promoted, moved to different company, or role shifted to higher seniority).
- Technology change (switched platforms, adopted new stack, or announced new initiative).
- Public news (expansion, new office, new product, strategic pivot, acquisition, leadership change).
- Inbound behavior (visited website, opened marketing email, clicked LinkedIn content).
-
Message structure (reference the gap):
- Opener: "We spoke a few months ago about [their stated problem]. I noticed you [new signal]. Thought this might be timely."
- Premise: Different angle than original sequence. If Day 0 was "speed problem," re-engage with "scale problem" or "team efficiency." Do not replay original pitch.
- Proof: New customer win, product feature, or benchmark that directly addresses the new signal.
- CTA: "Curious if this changes the conversation. Can we grab 20 minutes?" (Lower friction than original ask.)
-
Cadence after re-engagement: Treat as new sequence. Apply Branch B logic (Day 3, Day 7, Day 12) only if re-engagement email gets no reply. Do not reuse old email copy.
Sequence Performance Diagnostics
Track these metrics at the sequence level (not campaign-wide) to identify bottlenecks and fix them:
Diagnostic 1: Open Rate < 30%
Problem: Inbox placement or subject line fatigue.
- Fix 1 (Deliverability): Check DKIM/SPF/DMARC alignment. Verify email domain isn't on spam lists (check MXToolbox). Rotate sending IP or domain if rate persists.
- Fix 2 (Subject line): A/B test subject lines in next send. Lower performs if:
- All caps or too many punctuation marks (triggers spam filters).
- Generic ("Follow-up", "Quick question") vs. personalized ("I saw you hired 3 engineers—here's what that means for Infra").
- No curiosity gap or relevance to role.
Target: 40–50% open rate is strong for cold outreach; 30% is minimum viable.
Diagnostic 2: Open Rate > 30%, Reply Rate < 2%
Problem: Engagement isn't converting to response. Content or CTA unclear.
-
Fix 1 (Content): Is the value proposition clear in first 2 lines? Prospect should answer "why is this about me?" in < 10 seconds. Rewrite to:
- Lead with their problem (not your solution).
- Use 1–2 metrics from their industry (shows research).
- Keep body to 100 words max.
-
Fix 2 (CTA): Is the ask too large? "Let's schedule a 30-minute discovery call" has higher friction than "Can I ask you one quick question?" Reduce ask size:
- Day 0: "Quick question" or "One thought."
- Day 3: "Does this resonate?"
- Day 7: "Who should I talk to?"
Target: 2–4% reply rate for cold B2B sequences. Below 1% signals broken content or list quality.
Diagnostic 3: Reply Rate > 2%, Meeting Rate < 30%
Problem: Replies exist but aren't converting to meetings. Discovery call or reply CTA is unclear.
-
Fix 1 (Reply message): When you respond to a positive reply, is the CTA explicit? Vague ("Let's talk soon") vs. explicit ("I have Tuesday 2pm and Thursday 10am available—which works for you?"). Use calendar links (Calendly, Chili Piper). Reduce friction.
-
Fix 2 (Discovery call scripting): Are your discovery calls exploring their problem or pitching? Audit calls for: opening with muted mic/camera? Talking first? Not asking about timeline? Replace with:
- "What brought you to reply?"
- "If I could wave a magic wand on [problem], what would it look like?"
- "When were you hoping to have this solved?"
Target: 30–50% of replies should convert to meetings (depends on reply temperature and your qualification).
Multi-Channel Sequence Overlay
Email alone has 30–40% open rates. Stack channels for 2–3x meeting conversion:
Day 0: Email 1 (Problem hook)
↓
Day 1: LinkedIn view their profile + no message yet (passive signal)
↓
Day 3: Email 2 (Pain framing)
↓
Day 5: LinkedIn direct message (not connection request)
Message: "Saw your profile—quick thought on [their recent job/company move/content]."
Do NOT resend email copy.
↓
Day 7: Email 3 (Delegation ask)
↓
Day 7 (same day): Phone call attempt (optional, high-touch)
Leave voicemail if no answer: "Hi [name], this is [your name] from [company]. I had a thought about [problem]—call me back at [number]. Sending you an email too."
↓
Day 12: Email 4 (Break-up)
Channel-specific rules:
- Email: Authority, context, proof. Use for problem statement and reframes.
- LinkedIn message: Curiosity, brief, personalized to their public activity. "I noticed you wrote about [topic]—we're seeing [related trend] with [similar company]."
- Phone: Warmth, urgency, discovery. Use voicemail to prime email followup. If person picks up, ask, don't pitch. "Is this a bad time?" Listen first.
Multi-channel benefit: If email bounces or gets caught in spam, LinkedIn or phone creates backup touchpoint. If they're responsive to email but not phone, you've learned preference.
Daily Task Structure for Managing Multiple Sequences
To operationalize multiple active sequences (50–100 prospects) without manual drift:
Morning Review (10 min)
- Check replies from yesterday's sends (Email 1, 2, 3, 4 across active sequences).
- Classify each reply: Hot/Warm/Cold or Objection.
- Create tasks for same-day responses (Hot replies get 2-hour timer, Warm replies get 4-hour timer).
- Flag any new positive signals (funding, job change) for re-engagement prospects in park.
Sending Block (per cadence)
- Day 0 sends: Batch 20–30 Email 1 sends in morning block (8–9am). Set timer for Day 3 email (set to auto-send or remind).
- Day 3 sends: Auto-send Email 2 to non-responders from Day 0 batch. Manual review: any opens that didn't reply yet? (Possible bottleneck.)
- Day 7 sends: Auto-send Email 3. Manual check: anyone who replied between Day 3–7? Exit them from sequence, move to Branch A workflow.
- Day 12 sends: Auto-send Email 4. Review: anyone moving to Branch C (objections)? Route them to reframe workflow.
Afternoon Review (10 min)
- Check for new replies to today's sends (less common but possible).
- Log any re-engagement signals (funding, hires, etc.). Tag for 60-day re-engagement list.
- Confirm next day's send tasks are queued (or set auto-send).
Weekly Review (20 min)
- Metrics check: Open rate, reply rate, meeting rate for week's sequences. Any diagnostics triggered (< 30% open, < 2% reply, < 30% meeting conversion)?
- Park list review: Any 60-day or 6-month parked prospects ready for re-engagement? Check for new signals.
- Objection triage: Anyone in objection reframe? Check if they've replied to reframe (within 5 days). If not, move to 6-month retirement, tag reason.
Tools/Automation
- CRM task automation: Set rules so Day 3, 7, 12 emails trigger automatically unless prospect replied (exit sequence on reply).
- Slack/email reminders: Set daily 10am summary: "20 prospects need same-day responses. 5 sequences hit diagnostics. 3 ready for re-engagement."
- Spreadsheet or Airtable: Track each sequence: send date, opens, replies, meeting booked, reason for park/retirement.
Example
Real Scenario: Enterprise SaaS SDR Managing 60 Active Prospects
Company: Data integration platform (enterprise). SDR: Alex. Prospect pool: 60 mid-market DevOps leaders (VP/Director level).
Week 1: Initial Outreach (Day 0 batch)
Alex sends 20 Email 1s across two days:
- Subject: "Engineering debt at [company]?"
- Body: "I noticed [company] expanded your data engineering team 2x in the last year. Lots of companies we work with hit a scaling wall when they do. Curious if it's on your roadmap."
- CTA: "One quick question—is data pipeline complexity a problem for your team?"
Day 0 metrics: 12 of 20 opens (60% open rate). ✅ Good.
Day 3: Pain Framing (Branch B, no reply cohort)
Alex sends Email 2 to the 8 who didn't reply:
- Subject: "Re: Engineering debt at [company]?" (different subject than Email 1).
- Body: "Following up—I'm seeing a trend. Companies scaling from 1 to 2 ETL tools usually end up with a brittle data platform. Here's what it costs (case study): mean time to recovery is 6+ hours when failures happen. Two questions: (1) How's your current setup scaling? (2) Who owns that on your team?"
- CTA: "Appreciate a quick response—or point me to the right person if that's you."
Observation: 2 of 8 opens Email 2, neither replies. 6 of 8 don't open. → Deliverability issue flagged. (Check domain DKIM; Email 1 likely went to spam.)
Day 3: Branch A (Positive reply)
Of the 12 who opened Email 1:
- 1 prospect replies: "We're evaluating solutions. Can you send a demo?"
- 1 prospect replies: "Thanks but we're not in market right now."
Prospect A (positive): HOT. Reply within 2 hours.
- Message: "Great—let's schedule 30 min next week. I'll send a Loom of what your use case looks like. Tuesday 2pm or Thursday 10am?" (Explicit CTA, calendar link.)
- Outcome: Prospect books Thursday meeting. Exit sequence, move to meeting prep.
Prospect B (negative): COLD. Move to Branch C (objection).
- Reframe attempt within 24 hours: "That makes sense—most teams evaluate when they hit a breaking point (usually when pipelines start failing in production). If that changes, I'll send you a benchmark on what's typical for companies at your scale."
- Set re-engagement condition: "If you hire for this or start an evaluation, let me know."
- Outcome: Prospect doesn't reply. Move to 6-month retirement. Tag: "Not in market." Checkpoint: 6 months or when Series B announced.
Day 7: Delegation Ask (Branch B, continued)
Email 3 sent to remaining 6 (who didn't open Email 2):
- Subject: "Quick question—who owns data architecture at [company]?"
- Body: "I may have the wrong person. If you're not the right fit, can you forward to whoever owns data pipeline architecture?"
- CTA: None.
Outcome: 1 prospect replies, forwarding to colleague (Data Engineering Lead). Add new contact to sequence, restart at Day 0.
Day 12: Break-Up
Email 4 sent to 5 remaining non-responders:
- Subject: "No pressure—stepping back"
- Body: "I'll wrap up here. Doesn't seem like the right time. If you hit a data platform breaking point or have a migration coming up, I'd love to reconnect. Good luck with the team scaling."
- CTA: None.
Outcome: All 5 moved to 60-day park. Set re-engagement checkpoint: Day 72.
Summary after Day 12 batch:
| Outcome | Count | Status |
|---|
| Meeting booked | 1 | Active (meeting prep) |
| Moved to objection reframe | 1 | 6-month park |
| Forwarded (new contact) | 1 | Restarted sequence |
| Parked 60 days | 5 | Task set for Day 72 |
| Total engaged | 8 / 20 | 40% engagement |
Week 4: Re-engagement (Day 72 checkpoint)
Alex checks 5 parked prospects for new signals:
-
Prospect C: Funding round announced (Series B, $40M). New signal detected.
- Re-engagement email: "We spoke a few weeks ago about your data scaling. I noticed the Series B—congratulations. Now's usually when data platform decisions accelerate. Different take on the problem: here's how 3 companies at your new scale handled their data stack. Can we grab 20 min?"
- CTA: Calendar link.
-
Prospects D, E: No new signals. Continue park for another 30 days.
Outcome: Prospect C opens re-engagement email, replies with interest. Exit sequence, move to meeting prep. Prospects D, E remain parked.
Diagnostics Applied (Week 4 review)
Alex noticed:
- Open rate Day 0: 60% (good). Open rate Day 3: 25% (bad). → Fix: Deliverability issue (domain DKIM wasn't aligned). Added DMARC record.
- Reply rate overall: 3 replies out of 20 Day 0 sends = 15% (strong for cold B2B data engineering).
- Meeting rate from replies: 2 meetings out of 3 replies = 67% (high because HOT replies were qualified fast, objection was parked early).
Adjustments for next batch:
- Re-align DKIM before sending next 20 Email 1s.
- A/B test subject lines (current "Engineering debt" is working; test "Team scaling hit a wall?" on next cohort).
- Keep delegation ask (Day 7) as-is—it's generating forwarding.
This scenario shows how the three branches (A: hot/warm exit and nurture; B: no-reply cadence; C: objection park) operate simultaneously across 20 prospects over 12 days, with metrics diagnostics triggering real adjustments.
