Win-loss interviews: how to understand why a deal was won or lost
Analyze a win-loss interview to reconstruct the buyer’s decision, criteria, alternatives, turning points and evidence. Includes a table and example.
A deal rarely comes down to one CRM field
“Lost on price” may be true, but it can conceal a sequence of events: implementation risk, unclear value, a restriction discovered late, or an internal approval. A win-loss interview restores the buyer’s timeline.
One interview doesn’t establish a market pattern. It identifies episodes and hypotheses you can compare with other cases. Don’t turn an emotional quote into a percentage or rank a cause as primary without comparison rules.
Reconstruct the decision through events
Separate the outcome from its explanation
Record the outcome, amount and stage using authorized sources only. Then record the seller’s and buyer’s explanations separately. Ask open questions without suggesting an answer.
Build the decision timeline
Find the trigger, alternatives, criteria, decision participants and turning points. Keep timestamps for the passages on which each conclusion rests.
Mark the strength of the evidence
A direct statement about a specific event carries more weight than an analyst’s general impression. If you infer a cause from several remarks, label it as an interpretation and show what supports it.
Compare cases using the same fields
Use one table for won and lost deals. If you update categories, log the changes so the frequencies remain comparable across interviews.
A fictional company’s lost deal
This is a fictional training example. The names, circumstances and outcomes are included solely to explain the method.
The price was higher, but what changed our minds was the demo. We didn’t see how to move the archive without stopping work. The competitor had a clear migration plan.
Recording only “too expensive” would miss the buyer’s stated turning point and the criterion for reducing risk. Price still mattered, but the final decision depended on whether the migration path was clear.
In the table, keep these separate: mentioned factor — price; turning point — demo; criterion — archive migration without downtime; alternative — a vendor with a plan. The scenario is fictional.
| Field | Interview excerpt | What it shows |
|---|---|---|
| Initial task | Move the archive without downtime | Continuity matters |
| Criteria | Price and clarity of the migration | Several criteria mattered |
| Turning point | The demo didn’t reduce the risk | Uncertainty increased |
| Outcome | Chose the vendor with a plan | The implementation path decided the deal |
Win-loss interview worksheet
Fill it out the same way after each interview and keep links to the evidence.
Deal and outcome: Who took part in the choice: What triggered the search: Alternatives considered: Comparison criteria: Turning points: What built trust: What increased risk: Direct reason in the buyer’s words: Analyst’s interpretation: Timestamps and quotes: Open questions to check: Possible action for the team:
Check that the report reflects what happened
- The reason is linked to a particular event or criterion.
- Quotes are separate from interpretations.
- Won and lost deals use the same fields.
- One conversation isn’t presented as market statistics.
A closer look
Who should we interview?
Speak to someone who took part in the choice or knows how it unfolded. Your main contact can offer useful insight, but can’t speak for everyone involved.
Can we combine win-loss interviews and satisfaction surveys?
They serve different purposes. Win-loss reconstructs a particular vendor choice. A satisfaction survey evaluates the experience after purchase.