All hubs

Getting Started

How to validate a business idea

Validation is the cheapest insurance policy in business. Done well, you spend two weeks and $200 to find out an idea is dead — instead of spending six months and $40,000 of your life. Done badly, you collect a stack of 'great idea!' compliments from friends and build something nobody pays for. This guide is the difference.

Last updated May 19, 2026

Who this is for

Founders sitting on an idea who don't yet know if anyone will pay for it.

What you'll learn

  • Which validation methods produce real evidence vs comforting noise
  • How to run a customer interview that surfaces actual pain
  • How to design a smoke test landing page that doesn't lie to you
  • When to take pre-orders and when not to
  • What 'validated enough to build' looks like
Build your interview script

The evidence hierarchy

Not all validation evidence is equal. Order them from weakest to strongest:

  1. Compliments — "Great idea!" Nearly worthless. Your friends will lie to spare your feelings.
  2. Survey responses — "Yes, I'd use this." Slightly better, still cheap talk.
  3. Email signups for a waitlist — Weak. People sign up for things they'll never buy.
  4. Interview pain admission — "I'm currently doing X manually and it kills me." Real signal.
  5. Time given — "Yes, I'll spend 30 minutes on a call to walk you through how I do this today." Strong signal.
  6. Pre-orders / paid LOIs — "I'll pay you $500 now to be customer #1." Almost the only signal that matters.

If you don't have at least 3-5 hits at level 4 or above, you don't have validation. You have hope.

How to run a customer interview that works

The biggest mistake first-time founders make in interviews is pitching. Don't. The customer is the data source; you are the interviewer.

Three rules:

  1. Ask about the past, not the future. "Walk me through the last time you did X" beats "Would you use a tool that does X?"
  2. Specifics beat opinions. "What was annoying about that?" beats "What features do you want?"
  3. Listen for pain you can hear. When someone tells you about a problem with audible frustration in their voice, that's the signal.

After 5 interviews you'll see patterns. After 10 you'll know if you have a real problem. Use the Customer Discovery Script as a starting point; adapt to your context.

Smoke tests that don't lie

A smoke test is a landing page that pretends the product exists, with a real call to action. Done well: high signal. Done badly: garbage.

What works:

  • Real, specific value prop. "Schedule meetings 10× faster with AI" is bad. "AI scheduler for solo founders that books deep-work blocks first" is testable.
  • Realistic price, not "Coming soon, get on the waitlist."
  • Friction at the right point. "Pre-order for $99" produces signal. "Sign up for early access" doesn't.
  • Tracking the right metric. Conversion rate from real traffic (not your network) is the only metric that matters.

What doesn't:

  • Promoting the page to your audience and counting their signups as validation
  • Free signup as the conversion event ("I'd try it for free!" — of course they would)
  • Cute features and design before the offer works

Concierge MVP — deliver before you build

For the right kind of business, the fastest validation is to deliver the outcome manually for the first 5 customers, charging real money, with zero code.

A SaaS that automates accounting? Do their accounting by hand for $500/mo. A content tool that finds keywords? Run the keyword research yourself in Google Docs.

If your first 5 customers pay you $500/mo each to do the thing manually, you have an idea worth automating. If you can't find 5 paying customers for the manual version, you don't have a software business — you have a hobby.

What 'validated' actually looks like

You're validated enough to build when you can answer all of these:

  • "Who exactly is the customer?" — Specific role + company size + situation.
  • "What pain are they hiring you to solve?" — One sentence, plain English.
  • "How are they solving it today?" — Without your product. (This is the real competition.)
  • "Why is the current solution not enough?" — Specific frustration, not generic complaint.
  • "What will they pay?" — Real numbers from a real conversation, not your guess.

If any of those answers is vague, do another round of interviews. Building before this is the most common way to waste a year.

Step-by-step action plan

Do these, in order

  1. 1Score the idea on the Business Idea Scorecard
  2. 2Build a list of 30 people who fit your ICP
  3. 3Book 10 customer interviews this fortnight
  4. 4Ship a smoke-test landing page with a real CTA
  5. 5Set a kill / continue criterion before running the test

Frequently asked questions

How many customer interviews are enough?
10 deep interviews beats 100 shallow surveys. The pattern usually shows itself by interview 5-8 if your ICP is sharp.
What if nobody will pre-order?
Then the idea isn't validated, regardless of how much enthusiasm you've collected. Pre-order resistance is the cheapest lesson in business.
Should I show a prototype during interviews?
Only after you understand the pain. Showing a prototype early corrupts the answer — people start reacting to your design instead of describing their reality.

Related resources

Related tools

Related templates

Related courses

Related hubs