How to Validate a SaaS Idea on Reddit (Before You Build)

Most SaaS ideas die in one of two places: either they never get built because the founder keeps tweaking the concept forever, or they get built and then nobody uses them.

Both failures have the same root cause: the founder didn't find out whether the problem was real before investing months of work.

Reddit is the fastest way to find out. Here's how to do it.

What Validation Actually Means

Validation doesn't mean "I found some people who said they'd pay for this." It means finding evidence that a specific group of people has a recurring, painful problem — and that they're currently solving it with something worse.

The bar is concrete frustration, not hypothetical interest.

Step 1: Find Where Your Target Customers Gather

Start by listing 5–10 subreddits where your ideal customer already spends time. Not subreddits about your product category — subreddits about their job, their industry, or their problems.

If you're building a tool for freelancers, they're in r/freelance and r/webdev. If it's for e-commerce operators, they're in r/fulfillment and r/ecommerce. If it's for founders in general, start with r/SaaS, r/entrepreneur, and r/startups.

The product category subreddits (r/projectmanagement, r/crm) are less useful at this stage — people there are already past the pain and into evaluation mode.

Step 2: Search for the Problem, Not the Solution

Go to each subreddit and search for phrases that signal frustration or a workaround. You're looking for posts where people describe doing something manually, badly, or reluctantly.

Useful search phrases:

• "I've been manually..."
• "Is there a way to..."
• "I wish there was..."
• "Anyone else frustrated with..."
• "we use [tool] but it can't..."
• "every week I have to..."

The goal is to find posts where people describe the problem in their own words — not posts asking for tool recommendations.

Step 3: Measure Signal Strength

Not all complaints are equal. When you find a relevant thread, check three things:

Upvote count. More upvotes means more people recognized themselves in the post. A complaint with 300 upvotes is a different signal than one with 8.

Comment depth. Are people sharing their own versions of the same problem in the comments? Do replies say "same here" or describe workarounds? That's validation.

Thread age vs. frequency. A single old thread is interesting. The same complaint showing up in threads from 2022, 2023, 2024, and 2025 means the problem is persistent — nobody has solved it well.

Step 4: Look for the Workaround

The strongest validation signal isn't the complaint — it's the workaround. When people have a painful problem with no good solution, they build one out of duct tape.

Look for posts where people describe using:

• Spreadsheets to replace something that should be automated
• Multiple tools stitched together with Zapier or manual steps
• A daily or weekly routine to compensate for a missing feature
• A script or hack they built themselves

If you find a thread where 50 people are describing how they manually do the thing your SaaS would automate, that's strong validation.

Step 5: Check If Anyone Is Paying Already

Search Reddit for competitors — tools people mention when they describe their current solution. Look at how people talk about them:

• Are users happy or just tolerating them?
• Are there "alternatives to [competitor]" threads?
• Do people describe the workarounds they still need even with the existing tool?

If people are paying for an imperfect solution, that's more validation than a hundred "I'd pay for that" comments from people who haven't paid for anything.

What Weak Validation Looks Like

Be honest with yourself about the difference between real signal and wishful thinking:

• A few upvotes and generic comments — might just be a niche edge case
• Posts about wanting more features in an existing tool — that's a roadmap request for someone else, not a business opportunity
• Problems people mention once and move on — not painful enough to solve
• "Interesting idea, I'd try it" — interest is not demand

You're looking for people who are currently suffering, not people who are mildly interested.

How Long This Takes

Done manually, searching 5–10 subreddits across different time periods takes 2–4 hours to do properly. That's enough time to get a meaningful read on whether real demand exists.

If you want to track demand over time — whether the conversation is growing, what language keeps repeating, how engagement shifts — Reddiscope monitors subreddits continuously and surfaces the patterns without the manual searching. Useful when you're post-validation and building in public, or when you're watching a market and want to know when the conversation changes.

But for initial validation, the manual method above works. Do it before you build anything.