While building products, I noticed feedback was everywhere Slack, DMs, screenshots, random messages and nowhere useful.

I built Retour to fix that for myself:
a drop-in feedback component that routes feedback into selected Slack channels, with AI summaries to reduce noise.

Teams at PwC, Vercel, Supabase, and indie startups use it today mostly because it removes friction, not because it s fancy.

Sharing in case this problem resonates.
Happy to answer questions or hear how others handle feedback.

There s one thing we re really good at as builders:
we constantly try to improve our work and our product every single day. But an honest question I often ask myself is: do we put the same effort into updating ourselves?

At Murror, we re a small team of around five people.
For me, it s important not only to improve the product, but to continuously update my mindset, skills, and learnings and share them openly with the team.

I try to communicate everything I learn, ask questions, and clarify problems as much as possible, so the product we re building becomes better, clearer, and more convincing for our users.

To do that, I try to practice a few things consistently: