Every cancellation survey I've ever read tells the same story. Forty-something percent say "too expensive." A chunk say "not using it enough." The rest split across "missing features," "switched to a competitor," and the ever-popular "other." Then the team argues about pricing for a quarter.
I don't think "too expensive" is a lie. I think it's a shrug. It's the answer people give when they've already decided, the cancel button is right there, and the dropdown is between them and the door. A 2022 Directions Research survey of 1,054 US adults found 43% of people likely to cancel a subscription named cost as the reason. That's the ceiling of what a dropdown can tell you: a plausible category, chosen in about four seconds, by someone who's done talking to you.
The reason you can act on lives two or three questions deeper. This post is about how to get there: the cancellation survey that belongs in the flow, the churn interview that belongs a week later, the questions I'd ask at each stage, and how to run it when you have 200 cancellations a month and no one to call them.
The dropdown is a receipt, not a diagnosis
When someone picks "too expensive," here's what they usually mean, in my experience:
- The value dropped and the price didn't. They'd have paid it six months ago.
- A cheaper tool covers the 20% of your product they were using.
- Their usage never got past the trial habits, so any price felt like paying for nothing.
- Budget got cut and yours was the easiest line to delete, which is a statement about how visible your value was to whoever holds the budget.
Four different problems. One checkbox. If you fix pricing because the checkbox said so, you'll solve the fourth problem for a while and none of the others.
The pattern holds for the other options too. "Not using it enough" is usually an onboarding story. "Missing features" is usually one feature, and the interesting part is what they were trying to do with it. "Switched to a competitor" is the beginning of a sentence, not the end of one.
So the goal of the in-flow survey isn't to learn why they left. It's to get the one piece of context that lets you have a real conversation later, without making the exit feel like a hostage negotiation.
Stage one: the cancellation survey (keep it to one question)
I'd put exactly one question between a customer and the cancel button, and I'd make it open-ended.
involve.me tested this on their own product. They replaced a multi-option dropdown with branching logic with two open questions, "What made you cancel?" and "What could make you reconsider?", and their response rate went up 11%. People who are leaving will still type a sentence if you ask like a person instead of a form.
My version:
Before you go, what changed? One sentence is plenty.
Not "why are you cancelling." "What changed" points them at the event, and the event is what you want. "Price went up" and "we lost the client we used this for" and "I found something that does the export I need" are three completely different answers that would all land in the same dropdown bucket.
Two rules for this stage. First, the cancel button stays visible and works. The moment the survey feels like a wall, the quality of what people type collapses into "just let me leave." Second, don't pitch a save offer here unless the answer triggers it. A discount offered to someone who left because the export was broken is insulting, and it teaches everyone else to cancel to get a discount.
Stage two: the churn interview (a week later)
The interview is where the real reasons live, and timing matters more than most teams think. Inside the first day or two, people are still annoyed, and you'll get the grievance rather than the story. Wait a month and the story has hardened into a tidy one-liner they've told three colleagues. Somewhere around a week to two weeks out, the decision is still fresh but the heat is gone. That's when I'd ask.
The frame I use is borrowed from Bob Moesta's switch interview, the jobs-to-be-done technique for reconstructing a purchase. A cancellation is a switch too, just in reverse. You walk the timeline backward from the moment they hit cancel and find the first moment they thought about leaving. Most of what you need is between those two points.
The question bank, by stage of the timeline
The first thought. Find the moment doubt started, not the moment they acted.
- When did you first think you might not keep using [product]? Not when you cancelled. The first flicker.
- What was going on that week? What were you trying to get done?
- Was that a one-time event, or had it been building?
The push. What made staying harder than leaving.
- What did you try inside [product] before you started looking elsewhere?
- Was there a specific task you gave up on? Walk me through the last time you tried it.
- Who else was involved in the decision? What did they say?
The pull. What the alternative offered, if there was one.
- What are you using now for that job? (Including "a spreadsheet" or "nothing.")
- What does it do that mattered enough to move?
- What did you lose by moving that you're living with?
The decision. The actual mechanics of the exit.
- What happened the day you cancelled? What was the last straw, if there was one?
- Did you look for a way to stay first, like a cheaper plan or a pause? What did you find?
The counterfactual. The single most useful question in the set.
- What would have had to be true for you to still be a customer today?
Note what's not in there. No "how likely are you to recommend us" (they just left). No "which features did you like most" (irrelevant). No "would you come back if we fixed X" (they'll say yes to be polite). Every question is about a specific moment or a specific job, because specifics are the only thing you can build from.
The probing rules that make the questions work
The list above is the easy part. What separates a churn interview from a churn survey is what happens after each answer.
- Unpack every vague word. "It got clunky." Clunky doing what? On which screen? Compared to what? "Too expensive." Expensive relative to what you were getting, or relative to what else was available?
- Ask for the scene, not the opinion. "Tell me about the last time you opened it" beats "how was your experience." People remember scenes. They invent opinions.
- Follow the emotion. When the voice changes or the sentence speeds up, that's where the real reason is. "It made me look bad in front of my boss" is a root cause. "The reporting wasn't flexible" is the same fact with the feeling removed.
- Don't defend. The second you explain why the feature works that way, the interview is over. You're collecting, not correcting.
This is the part that doesn't scale with humans. A good researcher can run maybe five of these a day and stay sharp. Most SaaS teams don't have a good researcher, and the ones that do have her booked.
Running it at scale with an AI interviewer
This is the problem we built ChatWisp around, and churn is where it earns its keep, so here's how I'd set it up. The mechanics generalize to any AI-moderated interview tool.
Put the one-question survey in the cancel flow, and make the interviewer ask it. A conversational form asking "what changed?" and then one context-aware follow-up gets you the event plus one layer of why, in under a minute, from a much larger share of cancellers than a link in an email ever will. In ChatWisp you'd cap follow-ups on the "what changed" question at one, and set the motive and guardrails so the interviewer never pitches, never argues, and never asks a second time if the person says they're done. The cancel button stays on the page.
Send the full interview a week later, by voice if they'll take it. The 12-question bank above becomes the interview script, with the timeline questions as the required spine and the probing rules encoded as the conversation style. Voice matters here: people say things out loud they won't type, and a spoken answer to "what would have had to be true" runs a lot longer than a typed one. Offer both. Someone cancelling on their phone at 11pm isn't going to talk, and that's fine.
Route by what they said, not by which box they ticked. Conditional logic off the stage-one answer decides what the interviewer leans into. "Lost the client we used this for" gets the budget-holder questions. "Found something that does X" gets the pull questions. A save offer, if you make one at all, triggers off a specific answer and never appears otherwise.
Read the transcripts, then the tags. The output you want isn't a pie chart of reasons. It's forty transcripts you can search for "the last time I tried" and a theme summary you can argue with. ChatWisp's Insight Analyst does the second part, but I'd still read the first ten transcripts of any new churn program by hand, because the categories you'd pick in advance are the dropdown all over again.
What this won't do
It won't save the customer. That's not the point, and the fastest way to poison the data is to let the retention team turn the interview into a save flow. Keep them separate.
It won't get everyone. A good share of cancellers will type one sentence and take nothing further, and a smaller share will take a 10-minute voice interview a week later. That's normal. My rule of thumb is that somewhere between fifteen and twenty-five real interviews per segment is enough to see the pattern, and most SaaS teams will hit that inside a month.
And it won't replace looking at the account. Stated reasons plus usage history plus support tickets is the diagnosis. Any one of the three alone is a guess. The interview is the piece most teams are missing, not the only piece.
Start with the counterfactual
If you do one thing after reading this, add "what would have had to be true for you to stay?" as an open question somewhere a cancelling customer will see it, and read every answer for a month. It's the question the dropdown can't ask, and the answers cluster fast.
Then, when you're ready to ask the other eleven, ask them the way you'd want to be asked: one at a time, in your own words, by something that listens to the answer before deciding what to say next. The same approach works for the follow-up behind an NPS score, and for most of the product feedback you're currently collecting with a form.