What I learned after routing all user feedback directly into Slack

I want to be transparent — this is about something I built — but sharing mainly because the problem might resonate.

As a founder, my biggest blind spot wasn’t features or growth.
It was feedback fragmentation.

Users were sharing thoughts everywhere:
emails, DMs, support chats, random calls — and most of it never made it into actual product decisions.

I noticed something interesting while working with teams at companies like PwC, Vercel, Supabase, and a few indie startups:
they didn’t need more dashboards — they needed feedback to land where work already happens.

So I experimented with a simple idea:
→ route user feedback straight into a selected Slack channel
→ add light structure (context, mood, summary)
→ remove the friction of “checking feedback later”

That experiment became Retour.

Not posting this as a pitch — more as a case study in:

• reducing feedback loss

• shortening feedback → action loops

• keeping founders closer to real user sentiment

I’m curious:
How do you make sure important feedback doesn’t get lost before it reaches your team?

If useful, happy to share what worked, what didn’t, and what surprised me while building this.

🔗 https://retour.tech