Validate the market

Market validation is the process of gathering evidence that a specific, reachable group of customers will choose your offer under realistic conditions. It investigates who needs the offer, what they will commit to, how you can reach them, and whether the opportunity deserves further investment.

Someone agreeing that an idea sounds useful is a starting point. A customer spending time, changing a workflow, or paying for a clearly described offer provides evidence about a different question. Decide which question matters before choosing a test.

Use the experiment cards in this playbook to investigate demand. The guide below explains how to choose among them and turn the result into a decision.

What evidence are you looking for?

Separate the claims hidden inside “there is a market.” A large industry, a busy landing page, and a paid pilot do not establish the same thing.

For a purchase question, a payment is more direct evidence than a compliment. For a question about the customer’s problem, a detailed interview may be more informative than a payment count. Match the evidence to the claim.

Use total addressable market to reason about the size of an opportunity. A market-size estimate does not show that customers will choose your particular value proposition.

How to make a market validation plan

1. Define the customer and buyer. Describe the situation, the problem and the eligibility criteria. In a business purchase, the user, budget holder and approver may be different people.
2. Investigate current behavior. Ask about a recent occurrence, the workaround, its cost and the buying process. Use customer interviews to discover what needs investigating rather than asking people to endorse your idea.
3. Describe a specific offer. State what the customer gets, the price, the delivery conditions and the action you are asking them to take. Keep the offer consistent enough to interpret the result.
4. Choose a consequential assumption. Identify what would change your investment decision. “People want this” is too vague; “eligible studio owners will pay for this pilot through this outreach channel” can be investigated.
5. Specify the test and decision before running it. Record the audience, procedure, measure, timebox, cost limit and what would make you continue, revise or stop.
6. Record the result and its limits. Include the denominator, recruitment source, price, conditions, assistance and dropouts. Decide what remains uncertain before funding the next step.

Alex Osterwalder’s Test Card makes the assumption, test, measure and success criterion explicit. Our experiment sheet is a practical place to record your own plan. A threshold is a decision rule for that plan, not a universal definition of a validated market.

Which market validation method should you use?

These methods can complement one another. Choose the next one because it resolves an important uncertainty, rather than following a fixed interview-to-prototype-to-launch sequence.

Market validation example: an invoice-reminder service

This scenario, price, counts and threshold are illustrative. They are not results from a real business or recommended conversion benchmarks.

A team is considering an invoice-reminder service for independent yoga studios that invoice companies for staff classes. Its proposed customer is a studio owner who currently follows up overdue corporate invoices manually. The team first investigates recent late payments and how owners handle them.

Instead of building an integration, it offers a two-week, manually delivered reminder pilot for $49. The customer approves the reminders before they are sent. The team plans to present the same offer to 20 additional eligible owners through direct outreach.

Two purchases establish that two people bought this offer under these conditions. The six requests for information are a separate signal. Combining them into “eight interested customers” would obscure the payment question.

The small, deliberately recruited group does not establish a population conversion rate. Even reaching the threshold would leave repeat use, acquisition costs, service costs and a larger market unresolved. Record the delivery effort and ask whether the customers return before extrapolating.

The next investigation might reveal that the price, timing, scope or buying process prevented a purchase. Those are competing explanations to investigate, not findings to invent after a disappointing result.

Market validation vs. product validation and market research

Research informs the hypotheses; experiments investigate specific claims. The work overlaps, but a market report cannot substitute for evidence about the offer. A usable product also needs customers who can find it and choose to adopt it.

The Lean Startup methodology connects product experiments to repeated learning and investment decisions. Use the product validation playbook for solution questions and product experimentation to connect the tests.

How to decide what happens next

Continue when the evidence supports the next bounded investment, while recording the risks it has not addressed. Revise when the result exposes a plausible problem with the segment, offer, channel or test. Stop or change direction when a critical assumption keeps failing and further investigation is unlikely to justify the cost.

Keep observations separate from explanations. Record what each buyer did, what you think caused it and what you will investigate next. The learning sheet helps preserve that distinction.

Avoid choosing a success threshold after seeing the result, recruiting only supportive friends, mixing different offers into one conversion count, or ignoring customers who disappear. A single positive experiment is evidence for a particular decision, not permanent certification that the whole market is validated.

Common questions about market validation

Do I need a finished product?

No. Interviews, clear offers, prototypes and manually delivered services can investigate important assumptions before a finished product exists. Represent the offer and its delivery conditions accurately, and choose the method that can answer the question.

How many customers are enough?

There is no universal count. A few conversations can expose a misunderstanding; estimating a conversion rate or comparing alternatives reliably needs a suitable sampling and analysis plan. Match the evidence to the decision and the cost of being wrong.

How long should market validation take?

Timebox each investigation around the customer’s buying cycle and the decision you need to make. A two-week test is an example, not a rule for enterprise procurement, repeat use or seasonal demand.

Use the Validation Patterns overview to revisit the next uncertainty. Problem validation examines the underlying need, product validation examines whether the experience helps, and willingness-to-pay testing examines the price and terms of a purchase. These questions overlap; none is a universal launch approval.