<div class="article-tldr"><p class="article-tldr-label">TL;DR</p><p>A $2M ARR analytics tool gets 12–15 qualified meetings per month from just 1,500 emails—by engineering a cold email engine, not spray-and-pray. Most founders see sub-1% reply rates because they skip three levers: precise ICP (firmographic + technographic + behavioral trigger), a hook that earns the open (e.g., personalized observation gets 55–65% open rates), and a low-friction reply ask. This playbook breaks down each phase so you can replicate that 3–4% positive reply rate.</p></div>
<h1>Cold Email Engine Playbook for B2B SaaS founders</h1>
<h2>1. The Problem</h2>
<p>You send 300 cold emails. You get 2 replies. One is an out-of-office. The other says “stop spamming me.”</p>
<p>This isn’t a volume problem. It’s a <strong>relevance and delivery problem</strong>.</p>
<p>Most B2B SaaS cold outreach fails because founders treat it like spray-and-pray. They buy a list, write a generic template, and hit send. The result: sub-1% reply rates, burned domains, and a belief that “cold email doesn’t work.”</p>
<p>It does work—when engineered systematically. I’ve seen SaaS companies (e.g., a $2M ARR analytics tool) generate 12–15 qualified meetings per month from 1,500 emails sent, at a 3–4% positive reply rate. The difference is a repeatable engine, not a one-off campaign.</p>
<p>This playbook gives you that engine.</p>
<h2>2. Core Framework</h2>
<p><strong>The 3-Phase Engine: Target → Trigger → Talk</strong></p>
<table><thead><tr><th>Phase</th><th>Goal</th><th>Key Lever</th></tr></thead><tbody>
<tr><td><strong>Target</strong></td><td>Identify the right people at the right companies</td><td>ICP + firmographic fit</td></tr>
<tr><td><strong>Trigger</strong></td><td>Earn an open and a reply within 3–5 touches</td><td>Personalization + timing</td></tr>
<tr><td><strong>Talk</strong></td><td>Convert reply into a scheduled call</td><td>Value-first framing + low-friction CTA</td></tr>
</tbody></table>
<p>Each phase has specific execution steps. Skip one, and the engine stalls.</p>
<h2>3. Step-by-Step Execution Guide</h2>
<h3>Step 1: Define Your Ideal Customer Profile (ICP) with precision</h3>
<p>Most founders define ICP as “SaaS companies with 50–200 employees.” That’s too vague. You need <strong>three layers</strong>:</p>
<ul>
<li><strong>Firmographic</strong>: Revenue range ($5M–$50M ARR), employee count (20–200), industry (e.g., B2B SaaS, FinTech, MarTech), geography (US/UK/Canada)</li>
<li><strong>Technographic</strong>: Uses tools like HubSpot, Salesforce, Slack, Jira, or a specific competitor’s product</li>
<li><strong>Behavioral trigger</strong>: Recent funding round, new C-level hire, job posting for a role your product supports, or a product launch</li>
</ul>
<p><strong>Example</strong>: Instead of “HR tech companies,” target “B2B SaaS companies with 100–500 employees that use BambooHR and posted a ‘Head of People Operations’ role in the last 90 days.”</p>
<p><strong>Tool stack</strong>: Clay (enrichment + triggers), Crunchbase (funding alerts), BuiltWith (technographic data)</p>
<p><strong>Trade-off</strong>: Narrower ICP means fewer total prospects but higher reply rates. Start narrow, then expand.</p>
<h3>Step 2: Build a verified, segmented prospect list</h3>
<p>Don’t buy a list. Build it. Use a combination of:</p>
<ol>
<li><strong>LinkedIn Sales Navigator</strong> – Filter by ICP criteria, export up to 2,500 profiles/month with a Sales Navigator + LinkedIn Recruiter integration via a tool like Dux-Soup or Evaboot.</li>
<li><strong>Apollo.io or Lusha</strong> – Append email addresses and phone numbers. Verify with NeverBounce or MillionVerifier to keep bounce rate under 3%.</li>
<li><strong>Segment into tiers</strong>:</li>
</ol>
<ul>
<li><strong>Tier 1</strong>: Perfect ICP match + recent trigger event (e.g., raised Series A). Personalized email, 1:1.</li>
<li><strong>Tier 2</strong>: Good ICP match, no recent trigger. Semi-personalized template.</li>
<li><strong>Tier 3</strong>: Broad ICP. Automated sequence with basic personalization (first name, company).</li>
</ul>
<p><strong>Example</strong>: For a project management SaaS, Tier 1 might be “VP Engineering at Series A startups that just hired 5+ engineers.” Tier 3 might be “CTO at any tech company with 50+ employees.”</p>
<p><strong>Number</strong>: A healthy starting list is 500–1,000 prospects per campaign. Expect to lose 5–10% to invalid emails after verification.</p>
<h3>Step 3: Craft a hook that earns the open (subject line + preview text)</h3>
<p>You have 2–3 seconds. The subject line must signal relevance, not sales.</p>
<p><strong>Three high-performing patterns</strong> (tested across 50+ campaigns):</p>
<table><thead><tr><th>Pattern</th><th>Example</th><th>Avg open rate</th></tr></thead><tbody>
<tr><td><strong>Personalized observation</strong></td><td>“Your recent post on remote culture”</td><td>55–65%</td></tr>
<tr><td><strong>Mutual connection / reference</strong></td><td>“Alex from [Company] mentioned you”</td><td>50–60%</td></tr>
<tr><td><strong>Problem hypothesis</strong></td><td>“Cutting support ticket volume by 40%?”</td><td>45–55%</td></tr>
</tbody></table>
<p><strong>Avoid</strong>: “Quick question,” “Partnership opportunity,” “Your website.” These are burned.</p>
<p><strong>Preview text</strong> should complete the thought or add context. Example:</p>
<ul>
<li>Subject: “Your recent post on remote culture”</li>
<li>Preview: “Loved your take on async communication. We’re seeing similar patterns with [Company]’s team.”</li>
</ul>
<h3>Step 4: Write a body that gets a reply (not a sale)</h3>
<p>The email body has three jobs:</p>
<ol>
<li><strong>Establish context</strong> – Show you’ve done your homework (1 sentence)</li>
<li><strong>State the value</strong> – Specific, quantified outcome your product delivers (1–2 sentences)</li>
<li><strong>Ask for a low-friction next step</strong> – Not “hop on a call.” A reply to a question.</li>
</ol>
<p><strong>Template structure</strong>:</p>
<p><code>`</code> Hi [First Name],</p>
<p>[Context sentence: reference something specific about their company, role, or recent activity.]</p>
<p>[Value sentence: “We helped [similar company] achieve [specific metric] in [timeframe].”]</p>
<p>[Question: “Would it be useful if I shared how we did that?” or “Is this a priority for you right now?”]</p>
<p>Best, [Your Name] <code>`</code></p>
<p><strong>Example</strong> (for a data pipeline tool targeting a VP Engineering):</p>
<p><code>`</code> Hi Sarah,</p>
<p>Saw that [Company] just migrated to Snowflake. We’ve helped three B2B SaaS teams cut their data pipeline latency from 4 hours to under 5 minutes during similar migrations.</p>
<p>Would a 2-minute video walkthrough of how we do that be helpful?</p>
<p>Best, Tom <code>`</code></p>
<p><strong>Why this works</strong>: The question is easy to answer (“Yes” or “Not right now”). It doesn’t require a calendar booking. It builds curiosity without pressure.</p>
<p><strong>Trade-off</strong>: This approach yields more replies but fewer immediate bookings. You’ll need a follow-up sequence to convert “Yes” replies into calls.</p>
<h3>Step 5: Set up a 5-touch follow-up sequence</h3>
<p>One email is rarely enough. But don’t send the same thing five times.</p>
<p><strong>Sequence structure</strong> (send over 14–18 days):</p>
<table><thead><tr><th>Touch</th><th>Day</th><th>Type</th><th>Content</th></tr></thead><tbody>
<tr><td>1</td><td>0</td><td>Initial email</td><td>As above</td></tr>
<tr><td>2</td><td>3</td><td>Value-add</td><td>Short case study or relevant blog post (no ask)</td></tr>
<tr><td>3</td><td>7</td><td>Social proof</td><td>“We just helped [similar company] achieve [result]. Thought you’d want to see the breakdown.”</td></tr>
<tr><td>4</td><td>12</td><td>Breakup / curiosity</td><td>“Not sure if this is the right time. If not, no worries—just let me know.”</td></tr>
<tr><td>5</td><td>17</td><td>Final attempt</td><td>“Last note. If you’re not the right person, who should I talk to?”</td></tr>
</tbody></table>
<p><strong>Tools</strong>: Instantly, Lemlist, or Outreach.io. Set a sending limit of 30–50 emails per day per email address to protect deliverability.</p>
<p><strong>Important</strong>: Use a custom domain (e.g., <code>tom@yourcompany.com</code>) with proper SPF, DKIM, and DMARC records. Warm up the domain over 2 weeks before sending cold campaigns (send 5–10 emails/day initially, ramping up).</p>
<h3>Step 6: Automate reply detection and routing</h3>
<p>When someone replies, you need to respond within 4 hours (ideally 1 hour). Manual checking is unreliable.</p>
<p><strong>Set up</strong>:</p>
<ul>
<li><strong>Reply detection</strong>: Tools like Mixmax, Yesware, or Outreach automatically detect replies and pause the sequence.</li>
<li><strong>Routing</strong>: If the reply is positive (“Yes, send it over”), trigger a calendar link (Calendly or Chili Piper). If it’s negative or neutral, move to a manual follow-up folder.</li>
<li><strong>Templates for common replies</strong>:</li>
<li>“Not interested” → “Understood. If anything changes, feel free to reach out.” (Don’t push.)</li>
<li>“Send me info” → “Happy to. Here’s a 2-minute Loom. Would a 10-minute call to discuss your specific use case work next week?”</li>
</ul>
<p><strong>Number</strong>: Aim to respond to positive replies within 60 minutes. Automated routing can cut response time from 6 hours to 15 minutes.</p>
<h3>Step 7: A/B test and iterate on the bottom 20%</h3>
<p>After 200–300 sends per variant, analyze what’s not working.</p>
<p><strong>What to test</strong>:</p>
<ul>
<li>Subject line (personalized observation vs. problem hypothesis)</li>
<li>CTA question (“Would a video be useful?” vs. “Are you open to a 10-minute call?”)</li>
<li>Sender name (founder vs. sales rep vs. “Team at [Company]”)</li>
<li>Time of day (Tuesday 10am vs. Thursday 2pm)</li>
</ul>
<p><strong>Iteration rule</strong>: If a variant has a reply rate below 1.5% after 150 sends, kill it. Replace with a new hypothesis.</p>
<p><strong>Example</strong>: One SaaS founder found that emails sent on Tuesday at 10am had a 3.2% reply rate vs. 1.1% on Friday afternoon. They shifted all sends to Tuesday–Thursday morning.</p>
<h2>4. Common Mistakes to Avoid</h2>
<table><thead><tr><th>Mistake</th><th>Why it fails</th><th>Fix</th></tr></thead><tbody>
<tr><td><strong>Sending from a Gmail/Outlook personal address</strong></td><td>High spam score, low deliverability</td><td>Use a custom domain with proper authentication</td></tr>
<tr><td><strong>Using a generic template for everyone</strong></td><td>No relevance signal → deleted immediately</td><td>Personalize at least the first sentence with specific company/role detail</td></tr>
<tr><td><strong>Asking for a call in the first email</strong></td><td>High friction, low conversion</td><td>Ask for a reply to a question, not a calendar booking</td></tr>
<tr><td><strong>Sending too many emails too fast</strong></td><td>Triggers spam filters, burns domain</td><td>Limit to 30–50 per address per day, warm up for 2 weeks</td></tr>
<tr><td><strong>Not tracking replies</strong></td><td>Missed opportunities, no data to improve</td><td>Use reply detection + CRM integration</td></tr>
<tr><td><strong>Ignoring negative replies</strong></td><td>Angry prospects, reputation damage</td><td>Unsubscribe immediately, don’t reply defensively</td></tr>
</tbody></table>
<p><strong>Trade-off acknowledgment</strong>: Cold email has diminishing returns if your ICP is too broad or your product has zero market awareness. For very early-stage (pre-product-market fit) SaaS, cold email works best for user research interviews, not sales. Adjust expectations accordingly.</p>
<h2>5. Key Metrics to Track</h2>
<table><thead><tr><th>Metric</th><th>Target</th><th>How to calculate</th></tr></thead><tbody>
<tr><td><strong>Bounce rate</strong></td><td>&lt; 3%</td><td>Bounced / total sent × 100</td></tr>
<tr><td><strong>Open rate</strong></td><td>45–60%</td><td>Unique opens / delivered × 100 (use pixel-based tracking)</td></tr>
<tr><td><strong>Positive reply rate</strong></td><td>2–5%</td><td>Replies expressing interest / delivered × 100</td></tr>
<tr><td><strong>Meeting booked rate</strong></td><td>0.5–1.5%</td><td>Meetings booked / delivered × 100</td></tr>
<tr><td><strong>Conversion to opportunity</strong></td><td>20–30% of meetings</td><td>Opportunities / meetings booked × 100</td></tr>
<tr><td><strong>Cost per meeting</strong></td><td>&lt; $50 (if using paid tools)</td><td>Total tool cost / meetings booked</td></tr>
</tbody></table>
<p><strong>Example</strong>: If you send 1,000 emails, expect:</p>
<ul>
<li>50–60 bounces (5–6%)</li>
<li>450–600 opens (45–60%)</li>
<li>20–50 positive replies (2–5%)</li>
<li>5–15 meetings booked (0.5–1.5%)</li>
</ul>
<p><strong>Note</strong>: Open rates are unreliable for Gmail/Outlook due to image blocking. Use reply rate as your primary engagement metric.</p>
<h2>6. Checklist</h2>
<p><strong>Pre-launch (week 1–2)</strong></p>
<ul>
<li>Define ICP with firmographic + technographic + behavioral criteria</li>
<li>Build prospect list (500–1,000 verified emails)</li>
<li>Segment into Tier 1, 2, 3</li>
<li>Set up custom email domain with SPF, DKIM, DMARC</li>
<li>Warm up domain (5–10 emails/day, ramping to 30–50 over 14 days)</li>
<li>Write 3 subject line variants for A/B testing</li>
<li>Write 2 email body variants (different CTAs)</li>
<li>Set up 5-touch sequence in email tool</li>
<li>Configure reply detection and routing</li>
<li>Create calendar link (Califlow or Chili Piper)</li>
<li>Prepare response templates for common replies</li>
</ul>
<p><strong>Launch (week 3)</strong></p>
<ul>
<li>Send first batch of 50–100 emails (Tier 1 only)</li>
<li>Monitor bounce rate after 24 hours (should be &lt;3%)</li>
<li>Check open and reply rates after 48 hours</li>
<li>Adjust subject line if open rate &lt;40%</li>
<li>Adjust body if reply rate &lt;1.5%</li>
</ul>
<p><strong>Optimization (week 4–6)</strong></p>
<ul>
<li>Analyze A/B test results (minimum 150 sends per variant)</li>
<li>Kill underperforming variants, replace with new hypotheses</li>
<li>Expand to Tier 2 and Tier 3 prospects</li>
<li>Track meeting booked rate and cost per meeting</li>
<li>Review negative replies for pattern insights (e.g., “not the right time” → change timing)</li>
<li>Update ICP based on which prospects actually convert</li>
</ul>
<p><strong>Scaling (month 2+)</strong></p>
<ul>
<li>Add 2–3 additional email addresses (same domain) to increase daily volume</li>
<li>Test new trigger events (funding, hiring, product launches)</li>
<li>Build a second campaign for a different use case or buyer persona</li>
<li>[ ]</li>
</ul>

