What Is the Best Way to Get Early Feedback on Your SaaS?
Most early feedback is noise. The founders who built the right product got signal through specific methods — here is what actually worked.
The best way to get early feedback on your SaaS is to put it in front of the people who have the problem you are solving — and then ask about their problem, not about your solution. Most early feedback is low-quality because founders ask "what do you think of my product?" instead of "walk me through how you currently handle this."
User interviews before you build
The highest-value feedback happens before you write a line of code. A 30-minute conversation with someone who has the problem you are solving tells you more than 100 survey responses. Use the Jobs to Be Done framework: ask what they are trying to accomplish, what they currently use, what frustrates them about it, and what they have already tried. Do not pitch your solution. Listen.
Aim for 5–10 interviews with people who match your target customer profile. By the fifth conversation, you will start hearing the same phrases. Those repeated phrases are your product copy and your positioning — use them verbatim.
Closed beta with limited seats
A closed beta with a waiting list creates scarcity, which filters for people who genuinely want the solution. Fifty users who asked to be let in provide better signal than five hundred who signed up because entry was frictionless. Give each beta user a specific task to complete — not "explore the product," but "try to do X with the product and tell me where you got stuck." Concrete tasks produce concrete feedback.
Loom walkthroughs for asynchronous feedback
Record a short Loom walkthrough of a specific workflow and send it to five potential users with the question: "Does this solve the problem you have? What would make you switch to this from what you currently use?" Loom removes the scheduling friction of live calls and gives you a shareable artefact. The responses you get reveal whether your explanation of the value lands — which is often a different problem from whether the product itself works.
In-product feedback during beta
Once users are inside the product, a simple in-app prompt — "Was this useful? Yes / No" — after key actions gives you quantitative signal about which parts of the product are working. Combine this with a short open text field: "What would make this better?" The combination of thumbs up/down data and open text is more actionable than either alone.
The difference between feedback that builds features and feedback that reveals problems
Feature requests are opinions. Problem descriptions are facts. When a user says "I wish this had a calendar view," they are giving you a feature request. When they say "I keep losing track of which tasks are due this week," they are describing a problem. Only act on the problem — the calendar view might be the right solution, or it might not be. Build for the problem, not the request.
Founders who build directly from feature requests end up with products that satisfy the individual users who asked, but not the broader market they are trying to reach. The product becomes a custom solution for five loud users instead of a scalable tool for five hundred quiet ones.
Fake door tests for unbuilt features
A fake door test is a button or link to a feature that does not yet exist. When a user clicks it, they see a message: "This feature is coming soon — want to be notified?" The click-through rate tells you how much demand exists before you invest in building. This works best for discrete features with clear entry points, not for core product workflows.
The users most likely to give you honest, actionable feedback are the ones who found you intentionally. Launchstag is a weekly indie product directory where every listing is a permanent indexed page with a dofollow badge — founders who discover you through a curated directory are already interested in indie tools and more likely to engage with early-access invitations. tools.cafe is a curated tool directory with a badge-for-backlink model that attracts builders who evaluate tools seriously and give considered feedback. LaunchBuff is a fortnightly bracket competition with 16 products across 4 rounds over 14 days — users who voted for your product in a bracket are self-selected advocates whose early feedback reflects genuine enthusiasm rather than polite indifference.
Ready to get your product discovered?
Submit to Launchstag — free, permanent listing, indexed by search engines and AI assistants.
Submit your product