| name | cold-email-sequence |
| description | - You are building a 4-email outbound campaign with specific timing (Day 0, 3, 7, 12) |
Cold Email Sequence
When to activate
- You are building a 4-email outbound campaign with specific timing (Day 0, 3, 7, 12)
- You need subject line formulas that avoid spam filters while driving opens
- You are designing branching logic: reply at any touchpoint exits the sequence and starts dialogue; no reply after Email 4 triggers a 60-day park and reactivation
- You need to generate 3+ complete, real-world email sets (different ICPs) with exact word counts and proof points
- Your team wants a repeatable, measurable cold email framework with post-sequence reactivation rules
When NOT to use
- For transactional or customer onboarding emails (use nurture sequences instead)
- If your ICP is unknown or buyer personas are not defined—define those first
- For high-touch accounts requiring personalization beyond the trigger signal (use 1-1 outbound instead)
- If your company lacks the infrastructure to track replies and execute branch logic (set up CRM automation first)
- For prospect lists under 100 contacts—ROI is typically too low to justify sequence execution
Instructions
Framework: The 4-Email Sequence Structure
The sequence is built on progressive context-stacking: each email assumes the previous was read but unanswered. Subject line formulas and body copy are designed to move the needle on open rates, reply rates, and psychological receptivity.
Email 1: The Hook (Day 0)
Purpose: Establish relevance with zero ask. Trigger signal or personalization hook only.
Subject Line Formula:
[specific fact about their business] + [question marker]- Examples:
hiring 12 engineers this quarter? | moving to [region]? | saw the [product] launch
- Rule: lowercase (except proper nouns), no spam trigger words (free, limited, exclusive, guarantee, act now, urgent)
- Benchmark: 35–45% open rate with strong trigger signal
Body Copy Rules:
- Max 60 words (strict)
- No product mention
- One relevant question that assumes no context
- Tone: curious, not salesy
- Opening: specific observation or trigger (hiring, funding, integration, announcement)
- Closing: soft handoff (quick question, no CTA)
Template:
[Name],
[Trigger signal: specific, fact-based observation about their business].
Quick question: [one question that shows you read their context and care about the answer].
[Your name]
Word Count Check: Count every word in the body. Stop before hitting 61.
Email 2: The Pain (Day 3)
Purpose: Connect their likely pain to concrete KPI impact. One proof point. One CTA.
Subject Line Formula:
re: [original subject] (reply-threading for deliverability; technically a re- subject)- Or:
[metric/outcome] at [similar company type]
- Benchmark: 25–35% open rate (lower than Email 1; expected in sequence)
Body Copy Rules:
- Max 80 words
- One sentence proof (real company, similar size/industry, concrete result)
- Connect pain to KPI (revenue, headcount, cost, churn, time-to-hire)
- One CTA: "worth a quick call?" or "make sense to explore?"
- Tone: confident, problem-aware, helpful
- No product pitch; only outcome
Template:
[Name],
[Pain statement: what's probably costing them time/money/growth].
[Similar company name] saw [specific metric improvement] after [brief intervention description].
[One question linking their pain to next step].
[Your name]
Proof Point Specificity: Use real benchmarks. "We helped a [size]-person [industry] team reduce [metric] by [%]" is stronger than "typical companies see results."
Email 3: The Delegation Ask (Day 7)
Purpose: Remove ego. Assume they own the problem OR someone else does.
Subject Line Formula:
re: [original subject] (threading)- Or:
might be on someone else's desk?
- Benchmark: 15–25% open rate (third touchpoint; fatigue sets in)
Body Copy Rules:
- Max 80 words
- Lead with uncertainty: "Not sure if X is on your radar..."
- Offer delegation: "...or if someone else owns this at [company]."
- Soft exit: "happy to follow up with them instead" or "happy to circle back when timing's better"
- Tone: helpful, non-pushy, removes commitment friction
- This email lowers the psychological barrier to a reply (they can delegate instead of ignore)
Template:
[Name],
Not sure if [specific problem/initiative] is on your radar right now, or if [peer/function] owns this at [company].
[One value statement or context reminder].
Happy to follow up with them directly, or circle back in [timeframe]. What makes most sense?
[Your name]
Email 4: The Break-Up (Day 12)
Purpose: Leave a gift, no ask. Often generates unexpected replies (curiosity, guilt, or genuine interest).
Subject Line Formula:
re: [original subject] (threading)- Or:
last note: [insight/resource type]
- Benchmark: 10–20% open rate (final touchpoint; often opens out of guilt or clarity)
Body Copy Rules:
- Max 100 words
- Lead with explicit exit: "I'll stop reaching out after this."
- Gift: [insight, resource, template, benchmark, article] relevant to their pain
- No CTA. No ask for a call. None.
- Tone: generous, low-pressure, helpful regardless of their decision
- This email often generates replies because there's no ask
Template:
[Name],
I'll stop reaching out after this—but thought you might find [specific resource type] valuable regardless of timing.
[Brief insight or why this resource matters to their context].
[Link or description of resource].
All the best,
[Your name]
Gift Ideas: Case study, benchmark report, template, article, integrations guide, competitor analysis, hiring rubric, etc.
Branching Logic and State Management
Reply Path (Any Email)
If the prospect replies at any point in the sequence:
- Exit the sequence immediately. Stop all automated sends.
- Tag the prospect:
replied_email_[n] (e.g., replied_email_2)
- Hand off to sales: Direct sales representative engages in 1-1 conversation
- No further automation: Conversation is live and human-driven
- Benchmark: Typical reply rate across all 4 emails: 5–12% (depends on ICP, list quality, personalization depth)
No-Reply Path (All 4 Emails Sent)
If the prospect does not reply to any of the 4 emails:
- Park the prospect for 60 days. No sends during this window.
- Reactivation trigger (Day 72+): Watch for new signals
- Job change (prospect title or company change)
- Company funding announcement
- New product launch
- Website/product update indicating growth/shift
- New hiring/expansion announcement
- Reactivation email: New sequence with fresh trigger signal (not a repeat of the original sequence)
- Subject: New trigger signal (not "re:")
- Body: Reference that time has passed; position new signal as reason to reconnect
- Tone: "Saw your announcement on [X], thought it might be relevant now"
Disqualification
Park indefinitely (remove from active nurture) if:
- Prospect company goes into decline, funding trouble, or acquisition
- Prospect job title changes to non-target role
- Company is no longer in target ICP (size, industry, geography)
Subject Line Hygiene Rules
Spam Triggers to Avoid (will tank deliverability):
- Free, limited, exclusive, guarantee, act now, urgent, click here, don't miss, last chance
- ALL CAPS words
- Excessive punctuation (!!!, ???, [multiple emojis])
- Numbers alone (e.g., "50% OFF")
- Re-subject threading after Email 2 (switch to fresh subject for Email 3 or use
re: [fresh angle])
High-Performing Patterns:
- Curiosity: "quick question about [specific thing]?"
- Specificity: "[Named person/company] did [thing]"
- Relevance: "[Their announced initiative] + [your domain]"
- Social proof: "noticed you [hired/launched/announced]"
Personalization Depth Per Email
| Email | Personalization Level | Examples |
|---|
| Email 1 | High: Individual signal | "Just saw you hired 12 engineers" / "Caught your podcast on [topic]" |
| Email 2 | Medium-High: Role + company context | "Finance teams at [industry] usually see [metric] improve after" |
| Email 3 | Medium: Assume role or delegate | "If [role] handles [initiative] at [company]..." |
| Email 4 | Low: Gift is universally relevant | Resource/insight applies broadly |
Measurement Benchmarks
| Metric | Benchmark Range | Healthy |
|---|
| Email 1 Open Rate | 35–50% | 40%+ with strong signal |
| Email 2 Open Rate | 20–35% | 25%+ |
| Email 3 Open Rate | 15–25% | 20%+ |
| Email 4 Open Rate | 10–20% | 15%+ |
| Cumulative Reply Rate (All 4) | 5–12% | 8%+ for B2B SaaS |
| Cost per Reply (including time) | $50–200 | Depends on load, ICP |
Conversion to Conversation (reply → first call):
- Typical conversion: 50–70% of replies convert to meetings
- Higher if Email 3 generates replies (lower barrier, more genuine interest)
Decision Tree for Sequence Execution
START: Prospect added to list
|
+→ Email 1 sent (Day 0)
|
+→ Reply received? YES → EXIT sequence, tag "replied_email_1", hand to sales
|
+→ No reply → wait 3 days
|
+→ Email 2 sent (Day 3)
|
+→ Reply received? YES → EXIT sequence, tag "replied_email_2", hand to sales
|
+→ No reply → wait 4 days
|
+→ Email 3 sent (Day 7)
|
+→ Reply received? YES → EXIT sequence, tag "replied_email_3", hand to sales
|
+→ No reply → wait 5 days
|
+→ Email 4 sent (Day 12)
|
+→ Reply received? YES → EXIT sequence, tag "replied_email_4", hand to sales
|
+→ No reply → PARK for 60 days
|
+→ Day 72: Monitor for new signal
|
+→ New signal detected? → Send Reactivation Email with fresh subject
|
+→ No signal after 60 days? → Move to low-priority nurture or remove
Reactivation Email Template (Day 72+)
Use only if NEW signal is detected.
Subject Line Formula:
saw [announcement/change] at [company] (fresh subject, no "re:")- Examples:
saw the new Chief Revenue Officer hire | caught the Series A announcement
Body:
[Name],
Saw that [specific new signal: hiring, launch, funding, partnership, etc.] at [company].
Thought it might be relevant timing to revisit [original pain/opportunity], especially given [how new signal connects to original context].
Would be worth a brief chat?
[Your name]
Rules:
- Max 60 words
- Fresh subject line (not "re:")
- Reference the original pain, but frame it as newly urgent because of the signal
- If no new signal emerges by Day 90, move to nurture or remove
Example
Example 1: B2B SaaS Sales Leader (ICP: VP Sales, 40–300 person company, Series A–C)
Company Context: Mid-market SaaS company, Series B funding, 3-month-old VP Sales hire, scaling sales team
Email 1: The Hook (Day 0)
Subject: hired your third sales manager?
Body:
Marcus,
Saw you just promoted your second sales manager. Curious: are you planning a third hire before year-end, or are you hitting hiring cap?
The reason I ask—most VPs in your stage are getting bottlenecked on pipeline velocity, not headcount.
[Your name]
Word count: 48 words ✓
Email 2: The Pain (Day 3)
Subject: re: hired your third sales manager?
Body:
Marcus,
Most VP Sales at your stage see pipeline velocity as the #1 blocker to hiring more AEs without losing quality.
Notion saw a 40% increase in pipeline quality once they standardized their discovery process and started tracking leading indicators instead of lag indicators.
Worth spending 15 minutes exploring whether you're measuring the right metrics?
[Your name]
Word count: 65 words ✓
Email 3: The Delegation Ask (Day 7)
Subject: re: hired your third sales manager?
Body:
Marcus,
Not sure if ops/analytics own this at [company], or if it's still on your plate with the new VP role.
Either way, most teams benefit from having a clear view of which metrics actually predict deal closure.
Happy to loop in whoever owns RevOps, or circle back with you when things settle.
[Your name]
Word count: 61 words ✓
Email 4: The Break-Up (Day 12)
Subject: re: hired your third sales manager?
Body:
Marcus,
I'll stop reaching out after this—but thought you might find this useful regardless: we put together a "Sales Leading Indicators Checklist" (used by Notion, Figma, Airtable), focused on metrics that actually predict early-stage growth.
It's a one-pager, no pitch.
[Link to resource]
All the best,
[Your name]
Word count: 59 words ✓
Reactivation Signal (Day 72+): New signal detected: "Just saw Marcus's company raised Series C"
Reactivation Email:
Subject: caught the Series C announcement
Body:
Marcus,
Just saw you closed the Series C. Congratulations.
Series C is exactly the moment where pipeline quality becomes make-or-break. Most teams either accelerate hiring and lose the sales floor, or move too slow and miss growth windows.
Worth a brief call to talk about how you're thinking about scaling without losing margin?
[Your name]
Word count: 58 words ✓
Example 2: Finance Director (ICP: Finance Director, 100–500 person company, Manufacturing or Distribution)
Company Context: Regional manufacturing company, 3-year growth from $50M to $120M ARR, recently promoted Finance Director, scaling finance team
Email 1: The Hook (Day 0)
Subject: how are you tracking cash position with supply chain volatility?
Body:
Jennifer,
With commodity prices moving the way they are, I'm curious: are you rebuilding cash flow forecasts weekly, monthly, or are you still on the old cadence?
Most finance teams your size are getting surprised by working capital swings they could've flagged 30 days earlier.
[Your name]
Word count: 57 words ✓
Email 2: The Pain (Day 3)
Subject: re: how are you tracking cash position with supply chain volatility?
Body:
Jennifer,
Finance teams at distributors your size typically waste 15–20 hours a week rebuilding cash forecasts manually, and they still miss signals.
A regional distributor we worked with reduced forecast error from 18% to 5% once they automated supplier payment and inventory lookback.
Would be worth seeing if the same approach works for you?
[Your name]
Word count: 62 words ✓
Email 3: The Delegation Ask (Day 7)
Subject: re: how are you tracking cash position with supply chain volatility?
Body:
Jennifer,
Not sure if this sits with your supply chain partner or if you're running point on cash forecasting at [company].
Either way, most teams benefit from having supply chain and finance sync on inventory and payables once a week.
Happy to connect with your supply chain lead, or follow up when you have 15 minutes.
[Your name]
Word count: 64 words ✓
Email 4: The Break-Up (Day 12)
Subject: last note: cash flow template for supply-constrained teams
Body:
Jennifer,
I'll stop reaching out after this, but I put together a cash flow forecast template built specifically for distribution teams managing volatile supplier payment windows.
It's built for Excel, no setup needed.
Some teams have found it useful as a starting point even if they don't use our full system.
[Link to template]
All the best,
[Your name]
Word count: 62 words ✓
Reactivation Signal (Day 72+): New signal detected: "Saw Jennifer's company received a major contract win (industry news)"
Reactivation Email:
Subject: saw the new [major client] contract
Body:
Jennifer,
Just saw [company] landed the [major client] contract—a big win for the region.
That kind of growth typically means your cash cycles get more complex: longer payment terms, inventory ramp, customer concentration risk.
Might be a good moment to revisit your cash forecasting approach?
[Your name]
Word count: 58 words ✓
Example 3: Engineering Manager (ICP: Engineering Manager, Early-Stage Startup, 10–30 person team)
Company Context: Series A fintech startup, 6-month-old engineering manager hire, scaling engineering team from 8 to 15 people
Email 1: The Hook (Day 0)
Subject: moving from 8 engineers to 15—how are you keeping shipping velocity?
Body:
David,
Saw on LinkedIn you just ramped from 8 to 15 engineers over the last 6 months. That's fast.
Quick question: are you still hitting your sprint goals on time, or has velocity started to slip with the new headcount?
[Your name]
Word count: 52 words ✓
Email 2: The Pain (Day 3)
Subject: re: moving from 8 engineers to 15—how are you keeping shipping velocity?
Body:
David,
Most engineering teams see a 20–30% velocity drop in months 2–4 after scaling headcount (onboarding tax, context switch, architectural debt surfaces).
A Series A fintech we worked with flattened their velocity loss to 8% by documenting their architecture decisions and pairing new hires with systems ownership from day one.
Might be worth a conversation?
[Your name]
Word count: 67 words ✓
Email 3: The Delegation Ask (Day 7)
Subject: re: moving from 8 engineers to 15—how are you keeping shipping velocity?
Body:
David,
Not sure if architectural documentation or developer onboarding is your call at [company], or if you're sharing the load with a Staff Eng or Tech Lead.
Either way, most teams benefit from having a clear map of "who owns what system" before they hit 15+ headcount.
Happy to loop in whoever runs architecture, or circle back next month.
[Your name]
Word count: 70 words ✓
Email 4: The Break-Up (Day 12)
Subject: last note: system ownership template for growing teams
Body:
David,
I'll stop reaching out after this, but thought you might find this useful: we built a "System Ownership Matrix" template that helps teams clarify who's accountable for each major system, which usually cuts onboarding time for new hires by 40%.
No product involved—just a template you can modify.
[Link to template]
All the best,
[Your name]
Word count: 65 words ✓
Reactivation Signal (Day 72+): New signal detected: "David's company just announced Series B funding"
Reactivation Email:
Subject: caught the Series B news
Body:
David,
Saw [company] just announced the Series B. Nice work.
Series B means you're probably hiring 8–12 more engineers in the next 9 months. That's when poor system ownership and onboarding really hit. Teams usually see another 15–20% velocity dip if they don't get documentation in place now.
Worth a quick chat on how to structure the next phase?
[Your name]
Word count: 68 words ✓
Rules & Guardrails
Never
- Send more than 4 touches in the initial sequence
- Ask for a meeting in Emails 1, 3, or 4 (only Email 2 has a soft CTA)
- Use the prospect's company name generically; use their announced changes specifically
- Ignore replies—exit the sequence immediately when a reply lands
- Reactivate a prospect without a new, material signal
Always
- Verify the prospect still fits your ICP before reactivation (job title, company status, growth indicators)
- Track reply rate by email # (Email 1 vs 2 vs 3 vs 4) to optimize subject lines and body copy
- A/B test subject lines in Email 1 across your list (lowercase + question vs announcement format)
- Include a real proof point (company, metric, percentage improvement) in Email 2
- Leave no product mention in Emails 1, 3, 4 (only business outcome in Email 2)
Timing Windows (strict adherence required for sequence integrity)
- Email 1 → Email 2: 3 days (not 2, not 4)
- Email 2 → Email 3: 4 days (total 7 days from start)
- Email 3 → Email 4: 5 days (total 12 days from start)
- No-reply → Park: 60 days (minimum; can extend to 90 if signal-monitoring capacity is limited)
- Reactivation watch window: Day 72–120 (monitor for new signal; if none, move to low-priority nurture)
Prompt for CRM Automation
Use this prompt to set up your email sequence in your CRM (HubSpot, Pipedrive, Close, etc.):
1. Create a workflow: "Cold Email Sequence – 4 Touch"
2. Trigger: Contact added to list "Outbound Sequence [Campaign Name]"
3. Actions (sequential, with delays):
- Day 0: Send Email 1 (subject: [insert subject], body: [insert body])
- Wait 3 days
- If no reply: Send Email 2
- Wait 4 days
- If no reply: Send Email 3
- Wait 5 days
- If no reply: Send Email 4
- Wait 60 days
4. Branching: If contact replies at any step, immediately:
- Tag contact with "replied_email_[n]"
- Move contact to "Sales Engagement" queue
- Pause/remove from automation
5. After Email 4: Tag as "sequence_complete_no_reply", set reminder for Day 72 reactivation check
Optimization Loop (After 50+ Sequences Sent)
After you've sent at least 50 complete sequences, measure:
- Subject line performance: Which Email 1 subject got the highest open rate? (You can A/B test 2 variants per campaign)
- Reply rate by email: Which email generated the most replies? (If Email 3 has high reply rate, you're removing friction correctly; if Email 2 dominates, your pain point is too compelling)
- Proof point efficacy: Does the specific KPI you mention in Email 2 resonate? (Update based on which metric prospects ask about in replies)
- Time-to-first-reply: Are replies coming in on Day 1–2, or Days 5+? (Faster replies = stronger trigger signal or better subject line)
Iterate based on data, not gut. If Email 1 open rate is under 30%, your trigger signal is weak—change it. If Email 2 reply rate is under 1%, your pain point doesn't land—test a different KPI.
