ChurnNote

Cancel flow guide

How to build a SaaS cancel flow.

A good cancel flow saves customers without resorting to dark patterns, and learns something from the ones it can't save. Here's the five-step structure, including the after-cancellation step most flows forget.

Run the free Churn Leak ReportStart ChurnNote for $12/mo

Quick answer

Build a cancel flow in five steps: (1) ask one reason question, (2) match the offer to the reason, (3) offer a pause before a cancel, (4) make leaving easy and respectful, and (5) follow up after the cancellation with a plain-text email. The follow-up is where the honest reasons and win-backs come from.

The 5 steps

  1. 1

    Ask one reason question first

    Before any offer, ask why they're cancelling with a short single-select list (too expensive, missing a feature, not using it, switched tool, bug/experience) plus an optional free-text box. This routes the rest of the flow and gives you data even when you don't save the customer.

  2. 2

    Match the offer to the reason

    Don't show the same discount to everyone. Price-sensitive churners get a discount or cheaper plan; 'not using it' churners get a pause or onboarding help; missing-feature churners get a roadmap note and a follow-up, not a coupon. A reason-matched offer converts far better than a blanket one.

  3. 3

    Offer a pause before a cancel

    For 'too busy' or 'not using it right now,' a pause (1-3 months) saves the subscription without discounting. Many customers who would have cancelled will pause and come back, especially for seasonal or project-based usage.

  4. 4

    Make leaving easy and respectful

    If they still want to cancel, let them, in one click, without dark patterns. A frustrating flow earns chargebacks and bad reviews. Confirm the end date and what happens to their data.

  5. 5

    Follow up after the cancellation

    This is the step most flows skip. A day or two later, send a plain-text email asking why, when they've cooled down. You'll get more honest reasons than the in-flow survey, and a chance to win them back when you fix the issue.

FAQ

Do I need to build the cancel flow myself?▼
Not necessarily. Tools like Churnkey, ProsperStack, and Raaft build no-code cancel flows. If you'd rather not build or pay for a flow, you can skip the in-app flow entirely and capture the reason after cancellation with a plain-text email (the approach ChurnNote takes).
What's the most common mistake in cancel flows?▼
Showing the same discount to everyone. It trains customers to cancel for a coupon and ignores the real reasons. Match the offer to the stated reason, and don't offer money to customers who left for a missing feature or a bug.
Should the cancel flow be hard to get through?▼
No. Friction and dark patterns produce chargebacks, bad reviews, and churned customers who badmouth you. Make leaving easy; win retention with relevant offers and a genuine follow-up, not obstacles.
Why follow up after cancellation if I have an in-flow survey?▼
In-flow surveys capture rushed answers from someone mid-exit, so you get 'too expensive' or 'not using it.' An email a day or two later reaches a cooled-down customer who'll explain what actually happened, which is far more useful for product decisions and win-backs.
How does ChurnNote fit with a cancel flow?▼
ChurnNote handles the after-cancellation step: it sends the plain-text exit email, groups the reasons, and queues a win-back when you ship a fix. You can run it alongside a cancel-flow builder, or on its own if you don't want to build a flow.

Don't skip the after-cancellation step.

ChurnNote sends the plain-text exit email, groups the reasons, and queues win-backs, with or without a cancel flow in front of it. Flat $12/mo.

Run the free Churn Leak ReportStart ChurnNote for $12/mo

Related

Cancel flow best practicesCancel flow examplesCancel flow offer examplesCancel flow feedback questionsCancellation flow graderBest cancel flow tools