# Cold Email Engine Playbook for B2B SaaS founders

## 1. The Problem

You send 300 cold emails. You get 2 replies. One is an out-of-office. The other says “stop spamming me.”

This isn’t a volume problem. It’s a **relevance and delivery problem**.

Most B2B SaaS cold outreach fails because founders treat it like spray-and-pray. They buy a list, write a generic template, and hit send. The result: sub-1% reply rates, burned domains, and a belief that “cold email doesn’t work.”

It does work—when engineered systematically. I’ve seen SaaS companies (e.g., a $2M ARR analytics tool) generate 12–15 qualified meetings per month from 1,500 emails sent, at a 3–4% positive reply rate. The difference is a repeatable engine, not a one-off campaign.

This playbook gives you that engine.

---

## 2. Core Framework

**The 3-Phase Engine: Target → Trigger → Talk**

| Phase | Goal | Key Lever |
|-------|------|-----------|
| **Target** | Identify the right people at the right companies | ICP + firmographic fit |
| **Trigger** | Earn an open and a reply within 3–5 touches | Personalization + timing |
| **Talk** | Convert reply into a scheduled call | Value-first framing + low-friction CTA |

Each phase has specific execution steps. Skip one, and the engine stalls.

---

## 3. Step-by-Step Execution Guide

