How to Validate a Product Idea Without Surveys or Interviews

Customer interviews are genuinely useful. They're also slow, hard to schedule, and easy to misread — people tell you what they think you want to hear more often than they realize.

Before you invest weeks in interview recruiting and scheduling, there's a faster first pass: finding out whether the demand already exists in public, without talking to anyone.

This doesn't replace interviews. It tells you whether the interviews are worth doing.

The Standard Advice (and Its Problems)

Most validation advice says: talk to 10 customers, run a survey, build a landing page and see if people sign up.

All of these are valid. The problem is the order. You end up spending time on outreach and landing pages before you've confirmed the basic premise: does this problem actually bother people enough to pay for a solution?

The faster question to answer first is: is there already evidence that people are struggling with this problem? If yes, then interviews and landing pages make sense. If not, you're validating a hypothesis that doesn't yet have evidence.

Where the Evidence Already Exists

Real demand leaves traces before anyone builds a product. People ask questions in forums. They describe workarounds in comment threads. They complain in community Slacks. They search for tools that don't exist yet.

The most accessible of these traces is Reddit. Here's how to read them.

Signal 1: The Workaround Post

The clearest demand signal is a post where someone describes the elaborate thing they do instead of using a proper solution.

These posts look like: "I've been manually copying data between X and Y every Monday for two years," or "Our team uses a Google Sheet to track this because nothing else does it right."

When people build workarounds, it means:

1. The problem is real enough to spend recurring time on
2. No existing solution solves it well enough
3. They've decided to live with the pain rather than keep looking

That's your market.

Signal 2: Recurring Identical Complaints

Search Reddit for your problem area and sort by Top, then All Time. Read the top 20 results. Then sort by New and read 20 more.

If the same complaint appears in both — if threads from 2020 and threads from 2025 describe the same frustration — the problem is persistent. Not a trend, not a phase: an ongoing, unsolved pain.

Persistence is important. Problems that people post about once and resolve aren't worth solving with a product. Problems that have been showing up for years haven't been solved well by anyone yet.

Signal 3: People Already Paying for Something Worse

Search for tools that partially solve the problem. Find threads where people discuss them. Are users happy with the existing solution, or are they describing its limitations in detail?

If people are paying for a tool they're not fully satisfied with, that tells you:

1. There's willingness to pay (they're already paying)
2. The problem is real enough to spend money on
3. There's a gap the current market leader hasn't filled

This is more reliable validation than any "I'd pay for that" comment. Money already changing hands is real demand.

Signal 4: The "Does This Exist?" Thread

Occasionally someone posts exactly what they want built: "Is there a tool that does X?" If that thread has high upvotes and comments saying "I've been looking for this too," you've found expressed demand at its most direct.

These threads are uncommon, but worth searching for. Try: "is there a tool that" site:reddit.com [your problem area].

What Weak Signal Looks Like

Being honest about what doesn't count:

• A few upvotes on a complaint post — could be a niche edge case, not a broad market
• "That would be cool" comments — interest is not demand
• One subreddit, one thread — not enough surface area
• Problems people mention but immediately resolve — not painful enough

You're looking for problems that people keep posting about, keep workaround-ing, and keep paying imperfect solutions to solve.

Using This as a First Pass

A few hours of Reddit research — searching across 3–5 relevant subreddits, reading threads, noting what keeps coming up — gives you a rough answer to the most important question: is there already evidence that this problem is painful?

If yes, then build the landing page and schedule the interviews. If not, you've saved weeks.

Reddiscope makes this faster by monitoring subreddits you pick and surfacing what's recurring — so instead of searching manually, you see which problems keep coming up and how engagement on those threads is trending. Useful when you're doing ongoing market research across multiple problem areas at once.

But the manual version works too. The point is to do it before you build, not after.