Customer Development: no business plan survives first contact with customers
Steve Blank's four steps as he actually sequenced them — why validation means selling, not surveying, and why hiring a sales team is deliberately the last step, not the first.
The theory in one paragraph
Blank's founding claim is that a startup is not a small version of a large company — it's a temporary organization searching for a repeatable, scalable business model. Large companies execute known models; startups don't have one yet, so borrowing big-company behavior (business plans, product roadmaps, sales headcount) means executing a guess. Customer Development replaces execution with search: four gated steps — discovery, validation, creation, company building — where nothing about the model is treated as fact until customers, met face to face, have confirmed it with behavior and money.
How it works
The mechanics — as Steve Blank defined them, not the folklore version.
Search: discovery and validation
Customer discovery turns your business plan into a stack of hypotheses and tests the core ones — problem, customer, product — through direct conversation. Customer validation raises the bar from words to money: can you build a repeatable sales roadmap and close early orders yourself? These two steps loop; failure here sends you back to discovery with a pivot, cheaply.
Execute: creation and company building
Customer creation is when you finally spend on demand generation — and how you spend depends on whether you're in an existing market, resegmenting one, or creating a new one. Company building converts the informal, learning-oriented team into departments with missions. The sequence is the discipline: sales and marketing headcount arrives after the model is proven, because scaling an unvalidated model just makes the failure more expensive.
Get out of the building
Blank's most quoted instruction is also his most operational: facts live outside the office, and no amount of internal debate substitutes for them. Founders themselves — not hired researchers, not a survey link — do the interviews, because the goal isn't data collection, it's founders updating their own mental model fast enough to steer. You're not pitching in these conversations; you're hunting for the moment a customer describes the problem better than you can.
Validation means a purchase order, not a compliment
The step most teams fake is validation. Blank's bar is uncomfortably concrete: earlyvangelists — customers with the problem, who know they have it, who've cobbled together their own fix, and who have budget — paying real money for an unfinished product. Interviews full of 'I'd definitely use that' pass discovery and prove nothing more; people are polite for free. The reason the founder does the first sales personally isn't thrift — it's that every objection heard firsthand is a business-model fact you can't get from a pipeline report.
The person behind it
Steve Blank
8-time Silicon Valley entrepreneur · adjunct professor at Stanford
Blank spent 21 years inside eight startups — semiconductors, supercomputers, enterprise software — before retiring and asking why some of them worked. The Four Steps to the Epiphany, self-published from his teaching notes, became the founding text of modern entrepreneurship; Eric Ries took Blank's Berkeley class as a condition of Blank's investment in IMVU, and turned the ideas into the Lean Startup.
Lineage — Spawned the Lean Startup movement — Ries built the Build–Measure–Learn loop on these four steps →
How to apply it this week
Each step maps to a field in the Assumptions Tracker tool — finishing the read means finishing the work.
Turn your plan into explicit assumptions
Write every belief as a falsifiable statement: 'Riyadh clinic owners lose 5+ hours a week to no-shows', not 'the market needs this'. If it can't be proven wrong, it can't be validated either — rewrite it until it can.
Assumptions Tracker · list every assumptionRank them by kill potential
Sort by one question: if this is false, is the company dead? Problem and willingness-to-pay assumptions almost always outrank technical ones. Test from the top — most founders test from the bottom because it's more comfortable.
Assumptions Tracker · riskiest assumptionGet out of the building — interviews, not pitches
Ten to fifteen conversations per assumption, founders in the room, product demos banned until the problem is confirmed. Ask about the last time they hit the problem and what they did next; the workaround they built is worth more than any opinion they offer.
Validate with money, not sentiment
Move earlyvangelists from agreeing to buying: a signed LOI, a prepayment, a paid pilot. Log each result against the assumption it tests — the pattern across ten conversations is the finding, not the one enthusiastic quote you remember.
Assumptions Tracker · evidence + verdictHold the gate before you scale
Only when sales are repeatable — you can predict who buys, why, and at what cost — do you enter creation and company building. If the evidence says otherwise, pivot and re-enter discovery. That loop is the method working, not the method failing.
Feeds your Readiness Score · Plan
Build it, don't just read it
The steps above are the Assumptions Tracker tool's structure. Open it and work through them with your own startup — your readiness score starts building from the first field.
Free account · no card required
See it in the wild
Teardowns from our benchmarks library where this framework is doing real work.
Benchmark teardown
Airbnb
The founders flew to New York and stayed with their own hosts — discovery done so literally it found the fix (better photos)
Read the teardown
Benchmark teardown
Careem
Started as a corporate car-booking service, then followed what customers actually did into consumer ride-hailing
Read the teardown
Frequently asked questions
What are the four steps of customer development?
Customer discovery (test your problem and customer hypotheses through direct interviews), customer validation (prove a repeatable sales process by getting early customers to pay), customer creation (spend on demand generation once the model works), and company building (convert the learning team into a scaling organization). The first two are a search loop you may repeat several times; the last two are execution and come only after validation.
What does 'get out of the building' mean in customer development?
It's Steve Blank's instruction that facts about your business model exist only outside your office — so founders must personally leave and talk to real customers rather than debating internally, running surveys, or delegating research. The point isn't collecting data; it's the founders updating their own assumptions fast enough to change course while it's still cheap.
What is the difference between customer discovery and customer validation?
Discovery tests whether the problem is real and who has it — its currency is interviews and observed behavior. Validation tests whether people will pay and whether the sale is repeatable — its currency is money: prepayments, signed orders, paid pilots. Teams commonly stop after discovery, but polite interest validates nothing; Blank's bar for validation is a purchase, not a compliment.
How is customer development different from the Lean Startup?
Customer Development is the parent: Blank published the four-step search framework in 2005, and Eric Ries — who took Blank's class as a condition of his investment in IMVU — built the Lean Startup on top of it, adding the Build–Measure–Learn loop, MVPs, and innovation accounting. Use them together: customer development tells you what to learn from the market, lean startup gives you the experimental engine to learn it.
Why did Steve Blank say no business plan survives first contact with customers?
Because a business plan is a stack of untested guesses formatted to look like facts — and the first real customer conversations reliably break several of them. Blank's paraphrase of the military maxim argues that since the plan will change anyway, the winning move is to treat it as hypotheses and test them deliberately, rather than executing a fiction until the money runs out.
Related frameworks
The Lean Startup
Eric Ries · 2011
Lean Canvas
Ash Maurya · 2010
Jobs to be Done
Clayton Christensen · 2003
Sources
Independent educational summary written by StartupKit from public sources. Customer Development is the work of Steve Blank; this page is not affiliated with or endorsed by the author.