THE SHORT ANSWER

Win-loss interviews explain how a particular buying decision developed. They are neither a satisfaction survey nor a delayed attempt to sell. Comparing successful, lost and deferred cases carefully can reveal where your offer fits, where the buying process becomes difficult and which internal explanations remain unsupported. Keep the investigation focused on learning that can change a decision.

To connect this decision with positioning, market entry and growth, read the pillar guide Go-to-market for B2B SaaS: turn market insight into an executable growth strategy.

Choose a bounded learning question

Before inviting participants, decide which business choice the investigation should improve. Are you examining one segment, recurring price concerns or difficulty demonstrating implementation feasibility? A narrower question makes case selection easier. Do not include only obvious successes or especially painful losses. Include decisions against buying anything and cases where internal assessments differed from the customer’s view. Document selection and omissions. This is qualitative research with limits to generalisation, not an automatic vote on the next feature to build. The selection should let you explore an explanation rather than merely collect supportive stories. Explore this further in the guide Competitive research beyond feature collection.

Separate the interview from the sale

Explain the purpose, treatment of comments and voluntary nature of participation. Where possible, use an interviewer who was not responsible for closing the deal. This creates room for criticism without guaranteeing complete candour. Avoid defending the team or offering to reopen the decision. GOV.UK guidance recommends open, neutral questions and concrete experiences in in-depth interviews. Apply that principle to understand the participant’s perspective. Establish their role as well: a user may know the workflow thoroughly while knowing little about final budget approval or every internal trade-off made by the purchasing group.

Topic overview: Choose a bounded learning question; Separate the interview from the sale; Reconstruct what actually happened
Topic overview for this article. Topic overview: Choose a bounded learning question; Separate the interview from the sale; Reconstruct what actually happened

Reconstruct what actually happened

Start before supplier research. What changed, which alternatives were possible and who became involved when? Then ask about concrete comparison moments: which document circulated internally, what remained unanswered and what changed someone’s assessment? Explore the decisive difference between final options without supplying the answer yourself. Preserve contradictions and uncertainty. “Too expensive” requires context: was total expenditure unaffordable, value unclear or another offer more appropriately bounded? These explanations imply different actions. Do not collapse them into one convenient category simply because a reporting field accepts only a short label for the reason a deal was lost.

Hypothetical example: a loss attributed to price

A fictional supplier loses a contract and records “price” in its CRM. During the interview, the buying organisation explains that ongoing costs were similar across the two final offers. The decisive issue was uncertainty about data migration, which nobody wanted to own internally. The supplier revises its interpretation: implementation uncertainty, rather than automatically the list price, drove this decision. It examines migration guidance and responsibilities. This case does not prove a general cause of other losses. It produces a targeted hypothesis to check against further decisions and the service the supplier can actually deliver.

Three aspects: Reconstruct what actually happened; Hypothetical example: a loss attributed to price; Test patterns against counterexamples
Editorial overview of the content. Three aspects: Reconstruct what actually happened; Hypothetical example: a loss attributed to price; Test patterns against counterexamples

Test patterns against counterexamples

Summarise each case before comparing similar circumstances. Separate direct statements, reported sequences and your conclusions. Deliberately seek successful cases where the same supposed barrier was present. Perhaps the barrier mattered only under particular conditions. Avoid percentages drawn from small, selectively recruited interview groups. A concise pattern record can instead show which explanations recur, which counterexamples exist and what remains unknown. Review findings with sales, product marketing and customer success. Avoid using a research discussion to blame individual employees for complex organisational buying decisions, because that makes honest interpretation harder and encourages defensive explanations.

Agree changes and a subsequent check

Translate findings into a few testable adjustments. A frequently unresolved integration question may call for improved qualification or an earlier technical discussion. A requirement you cannot deliver belongs in a product decision or an explicit exclusion rule. Assign an owner, desired change and review point. Communicate updates to interview participants only where that communication was agreed. Win-loss work becomes useful when it corrects assumptions and changes behaviour. A report full of quotations without owned consequences can create an appearance of customer understanding while doing little to improve the decisions people make in everyday commercial work. Explore this further in the guide B2B buyer research: use customer interviews to make better market decisions.

INTERACTIVE / FROM READING TO ACTION

Three checkpoints for your implementation

Choose a checkpoint and track your reading progress. Checks are neither saved nor sent and do not score your business.

CHECKPOINT 01

Reconstruct what actually happened

Start before supplier research.

Explore in the article ↗

CHECKPOINT 02

Hypothetical example: a loss attributed to price

A fictional supplier loses a contract and records “price” in its CRM.

Explore in the article ↗

CHECKPOINT 03

Test patterns against counterexamples

Summarise each case before comparing similar circumstances.

Explore in the article ↗
0 / 3 reviewed

Frequently asked questions

Who should interview?

Prefer someone without responsibility for the sale who understands the context and can ask neutral follow-up questions.

How should we interpret “too expensive”?

Investigate comparisons, budget, expected value and total effort. The phrase alone does not explain the cause.

Can we quantify findings?

Only with an appropriate data foundation. Small qualitative samples are better for patterns and hypotheses than reliable market proportions.

How can I put “Choose a bounded learning question” into practice?

Before inviting participants, decide which business choice the investigation should improve. Are you examining one segment, recurring price concerns or difficulty demonstrating implementation feasibility? A narrower question makes case selection easier.

What matters when working on “Separate the interview from the sale”?

Explain the purpose, treatment of comments and voluntary nature of participation. Where possible, use an interviewer who was not responsible for closing the deal. This creates room for criticism without guaranteeing complete candour.

Sources & further documentation