How to Test a Business Idea in 5 Steps (Before You Build It)

The top reason startups fail is not money or competition. In CB Insights' analysis of failed-startup post-mortems, the leading cause was building something nobody needed, in roughly 43% of cases. It is also the most avoidable one.

Testing a business idea comes down to a single principle: pay attention to what people do, not what they say they will do. Here are the five steps.

Step 1: Write down your assumption

Good ideas start with a friction you keep hitting, or watch others hit. The word that matters is persistent: a problem that recurs is worth solving, a one-off annoyance is not.

Turn the observation into one testable sentence naming who has the problem, what it is, and why they would want something new. Written plainly, it exposes the weak point in your own thinking, and every later step exists to confirm or disprove it.

Step 2: Analyse the market

Desk research tells you whether interest is rising or fading, and where the gaps are. Google Trends is free and takes ten minutes.

Then look at who is already doing this: their pricing, and above all their customer reviews, which are a free source of unmet needs in your customers' own words. If the market looks crowded, go narrower rather than broader. A sharp offer for a specific group beats a generic one aimed at everyone.

Step 3: Talk to potential customers

Five to eight conversations with people who match your audience, run as user research. One rule above all others: do not pitch your idea. Anchor every question in what they have already done.

• How do you deal with this at the moment?
• What did it cost you, in time or money, the last time it came up?
• What have you tried before, and why did you stop?

What someone has done is a reliable signal. What they say they might do is not. Two things draw out honest answers: say openly that the unflattering responses are the useful ones, and when an answer comes out thin, let the silence sit. The first thing people say is the tidy version.

Step 4: Test demand, price, and feature priorities

Interest is free, so it proves little. The only honest signal is whether people commit something real. A product research survey puts a number on all three.

• Demand: a landing page with a real price and a real action, or better, pre-orders.
• Price: the Van Westendorp method, asking at what point it feels too expensive and at what point so cheap you would doubt it.
• Features: force a trade-off. Ask people to rate everything and they will rate everything highly.

Founders routinely overvalue the features they are excited about and undervalue the dull ones that drive the decision to buy. Then sanity-check the economics, so you can tell a viable idea from one that only looks popular because it is underpriced.

Step 5: Validate and iterate

Only now does it make sense to test the product itself, through concept and prototype testing, in front of people you have already confirmed have the problem.

• Does it fit into their day, or demand too much change?
• Is it clear what it does within a few seconds?
• Would they use it occasionally, or regularly?

That last one quietly decides most outcomes, and it only shows when you ask about frequency directly. This is a loop, not a final gate. Act on signals that repeat, treat one-off opinions as noise, and keep running it after launch.

How many people do you need to test with?

There is no magic number, but reaching too few is the usual mistake. It is what pushes founders toward friends and family, whose feedback is the most flattering and the least useful.