Use CasesGuidesMethodology
Idea validation

Validate your startup idea with evidence, not optimism

Pull the threads where your future customers already complain, compare tools, and ask for help — then get a ranked report of where the real pain and willingness to pay live.

The problem

Why stated interest overstates demand.

Most ideas die because they solve a problem nobody is paid to care about. Surveys flatter you, friends are polite, and "I would totally use that" never converts.

Reddit is the opposite: thousands of unfiltered threads where people describe what actually frustrates them, what they have tried, and what they would gladly pay to fix.

The catch is volume. Reading it by hand is hopeless, and a single cherry-picked thread proves nothing. You need the signal across the whole conversation.

How it works

From an idea to a demand verdict, in four steps.

01

State the claim

Write your idea as a testable hypothesis — e.g. "indie founders struggle to get their first 100 customers."

02

Pull the threads

We search the subreddits where that audience lives and gather the discussions that match, comments and all.

03

AI classifies each one

Every thread is scored for pain intensity, willingness to pay, and the workarounds people already use.

04

Read the ranked report

A single markdown report ranks the strongest demand signals so you know whether to build — or pivot.

What the report looks like

Real demand, ranked by pain and willingness to pay.

The report

Every matching thread is scored 0–100 for pain intensity and bucketed into a willingness-to-pay tier, then sorted so the strongest demand sits at the top.

SourcePain signalWTP tier
r/SaaS88high
r/startups64medium
r/Entrepreneur41low
Illustrative example

A representative run — not a measured result.

CLAIM
“Indie founders struggle to get their first 100 customers.”
Subreddits r/SaaS, r/Entrepreneur, r/startupsThreads ~250 classifiedCost ≈ $0.20Runtime ~12 min

A representative run surfaces a tight cluster of high-pain threads about cold-start distribution, with several posters naming the exact tools they already pay for to escape it.

Takeaway. Demand for a fix reads as real and acute — so the open question becomes price, not whether the pain exists.

Why it works

Validate the idea before you build.

Demand before development

Find out if the pain is real and acute enough to pay for, before you spend a month building.

Pricing signals

See where people already pay for alternatives and how they describe "worth it" versus "too expensive."

Your competitors, named

Discover which tools your future customers already reach for — and exactly where those tools let them down.

Language that converts

Capture the precise phrasing your audience uses so your landing page sounds like their own words.

Under the hood

How we score demand for an idea.

Scored, not skimmed

Each thread gets a pain_signal (0–100) and a wtp_tier of high / medium / low / none, so you rank by intensity instead of by upvotes.

What a run costs

A typical pass classifies ~250–300 threads for roughly $0.13–0.40 and finishes in 10–15 minutes.

No API-lockout risk

Threads come from Reddit’s public JSON endpoints — no OAuth, no key, and resilient to the API changes that have killed other tools.

FAQ

Questions, answered.

How is this better than a survey?

Surveys capture stated preference from people trying to be helpful. Reddit captures revealed frustration from people who had no idea you were listening — a far stronger demand signal.

What if the report shows little or no demand?

That is a finding, not a dead end. A sparse, low-pain report is early evidence the problem is not acute enough to build on yet — far cheaper to learn now than after a year of building. Reframe the claim and test an adjacent angle.

How much demand counts as validation?

Look for a tight cluster of high-pain threads where people describe the problem unprompted and name what they already pay to work around it. A handful of acute, willing-to-pay voices beats hundreds of mild, polite mentions.

Can I validate before I build anything?

Yes — that is the point. Because it reads existing public threads rather than needing a product or an audience, you can test real demand the day you have the idea, before writing a line of code.

Can I test more than one idea?

Yes. Each idea is its own claim, so you can run several in parallel and compare which has the strongest underlying demand.

Keep reading

Related playbooks.

Validate what people actually say, not what you wish they would.