TL;DR Summary
Use three SaaS win-back email examples for a fixed blocker, a seasonal return, or a better-fit plan. See when each message makes sense.
I’d send a win-back email when I have a better answer to the reason someone left. “We miss you” tells me nothing about whether the product now fits my work.
1. A missing workflow now works
Subject - [Product] now supports [workflow]
Hi [name], when you left, you told us [workflow] took too much manual work. We’ve since added [specific capability]. This [short walkthrough] shows what it does and where the limits still are. If you’re still doing that work, I can help you test it.
2. Their work is seasonal
Subject - Setting up [workflow] again this season?
Hi [name], you mentioned that [workflow] comes back around [time]. If you’re restarting it, here’s the setup guide we use now. [Explain what account data, if any, they can still access.] Happy to point you to the right starting place.
Send this when the person gave you a reason to expect a return. Keep any data retention promise specific to the account and your actual policy.
3. The old plan was a poor fit
Subject - A smaller plan for [use case]
Hi [name], you mentioned you only needed [feature]. Our [plan] now covers that for [verified price and billing cadence]. You can compare the limits [here]. If it still doesn’t fit, you can skip this.
Growth mechanics, zero fluff.
Join SaaS founders and operators getting weekly notes and tear-downs on organic acquisition and churn reduction.
Measure the return after the first invoice
Start with people eligible for this kind of outreach and suppress opted-out, already-reactivated, and otherwise excluded contacts. Give each message one reason and one action. Track reactivated accounts that stay paid for a fixed period. If you have enough accounts, leave a comparable group unsent so you can estimate how many would have returned on their own.
For the definitions and churn calculations behind this workflow, see my SaaS churn rate guide.






