Sales Email Sequences

Sales Email Sequences

Design end-to-end outbound email sequences that move prospects from cold outreach to booked meetings. This skill builds persona-targeted messaging across multiple touches — intros, follow-ups, value-adds, and breakup emails — with personalization tokens, subject line variants, and send-timing cadences optimized for reply rates.

Workflow

1. Define ICP and Persona — Establish the ideal customer profile (industry, company size, revenue range, geography) and the target persona (title, seniority, responsibilities, pain points). This determines tone, vocabulary, value framing, and which proof points resonate.

2. Craft the Core Value Proposition — Distill your product's relevance to this persona into a single compelling statement. Focus on a specific, measurable outcome (e.g., "reduce month-end close from 10 days to 3") rather than feature lists. This value prop threads through every email in the sequence.

3. Write the Email Sequence — Build a multi-touch sequence: an opening email that earns attention with a relevant hook, follow-ups that introduce new angles or proof points, a value-add email offering a resource, and a breakup email that creates urgency through finality. Each email should be 50–120 words in the body.

4. Add Personalization Tokens — Insert dynamic fields for prospect name, company, industry, recent trigger events (funding rounds, job changes, earnings calls), and any known tech stack details. Personalization beyond {{first_name}} dramatically lifts reply rates.

5. Set Timing and Cadence — Define send days, times, and intervals between touches. B2B sequences typically perform best with Tuesday–Thursday sends between 8–10 AM local time, with 2–4 day gaps between early touches and longer gaps (5–7 days) before the breakup.

Usage

Specify the target persona, your product/service, the core pain point you solve, and desired sequence length. Optionally include trigger events or specific personalization data.

Example prompt:

Create a 5-email cold outreach sequence targeting VP of Engineering at Series B+ SaaS companies. We sell an automated code review platform that cuts PR review time by 60%. Include subject lines, body copy, and send timing for each email.

Examples

Example 1: 5-Email Cold Outreach Sequence (B2B SaaS)

Target: VP of Engineering at Series B+ SaaS companies (100–500 employees) Product: Automated code review platform Value prop: Cut PR review time by 60%, ship 2x faster

---

Email 1 — The Hook (Day 1, Tuesday 9:00 AM)

Subject: {{company}}'s PR bottleneck

Hi {{first_name}},

Saw {{company}} just shipped {{recent_launch}} — congrats. Curious if your team is feeling the review bottleneck that usually comes with scaling engineering velocity post-Series B.

Our platform plugs into your existing GitHub workflow and automates 60% of code review — teams our size typically cut PR cycle time from 24 hours to under 4.

Worth a 15-min look? I can show you results from {{similar_company}} in your space.

Best, {{sender_name}}

---

Email 2 — Social Proof (Day 3, Thursday 8:30 AM)

Subject: How {{similar_company}} ships 2x faster

{{first_name}}, quick follow-up.

{{similar_company}} was averaging 22-hour PR cycle times with a 40-person eng team. After deploying our automated review, they dropped to 3.5 hours and increased weekly deploys by 94%.

Happy to share their playbook — no strings.

{{sender_name}}

---

Email 3 — Value-Add (Day 7, Monday 9:00 AM)

Subject: Code review benchmarks for {{industry}} teams

{{first_name}},

We just published our 2025 Engineering Velocity Report — covers review cycle benchmarks across 200+ SaaS teams your size.

Key finding: top-quartile teams automate 55%+ of review comments. Bottom quartile still relies on fully manual review and ships 3.2x slower.

Here's the report: [link]

Useful regardless of whether we chat — but if the data resonates, I'd love to show how we help teams move from bottom to top quartile in weeks.

{{sender_name}}

---

Email 4 — New Angle (Day 11, Friday 8:00 AM)

Subject: Developer satisfaction at {{company}}

{{first_name}},

One thing that doesn't show up in cycle-time metrics: developer frustration. Our latest survey found that 72% of engineers rank "waiting on code review" as their top workflow blocker.

If retention and developer experience are on your radar this year, automating the review bottleneck is low-hanging fruit with outsized impact.

Open to a quick call next week?

{{sender_name}}

---

Email 5 — Breakup (Day 16, Wednesday 9:00 AM)

Subject: Closing the loop

{{first_name}},

I've reached out a few times and haven't heard back — totally understand if the timing isn't right.

I'll leave you with this: {{company}} can trial our platform free for 30 days on a single repo, no integration work required. If review speed becomes a priority, you'll know where to find us.

Wishing you and the {{company}} team a strong quarter.

{{sender_name}}

---