How to Validate a Product Idea Before You Build

There is a graveyard of technically excellent products that nobody wanted. The founders were not lazy or unskilled — they simply built first and asked later. Validation is the discipline of reversing that order: spend a little effort up front to learn whether the market is real, so you do not spend a lot of effort building for a market that is not.

What you are actually testing at this stage

"Validation" gets used loosely, so it helps to separate three different things:

• Demand validation — do people want this outcome badly enough to seek it out or pay for it? This is the question that kills most ideas, and the one to answer first.
• Idea validation — is your specific solution the one they want, versus a different shape of the same fix?
• Usability validation — can people actually use what you built? This only matters once demand and idea are proven, so save it for later.

The mistake is jumping straight to usability — polishing an onboarding flow for a product no one has demonstrated they want.

Five cheap experiments, ranked by signal strength

Not all validation produces equally trustworthy evidence. From weakest to strongest signal:

1. Landing page + email waitlist. Fast and cheap, but an email is a low bar — people give one without much thought. Useful for reading relative interest across variants.
2. Existing-demand check. Search request marketplaces, communities, and reviews for people already asking for your solution. Free, fast, and often decisive: if the demand is visible, you have your answer.
3. Concierge test. Deliver the outcome manually for a handful of real users before automating anything. If they will not accept the result even done by hand, no software will save it.
4. Waitlist with a deposit or commitment. Asking for a small, refundable commitment filters curiosity from intent instantly.
5. Pre-sale. The strongest signal short of a live product. People paying before it exists is the clearest possible statement that the problem is real and worth money.

How to tell real intent from politeness

The most dangerous feedback is "that's cool." It feels like validation but costs the speaker nothing. Real buying intent looks different: people ask when they can have it, describe exactly how they would use it, tell you what they pay for their current workaround, or try to give you money. Weight signals by what they cost the person to give. An enthusiastic comment is worth little; a pre-order is worth a great deal.

Using a request marketplace to skip the experiment

Often the cheapest validation is not an experiment at all — it is checking whether other people have already run it for you. On RequestProduct, people post the products they wish existed and others upvote them. If your idea already appears as a request with strong upvotes and no product solving it, you are looking at demand you did not have to manufacture. You can also post your idea as a request and watch whether strangers pile on — a public, low-cost way to see if the need resonates beyond your own head. Browsing categories also tells you how crowded a space already is.

Set a go/no-go bar first

Decide your threshold before you run anything. Write it down: "I will build if X people pre-commit" or "if I find Y independent requests for this." Founders who skip this step end up moving the goalposts to justify building the thing they were always going to build. A bar set in advance is the only thing that protects you from your own optimism.

From validated demand to a two-week MVP

Once demand clears your bar, scope the smallest thing that delivers the core outcome — not the smallest thing you can technically ship. Cut every feature that is not the one people asked for. The goal of a first build is to convert validated demand into real usage as fast as possible, then let actual behavior tell you what to add next.

Common validation mistakes

• Leading questions. "Would you use a tool that saves you time?" gets a yes from everyone and teaches you nothing. Ask about past behavior, not hypothetical futures.
• Friends-and-family bias. People who like you will not tell you the idea is weak. Test with strangers who have the problem.
• Vanity signups. A big waitlist that never converts is a warning, not a win. Chase intent, not volume.

Next steps

If you are still upstream of a specific idea, start with how to find validated startup ideas. Once your idea is validated and built, the next challenge is distribution — read how to find early adopters for your startup and our roundup of the best Product Hunt alternatives.