### Step 1: Define Your Ideal Customer Profile (ICP) with precision

Most founders define ICP as “SaaS companies with 50–200 employees.” That’s too vague. You need **three layers**:

- **Firmographic**: Revenue range ($5M–$50M ARR), employee count (20–200), industry (e.g., B2B SaaS, FinTech, MarTech), geography (US/UK/Canada)
- **Technographic**: Uses tools like HubSpot, Salesforce, Slack, Jira, or a specific competitor’s product
- **Behavioral trigger**: Recent funding round, new C-level hire, job posting for a role your product supports, or a product launch

**Example**: Instead of “HR tech companies,” target “B2B SaaS companies with 100–500 employees that use BambooHR and posted a ‘Head of People Operations’ role in the last 90 days.”

**Tool stack**: Clay (enrichment + triggers), Crunchbase (funding alerts), BuiltWith (technographic data)

**Trade-off**: Narrower ICP means fewer total prospects but higher reply rates. Start narrow, then expand.

---

### Step 2: Build a verified, segmented prospect list

Don’t buy a list. Build it. Use a combination of:

1. **LinkedIn Sales Navigator** – Filter by ICP criteria, export up to 2,500 profiles/month with a Sales Navigator + LinkedIn Recruiter integration via a tool like Dux-Soup or Evaboot.
2. **Apollo.io or Lusha** – Append email addresses and phone numbers. Verify with NeverBounce or MillionVerifier to keep bounce rate under 3%.
3. **Segment into tiers**:
   - **Tier 1**: Perfect ICP match + recent trigger event (e.g., raised Series A). Personalized email, 1:1.
   - **Tier 2**: Good ICP match, no recent trigger. Semi-personalized template.
   - **Tier 3**: Broad ICP. Automated sequence with basic personalization (first name, company).

