Customer validation is the step where a founder moves beyond discovery and tests whether real customers will act on the problem, the offer and the buying decision. The goal is not to collect more positive feedback. It is to learn whether the behaviour repeats strongly enough to justify the next build, sales or scaling decision.
Customer validation can strengthen or weaken a customer, offer or buying hypothesis. Interviews, demos, pilots, signups and even one payment each answer a narrower question. None of them alone establishes product-market fit, retention, repeatable acquisition, scalable delivery or long-term economics.
Confirm the recent problem, current workaround, consequence and buyer role before asking whether your solution sounds useful.
Evidence: Repeated descriptions of the same real problem and workaround from people who fit a specific customer profile.
Does not establish: Problem evidence does not establish demand for your proposed solution.
Put a bounded offer, prototype, manual service or pilot proposition in front of the customer so they have something specific to accept, reject or reshape.
Evidence: Questions about fit, constraints, timing, implementation, price or the decision process that arise around a concrete offer.
Does not establish: Feedback on a concept or prototype is not payment and does not establish repeated use.
Record what the customer actually did: returned, shared data, involved another stakeholder, accepted a dated next step, entered procurement or took another observable action.
Evidence: Behaviour that costs attention, effort, reputation, access or internal coordination and therefore carries more weight than a compliment.
Does not establish: The strength of the signal depends on what was at stake; the A-03 rubric interprets that separately.
Make price, commercial terms or another meaningful economic consequence real enough that the customer can say yes, no or not yet.
Evidence: A paid pilot, deposit, accepted commercial terms, signed order, formal procurement step or another consequential buying action.
Does not establish: A promise to pay is not payment, and one payment does not establish repeatable demand or lifetime value.
Repeat the test with comparable customers and record which problem, buyer, trigger, objections, buying steps and commitments recur.
Evidence: A pattern across comparable customers that is similar enough to inform the next sales and product decision.
Does not establish: A repeated early buying pattern still does not establish retention, scalable acquisition or scalable delivery.
Before collecting more feedback, state what the evidence would make you build, narrow, change, test again, pause or stop.
Evidence: A decision rule that changes when the evidence changes instead of accumulating interviews indefinitely.
Does not establish: There is no universal interview count, conversion threshold or fixed duration that completes customer validation.
Run evidence-producing buyer interviews: Use the worksheet for past behaviour, workarounds, consequences, buying roles and a real next action.
Interpret the evidence you already hold: Use the existing A-03 Politeness → Interest → Intent → Commitment rubric and the six-action retrospective re-read.
Choose the validation method: Compare the seven evidence method families when you need to decide how to run the next test.
GTM Right Stage 1 checks public evidence for the problem and current workaround. It does not read or authenticate your interview notes, prove willingness to pay, or establish a repeatable sales process.