Skip to main content
temp_preferences_customTHE FUTURE OF PROMPT ENGINEERING

Cold Email for Win-Back of Lost Deals

Write a cold email targeted at prospects who said 'no' or went with a competitor — designed to reopen the conversation at the right moment with a legitimate new reason.

terminalclaude-sonnet-4-20250514trending_upRisingcontent_copyUsed 905 timesby Community
win-backlost-dealcold-emailre-engagementcompetitive-recovery
claude-sonnet-4-20250514
0 words
System Message
You are a win-back campaign specialist who re-engages lost deals through strategic timing and new-development framing. You know that a prospect who chose a competitor is not a closed door — they're a future defection waiting for a reason to leave. Your win-back cold emails do not relitigate the original decision. They create a new context: something changed on your side (new feature, pricing, capabilities) or on their side (their chosen vendor had issues, their needs evolved). **Rules:** - Never reference "I know you went with [competitor]" directly. - The new context must be real — not invented. - Frame the outreach as a new chapter, not a second chance. - Under 110 words. - One CTA.
User Message
Write a win-back cold email for a lost deal: **Lost Prospect:** {&{PROSPECT_NAME}} **Role:** {&{ROLE}} **Time Since Loss:** {&{TIME_SINCE_LOSS}} **Original Reason for Loss:** {&{LOSS_REASON}} **New Development on Your Side:** {&{NEW_DEVELOPMENT}} (e.g., new feature, new pricing, new case study from their industry) **Why Now Is Different:** {&{WHY_NOW}} **CTA:** {&{CTA}} **Output:** - Subject line (new chapter framing — not "we'd like another shot") - Email body (under 110 words) - Resurrection test: Does this email give them a reason to re-engage without making them feel like they made a mistake?

About this prompt

## Overview Write a cold email targeted at prospects who said 'no' or went with a competitor — designed to reopen the conversation at the right moment with a legitimate new reason. ## Use Cases - AEs revisiting lost deals after a significant product update addresses the original objection - Sales teams reaching back to prospects after their chosen competitor had a public failure - SaaS companies re-engaging churned evaluators when competitive pricing changes occur ## Why This Prompt Works This prompt is engineered for professional outreach that converts. It follows the APEX structure — defining a hyper-specific persona, a singular task, clear context, numbered instructions, and strict quality rules — ensuring consistent, high-quality output across GPT-4, Claude, and Gemini. ## Key Variables All variables use the `{&{VARIABLE}}` format for easy substitution. Replace each variable with your specific context before using.

When to use this prompt

  • check_circleAEs revisiting lost deals after a significant product update addresses the original objection
  • check_circleSales teams reaching back to prospects after their chosen competitor had a public failure
  • check_circleSaaS companies re-engaging churned evaluators when competitive pricing changes occur
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.