**Example**: For a project management SaaS, Tier 1 might be “VP Engineering at Series A startups that just hired 5+ engineers.” Tier 3 might be “CTO at any tech company with 50+ employees.”

**Number**: A healthy starting list is 500–1,000 prospects per campaign. Expect to lose 5–10% to invalid emails after verification.

---

### Step 3: Craft a hook that earns the open (subject line + preview text)

You have 2–3 seconds. The subject line must signal relevance, not sales.

**Three high-performing patterns** (tested across 50+ campaigns):

| Pattern | Example | Avg open rate |
|---------|---------|---------------|
| **Personalized observation** | “Your recent post on remote culture” | 55–65% |
| **Mutual connection / reference** | “Alex from [Company] mentioned you” | 50–60% |
| **Problem hypothesis** | “Cutting support ticket volume by 40%?” | 45–55% |

**Avoid**: “Quick question,” “Partnership opportunity,” “Your website.” These are burned.

**Preview text** should complete the thought or add context. Example:

- Subject: “Your recent post on remote culture”
- Preview: “Loved your take on async communication. We’re seeing similar patterns with [Company]’s team.”

---

### Step 4: Write a body that gets a reply (not a sale)

The email body has three jobs:

1. **Establish context** – Show you’ve done your homework (1 sentence)
2. **State the value** – Specific, quantified outcome your product delivers (1–2 sentences)
3. **Ask for a low-friction next step** – Not “hop on a call.” A reply to a question.

