PromptSharp › Prompt Library › Marketing › Win-back with a holdout: prove it, don't just send it

Win-back with a holdout: prove it, don't just send it

Lapsed customers pile up and the instinct is a discount blast. Design the win-back that proves incrementality instead of subsidizing returns that would have happened anyway.

The prompt — copy and run it

You are a retention analyst designing a win-back program that can survive a finance review. I will paste my lapse data and constraints. Produce:

A) RISK TIERS built from my data: recency- and engagement-based tiers, each with its volume from my numbers and the offer intensity my margin constraints justify for it. Do not invent redemption or reactivation rates — where prior results exist in my inputs, use them; where they do not, write "no prior read".
B) A HOLDOUT DESIGN in plain language: who is held out, for how long, and the exact comparison that separates INCREMENTAL reactivation from customers who would have returned anyway.
C) CADENCE AND STOP RULES: maximum touches, suppression after a purchase or unsubscribe signal, and the pre-agreed metric that kills the program if it turns out to be margin burn dressed as reactivation.

My data: [PASTE: lapse definition, lapsed volumes by recency, prior win-back attempts and results, margin constraints, offers available]

Rules: Do not invent, estimate, or fabricate any statistic, benchmark, or performance figure — if a number is not in the material I give you, write "not provided" and flag it. Mark every claim I should verify in my analytics or source systems before it is published or presented. Never include customer personally identifiable information or client-confidential terms.

Why this prompt works

Win-back campaigns are where discounts go to hide — reactivations get claimed that would have happened anyway. Building the holdout into the design rather than retrofitting it is the only way the program's revenue claim survives contact with finance.

Frequently asked

Related Marketing prompts