Why this exists
WhyLeft is a small, deliberately narrow product built by someone who got tired of guessing.
I'm Samir. I build software, and for years I did what every founder does when a cancellation email arrives: felt bad for a minute, told myself I'd look into it, and moved on to whatever was on fire.
Occasionally I'd write back and ask why. Almost every time, they answered — and almost every time, the answer was something I hadn't considered. Not the price. Not the thing I'd spent the quarter building. Something specific and small and completely fixable that I had no way of knowing about.
The problem was never that customers wouldn't tell me. It was that asking took ten minutes I didn't have, at the exact moment I least wanted to do it, and the answers ended up scattered across an inbox where no pattern could ever form. Six people telling me the same thing across eight months reads as six unrelated complaints.
WhyLeft is those ten minutes, automated — and then the part I could never do at all, which is holding a year of replies in mind at once and noticing what they have in common.
What it will and won't do
These are the constraints the product is built around. They cost real features, and they're the reason WhyLeft is worth trusting with a conversation this sensitive.
Ask, don't intercept
WhyLeft will never add friction to a cancellation. No save-offers, no discount pop-ups, no "are you sure" mazes. Making it harder to leave produces worse data and a worse business, and it's the direction regulation is closing off anyway.
Two emails, enforced in code
A cancelled customer hears from us at most twice per interview. That's a limit in the send path, not a promise in a policy document. Someone who has left owes you nothing, least of all their attention.
Their names are none of the AI's business
The automated pipelines see what people wrote and nothing that identifies them. That constraint costs a little capability and is worth it.
No feature gates
One plan, one price, everything included. Charging more for the feature that makes the product work is a tax on the customers who need it most.
Narrow on purpose
WhyLeft asks departing customers a question and helps you understand the answers. It isn't becoming a CRM, a support desk, or a growth suite. There are enough products that do everything adequately.
Where it's going
The next work is depth rather than breadth: better questions, better pattern-finding, and closing the loop between what you learn and what you ship. WhyLeft already knows who left over what — the interesting frontier is making the path from that knowledge to a shipped fix as short as possible.
We run WhyLeft on WhyLeft. When you cancel, you get the exit interview. It would be strange not to.
Product questions, feedback, or an argument about any of the above: support@whyleft.com. Or see what's shipped recently.
Your next cancellation is coming.
It can be another number on a chart, or the reason you build the right thing next quarter.
No credit card. Cancel in one click — we'd rather you tell us why.