How I finally fixed the “feedback chaos” problem in my product (case study)
As a founder, the biggest silent killer for me wasn’t traffic or growth — it was unclear, scattered user feedback.
Feedback came in through:
random Slack DMs
emails I forgot to answer
comments inside Notion docs
screenshots people dropped in Discord
Result: I couldn’t see patterns, sentiment, or what actually mattered.
So I built a small internal tool just to fix my own workflow — a drop-in feedback component that sends every piece of feedback to one selected Slack channel, with mood + summary so I don’t miss what’s important.
Unexpectedly, a few engineers at PwC, Vercel, Supabase, and some indie teams started using it too, because they had the same problem:
“Users are giving feedback — we just don’t capture it cleanly.”
What ended up working well:
A component users can open anywhere inside the product
All feedback goes into one Slack channel per project
AI adds emotional tone + a short summary
Custom fields/themes so teams fit it into their UI
Zero dashboard babysitting — Slack becomes the hub
This wasn’t meant to be a product initially, but it solved the chaos for us and later for others.
Sharing here in case anyone else struggles with “feedback is coming in, but it’s all over the place” — happy to answer how teams are using it or what patterns are emerging.
If anyone else is dealing with scattered or missing user feedback, here’s the tool I built:
👉 https://retour.tech
Replies