Flidget

This reframe honestly stopped me for a second because you're right and I hadn't seen it this way before.

The founder didn't reach out because he knew something was wrong. He reached out because Flidget gave him a specific reason to. Without that drift signal he would have assumed everything was fine like most founders do.

"Permission to help" is actually a much more honest description of what the product does. It doesn't save accounts. The founder does. Flidget just tells him when it's worth trying.

I have more stories coming in now and this pattern shows up in almost all of them. Would love to dig into this with you, what did you have in mind?

Flidget tracks signups. You haven't created an account. Happy to be wrong if you can share the email you signed up with.

Glad it resonated. You can get started directly at flidget.com — setup takes around 10 minutes. If you run into anything or need help, just drop us an email at hello@flidget.com and we’ll take care of it.

Not really advertising, just sharing what I built and asking for honest feedback. IH feels like the right place for that. People here are building too, so the conversations are actually useful. Reddit is great for reach but this isn't about reach right now, it's about finding people who get the problem.

Both actually. Drifting users show up in the dashboard with a priority queue so you always know who needs attention first, and you can set up automatic alerts so you get notified the moment someone crosses into Drifting territory without having to check manually.

On the intervention side yes, that is already in there. Once someone is flagged as Drifting you can trigger a rescue email directly from the same view, either manually or fully automated based on the drift action that fired. The email suggestions are shaped by the actual signals so if someone stopped using a specific feature the outreach reflects that rather than sending a generic check-in.

The goal was always to close the loop fully. See the risk, understand why, act on it, all from one place without jumping between tools.

This is genuinely one of the better pieces of feedback we have gotten on the post itself, thank you for breaking it down like that.

You are right that it was intentional. The structure mirrors the product logic, lead with the pain before the skepticism kicks in, same way the widget catches the reason before the user mentally moves on. Good to know it landed.

On drift detection being under-explained, completely agree. It is honestly the more interesting layer and we compressed it into two lines because we did not want the post to feel like a feature dump. But you are right that it deserves its own post. The idea that you can see someone quietly heading toward cancel weeks before they get there, based on actual usage patterns not just login frequency, is a different conversation entirely.

Going to write that one next.

Honestly the most surprising one was a Safari bug.

The product worked fine on Chrome, fine on every internal test. But a segment of users on Safari were hitting a silent rendering issue that broke a key part of the flow. They never reported it. They just quietly stopped using it and eventually cancelled.

Nobody said "Safari bug" in a survey. They said "product felt buggy" or just nothing at all. The in-page chat caught someone saying exactly what broke and when. We found three more users who had hit the same thing within the same week.

One bug fix, three potential saves. That one still sticks with me.

This is honestly one of the best examples of drift detection I've heard and you're doing it without any software.

The attendance drop is exactly the signal, same logic as what Flidget tracks but for a gym. And the "how's life man" call is the intervention at exactly the right moment, before they've mentally checked out.

What you're describing is retention done right. Not a discount email, not a survey, just a human noticing and reaching out. The fact that people break down in tears tells you everything about how rare that feels.

We're essentially trying to bring that same instinct to SaaS. Catch the signal early, respond like a human, not like a tool. You've clearly figured out the hard part already.

Really sharp observations, worth addressing properly.

On survival bias, you're right that the cancel button only catches the loud churners. Drift detection is a separate layer that tracks real usage events, login gaps, key actions not taken and flags users Risky or Drifting weeks before they ever see a cancel screen. In-page chat is the last line, drift catches the silent ones way before that.

On voice, adoption has been better than expected. Roughly 40% of responses come in via voice. The office friction concern is real but cancel is usually a solitary decision, people aren't cancelling in open standups. Text fallback is always there so completion rates stay healthy.

Good luck with the PMF hunt, thinking about churn instrumentation this early is already a good sign.

Thanks for this, really appreciate it.

you are right about the missing qualitative layer. what we keep seeing is that the real reason is almost never what founders expect. pricing comes up way less than people think. it is usually something small that never got fixed because nobody knew it was broken.

and yes the intuition problem is everywhere. founders build features based on what they assume users want and churn tells them something is wrong but not what.

