How to Validate a Product Idea Before You Build Anything
Most product ideas fail before launch because the demand was never real. Here’s a practical way to test pain points, buyer intent, and recurring demand signals before you spend weeks building the wrong thing.
A surprising number of product ideas feel promising for one simple reason: they sound plausible in isolation.
You notice a complaint on Reddit. A founder on X mentions a painful workflow. A niche seems underserved. Pretty soon, you can imagine the landing page, the MVP, even the launch thread.
But plausibility is not demand.
If you want to make better product bets, the job is not to find a clever idea. The job is to find a painful, recurring problem that people already care enough to describe clearly, work around awkwardly, or actively pay to solve.
Here’s a practical way to validate an idea before you build.
Start with pain, not categories
Many builders begin with a market category: “AI for recruiting,” “CRM for agencies,” “automation for finance teams.”
That’s usually too broad to be useful.
Validation gets easier when you start narrower:
- A repeated workflow frustration
- A task people are doing manually too often
- A problem that creates delays, errors, or revenue loss
- An existing workaround that users clearly dislike
Good early signals often sound like this:
- “I’m tired of stitching together three tools just to do this one thing.”
- “We still do this in spreadsheets because every tool is overkill.”
- “I’d pay for something that solved this cleanly.”
- “Does anyone know a tool for this?”
- “We tried X, but it breaks when…”
Those statements are far more useful than general excitement around a market. They point to real friction.
Look for repeated language, not isolated complaints
One person being annoyed is not a market.
Ten people describing the same job-to-be-done, in similar language, over time, is more interesting.
When reviewing discussions on Reddit and X, pay attention to patterns such as:
- The same pain point showing up in multiple communities
- Similar complaints from people in the same role
- Requests for alternatives to existing tools
- Buyers asking for recommendations, not just opinions
- Users explaining what they already tried and why it failed
This is where many founders get misled. Social platforms produce an endless stream of emotional, exaggerated, and novelty-driven commentary. That noise can make weak ideas look stronger than they are.
A better approach is to separate:
- recurring pain from random frustration
- buyer intent from casual discussion
- durable workflow problems from short-lived hype
If you want help doing that consistently, tools like Miner from Ethanbase are useful for builders who don’t want to manually comb through Reddit and X every day. Its core value is simple: turning noisy conversations into daily, evidence-backed opportunity signals, with validated pain points, explicit buyer intent, and weaker signals kept separate from stronger bets.
Ask whether the problem is expensive enough
A real problem still may not be a viable product opportunity.
The next question is: what does this pain cost?
That cost doesn’t always have to be financial on the surface. It can show up as:
- lost hours
- operational mistakes
- delayed decisions
- missed leads
- poor customer experience
- team frustration
- compliance or reporting risk
The sharper the cost, the easier the sale.
For example, “people dislike writing status updates” is weak.
“Operations teams spend six hours every week compiling cross-tool updates for clients” is stronger.
One sounds mildly annoying. The other sounds budget-worthy.
Check for behavior, not just sentiment
People often overstate what they want and understate what they’ll actually do.
That’s why the best validation signals are behavioral:
- They are actively searching for solutions
- They mention paying for current tools
- They built workarounds
- They switched tools and still remain unsatisfied
- They ask peers what they use
- They return to the same complaint repeatedly
A useful rule: complaints are interesting, but effort is stronger.
When users invest time, money, or reputation into solving a problem, you’re closer to something real.
Score the opportunity before you romanticize it
Founders often fall in love with the shape of a product before scoring the quality of the problem.
A lightweight scoring system can help. Rate each idea from 1 to 5 on:
1. Frequency
How often does the problem appear?
2. Specificity
Are people describing a concrete workflow pain, or speaking vaguely?
3. Buyer intent
Do users ask for tools, alternatives, or recommendations?
4. Existing dissatisfaction
Have they tried current solutions and found them lacking?
5. Consequence
Does the problem waste money, time, or trust?
An idea with moderate hype but high specificity and strong buyer intent is often better than a trendy idea with lots of engagement and little consequence.
Validate the niche before the product
A common mistake is asking, “Would people use my product?”
That question is too late.
Ask first:
- Is this niche consistently experiencing the same pain?
- Can I identify the user role clearly?
- Do they already try to solve this problem?
- Is the problem painful enough to prioritize?
- Can I explain the value proposition in one sentence?
If you cannot define the niche sharply, your product idea is probably still too blurry.
The strongest early opportunities usually live at the intersection of:
- a clear user type
- a repeated painful workflow
- visible intent to solve it
- dissatisfaction with current options
Track signals over time
One of the hardest parts of idea validation is resisting recency bias.
A fresh complaint feels urgent. A viral thread feels important. But product demand is usually clearer over weeks and months than in a single day.
That’s why archives matter.
Being able to review past signals helps answer better questions:
- Is this pain recurring or just topical?
- Is interest growing, stable, or fading?
- Are more people describing the same workflow issue over time?
- Is buyer intent becoming more explicit?
For indie hackers and lean product teams, this kind of pattern-tracking can save weeks of work. Instead of chasing every interesting conversation, you start building a case for demand.
A simple pre-build validation workflow
Before writing code, try this sequence:
- Collect 20-30 pain-point mentions around a narrow workflow.
- Group them by repeated job-to-be-done.
- Highlight direct signs of buying intent.
- Note which existing tools are mentioned and why they fail.
- Score the opportunity on frequency, specificity, consequence, and intent.
- Recheck the signal after a few days or weeks.
- Only then sketch an MVP around the clearest pain.
This process is slower than impulse-building, but much faster than spending a month on an idea nobody truly needed.
The goal is not certainty
Validation will never remove all risk.
What it can do is improve the quality of your bets.
Instead of building from a clever hunch, you build from repeated evidence:
- users saying the same thing
- buyers showing intent
- weak signals filtered out
- patterns observed over time
That’s a much stronger place to start.
A grounded next step
If your current challenge is finding reliable demand signals without spending hours manually reading Reddit and X, Miner is worth a look. It’s a good fit for indie hackers, SaaS builders, and lean teams that want daily high-signal research, clearer separation between strong opportunities and weak noise, and an archive they can revisit before committing to a product direction.
Related articles
Read another post from Ethanbase.
How to Restart a Stalled Sales Email Thread Without Sounding Desperate
When a sales thread goes quiet, the problem is usually not timing alone. This guide shows founders and small B2B teams how to diagnose what stalled the deal and choose a better next reply.
How to Practice for Product Manager Interviews Without Wasting Time on Generic Prep
Most PM interview prep fails because it stays too generic. This guide shows how to practice against real job requirements, handle sharper follow-ups, and improve your stories, metrics, and tradeoff thinking faster.
How Active Traders Can Make Pre-Market Prep More Decisive
Many active traders already do pre-market prep, but still arrive at the open overloaded and unclear. Here’s a simple way to narrow focus, structure your thinking, and review setups with more discipline before execution.