How do you actually figure out why users churn? I built a small tool to test this
Hey everyone,
I’ve been thinking a lot about churn lately and realized something uncomfortable:
most teams say they track churn, but very few actually understand why users leave in a structured, actionable way.
so, I built a small MVP called Churnalysis to test the idea.
The concept is simple:
collect cancellation feedback in a structured way
run short AI-powered exit interviews
analyze patterns instead of reading random comments or spreadsheets
Right now this is nearly-finished - I’m not selling anything yet.
I’m trying to validate:
whether this is a real problem for founders / SaaS teams
what insights people actually want from churn data
whether an API-first approach even makes sense
I put together a short landing page + feedback form (2–3 minutes):
👉 https://churnalysis.darealdevelopmaster.workers.dev/
I’d genuinely love feedback on:
Is this a real pain for you?
How do you currently handle churn feedback?
What feels unclear or unnecessary on the page?
I’ll be adding screenshots below for context.
Thanks - and feel free to be brutally honest.

Replies
Hi Yousef, this is quite interesting. More interesting because I've been heads-down working on churn predictive and prevent experience, and I recognized you've been embarking on a beautiful problem as well.
If I may ask, what led you down this part, and what are some learnings you've seen out there with how teams solve for churn?
We built firstdistro.com - helps B2B companies predict customers looking to churn and quickly help teams prevent them. Would love to chat some more on this topic and how I might be able to help with your project.
- Jide