would love to see what Right Suite is surfacing on the messaging side. feels like the two problems are connected, bad messaging brings in the wrong users and then churn looks high even when the product is solid.

This is probably the sharpest framing of the problem we have heard.

You are right that we treat them as two layers right now and that is a limitation worth being honest about. The cancel moment captures the stated reason. Drift captures the behavioral signal. But neither of them shows you the actual decision forming, which is the thing that would let you intervene meaningfully rather than just respond.

The timeline idea is where we want to go. Not just "this user is drifting" or "this user said pricing" but here is the sequence of moments where trust started eroding, engagement dropped, and the decision quietly closed before they ever clicked cancel.

That is a harder problem than most churn tools are trying to solve. Most are optimizing for better data collection at known moments. What you are describing is making the invisible decision process legible before it becomes a data point at all.

We are earlier on that than we would like to be. But this is exactly the direction. Appreciate you pushing on it this clearly.

Honest answer - we did not do formal pricing interviews before launching.

We looked at what founders were already paying for tools that solved adjacent problems. Intercom, Hotjar, survey tools. All of them significantly more expensive for significantly less specific insight.

Then we thought about the math from the buyer's side. If one recovered user at $49 a month covers three months of Flidget you are ROI positive on the first week. That math had to work at every plan tier otherwise the pricing would feel like a gamble instead of an obvious yes.

The free tier was deliberate. Not a trial. Not a time limit. Just enough completions to see the first real signal and understand what you are actually buying before spending anything.

After launch we adjusted once. The original starter plan was slightly higher and the feedback was consistent that early stage founders wanted to see more value before committing. We brought it down and conversion improved immediately.

The validation we trust most is not what people say about pricing in interviews. It is whether they upgrade after the free tier without us asking. That tells you whether the value landed or not.

Most teams who see two or three completed exit conversations upgrade on their own. That is the pricing signal we pay attention to now.

Yes that is exactly what the offer bar does.

When someone clicks cancel the exit chat opens first. While that conversation is happening the offer bar sits right there on the same page. Discount, extended trial, plan downgrade, whatever you configure from the dashboard.

The smart part is you can trigger the offer based on what the conversation detects. If someone mentions pricing the offer bar can show a discount automatically. If they mention a missing feature it can show a roadmap update or a workaround instead.

So the flow is cancel click, conversation starts, reason detected, relevant offer shown, original cancel either proceeds or does not depending on what they choose.

No redirect. No separate flow. All of it happens on your domain right where they already are.

This is exactly the kind of insight that never shows up in a churn dashboard. "Loved the product but did not understand the setup" is not a pricing problem or a competition problem. It is an onboarding problem wearing a churn label.

The fact that one honest conversation changed your retention curve more than months of feature work probably did says everything about where the real leverage is.

Most teams would have seen that user churn and assumed product market fit issues. You asked and found out it was a two week fix.

All the time. And it is always obvious in hindsight which makes it worse.

The most common one we see is the bug that multiple users hit, never reported, and just quietly left over a span of weeks. When you finally piece it together from exit conversations you can see five people mentioned the exact same thing across a thirty day window. The signal was there the whole time. Nobody connected the dots because the dots were never in the same place.

The timing thing you mentioned is the real unlock. Same insight captured at the wrong moment is basically useless. A churned user filling out a survey two weeks later gives you a vague summary of how they feel about leaving. That same user mid-cancel gives you the specific moment, the specific frustration, and often the specific fix.

The structure piece matters just as much though. Raw honest feedback at the right moment still goes nowhere if it lands in an inbox or a spreadsheet nobody checks. The insight has to be captured, tagged, and surfaced in a way that puts it in front of the person who can actually do something about it.

Timing gets you the truth. Structure gets the truth to the right person. Both have to work together or the signal dies somewhere in the middle.

Fair question. A feedback button is reactive. It only works if the user decides to click it which most never do especially when they are already frustrated and halfway out the door.

The cancel page is different. That is the one moment where you have their full attention and they actually have a reason to talk. They are not browsing, they are leaving. That emotional state gets you honest specific answers that a passive feedback button almost never captures.

