cold-email

What this skill does

# Cold Email Outreach

Production-grade B2B cold email that sounds like it came from a person, not a sequence tool.

---

## Table of Contents

- [Keywords](#keywords)
- [Quick Start](#quick-start)
- [Core Workflows](#core-workflows)
- [Writing Principles](#writing-principles)
- [Voice Calibration by Audience](#voice-calibration-by-audience)
- [Subject Line Framework](#subject-line-framework)
- [Follow-Up Strategy](#follow-up-strategy)
- [Personalization Framework](#personalization-framework)
- [Deliverability Setup](#deliverability-setup)
- [Compliance Requirements](#compliance-requirements)
- [Anti-Patterns](#anti-patterns)
- [Best Practices](#best-practices)
- [Integration Points](#integration-points)

---

## Keywords

cold email, cold outreach, prospecting email, SDR email, sales email, first-touch email, follow-up sequence, email prospecting, outbound email, sales development, sequence building, email personalization, email deliverability, CAN-SPAM, GDPR, B2B outreach, email compliance, subject lines, reply rates, breakup email

---

## Quick Start

### Write a First-Touch Email

1. Define the ICP, specific problem, and outreach trigger
2. Select voice calibration based on recipient seniority
3. Write opener about their world (not yours)
4. State relevance in 1-2 sentences with specific proof
5. Close with a single, low-friction ask
6. Generate 3 subject line variants
7. Validate: under 150 words, no corporate speak, one CTA

### Build a Full Sequence

1. Write the first email (above)
2. Plan 4-5 follow-ups, each with a different angle
3. Set escalating gap cadence (Day 1, 4, 9, 16, 25, 35)
4. Write each follow-up as a standalone (recipient does not remember earlier emails)
5. End with a breakup email that closes the loop professionally
6. Validate deliverability setup before sending

---

## Core Workflows

### Workflow 1: Single First-Touch Email

**Step 1: Gather Context**

Required information:
- **Sender context**: Role, company, what they sell, key proof points
- **Prospect context**: Job title, company type/size, likely problem, trigger for outreach
- **Goal**: Book a call? Get a reply? Get a referral?

**Step 2: Choose Framework**

| Framework | Best When | Structure |
|-----------|-----------|-----------|
| Problem-First | Prospect has a visible pain point | Problem observation > Relevance > Ask |
| Trigger-Based | There is a specific event (funding, hiring, news) | Trigger reference > Connection to problem > Ask |
| Mutual Connection | Referral or shared network | Name drop > Context > Ask |
| Value-First | You have something genuinely useful to share | Insight/resource > Brief context > Ask |
| Direct Ask | Prospect is high-intent or very senior | Brief context > Direct question |

**Step 3: Draft the Email**

Structure:
```
Subject: [2-4 words, looks like an internal email]

[Opener: 1 sentence about their world — trigger, observation, or question]

[Relevance: 1-2 sentences connecting their situation to what you do]

[Proof: 1 sentence of credible evidence — specific number, named customer, result]

[Ask: 1 sentence with a single, specific, low-friction CTA]

[Sign-off]
```

**Step 4: Validate**

- [ ] Under 150 words total
- [ ] Opener is about them, not you
- [ ] No sentence starts with "I" or "We"
- [ ] One CTA, not multiple
- [ ] CTA is a question, not a statement
- [ ] No jargon or corporate speak
- [ ] Would a friend send this to another friend in business?

### Workflow 2: Full Sequence Build

**Step 1: Write Email 1 (Using Workflow 1)**

**Step 2: Plan Follow-Up Angles**

Each follow-up needs a distinct angle. Plan before writing:

| Email | Day | Angle | What is New |
|-------|-----|-------|-------------|
| 1 | Day 1 | Problem-first | Initial outreach |
| 2 | Day 4 | New evidence | Case study, data point, or recent result |
| 3 | Day 9 | Different pain point | Alternative angle on their world |
| 4 | Day 16 | Industry insight | Something notable about their space |
| 5 | Day 25 | Direct question | Simple, clear ask without context |
| 6 | Day 35 | Breakup | Professional close, referral ask |

**Step 3: Write Each Follow-Up**

Rules for every follow-up:
- Standalone: does not require reading previous emails
- New angle: brings something the previous email did not
- Shorter than Email 1 (each subsequent email gets shorter)
- Never says "just checking in" or "circling back"
- Never references all previous emails ("As I mentioned in my last three emails...")

**Step 4: Write the Breakup Email**

The breakup email closes the loop. It signals this is the last one, which paradoxically increases reply rate.

Template:
```
Subject: closing the loop

[Name],

Last note from me. If [specific problem] becomes a priority,
reply here and I'll pick it up.

If there's someone else at [Company] better suited for this
conversation, a name would help.

Either way — [genuine well-wish related to something specific].

[Sign-off]
```

### Workflow 3: Performance Iteration

**Step 1: Diagnose the Problem**

| Symptom | Likely Cause | Fix |
|---------|-------------|-----|
| Low open rate (< 25%) | Subject lines | Test new subject line patterns |
| Opens but no replies (< 2% reply rate) | Email body | Rewrite with stronger relevance and lower-friction CTA |
| Replies but wrong outcome | CTA mismatch | Adjust the ask |
| High bounce rate (> 5%) | List quality | Verify email addresses before sending |
| Landing in spam | Deliverability | Check SPF/DKIM/DMARC, reduce send volume, warm domain |

**Step 2: Rewrite the Underperforming Element**

Focus on one element at a time. Do not rewrite the entire email when only the subject line is the problem.

**Step 3: Test and Measure**

- A/B test subject lines with minimum 100 sends per variant
- Test one variable at a time
- Wait for 3-5 days of data before drawing conclusions
- Document every test and result for future reference

---

## Writing Principles

### 1. Write Like a Peer, Not a Vendor

The moment your email sounds like marketing copy, it is deleted.

**Test:** Would you send this to a smart colleague at another company? If not, rewrite.

### 2. Every Sentence Earns Its Place

Each sentence must do one of these jobs:
- Create curiosity
- Establish relevance
- Build credibility
- Drive to the ask

If a sentence does none of these, cut it.

### 3. Personalization Must Connect to the Problem

Generic personalization is worse than none.

- Bad: "I saw you went to Stanford" followed by a pitch unrelated to Stanford
- Good: "I saw you're hiring three SDRs — usually a signal that you're scaling cold outreach. That's exactly the challenge we help with."

The personalization must bridge to the reason for reaching out.

### 4. Lead with Their World, Not Yours

The opener should be about their situation, problem, or context. Not about you or your product.

### 5. One Ask Per Email

Do not ask them to book a call, watch a demo, read a case study, AND reply with their timeline. Pick one.

---

## Voice Calibration by Audience

| Audience | Length | Tone | Subject Style | What Works |
|----------|--------|------|---------------|------------|
| C-suite (CEO, CRO, CMO) | 3-4 sentences | Ultra-brief, peer-level, strategic | Short, vague, internal-looking | Big problem > relevant proof > one question |
| VP / Director | 5-7 sentences | Direct, metrics-conscious | Slightly more specific | Specific observation + clear business angle |
| Manager | 7-10 sentences | Practical, shows homework | Can be descriptive | Specific problem + practical value + easy CTA |
| Technical (Engineer, Architect) | 7-10 sentences | Precise, no fluff | Technical specificity | Exact problem > precise solution > low-friction ask |
| Founder / Solo | 5-7 sentences | Empathetic, peer-to-peer | Casual, human | Shared experience + relevant proof + conversational ask |

Rule: The higher up the org chart, the shorter your email needs to be.

---

## Subject Line Framework

### Principles

The goal of a subject line is to get the email opened. N