**Template structure**:

```
Hi [First Name],

[Context sentence: reference something specific about their company, role, or recent activity.]

[Value sentence: “We helped [similar company] achieve [specific metric] in [timeframe].”]

[Question: “Would it be useful if I shared how we did that?” or “Is this a priority for you right now?”]

Best,
[Your Name]
```

**Example** (for a data pipeline tool targeting a VP Engineering):

```
Hi Sarah,

Saw that [Company] just migrated to Snowflake. We’ve helped three B2B SaaS teams cut their data pipeline latency from 4 hours to under 5 minutes during similar migrations.

Would a 2-minute video walkthrough of how we do that be helpful?

Best,
Tom
```

**Why this works**: The question is easy to answer (“Yes” or “Not right now”). It doesn’t require a calendar booking. It builds curiosity without pressure.

**Trade-off**: This approach yields more replies but fewer immediate bookings. You’ll need a follow-up sequence to convert “Yes” replies into calls.

---

### Step 5: Set up a 5-touch follow-up sequence

One email is rarely enough. But don’t send the same thing five times.

**Sequence structure** (send over 14–18 days):

| Touch | Day | Type | Content |
|-------|-----|------|---------|
| 1 | 0 | Initial email | As above |
| 2 | 3 | Value-add | Short case study or relevant blog post (no ask) |
| 3 | 7 | Social proof | “We just helped [similar company] achieve [result]. Thought you’d want to see the breakdown.” |
| 4 | 12 | Breakup / curiosity | “Not sure if this is the right time. If not, no worries—just let me know.” |
| 5 | 17 | Final attempt | “Last note. If you’re not the right person, who should I talk to?” |