Also a feedback button tells you what annoyed people enough to report. The exit chat tells you what made them leave quietly without saying a word. Those are two completely different signals.

Most churn is silent. The people who click feedback buttons are the vocal minority. The ones who just cancel and disappear are where the real pattern lives.

Fair point on the 90 seconds. But the exit chat is not just a retention tool, it is a signal tool. When 30 percent of exits mention the same confusing flow you now know exactly what to simplify. The conversation at the door tells you what to fix before the door.

On AI search sending users to five tabs at once, that is exactly why the feedback matters more now not less. You cannot out-feature five alternatives. But you can know why people left and fix it faster than anyone else.

I get your point, churn can be complex and not everything is a $0 fix.

We’re actually using ML as well to identify patterns and predict drop-offs. The point I was making is that a surprising chunk of churn still comes from small, fixable issues that users never report.

ML helps you spot the signal, but the real insight often comes from actually talking to users at the right moment.

Congrats on the launch, that first live moment after years of working towards it is a big deal.

Honestly I would not touch paid ads yet. You do not have enough signal on what makes someone stick around and you will just burn money optimizing for signups that may not convert to engaged users. That is exactly the trap the article is about.

For an entertainment product built around collecting and unlocking content the early growth is almost always community driven. Find where your target audience already hangs out. Reddit, Discord, niche Facebook groups, even TikTok if the content is visual enough. Show up there genuinely, not just to drop links.

A few things that actually move the needle early on for this type of product are giving early users something exclusive. A rare card, early access to a content drop, a founder badge. Something that makes them feel like they got in early and that feeling is worth sharing.

The other thing I would focus on before anything else is just talking to the first 50 people who sign up. Not a survey. Just a real conversation. What did they collect first. What made them come back. What felt confusing. That feedback is worth more than any ad spend right now.

What niche is the card collecting around? That would change the go to market approach quite a bit.

Appreciate it, glad it resonated.

One of those lessons you only need to learn once 😅

Really appreciate this, “silent churn” is exactly it.

The digital body language part is interesting too. There are definitely signals before someone cancels, but honestly they are easy to miss or overthink.

What surprised me was how simple it gets when you just ask at the moment they leave. No guessing, just the real reason.

Feels like combining both would be powerful.

And yeah, that leaky bucket lesson hurt enough that it sticks 😅

That’s a really good way to put it, the timing problem really does cut both ways.

I like the Stripe layer you’re talking about. Those signals tell you something is off, even if they don’t tell you exactly why. It’s more like an early warning before things reach the cancel point.

From what I’ve seen so far, around 25 to 35 percent are clearly fixable. Broken flows, confusing UX, edge cases, things like that. Then there’s a middle group where it’s partly fixable but needs more effort or better positioning. And the rest is just not the right fit or timing.

The interesting part is the fixable ones almost never say anything unless you catch them at that exact moment. That’s where most of the value is hiding.

Honestly feels like your approach and this together make a lot of sense. Detect early and then ask at the right time.

Honestly the "test as a customer" habit is underrated. Most founders never do it and then wonder why churn looks the way it does.

The thing is though most of your real users won't tell you when something feels off. They just leave. That's exactly why we built Flidget - catch that feedback at the exact moment they're about to go.

Curious what's the most surprising thing you've found broken that you had no idea about?

You nailed it. The day 2-3 window is where most silent churn actually starts. By the time someone hits the cancel page the decision is already 80 percent made. The exit chat catches the ones still on the fence but you are right that the real opportunity is earlier.

Honestly that is the next layer we are thinking about. The cancel conversation gives you the pattern. Once you see that 30 percent of exits mention a specific flow or a specific moment you now know exactly where to look inside the product.

So it becomes a two step thing. Exit chat surfaces the signal. You take that signal back into onboarding or the day 2-3 experience and fix the friction before it becomes a cancellation.

The exit conversation is almost like a diagnostic tool as much as a retention tool. Most teams use it only for win-backs but the smarter use is feeding those insights back into the activation funnel.

