WIN-BACK

Win-back email examples: what to send at 30, 60 and 90 days

Original win-back email examples for SaaS, sorted by cancel reason and timed at 30, 60 and 90 days, with subject lines, rules for offers and a checklist.

Published 7 min read

A win-back email goes to someone who has already cancelled. That changes everything about how it should read. The customer made a decision, so the email has to give them a new reason to reconsider: something changed, something fits better now, or the original problem has a fix. A generic “We miss you! Come back for 20% off” ignores why they left.

The most useful input you have is the cancel reason. If your cancel flow asked “what’s the main reason?”, you can write a different sequence for each answer. This guide gives a timing framework and original example emails for the most common reasons.

Why 30, 60 and 90 days

There is no universal best schedule, but a 30/60/90 cadence works as a default for monthly SaaS:

Day Purpose Tone
30 Check in after the dust settles. Address the cancel reason directly. Helpful, low pressure
60 Share what changed: new features, fixes, pricing options. Informative
90 Last message in the sequence. Make the offer, if any, and say you won’t keep emailing. Direct, respectful

Thirty days gives the customer time to try life without your product, or to try the alternative. By 90 days, most people have either settled into something else or are ready to reconsider. After the third email, stop. Add them to your regular product newsletter only if they opted in.

Adjust for your billing cycle. For annual plans, the first useful moment may be closer to their old renewal date. For seasonal businesses, time the emails to the next season.

Ground rules

  • Respect consent. Win-back emails are marketing in many jurisdictions. Check that you have the right to send them (for example, opt-in requirements for EU consumers under ePrivacy rules), and include a working unsubscribe link.
  • Write from a person. A named sender with a reply-to address that a human reads.
  • One message, one action. One link or button per email.
  • Be specific about what changed. “We’ve improved a lot” means nothing. “Bulk export to CSV shipped in October” means something.
  • Don’t fake scarcity. No invented deadlines.
  • Keep the data promise. If you said you would delete their data after 90 days, don’t promise in email 3 that “everything is still there.”
  • Stop when they come back. Remove reactivated customers from the sequence immediately.

Examples by cancel reason

The examples below use a fictional project management tool called “Planwise” with a $49/month Team plan and a $19/month Basic plan. Replace the details with yours.

Reason: too expensive

The customer may still like the product. The question is whether there is a price that works.

Day 30

Subject: A smaller Planwise plan

Hi Dana,

When you cancelled last month, you said Planwise was too expensive. That’s fair feedback.

In case it helps: the Basic plan is $19/month for up to 3 people, and it keeps boards, tasks and history. If your team is small, it may cover what you used.

[Compare plans]

Either way, thanks for trying Planwise. Sam, Planwise

Day 60

Subject: Annual billing is now 2 months free

Hi Dana,

One more option since you left: paying yearly now costs the same as 10 months. For the Team plan, that’s $490/year instead of $588.

[See annual pricing]

Sam

Only send this if the pricing change is real. If nothing changed, skip day 60 for this reason.

Day 90

Subject: Last note from Planwise

Hi Dana,

This is the last email I’ll send about coming back. If you’d like to restart, you can have 40% off your first 3 months on any plan. After that, it’s the regular price.

[Restart with 40% off]

If not, no hard feelings. Good luck with the projects. Sam

Reason: not using it enough

This reason often means the product didn’t become a habit, or the project that needed it ended.

Day 30

Subject: Starting a new project?

Hi Marco,

You cancelled because you weren’t using Planwise much. If a new project comes up, you can restart in a minute and import from a spreadsheet.

[Import a project]

Sam

Day 60

Subject: 3 templates for getting started fast

Hi Marco,

A lot of teams stop using a tool when setup takes too long. We added templates for product launches, client onboarding and content calendars. Each takes about five minutes to adapt.

[Browse templates]

Sam

Day 90

Subject: Pause instead of cancel, next time

Hi Marco,

Last email from me. If you come back and your usage goes up and down, you can now pause your subscription for up to 3 months instead of cancelling. Billing stops, and your boards stay.

[Restart Planwise]

Sam

Reason: missing a feature

