A customer exit survey asks people who cancel why they left, and the answer that often comes back is “too expensive.” Spoke asks the follow-up that finds out what the price was measured against: the part they never used, the setup they never finished, or the tool they switched to.
They didn't churn on price. They churned on a setup step nobody finishes.
An example of the line the Agent Results Brief leads with.Most cancellation flows answer “too expensive” with a discount offer. That can keep a customer for a month, but it doesn't tell you what the price was measured against. One follow-up usually does. Examples, not real respondents.
Not the price: a paid feature they were never shown how to use.
They only ever used the part a spreadsheet can do. The rest never got a chance.
The person who liked it had nothing to show the person who pays. A usage summary before renewal was the missing piece.
Usage dropped because a second person couldn't get in, not because the need went away.
Under every question is the follow-up Spoke asks when the first answer is vague. That second question is where the real answer usually is.
What's the main reason you cancelled?
What were you hoping it would do that it didn't?
What were you trying to do when you left?
What did you end up doing instead?
What did you use us for most?
What did that look like on a typical day?
What, if anything, made you hesitate before cancelling?
If we'd fixed one thing sooner, which one would have changed your mind?
What did we do well that you'll miss?
When did that matter most to you?
What did you expect to get for what you were paying?
Which part of that didn't you get?
What are you comparing the price with?
What does that option do for you that we didn't?
Which parts did you use in a typical week?
What else was in the plan that you didn't get to use?
What would have made the price feel worth it?
What would you have used it for then?
Who decided it cost too much?
What would they have needed to see to call it worth it?
When did you first think about cancelling?
What was happening that week?
How often were you using it in the month before you cancelled?
What took its place in those weeks?
What are you using instead now?
What made that the one you picked?
How does it compare with us for what you need?
Which part of that matters most to you day to day?
What would we have to change for you to come back?
What would that change let you do that you can't do now?
What would you tell a friend who was thinking of signing up?
What would you tell them to check first?
Every person gets interviewed, not surveyed. Spoke asks, listens, and follows up on what that person actually said. Here's an example.
Read the answer, not the transcripts: themes ranked by how many people raised them, the quotes behind each, and the places where two groups disagree.
Price barely comes up once Spoke follows up. Most churned customers describe the same wall: a data-source setup step that needs a credential they don't own, with the trial clock running. Several say they never saw the product working with their own data.
An example Agent Results Brief. The counts, themes and quotes are illustrative, not from a real survey.
Whatever they pick in the cancel flow, the reason is a label. Here is the follow-up for each one. The same questions work for a client or B2B account that doesn't renew: ask them in the non-renewal conversation instead of a form.
| They say | Ask next | What it tells you |
|---|---|---|
| “Too expensive” | What are you comparing the price with? | Whether it's the price, or value they never reached |
| “Missing a feature” | What were you trying to do when you needed it? | The job behind the feature request |
| “Switched to another tool” | What made that the one you picked? | What the other option does that mattered |
| “Not using it enough” | What took its place in those weeks? | Whether the need went away or something got in the way |
| “Support or onboarding” | Where did you get stuck the last time you needed help? | The step or reply that lost them |
| “Our business changed” | How did that change what you needed from us? | Whether a different plan or product would still fit |
A dropdown in the cancel flow gets a reason from almost everyone. An exit survey adds a few open questions. An interview follows up. With Spoke you send one link and get the interview's depth from every customer who answers.
| Cancellation dropdown | Customer exit survey | Interview with Spoke | |
|---|---|---|---|
| What you get | One reason from a list, like “too expensive” | The reason plus a few typed answers | The reason, the moment they decided, and what it was measured against |
| Follows up on “too expensive” | No: at most it offers a discount | No, it keeps the first answer | Yes, on every vague answer |
| When it happens | In the cancel flow, before they leave | By email, soon after they cancel | By link, in the app or by email, soon after they cancel |
| Compare across customers | Yes, but only the labels | Yes, if you read every answer | Yes: reasons counted across everyone who answered |
| Your time | None after setup | Minutes to send; reading is on you | Minutes to send; you read the answer |
Keep the dropdown if you have one: it's a good first question. Send the interview to the people who picked a reason, so you learn what the reason meant.
What do you want to learn, and who's answering?
Drafted the spec. Should I ask what they switched to, or keep it to their experience with us?
Start with the main reason they cancelled and what they were trying to do when they left. Then add the group that fits their answer: what “too expensive” meant, the moment they decided, or what they switched to.
Pick two or three of these for most cancellations. Spoke's follow-ups add the depth, and you can cap the interview at 5, 10 or 15 minutes.
Right away, while the reason is fresh: a question in the cancel flow, then an email link within a day or two. For annual plans, ask within a week of the renewal date they let pass.
Ask what they're comparing the price with and what they expected to get for it. In the examples above, the answer turns out to be a feature they never set up, or a tool that does the one part they used.
Ask first, offer later. A discount offered before you know the reason can miss: it won't help a customer who never finished setup or who needed a feature you don't have.
Group the answers by the real reason, not the dropdown label, and count how many customers gave each one. Then read a few answers from the biggest group before deciding what to fix first.
Free to start. No card. Your first ten agent surveys are on us.