The founders getting the most value from Flidget are the ones doing exactly that. They filter by reason, find the pattern, and then go fix the moment where users first hit the wall. Churn drops not because they are saving cancellations but because fewer people are reaching that point in the first place.

Would love to hear what friction points you have seen show up most consistently at that day 2-3 stage.

Exactly right. Saving everyone is actually the wrong goal.

A bad fit user who stays becomes a support nightmare, a bad review, and churns anyway six months later with more damage done.

The three way split you laid out is the real framework. Bug goes to engineering. Bad fit goes to ICP refinement. Confused user goes back to onboarding. Treating all three the same is where most retention efforts waste time and money.

The pattern detection before cancellation is the layer that compounds everything. The exit chat gives you the signal. The smarter move is taking that signal and working backwards to find where the friction started in the first place.

Most teams use churn data to save users. The ones who grow fastest use it to stop the next hundred from ever reaching that point.

This is the conversation most churn discussions never get to. Appreciate you adding this layer.

The 48 hour window is the whole thing. After that the specific moment that frustrated them has faded and you get vague feedback you cannot act on.

The one number problem is what makes most churn work feel useless. You end up optimizing against a combined metric where half of it was never yours to fix. Building features for bad fit users. Discounting people who were leaving anyway. Never finding the fixable 30 percent sitting quietly underneath.

Separate the two and every decision gets cleaner. Roadmap, ICP, win-backs, all of it sharpens immediately.

Most tools show you the number. Very few help you understand what it actually means. That is the gap we are trying to close.

Best resource hands down is Mom Test by Rob Fitzpatrick. Small book, reads in a few hours, completely changes how you think about user conversations.

Core idea is simple. Never ask people what they want. Ask them about their life, their problems, their past behavior. People lie about the future but they cannot lie about what already happened.

Few things that actually work in practice.

Ask about the last time they had the problem not whether they have the problem. Specifics beat opinions every time.

Stay quiet after they answer. Most of the real insight comes in the second sentence not the first.

Never pitch during the interview. The moment you start selling they start being polite and you lose the honest signal.

For churn specifically the cancel page conversation works better than a scheduled interview because you are catching them at the exact moment of the decision. No scheduling, no context switching, no faded memory. The frustration is still fresh and they will tell you things they would never say in a formal call two weeks later.

That combination of Mom Test principles applied at the exit moment is honestly the most underrated user research setup most SaaS teams are not doing.

Exactly this. Assumptions feel like confidence but they are just expensive guesses.

One real conversation with a churned user is worth more than three months of dashboard staring.

That is literally why Flidget exists. To make that conversation happen before it is too late.

530 Shopify app reviews is a serious data set and that pattern you are describing is exactly what we kept hearing before we built this. Merchants optimizing the top of the funnel while the bottom is quietly leaking.

On your question about response rate vs quality, honestly quality wins every time. We would rather have 3 honest sentences from someone mid-cancel than 50 survey responses filled out two days later when the emotion is gone.

The cancel moment is unique because the user has already made a decision. They are not trying to be polite anymore. That honesty is the whole product. A 15 percent response rate with real actionable feedback beats a 60 percent survey completion rate of "it was okay" every time.

What we found is the responses cluster pretty naturally. Broken flow. Price confusion. Missing feature. Wrong expectation set at signup. Once you see the same reason show up three times you know exactly what to fix.

Curious what the most common hidden cost was across those 530 reviews. Was it post purchase experience or something earlier in the flow?

That "pleasantly surprised we care" moment is so underrated. Most companies just let the cancel happen and move on. The fact that a simple email brings them back says everything about how low the bar is for just showing up.

The silent cancellers are the most interesting segment honestly. They are not angry. They are not vocal. They just drifted. And that drift is almost always fixable if you catch it at the right moment.

That is literally the problem Flidget was built for. Instead of waiting to email them after they leave, we put one honest conversation right on the cancel page. Same energy as your follow up email but before the decision is final.

What percentage of those re-engagements actually stick around the second time?

You are not overthinking it at all. The pre-cancel ghost is honestly the scariest cohort because there is no moment to catch. No click. No signal. Just a user who made the decision in their head and quietly walked out.

