How to Validate a SaaS Idea on Reddit

Most idea validation fails quietly, not because nobody did it, but because of who got asked. Friends, former colleagues, and people in your own network are structurally biased toward encouragement, not honesty, and a survey you distribute yourself mostly reaches people already inclined to be nice to you. The validation that actually predicts whether something will sell is the kind where the person answering has no idea who you are and nothing to gain from being kind.

Reddit is one of the few places that reliably produces that kind of honest reaction, pseudonymous, no relationship to protect, and a culture that actively rewards calling out a bad idea rather than softening it. Here's how to actually use that before you spend weeks building something nobody asked for.

Why Reddit validation beats a survey or a friends-and-family round

• No incentive to be kind. A stranger on Reddit has nothing invested in your feelings and no social cost to telling you an idea won't work. That's uncomfortable and also exactly the signal you need before building, not after.
• The problem has to already exist, unprompted. The strongest validation isn't someone reacting positively to your pitch, it's finding people already complaining about the problem before you ever mention a solution. That's a fundamentally stronger signal than any reaction to a pitch, since nobody asked them to complain.
• You see the actual words people use. A survey answer is shaped by the question you asked. A Reddit complaint is shaped by nothing but the person's own frustration, which gives you real language for positioning later, not just a yes or no.

Two different validation methods, and when to use each

1. Passive: search for the problem before you mention a solution

Search your target problem, not your product category, across Reddit. "I hate doing X," "is there a tool that does X," "anyone else struggle with X" style phrases. Look for:

• Recurrence. One person complaining once is an anecdote. The same complaint surfacing across multiple threads, multiple subreddits, and multiple people over time is a real pattern.
• Specificity. Vague dissatisfaction ("this is annoying") validates less than a specific, detailed complaint ("I spend 2 hours every Monday manually doing X because every tool I've tried does Y instead"). Specific complaints point at a real, describable gap.
• Workaround behavior. People building their own janky spreadsheet or duct-tape process to solve the problem is one of the strongest validation signals there is, since it shows willingness to spend real effort solving it themselves.

This method validates a problem, not your specific solution, and it's the stage to do before you've committed to any particular implementation.

2. Active: ask directly, carefully

Once you have a specific solution in mind, a direct post asking for feedback can work, but it has to be framed as a genuine question, not a pitch. "I'm considering building X to solve Y, is this something you'd actually use, and what would make you skip it" invites honest pushback. "Check out my new tool" invites silence or a report for self-promotion, depending on the subreddit's rules.

Check self-promotion and feedback-request rules before posting this kind of question, since many founder-adjacent subreddits have specific threads or days set aside for exactly this. See how to find leads on Reddit without getting banned for the subreddit-rules table and account-readiness basics before posting anything like this.

What counts as real validation, and what doesn't

• Real: multiple independent people describing the same specific problem, unprompted, across different threads and time periods.
• Real: people asking "does anything already do this" in a thread you found by searching the problem, not your product name.
• Not real: upvotes on a post announcing your idea. Upvotes measure how interesting the idea sounds for thirty seconds, not whether anyone would pay for it or change their workflow to use it.
• Not real: "I'd use that" comments on a direct pitch post. Saying so costs nothing and commits to nothing. Willingness to actually try something, covered next, is a much stronger signal.

The strongest signal: get someone to actually try something

Verbal interest is cheap. The best validation available before building anything substantial is getting someone who complained about the problem to agree to look at a mockup, join a waitlist with their real email, or try a rough prototype. A DM follow-up to someone who posted a genuine complaint, offering to show them what you're building in exchange for honest feedback, converts validation from opinion into behavior.

What to do once you have real signal

Keep a running list of the specific phrases people used to describe the problem, the subreddits where it surfaces most, and the workarounds they're currently using. This becomes the raw material for your actual positioning and copy later, and it's also exactly the groundwork you'll need once you're ready to find your first users, not just validate the idea. See how to market a vibe-coded product and why building is easy and selling is hard for what comes after validation, once you've actually built the thing.

A caution worth repeating

Reddit's audience skews toward a specific demographic and toward people comfortable complaining pseudonymously. Treat a pattern found here as a strong, free hypothesis, not statistical proof your whole market wants this. It's the cheapest and most honest validation available before you've built anything, but it's still a hypothesis worth a few direct conversations before you commit months to building around it.

Finding the threads where your exact problem keeps coming up, across however many subreddits it lives in, is tedious to do by hand every day. ThreadyGo monitors Reddit continuously for conversations matching what you're building and surfaces the ones worth reading, so validation doesn't stop the day you finish your first manual search. Try it for $9 and point it at the problem you're considering solving.