Skip to content

Win-loss analysis: how to run it and what to ask

By · Published · 5 min read

Hand-drawn illustration for the guide: Win-loss analysis: how to run it and what to ask

Win-loss analysis means asking buyers, shortly after they decide, why they chose you or someone else, then looking for patterns across many decisions. Interview both wins and losses, ideally within a few weeks of the decision, and have someone other than the salesperson do it. CRM "loss reasons" are not enough: salespeople, like everyone, tend to blame circumstances such as price, while buyers often give different reasons when asked directly.

Why CRM loss reasons mislead

When salespeople record why a deal was lost, "price" usually tops the list. Sometimes it is true. Often it is the easiest explanation for both sides: the buyer says price because it is polite, and the salesperson records it because it is outside their control. Research on how people explain outcomes finds that we tend to credit successes to ourselves and failures to circumstances. Talking directly to buyers gets past both.

Step 1: choose the deals

  • Include wins and losses. Wins tell you what to keep doing; losses alone give a distorted picture.
  • Pick recent decisions, ideally within the last one to three months, while memories are fresh.
  • Focus on qualified deals that reached a real decision, not prospects who never engaged.
  • Aim for 10 to 20 interviews to start. Patterns usually appear within the first dozen.

Step 2: choose the interviewer

Buyers are more honest with someone who was not selling to them. Options include a sales manager from another team, a founder, someone from customer success or product, or an outside interviewer. The salesperson who ran the deal should not conduct the interview.

Step 3: ask for the interview

Keep the request short and honest:

"Thank you for considering us for [project]. We're trying to learn how we can improve, whatever the outcome. Would you give us 20 minutes for a few questions? There's no sales pitch, and I'm not the person who was selling to you."

Tell them how notes or recordings will be used and stored. If you record, ask permission first.

Step 4: 12 questions to ask

  1. What problem were you trying to solve, and why did it become a priority when it did?
  2. Who was involved in the decision, and who had the final say?
  3. Which options did you consider, including doing nothing?
  4. What mattered most in the decision? How did you rank those factors?
  5. How did we compare with the others on each of them?
  6. What did we do well during the process?
  7. What did we do badly, or what was missing?
  8. Was there a moment when you leaned towards one option? What happened then?
  9. How did price compare with the value you expected?
  10. Was there anything we said or did that raised a concern?
  11. If you were advising us, what would you tell us to change?
  12. Is there anything else we should know?

Ask follow-up questions: "What do you mean by that?" and "Can you give me an example?" The most useful answers usually come in the second half of the conversation.

Step 5: code the answers

After each interview, write a short summary and tag the main reasons into a consistent set of categories. For example:

CategoryExamples of what buyers say
Product fit"It didn't integrate with our accounting system."
Sales process"We never got a clear proposal." "Too slow to respond."
Trust and risk"We weren't sure you could support us at our size."
Price and value"Hard to justify against the cheaper option."
Relationship"The other supplier understood our business better."
Timing and priority"It wasn't urgent enough this year."

Worked example. After twelve interviews (five wins, seven losses), a team tallies the main reason for each loss:

Main reason for the lossCount
No clear plan for implementation3
Slow response after the demo2
Price1
Missing integration1

The CRM had recorded price as the reason for five of the seven losses. The interviews point instead to the sales process after the demo: unclear next steps and slow follow-up. Wins mentioned "a clear rollout plan" in four of five cases.

Step 6: act and share

Share a short summary with sales, marketing and product every quarter: the top three patterns, quotes that illustrate them and one or two changes. In the example, the team introduces a one-page implementation plan in every proposal and a 24-hour follow-up rule after demos. Then keep interviewing, and check whether the pattern changes.

Common mistakes

  • Interviewing only losses.
  • Letting the salesperson interview their own buyer.
  • Arguing with the buyer or trying to reopen the deal during the interview.
  • Collecting insights and changing nothing.
  • Relying only on CRM loss reasons.

What the evidence says

That people tend to explain failures by circumstances and successes by their own actions is Strong, which is why CRM loss reasons need checking. The interview method, questions and coding are Practice, widely used in B2B companies. Vendor statistics on how much win-loss programmes raise win rates are Weak.

Frequently asked questions

What is win-loss analysis? Interviewing buyers after they decide, about why they chose you or another option, and looking for patterns across many decisions.

Who should conduct win-loss interviews? Someone other than the salesperson who ran the deal, so the buyer can speak freely.

How many win-loss interviews do I need? Start with 10 to 20 across wins and losses; patterns often appear within the first dozen.

Check yourself

  1. Why include wins as well as losses? Wins show what to keep doing, and losses alone give a distorted picture.
  2. Why are CRM loss reasons unreliable? Price is an easy explanation for both buyer and seller, and people tend to blame circumstances for failures.
  3. What should happen after each quarter's interviews? Share the top patterns and make one or two changes, then check whether patterns shift.

Go deeper: free sample lesson

The Buyer Psychology for Sales course covers why buyers choose, stall or walk away.

Written by , founder of Dokimos. He is a senior product and UX designer based in Athens, and is studying for a BSc in Psychological Science.