Ask departing members what they stopped expecting
Run cancellation conversations that reveal broken promises, missing habits and avoidable reasons for leaving.
A member cancels after three quiet months. The cancellation form says “not enough time”, so you send a polite thanks and move on. A week later, another member leaves for the same reason. Then another. You have a pattern, but not yet an explanation. The useful question is not only why someone cancelled. It is: what did they stop expecting to happen here?
Start with the expectation, not the explanation
“Why are you leaving?” invites a short answer: busy, expensive, not using it. Those answers may be true, but they describe the final decision rather than the experience that led to it. A better conversation moves backwards. Ask what the member thought would happen when they joined, when that expectation became less credible and what they had hoped to do next.
- 1When you joined, what were you hoping to get done, understand or practise?
- 2What did you expect to happen regularly inside the membership?
- 3What was the last moment that felt useful to you?
- 4What did you keep expecting to find, receive or take part in, but did not?
- 5Was there a point when you decided not to make this a regular habit?
- 6What would have made staying for another month an easy decision?
Find the promise that went quiet
Members rarely cancel because one update was imperfect. More often, a promise loses its shape. “Get feedback” may become a monthly thread with no clear way to submit work. “Stay accountable” may become occasional reminders. “Meet other people like me” may become a chat tab that members open once and never revisit.
Write down the promise as a member would have heard it, then compare it with the behaviour your membership currently requires. If the promise is “make progress each week”, the product needs a repeatable weekly job: a prompt, submission, review, call or decision. If the promise is simply access to your judgement, a library or occasional advice may be enough. The point is to make the mechanism visible rather than adding more content.
| What the member expected | What may have broken | Useful follow-up |
|---|---|---|
| A reason to return each week | There was no recurring job or clear rhythm | What would you have returned to do? |
| Personal progress | The material was available but not connected to a next action | Where did you get stuck after consuming it? |
| Useful conversation | Discussion had no question, context or response from the host | What kind of exchange would have been worth joining? |
| Access to the creator | The boundaries around replies, calls or feedback were unclear | What kind of access did you think you were buying? |
Ask about the habit that did not form
A membership can be valuable and still fail to become part of someone’s routine. Ask about the practical sequence: how they knew to return, what they saw first, what they did next and whether anything confirmed that they were making progress. This is different from asking whether they liked the content. People can like a resource and never use it.
Look for friction you can remove. A new member may not know where to begin. An active member may not know which discussion needs their reply. A course buyer may not know whether to watch, practise or submit something. If your storefront is the delivery point, tools such as [hosted online courses](/features/online-courses), [memberships](/features/memberships) or [communities](/features/communities) can support different mechanisms, but the tool does not create the habit for you. Your welcome sequence and recurring instructions still have to do that work.
Run the conversation without defending the product
The person leaving is giving you information, not asking you to win a case. Avoid explaining why the resource was posted, why the member could have asked for help or how busy you have been. Those details may be relevant to your internal review, but they make the conversation less safe and usually produce more polite answers.
Send a short message after the cancellation. Offer a reply by email or a brief call, and make clear that there is no attempt to reverse the decision. Ask permission before recording or quoting anything. If someone agrees to talk, spend most of the time listening. Repeat the phrase that seems important: “You expected a weekly checkpoint, but after the first month you were mostly browsing the archive. Have I understood that correctly?”
Turn answers into changes you can test
Do not create a large list of improvements from one conversation. Tag each answer by the stage where the expectation failed: joining, starting, returning, participating or renewing. Then count repeated themes over time. You do not need a complicated research system. A spreadsheet with the cancellation date, original goal, last useful moment, missing expectation and possible fix is enough.
Choose one repeated cause and change one part of the experience. If members do not know where to start, rewrite the first-day message and make the first action smaller. If they expect feedback, publish the submission rules and a regular response time. If they need occasional advice rather than an ongoing membership, make that alternative clear instead of trying to keep everyone inside the recurring offer.
Your cancellation process should also match the promise you can actually deliver. If you sell through store.fan, a storefront at store.fan/yourname can put the offer, checkout and delivery in one place, while [email marketing](/features/email-marketing) can help you explain what happens after someone joins. That may reduce uncertainty, but it will not replace a clear membership job or an honest description of access.
Use the findings before you rewrite the sales page
A cancellation conversation often reveals a promise that was too broad to operate. Before changing the headline, compare the words on the sales page with the moments a member can actually experience. “Support” might mean a monthly call, private replies, peer discussion or a resource library. Each creates different expectations and different work for you.
Make the promise narrower if necessary. Say what members receive, how often it happens, where they begin and what they need to contribute. If you offer a course, state the outcome and the path. If you offer a community, name the job members return to do. If you offer access to you, specify the boundaries. A smaller promise that happens reliably is easier for a member to trust and easier for you to improve.
Only if price is the actual problem and the lower price still makes the offer sustainable. First ask what stopped feeling worthwhile. A discount cannot repair missing feedback, unclear onboarding or a habit that never formed.
Soon enough that the experience is still easy to recall, but not so quickly that the message feels like a retention tactic. A short, optional request after cancellation is usually enough. Give them an easy way to decline.
Keep the answers separate by member type, goal and length of time subscribed. Contradictions may show that one offer is serving several jobs. Do not average them into a vague promise; decide which member and outcome the product is designed for.
Set up a storefront for your offer and make the promise, path and cancellation process easier to review.
Start with store.fanTurn your knowledge into income
Launch your Store.Fan in minutes — sell digital products, courses, and calls straight from your bio. Free to start.
