CB Insights found that 35% of startups fail because there is no market need — the biggest single reason companies die. Validating a business idea means proving real people will pay before you build anything. You get there by interviewing 15-20 potential customers, running small paid tests, and watching what they do instead of what they say. If nobody changes their behavior or hands over money, your idea is not validated — it is just a hope.
Why do most business ideas fail validation?
According to CB Insights research on why startups fail, a lack of market need is the number one cause, cited in about 35% of cases. Founders fall for their own solution before they confirm the problem is real.
The trap is confirmation bias. You ask leading questions, hear polite praise, and treat it as demand. Friends and family rarely tell you an idea is weak. That is why early enthusiasm is a poor signal, and paid commitment is a strong one. Excitement is free. A deposit is not.
What does validating a business idea actually mean?
Validation is evidence that strangers will pay to solve a problem they already have. It is not a survey where people say they might buy someday.
You might also like
Opinions are cheap. Behavior costs something. A pre-order, a paid deposit, a booked sales call, or a signup with a credit card all count as behavior. A thumbs-up on social media does not. The point is to shrink the risk that you spend six months building a product the market quietly ignores.
Eric Ries popularized this loop in The Lean Startup: build the smallest thing that produces real learning, measure the response, then decide. Ash Maurya's Running Lean turns it into a repeatable weekly cycle. Both agree on one rule — get out of the building and test with real people.
How do you validate a business idea in 7 steps?
Here is the sequence I use, adapted from lean startup practice:
- Name your riskiest assumption. Usually it is "people have this problem and will pay to fix it." Test that first.
- Find 15-20 people who have the problem. Not friends. Real prospects inside your target segment.
- Run problem interviews. Ask about their past behavior, not your idea. The book The Mom Test by Rob Fitzpatrick explains how to ask questions that cannot be answered with a polite lie.
- Look for a pattern. If most people describe the same painful, frequent problem, you have a signal worth chasing.
- Build a demand test. A simple landing page describing the offer, plus $100-300 of ads, tells you whether people click and sign up.
- Ask for money. Pre-sell, take deposits, or run a crowdfunding page. Payment is the only vote that fully counts.
- Decide. Continue, pivot, or drop the idea based on what people did, not what they said.
Which validation methods work best?
No single method proves everything. Combine a cheap signal with a strong one. Here is how the common options compare:
| Method | Cost | Time | Signal strength | Best for |
|---|---|---|---|---|
| Customer interviews | Low | 1-2 weeks | Medium | Confirming the problem |
| Landing page + ad test | $100-300 | About 1 week | Medium-high | Measuring demand |
| Pre-sale or crowdfunding | Low | 2-4 weeks | Very high | Proving willingness to pay |
| Concierge MVP | Medium | 2-3 weeks | High | Testing the solution by hand |
| Wizard of Oz MVP | Medium | 2-3 weeks | High | Faking automation to test value |
Start with interviews to learn the problem, then use a pre-sale to prove money will follow. If you want a deeper menu, David Bland and Alex Osterwalder's Testing Business Ideas catalogs more than 40 experiments you can run.
Should you build an MVP or sell first?
Sell first. That is my stance, and it cuts against the instinct to build.
You do not need a working product to test demand. A landing page, a pitch deck, or a manual concierge service can prove people will pay while you build almost nothing. Y Combinator's startup library is full of founders who sold before they shipped. Build the product once you have deposits, a waitlist that converts, or a pilot customer who signed a contract. Building first flips the risk the wrong way: you spend your scarcest resource, time, on an unproven guess.
How many customer interviews are enough?
Aim for 15-20 per customer segment. In my experience, the first five interviews teach you the most, and by number fifteen the answers start repeating. That repetition, called signal saturation, is your cue to stop.
Keep sessions short, around 20 minutes. Ask about the last time they faced the problem and what they did about it. If they already pay for a workaround, that is gold. If they shrug and call it "not a big deal," believe them and move on to the next idea.
0 Comments
Log in to comment
Not a member yet? Join the community
Pick a meme
KlipyHave a great take?
Drop your email — we'll send a magic link so you can post it. No password.
Not a member of the community? Join today.
Join the community →