The Customer Development Model: A Founder's Guide

Customer Development is Steve Blank's four-step framework for finding a repeatable business model before you scale: Customer Discovery, Customer Validation, Customer Creation, and Company Building. The first two steps search for product-market fit; the last two execute on it. The core discipline is to "get out of the building" and test your hypotheses against real customers.

Quick Answer: Customer Development runs in parallel to building your product. You Discover and Validate customers to search for a business model, then Create demand and Build the company to execute it — pivoting back a step whenever the evidence says your hypotheses were wrong.

Most founders can build a product. Far fewer can prove that anyone wants it, will pay for it, and can be reached repeatably enough to build a business. That gap is exactly what Steve Blank set out to close when he introduced the Customer Development model in The Four Steps to the Epiphany and later expanded it in The Startup Owner's Manual, co-written with Bob Dorf.

This guide walks through all four steps, the crucial difference between search and execution, and the mindset shift — getting out of the building — that makes the model work. It is a foundational piece in our complete guide to customer research for founders, and a good place to start before you run any single technique.

Why Product Development Fails at Finding Customers

Product development fails startups because it assumes you already know who your customer is and what they want, so it schedules building and shipping instead of learning. Blank's central observation was blunt: most startups die from a lack of customers, not a lack of product. Yet the traditional process optimizes only for the product.

A product-development or waterfall roadmap — concept, prototype, alpha, beta, launch — is a plan for execution. It works beautifully when the market, the customer, and the problem are already known quantities. Inside a startup, none of those are known. They are guesses.

Blank's framing is that a startup is not a smaller version of a large company. A large company executes a business model it already understands. A startup is a temporary organization searching for a business model it does not yet have. Running an execution playbook while you are still searching is how founders end up with a polished product and no market.

The Customer Development model exists as a parallel track to product development. While engineering builds, the founding team runs a separate, disciplined process to turn hypotheses about customers into facts. The two tracks feed each other; neither replaces the other.

Blank aims the same critique at the traditional business plan. A plan written before you have talked to customers is a stack of untested assumptions dressed up as facts, and, as the Customer Development Manifesto puts it, no business plan survives first contact with customers. The Startup Owner's Manual replaces that static document with a business model canvas — a scorecard of the handful of guesses your business depends on, kept visible so you can test and revise each one as the search produces evidence.

The purpose of the whole exercise is to move each of those guesses from opinion to fact before you spend money as if it were already true. A startup that treats its plan as a set of facts to execute, rather than hypotheses to test, is optimizing confidently in the wrong direction.

The table below contrasts the two mindsets. The takeaway: product development answers "can we build it?" while Customer Development answers "should we, and for whom?" — and a startup that skips the second question ships into a void.

The Four Steps of Customer Development at a Glance

The four steps are Customer Discovery, Customer Validation, Customer Creation, and Company Building, run in that order but revisited in loops. Steps one and two are the search for a business model; steps three and four are the execution of it once the search succeeds.

The single most important dividing line runs down the middle. Discovery and Validation are reversible, cheap, and iterative — you expect to loop back and revise. Creation and Company Building are where you commit capital and headcount — you only earn the right to enter them after the search has produced evidence.

The model is explicitly circular, not linear. If Customer Validation fails — nobody buys the way your hypotheses predicted — you do not push forward. You pivot back to Customer Discovery, revise your assumptions, and test again. That loop is the engine of the whole framework.

Here is the map before we walk each step in detail. Read the "you're done when" column as an exit test: you should not advance until you can honestly check it off.

Step 1: Customer Discovery — Test the Problem, Then the Solution

Customer Discovery turns the founders' vision into a set of testable hypotheses, then gets out of the building to check whether a problem customers care about actually exists — and whether your product solves it. Its output is not a sale; it is evidence of problem-solution fit.

In The Startup Owner's Manual, Blank breaks discovery into four phases: state your hypotheses, test the problem, test the solution, and verify — then pivot or proceed. Working them in order keeps you from the classic mistake of validating a product before you have confirmed anyone has the problem it solves.

Phase 1: State Your Business Model Hypotheses

The first phase writes down every guess your business depends on, so each one is explicit and falsifiable. You name the customer, the problem, the proposed solution, the channel you would sell through, and how you would price it — captured on a business model canvas rather than a narrative plan.

The value is discipline. Hypotheses you have written down can be proven wrong; convictions you carry in your head quietly bend the evidence to fit. This phase converts a fuzzy vision into a checklist of specific, testable claims.

Phase 2: Test the Problem With Real Customers

The second phase gets you out of the building to confirm the problem is real, painful, and worth solving — before you say a word about your product. You are testing demand for a solution, not pitching yours.

This is where the earlyvangelist matters — Blank's term for the ideal first customer. Earlyvangelists have the problem, know they have it, are actively looking for a fix, have often cobbled together a makeshift workaround, and have or can find budget. If you cannot find anyone who fits that profile, that absence is itself a critical finding.

