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. 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. 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. 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. 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?
It's capturing why each customer cancels and following the breakdown over time, so scattered individual exits become a trend you can act on: which reason is rising, and which fix would save the most revenue. It's the difference between anecdotes and a decision.
How do I track cancellation reasons reliably?
Capture a reason for as many cancellations as possible (an after-cancellation email beats relying on the vocal few), map every reply to a consistent taxonomy, and review the trend monthly. Inconsistent buckets or low capture rates make the trend meaningless.
Should I track reasons by count or by revenue?
Both, but weight by lost MRR for prioritization. A reason that's common among low-value customers may matter less than a rarer reason concentrated in your highest-value accounts. Revenue-weighting tells you which fix protects the most money.
What taxonomy should I use?
A short, fixed set covers almost everything: pricing/value, missing feature, not using it, too complex, switched tool, bug/experience, and temporary need. Keep it stable over time so trends are comparable month to month.
How does ChurnNote track cancellation reasons?
ChurnNote emails each churned customer, captures the reason, groups replies into a consistent taxonomy automatically, and tracks the trend over time, including by lost MRR, so you can see what to fix first. Flat $12/mo.

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.