How to Analyse Lost Deals and Improve the Next Conversation
For sales leaders and teams: learn how to separate buyer feedback from assumptions, document what a lost deal can—and cannot—tell you, and choose one change to test in the next relevant conversation.
On this page
“We lost on price” may be accurate. But on its own, it is a label, not an explanation. Was the buyer comparing similar offers? Was budget the obstacle, or did the offer seem too risky for the price? Did they choose another provider, or decide not to act?
A useful loss review separates what the buyer reported, what the deal record supports, what the team infers and what remains unknown. Its purpose is not to prove why every deal was lost. It is to choose one defensible change to test in the next relevant conversation.
Separate the loss label from the evidence#
Start with the outcome and date. Gather the relevant opportunity notes and any buyer feedback you are permitted to use. Keep the source attached to each detail: a buyer’s comment, a dated proposal, a seller’s meeting note or a CRM reason code.
Sort what you find into three categories:
- Reported or observed: what the buyer said, or what a dated record shows.
- Inferred: what the team thinks those details may mean.
- Unknown: what the available evidence cannot establish.
For example, a CRM record says “lost on price”. The buyer’s email says the proposed fee exceeded the approved budget. That supports the narrower conclusion that the fee did not fit the budget described. It does not show whether the buyer considered the offer poor value, whether a different scope would have worked, or whether budget was the only factor.
Buyer feedback offers a perspective, not infallible proof of causation. Internal notes can help reconstruct the sequence, but they do not establish what the buyer was thinking. Win-loss guidance recommends gathering buyer feedback, looking for recurring themes and using them to inform action; that is a practical approach, not evidence that a particular review process will increase win rates. (SurveyMonkey, “Win-loss analysis: a framework any team can run”)
Make a useful review from the records you have#
Ask the buyer for feedback where appropriate, but do not make it a prerequisite for documenting what the team does and does not know. A compact review can capture:
| Record | What to include |
|---|---|
| Outcome and date | Closed-lost, no decision, stalled or still open. |
| Buyer’s stated reason | Their words or a faithful paraphrase, with its source; write “no buyer feedback” if there is none. |
| Supporting evidence | Relevant dated notes, proposals, decision changes or agreed next steps. |
| Alternatives considered | An incumbent, another provider, doing nothing, or any other option known to have been considered. |
| Inference and unknowns | What the team suspects, and what the evidence cannot establish. |
| Next test | One question or piece of proof to try in a relevant future conversation, with an owner and review date. |
Illustrative example: A provider loses a project to an incumbent consultancy. The buyer reports that the incumbent already understands the organisation; the proposal and meeting notes show concerns about transition time. The team may infer that continuity mattered. But if the buyer did not compare costs or explain the final decision, the review should not claim to know how much each factor contributed.
One loss can suggest a question to test. It cannot establish a market-wide pattern or prove why the deal was lost.
Turn the review into a better next conversation#
The review is useful when it changes a relevant question or decision—not when it simply adds another CRM note. For the next similar opportunity:
- Prepare from what is known. Summarise the buyer’s situation and relevant deal evidence. Mark assumptions plainly; reconstructed context is not verified buyer evidence.
- Decide what you need to learn. Is the conversation about the problem, fit, decision-making or whether further work is worthwhile?
- Explore the buyer’s alternatives. Ask for a recent example, its consequences and what the buyer has already tried. Include doing nothing if it is a real option.
- Match proof to a stated concern. Explain what a case example, demonstration or proposed method does—and does not—show.
- Agree the next step. Clarify who can approve scope, price and implementation, then record the action both sides have agreed.
In the illustrative case, the team might ask a future buyer: “What would need to stay continuous if you changed provider?” That tests whether transition risk matters in a new opportunity. It does not prove continuity caused the earlier loss.
This is a practical method for preparing a conversation, not a validated instrument. It cannot identify a single cause with certainty or guarantee a better commercial result.
Review the action without claiming it caused a win#
Set a review date when you choose the change. Check whether the question or proof was used, what buyers said and whether the original assumption still holds. Keep contrary examples. If a theme recurs, check whether the deals are comparable before changing the offer or sales process.
Keep closed-lost separate from no decision, stalled and open opportunities. A buyer who chose an alternative is in a different situation from one who postponed a decision.
Start with one lost deal. Record the buyer’s stated reason and its source, the supporting evidence, your inference and what remains unknown. Then choose one question or piece of proof to test in the next relevant conversation, and name an owner and review date.
For further information, see Meeting & Sales Performance.