Phase 3: Test the Product Solution

The third phase presents your solution — often a low-fidelity prototype or product concept — and watches whether it genuinely resonates with the customers whose problem you just validated. Only now does the conversation turn to what you are building.

You are looking for real signal: do earlyvangelists lean in, ask when they can have it, or offer to pay? Polite interest is not the same as pull, and this phase is where founders learn to tell them apart.

Phase 4: Verify — Pivot or Proceed

The final phase forces an honest decision: does the accumulated evidence support advancing to Customer Validation, or does it demand a pivot back to revised hypotheses? Discovery is iterative, so looping back is the expected outcome as often as moving forward.

When the data contradicts a hypothesis, you revise and go out again — you do not argue with the market. For a step-by-step breakdown of running these conversations, see our guide to the customer discovery process and its steps, which drills into how to structure interviews and read the signal.

Step 2: Customer Validation — Prove a Repeatable Sales Model

Customer Validation tests whether you can sell the product repeatably and predictably — building a sales roadmap that someone other than the founder could follow. Discovery proves people have the problem; validation proves they will actually buy your solution, in a pattern you can reproduce.

This is where hypotheses meet money. You attempt real sales to real earlyvangelists and watch what happens: Do they buy? At what price? Through what channel? With what objections? Each successful, repeatable sale is evidence that a business model — not just a product — exists.

Blank structures validation as its own sequence of phases that mirrors discovery:

• Get ready to sell — assemble the minimum you need to attempt real sales: a sales roadmap hypothesis, positioning, and the collateral to have a genuine commercial conversation.
• Get out of the building and sell — attempt to close earlyvangelists and treat every close, stall, and objection as data about whether the process repeats.
• Develop company and product positioning — sharpen how you describe who you are and what you sell based on what actually moved buyers.
• Verify — pivot or proceed — decide whether you have a proven, repeatable model worth scaling, or whether the evidence sends you back to Discovery.

Validation is also the moment of truth for the whole search. If you cannot build a repeatable sales process, you have not failed — you have learned. The model's answer is to pivot back into Customer Discovery, revise the hypotheses that reality broke, and re-run the loop.

Together, Customer Discovery and Customer Validation form the search cycle. You may traverse that Discovery-to-Validation loop several times before the pieces line up. Completing validation means you have found product-market fit and a proven way to sell — the green light, and only then, to start spending on scale.

Step 3: Customer Creation — Scale Demand for a Validated Product

Customer Creation shifts the company from search to execution: now that you can sell, you create and drive end-user demand at scale. This is the first step where Blank tells founders it is finally safe to spend aggressively on marketing and demand generation — because you are amplifying a model you have already proven.

Creation is not one-size-fits-all. Blank stresses that your strategy depends entirely on your market type, and getting the type wrong wastes the most money of any mistake in the model:

• Existing market — customers and competitors are known; you compete on better performance or features.
• New market — you are creating a category that did not exist; the challenge is educating customers that the problem and solution even exist, which takes time and patience.
• Resegmented market — you carve a slice of an existing market as either a low-cost or a niche play.
• Clone market — a proven model from another geography adapted to a new one.

Each type demands a different pace of spending, a different message, and different growth expectations. Launching a new-market product as if it were an existing-market one — pouring cash into demand that has to be educated first — burns runway fast. Agreeing on market type before you scale is one of the principles laid out in the Customer Development Manifesto and its core principles, which distills the mindset behind the whole model.

The mechanics of Creation follow the market type. In an existing market, you position against known competitors and drive demand into a category customers already understand, so spending can ramp quickly. In a new market, you invest first in customer education and adoption, accepting a slower curve because the category has to be built before it can be captured. The mistake the model guards against is spending at existing-market speed on a new-market problem — the fastest way to exhaust a round with nothing to show for it.

Step 4: Company Building — Transition From Startup to Company

Company Building is the transition from an informal, learning-driven startup into an organization structured to execute a proven model at scale. The founding team that was optimized for search — fluid roles, fast pivots, constant customer contact — reorganizes into functional departments built for repeatable execution.

In the search phase, titles are loose and everyone is learning. In Company Building, you deliberately create the operational structure a scaling business needs: dedicated sales, marketing, and business-development functions, along with the processes and mission-oriented culture to run them.

This is also a cultural transition, not only an org-chart one. The habits that made the startup effective at searching — improvisation, direct customer contact from everyone, comfort with being wrong — have to be preserved in the parts of the company still learning, even as other parts shift toward the repeatable execution a functional department is built for. Handled well, the company scales without losing the customer instinct that got it here; handled badly, it calcifies into process before the model is fully proven.

The key is timing, not just activity. Building formal departments before you have a validated model is premature scaling — you are pouring structure onto a business model you have not confirmed. Company Building is the right answer only once Discovery and Validation have done their job.

This step closes the arc. The company stops asking "what is our business model?" and starts asking "how do we execute it faster and larger?" That is the moment a startup graduates into a company.

