Aditya Raj

We recently launched Retour, a feedback widget designed for founders and product teams who want clarity—not clutter. What makes it different: Clean embeddable widget Central feedback dashboard AI-powered summaries for faster decisions Easy routing to team channels Would love honest feedback from the PH community—especially what you’d improve or remove. Happy to answer questions or share...

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...

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...

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...

This started as a personal fix. 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. Sharing here mainly to learn: How others...

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.

Link: https://www.retour.tech When you’re building fast, feedback doesn’t disappear — it just gets scattered. Some users DM on Twitter. Some drop notes in Slack. Some never bother because it’s “too much effort”. I hit that wall hard while building my own product. I wasn’t lacking feedback — I was lacking signal. That’s why I built Retour: a simple feedback component that lets users share...

Hey everyone — I’m Aditya. 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...

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...

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...

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...

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...

Retour The hardest part wasn’t building — it was knowing what users actually felt Post As a builder, I underestimated how messy user feedback gets once real people start using your product. Not because users don’t care — but because feedback shows up everywhere: Slack DMs Random emails One-off messages after meetings “By the way…” comments that never get written down The real problem for me...

Hey everyone 👋 I’m Aditya, a solo founder who’s spent way too much time building features before realizing feedback was the real bottleneck. Lately I’ve been focused on understanding: why feedback gets ignored why founders think they’re listening (but aren’t) and what actually helps teams act faster Looking forward to learning from this community. :- check outretour :- retour

I kept missing important user signals because they were scattered everywhere. So I built Retour — mainly to solve my own problem. The idea was simple: feedback should arrive where teams already live (Slack), not in yet another dashboard. Teams from places like PwC, Vercel, Supabase, and indie startups now use it in different ways — which has been interesting to watch. Not here to pitch. Happy...

👉Retour 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...