Why Validation Comes Before Everything Else
One of the most common — and costly — mistakes early-stage founders make is building a product before confirming that anyone actually wants it. Months of development, savings poured in, and then: silence. No customers, no traction, no feedback worth acting on.
Idea validation is the process of testing your assumptions about a problem and a potential solution before you fully commit. It saves time, money, and a lot of frustration. Here's how to do it properly.
Step 1: Clearly Define the Problem You're Solving
Start with the problem, not the solution. Ask yourself:
- Who exactly has this problem?
- How often do they experience it?
- How are they solving it today?
- How painful or costly is this problem for them?
If you can't answer these clearly, you don't yet understand the problem well enough to solve it. Spend time here before moving forward.
Step 2: Talk to Real People (Customer Discovery)
There is no substitute for real conversations. Reach out to 15–20 people who fit your target customer profile and have open-ended conversations — not pitches. Ask about their current workflows, their frustrations, what they've tried before, and what an ideal solution would look like.
Key rules for customer discovery interviews:
- Never lead with your idea — let them describe the problem in their own words.
- Ask about past behavior, not hypothetical future behavior ("Would you use this?" is a weak signal; "How did you handle this last time?" is much stronger).
- Look for patterns across multiple interviews, not just enthusiasm from one person.
Step 3: Test with a Landing Page
Before building a product, build a page. A simple landing page describing your solution with a call-to-action (like an email sign-up or a waitlist button) can tell you a great deal about real intent. Drive traffic to it through social media, relevant online communities, or even a small paid ad budget, and track how many people take action.
A conversion rate of even a few percent from cold traffic is a meaningful early signal.
Step 4: Offer a Manual "Concierge" Version
Before automating anything, do it manually. If you're building a job-matching platform, manually match a few candidates to companies. If you're building a budgeting tool, help a few people budget using spreadsheets. This approach — often called a "concierge MVP" — lets you deliver real value, gather deep feedback, and confirm willingness to pay without building technology.
Step 5: Look for Willingness to Pay
Positive feedback feels good, but it's not enough. The strongest validation signal is someone paying for your solution — even in a pre-sale, a deposit, or a paid pilot. If people love the idea but won't commit any money, that's important information too.
Common Validation Mistakes to Avoid
- Asking friends and family: They want to be supportive, not honest.
- Surveying too broadly: Generic surveys yield generic, low-quality data.
- Confusing interest with intent: "That's a great idea!" is not the same as "I'll pay for that."
- Validating with the wrong customer segment: Make sure you're talking to the actual decision-maker, not just an end user.
When Are You Validated Enough to Build?
There's no perfect threshold, but a reasonable benchmark is: you've spoken to at least 15 people in your target market, identified a consistent problem, and have at least a few people who are ready to pay or are already using a manual version of your solution. At that point, you have enough signal to begin building a focused MVP.
Validation is not a one-time event — it's an ongoing discipline throughout your startup's life. But getting it right at the beginning dramatically improves your odds of building something the market actually wants.