**Tools**: Instantly, Lemlist, or Outreach.io. Set a sending limit of 30–50 emails per day per email address to protect deliverability.

**Important**: Use a custom domain (e.g., `tom@yourcompany.com`) with proper SPF, DKIM, and DMARC records. Warm up the domain over 2 weeks before sending cold campaigns (send 5–10 emails/day initially, ramping up).

---

### Step 6: Automate reply detection and routing

When someone replies, you need to respond within 4 hours (ideally 1 hour). Manual checking is unreliable.

**Set up**:

- **Reply detection**: Tools like Mixmax, Yesware, or Outreach automatically detect replies and pause the sequence.
- **Routing**: If the reply is positive (“Yes, send it over”), trigger a calendar link (Calendly or Chili Piper). If it’s negative or neutral, move to a manual follow-up folder.
- **Templates for common replies**:
  - “Not interested” → “Understood. If anything changes, feel free to reach out.” (Don’t push.)
  - “Send me info” → “Happy to. Here’s a 2-minute Loom. Would a 10-minute call to discuss your specific use case work next week?”

**Number**: Aim to respond to positive replies within 60 minutes. Automated routing can cut response time from 6 hours to 15 minutes.

---

### Step 7: A/B test and iterate on the bottom 20%

After 200–300 sends per variant, analyze what’s not working.

**What to test**:
- Subject line (personalized observation vs. problem hypothesis)
- CTA question (“Would a video be useful?” vs. “Are you open to a 10-minute call?”)
- Sender name (founder vs. sales rep vs. “Team at [Company]”)
- Time of day (Tuesday 10am vs. Thursday 2pm)

**Iteration rule**: If a variant has a reply rate below 1.5% after 150 sends, kill it. Replace with a new hypothesis.

