All hubs

Validation

Customer discovery that finds real demand

The single highest-leverage activity for pre-PMF founders is sitting down with real candidate customers and asking honest questions. Done right, customer discovery cuts months off the path to revenue. Done as theatre — asking biased questions, taking happy talk as validation — it actively misleads. This hub walks through how to do it like a founder, not a focus group moderator.

Last updated May 21, 2026

Who this is for

Founders before product-market fit who need to learn whether the problem and customer they're betting on actually exist.

What you'll learn

  • The 5-question customer discovery interview that finds problems, not opinions
  • Problem interviews vs solution interviews — when to do each
  • How many interviews you need (and the diminishing-returns curve)
  • How to spot fake demand vs real demand
  • How to turn interview notes into a wedge
Get the customer discovery template

The 5-question interview

Use this for problem interviews — the kind you run before you've built anything. Each question is open-ended; let them talk.

  1. "Walk me through the last time you did [task]." Get the story. Names, tools, friction.
  2. "What was the hardest part of that?" This is where the pain lives. Stay quiet after.
  3. "Why was that hard?" Push for root cause. Most first answers are surface.
  4. "What did you try to solve it?" Active searching = real pain. "I just lived with it" = mild pain.
  5. "What would solving this be worth?" Pause. Watch what they say (and don't say). Anyone who can't quantify isn't paying.

What you DON'T ask: "Would you use a tool that...?" — they'll lie politely. "Is this a problem you'd pay for?" — same. You're listening for stories, not pitching.

Problem interviews vs solution interviews

Problem interviews (first 20-50 conversations): Goal is to confirm the problem exists, who has it, how often, what they pay today. No product talk. Listen 90% of the time.

Solution interviews (next 10-20 conversations, after you have a prototype): Show what you'd build. Ask "what would this not do that you'd still need?" Look for unprompted use-case extensions — they reveal where the value actually is.

The trap: Skipping problem interviews and going straight to solution. Almost guarantees you build the wrong thing. Even worse: hearing politely positive solution feedback ("looks cool!") and treating that as demand.

How many, and how to spot fake demand

How many: ~15 interviews before you spot patterns. ~30 to be confident about the segment. After ~50 you're in diminishing returns. Most founders do 3 and call it done.

Signs of real demand:

  • They name the workaround they use today (time, money, frustration cost)
  • They mention specific recent moments of pain (last week, last month)
  • They volunteer "if you build this, send me the link"
  • They sign LOIs or pre-pay

Signs of fake demand:

  • General enthusiasm ("great idea!", "I'd definitely use that") without specifics
  • "I have a friend who would love it" (always a flag — your customer is never their friend)
  • "Drop me a line when it's ready" with no urgency
  • Praise that focuses on the founder, not the problem

When in doubt: ask for $1 of commitment. A pre-order, a LOI, a calendar hold. Free praise is cheap; the moment you ask for anything real, the demand reveals itself.

Step-by-step action plan

Do these, in order

  1. 1Identify your candidate customer segment in one sentence (role + size + situation)
  2. 2List 30 prospects and start outreach this week (10 emails/day)
  3. 3Run the 5-question interview with each; transcribe within 24 hours
  4. 4After interview 15, look for repeating language and workarounds
  5. 5Ask for $1 of commitment from the next 5 — see who actually moves

Frequently asked questions

How do I find 30 candidate customers to interview?
LinkedIn outreach (specific role + company size), warm intros from your network, niche Slack/Discord communities, Reddit subreddits, conferences. Offer a $25 gift card or a copy of the eventual product. ~20% response rate is normal.
Should I record interviews?
Ask permission. Recording lets you re-listen for the exact language, which becomes your marketing copy. If they decline, take detailed notes during; transcribe within 24h while it's fresh.
What if everyone I talk to says yes?
You're either asking biased questions, talking to too narrow a sample of friends-and-family, or pitching instead of listening. Test with a $1 commitment ask; the unanimous "yes" usually disappears.
Can I just send a survey?
Surveys are useful for sizing once you know the question. They're terrible for discovery — they constrain the answers to your hypothesis. Conversations expose what you didn't know to ask.

Related tools

Related templates

Related hubs