Win/loss analysis: how to learn from every no

In short

Win/loss analysis means collecting the real reasons you win and lose, then changing something because of them. For an outbound team it starts on the phone: log one reason, from a short fixed list, for every 'not interested'. Review the counts every month, interview a few lost deals properly, and fix the biggest pattern first: the list, the script or the offer.

Win/loss analysis means you collect the real reasons you win and lose, count them, and change something because of them. For an outbound team it starts on the phone: every "not interested" gets one reason from a short, fixed list. Once a month you look at the counts, you interview a few lost deals properly, and you fix the biggest pattern first. That might be the lead list, the script or the offer. Without reasons, a "no" is just a number. With reasons, every no teaches you something.

Why most teams learn nothing from a no

Most teams track how many deals they lose, not why. When they do ask, the answer often lands in a free text field nobody reads. Or the salesperson writes "price" because that is the easiest explanation.

The idea of learning from people who say no is old. In their 1990 HBR article Zero Defections, Frederick Reichheld and W. Earl Sasser argued that feedback from customers who leave shows companies the weaknesses that really matter. One example they describe is a credit card company that started asking leaving customers why, and acted on it. Their focus was on customers who leave, but the logic is the same for prospects who say no: the people who did not choose you know something you do not.

You often lose to "nothing", not to a competitor

Many sales teams assume they lose to competitors. Research suggests a large share of losses go to no decision at all. In a 2022 HBR article, Matthew Dixon and Ted McKenna describe a study of more than 2.5 million recorded sales conversations. They found that between 40% and 60% of deals were lost to buyers who said they meant to buy and then did not act.

They split those "no decision" losses further. In their data, 56% came from the buyer's own indecision and 44% from a preference for the status quo. The important point for win/loss analysis: indecision is driven by personal fear of making a mistake, and buyers rarely say that out loud to a salesperson. So the reason a rep hears is often not the whole story.

Two other HBR pieces by Steve W. Martin, who runs win/loss studies, point the same way. Across more than 1,000 interviews with decision-makers, he writes in Top Reasons Salespeople Lose Business, buyers mostly rated the competing salespeople and products as roughly equal. What separated winners were factors such as the incumbent advantage (he puts the odds of unseating an incumbent at about one in five), removing risk, and reaching executives. In a later survey of more than 230 buyers, described in 6 Reasons Salespeople Win or Lose a Sale, 90% said there is always or usually one person on the buying committee who tries to push the decision their way. These are one consultant's studies, mainly from larger US deals, so treat them as patterns to check, not laws.

Two levels of win/loss for an outbound team

Classic win/loss analysis looks at big deals at the end of a long process. An outbound team has a second, much bigger source of data: the hundreds of short "no" answers on the phone every week.

LevelWhat you collectHow oftenWhat it changes
Call levelOne reason code for every "not interested"Every call, reviewed monthlyLead list, opening, objection answers
Deal levelA short interview after a lost (or won) dealA few per monthOffer, proof, process, who to involve

Start with the call level. It is cheap, fast and gives you numbers within weeks.

Capture a reason for every "not interested"

The rule is simple: no "not interested" without a reason. To make that work in practice:

  1. Use a fixed list. Five to eight reasons that cover most calls. Free text alone cannot be counted.
  2. Keep the words plain. Write the reasons the way prospects say them, so callers pick quickly.
  3. Add "no reason given". It is honest, and a high share tells you callers end calls too soon.
  4. Keep "other" small. If more than about one in ten calls ends up there, read the notes and add a reason.
  5. Same list for everyone. Otherwise you cannot compare callers or campaigns.

An example list for a B2B calling team:

  • Already has a supplier
  • No need right now
  • No budget
  • Not the right person
  • Bad timing (call back later)
  • Company not a fit (too small, wrong sector)
  • No reason given
  • Other (with a note)

Ask one more question before you hang up

A reason code is only as good as the question behind it. When someone says "not interested", a calm, curious follow-up often gives you the real reason: "Fair enough. Can I ask, is that because you already have something for this, or because it is not a priority right now?" You are not trying to turn the no around. You are trying to learn. Our guide on handling sales objections has more examples.

Read the patterns once a month

Once a month, count the reasons per campaign and per caller. The example below is made up, to show how to read it.

