The Validation Problem Most Founders Get Wrong
Spend enough time in startup ecosystems and you'll encounter the same tragic pattern: a founder spends 12–18 months building a product, launches it, and then discovers that not enough people care. The issue was rarely execution — it was assumption. The founder assumed there was a market, assumed customers had the problem they were solving, and assumed people would pay for the solution.
Validation is the process of replacing assumptions with evidence before you commit major resources. It doesn't need to be expensive or slow — in fact, the best validation is fast and cheap.
The Four Questions Every Idea Must Answer
- Is the problem real? Do real people experience this problem regularly, or is it rare and niche?
- Is the problem painful enough? People need to be motivated to seek a solution — mild inconveniences rarely create businesses.
- Will people pay to solve it? Willingness to pay is the most meaningful signal of genuine demand.
- Can you reach your customers? Even a great product fails if there's no cost-effective path to acquiring customers.
Stage 1: Problem Validation (Before You Build)
Conduct Problem Interviews
Talk to at least 20–30 potential customers. The goal is NOT to pitch your idea — it's to understand their world. Ask about:
- How they currently solve the problem
- What frustrates them about existing solutions
- How often the problem occurs and what it costs them
If you can't find 20 people willing to spend 20 minutes discussing this problem, that itself is a signal.
Search for Existing Solutions
If competitors exist, that's actually a good sign — it confirms market demand. Study reviews of competing products. The complaints and requested features in 1-star reviews are pure gold for understanding unmet needs.
Stage 2: Solution Validation (Before You Scale)
Build the Minimum Viable Product (MVP)
An MVP is not a rough version of your full product. It's the smallest possible thing that lets you test your core assumption. This might be:
- A landing page with a sign-up form to measure interest
- A manual concierge service that mimics the future automated solution
- A clickable prototype that looks like a product but isn't built yet
- A pre-sale or waitlist campaign
Set Validation Criteria in Advance
Define what success looks like before you run the experiment. For example: "If 10% of landing page visitors sign up and 3 people agree to pay in advance, we'll proceed." Without pre-defined criteria, it's easy to rationalize weak results.
Stage 3: Market Validation (Before You Raise)
Once you have paying users, focus on learning:
- Retention: Do customers come back? Do they use the product regularly?
- Referrals: Are users telling others? Word-of-mouth is the strongest validation signal.
- Willingness to pay more: Can you increase prices without losing customers?
Common Validation Mistakes to Avoid
- Asking leading questions in interviews that confirm your biases
- Counting "I would use that" as validation — hypothetical interest is not the same as real demand
- Validating with friends and family who are unlikely to give honest, critical feedback
- Skipping to the build phase because you're excited about the solution
The Bottom Line
Validation is an investment in efficiency. Every week spent validating before building is potentially months of wasted development saved. The best founders are obsessively curious about their customers and treat their initial assumptions as hypotheses to be tested — not truths to be executed on. Build only what the evidence tells you to build.