---
name: cold-outbound-email-writing
slug: cold-outbound-email-writing
description: This skill should be used when the user asks to "write cold outbound", "draft a cold email sequence", "write a sales sequence", "write outbound copy", "build a Lemlist sequence", "build an Outreach sequence", "build a Salesloft campaign", "write B2B cold emails", "draft a 3-email sequence", or any variation of writing outbound email copy for a B2B SaaS audience.
category: general
---

# Cold Outbound Email Writing

Write 3-email cold outbound sequences for B2B SaaS. Peer-to-peer tone. No fluff, no buzzwords. Each email earns the next.

## The 3-Email Shape

| # | Name | Angle | Max words | Timing |
|---|------|-------|-----------|--------|
| 1 | Hook | Why-now signal → tiny ask | 80 | Day 1 |
| 2 | Proof | Different angle + social proof | 90 | Day 4 |
| 3 | Breakup | One clean door-close | 30 | Day 9 |

Stop at 3. More than 3 cold touches = noise.

---

## Email 1 — Why-Now Hook

**Purpose:** Connect a specific, real, observable signal to a problem they care about. Ask for something small.

**Structure (4 sentences max):**
1. Signal — the specific thing that made you reach out today
2. Implication — why it matters for them right now
3. Credibility bridge — who else like them solved it
4. Tiny ask — 15 minutes, a teardown, a look

### Signal Rules

The signal must be specific and verifiable:

- Funding round, job posting, product launch, recent hire, a talk they gave, a tool change in their stack, a company announcement
- "Saw you're growing fast" is not a signal
- "Noticed you're hiring" with no specific take is not a signal
- If you cannot name the trigger, do not write Email 1 — add the prospect to nurture

**Good signals:**
- "Saw you posted for a RevOps lead last week — usually means someone's rebuilding attribution"
- "Congrats on the Series B. The scaling chaos usually hits around month 3"
- "Caught your talk at [event] on pipeline velocity — you mentioned CRM lag eating forecast accuracy"

**Bad signals (never use):**
- "I was doing some research on your company..."
- "I came across your LinkedIn profile..."
- "I've been following your growth..."

### Opener Rules

Start the email with the signal. No warmup. No intro. No throat-clearing.

**Never open with:**
- "Quick question if you have 30 seconds"
- "I hope this finds you well"
- "I'm reaching out because"
- "My name is X and I work at Y"
- "Hope you're having a great week"
- "Just wanted to..."

The first word of the email should be related to the signal or the prospect. Not "I".

### Ask Rules

- 15 minutes max. Not "30 minutes". Not "a quick intro call"
- No calendar link in Email 1 — earn it first
- Frame as optional: "worth a quick look?" not "let's get something booked"
- Never use "demo" — use "teardown", "walkthrough", or "quick look"

---

## Email 2 — Proof

**Purpose:** New angle. Not a bump. Bring one piece of evidence they can't ignore.

**Structure:**
1. New opener — different style from Email 1 (question, observation, or contrarian take)
2. Proof point — specific outcome from a peer company, a stat, or a before/after
3. Low-friction re-ask

### Proof Point Rules

- Name a company in the same category, stage, or motion if possible
- Make the outcome specific: "12% more pipeline in 60 days" beats "significant improvement"
- If you can't name a peer, use a category-level claim anchored to a real number
- Never repaste Email 1 content. Never "as I mentioned". Treat this as if they never saw Email 1
- Start a new thread if the angle is substantially different

**Good proof examples:**
- "[Similar company] cut SDR ramp from 90 to 45 days after reworking their sequencing layer"
- "Most Series B SaaS teams we work with generate 3x the pipeline with the same headcount after fixing [specific thing] — happy to show you the playbook"

**Bad proof examples:**
- "We've helped many companies like yours improve their results" (no name, no number)
- "Our customers see great ROI" (meaningless)

---

## Email 3 — Clean Breakup

**Purpose:** Close the loop cleanly. Trigger loss-aversion without aggression. Make it easy to say yes or no.

**Rules:**
- ≤ 30 words. No pitch. No recap. No summary of the previous emails
- Acknowledge timing might be off
- Leave the door open without groveling

**Templates (lightly customize, don't use verbatim):**
- "Sounds like timing's off — should I close the loop?"
- "No worries if this isn't a priority right now. Happy to check back in [timeframe] if that changes."
- "I'll take the silence as a no for now. Feel free to reach back out if [relevant trigger] shifts."

**Never use in Email 3:**
- "Per my last email"
- "I just wanted to follow up"
- "I know you're busy" (condescending)
- "I've now reached out X times"
- Any pitch, proof point, or feature mention

---

## Banned Phrases

These mark an email as a template and kill reply rates. Cut on sight.

**Openers:**
- "Quick question if you have 30 seconds"
- "I hope this finds you well"
- "I'm reaching out because"
- "My name is X and I work at Y"
- "I came across your profile"
- "Hope you're having a great week / day / Monday"

**Body language:**
- Em-dashes (—) in body copy. Reads as AI-generated. Use a period or restructure.
- "Leveraging" → use: using, running, building
- "In today's fast-paced world"
- "Best-in-class"
- "Holistic approach" / "holistic solution"
- "End-to-end"
- "Synergies"
- "Unlock" as a verb ("unlock growth", "unlock efficiency")
- "Streamline"
- "Pain points" → use the actual problem by name
- "Value prop" → name the specific value
- "Circle back" / "touch base"
- "Move the needle"
- "At the end of the day"

---

## Subject Line Rules

- ≤ 5 words. Lowercase. No emoji. No exclamation points
- Write like a peer, not a marketer
- Don't include the company name — signals automation
- Never "Following up" or "Re: [nothing]"

**Good patterns:**

| Pattern | Example |
|---------|---------|
| Trigger reference | `saw the series b` |
| Their specific problem | `attribution gap?` |
| Peer reference | `how [similar company] fixed this` |
| Open question | `still using [tool]?` |
| Contrarian take | `less pipeline, more revenue` |

---

## Length Enforcement

Count words before finalizing. If over limit, cut — never compress.

| Email | Max words | Reason |
|-------|-----------|--------|
| 1 | 80 | First impression; earn the read |
| 2 | 90 | Room for one proof point |
| 3 | 30 | Brevity triggers response |

Short emails signal confidence. Long emails signal desperation.

---

## Pre-Send Checklist

Run before finalizing any sequence:

- [ ] Email 1 has a specific, real, verifiable signal
- [ ] Email 1 has no calendar link
- [ ] Email 1 does not start with "I"
- [ ] Email 2 uses a different opener style from Email 1
- [ ] Email 2 has a named proof point (company or stat)
- [ ] Email 3 is ≤ 30 words with no pitch
- [ ] No banned phrases appear in any email
- [ ] Subject lines are ≤ 5 words and lowercase
- [ ] No em-dashes in body copy
- [ ] "Demo" does not appear — replaced with teardown / walkthrough / look
- [ ] Each email is under its word limit

---

## Anti-Pattern Check

- Could this email send to 100 other people unchanged? → Rewrite Email 1's signal
- Did you make a claim about their business you can't back up? → Cut it
- Did you ask for more than 15 minutes? → Reduce
- Is the proof point vague ("many customers", "great results")? → Add a number or a company name
- Does Email 3 contain any pitch? → Strip it entirely
- Did you use an em-dash anywhere? → Replace with a period or restructure the sentence