1
5 Comments

$4K MRR and the only growth hack that actually worked: talking to users at the worst moment

We tried content. We tried cold outreach. We tried Product Hunt.
Nothing moved the needle as much as one stupid simple thing: asking users why they were leaving, right when they were leaving.
Not a survey email three days later. Not an NPS form buried in settings. A real conversation at the exact moment someone clicked cancel.
Here's what happened.
When we built Flidget.com, we knew churn was a problem for SaaS founders. But we didn't realise how bad it was until we started reading the actual responses coming through our own tool.
People weren't leaving because the product was bad. They left because of an unreported bug. A feature they couldn't find. A billing concern they never raised with anyone. Things that were 100% fixable — but nobody ever asked.
That insight became our entire marketing message.
We moved away from "churn reduction" and focused on the conversation you're not having with your users. That reframe resonated. Founders got it immediately because they'd all felt that pain — watching someone cancel and having no idea why.
We're at $4K MRR now. Not life-changing money, not yet. But the growth has been consistent and almost entirely through word of mouth from founders who tried it and couldn't unsee the problem.
The thing I'd tell any SaaS founder right now: your cancel button is the most honest feedback channel you have. Most of you are not using it effectively.
What's the most surprising reason a user ever gave you for churning?

posted to Icon for group Startups
Startups
on May 13, 2026
  1. 2

    The timing insight is the real thing here - exit surveys sent three days later are answered by people who have already moved on emotionally. The conversation at the moment of cancel catches them while the actual reason is still sharp.

    The harder problem for solo founders is what you do with what you learn. Those exit conversations generate signal, and that signal needs to go somewhere structured before it becomes a 'I should probably fix that' that lives in your head for months and never becomes a decision.

    I have a decisions database in the Solopreneur Notion OS I am building for this exact reason: each piece of user feedback that triggers a decision gets a record - what the signal was, what options were on the table, what was chosen and why, outcome tracked. So you actually build institutional memory even when you are a team of one.

    How are you handling the follow-through layer? The conversation gets the insight - what converts it into a tracked action versus a mental note that decays?

    1. 1

      Exactly this, the follow-through problem is real. Insights from exit conversations are only useful if they go somewhere actionable instead of sitting in your head as a "should fix this someday."Right now we're doing it pretty manually honestly. Tagged reasons in the dashboard go into a weekly review where we decide what becomes a real fix versus something to watch for a pattern. It's not perfect but at least the tagging forces you to name the problem before it evaporates.Your decisions database approach sounds more structured than anything we're doing. Curious how you handle the outcome tracking part — do you actually go back and close the loop on whether the decision moved the metric you expected?

  2. 1

    yeah the exit moment is the only time people tell you the truth. ask them 3 days later in a survey and they're all polite and useless. we caught our biggest churn reason this way, something we'd never have guessed from the dashboard. nice that you actually do something with it tho, most people just collect NPS and call it a day.

  3. 1

    This is such a good point, the timing part is what most people miss.

    I’ve noticed the same thing even just talking to people informally. If you ask a few days later, you get a vague “just wasn’t for me” type answer. If you catch it in the moment, it’s usually something very specific and fixable.

    The interesting part is like you said, a lot of the reasons aren’t product-breaking, they’re just things people didn’t bother raising. Which is kind of scary because you can spend weeks building new stuff while missing something small that’s actually costing you users.

    Out of curiosity, were there any reasons that genuinely surprised you? Like things you didn’t expect at all going in?

    1. 1

      The "just wasn't for me" answer is genuinely useless and you're right that timing is everything. Catch someone in the moment and they actually want to explain, it's almost like they were waiting for someone to ask.
      The small fixable things were the biggest surprise for us too. One person left because they couldn't find a feature that already existed in the product. Another had a billing concern they never raised with anyone. Both would have stayed if we'd just had that conversation earlier.
      The ones that really shifted our thinking were unexpected competitor mentions. People named tools in their exit chat that we'd never even considered rivals. That alone made us rethink our positioning more than any market research did.

Trending on Indie Hackers
I Was Picking the Wrong SaaS Tools for Two Years. Here's the Mistake I Finally Figured Out. User Avatar 120 comments Drop your landing page URL. I'll use Ferguson to tell you why visitors might be leaving User Avatar 101 comments I sold $6,773 in 2 weeks, with almost no existing community. User Avatar 42 comments Ferguson is LIVE on ProductHunt today... so I audited their homepage first! User Avatar 35 comments Why Remote Teams Stop Talking (And Don't Even Notice It) User Avatar 26 comments Built a local-first Amazon profit-by-SKU + QuickBooks/Xero journal tool. Looking for founding users. User Avatar 24 comments