Growth & Pricing

How to Validate a Product Idea on Reddit

Use Reddit to test whether anyone wants your product before you build it — where to look, what to ask, and which signals actually mean something.

Reddit is the best free validation tool a founder has, because it’s full of people describing problems in their own words with nothing to sell. But most “validation” done there is worthless — a founder posts their idea, gets fifteen upvotes and four “sounds cool” comments, and starts building. Upvotes are not demand. Here’s how to get a signal that means something.

Start by reading, not asking

Before you post anything, spend a few hours searching for how people already talk about your problem. This is the highest-value hour of the whole process, and it requires no participation at all.

  • Search the problem, not your solution. Not “affiliate software” but “how do I track who referred a customer.” People describe pain long before they know a category exists.
  • Use Google with a site filtersite:reddit.com "your problem phrase" — since it often beats Reddit’s own search and surfaces threads that rank publicly.
  • Sort by top, past year, and read the comments rather than the posts. The comments are where people say what they actually tried and why it didn’t work.

What you’re looking for: evidence people are already spending money or effort on this. Someone describing a horrible manual workaround is a stronger signal than a hundred people saying an idea sounds neat. Effort already spent is the closest thing to a purchase intent you’ll find for free.

If you can’t find anyone discussing the problem, that’s information too — either your buyers aren’t on Reddit (here’s how to find the ones who are), or the problem is less painful than you think.

Don’t post your idea. Post about the problem.

The classic mistake is a post that says “I’m building X, would you use it?” It produces polite, useless answers. People are agreeable to strangers, and nobody knows what they’d do hypothetically.

Better formats, in rough order of signal quality:

1. Ask how they solve it now. “How are you all handling [problem] right now?” You get the current workarounds, the tools they’ve tried, and what annoys them. Highest signal per unit effort, and completely non-promotional.

2. Share your own experience with the problem. “I’ve been doing [workaround] for six months and it’s driving me insane — is everyone else just living with this?” This invites people to agree with a complaint, which is much easier and more honest than evaluating a hypothetical.

3. Publish research and let the reaction validate it. Analyze the existing options and post what you found. If the problem is real, the comments will fill with people arguing about the details — which is exactly the audience you want.

4. Ask what they’d pay to fix. Only works when you’re already deep in the thread and the person has described real pain. Never as an opening.

Note what these have in common: none of them ask for approval. They all extract information the person already has.

The signals that actually mean something

Ranked by how much you should trust them:

  • Someone asks you for the thing before it exists. “Do you have a link / can I try it / message me when it’s ready.” The gold standard.
  • Someone describes a costly workaround. Time or money already committed to a bad solution is the strongest proxy for willingness to pay.
  • Long, specific comments. People only write four paragraphs about things they care about. One detailed reply beats fifty upvotes.
  • Arguments in the comments about the right approach. Contested means it matters.
  • People correcting your understanding. Free consulting from people who live the problem.

The signals that mean nothing

  • Upvotes. They measure whether a post was well-written and well-timed, not whether anyone would buy.
  • “Great idea, I’d definitely use this.” The most common comment on validation posts, and the least predictive. Nothing was risked to say it.
  • Founders being encouraging. Builder subreddits are supportive by culture. That’s lovely and it isn’t market research.
  • Your own excitement after a good thread. The most dangerous signal of all.

Turn the signal into commitment

Interest is cheap. The point of validation is to find the smallest thing someone will commit to, and ask for it:

  • A waitlist signup — small, but it’s an action rather than an opinion.
  • A call. “Would you spend 15 minutes telling me how you do this?” Someone who gives you time will probably give you money.
  • Pre-payment or a design-partner commitment. The strongest signal available. If nobody will pre-pay, the problem may be real but not urgent — worth knowing before you spend six months.

Every step up that ladder costs the other person something, which is precisely why it means more.

What to do with a negative result

The whole point is that a “no” is cheap here and expensive later. If your searches turn up nobody discussing the problem, and your questions get thin answers, and nobody will take a call — that’s a successful validation, and it saved you a year. The most expensive SaaS development mistakes nearly all start with skipping this step.

Also worth separating: an idea can fail validation because it’s wrong, or because you’re asking the wrong people. Before concluding, check that you looked in the right communities and that you have a clear picture of who the buyer is (customer persona).

Don’t burn the community you’ll need later

One practical warning: the subreddits you validate in are the same ones you’ll want to launch in, and Reddit has a long memory. Follow each sub’s rules, disclose that you’re building something whenever it comes up, and don’t run the same “market research” post across ten communities. The credibility you build during validation is an asset — see the Reddit organic playbook for how to keep it.

And keep track of the people who gave you good answers. They’re your first users, your first interviews, and often your first affiliates once you have something to sell.

FAQ

Is Reddit good for validating a startup idea?

Yes, for finding out whether a problem is real and how people currently solve it. It’s poor for predicting whether they’ll pay — for that you need a commitment like a call, a waitlist signup, or a pre-payment.

Should I post my idea on Reddit before building?

Ask about the problem rather than pitching the idea. “How do you handle this today?” produces far more useful answers than “would you use this?”, which invites polite agreement.

How many responses do I need to validate an idea?

There’s no threshold. Five detailed replies describing a costly workaround tell you more than two hundred upvotes. Judge by depth and by whether anyone will commit to something, not by volume.

More validation and growth guidance is in the growth & pricing hub.

validationredditproductsaas
Share