The most common reason startups fail isn't bad execution. It's building something nobody wanted badly enough to pay for. Validation exists to find this out before you've spent months building it.
But most founders validate wrong. They talk to people who are too polite to say no. They get interest confused with intent. They spend six months on a prototype before talking to a single potential customer.
Here's a framework that actually works.
What validation actually means
Validation is not: asking people if your idea is good. It is not: getting 200 newsletter signups. It is not: building a prototype and showing it to friends.
Validation is the process of finding evidence that a specific group of people have a specific problem they're trying to solve, that they're not satisfied with current solutions, and that they would change their behaviour (ideally, pay money) to fix it.
That's a high bar. And it should be. The goal isn't to feel confident. It's to find out if you're wrong before you've committed a year of your life.
The 5-step validation framework
Write down your core assumption
Every startup is a bet on a specific assumption being true. Articulate yours in one sentence: "[Specific group] has [specific problem], and they're willing to [pay / change behaviour / give up current solution] to fix it." Everything else flows from this.
Find 10 people who match your target group
Not people who might be interested. People who have the problem right now. You need ten, minimum. LinkedIn, community Slack groups, Twitter, Reddit — wherever your target customer spends time. Do not skip this step by interviewing people who are "close enough."
Talk to them about the problem (not your solution)
Run problem interviews. Ask about their current workflow, what they've tried, how much it costs them in time or money. Do not mention your product idea until the end, if at all. You're looking for evidence the problem is real and painful — not for permission to build your solution.
Test willingness to act
At the end of each conversation, ask: "If I built something that solved this, would you want to be in the first group to try it?" Then stop talking. If they say yes: "Can I take your email and follow up?" If they won't give you their email, that's a signal. If 7 out of 10 give you their email, that's a stronger signal.
Build the smallest possible test
A landing page with a signup form. A Notion doc you manually send people. A 1-hour concierge service you deliver by hand. The goal is to test demand with the minimum amount of building. If you can't get 10 people to sign up without writing a single line of code, you have a demand problem — and building won't fix it.
The most common validation mistakes
How to score your idea
After running your interviews, go through each one and ask yourself:
- Did they describe the problem without prompting?
- Have they actively tried to solve it before?
- Is there a cost (time, money, frustration) they can quantify?
- Did they ask when your solution will be ready?
If you're getting yes to most of these in most of your conversations, your idea has a real foundation. Use our free Startup Idea Validator to score your idea across four categories: problem, market, solution, and founder fit.
What comes after validation
Once you've validated the problem, the next test is the solution. Build the smallest version you can — not the full product, but enough to answer the question: can this approach actually solve the problem?
At this stage, structured feedback becomes critical. You've confirmed the problem is real. Now you need to know if your solution is the right one. Getting feedback from people who match your target customer — and who will be honest because they have no personal stake in your success — is the fastest way to find out what's wrong before you build the next version.
Get structured feedback on your validated idea
You've confirmed the problem is real. Now get honest, structured feedback on your solution from matched reviewers on HelpMarq. Free for everyone.
Submit your project →