Skip to main content
temp_preferences_customTHE FUTURE OF PROMPT ENGINEERING

Cold Email Follow-Up Sequence: 3-Touch Cadence After No Response

Generate a 3-touch follow-up sequence for a cold email that received no response — each touch escalating value, changing the angle, and maintaining dignity. Designed to maximize reply rates without burning bridges or signaling desperation.

terminalclaude-sonnet-4-20250514trending_upRisingcontent_copyUsed 738 timesby Community
follow-up-sequencecold-email-cadenceno-response-emailemail-follow-upoutbound-salesb2b-emailsales-cadence
claude-sonnet-4-20250514
0 words
System Message
You are a follow-up cadence strategist who understands that the follow-up email is statistically more likely to get a reply than the initial cold email — but only if it does something the first one didn't. You know the cardinal rule of follow-up: never repeat yourself. Each touch must reframe, re-angle, or add new value. You write sequences that feel like a thoughtful professional following up — not a bot running a cadence. Your sequences have a beginning, middle, and end — and the final touch always closes with grace, not guilt.
User Message
Create a 3-touch follow-up sequence for a cold email that has received no response. **Original Email Summary:** {&{ORIGINAL_EMAIL_SUMMARY}} **Prospect Name:** {&{PROSPECT_NAME}} **Prospect Role:** {&{PROSPECT_ROLE}} **Company:** {&{PROSPECT_COMPANY}} **Your Product/Service:** {&{YOUR_PRODUCT}} **Original CTA:** {&{ORIGINAL_CTA}} **What You Can Add in Follow-Ups:** {&{NEW_VALUE_ANGLES}} (e.g., new case study, different pain angle, softer CTA) **Instructions:** 1. **Touch 2 (Day 3–4):** Reframe — don't repeat. Change the angle. Lead with a new proof point, a relevant stat, or a different pain framing. Keep it under 80 words. 2. **Touch 3 (Day 7–8):** Pattern interrupt. Use a different format — shorter, more direct, almost conversational. Sometimes a 3-sentence email outperforms a structured one. Keep under 60 words. 3. **Touch 4 (Day 14):** Graceful breakup. Tell them you're stepping back. Leave a door open. Make them feel respected, not chased. Under 50 words. Never passive-aggressive. **Output Format:** - Each touch with: Timing | Subject | Body | Rationale (1 line) **Quality Rules:** - Touch 2 must bring genuinely new information or framing — no recycling. - Touch 3 must feel human, not automated. - Touch 4 must NOT contain the phrase "closing the file", "last attempt", or any guilt-signaling language.

About this prompt

## 3-Touch Cold Email Follow-Up Cadence The data is clear: most replies come from follow-ups, not initial emails. The problem is that most follow-up sequences are lazy — they repeat the same message in a slightly different font and call it a cadence. This prompt builds a 3-touch follow-up sequence engineered around a core principle: **every touch must earn its send**. Each email has a different angle, a different format, and a different emotional register — moving from proof-led, to conversational, to graceful exit. ### The Sequence Logic - **Touch 2:** Proof and reframe — new evidence, different angle - **Touch 3:** Pattern interrupt — shorter, more human, less structured - **Touch 4:** Graceful close — dignity preserved, door left open ### Use Cases 1. **BDR teams** who need a replicable follow-up cadence that doesn't burn the list 2. **Founders doing direct outbound** who want a systematic but human-feeling follow-up approach 3. **Recruiters doing outbound candidate sourcing** who need a respectful, professional cadence that doesn't alienate passive candidates ### Expected Output Three fully-written follow-up emails with send timing, subject line, body, and a one-line rationale for each.

When to use this prompt

  • check_circleBDR teams building replicable follow-up cadences that don't exhaust the prospect list
  • check_circleFounders doing direct outbound who need a human-feeling follow-up system
  • check_circleRecruiters using outbound candidate sourcing who want dignified, professional cadences
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.