Every cancellation is a free customer-research interview, but only if you ask one question on the way out. The reason mix is one of the most valuable datasets in a subscription business — it tells you, in priority order, what to fix.
The standard list of cancellation reasons
Most subscription apps let you customize the options shown, but a clean default list covers 90% of real responses:
- Too expensive — pricing objection, often the customer's budget tightened.
- Too much product — frequency or quantity mismatch, not a product complaint.
- Not using it — value perception, the customer isn't seeing the benefit.
- Found a substitute — competitive, the customer is switching to another brand or solution.
- Product didn't meet expectations — quality issue.
- Just trying it out — never intended long-term subscription.
- Financial reasons — broader budget cut, not category-specific.
- Other — open text field for anything else.
What the reason mix tells you
The biggest bucket is your single highest-leverage improvement opportunity. Translated into action:
- Mostly "too expensive" → consider a smaller pack, loyalty discount tiers, or value reinforcement in marketing.
- Mostly "too much product" → fix frequency flexibility in the customer portal. This is the easiest win — a frequency change saves a customer who would otherwise cancel.
- Mostly "not using it" → value problem. Either the product isn't delivering, the customer isn't onboarding well, or the use case doesn't match expectations.
- Mostly "found a substitute" → competitive problem. Look at who they're switching to and why.
How to collect cancellation reasons reliably
Three principles:
- Required, but one click. Don't let customers skip the question, but don't make it a free-text essay either. Multi-choice with required selection.
- Show the question after the customer has committed to cancel, not before. If you ask first, they'll pick whichever option seems most likely to skip the rest of the flow.
- Add an optional open text field. The free-text responses are gold for product feedback — but make them optional so the multiple-choice data stays clean.
For more on building the flow itself, see subscription cancellation flow.