Your day-60 win-back is declaring quarterly buyers dead
Loyalty

Your day-60 win-back is declaring quarterly buyers dead

A fixed lapse window reaches monthly buyers a month late and interrupts quarterly buyers who were never gone. Timing win-back to each customer's own interval, and splitting it by why they left.

Most win-back programs run on a number somebody picked once. Sixty days, ninety days, whatever the platform suggested at implementation. Everyone past that line gets the lapsed treatment.

That single number is wrong for nearly every customer it touches, and it is wrong in both directions at the same time.

Lapse is relative to the customer, not the calendar

A customer who has ordered every four weeks for a year is meaningfully gone at six weeks. Your day-60 trigger reaches them two weeks after they had already stopped, which is exactly the wrong side of the decision.

A customer who orders quarterly is not lapsed at day 60. They are between orders, doing precisely what they have always done. Your win-back email arrives to tell them you noticed their absence, which they will find puzzling, and it usually arrives with a discount attached, which they will find educational. You have just taught a perfectly healthy customer that not buying for a while produces an offer.

Both errors come from the same source: lapse defined against a site-wide average rather than the customer’s own rhythm. The fix is not sophisticated. Compute each customer’s established interval, flag them when they exceed it by a meaningful multiple, and let the trigger be personal. Businesses with wide interval variance, which is most of them, see the biggest gains from this and generally have the least trouble computing it.

Split by reason, not by recency

The second failure is treating everyone past the line as one audience. There are at least three groups here, and they need different messages.

The drifted. No dramatic cause. Frequency slipped, attention moved, nothing broke. This group responds to a reason to come back and often to nothing more than a well-timed reminder of something relevant. It is also the group most likely to return unprompted, which matters enormously for measurement.

The completed. They got what they came for. The project finished, the child outgrew the size, the need ended. Asking them to come back for the same thing is asking them to have a need they do not have. If there is an adjacent offer, that is the play. If there is not, the honest response is to stop spending on them, which no win-back program ever seems willing to do.

The dissatisfied. They had a bad experience and left because of it. This group is actively harmed by a cheerful discount email, which reads as an offer to sell them the problem again at a reduced price. What works here is acknowledgment, and a specific statement of what changed. What does not work is pretending the reason never happened.

And before any of that: pull the involuntary churn out entirely. Customers whose payment failed did not decide to leave. They belong in payment recovery, where the recovery rate is several times higher and the cost is operational rather than promotional. Leaving them in the win-back audience is both wasteful and slightly insulting.

The discount reflex, and what it costs

Discount-led win-back has a reliable failure mode: it works well enough to look successful, recovers customers at negative contribution, and teaches the base that lapsing is rewarded.

The contribution point is worth being concrete about. A recovered customer who churns again within two cycles is worth very little, and a deep offer to acquire that outcome is a loss dressed as a save. Size the offer against the contribution the customer is actually expected to generate from here, which for a short-tenure re-lapser is a small number. The Cohort Payback Calculator is a fast way to see what a recovered customer’s remaining curve is worth before deciding what to spend on them.

The behavioral point is slower and worse. Brands that lean on lapse discounting eventually find they have trained a segment to lapse on a schedule, and that pattern is very hard to unwind once it is established.

Lead with something else where you can. A real change since they left. A removed friction. A product that addresses the reason they went. For the dissatisfied group, an acknowledgment that costs nothing and lands better than any percentage off.

Hold out a slice, permanently

A meaningful share of lapsed customers return on their own. People drift back to brands they like without being asked, and the share varies enough by category and interval that it cannot be assumed.

Without a control group, every one of those returns is counted as a save. With one, you get the actual number, which will be smaller and will be real. Keep the holdout permanently rather than running it once, because the natural return rate moves with seasonality, assortment, and everything else you change.

This is the same standard applied throughout loyalty and win-back, and it is the difference between a program and a report.

Where win-back belongs in the plan

Win-back deserves to exist and does not deserve to be the centerpiece. It intervenes after the decision, at the point of lowest leverage, with the fewest tools available. Its ceiling is low by construction.

The higher-return work sits upstream, in payment recovery, in the activation window, and in catching drift before the customer has concluded anything. A retention program spending most of its budget at the lapsed stage has chosen the easiest campaign to build over the most valuable one to run.

So a question for the next lifecycle review: is your lapse window a property of your customers, or a number someone typed into a platform during implementation?

Frequently asked questions

When should you send a win-back campaign?

Relative to each customer’s own established purchase interval rather than on a fixed number of days. A customer who has bought monthly for a year is meaningfully lapsed at around six weeks; a quarterly buyer at the same point is simply between orders. A single site-wide lapse window is guaranteed to be late for one group and premature for the other, and the premature contact is not harmless, it teaches customers that ignoring you produces an offer.

How do you segment a win-back campaign?

By why the customer left, not by how long they have been gone. The customer who drifted, the customer who completed what they came for, and the customer who was actively dissatisfied need different messages, and sending all three the same discount insults the third group and gives away margin to the second. Involuntary churn should be pulled out entirely; it belongs in payment recovery, not in win-back.

What is a good win-back offer?

Frequently not an offer at all. A genuine change since they left, a removed friction, a new product that addresses their reason for leaving, or a direct acknowledgment for the dissatisfied group will often outperform a discount and will always cost less. Where a discount is right, size it against the contribution the recovered customer is actually expected to generate, which for a short-tenure re-lapser is not much.

How many lapsed customers come back on their own?

Enough to invalidate any win-back result read without a control group. Customers drift back to brands they like without being asked, and a campaign with no holdout counts every one of those as a save. The share varies by category and interval, which is exactly why it has to be measured rather than assumed.

Is win-back worth running at all?

Yes, for the customers earlier work did not catch, and with realistic expectations. It is the lowest-leverage moment in the lifecycle because the decision is already made and the remaining tool is usually price. That makes it a legitimate last resort and a poor centerpiece. A program spending most of its retention budget at this stage is working the cheapest-to-build and least valuable end of the problem.

Disagree with any of this? That's the useful conversation. LinkedIn  ·  Email  ·  More writing