In short: Post-decision interviews can show how a buyer evaluated options, but an interview should not replace the CRM outcome or stand in for market-wide evidence. Choose a deliberate mix of recent wins, losses, and no-decisions; ask neutral questions about the decision sequence; preserve what the buyer actually said; and treat repeated themes as hypotheses to test.
A CRM loss reason such as “price” or “competitor” is a useful starting point, not a complete account of the decision. It may reflect what the rep heard, what the buyer chose to share, or the field that was easiest to select. A short interview can add context, but one person’s account cannot explain every deal in a segment.
1. Set a narrow research question
Choose one decision the interviews should inform. For example: “What evidence helps operations leaders trust a new provider?” or “Why do qualified prospects pause after comparing implementation options?” A broad question such as “Why do we win or lose?” can produce a long list that no team can act on.
Define the cohort before inviting anyone: deal outcome, product or service, market, approximate decision period, and any relevant source or stage. Keep no-decision cases distinct from losses to a named competitor. The no-decision outcome guide covers how to record that CRM outcome without assigning the cause to a marketing channel.
2. Select cases deliberately and track who responds
Include recent closed-won, closed-lost, and no-decision deals when they fit the question. Sample across the differences that may shape a buying decision, such as company size, service need, sales stage, or acquisition source. For a multi-person purchase, invite someone who took part in the evaluation as well as the final approver when that is practical; people in the same buying group may have seen different parts of the process. See the guide to buying-group progress for a related account view.
Do not recruit only the easiest customers to reach or the deals a sales team most wants to explain. Keep a simple record of eligible cases, invitations, replies, and completed interviews. This makes non-response visible and prevents the interview set from looking more representative than it is.
3. Reconstruct the decision in the buyer’s words
Prepare a short discussion guide with open, neutral questions and follow-ups. GOV.UK recommends deciding which topics to cover, writing starter and follow-up questions, and testing the guide with a colleague. Keep the sequence flexible enough to follow a useful example and clarify what the buyer meant. See the GOV.UK guide to in-depth interviews.
Start with the sequence rather than the presumed reason:
- What first made this issue a priority?
- What did you do before speaking with our team?
- Which alternatives did you consider, including keeping the current approach?
- Who became involved, and what did each person need to understand?
- What criteria mattered at the start, and what changed during the evaluation?
- Which moment or piece of evidence most affected the final decision?
- If the decision was delayed, what would need to change before you reconsider?
Avoid leading prompts such as “Was price the problem?” Ask instead, “How did price enter the comparison?” If a buyer names a factor, ask for a specific moment or example. Do not use the interview to reopen the sale or turn a research request into a testimonial conversation.
4. Keep the interview separate from the interpretation
Record the participant’s role and the relevant deal cohort, then distinguish a direct statement from the interviewer’s interpretation. Preserve a short quote only when it helps the team understand the buyer’s meaning; a concise factual note may be enough for other observations.
You might code themes such as implementation risk, time to value, internal approval, fit, or price. These are categories to test against the interviews, not findings to assume in advance. Look for cases that contradict a theme as well as cases that support it. Compare the interview with the deal record, sales notes, and customer context, but do not overwrite those sources with one person’s retrospective explanation.
Treat the interviews as qualitative evidence. A repeated pattern can suggest what to examine in landing-page copy, qualification, sales materials, or the offer. The number of interviewees does not turn a selected interview sample into a market-wide estimate. Check a wider set of CRM records or run a measurable test before changing a broad strategy.
5. Turn a theme into a decision and a follow-up
For each repeated theme, write down:
- the buyer group and deal cohort where it appeared
- the evidence and any contrary examples
- the page, campaign, offer, or sales step that could be affected
- the smallest change worth testing
- an owner, a review date, and the result that would change the decision
Keep the output tied to the question you set at the start. A theme about implementation confidence may support clearer process evidence on a service page; it does not automatically prove that every lost deal needs more technical content. The case-study review guide uses the same evidence discipline when evaluating public success claims.
6. Explain consent and protect interview data
Before the session, tell the participant who is doing the research, why, what notes or recordings you plan to make, who will see the findings, and how the information will be used. Ask for informed consent before taking notes or recording. Keep only the details needed for the research, store notes and recordings in an approved location, limit access, and remove them when they are no longer needed under your organization’s policy.
The GOV.UK consent guide and notes and recording guide set out these practices for government research. Apply the rules that govern your own organization and region; this article is a research-planning guide, not legal advice.
Win-loss interview worksheet
- Decision question: ______
- Eligible deal cohort and period: ______
- Won, lost, and no-decision cases included: ______
- Participant roles and recruitment gaps: ______
- Neutral prompts and follow-ups: ______
- Consent, notes, recording, access, and retention plan: ______
- Direct evidence separated from interpretation: ______
- Repeated theme and contradictory case: ______
- Smallest next test, owner, and review date: ______
Use interviews to learn how real buyers describe a decision. Keep the evidence, CRM label, and market-level conclusion separate so that one compelling story does not become a strategy by itself.
If buyer feedback and pipeline outcomes point in different directions, request a marketing diagnostic to review the message, qualification path, and CRM evidence together.
Sources and scope
- GOV.UK Service Manual: Using in-depth interviews — planning, discussion guides, open questions, and real examples.
- GOV.UK Service Manual: Getting informed consent for user research — consent information, evidence, and withdrawal.
- GOV.UK Service Manual: Managing user research data and participant privacy — data minimization, access, retention, and purpose.
- GOV.UK Service Manual: Taking notes and recording research sessions — consent before notes or recording and secure handling.
This is a qualitative research framework for B2B revenue teams. It does not prescribe a sample size or make interview findings a measure of market prevalence. Accessed October 9, 2026.
How did this article land?
Choose one reaction. You can change it anytime.