Win-Loss Analysis: How to Run One From Your Meeting Notes

The CRM said "Lost: price." Priya, a rep selling fleet telematics to regional trucking firms, had picked it from the dropdown on a Friday afternoon, three weeks after the decision. Then her manager asked for the notes from the four meetings. Price came up once, in passing. Installation downtime came up in three of them. (Priya is a composite, not a real rep.)

That gap between the reason you log and the reason you lost is what a win-loss analysis is for. You probably already sense it: the closed-lost field rarely tells the whole story.

This guide shows you how to run a win-loss analysis starting from the meeting notes you already have, then confirm it with the buyer. You'll get a 7-step process, 12 interview questions, a reason-code table, a worked example and a one-page record to copy.

It only works if the notes exist. Try ParrotNotes free to record a short debrief after every meeting, so each deal leaves a trail you can review later.

What a win-loss analysis is

A win-loss analysis is a structured review of closed deals that finds out why buyers chose you, chose someone else, or chose to do nothing. It compares what happened in the deal with what the buyer says drove the decision, then turns the patterns into changes to how the team sells.

Three outcomes belong in it:

• Wins, because a win you can't explain is a win you can't repeat.
• Losses to a named competitor.
• No-decisions, where the buyer kept what they had. In many pipelines this is the biggest "competitor" of all.

A good analysis uses two kinds of evidence: the seller's record of what was said, asked and promised in each meeting, and the buyer's account, usually gathered in a short interview after the decision.

Most guides start with the interview. This one starts with the record, because a rep or sales manager can open it today without a budget or a research team.

Is it worth the effort? In the State of Win-Loss survey that Clozd, a win-loss vendor, runs with The Alliance, 63% of companies reported higher win rates thanks to win-loss, rising to 84% for programs running more than two years. It's a vendor survey of more than 1,000 professionals, so read it as a direction, not a guarantee.

Why a win-loss analysis starts with your meeting notes

The closed-lost reason is one field, chosen at the end, by the person with the most reason to be kind to themselves. That isn't dishonesty. It's memory. Weeks after a deal, everyone remembers the last conversation and the price on the final quote.

Notes taken at the time don't have that problem. They show:

• What the buyer said mattered, in their words, at each stage.
• Who was in the room, and when new people appeared.
• What you promised and whether you delivered it on time.
• The next step agreed and whether it actually happened.

Without notes, a win-loss review is a debate between opinions. With them, it's a timeline you can test against what the buyer tells you. If your notes are thin, the sales pipeline management guide covers what to log at each stage so the next review has something to work with.

How to run a win-loss analysis in 7 steps

1. Pick the deals

Start small: 10 to 15 deals closed in the last 90 days, mixing wins, losses and no-decisions. Include only deals that reached a demo or proposal, so the buyer actually compared options.

Klue, a competitive intelligence vendor, suggests at least 10 similar deals before you trust a pattern. "Similar" matters: don't mix a $5,000 single-site sale with a $300,000 multi-site rollout.

2. Rebuild each deal's timeline from the notes

Before anyone forms a view, lay out the deal meeting by meeting. One row per meeting is enough:

Fill it from your notes, not from memory. Leave a cell empty if the notes don't say. Empty cells are findings too: they show where nobody wrote down what the buyer cared about.

3. Write down the rep's view first

Ask the rep, in two or three sentences, why they think the deal was won or lost. Record it before the buyer interview. You need it later, because the gap between the rep's view and the buyer's view is often the most useful result of the whole exercise.

4. Interview the buyer

Ask the main contact for a short call. Klue's guidance is to contact buyers within 90 days of their decision, while they still remember the details, and to plan for about 30 minutes.

Who asks matters. Buyers soften bad news for the rep they've been dealing with. If you can, have a manager from another team, someone in sales operations, or an outside interviewer run it. In the Clozd survey, 70% of companies using a third-party provider were satisfied with the feedback they got, against 34% of those running it internally.

If you want to record the interview, ask first and say why. Recording law varies by state, and our one-party consent states guide explains where consent from every participant is required.

5. Code the reasons

Turn each deal into two or three reason codes from a fixed list (see the table below). Code the notes and the interview separately, then compare. A fixed list stops one reviewer writing "budget" and another writing "cost" for the same thing.

6. Look for patterns across deals

Count the codes. Look for reasons that repeat, especially when the rep's view and the buyer's view disagree. Also look at timing: at which meeting did lost deals first go quiet, and what was said there?

7. Turn findings into one change per team

Don't finish with a slide deck. Finish with changes someone owns.

A missing question goes into your discovery questions. A recurring worry gets a prepared answer in your objection handling notes. A slow follow-up becomes a rule in the sales playbook. Then check the same codes next quarter.

Win-loss interview questions

