How to Find Real Product Demand Before You Build

Most bad product bets do not start with bad execution. They start with weak evidence.

A founder sees a few viral posts, notices people complaining online, and decides there must be a market there. Then weeks or months disappear into building, only to reveal that the “problem” was vague, low-frequency, or not painful enough for anyone to pay to solve.

The hard part is not finding conversations. It is finding the right ones.

Reddit and X are full of demand signals, but they are buried under performance, hot takes, edge cases, and one-off frustrations. If you are an indie hacker, SaaS builder, or part of a lean product team, the skill that matters is not trend spotting. It is learning how to distinguish repeated pain from ambient noise.

Start with pain, not ideas

A common mistake in early product research is beginning with a solution in search of validation.

You might think:

• “AI should make this easier.”
• “This workflow looks ripe for automation.”
• “People in this niche seem underserved.”

Sometimes that leads somewhere useful. More often, it creates confirmation bias. You start collecting evidence that supports the product you already want to build.

A stronger approach is to begin with observable pain:

• What task keeps coming up in complaints?
• What workaround do people repeatedly mention?
• What job feels important enough that users are actively trying to solve it?
• Where do people describe cost, delay, lost revenue, risk, or frustration in concrete terms?

Good product opportunities usually sound less like inspiration and more like recurring friction.

The three signals that matter most

When reviewing public conversations, three signals tend to matter more than volume alone.

1. Repeated pain points

A single complaint is not a market.

What you want is repetition across different people, contexts, and time periods. If multiple users describe a similar problem without coordinating with each other, that is more meaningful than a single popular post with hundreds of likes.

Look for patterns such as:

• the same workflow bottleneck appearing in multiple threads
• users describing similar manual workarounds
• frustration tied to a specific job, not a vague dislike
• complaints that persist over weeks or months

Repeated pain is often more valuable than loud pain.

2. Explicit buyer intent

Not every problem deserves a product. Some are annoying but tolerable. Others are painful enough that people actively seek a solution.

Buyer intent often shows up in phrases like:

• “I’d pay for…”
• “Does anyone know a tool that…”
• “I’ve tried everything and still can’t…”
• “We need a better way to…”
• “What are people using for…”

This is where many idea lists fall apart. They collect interesting complaints, but not signs that a user actually wants to buy, switch, or adopt something.

3. Weak signals worth watching

Not every opportunity is ready now. Some are early.

A weak signal might be a niche complaint that appears only occasionally, but in a category that is clearly growing. Or it may be a new workflow problem caused by changes in AI tooling, APIs, regulation, or distribution channels.

Weak signals should not drive immediate commitment on their own. But they are worth tracking, especially if you revisit them over time and see repetition increase.

A practical workflow for demand discovery

If you want a lightweight process, use this weekly workflow before you commit to building anything substantial.

Step 1: Define the job, not the feature

Instead of searching for ideas like “AI content app” or “CRM for creators,” define a job to be done:

• managing inbound leads from multiple channels
• reconciling invoices across tools
• tracking client approvals
• summarizing user feedback into priorities

This keeps your research grounded in user outcomes instead of shiny categories.

Step 2: Search where people speak plainly

Reddit and X are useful because users often describe problems in their own words. That matters.

Product pages, trend reports, and polished thought leadership usually smooth over the messy parts. Public conversations reveal the exact language people use when something is broken, expensive, tedious, or urgent.

Collect examples of:

• direct complaints
• requests for recommendations
• comparisons between workarounds
• expressions of switching intent
• signs that current tools are falling short

Step 3: Score what you find

Not every mention should carry equal weight. A simple scoring system helps.

For each signal, rate:

• frequency: does this appear repeatedly?
• specificity: is the problem concrete?
• severity: how painful is it?
• intent: are people trying to solve it now?
• market context: is this tied to an active buyer group?

This is also the point where curated research can save time. If your team is tired of manually digging through noisy threads every day, a focused resource like Miner can help surface stronger opportunities from Reddit and X by separating validated pain, buyer intent, and weaker signals worth monitoring. For builders who need better evidence before choosing what to build next, that kind of filter is often more useful than another generic startup ideas list.

Step 4: Separate strong bets from interesting noise

This step matters more than most founders realize.

Some ideas are compelling to read about but weak to build around. They may be novel, emotionally engaging, or adjacent to hype, but still lack repeated pain or intent.

Your job is to classify:

Strong bets

• repeated problem
• clear affected user
• visible workarounds
• signs of buying behavior

Weak signals

• interesting but infrequent
• loosely defined user need
• little evidence of urgency
• no clear payment or switching intent

That separation protects your roadmap.

Step 5: Revisit old signals

One snapshot is not enough.

Markets develop through repetition. A niche frustration that looked minor three months ago may now appear weekly. A workflow issue that seemed temporary may turn into a durable category opportunity.

This is why archives matter. When you can review past signals over time, you stop judging opportunities as isolated anecdotes and start seeing trajectories.

What strong demand usually looks like in the wild

The best early opportunities often share a few traits:

The user already has a workaround

If someone built a spreadsheet, stitched together three tools, hired a VA, or wrote a script, that is useful evidence. Workarounds signal pain plus commitment.

The problem sits close to money, time, or risk

Pain tied to revenue, operations, compliance, customer support, or core workflows tends to be more actionable than pain tied to vague preference.

The complaint is specific enough to build against

“Project management tools are bad” is not useful.
“We lose track of client approval status across email and Slack” is.

The same problem appears across multiple voices

You are not looking for one clever post. You are looking for convergence.

What to avoid when validating an idea

A few traps show up repeatedly in early-stage product research.

Mistaking engagement for demand

Likes, reposts, and comments can signal attention, not willingness to pay.

Overvaluing broad problems

If the pain is real but too broad, your product may become impossible to position clearly.

Ignoring market sophistication

Some spaces look attractive because many users complain. But if the category is crowded and mature, complaints may reflect preference rather than unmet demand.

Falling in love with novelty

New workflows attract curiosity. Curiosity is not the same as persistent need.

A better standard before you build

Before you invest seriously in a new SaaS or AI product, try to answer these questions:

• Can I point to repeated pain, not just isolated complaints?
• Do I see explicit evidence that people want a solution?
• Is the user and workflow specific enough to target?
• Do I understand why existing tools are not solving it well?
• Have I tracked the signal long enough to know it is not temporary?

If the answer to most of these is no, you probably do not have a validated opportunity yet. You have a hypothesis.

That is still useful. It just means the next step is more research, not more building.

A grounded way to reduce guesswork

For many builders, the real bottleneck is not creativity. It is signal quality.

There is no shortage of ideas. There is a shortage of ideas backed by repeated pain, visible intent, and enough evidence to justify commitment. That is why a disciplined demand-discovery workflow matters so much, especially for small teams that cannot afford months of speculative work.

If your current research process involves manually scanning Reddit and X, saving scattered posts, and trying to remember what looked promising last month, it may be worth using a more structured input. Ethanbase’s Miner is designed for exactly that situation: a paid daily brief that turns noisy social discussion into clearer product opportunities, validated pain points, and weak signals worth tracking over time.

Explore one useful input, not another source of hype

If you want a more evidence-backed way to choose what to build, explore Miner. It is a good fit for indie hackers, SaaS builders, and lean teams that want stronger demand signals before committing to a product direction.