Validation isn't about proving you're right. It's about finding out you're wrong while it's still cheap to change course.
Almost every founder falls in love with the solution before they're sure the problem is real. It's human — you've imagined the product, named it, pictured people using it. But customers don't buy solutions; they buy their way out of a problem. Validation is the work of confirming the problem is painful, common, and that people will actually pay to make it go away — before you write a line of code or sign a lease.
Start with the problem, not the product
Write down the problem you think you're solving in one sentence, framed entirely from the customer's point of view. Not "an app that does X," but "people who do Y waste hours every week on Z." If you can't name who has the problem and how often they feel it, that's your first sign to slow down.
Then ask the uncomfortable question: how are people solving this today? Every real problem already has a workaround — a spreadsheet, a competitor, duct tape, or simply living with it. If there's no current workaround, the pain may not be big enough to bother with.
Talk to ten people who actually have the problem
This is the single highest-leverage thing you can do, and most founders skip it because it's intimidating. You don't need a survey of a thousand people. You need real conversations with ten people who fit your target customer — and you need to listen more than you talk.
Good interview habits:
- Ask about the past, not the future. "When did you last run into this?" beats "Would you use a product that…?" People are terrible at predicting their own behavior and generous with hypothetical enthusiasm.
- Don't pitch. The moment you describe your idea, they start being polite. Keep your solution in your pocket until the very end.
- Dig into the cost. How much time, money, or frustration does the problem cause? A problem nobody pays to avoid is a hobby, not a business.
SCORE offers free 1:1 mentoring with experienced businesspeople who can help you sanity-check what you're hearing, and the SBA's local resources can point you toward your customer base. Use them — that's what they're there for.
Test demand with the smallest possible thing
Once you believe the problem is real, test whether people will act — using the lightest experiment that produces an honest signal. You're not building the product; you're buying evidence. A few proven approaches:
- A landing page. One page describing the offer with an email signup or a "notify me" button. If you can drive a little traffic to it and people sign up, that's a real signal.
- A pre-order or waitlist. Asking for a credit card or even a refundable deposit separates "nice idea" from "take my money."
- Concierge delivery. Deliver the outcome manually for your first few customers — by hand, behind the scenes — before automating anything. It's slow, and that's the point: you learn exactly what people value.
Signals that you're onto something
- People describe the problem back to you with more intensity than you expected.
- They're already paying for a clumsy workaround.
- Someone tries to give you money before the product exists.
- They follow up with you, unprompted, asking when it's ready.
Decide what would change your mind
Before you run any test, write down what result would tell you to stop. Maybe it's "if fewer than 3 of 10 people have felt this in the last month, I move on." Founders who skip this step tend to interpret every result as encouragement. Pre-committing to a kill signal keeps you honest with yourself.
Validation is a loop, not a checkbox
You won't get a clean yes or no. You'll get signals that sharpen the idea — a narrower customer, a different problem than you assumed, a feature that matters more than the one you led with. That's the whole point. Each loop costs you days, not months, and each one makes whatever you eventually build far more likely to land.