Twelve questions cover a 30-minute call. Ask them in roughly this order and let the buyer talk.

The trigger

1. What was happening in your business that made you start looking?
2. What would have happened if you had changed nothing?

The process 3. Who was involved in the decision, and who joined late? 4. What did you need to see or hear before you could move forward? 5. At what point did one option start to pull ahead?

The comparison 6. Which other options did you look at, including keeping what you had? 7. Where did we look strongest, and where did we look weakest? 8. Was there anything we said or sent that worried you?

The decision 9. What was the single biggest reason for your final choice? 10. How much did price matter compared with the other reasons?

The advice 11. What should we have done differently? 12. Is there anything you wish we had asked you?

Question 10 is deliberate. Buyers often say "price" because it's easy and polite. Asking how much it mattered compared with the other reasons usually gets the real ranking.

Reason codes for a sales win-loss analysis

Use a short list and add to it only when a reason truly doesn't fit.

Win-loss analysis example: one lost deal, four meetings

Back to Priya. This is a composite deal, built to show the method.

The rep's view: lost on price. The competitor was cheaper.

What the notes show: downtime came up in meetings 2, 3 and 4. The CFO joined at meeting 3 and asked about it twice. The install plan promised "by Friday" isn't mentioned again until meeting 3, and the phased proposal went out 12 days after the meeting where it was promised.

What the buyer said: the competitor offered to fit trucks over weekends and sent a schedule two days after asking. Asked how much price mattered, the CFO said the competitor was "a bit more expensive, but we couldn't take trucks off the road midweek."

Codes: implementation risk, follow-up speed, stakeholder gap. Not price.

The change: the team added "What happens to your operation while we install?" to its discovery questions, and set a two-day limit for sending anything promised in a meeting.

Wins deserve the same review. Take Daniel, another composite rep, who closed a deal he credited to his demo. In the interview the buyer said the demo was fine, but the deciding moment was the recap he sent that evening, which repeated their concerns in their own words. That's worth teaching the whole team, and our guide to the follow-up email after a sales call shows how to write one.

A one-page win-loss record

Copy this for each deal. One page keeps the review fast and makes deals easy to compare.

WIN-LOSS RECORD
Deal: ____________________  Value: ________  Closed: ________
Outcome:  [ ] Won   [ ] Lost to: __________   [ ] No decision
Meetings reviewed: ____   Notes available for: ____ of them

REP'S VIEW (before the interview)
Main reason: ______________________________________________

WHAT THE NOTES SHOW
First mention of the buyer's top concern: meeting __
New stakeholders and when they joined: _____________________
Promises made / kept on time: ____ / ____
Codes from notes: ___________ ___________ ___________

WHAT THE BUYER SAID (interview date: ________)
Biggest reason, in their words: "_________________________"
How much price mattered: __________________________________
Codes from interview: ___________ ___________ ___________

DID THE REP'S VIEW MATCH?  [ ] Yes  [ ] Partly  [ ] No

ONE CHANGE
What: ________________________  Owner: ________  By: ______

Keeping the notes that make win-loss work

Every step above depends on one habit: writing down what happened right after each meeting, while it's fresh. For a field rep between visits, typing that up rarely happens. Talking for two minutes in the car does.

That's where ParrotNotes helps:

• Record the meeting or a quick debrief on the phone you already carry. There's no meeting bot to invite, so it works for depot visits and site walks as well as office meetings.
• Get a summary and action items from every recording, so promises like "install plan by Friday" are written down with a date.
• Ask questions of a transcript with AI chat, such as "What did the CFO say about downtime?"
• Find a theme across deals with AI semantic search on Pro, so a search for "downtime" brings up every note where it came up.
• Apply MEDDIC, SPIN or BANT to a recording, which shows the gaps before a deal closes, not after.
• Interview buyers in other languages with Pro's 99+ languages and translation.

The Free plan gives you 100 minutes of recording a month, a summary on every recording and 5 AI-powered recordings. Pro is US$19.99 a month, or US$14.99 a month billed annually, with 3,000 minutes a month.

Start your next deal with a trail you can review. Download ParrotNotes free and record a debrief after your next meeting.

Conclusion

A win-loss analysis isn't about blame. It's about replacing the reason you logged with the reason you actually won or lost.

• Start with the notes from each meeting, not the closed-lost field.
• Rebuild the deal timeline before you talk to anyone.
• Write the rep's view down, then interview the buyer within 90 days.
• Code reasons from a fixed list and compare the two views.
• End with one owned change per team, and check it next quarter.

Pick three deals that closed last month and fill in the one-page record for each. You'll probably find at least one where the notes tell a different story from the CRM.

Make your next win-loss review easier. Try ParrotNotes free and keep a recorded debrief from every meeting in the deal.