The first phase of Steve Blank's Customer Development methodology (2005). The work of finding out whether the problem you think exists actually exists, for the buyer you think has it. It precedes customer validation (proving the buyer will pay). Customer discovery uses interviews and observation; customer validation uses behavioral evidence (pre-orders, signed LOIs, paid pilots). Both are required before scaling.
The fast version
Customer discovery is the first phase of Steve Blank’s Customer Development methodology (The Four Steps to the Epiphany, 2005). It’s the work of finding out whether the problem you think exists actually exists, for the buyer you think has it.
Discovery uses interviews and observation. The output: a defensible answer to:
- Who is the buyer? (Specific, named, reachable.)
- What’s the problem? (Real, frequent, intense, costing them today.)
- What’s their current workaround? (And why does it persist?)
- What’s the job they’re hiring a solution to do? (JTBD switch statement.)
Discovery is not validation. Validation comes next.
Customer Development’s four phases
Blank’s methodology, briefly:
- Customer Discovery. Does the problem exist? Discovery interviews + observation.
- Customer Validation. Will buyers pay? Behavioral evidence: pre-orders, paid pilots, signed LOIs.
- Customer Creation. Does demand scale? Marketing + sales motions to expand from the validated beachhead.
- Company Building. Operational scaling. Move from “find customers” to “serve at scale.”
Modern startup playbooks (Lean Startup, ShipFit’s 9 stages) reorganize these phases but the underlying logic is intact: prove the problem exists before you prove the solution; prove the solution sells before you scale; scale before you build the company around it.
How discovery is different from validation
| Discovery | Validation | |
|---|---|---|
| Question | Does the problem exist? | Will the buyer pay? |
| Method | Interviews, observation | Pre-orders, LOIs, paid pilots |
| Evidence | Verbatim phrasings, behavioral patterns | Money, signatures, demos booked |
| Sample size | 10-15 buyers per segment | 3-5 commitments |
| Output | Defended buyer + problem | Behavioral commitments at proposed price |
| When to do it | First (before solution scoping) | Second (before MVP build) |
The two are sequential. Discovery without validation produces a precise problem statement and zero customers. Validation without discovery produces commitments to solve the wrong problem.
Common discovery mistakes
1. Pitching during discovery. The moment you describe your idea, the conversation contaminates. Apply the Mom Test discipline: never mention the idea, ask about past behavior.
2. Talking to friends. They’re polite; you don’t get signal. Talk to strangers, ex-colleagues, or people one LinkedIn-degree away.
3. Counting one good interview as discovery done. Patterns emerge around interview 10. Below that, you have anecdotes.
4. Skipping discovery because “I am the customer.” Founder-as-customer is a strong start AND a known bias. Run 10+ discovery interviews to test whether your problem is their problem.
5. Confusing discovery with validation. Interviews tell you the problem exists. They don’t tell you anyone will pay. Don’t ship V1 on discovery alone; run validation first.
How ShipFit operationalizes this
ShipFit maps the Blank phases to its 9 stages:
- Discovery → Stages 2-3 (Who Pays? + What Hurts?)
- Validation → Stages 6-7 (How to Charge? + Will They Pay?)
- Creation → Stage 8 (How to Launch?)
- Building → outside the validation playbook (engineering + ops post-PMF)
Stages 2-3 generate the Mom Test interview questions tuned to your buyer + hypothesis, then synthesize transcripts into the 3-4 most-cited verbatim pain phrasings + buyer sub-segments + bias checks. The output is a defended discovery deliverable that feeds directly into the validation stages.
Further reading
- Steve Blank, The Four Steps to the Epiphany (2005), the source.
- The Mom Test framework, the interview discipline that makes discovery work.
- Buyer Persona Canvas, what to do with the persona insights discovery surfaces.
- How to validate a business idea, the wider validation flow that follows discovery.
Related
The Mom Test
The Mom Test is Rob Fitzpatrick's framework for customer interviews that generate real signal. Not praise. Three rules, applied step-by-step, with examples.
Jobs to be Done (JTBD)
Jobs to be Done reframes every product decision: customers don't buy features, they hire products to get a job done. Here's how to apply it without faking it.
Buyer Persona Canvas
Buyer personas done properly. Adele Revella's research-based approach plus a one-page canvas. Why most personas are useless, and what makes the rare ones decision-grade.
Idea Validation
Most founders confuse idea validation with idea-receiving-encouragement. The two have nothing in common. Here's what real validation looks like, and the four methods that actually produce it.
Buyer Persona
A research-based archetype of a real buyer in a specific market segment, used to align product, pricing, and positioning decisions. Coined by Tony Zambito in 2002. Methodology formalized by Adele Revella in 'Buyer Personas' (Wiley, 2015).
Frequently asked questions
Who coined customer discovery?
What's the difference between customer discovery and customer validation?
How many customer-discovery interviews do I need?
Can I skip customer discovery if I'm the customer?
Is customer discovery still relevant in 2026?
Keep exploring
The 9-step playbook from market verdict to ship-ready spec.
The Mom Test is Rob Fitzpatrick's framework for customer interviews that generate real signal. Not praise. Three rules, applied step-by-step, with examples.
The Van Westendorp framework uses 4 questions to surface a defensible price range for any product. Here's how to run it, interpret results, and avoid the cheapest mistakes.
Most founders confuse idea validation with idea-receiving-encouragement. The two have nothing in common. Here's what real validation looks like, and the four methods that actually produce it.
Most founder market research is a TAM slide that nobody believes. The numbers that actually matter are smaller, harder to defend, and tell you whether the market exists for the ten-customer version of your business.
Does each customer make you money? Or cost you money?
Run nine framework-backed decisions in order before writing code: define the buyer, prove the pain is painful, name the winning angle, scope V1 to the smallest test of the hypothesis, get behavioral evidence (paid pre-orders, signed letters of intent, or credit cards on file from a Fake Door Test), then ship. Most failed startups skipped at least three of those nine. Plan to spend two to four weeks on this. It saves six to nine months of building the wrong thing.
For indie hackers who've wasted months on dead ideas. ShipFit forces 9 decisions before you write a line of code. Proven frameworks, exports to Cursor.
If you want a conversation partner, Buildpad. If you want to stop researching and ship, ShipFit. Both solve different problems for different founders. Don't pick on hype.
Ready to make your next product a success?
9 decisions between your idea and a product worth building.