The pricing page insight is sharp. A paying user reopening pricing is not curiosity it is a question they are asking themselves and right now that question just disappears into the void.

We have thought about this surface. The challenge is intent is blurry at that point. On the cancel page you know exactly what is happening. On the pricing page it could be a "should I upgrade" visit just as much as a "should I leave" one. So the prompt has to be softer and more open ended which kills response rate like you said.

But here is what I keep coming back to. Even a 5% response rate on that cohort is conversations you would never have had. And those are the users who never clicked cancel so they are still recoverable.

What patterns are you seeing in the pricing page data? Curious if there is a time on page or scroll depth threshold that separates the upgrade intent visits from the exit intent ones.

Totally agree, that part hurts the most.

Spending thousands to acquire users and then losing them over something fixable is just bad visibility more than anything else. Most founders obsess over the top of the funnel, but almost no one looks at what happens at the exit.

And yeah, that 0.3 number feels small until you actually calculate it on your own MRR… then it gets uncomfortable real quick.

The crazy part is, it’s not even a product problem most of the time—it’s just that no one asked at the right moment.

That’s exactly it.

The signal was always there, just buried. That random reply wasn’t luck—it was proof people were willing to explain, just not through the usual channels.

And yeah, that’s the painful part… $0 fix, but the gap was in listening at the right moment. By the time we usually ask, the context is already gone.

Made me realize churn isn’t always a product problem - it’s often a timing problem.

Timing is the whole product honestly. The insight does not change, the window to act on it does.

Survey sent three days later gets you a polite summary. Conversation caught mid-cancel gets you the real reason. Same person, completely different truth.

Same way most founders find out about their real problems. By accident.

One churned user replied to a cancellation email out of nowhere and explained exactly why they left. Something small. Something fixable. Something we had no idea about because our cancel page just let people disappear silently.

That one reply made us go back through two months of cancellations and actually try to talk to people. What we found is that nearly a third had left for a reason that had nothing to do with pricing or competitors. Just small fixable things we never knew about because we never asked.

That was the whole idea behind Flidget. Stop waiting for the accidental reply and just ask every single person the moment they decide to leave.

And thank you, glad the site landed well.

That three week reply is such a specific feeling. You have already written that user off, moved on, and then out of nowhere they hand you the exact thing you needed to hear at the exact moment you were least expecting it.

And you are right it is worth more than 100 survey responses. Surveys catch people when they are being polite or when they have already forgotten the specifics. That reply caught someone when the reason was still real and specific and honest enough to actually act on.

The uncomfortable part is thinking about how many of those replies never came. Same reason. Same fixable problem. Just people who moved on and never looked back.

That one reply is what made us build Flidget. Trying to make sure that conversation happens every time instead of by accident three weeks later.

You are right that timing is the whole problem. The insight means nothing if you find out three weeks after they cancelled.

On the validation angle that is a genuinely interesting point. What we found early on is that the cancel conversation itself becomes a validation signal. When the same fixable reason shows up three times in a week that is your experiment right there. You already know there is demand for the fix before you build it.

The founders who get the most out of Flidget are the ones who treat every cancel conversation as a prioritization tool not just a retention tool. Someone leaves because a feature is missing. You fix it. You reach back out. Some of them come back. That loop is faster and cheaper than any formal experiment because the demand signal and the audience are already in front of you.

The structured experiment layer you are describing would make that loop even tighter. Instead of just fixing and hoping you are testing whether the fix actually moves someone from cancelled back to paying before you commit fully to building it.

What kind of experiments have you seen work best at early stage for something like this?

You’re thinking about this at the right time. A lot of founders only notice churn after they’ve already lost users. One thing that helps early on is not just catching feedback when someone cancels but also checking in during onboarding so you can fix issues before they even get to that point.

Honestly the best time to set this up is before you think you need it. Most founders add it after churn becomes a problem. By then you have already lost months of signal.

One thing that will save you early on. Do not wait for patterns. Read every single cancel conversation yourself in the beginning. Not a summary. Not tags. The actual words people use. That is where the real product insight lives and at your stage every cancelled user is telling you something your paying users are too polite to say.

Good luck with the launch.