How many questions should a SaaS cancellation survey have?

A SaaS cancellation survey should have 1–3 questions maximum. One required multiple-choice question asking for the primary cancellation reason, plus one optional open-text elaboration, achieves 40–55% response rates. Adding a third question drops completion rates by 10–15 percentage points.

What is the most common reason SaaS customers cancel?

The most common reason SaaS customers cancel is lack of use—customers who stop logging in before they cancel. ProfitWell's analysis of 23,000 B2B SaaS cancellations found 'not using it enough' accounts for 29% of cancellations, followed by missing features (23%) and competitive switching (18%).

Should I ask for cancellation reasons before or after the account is closed?

Always ask during the cancellation flow, before the account is fully closed. In-app surveys shown during the cancellation confirmation step get 42–55% response rates. Email surveys sent after the account closes get 4–18% response rates depending on timing.

How do I analyze cancellation survey responses at scale?

Segment cancellation responses by customer cohort, plan tier, and acquisition channel before analyzing reason distributions. Comparing reason distribution against revenue lost—not just customer count—reveals which cancellation drivers have the highest financial impact and should be prioritized first.

What's the difference between an exit survey and a cancellation survey?

In SaaS, exit survey and cancellation survey are used interchangeably. Both refer to the structured questionnaire presented to a customer who has decided to cancel their subscription. 'Exit interview' typically refers to a longer qualitative conversation with a churned customer, usually conducted by a customer success manager for high-value accounts.

Best Cancellation Survey Questions for SaaS

Why Most Exit Surveys Fail

Most cancellation surveys collect data that teams never act on. The failure isn't in the questions—it's in survey length, question order, and whether the data feeds back into product decisions. A cancellation survey sent after the account is already closed gets a 5–8% response rate. The same survey shown in-app during the cancellation flow gets 35–55%.

The goal of a cancellation survey is not to recover the churning customer in the moment. It's to identify the pattern that predicts future cancellations before they happen. That requires enough volume to spot trends, which means optimizing for response rate above all else.

The 7 Most Effective Cancellation Survey Questions

Use a maximum of three questions for in-app cancellation surveys. The first should always be a required multiple-choice reason picker. The second should be an open-text elaboration. The third, if used, should be a win-back-oriented question or NPS probe.

Question	Type	What It Reveals	Response Rate Impact
What's the primary reason you're canceling?	Multiple choice (required)	Root cause distribution	Baseline anchor
Can you tell us more about your decision?	Open text (optional)	Verbatim context, competitive names	−5% vs. required text
Which product did you switch to, if any?	Multiple choice (optional)	Competitive displacement data	−8% vs. no competitor Q
What would have kept you as a customer?	Open text (optional)	Feature gaps, pricing signals	−10% completion
How likely are you to return if X was added?	5-point scale (optional)	Win-back potential by feature	Low—use sparingly
How would you rate your overall experience?	1–10 NPS variant (optional)	Satisfaction baseline for churned users	Neutral
May we reach out to learn more?	Yes/No + email	Interview pipeline	15–25% opt-in rate

Cancellation Reason Categories That Matter

Across B2B SaaS products with $50–$500/month ARPU, the distribution of cancellation reasons is remarkably consistent. ProfitWell's analysis of 23,000 cancellations found: lack of use (29%), missing features (23%), switched to competitor (18%), too expensive (17%), and technical issues (8%). The remaining 5% cite business closure or budget freezes.

This distribution has a direct implication for question design. "Too expensive" is almost never the true root cause—it's the socially acceptable proxy for "not enough value relative to the price." When price is selected as the primary reason, the follow-up open-text response reveals the real driver in 70% of cases. Always include an open-text follow-up when price is selected.

In-App vs. Post-Cancel Survey Placement

Placement is the single largest variable in response rate. Surveys shown during the cancellation confirmation step—before the account is fully closed—outperform post-cancel email surveys by 4–6×. The data below reflects median response rates across 200+ SaaS products tracked in Baremetrics and ChurnBuster benchmarks.

Survey Placement	Median Response Rate	Average Time to Response	Data Quality
In-app, during cancellation flow	42%	Immediate	High (captive moment)
Email, sent within 1 hour of cancel	18%	3–6 hours	Medium
Email, sent 24 hours after cancel	9%	12–24 hours	Medium
Email, sent 7 days after cancel	4%	Variable	Low (retrospective bias)
In-app popup before cancel confirmation	55%	Immediate	High

Structuring the Multiple-Choice Reason List

The answer options in your reason picker shape the data you get. Overly broad options like "Other" or "Personal reasons" become black holes—they absorb responses that could be classified. Best practice is 6–8 specific options plus one "Other (please specify)" with a required text field when selected.

I'm not using it enough to justify the cost
It's missing a feature I need
I found a better alternative (which one? _____)
It's too expensive for my budget
Technical problems / reliability issues
My project or business needs changed
Too difficult to use or set up
Other (please describe): _____

Avoid vague options like "Doesn't meet my needs"—this is too broad to act on. Avoid options that double-count causes, such as listing both "Too expensive" and "Not enough value for the price."

Turning Cancellation Data Into Product Decisions

Raw cancellation survey data is noise until it's segmented. Aggregate reasons mask the patterns that matter. The correct analysis sequence is: (1) filter by customer cohort and plan tier, (2) compare reason distribution against revenue impact, not just customer count, and (3) identify which reasons cluster in specific acquisition channels or onboarding paths.

For a structured approach to analyzing this feedback at scale, see how to analyze cancellation feedback. If a specific reason category is spiking, the corrective action depends on the underlying driver—see how to reduce churn for a framework by cause type.

Win-back campaigns targeting customers who cited "missing features" should only launch after confirming those features are now built. Premature win-back outreach to feature-gap churners converts at under 2%; post-build outreach to the same segment converts at 8–12%. See win-back campaign playbooks for timing and messaging templates.