Churn is rarely a verdict on the product. It is often a timing problem, a budget problem, or an unresolved friction. A win-back program treats cancel as a pause, not a goodbye, and gives the former customer a clean reason to return.
A win-back campaign is an orchestrated outreach program aimed at churned customers, typically ninety to one hundred eighty days after they cancel. The standard play combines a product-update email, a free month on return, an exec-to-exec call for high-value accounts, and a roadmap preview. Customer success and marketing run it together, and a healthy program re-activates five to fifteen percent of the targeted logos. It is distinct from re-engagement, which targets dormant users who never churned.
The six decisions that separate a win-back program from a desperate follow-up, and the one timing choice most teams get wrong.
A win-back targets accounts that actually cancelled, downgraded off a paid plan, or let a contract expire. The record shows a real churn event, a real end date, and in most cases a real reason the customer gave on the way out. That is a different audience, and a different message, from a trial that never converted or a user who stopped logging in.
Reach out too soon and the frustration that drove the cancel is still fresh. Wait too long and the switching cost to come back feels higher than the pain they left to escape. The sweet spot sits between the quarterly budget cycle after cancel and the renewal moment of the competitor they moved to. Most mature programs run a first wave at ninety days and a second wave at one hundred eighty.
The standard pattern layers four assets. A product-update email that shows what shipped since they left. A free month or waived onboarding fee for returning accounts. An exec-to-exec call for anything that was paying real revenue. And a short roadmap preview so the customer sees where the product is going, not just where it is.
A disciplined win-back program re-activates between five and fifteen percent of targeted logos, with the top of the range reserved for programs that segment by churn reason and personalize the first message. Below five percent usually means the audience was wrong or the offer was weak. Above fifteen percent usually means the churn was involuntary and the real fix was billing, not marketing.
Win-back sits in the seam between the two functions. CS owns the account history, the churn reason, and the exec relationship. Marketing owns the message, the sequence engine, and the measurement. The program works when both are reading from the same contact record, so the follow-up email never contradicts what the CSM said on the exit call.
Every win-back needs a defined finish line. One wave, two waves, three waves, and the contact is suppressed from the program for a year. Without exit rules, a win-back turns into a monthly reminder that the customer left, which is the fastest way to burn the brand with the audience most likely to say nice things about you in the future.
Most teams do not need a bespoke win-back program. There is a short list of plays that cover almost every segment, and the work is in sequencing them, not inventing them. The pattern below is how a CS-plus-marketing pair runs a credible post-churn program against a book of a few hundred former customers without hiring anyone new.
The first touch is almost always a what-is-new email. Short, scannable, three or four improvements, no pitch, no discount. The job is to answer the one question every churned customer has: did anything actually change? If the answer is yes, the next email in the sequence has an audience. If the answer is no, the program should pause until the roadmap catches up.
A waived first month, a free onboarding, or a one-time credit on return. The point is not the dollar value, which is small. The point is to make the come-back decision reversible, so the customer can test the product again without a procurement cycle. Most returning accounts pay full price starting month two, which is why the free month pays for itself inside a quarter.
For former customers that were paying real revenue, a one-to-one email from a founder, VP, or GM lands differently than a template. Reference the specific churn reason, acknowledge what did not work, and offer a thirty-minute conversation with no sales pressure. These calls close more win-back revenue than every automated sequence combined for enterprise segments.
Some former customers are not coming back today. They might come back when a specific capability ships. A short roadmap preview, with honest dates, keeps the door open and gives the account a reason to re-open the thread when the item lands. Treat it as a seed, not a close, and let the customer decide the timing.
The most persuasive asset in a win-back program is another company that left and came back. One short story, same industry, same reason to leave, same reason to return. It is permission for the current reader to make the same decision. Use sparingly, request permission carefully, and attribute the outcome in the customer's own words.
The last message in the sequence names a specific window and a specific action. Return in the next thirty days and get the free month, the migration help, and a dedicated contact. The deadline is honest, the help is real, and the ask is a single click to book a call. Vague offers do not close win-backs. Named deadlines do.
Teams often fold win-back and re-engagement into one bucket. They are different audiences with different intents, different metrics, and different ways to fail. Running them as one program dilutes both. The split below is how mature CS and marketing teams keep the two separate without doubling the headcount.
Win-back targets former customers who actively cancelled, downgraded off paid, or let a contract expire. Re-engagement targets contacts, trials, and users who went inactive without ever churning. Different relationship, different history, different cost of return. A single sequence that treats both the same insults both audiences.
A win-back message acknowledges a relationship that ended. A re-engagement message pokes a relationship that stalled. The win-back references the account history and the exit reason. The re-engagement references the last activity and the value the contact never fully experienced. Mixing the tones feels off to both audiences.
Win-back fires on a cancel event plus a defined waiting window, usually ninety or one hundred eighty days. Re-engagement fires on an inactivity threshold, usually thirty, sixty, or ninety days of no logins, opens, or product use. The two triggers rarely overlap, which is why running them from the same workflow produces conflicts.
Win-back offers reduce the cost of coming back: free month, waived onboarding, dedicated contact. Re-engagement offers increase the perceived value of staying: new feature spotlight, use case guide, short survey. Giving a dormant user a return discount they do not need signals that something is wrong, which is the opposite of the message you want to send.
Win-back is owned by customer success and marketing, because the account history and exec relationships live in CS. Re-engagement is owned by marketing and product, because the signal is behavior inside the product. Clarifying who runs each program is how the two sequences stop fighting over the same contact record.
Win-back is measured in paid logos that come back and the revenue they bring with them. Re-engagement is measured in dormant accounts that return to regular use, which may or may not become revenue depending on the business model. Reporting both under one bucket makes neither number trustworthy.
A win-back program lives or dies on data quality. The churn reason, the exit date, the exec relationship, the last conversation, the open support tickets, the plan tier at cancel. All of it has to be on the account record, visible to CS and marketing together, or the sequence sends the wrong message to the wrong former customer. The pattern below is how to run the program against live records instead of a stale export.
The cancel event logs a structured churn reason: price, feature gap, acquisition, bad fit, team change. The win-back sequence reads that reason and branches the message. A customer who left for price gets a different first email than one who left because a specific feature was missing. Generic win-backs ignore the signal the customer already gave you.
The moment a CSM reaches out, the former customer replies, or a new deal opens on the account, the win-back sequence pauses. A former customer who is already talking to a human should not also be getting a canned reactivation email the next morning. Suppression keeps the automated program from stepping on the one-to-one work that closes the actual win-back.
Not every former customer gets the same program. The top tier by prior spend gets the exec-to-exec call and a tailored offer. The mid tier gets the full automated sequence plus a human touch. The long tail gets the automated sequence alone. Tiering is how a small team runs a credible program across hundreds of logos without faking personalization.
When a former customer returns, the new deal links back to the win-back sequence they engaged with, the message that got the click, and the offer that closed the come-back. Marketing sees which plays actually produced re-activated revenue. CS sees which conversations landed. The finance view sees the program's real return, not just its open rate.
Automated outreach is the opening move, not the whole program. When a former customer replies, books a call, or clicks the reactivation link, the record routes to the right CSM or AE, the sequence suppresses, and the human takes it from there. The handshake is where the program feels either personal or robotic, and it has to be instant.
A single view answers the question every revenue leader asks: of the customers who cancelled this year, how many came back, how long did it take, how much are they worth, and which play did the work. That report only exists when the win-back sequence, the exit survey, and the pipeline all live on the same contact and account records.
Strkr includes customer success workflows and marketing automation in one tool, so the win-back sequence reads the churn reason, pauses the moment a CSM takes over, and reports re-activated revenue, not just opens. Pricing is published. The feature pages show exactly what ships today.
A win-back targets former customers who actively cancelled, downgraded off a paid plan, or let a contract expire. A re-engagement campaign targets contacts, trials, or users who went dormant without ever being paying customers. The audiences, timing, message tone, offers, and success metrics are all different. Treating them as one program dilutes both.
Most mature programs run the first wave ninety days after cancel and a second wave at one hundred eighty days. Earlier than ninety days is usually too soon because the frustration that drove the cancel is still fresh. Later than one hundred eighty days usually means the former customer has already renewed with a competitor and the switching cost to return is too high.
A disciplined win-back program re-activates five to fifteen percent of targeted logos. Below five percent usually signals the audience was wrong, the churn reason was product-truth rather than fixable friction, or the offer was weak. Above fifteen percent often means the churn was involuntary (billing failures, card expiry) and the real fix was in payments, not marketing.
The standard assets are a product-update summary, a free month or waived onboarding fee on return, a roadmap preview for customers who left because of a specific gap, and an exec-to-exec conversation for the highest-tier accounts. The point of the offer is not the dollar value, it is to make the decision to come back reversible so the customer can test the product again without a long procurement cycle.
Both. Customer success owns the account history, the churn reason, and the exec relationship. Marketing owns the message, the sequence engine, the segmentation, and the measurement. The program works when both teams read from the same contact and account record, so the follow-up email never contradicts what the customer success manager said on the exit call.
Short, usually three to five messages across the ninety to one hundred eighty day window. A product-update email, a reactivation offer, a case study or roadmap preview, and a final named-deadline nudge. Longer sequences do not improve re-activation rates and start to feel like a monthly reminder that the customer left, which erodes the brand with an audience you want speaking well of you.
By segmenting on the churn reason captured at cancel, the prior plan tier, the industry, and the exec relationship on file. A customer who left for price gets a different first email than one who left because a feature was missing. A top-tier former account gets a one-to-one exec reach, not an automated sequence. Generic win-backs ignore the signal the customer already gave on the way out.
Starting too soon, running the sequence forever with no exit rule, treating every churned customer the same regardless of prior revenue or churn reason, offering a discount war instead of a credible reason to return, letting the automated sequence talk over a human conversation the CSM already started, and reporting re-activation rate without tying it back to actual revenue returned.
No sales call, no migration consultant, no four-month implementation. Enter your card, get 14 days of the full Pro tier, cancel any time before day 14 with zero charge. Spin up a workspace, import your CSV, and have something useful before lunch.
