Customers & Markets
The Step-by-Step Guide for Building a Great Company
The detailed field manual for Customer Development: how to test your business model with real customers before you scale.
The big idea
Blank and Dorf argue that a startup is not a small version of a big company. A big company executes a known business model; a startup is searching for one. Treating guesses as facts and spending against a business plan is how most new ventures fail. Their Customer Development process turns each part of the business model into a hypothesis, then tests those hypotheses through direct contact with customers, moving to scaling only after a repeatable way to find and sell customers has been proven.
Key takeaways
The answers to whether customers have the problem, will pay, and how they buy are not in your office or your spreadsheet. They are with prospective customers. The founders themselves should be doing these conversations, early and often, because they are the ones who can change the plan based on what they hear.
Large-company tools such as annual budgets, detailed hiring plans, and departmental targets assume the business model is known. Applying them during the search phase locks in assumptions that haven't been tested. Startups need different measures: how fast you are learning and validating the model, not how closely you are hitting a forecast.
The authors' term for early customers who have the problem, know they have it, are actively looking for a fix, have often built their own workaround, and can get budget to pay for it. These buyers will tolerate an unfinished product and help you shape it. Asking how someone handles the problem today quickly shows whether they qualify.
A minimum viable product is the smallest thing that lets you test a specific hypothesis with real customers. It might be a landing page, a mock-up, or a manually delivered service. The measure is how much you learn for the time and money spent, not how polished or complete it looks.
The book uses the Business Model Canvas, a one-page map of nine building blocks such as customer segments, value proposition, channels, and revenue streams, to replace the static business plan. Each box holds a hypothesis. As interviews and tests come back, the canvas changes. A canvas that never changes suggests you aren't testing much.
When testing shows a hypothesis is wrong, change it deliberately: a different customer segment, problem, channel, or pricing model, while keeping what has been validated. A pivot should come from data gathered in discovery, not from frustration or a hunch. Looping back to an earlier step is a normal part of the process.
The framework
Turn your vision into hypotheses and test the problem and proposed solution directly with prospective customers.
Prove you can sell repeatedly, building a sales roadmap that works. Loop back to discovery if it doesn't.
Once validated, invest in driving demand into the sales channel you have proven.
Shift from searching to executing, building departments and processes for the proven model.
“No business plan survives first contact with customers.”
— Steve Blank
Apply it this week
Read next
A method for building under uncertainty: test your riskiest assumptions with small experiments and let evidence decide what to build next.
A short, practical guide to customer conversations that produce facts instead of polite encouragement.
A systematic way to test a business model on one page, measure traction, and sell before you build.
This page is an original summary and commentary prepared by XRAYCLOUD.AI with AI assistance. It is not affiliated with or endorsed by the author or publisher, and it is no substitute for the book — read it for the full argument.