Win-Back Emails That Actually Win: A Lifecycle Playbook
A win-back flow built as a discount ladder on a generic timer can arrive too late. A practical sequence — timing, message angles, and the metric that tells you when to stop.
A win-back email sent on a generic timer can land months after the customer stopped being a customer. The playbook below is built on one principle: win-back begins before churn, not after.
Define "lapsed" from your own data
Forget generic 90-day rules. Pull the distribution of gaps between orders; your risk threshold is roughly the 80th percentile of that gap. If 80% of repeat purchases happen within 45 days, a customer at day 50 is already unusual — that is when the sequence starts, not at day 90 when the habit is gone.
The four-touch sequence
- The nudge (at risk threshold). No discount. Best-sellers, what's new, a reason to visit. You are testing whether attention, not price, was the problem — and protecting margin on everyone this recovers.
- The reason-why (7–10 days later). Address the actual objection: restock reminders for consumables, social proof for considered purchases, sizing/fit help for apparel. Segment if you can; even two variants beat one generic blast.
- The offer (10–14 days later). Now the discount — single-use, expiring, and meaningful (pick the depth your margin floor allows, then let the holdout tell you whether it moved anyone). One offer, one deadline, no stacking.
- The goodbye (30+ days later). "We'll stop emailing." Honest, and it can prompt a last spike of recoveries while cleaning your list — deliverability is a retention asset too.
Measure incrementality or measure nothing
Hold out 10% of each lapsed segment from the entire sequence. Revenue per recipient versus holdout is the only number that justifies the discounts. Do not assume which step is doing the work: the nudge and goodbye emails can outperform expectations while the discount step does less than it appears — which is exactly why you test.
Win-back is the highest-leverage flow in lifecycle marketing because the audience already trusted you once. Treat it as a system with a clock, not a coupon with a subject line.
Setting the clock from your own data
Pull every customer with at least two orders and list the gap in days between consecutive orders. Sort those gaps and read the 80th percentile. If 80% of repeat orders land within 38 days, 38 is your risk threshold — not 90, and not whatever the last agency deck said.
Now hang the sequence off it. The nudge goes at day 38, the reason-why around day 46, the offer at day 58, the goodbye at day 90. Every date derives from one measured number, which is what makes the schedule defensible when someone asks why the discount fires when it does.
Two things distort that percentile, and both matter. Customers with a single order are not in the distribution at all, so the number describes people who already repeat: it is a threshold for at-risk repeaters, and one-time buyers need a different flow entirely. And seasonal categories produce a gap distribution with two humps rather than one — if you see that, split the calculation by season instead of averaging into a threshold that fits neither.
Recompute quarterly until the number stops moving. A threshold nobody has checked in a year is a generic rule with extra steps.
Frequently asked questions
I do not have enough order history to compute the 80th percentile. Now what?
Use the distribution you have and mark the threshold as provisional. With a few hundred repeat orders you can still see where the mass of gaps sits, even while the exact percentile keeps moving. What does not work is importing a 90-day rule from another category: the gap distribution for coffee and the one for mattresses have nothing to say to each other.
Should the goodbye email actually unsubscribe them?
It should stop the marketing stream, because that is the promise it makes. Keep transactional and service messages running — different basis, different expectation. Suppressing rather than deleting also preserves the record you need if that customer returns through another channel and someone has to explain why they stopped hearing from you.
Do consumables and considered purchases use the same sequence?
Same shape, different clock and a different second touch. For consumables the risk threshold is a replenishment interval and the reason-why message is a restock reminder, which can recover the customer before any discount is needed. For considered purchases the normal gap is long enough that lapse and patience look identical, so the sequence matters less than fixing why the second purchase had no trigger in the first place.