r/indiehackers
Get Product Feedback

Get Product Feedback from the r/indiehackers Community

r/indiehackers is uniquely valuable for product feedback because members are builders themselves. They'll critique your product like they'd critique their own - honestly, constructively, and with practical suggestions.

Signs of Success

You'll know this approach is working when you see:

  • Getting feedback from people who've built similar products
  • Identifying blind spots in your product thinking
  • Finding potential customers through feedback conversations
  • Building relationships with experienced founders who can advise long-term

Community-Specific Approach

How to tackle this problem specifically in r/indiehackers.

1

Ask for specific feedback types

r/indiehackers members give better feedback when you narrow the scope. "Is this landing page clear?" beats "what do you think?"

Example

Instead of "feedback please", ask "Does this value prop make you want to try it?"

2

Provide context about your stage

The community calibrates feedback to your stage. Pre-launch advice differs from post-PMF optimization.

3

Show your thinking, not just your product

Explain why you made certain choices. r/indiehackers loves discussing the reasoning behind decisions.

Example

"I chose this pricing because X - is that the right approach?" sparks discussion.

4

Engage with every response

The community notices when you thoughtfully respond to feedback. It encourages more detailed responses.

5

Share what you changed

Post follow-ups showing how feedback improved your product. This builds your reputation as someone who listens.

Post Strategies That Work

Real post formats that resonate in r/indiehackers for this specific goal.

Specific feedback request

"Building [product] for [audience]. Stuck on [specific decision]. Here's option A vs B - which would you choose and why?"

Concrete choices are easier to respond to. Gets opinionated answers instead of generic advice.

Landing page roast request

"Roast my landing page: [URL]. Built for [audience] solving [problem]. What made you leave or stay?"

r/indiehackers enjoys constructive roasts. Being open to criticism invites honest feedback.

Pricing feedback

"Pricing dilemma: [option A] vs [option B]. Target customers are [description]. What would you pay?"

Pricing is a common challenge. Many members have tested various models and share experiences.

Avoid These Mistakes

Common pitfalls when tackling this problem in r/indiehackers.

Defending every piece of feedback

r/indiehackers members stop giving feedback if you argue with everything. They'll just move on.

Better approach

Thank people for feedback, even if you disagree. Ask clarifying questions instead of defending.

Posting without community history

The community can see your post history. Zero engagement elsewhere signals you're just here to extract value.

Better approach

Engage with others' feedback requests before posting your own. Build goodwill first.

Asking for feedback but really wanting validation

Indie hackers are perceptive. If you only engage with positive comments, they'll notice.

Better approach

Genuinely seek criticism. Ask "What would make you NOT use this?" to surface real concerns.

Frequently Asked Questions

Common questions about get product feedback on r/indiehackers.

Members are product builders themselves. They think about products professionally and give feedback like they would on their own work - practical, specific, and action-oriented.

Automate Your r/indiehackers Strategy

Ready to get product feedback on r/indiehackers?

Reddit Radar monitors r/indiehackers 24/7, finding the perfect opportunities to engage and helping you craft authentic responses.