Lemon Squeezy churn playbook

How to capture Lemon Squeezy cancellation reasons.

Lemon Squeezy hands you the cancellation but not the cause. This is how to collect the reason, categorize it, and turn a pile of individual goodbyes into a grouped, fixable picture of your churn.

Quick answer

Lemon Squeezy does not store cancellation reasons. Capture them by sending a plain-text founder email after the cancel, then classify every reply into a small reason taxonomy so you can see your top reasons at a glance. ChurnNote automates the email, the classification, and the reason-tied win-back on Lemon Squeezy. Flat $12/mo.

The 4-step method

  1. 1

    Listen for the subscription_cancelled webhook

    Lemon Squeezy fires subscription_cancelled when a customer cancels. That event is the trigger, but it carries no reason. ChurnNote subscribes to it for you when you connect with your API key.

  2. 2

    Send a plain-text exit email asking why

    Instead of a survey, send a short personal email from the founder a little after the cancel, when the customer has cooled down. Plain text, your name, one honest question. This is what produces real reasons instead of one-click clicks.

  3. 3

    Classify each reply into a reason taxonomy

    Sort replies into a fixed set of reasons (pricing, missing feature, too complex, switched tool, not using it, project ended) plus a sub-reason. ChurnNote does this automatically with Reply Intelligence, so your inbox becomes a categorized view of churn.

  4. 4

    Act on the top reasons and credit the win-backs

    When one reason dominates, fix it. When you ship the fix, reach back out to the exact customers who left for that reason. ChurnNote drafts those win-backs and credits recovered MRR to the ship that earned it.

Why grouping matters more than collecting

Collecting reasons is easy. Acting on them is the hard part, and it only works once the reasons are grouped. One customer saying the price is too high is noise. Eight customers saying it in a month, all on your lowest plan, is a pricing-page problem. The same reply is worthless on its own and a roadmap in aggregate. That is why the taxonomy matters: it turns scattered replies into a ranked list of what to fix first.

FAQ

Does Lemon Squeezy collect a cancellation reason?
No. Lemon Squeezy lets customers cancel from the portal and fires a subscription_cancelled webhook, but it does not ask for or store a reason. If you want to know why customers leave, you have to collect it yourself or use a tool that does.
Should I capture the reason at the cancel button or by email?
Both, and they do different jobs. A field at the cancel button captures something from everyone, even the ones who never reply, but the answers are short and defensive. A founder-style email sent after the cancel gets fewer but far more honest and detailed answers. ChurnNote can do both on Lemon Squeezy.
How does ChurnNote categorize cancellation reasons?
Every reply is classified by Reply Intelligence into a primary reason, a sub-reason, a recoverability read, and a suggested response. Instead of a folder of one-off emails, you get a grouped view: how many left over pricing, how many for a missing feature, and so on.
What is a good cancellation-reason taxonomy?
Keep it small and stable so the groups stay comparable over time. A practical set is: pricing or value, missing feature, too complex or poor onboarding, switched to another tool, not using it, and project ended. ChurnNote uses a taxonomy like this so trends are easy to read.
Does this work on Lemon Squeezy specifically?
Yes. Most churn tools are built Stripe-first and never integrated Lemon Squeezy. ChurnNote connects to Lemon Squeezy with your API key and runs the same reason-capture and grouping loop it runs for Stripe.

Turn goodbye emails into a roadmap.

ChurnNote captures the reason on every Lemon Squeezy cancellation and groups it automatically, so you always know the top reason customers leave. Flat $12/mo.