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.
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.
Hey everyone! I m Aditya, a frontend developer and indie founder.
I m currently building Retour, a lightweight feedback widget that helps teams collect user input, summarize insights, and route feedback to the right channels without noise.
Excited to learn from this community, share experiences, and connect with fellow builders
Sharing a quick case study from my own product journey not a pitch.
While building SaaS products, feedback was always fragmented: Slack messages, emails, random screenshots, nothing actionable. So I built Retour to solve my problem first.
What changed:
Feedback goes straight into selected Slack channels
Teams discuss feedback where they already work
AI summaries help spot patterns without extra dashboards
Hey everyone, I m Aditya Founder + frontend dev. I spend most of my time building SaaS tools and obsessing over developer workflows and user feedback loops.
Big fan of learning in public and trading notes with other makers here. Looking forward to contributing and learning from this community.
Hey everyone I m Aditya Raj, a frontend developer and SaaS builder. I enjoy working with React, Next.js, and building clean, performance-focused products.
I m currently exploring ways to improve how teams collect and understand user feedback, which led me to build Retour. I joined this community to learn, share experiences, and connect with like-minded builders.
Looking forward to great discussions and learning from you all
Hi everyone I d like to share something I ve been working on called Retour.tech .
Retour is a lightweight feedback widget that helps teams collect meaningful user feedback directly from their product without disrupting performance. It focuses on clean UX, customizable forms, and noise-free feedback.
I m still improving it and would genuinely appreciate any feedback or suggestions from the community. Happy to answer questions or discuss the approach behind it
Feedback was everywhere emails, DMs, comments and nothing felt actionable. So I built Retour, a lightweight feedback component that sends everything into Slack, with AI mood detection and summaries to keep signal clear.
It s now used by engineers at PwC, Vercel, Supabase, and indie teams who care about fast loops.
Hey everyone, I m Aditya Frontend dev turned founder.
One problem I kept hitting: users did have feedback, but it never reached the right place at the right time. That gap pushed me to build tools around listening, not just shipping.
Here to learn how others handle feedback, growth, and staying close to users while scaling. Excited to be part of this community.
I ve been building products for a while and kept running into the same issue: users do give feedback, but it rarely lands where teams can act on it quickly.
Lately I ve been focused on tooling that fits into existing workflows (especially Slack-first teams).
Excited to learn from others here what s one problem you keep solving over and over in your products?
I want to share a quick lesson from something I built recently.
While working with teams (including engineers at PwC, Vercel, Supabase, and indie startups), one thing was consistent: feedback only mattered when it showed up where decisions were already happening.
So I built Retour a small drop-in feedback component that sends user feedback directly into a selected Slack channel, with AI summaries to highlight sentiment and patterns.
Not sharing this as a pitch more as a case study. It reduced response time and made feedback part of daily standups instead of a forgotten backlog.
As a founder, I kept thinking we had enough feedback. In reality, it was scattered Slack DMs, emails, Notion comments, screenshots, calls. Nothing actionable, nothing timely.
The breaking point was realizing decisions were being made without fresh user context.
I built a simple system for our own team: users share feedback it lands directly in a specific Slack channel the team reacts while context is still fresh.
Surprisingly, teams at places like Vercel, Supabase, and PwC resonated with the same problem and started using it too.
Hey everyone I m Aditya, an indie founder building SaaS products and learning everything the hard way.
One thing I keep running into as a builder is this gap between users having thoughts and teams actually seeing them. Feedback exists it s just scattered, delayed, or lost in tools people don t check daily.
Lately I ve been experimenting with simpler ways to close that gap while keeping teams focused where they already work.
Excited to learn from other makers here especially how you stay close to users without drowning in noise.
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.
Something I didn t expect as a founder: feedback doesn t disappear it fragments.
Early on, users reply to emails. Then it moves to DMs, support tickets, Slack messages, random calls. By the time you have traction, the signal is everywhere and nowhere.
The hardest part isn t collecting feedback it s not missing the important stuff when velocity increases.
Curious how others here keep feedback actionable without adding more tools or process overhead. What s worked (or failed) for you? :- introduce :- retour