Get Out of the Building in Practice

"Get out of the building" is Blank's shorthand for the model's non-negotiable habit: founders must talk to real customers directly, because the answers they need do not exist at their desks. As Blank puts it, there are no facts inside your building — only opinions — so you have to go outside to find them.

In practice, this discipline has a few defining features:

• Founders do it themselves. Customer contact is not outsourced to a research agency or a junior hire; the people making the decisions hear the evidence firsthand.
• You test, you don't pitch. The goal of an early conversation is to learn whether a problem is real, not to convince someone to like your idea. Seeking praise corrupts the data.
• You look for evidence, not validation. A founder hunting only for reasons to feel good will find them; a founder hunting for the truth will find the pivot they actually need.
• You turn opinions into facts. Every conversation should move a hypothesis from "we think" toward "we know" or "we were wrong."

The hardest part is emotional, not logistical. It is uncomfortable to hear that a beloved idea has no market, which is exactly why the model builds the habit into a repeatable process rather than a one-time survey.

This is also where a validation platform like Edmired earns its keep — giving founders a structured place to log hypotheses, capture what customers actually said, and see the evidence accumulate instead of relying on memory and optimism. The tool does not replace getting out of the building; it keeps the search honest.

Common Misreadings of the Customer Development Model

The most common misreading is treating Customer Development as a one-time research phase you finish before "real" work begins. It is not a phase — it is a parallel, iterative process that runs alongside product development from day one.

A handful of misinterpretations trip up founders repeatedly:

• "It's just customer interviews." Interviews are one tactic. The model spans problem testing, solution testing, repeatable selling, demand creation, and organizational design — far beyond a batch of calls.
• "It's linear." The framework is circular by design. Pivoting back a step when evidence contradicts a hypothesis is success working as intended, not a detour.
• "It replaces product development." It runs in parallel to it, not instead of it. You still build; you just stop assuming you already know for whom.
• "Ask customers what to build." Discovery surfaces problems worth solving, not feature requests to implement verbatim. Customers describe pain; founders design the solution.
• "Delegate it to a market-research firm." The model insists the founders themselves get out of the building, because the decision-makers must hear the market unmediated.
• "Scale as soon as the product works." Spending on Creation and Company Building before Validation confirms a repeatable sales model is the premature-scaling trap the model exists to prevent.

Read correctly, Customer Development is less a checklist and more a stance: stay in search mode, treating every plan as a hypothesis, until the evidence earns you the right to execute.

Key Takeaways

• Customer Development is a four-step search-then-execute framework — Customer Discovery, Customer Validation, Customer Creation, and Company Building — created by Steve Blank to find customers before scaling them.
• The search/execution split is the model's spine: Discovery and Validation search for a repeatable business model; Creation and Company Building execute it, and you only earn the second half by completing the first.
• A startup is not a smaller version of a large company — it searches for a business model rather than executing a known one, which is why traditional product-development plans fail founders.
• The Discovery-to-Validation loop is meant to be traversed more than once; pivoting back when evidence breaks a hypothesis is the process succeeding, not failing.
• "Get out of the building" is the operating principle — founders test hypotheses with real customers directly, because there are no facts inside the building, only opinions.
• Market type changes everything in Customer Creation — existing, new, resegmented, and clone markets each demand a different spending pace and message, and mismatching them wastes runway.
• Premature scaling is the failure the model guards against — building formal departments or driving demand before Validation confirms a repeatable sales model commits capital to an unproven business.

Frequently Asked Questions

What are the four steps of the customer development model?

The four steps are Customer Discovery, Customer Validation, Customer Creation, and Company Building. Discovery and Validation form the search for a repeatable business model; Creation and Company Building execute that model at scale. The order matters, and you loop back a step whenever customer evidence contradicts your hypotheses.

What is the difference between customer development and product development?

Product development assumes you already know your customer and builds on a fixed schedule — it is an execution process. Customer Development assumes the customer and problem are unproven hypotheses and tests them with real people. Blank designed the two to run in parallel, because most startups fail from missing customers, not a missing product.

What does "get out of the building" mean in customer development?

It means founders must leave their desks and talk to real customers directly, rather than reasoning about the market from inside the company. Blank's point is that there are no facts inside your building — only opinions — so the only way to turn hypotheses into facts is to test them with actual prospects, in person.

What is the difference between customer discovery and customer validation?

Customer Discovery tests whether a real problem exists and whether your product solves it — proving problem-solution fit. Customer Validation tests whether you can sell that product repeatably and predictably, building a proven sales roadmap. Discovery confirms people have the pain; Validation confirms they will actually pay for your cure in a repeatable pattern.

Is the customer development model the same as the lean startup?

No, but they are closely related. Customer Development is Steve Blank's framework; the Lean Startup, popularized by Eric Ries, built on it by combining Customer Development with agile development and the business model canvas around a build-measure-learn loop. The Startup Owner's Manual folds many of these lean ideas back into Blank's original four-step process.