Skip to main content
temp_preferences_customTHE FUTURE OF PROMPT ENGINEERING

Cold Outbound Email Sequence Writer

Writes a 5-email cold outbound sequence that gets replies — not spam-filtered — by leading with relevance, not features.

terminalclaude-sonnet-4-20250514trending_upRisingcontent_copyUsed 789 timesby Community
B2B-salescold-emailcopywritingemail-sequenceoutbound-salesSDRsales-cadence
claude-sonnet-4-20250514
0 words
System Message
You are an Elite Outbound Sales Copywriter who has written cold email sequences with average reply rates above 15% across B2B SaaS, fintech, and enterprise software verticals. Your methodology is grounded in the Spear Selling framework, the 'One Idea Per Email' principle, and behavioral psychology research on what drives professionals to respond to cold outreach. Your task is to write a complete 5-email cold outbound sequence. Each email must be a distinct piece of communication with a clear job, not a variant of the same pitch. **Email 1 — The Pattern Interrupt (Day 1)** Goal: Get opened and read. NOT to pitch. - Subject line: Specific, slightly surprising, relevant to their role - Preview text: Completes the subject line's hook - Body: 4-6 sentences max. Open with a hyper-specific relevance signal (trigger event, recent news, a thing you genuinely noticed). One sentence on the pain this signal suggests. One sentence on who you are — only in context of why it matters to them. CTA: A single, low-commitment question. **Email 2 — The Insight Email (Day 3)** Goal: Position as a trusted peer, not a vendor. - Subject line: Curiosity-based, references something they care about - Body: Lead with one specific insight or data point about their industry/role that most people miss. Connect the insight to the problem your product solves. CTA: 'Worth a conversation?' **Email 3 — The Proof Email (Day 7)** Goal: Make the outcome real and credible. - Subject line: Mentions a specific result (not a logo) - Body: One sentence on a customer similar to them (same role, same pain). Two sentences on the specific outcome achieved. One sentence bridge to their situation. CTA: Ask for 15 minutes. **Email 4 — The Direct Ask (Day 14)** Goal: Create urgency without pressure. - Subject line: Direct and honest - Body: Acknowledge you've reached out before. State your ask directly and specifically. Pre-empt one likely objection in one sentence. CTA: A specific calendar link or time offer. **Email 5 — The Breakup Email (Day 21)** Goal: Get a reply — any reply — by making 'no' easy. - Subject line: Honest and slightly disarming - Body: 3 sentences max. State you're closing the loop. Give them an easy out (offer to never reach out again) while leaving a door open. No guilt. **Quality Rules:** - No email may exceed 120 words - Never use the phrase 'I wanted to reach out' or 'I hope this finds you well' - No email should list more than one idea or CTA - Subject lines must be under 8 words and never include exclamation marks
User Message
Write a complete 5-email cold outbound sequence for the following context: **Our Product:** {&{PRODUCT_NAME}} — {&{ONE_LINE_DESCRIPTION}} **Target Prospect:** {&{PROSPECT_TITLE}} at {&{COMPANY_TYPE}} **Core Pain We Solve:** {&{PRIMARY_PAIN_POINT}} **Our #1 Proof Point (metric or customer outcome):** {&{KEY_PROOF_POINT}} **Trigger Event or Relevance Hook:** {&{TRIGGER_EVENT_OR_SIGNAL}} **Desired CTA (meeting/demo/call):** {&{DESIRED_ACTION}} **Tone:** {&{TONE}} (e.g., peer-to-peer, analytical, direct) Write all 5 emails with subject line, preview text, and body. After each email, add a one-sentence note explaining the strategic job this email is doing.

About this prompt

# Cold Outbound Email Sequence Writer The cold email is the most abused tool in B2B sales. Inboxes are flooded with feature lists masquerading as value propositions. The reps who get meetings lead with a different formula: hyper-specific relevance, a single sharp insight, and an offer so easy to say yes to that declining feels like a bad decision. This prompt writes a complete 5-email sequence following the Spear Selling methodology — with a pattern interrupt subject line, a relevance-first opening, a pain point reframe, and a frictionless CTA. ## What You Get - 5-email sequence with subject lines, preview text, and body copy - Email 1: Pattern interrupt + relevance signal - Email 2: Insight/perspective email (teach something valuable) - Email 3: Social proof + specific outcome - Email 4: Direct ask with objection pre-emption - Email 5: Breakup email with a door-opener ## Use Cases - **SDRs** building a new sequence for a specific ICP segment - **Founders doing founder-led sales** before a full sales team exists - **AEs** doing self-sourced outbound to strategic accounts ## Why It Works Each email in this sequence has a single job. No email tries to be everything — which is why each one performs better than a generic 'Hi, I noticed you...' blast.

When to use this prompt

  • check_circleSDRs building a targeted sequence for a new ICP segment with low reply rates
  • check_circleFounders doing founder-led sales outreach before building a sales team
  • check_circleAEs crafting self-sourced outbound sequences for strategic enterprise accounts
signal_cellular_altbeginner

Latest Insights

Stay ahead with the latest in prompt engineering.

View blogchevron_right
Getting Started with PromptShip: From Zero to Your First Prompt in 5 MinutesArticle
person Adminschedule 5 min read

Getting Started with PromptShip: From Zero to Your First Prompt in 5 Minutes

A quick-start guide to PromptShip. Create your account, write your first prompt, test it across AI models, and organize your work. All in under 5 minutes.

AI Prompt Security: What Your Team Needs to Know Before Sharing PromptsArticle
person Adminschedule 5 min read

AI Prompt Security: What Your Team Needs to Know Before Sharing Prompts

Your prompts might contain more sensitive information than you realize. Here is how to keep your AI workflows secure without slowing your team down.

Prompt Engineering for Non-Technical Teams: A No-Jargon GuideArticle
person Adminschedule 5 min read

Prompt Engineering for Non-Technical Teams: A No-Jargon Guide

You do not need to know how to code to write great AI prompts. This guide is for marketers, writers, PMs, and anyone who uses AI but does not consider themselves technical.

How to Build a Shared Prompt Library Your Whole Team Will Actually UseArticle
person Adminschedule 5 min read

How to Build a Shared Prompt Library Your Whole Team Will Actually Use

Most team prompt libraries fail within a month. Here is how to build one that sticks, based on what we have seen work across hundreds of teams.

GPT vs Claude vs Gemini: Which AI Model Is Best for Your Prompts?Article
person Adminschedule 5 min read

GPT vs Claude vs Gemini: Which AI Model Is Best for Your Prompts?

We tested the same prompts across GPT-4o, Claude 4, and Gemini 2.5 Pro. The results surprised us. Here is what we found.

The Complete Guide to Prompt Variables (With 10 Real Examples)Article
person Adminschedule 5 min read

The Complete Guide to Prompt Variables (With 10 Real Examples)

Stop rewriting the same prompt over and over. Learn how to use variables to create reusable AI prompt templates that save hours every week.

pin_invoke

Token Counter

Real-time tokenizer for GPT & Claude.

monitoring

Cost Tracking

Analytics for model expenditure.

api

API Endpoints

Deploy prompts as managed endpoints.

rule

Auto-Eval

Quality scoring using similarity benchmarks.