Reason tracking
Turn scattered exit replies into a trend you can act on.
One cancellation is an anecdote. Tracking reasons over time tells you which one is rising and which fix would save the most MRR. Here's how to do it without it becoming noise.
How to track cancellation reasons
- 1
Capture a reason for every cancellation
Ask why after each cancellation (a plain-text email gets a 20%+ reply rate). Without near-complete capture, trends are noise. Aim to attach a reason to as many cancellations as possible, not just the vocal ones.
- 2
Group into a consistent taxonomy
Map free-text replies to a fixed set: pricing, missing feature, not using it, too complex, switched tool, bug, temporary. Consistent buckets are what make a trend readable across months.
- 3
Weight by lost MRR, not just count
Five low-tier 'too expensive' churns may matter less than one enterprise 'missing feature.' Track reasons by revenue lost as well as count, so you prioritize the fix that protects the most MRR.
- 4
Watch the trend and act
A reason rising month over month is a signal: a new competitor, a pricing-perception problem, a regression. Ship the fix, then win back the customers who left for that reason.
FAQ
What is cancellation reason tracking?▼
How do I track cancellation reasons reliably?▼
Should I track reasons by count or by revenue?▼
What taxonomy should I use?▼
How does ChurnNote track cancellation reasons?▼
See which reason is costing you most.
ChurnNote captures, groups, and trends every cancellation reason, weighted by lost MRR, so you know what to fix first. Flat $12/mo.