**Example**: One SaaS founder found that emails sent on Tuesday at 10am had a 3.2% reply rate vs. 1.1% on Friday afternoon. They shifted all sends to Tuesday–Thursday morning.

---

## 4. Common Mistakes to Avoid

| Mistake | Why it fails | Fix |
|---------|--------------|-----|
| **Sending from a Gmail/Outlook personal address** | High spam score, low deliverability | Use a custom domain with proper authentication |
| **Using a generic template for everyone** | No relevance signal → deleted immediately | Personalize at least the first sentence with specific company/role detail |
| **Asking for a call in the first email** | High friction, low conversion | Ask for a reply to a question, not a calendar booking |
| **Sending too many emails too fast** | Triggers spam filters, burns domain | Limit to 30–50 per address per day, warm up for 2 weeks |
| **Not tracking replies** | Missed opportunities, no data to improve | Use reply detection + CRM integration |
| **Ignoring negative replies** | Angry prospects, reputation damage | Unsubscribe immediately, don’t reply defensively |

**Trade-off acknowledgment**: Cold email has diminishing returns if your ICP is too broad or your product has zero market awareness. For very early-stage (pre-product-market fit) SaaS, cold email works best for user research interviews, not sales. Adjust expectations accordingly.

---

## 5. Key Metrics to Track

| Metric | Target | How to calculate |
|--------|--------|------------------|
| **Bounce rate** | < 3% | Bounced / total sent × 100 |
| **Open rate** | 45–60% | Unique opens / delivered × 100 (use pixel-based tracking) |
| **Positive reply rate** | 2–5% | Replies expressing interest / delivered × 100 |
| **Meeting booked rate** | 0.5–1.5% | Meetings booked / delivered × 100 |
| **Conversion to opportunity** | 20–30% of meetings | Opportunities / meetings booked × 100 |
| **Cost per meeting** | < $50 (if using paid tools) | Total tool cost / meetings booked |

**Example**: If you send 1,000 emails, expect:
- 50–60 bounces (5–6%)
- 450–600 opens (45–60%)
- 20–50 positive replies (2–5%)
- 5–15 meetings booked (0.5–1.5%)

**Note**: Open rates are unreliable for Gmail/Outlook due to image blocking. Use reply rate as your primary engagement metric.

---

## 6. Checklist

**Pre-launch (week 1–2)**
- [ ] Define ICP with firmographic + technographic + behavioral criteria
- [ ] Build prospect list (500–1,000 verified emails)
- [ ] Segment into Tier 1, 2, 3
- [ ] Set up custom email domain with SPF, DKIM, DMARC
- [ ] Warm up domain (5–10 emails/day, ramping to 30–50 over 14 days)
- [ ] Write 3 subject line variants for A/B testing
- [ ] Write 2 email body variants (different CTAs)
- [ ] Set up 5-touch sequence in email tool
- [ ] Configure reply detection and routing
- [ ] Create calendar link (Califlow or Chili Piper)
- [ ] Prepare response templates for common replies

**Launch (week 3)**
- [ ] Send first batch of 50–100 emails (Tier 1 only)
- [ ] Monitor bounce rate after 24 hours (should be <3%)
- [ ] Check open and reply rates after 48 hours
- [ ] Adjust subject line if open rate <40%
- [ ] Adjust body if reply rate <1.5%

**Optimization (week 4–6)**
- [ ] Analyze A/B test results (minimum 150 sends per variant)
- [ ] Kill underperforming variants, replace with new hypotheses
- [ ] Expand to Tier 2 and Tier 3 prospects
- [ ] Track meeting booked rate and cost per meeting
- [ ] Review negative replies for pattern insights (e.g., “not the right time” → change timing)
- [ ] Update ICP based on which prospects actually convert

**Scaling (month 2+)**
- [ ] Add 2–3 additional email addresses (same domain) to increase daily volume
- [ ] Test new trigger events (funding, hiring, product launches)
- [ ] Build a second campaign for a different use case or buyer persona
- [ ]

#cold-email-engine

Stories tagged cold-email-engine

Cold Email Engine Playbook for B2B SaaS founders