A cancellation flow can collect useful feedback while remaining clear. Separate the decision to leave, its consequences and an optional question about the reason.
Explain what ends and when
In a fictional project-management product, cancellation may stop renewal while access continues until a defined date. Explain remaining access and export options under the applicable terms. Do not bury those facts beneath repeated retention offers.
| Stated reason | Question to investigate |
|---|---|
| No longer needed | One-off use or changed business activity? |
| Too complicated | Which workflow remained incomplete? |
| Too expensive | Insufficient value or budget pressure? |
| Another product | Which capability made the difference? |
Preserve uncertainty
A selected option does not tell the whole story. Offer optional free text and compare reasons with usage patterns without pretending those patterns reveal intent. A person choosing the first available reason may simply want to finish the process.
Should every customer be retained?
No. Some needs have ended or fall outside the offer. A clean exit supports understanding and avoids turning a reasonable departure into a dispute. Look for repeated, fixable problems instead of responding to every cancellation with an improvised discount.
One account can contain several departure reasons
An administrator may cancel after a merger while individual teams still value the product. Record the organisational context without forcing it into a usability complaint. That distinction changes whether the appropriate response is migration support, packaging review or product improvement.
From this guide to your project
Growth ↗
A product finds its market when acquisition, activation and retention work together.
Tell us about your ideaExamples are educational and do not describe client results. Content prepared with AI assistance; see our editorial policy. Our method ↗