Customer Development
A hypothesis-driven process for searching for customers and a repeatable business model before scaling execution.
Download Markdown (.md)Soroush’s Product Wiki · https://wiki.soroush.uk/topic/customer-development/
01What it means
Customer Development is Steve Blank's process for testing assumptions about customers, problems, channels, revenue, and the wider business model outside the organization. Its four stages are customer discovery, customer validation, customer creation, and company building; the early stages deliberately iterate until evidence supports moving from search toward execution.[1][2]
- 01Customer discoveryTest problem, customer, value, and solution hypotheses
- 02Customer validationSeek repeatable evidence of adoption and purchase
- 03Customer creationBuild demand appropriate to the market type
- 04Company buildingScale organization and execution after evidence
- 05Revisit assumptionsPivot or refine when evidence contradicts the model
Customer development complements product development; conversations alone do not validate demand, and premature scaling magnifies untested assumptions.
02Why it matters
New ventures often treat an untested plan as a forecast and build or scale before confirming who will buy, why, and through which repeatable motion. Customer Development makes those beliefs explicit, gathers evidence from real customers, and delays costly execution until the business model has stronger support.
03When to use it
Use it when creating a new venture, entering an unfamiliar market, or testing a materially different business model. Apply the underlying search logic inside established organizations, but adapt governance and channels to their context. It is broader than interviewing and is not a substitute for product delivery, market sizing, or financial diligence.
04How it works
- Represent the proposed business model as explicit, testable hypotheses.
- Leave the building to investigate customer problems, contexts, buying behavior, and alternatives.
- Use experiments and early offers to test value, channels, revenue, and willingness to commit.
- Revise or replace unsupported hypotheses and repeat discovery rather than defending the original plan.
- Validate a repeatable, scalable model before increasing customer creation and organizational execution.
05A practical example
A team assumes independent clinics will buy scheduling software through self-service signup. Discovery shows that office managers feel the pain but owners control purchasing and require migration support. The team changes its customer, channel, onboarding, and pricing hypotheses, then validates them with paid pilots before hiring a large sales team.
06Where it breaks
Customer statements alone do not validate a business model, and early enthusiasts may not represent a scalable market. The framework originated in startup contexts and can oversimplify regulated procurement, multi-sided markets, public services, or long adoption cycles. Teams still need ethical research, sound experiments, and operational evidence.
Common mistakes
- Calling ordinary customer interviews Customer Development without testing the wider business model.
- Treating polite interest or feature requests as validation instead of seeking meaningful commitment.
- Scaling sales, marketing, or headcount before demonstrating a repeatable acquisition and revenue model.
07Sources
- Customer Development for Web StartupsSteve Blank · Framework creator guidanceCustomer Development for Web Startups
- Why the Lean Start-Up Changes EverythingHarvard Business Review · Creator-authored professional articleWhy the Lean Start-Up Changes Everything