What This Template Is For
Every customer who cancels has a reason. Most SaaS companies never learn what that reason is because they either do not ask, ask at the wrong time, or ask the wrong questions. The result is a retention problem that Product, CS, and leadership all have different theories about but no data to resolve.
This template provides a structured approach to churn interviews. It covers three stages: the cancellation survey (at the moment of churn), the exit interview (a follow-up conversation), and the churn analysis framework (aggregating patterns across multiple churned customers). Each stage has a different purpose and captures different information.
For the quantitative side of churn measurement, the churn rate metric defines how to calculate and benchmark your rate. The Product Analytics Handbook covers how to build the instrumentation needed to detect at-risk customers before they reach the cancellation page. If you are building a retention-focused product strategy, the PLG Handbook covers activation and engagement loops that reduce churn structurally.
The Customer Success Playbook Template covers the proactive side of retention. This template focuses on learning from the customers you have already lost.
How to Use This Template
- Implement the cancellation survey first. It captures data from every churned customer at the moment of cancellation with minimal effort.
- Set up the exit interview process for high-value accounts. Not every churned customer needs a call, but accounts above your target ACV threshold do.
- Build the churn analysis dashboard. Aggregate reasons monthly and share with Product, CS, and leadership.
- Close the loop. Every churn reason should map to a specific action: a product fix, a process change, or a positioning adjustment.
The Template
Part 1: Cancellation Survey
This survey appears when a customer clicks "Cancel" or "Downgrade" in the product. Keep it to 3-4 questions. Completion rate drops sharply after 4 questions.
Question 1: Primary reason for cancelling (Single select, required)
- ☐ No longer need the product (business changed)
- ☐ Switched to a competitor
- ☐ Too expensive for the value received
- ☐ Missing features I need
- ☐ Product was too difficult to use
- ☐ Poor customer support experience
- ☐ Internal budget cuts
- ☐ We are shutting down or restructuring
- ☐ Other: [free text]
Question 2: What would have changed your mind? (Free text, optional)
[Open text field. This is the most valuable question. Customers who answer it are telling you exactly what to fix.]
Question 3: Would you consider returning in the future? (Single select, optional)
- ☐ Yes, if specific issues are fixed
- ☐ Possibly, depending on circumstances
- ☐ Unlikely
- ☐ No
Question 4: How likely are you to recommend us to others? (Scale 0-10, optional)
[Standard NPS question. Churned customers who still rate you 7+ are recoverable.]
Part 2: Exit Interview Script
For accounts above [threshold ACV], schedule a 20-minute exit interview within 5 business days of cancellation. Send the interview request from the CSM or a product leader, not from a generic email.
Before the interview.
- ☐ Review the account's usage data for the last 90 days
- ☐ Check support ticket history for unresolved issues
- ☐ Review the cancellation survey response (if completed)
- ☐ Identify the stakeholder most likely to agree to a call
- ☐ Prepare 2-3 hypotheses about why they churned
Interview questions.
| Phase | Question | Purpose | Notes |
|---|---|---|---|
| Warm-up (2 min) | "Thank you for taking the time. We want to learn from your experience so we can improve. There is no sales pitch here." | Set expectations | Mean it. Do not pitch. |
| Context (3 min) | "Can you walk me through how you were using [product] day to day?" | Understand their workflow | Listen for gaps between intended and actual use |
| Trigger (5 min) | "What was the moment or event that made you decide to cancel?" | Identify the triggering event | There is almost always a specific moment, not a gradual decline |
| Alternatives (3 min) | "What are you using now instead? How did you find it?" | Understand competitive landscape | Do not argue or defend |
| Missing value (3 min) | "If you could change one thing about the product, what would it be?" | Surface unmet needs | Focus on their words, not your interpretation |
| Future (2 min) | "Under what circumstances would you consider coming back?" | Assess win-back potential | Note specific conditions |
| Close (2 min) | "Is there anything else you want us to know?" | Catch what you missed | Often the most honest answer |
After the interview.
- ☐ Write up notes within 24 hours
- ☐ Categorize the churn reason (see taxonomy below)
- ☐ Share findings with Product team if the reason is product-related
- ☐ Flag as win-back candidate if conditions are achievable
- ☐ Add to monthly churn analysis report
Part 3: Churn Reason Taxonomy
Categorize every churn event into one of these buckets. Use consistent categories so you can track trends over time.
| Category | Sub-Reasons | Ownership | Typical Fix |
|---|---|---|---|
| Product-Market Fit | Outgrew the product, wrong use case, business changed | Product | Roadmap adjustment or positioning change |
| Product Quality | Bugs, performance, missing features, UX friction | Product / Engineering | Bug fixes, feature development |
| Pricing | Too expensive, competitor is cheaper, poor value perception | Product / Finance | Pricing model review, value communication |
| Competition | Switched to competitor, consolidating vendors | Product / Marketing | Competitive analysis, differentiation |
| Onboarding Failure | Never activated, poor first experience, no training | CS / Product | Onboarding process improvement |
| Support Failure | Unresolved tickets, slow response, poor quality | Support / CS | Support process improvement |
| Internal Change | Budget cuts, reorg, company shutdown, champion left | None (external) | Win-back nurture when timing improves |
| Relationship | Lost trust, broken promises, communication gaps | CS / Leadership | Account management process review |
Part 4: Monthly Churn Analysis Report
| Metric | This Month | Last Month | 3-Month Trend |
|---|---|---|---|
| Total churned accounts | [X] | [X] | [Up/Down/Flat] |
| Total churned ARR | [$X] | [$X] | [Up/Down/Flat] |
| Average churned account age | [X months] | [X months] | [Up/Down/Flat] |
| Cancellation survey completion rate | [X%] | [X%] | [Up/Down/Flat] |
| Exit interviews completed | [X] | [X] | [Up/Down/Flat] |
Churn reasons (this month).
| Reason Category | Count | % of Total | ARR Lost | Trend |
|---|---|---|---|---|
| Product-Market Fit | [X] | [X%] | [$X] | [Up/Down/Flat] |
| Product Quality | [X] | [X%] | [$X] | [Up/Down/Flat] |
| Pricing | [X] | [X%] | [$X] | [Up/Down/Flat] |
| Competition | [X] | [X%] | [$X] | [Up/Down/Flat] |
| Onboarding Failure | [X] | [X%] | [$X] | [Up/Down/Flat] |
| Support Failure | [X] | [X%] | [$X] | [Up/Down/Flat] |
| Internal Change | [X] | [X%] | [$X] | [Up/Down/Flat] |
| Relationship | [X] | [X%] | [$X] | [Up/Down/Flat] |
Top 3 actions this month.
- [Action tied to the largest churn reason]
- [Action tied to the second largest churn reason]
- [Systemic improvement based on interview patterns]
Filled Example: B2B Project Management SaaS
Cancellation Survey Results (February 2026)
| Reason | Count | % |
|---|---|---|
| Missing features I need | 12 | 28% |
| Switched to a competitor | 9 | 21% |
| Too expensive for the value received | 8 | 19% |
| Internal budget cuts | 6 | 14% |
| Product was too difficult to use | 4 | 9% |
| Other | 4 | 9% |
Exit Interview Summary (Top 5 by ARR)
Account: TechScale ($85K ARR). Switched to Linear. Trigger: their engineering team grew from 30 to 80, and our product could not support cross-team dependencies at scale. They evaluated 3 tools and chose Linear for its speed and API flexibility. Would return if we added dependency mapping and improved performance for 100+ user workspaces.
Account: RetailHub ($42K ARR). Budget cut. Their parent company acquired them and mandated consolidation to the acquirer's existing toolset. No product issue. Low win-back probability (corporate mandate).
Account: DataFlow ($38K ARR). Onboarding failure. Signed in January, never completed setup. Their technical lead left 2 weeks after kickoff and the replacement did not know the product. CSM follow-up was delayed by 3 weeks due to caseload. Recoverable if we re-engage the new lead.
Common Mistakes to Avoid
- Pitching during exit interviews. The moment you try to save the account during an exit interview, you lose their honesty. These conversations are for learning, not selling.
- Only surveying, never interviewing. Cancellation surveys tell you what happened. Exit interviews tell you why. You need both.
- Not closing the loop with Product. If 28% of churn is due to missing features and Product never sees that data, you are learning without acting.
- Treating all churn as equal. A $5K account churning because they shut down is not the same signal as an $85K account switching to a competitor. Weight your analysis by ARR.
Key Takeaways
- Every churned customer is a learning opportunity. Capture data at cancellation (survey) and after cancellation (interview).
- Use a consistent taxonomy to categorize churn reasons. Inconsistent categories make trend analysis impossible.
- Weight your churn analysis by ARR, not just account count. One $100K churned account matters more than ten $5K accounts.
- Close the loop between churn data and product decisions. If the data does not drive action, the process is wasted effort.
- Track win-back potential. Customers who churn due to external factors often return when circumstances change.
About This Template
Created by: Tim Adair
Last Updated: 3/5/2026
Version: 1.0.0
License: Free for personal and commercial use