How to validate a startup idea with real evidence

A practical validation guide: the evidence hierarchy, how to test problem and customer assumptions, and what separates weak signal from strong evidence.

Quick answer

Validate an idea by ranking your assumptions by how badly you would be hurt if they were wrong, then testing the most dangerous one with the strongest evidence you can afford. Money changing hands and repeated unprompted use are strong evidence; positive opinions and survey intent are weak.

Start from the assumption that would hurt most

List what has to be true for the business to work, then rank by damage-if-wrong rather than by ease of testing. Most founders test the comfortable assumptions first — whether the product can be built — and leave the dangerous one untested: whether anyone will pay to have this problem solved.

• The problem is frequent and painful enough to act on
• A definable group has it and can be reached
• They will pay, or someone will pay on their behalf
• You can deliver at a cost that leaves a margin
• You can acquire customers for less than they are worth

The evidence hierarchy

Not all evidence is equal, and treating it as equal is how founders convince themselves. Rank what you gather, and be honest about where each piece sits.

• Strongest — repeat paid usage, renewals, signed contracts
• Strong — a single payment, a paid pilot, a binding commitment
• Moderate — unprompted repeat use of a free product, referrals
• Weak — sign-ups, waiting lists, positive interviews
• Weakest — survey intent, social engagement, encouragement from people who will never buy

Interview for behaviour, not opinion

Asking whether someone would use your product produces politeness. Asking what they did the last time they hit the problem produces information. Anchor every question in past behaviour, and let them describe the workaround they already use — that workaround is your real competition.

• When did you last hit this problem?
• What did you do about it?
• What did that cost you in time or money?
• What did you try before that, and why did you stop?
• Who else was involved in deciding?

Design a test that can fail

A test that cannot produce a negative result is a marketing exercise. Before running anything, write down the number that would make you stop or change direction. If you cannot state it, you are not testing — you are collecting encouragement.

• State the assumption in one sentence
• State the metric and the threshold in advance
• Set a time box
• Record the result, including when it disconfirms you

Common validation traps

These are the patterns that produce confident founders with no business. Each one feels like evidence at the time, which is exactly why they are worth naming before you start.

• Talking only to people who like you
• Counting sign-ups as demand
• Changing the target customer after every conversation
• Building for months between tests
• Treating a large market as evidence that you can reach any of it
• Discarding disconfirming evidence as 'not the right customer'

Write down what changed

Validation only compounds if the learning is recorded. Keep a short running record of each assumption, what you tested, what happened, and what you now believe. Six months of that record is the most persuasive thing you can show an investor, because it demonstrates how you think rather than what you hope.

Home · Features · How it works · Pricing · Compare · For founders · Try free