I've been pondering how feedback is typically collected in early-stage SaaS and indie projects. From my experience, it's often done through links to external tools, Google Forms, email threads, or feature request boards outside the product. The downside I've noticed is that the more effort it takes for users to give feedback, the less valuable it tends to be. Users don't want to leave the app, create additional accounts, or explain issues multiple times.
I'm curious if anyone has successfully embedded a simple feedback system directly within their app. I'm thinking about something minimal, like:
- A small form for users to leave suggestions directly
- A feature for other users to upvote existing feedback
- No additional logins or redirections required
From a development perspective, I'd love to hear what others think:
- Would you rather build this feedback system yourself or use a ready-made solution?
- How crucial is it for you to own the feedback data compared to how easy it is to set up?
- Do you find voting on feedback helps prioritize features, or do you lean more on direct messages?
I'm not trying to promote a product; I'm genuinely interested in hearing from indie hackers and small SaaS founders who might not have dedicated product teams yet. I'd appreciate any real experiences on what has worked or not worked in your feedback-gathering efforts.
6 Answers
I've been using PostHog. It started as an analytics tool, but it includes a feedback form that doesn't require users to log in, which is great. You can control how users access it based on their app navigation, but be warned—it contains a lot of data that might be overwhelming for some!
In my experience, users usually struggle to articulate what they need. They might tell you their thoughts, but actions speak louder. Observing user behavior is key. That's where tools like Sentry or DataDog can help, but just collecting feedback through forms should come second. Focus on seeing how users interact with your app instead of chasing ideas from them that don't align with your goals.
Low-friction feedback is always the way to go! The more straightforward the process, the more genuine and actionable the feedback you'll receive. While voting can highlight trends, user comments are invaluable, especially when they're prompted after a frustrating experience!
Have you found effective ways to ask for feedback without coming off as annoying?
I've found that any extra effort users have to do to provide feedback is a huge turnoff. I implemented a simple feedback widget on key pages which is completely anonymous and requires just one click to start typing suggestions or issues. Something like a GitHub project for it could work well too, or you could build your own.
Totally agree! It sounds like you've segmented users perfectly, targeting those willing to give feedback.
1. Personally, I'd prefer to build my feedback system from scratch.
2. Data ownership is complicated. Legal responsibilities might make you think twice about keeping it in-house, while relying on an external tool may alleviate some of that burden.
3. Votes can guide priorities, but they shouldn't be the only factor. You need to balance user requests with your project's roadmap, especially if it involves complex features that you can't simply implement.
That’s a valid point, especially about legal stuff and data ownership; many people overlook that early on. You're right that votes shouldn't drive everything—context matters!
On our last site, we added a feedback button that opened a simple input window. Users could type directly, and we also showed some FAQs for self-help. This way, we reduced friction significantly when asking for feedback!
That sounds like a fantastic way to minimize friction! Did you create that system in-house, or did you use an external service for it?
Absolutely! Forming partnerships with users, even at a small scale, can drive better feedback too.