Where SaaS founders can get useful product feedback
Choose a SaaS founder or user community for problem, usability, technical, pricing, beta, or launch feedback—and ask without spamming.
Direct answer
The short version
Choose the feedback community by the evidence you need. Use a target-user community for problem language, Buildside or a defined beta group for observed product use, DEV or Hacker News for technical scrutiny, Indie Hackers or MicroConf Connect for founder operating decisions, and Product Hunt for launch reactions. Ask one bounded question and report what changed afterward.[1][2][3][4][5][6][7]
Compare every build-in-public platformFeedback routing matrix
Match the question to people qualified to answer it
A founder can receive thoughtful replies and still learn the wrong thing if the respondents never perform, buy, evaluate, or operate the workflow in question.
| Evidence needed | Best-fit setting | Ask | Do not infer |
|---|---|---|---|
| Problem language[1][8][9] | The niche Reddit or professional community where users discuss the job | What is difficult, how it is handled now, and what triggers a change | That interest in a discussion equals demand for your solution |
| Observed usability[2] | A defined Buildside beta request or recruited user group | Complete one realistic task while you observe where the person hesitates | That a signup or supportive comment equals activation |
| Technical scrutiny[3][4] | DEV, Show HN, or a technically relevant community | Challenge the architecture, limitation, benchmark method, or developer experience | That technical approval proves market fit |
| Founder operating decision[5][10][6] | Indie Hackers, Buildside, or MicroConf Connect | Compare a concrete pricing, channel, hiring, or execution tradeoff | That another founder represents the customer |
| Launch reaction[7][11] | Product Hunt or another ready-to-try launch surface | What is unclear, which use case resonates, and what blocks trying it | That launch-day engagement predicts retention |
Swipe the comparison sideways to see every column.
A reusable request
Write a feedback request that can produce a decision
Context
Name the exact role, workflow, product stage, and decision under consideration.
Evidence shown
Include the screenshot, prototype, sequence, result, or tradeoff the reader needs to inspect.
One bounded question
Ask what is unclear, what would block the task, which assumption is wrong, or how the person handles the job today.
Commitment
State what participation requires and what the person receives in return, especially for beta use.
Follow-through
Return with what changed, what did not, and why. This turns extraction into community memory.
Community fit
A useful request must survive without the promotional link
Read the local rules, observe accepted posts, and write the problem or evidence so the community can learn even if nobody clicks. Reddit explicitly gives communities control over post formats and moderation, while Hacker News asks submitters not to use the site primarily for promotion or solicitation. Those are product constraints, not distribution obstacles to work around.[1][8][12]
After the replies
Code feedback before changing the roadmap
- Record the respondent's role and relationship to the workflow.
- Separate observed behavior, stated behavior, preference, objection, and feature request.
- Mark repeated evidence without treating volume as representativeness.
- Capture the decision the evidence supports and the evidence that would reverse it.
- Report the change back to the community without exposing private participant information.
Methodology and disclosure
How this guide was made
The matrix separates feedback types because opinions about a problem, observed usability, technical review, founder advice, and launch reactions are not interchangeable evidence. Platform facts come from official community and publishing rules.
Buildside publishes this guide and appears where it fits the stated job. Platform facts come from linked official sources; recommendations and workflows are Buildside's editorial assessment.
Official sources checked . Features, access, and policies can change.
Official and first-party sources
- [1] Reddit community settings
Community types, post formats, title and body requirements, link restrictions, and moderation controls.
- [2] Buildside Beta Lab
Explicit public opportunities from SaaS founders looking for beta testers.
- [3] About DEV
Developer-community purpose, collaborative learning, and Forem foundation.
- [4] Show HN guidelines
Eligibility, product readiness, trial friction, launch scope, voting rules, and comment expectations.
- [5] Indie Hackers
Current posts, case studies, Build Board, products, jobs, Partner Up, and meetups.
- [6] MicroConf Connect
Audience, vetting, discussion channels, expert sessions, content vault, directory, pricing, application, and refunds.
- [7] How Product Hunt works
Audience, launch eligibility, free access, launch goals, and leaderboard factors.
- [8] Reddiquette
Reading local rules, choosing the right community, factual titles, vote behavior, and the 9:1 guidance.
- [9] Post and share updates on LinkedIn
Post length, audiences, comment controls, formats, events, polls, documents, and scheduling.
- [10] Public founder updates
Public, source-level founder progress, experiments, lessons, launches, and requests.
- [11] How to post a product
Personal-account requirement, launch fields, media, makers, first comments, and scheduling.
- [12] Hacker News guidelines
Submission quality, limits on promotion and solicitation, original sources, and discussion conduct.
FAQ
Questions founders ask next
What is the best community for SaaS feedback?
There is no single best community. Target-user communities are strongest for problem evidence, structured beta groups for observed use, technical communities for implementation scrutiny, and experienced founder communities for operating tradeoffs.
How do I ask for feedback without self-promoting?
Make the post useful without the link: provide context and inspectable evidence, ask one bounded question, disclose your relationship to the product, follow local rules, and return with what changed.
How much feedback is enough to change the product?
Count evidence quality before reply count. Repeated observed friction from relevant users is stronger than many general preferences. Define in advance what evidence would change the decision.
Continue the decision
Related build-in-public guides
SaaS founder social network
Which SaaS founder social network should you join?
Choose a SaaS founder network by the relationship you need. Buildside fits public founder-and-product continuity; Indie Hackers fits bootstrapped peer discussion; LinkedIn fits professional reach; Reddit fits problem-specific communities; MicroConf Connect fits private SaaS advice; and Startup Grind fits events and local networking. Join one primary network before adding another distribution channel.
Building a SaaS in public
How to build a SaaS in public without turning it into a performance
Build a SaaS in public by documenting specific decisions, evidence, progress, and lessons where relevant people can respond. Keep one durable product history, distribute selected lessons in an audience-native channel, and close the loop by explaining what changed. Protect customer, security, commercial, and personal information, and measure useful conversations and product actions separately from public engagement.
Where to build in public
Where should a SaaS founder build in public?
Build in public in three layers: keep a durable home for the founder and product, choose one reach channel where the intended user already participates, and add a launch platform only when there is something ready to try. For many SaaS founders that means Buildside plus LinkedIn or X, followed later by Product Hunt, Hacker News, or a relevant directory.
Inspect the relevant platforms
Keep the public journey connected
Give useful progress a durable home.
Create a founder profile, connect your SaaS product, publish the evidence behind the work, and make the next useful action clear.
Join Buildside