FlagUp
Collect feedback, manage suggestions and get churn insights.
-
1
Really like the positioning. I agree that collecting feedback isn't the hard part anymore—knowing which signals actually matter is.
One question though: how do you differentiate FlagUp from tools like Canny, Featurebase, Productboard, or even building a simple feedback board with AI summarization?
Looking forward to seeing how you solve that problem. Good luck with the launch! 🚀
-
1
Honestly fair question. Most tools do feedback collection really well. Where FlagUp is different is that it tries to answer a question they don't, who is about to leave? That churn layer is the whole point. Thank you for pushing on it.
-
1
That makes sense. Focusing on identifying churn before it happens feels like a much clearer positioning than trying to compete on feedback collection alone. I like that you're solving a specific decision rather than trying to replace every feedback tool. Wishing you the best with FlagUp—I'll be interested to see how it evolves.
-
-
13 Comments
That reach out thing is real. One conversation saves more users than any feature ever will. Honestly for a team under 3 just do it manually. You know your users. Watch who goes quiet and send a message. Scoring models are for when you have too many users to keep track of manually.
Great insight. User feedback is more than feature requests. it's one of the earliest indicators of customer satisfaction. Acting on those signals early can make a huge difference in retention.
Exactly. Most teams read feedback looking for what to build next. The real value is knowing how your users feel right now.
This tracks with what we've seen too. FlagUp's angle is the right one — most real signal shows up as sentiment weeks before anyone cancels. Where we've focused (CancelKit) is the other end: even with good sentiment tracking, some churn only becomes legible at the literal cancel click, because almost nobody instruments that moment. Feels complementary rather than overlapping — you catch the slow leak, we catch the stated reason at the door. Curious if you've validated the sentiment score against actual outcomes yet, or if it's still mostly forward-looking? We ended up making CancelKit free — gating the actual cancel-reason data behind a plan felt backwards.
This approach makes perfect sense: we're addressing two distinct aspects of the same problem. We're still in the very early stages of validation, but that's exactly the goal I'm working toward.
I build Featurevote, so we are in the same category. Not here to pitch, just wanted to wish you luck with it.
The churn angle is a real gap. Most feedback tools do stop at collecting.
Thank you, means a lot coming from someone in the same space. Featurevote is solid work.
Great perspective! The best products are built by listening to users before they leave, not after they've gone. Early feedback, sentiment analysis, and quick action can make all the difference. Wishing you continued success! 🚀
That is exactly it. The signs are always there, most just miss them. Thank you.
The users who complain may actually be the easier ones to save.
I'd be curious about the opposite group: users whose feedback, usage, or communication simply goes quiet. If FlagUp can distinguish “satisfied and silent” from “disengaging and silent,” that feels like a much stronger churn signal than negative sentiment alone.
You are right and that is actually the harder problem to solve. Silent disengagement gives you almost nothing to work with. It is on my radar for FlagUp. Really appreciate the insight.
I appreciate you saying that. Silent disengagement is actually the part that caught my attention most.
I'd be interested in continuing the conversation by email if you're open to it. What's the best email to reach you on?