Win-loss analysis for sales teams
Use win-loss analysis to learn why deals closed, compare buyer feedback with sales notes, and turn recurring themes into changes your team can test.
Free app. Runs on your Mac with the Claude or Codex plan you already have.
What win-loss analysis is
Win-loss analysis examines closed deals to learn what shaped buying decisions. Start with a defined group of opportunities and reconstruct what mattered to buyers across wins and losses. A CRM export tells you which deals closed and how your team recorded the outcome. Buyer interviews and other firsthand feedback can explain how buyers reached their decisions. A useful analysis traces each explanation to its source and shows how often it appears across distinct deals.
The same issue can play different roles across deals. A buyer might mention price during negotiation, then choose the seller whose rollout plan meets a deadline. Another might select a lower-cost option because it meets the same requirements. Recording both the issue and its role in the decision gives sales leaders a way to tell which objections need a better response, which offer changes deserve a test, and where they need more evidence.
What it does for the business
- Focus coaching on the moments buyers rememberWhen buyers say a late handoff left implementation questions open, review what reps cover before the final demo. You can give managers a specific call behavior to coach and a way to see whether reps adopt it.
- Protect the strengths that win dealsWins show which parts of your sales process help buyers move forward. If buyers consistently point to an early technical review, document what made it useful so more reps can repeat it with similar accounts.
- Spend product time on clearer requestsA sourced account of why deals were lost gives product teams the buyer's actual requirement and the situation in which it mattered. Product can check whether a gap recurs in the segment it serves before assigning work.
- Put pricing changes to a more specific testA broad price label can hide budget timing, unclear value, or a competing offer with a different scope. The evidence can help you choose whether to test a packaging change, introduce a clearer comparison, or discuss budget approval earlier.
Win-loss analysis, step by step
Choose the deals and define the decision
A result is only as specific as the group of deals it describes.
What to do
- Name the decision the analysis will inform. For example, decide what to change in late-stage technical evaluations for midmarket buyers next quarter. Write down which deals qualify before inspecting their reasons.
- Set a close-date window and record qualifying teams, products, segments, and deal types. Handle renewals and new business according to your question. Use the same eligibility rules for wins and losses.
- Define the deal cohort, the set of opportunities covered by the analysis. Record how your CRM handles reopened and duplicated opportunities and use a consistent record when historical exports disagree about the same deal.
- List the current CRM export and any authorized notes, correspondence, or interview records you can use. Record which deals each source covers and preserve the originals. If you select a subset, record the selection rule and the total eligible set.
Why
Comparing wins and losses across different markets can hide differences in who buys and why. Explicit inclusion rules let you reproduce the analysis next quarter. A source inventory shows where your buyer feedback is concentrated.
Read the evidence behind each outcome
Who said it and when they said it belong beside every reason.
What to do
- Use one stable opportunity ID across the source files. Compare duplicate rows against the original records and check for copied notes across deals. Keep the source and date for observations you retain.
- Label CRM reason codes, rep notes, and statements from the buyer by source type. A rep's account of a conversation and the buyer's own email both inform the review. Record their provenance so readers can weigh them.
- When you conduct buyer interviews, ask people to walk through their decision in order. Start with what prompted the evaluation, then ask which options stayed in contention, what changed as they compared them, and what tipped the decision.
- Log each relevant observation beside its deal ID and the row, email, or interview passage it came from. A buyer may mention procurement timing and a product gap in the same account. Preserve both and mark conflicts or gaps where the evidence leaves the reason uncertain.
Why
When you have little buyer feedback, a rep's account can point to evidence worth reviewing. Keep the accounts separate so you can tell where they agree and where you need more evidence.
Count themes and propose changes you can test
Every theme count needs a defined set of deals underneath it.
What to do
- Group observations into concrete themes. Define what qualifies for each one. For instance, use budget availability for an account without approved funds and value for money for a buyer who questions whether the benefits justify the price.
- Count distinct deals per theme and show wins and losses separately. Name the denominator next to each count, such as all eligible losses. Report how many deals in that group have unknown reasons. Explain that a deal can contribute to several themes.
- Show how much buyer evidence backs each theme and quote a passage that explains how it mattered. Look for counterexamples, such as wins where buyers raised the same objection. If you also weight the results by deal size, use complete amounts in compatible currencies and leave the deal counts visible.
- Choose a short list of changes tied to those observations. If buyers repeatedly cite uncertain rollout dates, test an earlier implementation review on comparable opportunities. Decide who will own the test, which deals qualify, and what evidence will tell you whether to keep the change.
Why
A theme may appear often because a team uses the same reason code by default. When it appears in wins and losses, read the supporting passages and exceptions to see where it may have influenced the outcome.
Verify the counts and claims against their sources
A reviewer needs to be able to reconstruct every finding from the evidence.
What to do
- Have a second reader compare the win-loss report with the source inventory and evidence. Trace the major findings to the records that support them and read quoted excerpts in context.
- Recalculate the counts from the source rows. Confirm that each deal is counted once within a theme and that denominators include the deals described by their labels. Check totals for exclusions, unknown reasons, wins, and losses.
- Check the meaning of empty fields and groups. An eligible cohort with zero recorded events and an export with missing rows give readers different information. Verify dates and report which records were actually available.
- Read each proposed test beside the theme that prompted it. Record what you corrected and what questions remain. If a material finding still lacks support, label the report partial or hold it pending the missing evidence.
Why
Review can catch a denominator that drops deals with missing reasons or a quote that describes a preference recorded after the decision. Either can change which theme the team acts on.
Deliver the findings and make the next decision
The report should tell its reader which decision the evidence can support.
What to do
- Lead with the clearest finding and name the group of deals it applies to. Put the source breakdown, theme counts, and missing evidence where readers can find them.
- Share the findings with the people who can test a change. Give sales managers a specific behavior to coach, or give product managers the buyer requirement and deal context they need to evaluate.
- Record the decision your team takes and the test it agrees to run. If the strongest evidence comes from a narrow slice of your pipeline, decide where to collect more buyer feedback before applying the finding more widely.
Why
A report that ends with a clear decision and an owner gives the team a way to learn whether the proposed change helps. Recording the starting evidence also makes it possible to revisit the decision if the buyer mix changes or the next set of deals shows a different pattern.
Common mistakes
- Counting comments instead of dealsMultiple comments about the same theme on one opportunity still give you one deal for that theme.
- Treating a rep's reason code as the buyer's verdictKeep the reason code attributed to the seller unless a direct buyer source supports it.
- Filing missing reasons under OtherKeep unknown reasons visible so readers can judge coverage and distinguish missing evidence from a rare known reason.
- Analyzing only the loudest lossesUse a defined cohort that includes wins and losses, and record the selection rule when you review a subset.
- Treating a recurring theme as proof of causeDescribe how the theme appears in the evidence and test whether a change affects the outcome in similar deals.
What a good result looks like
- The report states the close-date window, eligibility rules, and number of deals covered.
- Readers can tell which observations come from buyers and which come from the sales team.
- Theme counts identify distinct deals, their denominator, and the share with unknown reasons.
- Representative quotes and counterexamples can be traced to the source records.
- Every proposed change has a reason, a way to test it, and a decision the test will inform.
And then what? Using the result
- Pick one proposed change and agree with its owner on the next group of eligible deals for the test.
- Bring buyer language to a coaching session and revise the discovery question or sales material implicated by the evidence.
- Give product or pricing teams the passages behind recurring concerns so they can check whether the issue applies to the customers they serve.
- Review which segments have few direct buyer accounts and focus your next interview invitations there.
- Revisit the same theme definitions after the test and compare outcomes for deals with similar characteristics.
When to run it
- During quarterly sales planningUse a defined close-date window to see which buyer concerns should inform the next round of coaching, product feedback, or sales materials.
- When losses cluster around a decision pointReview what buyers say about that point, such as the final security review or proposal, and compare it with how similar wins moved through the same step.
- After changing the offer or sales processCheck whether buyers who saw the change describe the issue it was meant to address, and account for differences in who entered the pipeline.
Questions people ask
How do you do win-loss analysis?
Define a group of closed opportunities, label the evidence about each decision, and count recurring themes by distinct deal within wins and losses. Propose changes you can test and review their evidence alongside the counts and quotations.
What should a win-loss report include?
Include scope, wins and losses, theme counts with denominators, unknown reasons, supporting observations, and proposed tests. Record exclusions and buyer feedback coverage so readers can judge how far the findings apply.
Can you do win-loss analysis without buyer interviews?
Yes, you can analyze CRM records, sales notes, and any available buyer correspondence. State which conclusions rest on seller reports, and identify the cases where direct buyer evidence is missing. That gives the team a basis for deciding what to investigate.
How do you count deals with more than one reason?
Count a deal once in each supported theme. A deal can contribute to both a procurement theme and an implementation theme. Show the same deal only once within either theme and explain that the theme counts can add up to more than the number of deals.
Should you include no decision in win-loss analysis?
Include no decision outcomes when they fit the question and cohort rules, and identify them separately from losses to another supplier. A buyer that stays with its existing process presents a different sales question from one that buys from a rival.
Who should interview buyers after a deal closes?
Choose someone who can ask neutral questions and make it easy for the buyer to give candid feedback. A colleague who was outside the deal can ask what happened at each stage and follow up on contradictions without having to defend the original sales approach.
More jobs in Sales & outbound
Win-loss analysis, on your own Mac.Free app. Runs on your Mac with the Claude or Codex plan you already have. Your files stay on your computer.
Download for Mac