Organize and interpret why subscribers are cancelling so you can identify the top churn drivers and take targeted action to reduce them.
The template
Cancellation Reason (Verbatim)
Paste the exact words the user wrote or said when cancelling — do not paraphrase yet.
Example: "I signed up to track my team's projects but the reporting is too basic — I can't filter by assignee or date range, so I stopped using it."
Theme / Category
Assign one short label that captures the core reason behind this cancellation (e.g. Missing Feature, Pricing, Onboarding, Competitor Switch).
Example: Missing Feature — Reporting & Filtering
Segment or User Profile
Note any relevant context about this user — their plan, company size, tenure, or use case — so you can spot if a theme is concentrated in one segment.
Example: Pro Plan, 8-person team, churned after 3 months, primary use case: project management
Suggested Action
Write one concrete next step the product, success, or marketing team could take in response to this specific piece of feedback.
Example: Add assignee and date-range filters to the reporting dashboard — flag to product team with 4 similar responses as supporting evidence
How to use it
Collect your cancellation responses Export cancellation survey responses, support ticket notes, or exit interview transcripts into a spreadsheet — aim for at least 20 responses before looking for patterns.
Fill in one row per response For each piece of feedback, complete all four template sections: verbatim quote, theme, user segment, and a suggested action.
Group and count by theme Sort or filter your rows by the Theme column to see which cancellation reasons appear most frequently across your dataset.
Prioritize and present findings Rank themes by frequency and segment impact, then share the top three with your product and success teams alongside the verbatim quotes as evidence.
What it looks like filled in
Too Expensive / Poor Perceived Value
"It's just not worth the price for what I actually use — I only need two or three features but I'm paying for a whole platform I don't need."
→ Introduce a lower-tier plan or usage-based pricing to retain cost-sensitive users before they reach the cancellation screen
Switched to a Competitor
"We moved to [Competitor] because our developers were already using it and the API integrations we needed were already built in."
→ Audit the top three native integrations competitors offer that you don't, and prioritize the most-requested one on the roadmap
Never Got Value / Poor Onboarding
"Honestly I just never really figured out how to make it work for my workflow — I kept meaning to dig in but never did and the trial ran out."
→ Trigger a human check-in from customer success at day 7 for users who have not completed the core activation milestone
Why teams skip the template
Manual tagging takes hours at scale Reading and categorizing hundreds of cancellation responses one by one is time-consuming and impossible to keep up with when churn spikes or your user base grows.
Theme labeling is subjective and inconsistent Different team members assign different category names to the same underlying issue, making it hard to track whether a problem is getting better or worse over time.
Insights arrive too late to act By the time you've finished a manual analysis round, the cohort that churned is long gone and the window to run a win-back campaign or emergency fix has already closed.
Analyze your cancellation feedback automatically — no template needed
