Start with the problem, not the product presentation
A validation conversation should first establish whether the problem is important, current and costly enough to create action. If the discussion starts with a long presentation, the respondent may react politely without revealing the real priority. Ask about the existing process, alternatives, cost of inaction, decision criteria and timing before explaining the full solution.
Build a ladder of evidence
Signals have different strength. A page visit is weaker than a reply; a reply is weaker than a meeting; a meeting is weaker than a request for a calculation, sample or pilot; a paid or contractually meaningful next step is stronger again. Design validation as a progression. The purpose of each step is to reduce uncertainty enough to justify asking for the next commitment.
Conversations must represent the target segment
Ten conversations are not useful if they come from friendly partners while the target buyer is a different organisation. Define the target segment and roles before the outreach. In small B2B markets, representativeness means coverage of the important account types, use cases and roles rather than a large statistical sample. Keep a structured log of what changed in the hypothesis after each conversation.
A pilot is a commercial experiment
A pilot should reduce a specific business risk: willingness to pay, delivery capability, integration burden, usage quality or another uncertain condition. Define the cost, responsibilities, duration, expected outcome and decision rule. Free pilots can create weak signals if the buyer has no real commitment. Whenever possible, include a meaningful cost or operational involvement that proves seriousness.
Price should be tested earlier than feels comfortable
Teams often delay price discussions because they fear losing interest. But a market that likes the idea only at an uneconomic price is not validated demand. Test price ranges, commercial terms and the value logic while the hypothesis is still cheap to change. Strong objections are useful data because they reveal whether the problem, proof or economic frame needs redesign.
Rejections are high-value data
A structured loss reason is often more useful than a compliment. Record whether the barrier is urgency, fit, price, risk, regulation, timing, internal capability or access to the real decision-maker. Repeated rejection patterns can invalidate a segment or reveal a different offer. The purpose of validation is not to collect positive quotes; it is to discover the conditions under which a market will and will not move.
Practical case: separating polite interest from a moving market
A company receives strong responses to its introductory outreach, but almost nobody agrees to discuss a paid pilot or internal next step. The team could declare “high interest” and expand the budget. A stricter reading says the signal is still soft. It changes the offer, clarifies the commercial condition and asks for a concrete next commitment. The response rate falls, but the remaining conversations are far more valuable because they reveal actual buying intent.
30-day protocol
- Choose one segment and a concrete problem hypothesis.
- Build a list of 30–50 target accounts and the roles to reach.
- Run 15–30 structured conversations, recording problem, alternatives, price reaction and next-step willingness.
- Ask for a stronger commitment from the best-fit accounts: calculation, sample, pilot or commercial review.
- Write a scale / redesign / stop decision from the observed signals, not from activity volume.
Where validation creates false positives
- The sample contains partners, friends or low-authority contacts rather than target buyers.
- The team asks whether the product is “interesting” instead of testing a buying decision.
- Price and terms are hidden until late.
- Free pilots create engagement without commitment.
- The team counts every reply as demand and ignores repeated reasons for non-progression.
Signal strength
A useful signal ladder can move from awareness to response, meaningful conversation, explicit problem confirmation, price discussion, internal stakeholder involvement, pilot or proposal, and finally a commercial commitment. No level is universal, but the principle is stable: the more cost, effort or internal reputation the buyer is willing to invest, the stronger the evidence of demand.
Decision note
A strong analysis makes its assumptions visible, connects evidence to a decision and defines the next observation that can confirm, weaken or close the hypothesis.
The purpose of this note is not to make uncertainty disappear. It is to make the assumptions visible, connect them to a decision and define the next evidence step.