Win-Back Drip Sequences: Recover Churned Customers
Build a win-back drip sequence in Drip or an alternative: triggers, segments, timing, offers, pricing by list size, and the metrics that show whether it works.
By the editorial team. Prices last checked on 7 October 2026 against each vendor's pricing page.
For most small and mid-sized subscription businesses and online stores, Drip is the best starting point for a win-back sequence. Its lowest listed plan covers 1 to 2,500 people at $39 a month, that plan includes dynamic segments and up to 50 workflows, and the 14-day trial runs without a credit card. The reason it suits win-back work is that a win-back program is mostly two things: segments that separate churned people by why and when they left, and timed workflows that send the right message at the right gap. Those are the two features you need most, and you can build and test the whole sequence before you pay.
What a Win-Back Sequence Has to Do
A win-back sequence is a short series of emails sent to people who have stopped paying, or who have stopped using a product, and who have not returned. It has three jobs. It has to reach the person at a moment when they are not annoyed by the last message. It has to speak to the reason they left. And it has to stop at a sensible point so that the cancelled list does not turn into a long-running newsletter nobody asked for.
Most failed win-back programs fail on one of those three points. Some send the first email the same day the subscription ends, when the customer is still irritated about the charge. Others send one generic message to everyone, whether they left over price, over a missing feature or because they stopped needing the product. Others never end, so a customer who cancelled two years ago keeps receiving the same promotion.
The tool you pick matters less than the inputs you give it. A win-back sequence is only as good as its trigger (the event that starts it), its segments (the groups it treats differently) and its exit rules (the events that remove someone from it). Any email platform can send the messages. The work is in deciding those three things, and then making sure your billing system or product database passes the events into the email tool reliably.
Tools Compared for Win-Back Programs
Three tools come up most often when teams plan win-back work. They are built for different jobs, so the comparison below starts with what each one is for.
| Tool | Best for | Starting price | Key limitation |
|---|---|---|---|
| Drip | Ecommerce and SaaS teams that want segments and timed workflows for their subscriber list | $39 a month (monthly billing), 1 to 2,500 people | No ongoing free plan; the trial is 14 days |
| Outreach | Sales teams running multi-step outreach to prospects and named accounts | Pricing on request | Built around sales-rep activity, not automated subscriber win-back; no public free plan |
| Segment (Twilio Segment) | Teams that need one customer data layer feeding several tools, including cancellation events | Pricing on request; a free trial is offered for Connections | It moves and organizes customer data but does not replace an email sending tool |
If you only need to send a sequence to a list of former subscribers, Drip covers the job on its own. Outreach and Segment solve different problems and are worth considering only when those problems already exist in your organization.
Drip's Pricing for Win-Back Programs
Drip's plans are priced on the number of people in your account, and the lower tiers include unlimited email sends. That matters for win-back, because a cancelled customer usually stays in your database and counts toward your people total unless you remove or suppress them. The table below uses three realistic list sizes and the monthly prices shown on Drip's pricing page.
| Total people in account | Drip plan band | Monthly price | Yearly cost at the monthly rate |
|---|---|---|---|
| 2,000 | 1 to 2,500 people | $39 | 12 × $39 = $468 |
| 5,000 | 4,501 to 5,000 people | $89 | 12 × $89 = $1,068 |
| 10,000 | 9,001 to 10,000 people | $154 | 12 × $154 = $1,848 |
| 20,000 | 17,501 to 20,000 people | $289 | 12 × $289 = $3,468 |
These are the monthly rates. Drip's higher bands add support and onboarding; the $154 band adds chat and email support, and the 22,501 to 25,000 band includes a free migration and personalized onboarding. Tiers above 37,500 people include a set number of email sends, so check those bands on the pricing page if your list is that large.
For Outreach and Segment, the price depends on your contract, so the table shows pricing on request. Ask each vendor for a quote based on your actual list size and the number of integrations you need before you compare costs.
Drip: The Pick for Most Win-Back Programs
Drip is the tool to start with when your goal is to recover subscribers or customers who have left and you want the sequence to live in the same place as the rest of your email. Its strength for this use is the combination of dynamic segments and workflows. A segment can hold everyone who cancelled in the last 30 days, another can hold people who cancelled after more than a year, and a third can hold people who never completed onboarding. Each group can then enter a different workflow with its own timing.
At the entry tier, Drip includes dynamic segments and up to 50 workflows, so a team with one win-back sequence, a second for failed trials and a third for lapsed buyers has room to work. Email sends are unlimited across the lower tiers, which means a five-email sequence to a segment of a few hundred people does not use up a separate sending allowance.
Where it falls short. Drip has no ongoing free plan. The trial is 14 days and does not require a card, which is enough to build and test one sequence but not enough to run a program for months on a shoestring budget. Its pricing also rises as the people count grows, so a large list that churns heavily will feel the cost. Finally, a win-back sequence is only as good as the events you feed into it. Drip cannot tell why someone cancelled unless your billing or cancellation flow captures that reason and passes it on.
Price and link. The entry plan is $39 a month for 1 to 2,500 people. Current plans and their details are on Drip's pricing page.
Outreach: Sales Sequences, Not Subscriber Win-Back
Outreach is aimed at sales teams that run multi-step sequences to prospects and accounts. It is a sales engagement platform, and its strength is tracking what individual reps do across calls, emails and tasks. For a company whose account managers contact lapsed customers by hand, that workflow can be useful: the win-back becomes a set of tasks and emails for named people, and the rep follows up when someone replies.
Where it falls short for this job. Outreach does not offer a public free plan, and its pricing is custom. More important, it is not designed to send an automated, self-serve sequence to thousands of former subscribers who have not spoken to anyone at your company. If your win-back is a set of automated emails triggered by a cancellation, Drip is the better match. If your win-back is a set of personal calls and emails to a few hundred high-value former accounts, Outreach may be worth a conversation.
Price and link. Pricing on request. See Outreach's pricing page for how the company describes its plans.
Segment: The Data Layer Behind Win-Back
Segment, now part of Twilio, is a customer data platform. Its Connections product collects first-party data and sends it to other destinations, and its higher tier adds Engage, which includes journey orchestration. For win-back, the appeal is that a cancellation event can be captured once and delivered to every tool that needs it: your email platform, your support desk, your analytics. Teams that run several tools often find this useful because the cancellation reason and the timestamp reach each system without a manual export.
Where it falls short. Segment organizes and routes data. It does not replace the email platform that sends your win-back messages, so you still need Drip or another sending tool at the end of the chain. Its pricing is custom and not published as plan prices, and the free trial for Connections does not list duration or limits. For a small team with one billing system and one email tool, Segment is usually more infrastructure than a win-back program needs.
Price and link. Pricing on request. The company's current plan descriptions are on Segment's pricing page.
Build the Win-Back Sequence in Drip
The steps below assume you are using Drip, since it is the pick for most readers. The same logic applies to any email platform.
Step 1: Define the trigger
Choose one event that starts the sequence. The common choices are a cancelled paid subscription, a lapsed subscriber who has not opened or clicked in a set period, and an ecommerce customer with no order in a defined window. Avoid starting a win-back from a single failed payment, because that person may still be a current customer waiting on a card update. Use a separate payment-recovery flow for failed charges, and start the win-back only after the subscription has actually ended.
Step 2: Build the segments
Create segments before writing any email. At minimum, split people by time since they left (under 30 days, 30 to 180 days, over 180 days) and by what they had. A former customer on a high plan and a former trial user need different messages. If you capture a cancellation reason, add a segment for each common reason.
Step 3: Write the exit rules
Decide in advance what removes someone from the workflow. The obvious exits are a return to a paid plan, a purchase, and a reply from the customer. The less obvious ones matter just as much: a request to be deleted, a spam complaint, and a bounce must stop every marketing email at once. Add a rule that moves a person to a longer, lower-frequency list after the sequence ends, rather than leaving them in limbo.
Step 4: Build the workflow
Add the emails in order with the delays described in the timing section below. Keep one workflow per segment, not one workflow with branches for every case. Separate workflows are easier to read, easier to test and easier to change when you learn that a message works for one group but not another.
Step 5: Test the path, not just the copy
Before you switch the workflow on, add a test contact to each segment and move it through the sequence. Check that the right email arrives, that the delays are correct, and that the exit rules remove the test contact when you expect them to. Most broken win-back programs are broken in the routing, not the wording.
How the Five Emails Should Work
A win-back sequence needs a clear purpose for each message. The five-email structure below is a practical starting point. You can shorten it to three emails for smaller lists, and you should adjust the offer in the fourth email to match your margins.
Email 1: Acknowledge the departure
Send this three to seven days after the subscription ends, not on the same day. Say that you noticed they left, thank them for their time with the product, and ask one question: what would have made the product work better for them? One question is easier to answer than a survey. Keep the email short and do not include a discount.
Email 2: Show what has changed
Send this one to two weeks after email 1. Describe a change that addresses a reason someone might have left: a feature they asked for, a fix to a problem they reported, or a simpler setup path. Link to one page, not five. The goal is to give the person a reason to look again, without asking them to commit to anything yet.
Email 3: Show other customers succeeding
Send this two to three weeks later. Describe how a customer with a similar setup uses the product today. Only use real examples that you have permission to share, and avoid invented numbers. A specific sentence about one workflow is more persuasive than a general claim about results.
Email 4: Make the offer
Send this six to eight weeks after the sequence started. This is where the incentive appears, and it should be the first email in the sequence that includes one. The offer types and the sequencing advice are covered in the next section.
Email 5: Close the sequence
Send this 10 to 12 weeks after the start. Say clearly that this is the last message in the series and that you will stop sending win-back emails unless they reply or return. A personal note from a founder or account manager often works better here than a template, if your list is small enough to make that practical. End the sequence without guilt. A clean exit protects your sender reputation and your unsubscribe rate.
Offers and Incentives: What to Use and When
The offer is the most sensitive part of a win-back. A good offer changes the decision for someone who was close to returning. A poorly timed offer teaches people that cancelling is a way to get a discount, which is expensive and hard to undo.
Common incentive types
- Percentage discount on return: A time-limited reduction on the next billing period. Limit it to the people in the offer segment and make the expiry date visible.
- Free period: One to three months free, useful when the main barrier was a feeling that the product was not worth the time. It works best when the person has to take an action, such as completing setup, to unlock it.
- Plan change at the same price: Return on a higher tier at the price they previously paid for the lower one. This suits customers who churned because they outgrew a plan.
- Feature trial: Access to a feature they did not have before. It costs little and gives them a reason to test something new.
- Setup help: A short onboarding call or a guided checklist. This suits people who left because they never got the product working.
Sequence the offer, do not lead with it
Keep the strongest discount for the last or second-to-last email, after softer messages have had a chance to work. Customers who learn that the first email carries a discount will wait for the discount next time. Where possible, make the offer conditional on returning through a specific path, such as reactivating within the offer window, so it cannot be stacked with a second cancellation.
Segmenting Win-Back Messages by Reason and Value
A single sequence sent to everyone will work for some people and miss most others. Segmenting by reason, value and tenure lets you match the message to the situation without writing dozens of separate emails.
By reason
Ask why someone is leaving during the cancellation flow. A single optional question with a short list of answers is enough. Then group the answers into segments:
- Price: Lead with the value they got while subscribed, then offer a discount or a cheaper plan in a later email.
- Missing feature: Lead with the feature, if you have shipped it, or with a clear date if you have not. Do not promise a feature you cannot deliver.
- Did not use it: Lead with setup help and a simpler path to the first useful result.
- Problem or support experience: Lead with what you fixed, and do not send a sales email before acknowledging the problem.
- No longer needed: Keep the sequence short and make the return easy. Do not spend the full offer on this group.
By value
A former customer who spent a lot with you deserves more attention than a former trial user. A practical split is to give high-value former customers a shorter sequence with a personal reply option and a better offer, and give low-value former customers an automated sequence with fewer incentives. The cost of a personal email is only worth paying where the expected return justifies it.
By tenure
Someone who cancelled after three years probably changed their circumstances or their needs. Someone who cancelled after a week may never have reached the first useful result. Treat the long-tenure group as a question about what changed, and the short-tenure group as a failed onboarding. The emails for each should look different.
Timing: How Long to Wait and How Long to Keep Going
Timing errors are the most common cause of win-back emails that feel intrusive. Four rules cover most cases.
- Wait before the first email: Give the person three to seven days after the end of the subscription. Sending on the day of cancellation reads as pressure.
- Space the messages: One to two weeks between emails is typical. Daily messages are a sign the sequence is trying to close a sale, not start a conversation.
- Limit the length: Six to twelve weeks is a common window. After that, move people to a low-frequency list, such as a monthly update, and remove them from the win-back workflow.
- Think about seasonality: If your product is used in a particular season, schedule the later emails so they arrive when the person is likely to need the product again.
The exact numbers should come from your own results. Start with the timing above, measure the return rate by email, and move the messages that get no response.
Win-Back for Different Business Models
SaaS subscriptions
For software, the win-back question is usually whether the person still has the problem your product solves. Use the first email to ask about the problem, not the product. Include a plan change option, since a monthly or annual switch can remove the price objection without a discount. If your cancellations include failed payments, handle those separately: a card update is a different request from a return, and mixing them in one sequence confuses the reader.
Ecommerce
For an online store, win-back usually means a customer who bought once or stopped buying on a schedule. Use the purchase history to recommend products they are likely to need, and use replenishment timing where the product runs out. A customer who bought a consumable item six months ago is a better target for a reminder than a generic promotion. A loyalty reward can work as the incentive, but keep it tied to a purchase, so it does not reward inactivity.
Setup and Migration Checklist
If you are moving an existing list into a new tool, or setting up a win-back program for the first time, work through this checklist before the first email goes out.
| Item | What to confirm | Why it matters |
|---|---|---|
| Trigger event | The cancellation or lapse event is sent to the email tool reliably and time-stamped | A missing or late trigger means the sequence starts at the wrong time or never starts |
| Suppression list | Deleted-account requests, spam complaints and hard bounces are excluded from all sends | Sending to these people breaks trust and can harm deliverability |
| Cancellation reason | An optional reason question is captured at cancellation and stored on the contact | Without it, you cannot segment by reason |
| Segments | One segment per time-since-leaving band and per major reason | Segments drive the message and the timing |
| Exit rules | Return to paid, purchase, reply and unsubscribe each remove the contact | Prevents sending a return offer to someone who already came back |
| Offer code | The discount is restricted to the offer segment and has an expiry date | Stops the offer leaking to people who should not receive it |
| Test path | A test contact moves through each workflow with the correct delays | Catches routing errors before real customers see them |
When you migrate an existing list, import the contacts with their last-active date and cancellation status. Do not import every former customer into an active workflow on day one. Start with the most recent cancellations, check the return rate and the complaint rate after two weeks, and then add older groups in batches.
Measuring Whether the Sequence Works
A win-back program has four numbers that matter. Define them before you start so you can compare results over time.
- Win-back rate: The number of people who return in the window divided by the number who entered the sequence. If 80 of 1,000 churned people return within 90 days, the rate is 8%.
- Time to return: The average number of days between the cancellation and the return. A shorter time suggests the early emails are working.
- Retention after return: The share of returned people still active 90 days later. A high win-back rate with a low retention rate means the offer brought people back without solving the reason they left.
- Cost per return: The email tool cost, the incentive cost and any staff time divided by the number of returns.
Measure each email as well as the whole sequence. If email 4 brings returns and email 2 brings none, keep the offer and test a different version of email 2. Compare results by segment: a win-back rate that looks average overall can hide one segment that is performing very well and another that needs a different message.
Common Win-Back Mistakes
- Starting too soon: An email on the day of cancellation reads as pressure. Wait at least three days.
- Ignoring the reason: A generic message does not answer the question the person left with.
- Leading with the discount: This trains people to cancel for offers and removes your best incentive from the later emails.
- Never ending the sequence: After the final email, move people to a low-frequency list and stop the win-back workflow.
- Missing suppression rules: Former customers who asked to be deleted or who complained should never receive a win-back email.
- Fixing emails instead of the product: If many people leave for the same reason, the product or the onboarding needs work. A better email will not fix that.
How to Choose a Tool for Win-Back
The right tool depends on who does the win-back, how many people are in the list, and where the cancellation events come from. The decision table below covers the common situations.
| If you need | Pick | Because |
|---|---|---|
| Automated, self-serve win-back emails to a list of a few thousand people | Drip | Segments and workflows are included at the entry plan, starting at $39 a month for up to 2,500 people |
| To try a full sequence before paying | Drip | The 14-day trial requires no credit card |
| Personal outreach to a short list of high-value former accounts | Outreach | It is built for tracking named rep activity across multi-step sequences |
| One customer data feed sent to several tools, including cancellation events | Segment | It collects and routes customer data, which can then feed your email tool |
| A free plan for an ongoing program with no trial deadline | Check each vendor directly | Drip has no ongoing free plan, and Outreach and Segment do not publish one |
If you are still unsure, start with the pricing and trial details on each vendor's site and run one sequence to one segment. A single well-built sequence will tell you more than a longer comparison of feature lists.
To compare other drip email platforms, see the home page for the full list of tools reviewed on this site.
Frequently Asked Questions
Is Drip free to use for win-back emails?
Drip does not show an ongoing free plan on its pricing page. It offers a 14-day free trial that does not require a credit card. The entry paid plan covers 1 to 2,500 people at $39 a month, billed monthly on the figures listed there.
How many emails should a win-back sequence have?
Three to five emails over six to twelve weeks is a common structure. Smaller lists can run three emails, and larger programs can split the sequence by segment so each group receives only the messages that fit its reason for leaving.
When should I send the discount?
Send the discount in the fourth or fifth email, after softer messages have had a chance to bring people back. Keep it time-limited, restrict it to the offer segment, and make sure it cannot be combined with a second cancellation.
Should I email people who asked to be deleted?
No. Deletion requests, spam complaints and hard bounces should be suppressed from every marketing email, including the win-back sequence. Sending to these contacts damages trust and can hurt deliverability.
Can I run a win-back sequence for people who cancelled a free trial?
Yes, and the sequence can be shorter. A trial user who never reached the first useful result usually needs setup help rather than a discount, so lead with onboarding and a clear first step.
How do I define a win-back in my reports?
Define it as a return to a paid plan or a repeat purchase within a fixed window, such as 90 days after the start of the sequence. Use the same window for every cohort so the results can be compared over time.
What should I measure first?
Start with the win-back rate for each email and each segment, and the retention of returned people 90 days later. Those two numbers show whether the messages bring people back and whether the return lasts.