This is the best reason to have, because you can answer it precisely. Store the feature they named (from the free-text field or a follow-up question) and only email when it ships.

Day 30 (if the feature shipped)

Subject: Gantt view is live

Hi Priya,

When you left, you mentioned Planwise didn’t have a Gantt view. It shipped this week. Here’s a 90-second video of how it works.

[Watch the video]

If you want to try it, your workspace is still available until March 2. Sam

Day 30 (if it didn’t ship)

Subject: About the Gantt view

Hi Priya,

You told us you needed a Gantt view. I wanted to be straight with you: it’s planned, but not before next quarter. I’ll email you once when it ships, and not before.

Sam

The honest version builds more trust than silence, and it sets up a much stronger email later.

Day 60 and 90: send only if there is real news on that feature. Otherwise, end the sequence.

Reason: switched to a competitor

The customer is now using something else. Discounts rarely work here; learning and specific differences might.

Day 30

Subject: One question

Hi Alex,

You moved to another tool last month. Would you tell me what it does better? One line is enough, just hit reply. It goes straight to me.

Sam

Day 60

Subject: Moving back is one click

Hi Alex,

If the new tool isn’t working out, Planwise can now import directly from CSV and from most tools’ export formats. Your old workspace is still here until March 2.

[Import your data]

Sam

Day 90: usually skip. If you send one, keep it to a single line saying the door is open.

Reason: too hard to use

The barrier was effort. Offer to remove it.

Day 30

Subject: Want us to set it up for you?

Hi Jordan,

You said Planwise was hard to get going. If you’re up for it, I can do a 20-minute setup call and build your first board with you.

[Book a time]

Sam

Day 60

Subject: We simplified the first screen

Hi Jordan,

Since you left, we cut the onboarding to three steps and added a sample project you can edit. Here’s what it looks like now.

[See the new onboarding]

Sam

Reason: no longer needed (company closed, project ended)

Usually send one email at most, at day 60 or 90, and only a friendly note. No discount.

Subject: Thanks for using Planwise

Hi Lee,

Just a note to say thanks for the time you spent with Planwise. If you ever need it again, your account email still works.

Sam

Which offers belong in win-back emails

Offer Good fit Watch out for
Discount on return Price-driven cancellations Training customers to churn and return for a discount
Cheaper plan Price, low usage Making sure it actually covers their use case
Annual billing Price, if they liked the product Only if the saving is real
Setup call Too hard to use Staff time; cap it
Feature news Missing feature Send only when it ships
No offer Competitor, no longer needed None; restraint is the point

Two rules for discounts: make them one-time per customer, and state when the regular price resumes. See pause vs discount vs downgrade for the trade-offs.

Measuring win-back

Track per reason and per email:

  • Reactivation rate: reactivated customers / customers who entered the sequence.
  • Reactivated MRR, minus the cost of any discount.
  • Retention after reactivation: do they stay 3 and 6 months, or leave again when the discount ends?
  • Reply rate: especially for “one question” emails. Replies are research.
  • Unsubscribe and spam complaint rate: if it rises, your emails are too frequent or too pushy.

Keep a holdout group that gets no win-back emails, so you can see how many customers would have come back on their own.

Checklist

  • Cancel reason is stored with each cancellation.
  • One sequence per reason, three emails maximum.
  • Consent and unsubscribe handled.
  • Sender is a named person, replies are read.
  • Each email has one action.
  • “What changed” claims are true and specific.
  • Discounts are one-time and their terms are stated.
  • Reactivated customers leave the sequence immediately.
  • Holdout group in place.

How NoChurn helps

NoChurn sends win-back emails at 30, 60 and 90 days, written from the cancel reason each customer gave in the cancel flow. NoChurn works in English, German, French, Italian and Portuguese. Every feature is included on every plan, priced by MRR only (pricing).

PROMPT

Read https://www.nochurn.sh/llms.txt,
then follow https://www.nochurn.sh/docs/quickstart/
to add NoChurn to this app. Use a test key
(nc_test_…) until I say we go live.

Stop leaking revenue.

  • Free until $300 MRR
  • No card needed
  • Live in 10 minutes
  • Never a cut of what we recover