How to Validate Product-Market Fit Before Launching

Every founder knows the statistic-shaped fear: most products die not because they were built badly, but because nobody wanted them. AI has made building almost free — which means the graveyard is filling faster, and the thing that kills you has moved. It's no longer “can I build this?” It's “does anyone have this problem badly enough to pay?” — and most of us answer that question by asking friends, posting a poll, and hearing the polite yes that means nothing.

There's a better source of truth, and it's free to check: people already describe their problems in public, every day, on Reddit. Not in response to your survey — unprompted, in their own words, with their frustration intact. Before you launch, before you even finish building, you can find out whether anyone is actually talking about the problem you're solving. This post is a practical method for doing that.

Why Reddit is the honest dataset

Validation advice usually starts with “do customer interviews,” and interviews are great — but they're slow, your sample is whoever answers your DMs, and people are kind to your face. Reddit inverts all three: it's instant, the sample is everyone with the problem, and nobody is being polite. When someone writes “our status page said everything was fine while the app was down for twenty minutes,” they're not validating your idea. They're just suffering, searchably. That's the signal survey data can't fake: unprompted problem talk is evidence; poll answers are courtesy.

The method: hunt for the problem, not the product

The classic mistake is searching Reddit for your product category (“uptime monitoring tool”) and concluding from silence that there's no market. But people with problems don't search in categories — they complain in symptoms. Do it in this order instead:

• Write down the problem in your customer's words. Not “lack of observability” — “I found out my site was down from an angry customer email.” If you can't phrase the problem the way a stranger would complain about it, that itself is a finding.
• Find where those people gather. Two or three obvious subreddits, plus the non-obvious ones — the adjacent communities where your buyer hangs out for other reasons.
• Count problem-talk over a fixed window. How many threads in the last few days describe the pain — not mention the category, but describe the pain? Zero is a red flag. A steady trickle is a market.
• Grade what you find. Severity: is it costing money, sleep, customers? Intent: is anyone asking “what should I use?” Workarounds: are people duct-taping spreadsheets? Paying for a bad option? Existing spend is the strongest pre-launch signal there is.

Using the reddit-lead-finder skill as the validation instrument

You can run all of the above by hand, and pre-product, you should try — an hour of manual reading builds intuition no dashboard replaces. But the search itself is exactly what ThreadSnoop's free reddit-lead-finder skill automates — install it once, then run the whole experiment from inside Claude:

npx skills add threadsnoop/reddit-skills --skill reddit-lead-finder -a claude-code -g

• Give it your URL — or describe the product you're planning to build. It drafts the problem statements and searches by both category vocabulary (how a seller would describe it) and pain vocabulary (how someone actually living with the problem complains about it) — category terms alone systematically miss most real threads, so it runs both.
• It shows you real threads on the spot, each with the exact quoted line that justified the match.
• Every match is scored on customer fit, problem severity, and purchase intent — the same three dimensions you'd grade by hand. Run it again in a few days: a steady trickle of new severe, high-intent threads is a live census of your problem — how often it comes up, how much it hurts, whether anyone's ready to pay.

A validation signal looks like this — a real, scored Reddit post from a real (anonymized) product's search. Notice the 95% problem severity: that's the number a pre-launch founder is actually validating.

(This particular example predates the skill and was found by ThreadSnoop's broader matching pipeline, which is why it's tagged “semantic” — the skill itself finds threads like it through varied-vocabulary search over the same real archive, not embedding similarity. Same rubric, same real data, different search mechanism.)

The readout is refreshingly binary. If a week or two of re-running it against the right communities surfaces a handful of scored threads at best, you've learned — for free, before writing more code — that the problem-talk isn't there, and you can pivot the framing or the idea. If every run keeps turning up people in pain, you haven't just validated the market: you're holding a list of your first customers, each one a real person you can reply to, today, as yourself.

Launch with a market, not at one

The founders who skip validation launch at a market — a Product Hunt post, a tweet, and silence. The ones who validate on real problem-talk launch with one: they've been in the threads for weeks, the early users recognize their name, and the first paying customer is often someone they already helped. Distribution stops being a launch-day gamble and becomes the byproduct of the validation itself.

Frequently asked questions