Win-loss analysis is a structured review of closed deals, won and lost, that finds out from buyers and from the deal record why each decision went the way it did. The goal is not a report but a change: one thing the team does differently on the next deal because of what the last ones showed.
This guide is for sales directors and account executives on complex deals, where a single loss can cost a quarter and the same mistake can repeat for years without anyone noticing. It includes a review template, buyer interview questions and a worked example.
Key takeaways
- In Clozd's analysis of buyer interviews, the closed-lost reason recorded in the CRM was wrong 85% of the time, according to the 2023 State of Win-Loss Analysis report.
- Clozd's 2025 State of Win-Loss report found that 39% of companies run an ongoing, cross-functional win-loss program, up from 30% the year before.
- In the same 2025 report, 63% of companies said win-loss analysis increased their win rate.
- A useful win-loss analysis combines the deal record, a buyer interview and a seller debrief, then codes one primary reason per deal.
- Win-loss analysis only pays off when each review ends with one specific change, an owner and a date.
What is win-loss analysis in sales?
Win-loss analysis looks at closed opportunities to understand why buyers chose you, chose someone else or chose to do nothing. It covers wins as well as losses, because a win you cannot explain is as hard to repeat as a loss you cannot explain.
It is different from tracking your win rate. The win rate tells you how many deals you close. Win-loss analysis tells you why, which is what you need to move the number. Our guide to sales win rate covers how to measure it; this one covers how to learn from it.
Why lessons from lost deals never get captured
A seven-month deal is lost on a Tuesday. The account executive is disappointed, logs “Price” in the CRM and moves on to the deals still open. Six months later, a different rep loses a similar deal the same way. Nobody connects the two.
The CRM field is the problem. A dropdown filled in by the seller, on the day of the loss, records the reason the seller believes or the one that is easiest to say. Clozd's research, published in the 2023 State of Win-Loss Analysis report with Pragmatic Institute, found that “the closed-lost reason listed in the CRM is wrong 85% of the time.” Keep in mind that Clozd sells win-loss services. Even so, any sales director who has read a buyer's account of a lost deal will recognize the gap.
The cost is not one deal. It is the same failed approach repeated across the team, because the lesson never left the head of the person who lost.
How to run a win-loss analysis in 7 steps
1. Choose which deals to review
Do not try to review everything. Pick deals above a value threshold, every loss to the same competitor, every “no decision” and a sample of wins. A steady rhythm of a few deals a month beats a big annual study.
2. Rebuild the deal record first
Before talking to anyone, collect the timeline: meetings, attendees, emails, documents sent, stage changes and close date changes. Memory fades within weeks. The record shows what actually happened, in what order.
3. Interview the buyer
The buyer interview is the heart of the analysis. Ask for 20 to 30 minutes, two to six weeks after the decision, and use open questions (see the question bank below). Someone other than the account executive should run it, so the buyer speaks freely.
4. Debrief the seller
Ask the account executive, and presales if they were involved, to walk through the deal. Where did they think it turned? Compare their view with the buyer's. The gap between the two is often the lesson.
5. Find the turning point
Complex deals are rarely lost at the end. Look for the moment the deal started to go one way: a stakeholder who joined late, a question that was never answered, a meeting that did not happen.
6. Code one primary reason
Use a short list of reasons (see the table below) and code one primary reason per deal, plus up to two contributing ones. Consistent coding is what lets you see patterns across 20 deals instead of 20 stories.
7. Change one thing, and check it
End each review with one change for the next deal, an owner and a date. Every quarter, look at the coded reasons together and check whether last quarter's changes moved anything.
Win-loss review template
Use this one-page template for each reviewed deal. Fill the first five sections before the meeting so the meeting is spent on decisions.
| Section | Questions to answer | Where the answer comes from |
|---|---|---|
| 1. Deal facts | Value, segment, cycle length, stage reached, outcome, competitor or status quo | CRM record |
| 2. The decision | Who made the final decision, when, and on what criteria? | Buyer interview, last emails, procurement notes |
| 3. The turning point | At which moment did the deal start to go our way, or away from us? | Deal timeline, call notes, buyer interview |
| 4. Buying committee | Who was involved, who did we never meet, who supported or blocked us? | Stakeholder map, meeting attendees, buyer interview |
| 5. The case for change | Did the buyer agree on the problem, its cost and why act now? Did the business case reach the CFO? | Discovery notes, business case, buyer interview |
| 6. What we did well | Which actions moved the deal forward, with evidence | Seller debrief, buyer interview |
| 7. What we would change | The one or two decisions we would make differently | Seller debrief, manager review |
| 8. Root cause and action | The coded reason (see the table below) and one change for the next deal, with an owner and a date | Review meeting |
Fill sections 1 to 5 before the review meeting, from the record and the buyer interview. Use the meeting for sections 6 to 8.
Win-loss interview questions
Keep the interview about the buyer's decision, not about defending your product. These eight questions cover what most reviews need.
| Topic | Question |
|---|---|
| Trigger | What made you start looking at this, and why at that moment? |
| Options | Which options did you consider, including doing nothing or building it yourselves? |
| Criteria | What mattered most in the final decision, and did that change during the process? |
| People | Who was involved in the decision, and who had the final word? |
| Turning point | Was there a moment when one option pulled ahead? What happened? |
| Our case | What did we do that helped you, and what made it harder to choose us? |
| Proof | Which evidence convinced your finance or leadership team, and what was missing? |
| Advice | If you were advising our team, what would you tell us to change? |
Ask for 20 to 30 minutes, two to six weeks after the decision. Someone other than the account executive should run the interview.
Common loss reasons in complex deals, and what to change
On complex deals, the coded reason is often upstream of what the buyer says last. “Price” and “timing” are frequent final answers; the root cause usually sits earlier in the cycle.
| Coded reason | What the buyer usually says | What to change on the next deal |
|---|---|---|
| No decision (status quo) | “We decided to wait” or “not a priority this year” | Quantify the cost of doing nothing in discovery; confirm why now before the proposal |
| Single-threaded | “The person you worked with left” or “leadership chose another direction” | Map the buying committee by the second meeting; meet the economic buyer before pricing |
| Weak business case | “We could not justify it internally” | Build the business case on the buyer's own figures and test it with the champion |
| Late procurement, security or legal | “The review took longer than planned” | Put procurement, security and legal on the mutual action plan from the start |
| Competitor better fit | “They understood our situation better” | Check discovery depth and the fit of your references to this buyer |
| Price | “Too expensive” | Treat as a symptom first: price is often what buyers say when value was not proven |
Use one primary reason per deal, plus up to two contributing reasons. Code the reason after the buyer interview, not before.
If your reviews keep landing on deals that depend on one contact, or on business cases that do not survive the finance review, start with stakeholder mapping and with how you build the business case.
Example: a lost deal, reviewed
Here is what the template looks like on one deal. Helix Logistics, a fictional mid-size logistics company, chose to build in-house after a seven-month evaluation.
| Section | What the review found |
|---|---|
| Deal facts | Managed services contract, seven-month cycle, lost at contract stage to an internal build option |
| CRM loss reason | “Price” |
| The decision | The CFO decided, on total three-year cost, in a meeting the seller did not attend |
| The turning point | Month five: the CFO asked for a three-year comparison with the internal option. The business case compared vendors only |
| Buying committee | Strong relationship with Marta, the operations champion. The CFO and the IT director were never met directly |
| Root cause | Weak business case (primary), single-threaded (contributing) |
| Action | From next quarter, every deal above a set value includes the internal-build option in the business case. Owner: sales director. Review in 90 days |
Helix Logistics and Marta are fictional. The point of the example: the CRM said price, the evidence said the business case never answered the CFO's question.
Who should own win-loss analysis?
Ownership is split. Clozd's 2025 State of Win-Loss report found that 72% of win-loss programs are owned by go-to-market teams, split evenly between sales (36%) and marketing (36%). The report also found that ongoing, cross-functional programs see a positive ROI 85% of the time, against 55% for project-based programs.
For a complex-deal sales team, a practical split works well: product marketing or RevOps runs the interviews and the coding, and the sales director owns the review meeting and the changes. What matters most is that the reviews happen every month, not once a year.
Where an AI sales agent helps
The slowest part of a win-loss review is step two: rebuilding the deal from scattered emails, call notes and CRM history, weeks after the fact. An AI sales agent that keeps the full context of each deal makes that step fast, because the timeline already exists. It cannot replace the buyer interview. Only the buyer can tell you why they decided.
Cobl: learn from every deal before the next one slips
Cobl is the AI sales agent for complex deals. It keeps one record per deal, with the timeline of meetings, emails and documents, and you can ask what was promised and when, with every answer sourced. When you review a closed deal, you start from the evidence instead of from memory.
On open deals, Cobl qualifies on evidence and flags the gaps a win-loss review usually finds too late: a missing economic buyer, a single-threaded deal, a business case the CFO has not seen. It proposes the next move and prepares the work. You approve, Cobl does it, and nothing goes to the buyer without you.
Move a live deal forward. Try Cobl free for 15 days.
