Lemon Squeezy churn playbook

Why Lemon Squeezy customers cancel, and how to actually find out.

Lemon Squeezy tells you that a customer cancelled. It never tells you why. That missing why is the whole game: it is the difference between a number going down and a roadmap of fixable reasons. Here are the reasons founders actually see, and how to capture them honestly.

Quick answer

Lemon Squeezy does not capture a cancellation reason. To learn why customers leave, send a short plain-text email from the founder after they cancel and group the replies into a reason taxonomy. ChurnNote automates exactly that on Lemon Squeezy, then turns recurring reasons into targeted win-backs. Flat $12/mo.

The six reasons behind most Lemon Squeezy cancellations

Missing feature

They needed something you had not shipped yet, so they switched to a tool that had it. This is the most recoverable reason, because the moment you ship the fix you have a concrete reason to reach back out.

Price or value

The price stopped matching the value they were getting, often because they were not using the product enough to justify it. The fix is usually onboarding or a lighter plan, not a discount.

Switched tools

A competitor won them over, or they consolidated into a tool they already paid for. Worth knowing exactly which tool and why, so you can decide whether it is worth competing on.

Not using it

They never built the habit. Often the cancel is months of quiet inactivity finally showing up. Churn Radar catches this before the cancel, but when it slips through, the exit reply confirms it.

Too complex

They could not get to value fast enough and gave up. The cancel reason reads like a feature gap but is really an onboarding gap, which is a different (and cheaper) fix.

Project ended

The customer genuinely no longer needs the product. Not every cancel is recoverable, and knowing which ones are not keeps you from wasting win-backs on people who will never come back.

The point is not the list, it is the distribution. You cannot fix churn you cannot see, and a stack of individual cancellation emails is not a distribution. Categorize the reasons and the top one or two are usually obvious, and usually fixable.

Ask after the cancel, not during it

A reason field on the cancel button is asked at the worst possible moment. The customer has already decided and wants to be done, so you get a one-word click that confirms nothing. A short, plain-text email sent in your name a little later, once the friction has passed, reads like a real person asking a real question, and tends to get longer, more honest answers than a survey ever will. That reply, in the customer's own words, is the raw material for every win-back.

How to capture and categorize Lemon Squeezy cancellation reasons →

FAQ

Does Lemon Squeezy tell me why a customer cancelled?
No. Lemon Squeezy fires a subscription_cancelled webhook and lets the customer cancel from the portal, but it does not ask why or collect a reason. You get the fact of the cancellation and nothing about the cause, which is the part you actually need to fix it.
Why not just add a reason dropdown to the cancel flow?
A dropdown at the cancel button gets rushed, defensive, one-click answers because the customer is mid-exit and wants to be done. A short personal email sent after they have cooled down gets longer, more honest answers. ChurnNote does both: it can capture a reason at the cancel button and follow up with the founder-style email.
How does ChurnNote find out why Lemon Squeezy customers cancel?
When the subscription_cancelled webhook fires, ChurnNote sends a plain-text exit email in your name asking why. Each reply is classified by reason, sub-reason, recoverability, and a suggested response, so you get a categorized view of your churn instead of a folder of one-off emails.
What do I do once I know the reasons?
Group them. When one reason shows up repeatedly (a missing integration, a confusing onboarding step), that is your roadmap. When you ship the fix, ChurnNote drafts win-backs to the exact customers who left for that reason, so the feedback turns into recovered revenue rather than a spreadsheet.
Does this work with Lemon Squeezy or only Stripe?
Both, natively. Most churn tools are built Stripe-first and never added Lemon Squeezy. ChurnNote connects to Lemon Squeezy with your API key and runs the same exit-email and reason-capture loop it runs for Stripe.

Stop guessing why they left.

ChurnNote asks every cancelled Lemon Squeezy customer why, in your voice, and hands you the reasons grouped and ready to act on. Flat $12/mo.