How to validate a startup idea before you build it

An idea is validated when people with the problem show they'll act on it: they agree to a call, join a waitlist, pre-order or pay. Spend a week talking to ten people who have the problem, a week testing a landing page with a clear offer, and only then build the smallest version that solves it.

What validation actually means

Friends saying "I'd use that" is not validation. Validation is behaviour: someone spends time, money or reputation on your idea. The further along that line they go, from a reply to a call to an email signup to a payment, the stronger the signal.

Step 1: write down the problem, not the product

Describe who has the problem, when they hit it and what they do about it today. If you can't name what they do today, you may not understand the problem yet. The current workaround (a spreadsheet, a freelancer, doing nothing) is your real competitor.

Step 2: talk to ten people who have it

• Find them where they already talk about the problem: communities, forums, reviews of competing tools.
• Ask about the past, not the future: "Tell me about the last time this happened" beats "Would you use…".
• Ask what they've tried and what it cost them in time or money.
• Don't pitch. You're there to learn; pitching makes people polite instead of honest.
• Write down their exact words. They become your landing page copy later.

Step 3: test demand with a landing page

Put up one page with the problem, the promised outcome, a rough idea of price and one button: join the waitlist, book a call or pre-order. Send the people you interviewed and the communities you found there. A waitlist with people who wrote back when you emailed them is a strong sign. A pre-order is stronger still.

Step 4: decide

• Strong signal: people describe the problem without prompting, some already pay for a bad fix, and signups reply to your emails. Build the smallest version.
• Weak signal: people agree it's a problem but have never tried to fix it. Narrow the audience or the problem and test again.
• No signal: nobody bites after real effort. Drop it or change it; two weeks lost is cheap next to six months.

Then launch early

Once a first version solves the core problem, launch it. Real users teach you faster than more interviews. Our launch checklist and first users guide cover what comes next.

Frequently asked questions

How many customer interviews do I need to validate an idea?

Around ten conversations with people who clearly have the problem usually shows a pattern. If ten people describe it differently, the problem or the audience is still too broad.

Can I validate an idea without building anything?

Yes. Interviews, a landing page with a waitlist or pre-order, and a manual version of the service you deliver by hand all test demand before you write code.

Is a big waitlist proof my idea works?

Not on its own. Signups are cheap. Check whether people reply to your emails, take a call or pay. A small list of engaged people beats a big list that never opens anything.