Suede Cold Email Writing
Use this Suede cold-email playbook to write concise, evidence-grounded outreach that sounds human and respects the recipient.
Before Writing
Check for product marketing context first:
If .agents/product-marketing.md exists (or .claude/product-marketing.md, or the legacy product-marketing-context.md filename, in older setups), read it before asking questions. Use that context and only ask for information not already covered or specific to this task.
Understand the situation (ask if not provided):
- Who are you writing to? — Role, company, why them specifically
- What do you want? — The outcome (meeting, reply, intro, demo)
- What's the value? — The specific problem you solve for people like them
- What's your proof? — A result, case study, or credibility signal
- Any research signals? — Funding, hiring, LinkedIn posts, company news, tech stack changes
Work with whatever the user gives you. If they have a strong signal and a clear value prop, that's enough to write. Don't block on missing inputs — use what you have and note what would make it stronger.
Writing Principles
Write like a peer, not a vendor
The email should read like it came from someone who understands their world — not someone trying to sell them something. Use contractions. Read it aloud. If it sounds like marketing copy, rewrite it.
Every sentence must earn its place
Cold email is ruthlessly short. If a sentence doesn't move the reader toward replying, cut it. The best cold emails feel like they could have been shorter, not longer.
Personalization must connect to the problem
If you remove the personalized opening and the email still makes sense, the personalization isn't working. The observation should naturally lead into why you're reaching out.
See personalization.md for the 4-level system and research signals.
Lead with their world, not yours
The reader should see their own situation reflected back. "You/your" should dominate over "I/we." Don't open with who you are or what your company does.
One ask, low friction
Interest-based CTAs ("Worth exploring?" / "Would this be useful?") beat meeting requests. One CTA per email. Make it easy to say yes with a one-line reply.
Voice & Tone
The target voice: A smart colleague who noticed something relevant and is sharing it. Conversational but not sloppy. Confident but not pushy.
Calibrate to the audience:
- C-suite: ultra-brief, peer-level, understated
- Mid-level: more specific value, slightly more detail
- Technical: precise, no fluff, respect their intelligence
What it should NOT sound like:
- A template with fields swapped in
- A pitch deck compressed into paragraph form
- A LinkedIn DM from someone you've never met
- An AI-generated email (avoid the telltale patterns: "I hope this email finds you well," "I came across your profile," "leverage," "synergy," "best-in-class")
Structure
There's no single right structure. Choose a framework that fits the situation, or write freeform if the email flows naturally without one.
Common shapes that work:
- Observation → Problem → Proof → Ask — You noticed X, which usually means Y challenge. We helped Z with that. Interested?
- Question → Value → Ask — Struggling with X? We do Y. Company Z saw [result]. Worth a look?
- Trigger → Insight → Ask — Congrats on X. That usually creates Y challenge. We've helped similar companies with that. Curious?
- Story → Bridge → Ask — [Similar company] had [problem]. They [solved it this way]. Relevant to you?
For the full catalog of frameworks with examples, see frameworks.md.
Subject Lines
Short, boring, internal-looking. The subject line's only job is to get the email opened — not to sell.
- 2-4 words, lowercase, no punctuation tricks
- Should look like it came from a colleague ("reply rates," "hiring ops," "Q2 forecast")
- No product pitches, no urgency, no emojis, no prospect's first name
See subject-lines.md for the full data.
Follow-Up Sequences
Each follow-up should add something new — a different angle, fresh proof, a useful resource. "Just checking in" gives the reader no reason to respond.
- 3-5 total emails, increasing gaps between them
- Each email should stand alone (they may not have read the previous ones)
- The breakup email is your last touch — honor it
See follow-up-sequences.md for cadence, angle rotation, and breakup email templates.
Quality Check
Before presenting, gut-check:
- Does it sound like a human wrote it? (Read it aloud)
- Would YOU reply to this if you received it?
- Does every sentence serve the reader, not the sender?
- Is the personalization connected to the problem?
- Is there one clear, low-friction ask?
What to Avoid
- Opening with "I hope this email finds you well" or "My name is X and I work at Y"
- Jargon: "synergy," "leverage," "circle back," "best-in-class," "leading provider"
- Feature dumps — one proof point beats ten features
- HTML, images, or multiple links
- Fake "Re:" or "Fwd:" subject lines
- Identical templates with only {{FirstName}} swapped
- Asking for 30-minute calls in first touch
- "Just checking in" follow-ups
Data & Benchmarks
The references contain performance data if you need to make informed choices:
- benchmarks.md — Reply rates, conversion funnels, expert methods, common mistakes
- personalization.md — 4-level personalization system, research signals
- subject-lines.md — Subject line data and optimization
- follow-up-sequences.md — Cadence, angles, breakup emails
- frameworks.md — All copywriting frameworks with examples
Use this data to inform your writing — not as a checklist to satisfy.
Boundaries
- Do not invent personalization, mutual connections, customer facts, results, urgency, or prior contact.
- Do not scrape prohibited data, expose sensitive personal information, or advise evasion of consent, spam, or platform rules.
- Do not send, schedule, enroll, or follow up with anyone without explicit authorization for the exact recipients and sequence.
- Do not decide that silence means consent; honor opt-outs and suppression lists before any execution.
Routing
- Need a qualified prospect list -> use
suede-prospecting.
- Need lifecycle or nurture email -> use
suede-emails.
- Need positioning context or collateral -> use
suede-product-marketing or suede-sales-enablement.
- Need CRM stages, lead routing, or suppression operations -> use
suede-revops.
- From those skills, route cold outbound message and follow-up writing back to
suede-cold-email.
1---2name: suede-cold-email3description: Suede-owned B2B cold-email discipline for evidence-based personalization, subject lines, opening lines, concise bodies, one clear CTA, and bounded follow-up sequences. Use when writing or repairing outbound email to qualified prospects. NOT FOR: building or qualifying the prospect list (use suede-prospecting), lifecycle or nurture email (use suede-emails), or broader sales collateral (use suede-sales-enablement).4---5
6# Suede Cold Email Writing
7
8Use this Suede cold-email playbook to write concise, evidence-grounded outreach that sounds human and respects the recipient.
9
10## Before Writing
11
12**Check for product marketing context first:**
13If `.agents/product-marketing.md` exists (or `.claude/product-marketing.md`, or the legacy `product-marketing-context.md` filename, in older setups), read it before asking questions. Use that context and only ask for information not already covered or specific to this task.
14
15Understand the situation (ask if not provided):
16
171. **Who are you writing to?** — Role, company, why them specifically
182. **What do you want?** — The outcome (meeting, reply, intro, demo)
193. **What's the value?** — The specific problem you solve for people like them
204. **What's your proof?** — A result, case study, or credibility signal
215. **Any research signals?** — Funding, hiring, LinkedIn posts, company news, tech stack changes
22
23Work with whatever the user gives you. If they have a strong signal and a clear value prop, that's enough to write. Don't block on missing inputs — use what you have and note what would make it stronger.
24
25---
26
27## Writing Principles
28
29### Write like a peer, not a vendor
30
31The email should read like it came from someone who understands their world — not someone trying to sell them something. Use contractions. Read it aloud. If it sounds like marketing copy, rewrite it.
32
33### Every sentence must earn its place
34
35Cold email is ruthlessly short. If a sentence doesn't move the reader toward replying, cut it. The best cold emails feel like they could have been shorter, not longer.
36
37### Personalization must connect to the problem
38
39If you remove the personalized opening and the email still makes sense, the personalization isn't working. The observation should naturally lead into why you're reaching out.
40
41See [personalization.md](references/personalization.md) for the 4-level system and research signals.
42
43### Lead with their world, not yours
44
45The reader should see their own situation reflected back. "You/your" should dominate over "I/we." Don't open with who you are or what your company does.
46
47### One ask, low friction
48
49Interest-based CTAs ("Worth exploring?" / "Would this be useful?") beat meeting requests. One CTA per email. Make it easy to say yes with a one-line reply.
50
51---
52
53## Voice & Tone
54
55**The target voice:** A smart colleague who noticed something relevant and is sharing it. Conversational but not sloppy. Confident but not pushy.
56
57**Calibrate to the audience:**
58
59- C-suite: ultra-brief, peer-level, understated
60- Mid-level: more specific value, slightly more detail
61- Technical: precise, no fluff, respect their intelligence
62
63**What it should NOT sound like:**
64
65- A template with fields swapped in
66- A pitch deck compressed into paragraph form
67- A LinkedIn DM from someone you've never met
68- An AI-generated email (avoid the telltale patterns: "I hope this email finds you well," "I came across your profile," "leverage," "synergy," "best-in-class")
69
70---
71
72## Structure
73
74There's no single right structure. Choose a framework that fits the situation, or write freeform if the email flows naturally without one.
75
76**Common shapes that work:**
77
78- **Observation → Problem → Proof → Ask** — You noticed X, which usually means Y challenge. We helped Z with that. Interested?
79- **Question → Value → Ask** — Struggling with X? We do Y. Company Z saw [result]. Worth a look?
80- **Trigger → Insight → Ask** — Congrats on X. That usually creates Y challenge. We've helped similar companies with that. Curious?
81- **Story → Bridge → Ask** — [Similar company] had [problem]. They [solved it this way]. Relevant to you?
82
83For the full catalog of frameworks with examples, see [frameworks.md](references/frameworks.md).
84
85---
86
87## Subject Lines
88
89Short, boring, internal-looking. The subject line's only job is to get the email opened — not to sell.
90
91- 2-4 words, lowercase, no punctuation tricks
92- Should look like it came from a colleague ("reply rates," "hiring ops," "Q2 forecast")
93- No product pitches, no urgency, no emojis, no prospect's first name
94
95See [subject-lines.md](references/subject-lines.md) for the full data.
96
97---
98
99## Follow-Up Sequences
100
101Each follow-up should add something new — a different angle, fresh proof, a useful resource. "Just checking in" gives the reader no reason to respond.
102
103- 3-5 total emails, increasing gaps between them
104- Each email should stand alone (they may not have read the previous ones)
105- The breakup email is your last touch — honor it
106
107See [follow-up-sequences.md](references/follow-up-sequences.md) for cadence, angle rotation, and breakup email templates.
108
109---
110
111## Quality Check
112
113Before presenting, gut-check:
114
115- Does it sound like a human wrote it? (Read it aloud)
116- Would YOU reply to this if you received it?
117- Does every sentence serve the reader, not the sender?
118- Is the personalization connected to the problem?
119- Is there one clear, low-friction ask?
120
121---
122
123## What to Avoid
124
125- Opening with "I hope this email finds you well" or "My name is X and I work at Y"
126- Jargon: "synergy," "leverage," "circle back," "best-in-class," "leading provider"
127- Feature dumps — one proof point beats ten features
128- HTML, images, or multiple links
129- Fake "Re:" or "Fwd:" subject lines
130- Identical templates with only {{FirstName}} swapped
131- Asking for 30-minute calls in first touch
132- "Just checking in" follow-ups
133
134---
135
136## Data & Benchmarks
137
138The references contain performance data if you need to make informed choices:
139
140- [benchmarks.md](references/benchmarks.md) — Reply rates, conversion funnels, expert methods, common mistakes
141- [personalization.md](references/personalization.md) — 4-level personalization system, research signals
142- [subject-lines.md](references/subject-lines.md) — Subject line data and optimization
143- [follow-up-sequences.md](references/follow-up-sequences.md) — Cadence, angles, breakup emails
144- [frameworks.md](references/frameworks.md) — All copywriting frameworks with examples
145
146Use this data to inform your writing — not as a checklist to satisfy.
147
148---
149
150## Boundaries
151
152- Do not invent personalization, mutual connections, customer facts, results, urgency, or prior contact.
153- Do not scrape prohibited data, expose sensitive personal information, or advise evasion of consent, spam, or platform rules.
154- Do not send, schedule, enroll, or follow up with anyone without explicit authorization for the exact recipients and sequence.
155- Do not decide that silence means consent; honor opt-outs and suppression lists before any execution.
156
157## Routing
158
159- Need a qualified prospect list -> use `suede-prospecting`.
160- Need lifecycle or nurture email -> use `suede-emails`.
161- Need positioning context or collateral -> use `suede-product-marketing` or `suede-sales-enablement`.
162- Need CRM stages, lead routing, or suppression operations -> use `suede-revops`.
163- From those skills, route cold outbound message and follow-up writing back to `suede-cold-email`.