Reason (example month)CountShareWhat it usually points to
Already has a supplier6231%Script: you need a reason to switch or to compare
No need right now4422%List or timing: look for urgency signals
Not the right person3618%List: wrong role on the lead, ask for a referral
Company not a fit2412%Targeting: tighten the profile
No budget147%Offer or segment: often too small companies
No reason given2010%Coaching: callers stop asking

In this example, almost a third of all no's are "already has a supplier". That is a script problem you can work on: a better question about what they would change about their current supplier, or a low-risk reason to compare. "Not the right person" and "company not a fit" together are 30%. That is a list problem. Our guide on the ideal customer profile shows how to test a sharper target group with separate campaigns.

Compare callers and campaigns, not just totals

The total hides the useful differences. If one caller has twice as many "no reason given" as the rest, that is a coaching topic. If one campaign has far more "company not a fit", the list is the problem, not the callers. Our article on coaching a sales team with data explains how to turn this into a one-on-one conversation.

Interview a few lost deals properly

Reason codes tell you what is happening on the phone. For deals that got further (a meeting, a proposal), a short interview tells you why. Because buyers rarely share their fears with the salesperson, as Dixon and McKenna note, it helps if someone else asks: a manager or a colleague who was not in the deal.

Keep it to 15 minutes. Possible questions:

  1. What problem were you trying to solve, and why then?
  2. Who was involved in the decision?
  3. Which options did you compare, including doing nothing?
  4. What almost made you decide differently?
  5. What could we have done better, even if the outcome stayed the same?

Do not re-sell during the interview. The moment it becomes a sales call, the honest answers stop. And interview some wins too. Knowing why people said yes is just as useful.

Turn reasons into one change at a time

Analysis without action is just reporting. After each monthly review:

  1. Pick the biggest reason you can influence.
  2. Decide one change: a new question in the script, a new answer to an objection, a filter on the list.
  3. Write it down with a date.
  4. Next month, check whether that reason went down and whether meetings per call went up.

Change one thing at a time. If you change the list, the script and the opening all at once, you will not know what worked.

In Ringlane, "not interested" (X) closes the lead and asks for a reason, so every no is counted. The reports show the reasons for not interested per period, campaign, team and person, next to the other results. When you decide on a new answer to an objection, you put it in the arguments panel next to the script. For writing those answers, see our guide on writing a cold calling script.

Common win/loss mistakes

  • Free text only. You cannot count stories.
  • Trusting the first answer. "Price" and "not interested" are often polite exits, not the real reason.
  • Only studying losses. Wins tell you what to repeat.
  • Blaming the caller. Many reasons point to the list or the offer, not to the person on the phone.
  • Never changing anything. If the same reason tops the list three months in a row, the analysis is not being used.

Frequently asked questions

What is win/loss analysis?
Win/loss analysis is the habit of collecting why prospects say yes or no, counting the reasons, and using the patterns to improve your targeting, script, offer or process. It can be as simple as a reason code on every lost call and a short interview with a few lost buyers each month.
Why do sales teams lose deals?
Often not to a competitor. In a study of more than 2.5 million recorded sales conversations described in HBR in 2022, 40% to 60% of deals were lost to buyers who said they intended to buy and then did nothing. Incumbent suppliers, unclear value and the wrong contact are other common reasons.
Which reasons should I track for 'not interested'?
Use a short fixed list of five to eight reasons, for example: already has a supplier, no need right now, no budget, not the right person, bad timing, company not a fit, and no reason given. Keep 'other' small and read those notes each month to see if a new reason is needed.
What questions should I ask in a win/loss interview?
Ask what problem they were trying to solve, who was involved in the decision, which options they compared, what almost made them choose differently, and what we could have done better. Keep it short, listen more than you talk, and never use the call to re-sell.
Who should run win/loss interviews?
Preferably someone other than the salesperson who lost the deal, such as a manager or a colleague from another team. Buyers tend to be more open with someone who was not in the deal, and the person asking is less likely to defend their own work.

Sources

  1. Harvard Business Review: Stop Losing Sales to Customer Indecision (Dixon and McKenna, 2022)
  2. Harvard Business Review: Top Reasons Salespeople Lose Business (Martin, 2012)
  3. Harvard Business Review: 6 Reasons Salespeople Win or Lose a Sale (Martin, 2017)
  4. Harvard Business Review: Zero Defections: Quality Comes to Services (Reichheld and Sasser, 1990)