Break-up email to close a dead sequence
Use as the final touch of a sequence to either revive a cold prospect or cleanly close the loop.
You write break-up emails that get more replies than the rest of the sequence because they are honest and ego-free.
Prospect: {{prospect_name}} at {{company}}
How many times I've reached out: {{touch_count}}
What I sell: {{offer}}
Write a break-up email that:
- Acknowledges the silence without guilt-tripping.
- Offers a graceful exit ("should I close your file?").
- Gives one last reason this might still matter, in a single line.
- Asks a binary question that is easy to answer either way.
Under 70 words. No passive aggression, no fake "final notice". Subject line under 4 words.Click the copy button in the top right of the block to grab the full prompt.
Replace each placeholder below with your own values before you run the prompt.
- {{prospect_name}}
- {{company}}
- {{touch_count}}
- {{offer}}
Related prompts
You are an experienced B2B sales rep who writes short, human cold emails that get replies. Write a first-touch cold email to {{prospect_name}}, who is {{prospect_role}} at {{prospe...
You are a sales copywriter. Create three distinct cold email variations for the same prospect so I can A/B test them. Prospect: {{prospect_role}} at {{prospect_company}} What I sel...
You write natural LinkedIn connection notes that do not feel like a pitch. Write a connection request note to {{prospect_name}}, {{prospect_role}} at {{prospect_company}}. Reason f...
You are a social-selling expert. Build a 4-message LinkedIn DM sequence for a prospect who just accepted my connection request. Prospect: {{prospect_role}} at {{prospect_company}}...
You write follow-up emails that add value rather than nag. Write a follow-up to {{prospect_name}} who did not reply to my first email. Original email was about: {{original_topic}}...
You are a sales cadence specialist. Design a 5-email follow-up sequence for a cold prospect. Prospect type: {{prospect_role}} at companies like {{target_company_profile}} What I se...
0 Comments
Loading discussion...