Systematically categorize why customers canceled, spot the most common exit reasons, and walk away with concrete retention actions you can act on this week.
The template
Cancellation Reason (Verbatim)
Paste the exact words the customer used when they canceled — from an exit survey, cancellation flow, or support ticket.
Example: "We stopped using it because the reporting wasn't detailed enough for our finance team and it took too long to get value."
Churn Category
Assign each response to one primary churn category so you can count frequency across your full dataset.
Example: Missing features — the customer needed advanced reporting capabilities that the product didn't offer at their plan tier.
Fixable or Structural?
Note whether this churn reason is something your team could realistically address (fixable) or outside your control such as budget cuts or company closure (structural).
Example: Fixable — the reporting gap is on the roadmap for Q3 and a workaround via CSV export exists today but was never communicated to this customer.
Recommended Action
Write one specific action your product, success, or marketing team should take in response to this pattern.
Example: Add a proactive in-app message at day 14 highlighting the CSV export option for accounts with a finance team member identified during onboarding.
How to use it
Collect your cancellation responses Pull exit survey answers, cancellation flow free-text, and any churn-related support tickets from the last 90 days into a single spreadsheet.
Fill in one row per response For each cancellation, complete all four template sections — verbatim reason, category, fixable flag, and recommended action — before moving to the next.
Count frequency by category Sort your completed rows by the Churn Category column and tally how many responses fall into each bucket to find your top exit reasons.
Prioritize fixable themes by volume Focus your retention roadmap on the churn categories that are both high-frequency and marked fixable, then assign an owner and deadline to each recommended action.
What it looks like filled in
Slow Time-to-Value
"We signed up but never really got it set up properly — by month two we just weren't using it and it felt like a waste of money."
→ Redesign onboarding to surface one activation milestone within the first 48 hours and trigger a success check-in call for accounts that miss it.
Missing Integrations
"We needed it to sync with HubSpot automatically. We were doing manual exports every week and eventually the team just gave up."
→ Accelerate the native HubSpot integration currently in backlog and add it to the public roadmap to recover at-risk accounts on similar stacks.
Price-to-Value Mismatch
"It was good but not $300 a month good for a team our size. We found something cheaper that did 80% of what we needed."
→ Introduce a small-team plan tier below the current entry price point and A/B test a value-focused email sequence at the 60-day mark before renewal.
Why teams skip the template
Manually reading hundreds of responses takes hours If you have more than 50 cancellation responses, categorizing and tagging each one by hand can consume a full day of a CSM or PM's time every single month.
Human categorization is inconsistent across reviewers When two people categorize the same response differently — one calls it "missing features" and another calls it "onboarding" — your frequency counts become unreliable and you act on flawed priorities.
The template can't surface nuance buried in long answers Customers often mention a secondary reason inside a longer response that a manual skim misses, meaning you may never see a pattern that affects 20% of churned accounts.
Analyze your churn feedback automatically — no template needed
