Primary reason
Start with one main cause.
A single primary choice is easier to trend than an unrestricted checklist.
- Use product-specific plain language.
- Include Other with optional text.
- Keep categories distinct.
Describe your subscription, customers, and cancellation flow. Makeform turns the brief into a focused exit survey with reason codes, optional follow-ups, open feedback, and consent to contact — ready to place after a customer cancels.
Send cancellation feedback to Slack, Google Sheets, and Zapier.
Sample prompts for the builder
Choose a prompt, adapt it to your product, or send it into the Makeform builder. Each structure is an example, not a live AI result.
Audience
Workspace owners canceling a SaaS plan
Format
Short exit survey with conditional reason follow-ups
Prompt size
281 chars
Example survey structure
Short exit survey with conditional reason follow-ups
What is your main reason for canceling?
Tell us more about that reason
Are you switching to another tool?
What could bring you back?
May our team follow up?
Suggested routing tags
Price
Product gap
Support issue
Keep the main cancellation reason required, but make written explanations optional. Customers who have already decided to leave are more likely to finish a short survey.
Step 1
Ask
capture one clear cancellation reason
Step 2
Clarify
show a relevant follow-up question
Step 3
Route
tag feedback for the owning team
Step 4
Learn
review patterns by segment and plan
Better cancellation feedback
A structured exit survey separates price pressure, weak adoption, product gaps, service issues, and business changes.
Use one required reason for comparable analysis, plus Other for causes you did not anticipate.
Ask about value after Price and blocked workflows after Missing feature without showing every branch.
Route product gaps, support complaints, and billing friction to the responsible teams.
Four cancellation contexts
Questions change with the buyer and billing cycle. Replace generic choices with your plans, features, and lifecycle stages.
Keep it brief, use product-specific reasons, and ask about alternatives.
Capture role, desired outcome, adoption barriers, and follow-up permission.
Design for phones and distinguish temporary pauses from lasting concerns.
Ask about benefits used, participation barriers, community, and price.
Survey workflow
Generate a focused survey, connect each reason to a useful follow-up, and review responses in a consistent rhythm with product, customer success, support, and billing teams.
Specify who is leaving, their subscription, survey placement, and decisions the answers should inform.
Use your product language and add one diagnostic follow-up per major reason.
Place it in confirmation, email, or offboarding without blocking cancellation.
Compare reasons by plan, tenure, or customer type without overgeneralizing from respondents.
Question design
Use one primary reason, a targeted branch, and one open space for nuance.
Field guide
Cover each layer from the main reason to follow-up permission.
Primary reason
A single primary choice is easier to trend than an unrestricted checklist.
Reason branch
Show one relevant follow-up instead of every possible question.
Product context
Ask what outcome the customer wanted and whether they reached it.
Value signal
A price response can mean budget, packaging, or insufficient value.
Alternative
Switching tools, returning to manual work, and abandoning the task imply different lessons.
Open feedback
End with optional comments and separate permission to make contact.
Related tools
Pair the exit survey with satisfaction, product feedback, and broader churn research forms built for adjacent customer questions.
Explore broader churn causes across canceled and at-risk customer groups.
Open toolCollect product, service, and experience feedback throughout the relationship.
Open toolMeasure satisfaction at key lifecycle moments before cancellation becomes likely.
Open toolBuild a general exit questionnaire for people leaving a program or service.
Open toolStructure the wider cancellation experience around clear choices and feedback.
Open toolAsk loyalty and recommendation questions at consistent customer touchpoints.
Open toolFAQ
Practical answers for SaaS, app, and membership teams designing an exit survey.
It is a short questionnaire for customers ending a recurring product or membership. It captures why they are leaving, what they may use instead, and what could make the subscription useful again.
Ask one primary reason, a conditional follow-up, an optional alternative, what could bring the customer back, and an open comment. Request permission separately before contacting them.
Keep it to a few questions. Branching ensures each person sees only the relevant follow-up. A longer interview can happen later with their agreement.
Show it after the customer can complete cancellation, or in the confirmation experience and follow-up email. The survey should be clearly optional and should not create confusion about whether the cancellation request succeeded.
Use single choice for consistent primary reasons, then offer optional explanation and an Other field. This creates comparable data without losing unexpected experiences.
Yes. Conditional logic can show a price-and-value question after Price, a blocked-workflow question after Missing feature, or an experience detail after Support or Reliability. Keep each branch short and focused on information a team can act on.
Yes. Makeform is unlimited free for generating, editing, publishing, and collecting responses. The paid tier removes the Makeform badge, so you can build and use the survey without a usage gate on the free plan.
Review the primary reason mix alongside comments and relevant context such as plan, tenure, or customer type. Track definitions consistently over time, read verbatim feedback, and avoid treating survey respondents as a perfect representation of every customer who canceled.
Turn canceled subscriptions into clearer product decisions.