
Reactions
Get early design feedback from users within your product
Scheduling user interviews is frustrating for everyone involved, and I've been on both sides of it.
I've emailed users a Calendly link and then sat alone on a Zoom call after a no-show. I've also been the user on the other end, stopping what I was doing to find a slot on someone else's calendar just to give a few minutes of feedback. The whole thing feels heavy for something that should be simple.
Meanwhile, I kept watching good prototypes die in a Figma file because "we didn't have time to run a study." Nobody schedules a formal interview for a 3-day feature, so those features just ship on a hunch or die without feedback.
The realization that stuck with me: most users are already inside your product. That's where feedback should happen too.
So my hypothesis was that async, in-context reactions on early designs (Figma prototypes, Loom videos, mockups) could fill that gap. Cheaper than interviews, faster than a survey, and closer to the real thing than either. I built a tool around it (https://getreactions.app) and have been dogfooding it on itself. Users explore early concepts right inside the app and leave feedback on their own time. No scheduling, no Zoom, no forcing anyone to switch contexts.
Happy to get into the go-to-market or the build in the comments. Mostly, though — if you do pre-build validation differently, I want to hear it, because I'm still figuring this out. How is your team handling early-stage design feedback today?
About
Scheduling user interviews is difficult. Most users are already inside your product. Reactions can surface early designs within your app so users can explore concepts and leave feedback in context, on their own time.

10 Comments
The “3-day feature” example is still the bit that sticks with me. Nobody wants to schedule a meeting for something that might not even exist next week. Reactions feels like it could be pulling in a lot more organic traffic than it probably is right now, especially while you’re still figuring out what teams will actually change their process for. Have you found one type of team that gets this immediately?
Getting more traffic is the difficult part. While Reactions focuses on Product Teams, I'm definitely learning what they need and how to engage them.
You mentioned that getting more traffic is the difficult part, and since Reactions is specifically focused on Product Teams, I’d look at targeted media placements alongside your current distribution efforts.
Getting featured in relevant product/design/startup publications could put Reactions in front of more of the right teams, which means more opportunities to learn how they actually engage with the product. Beyond the initial traffic, those placements can also build authority, brand awareness and a “Featured In” footprint you can keep using as you grow.
I work on this side and have some ideas that could fit Reactions specifically. If you’re interested, feel free to reach out at mumar@growwithmumar.online and I can share them.
Thank you, targeted ads is definitely my next step.
That makes sense. I’d probably test paid acquisition against a few very specific Product Team use cases rather than the broader “product feedback” category, then use whatever messaging gets traction to guide the organic side too.
For Reactions, I’d still keep targeted editorial placements in the mix alongside that. If you find a use case that converts well through ads, getting the product covered around that exact problem can give you another acquisition channel without relying entirely on paid traffic. Happy to share a few angles I’d test for Reactions if useful.
The contrast between a scheduled interview and feedback inside the product is easy to relate to. Curious what teams actually find easiest to get people to respond to.
I'm very interested in this as well. I know getting feedback easily/quickly is a problem. I experience it every day.
Yeah, that seems to be a surprisingly persistent problem. Curious what part of getting feedback slows you down most?
Reaching out to actual users and scheduling time with them. This is by far the most difficult task.
That’s a useful distinction. If reaching users and getting time with them is the main bottleneck, I’d be interested in continuing the conversation beyond the thread. What’s the best email to reach you at?