What Is Win-Loss Analysis? How to Run One

Win-loss analysis is the practice of systematically interviewing buyers after a deal closes, whether you won, lost, or ended in no decision, to understand the real reasons behind the outcome. It compares what buyers say with what your CRM and sales team say, and turns the gaps into changes in positioning, product, pricing, and process.

Ask a sales leader why the team lost last quarter and you’ll often hear “price” or “timing.” Ask the buyers and you’ll hear something different: a business case nobody believed, a missing integration, a champion who left, a security review that stalled. The gap between those two stories is where win-loss analysis earns its keep.

This guide explains what win-loss analysis is, why CRM data alone isn’t enough, and how to run a simple program, with a question guide, a coding frame, and a worked example.

What is win-loss analysis?

Win-loss analysis means picking a set of closed deals, interviewing the people who made the decision, labeling each conversation with the same reason categories, and comparing wins with losses inside a segment. It covers three outcomes: won deals, lost deals, and no-decisions, where the buyer chose to do nothing.

It’s not the same as a deal review, where the team talks about its own deal, or a post-mortem driven by the rep’s memory. The defining feature is the buyer’s voice, collected by someone who didn’t sell to them.

Why CRM loss reasons aren’t enough

Almost every CRM has a “closed lost reason” field, and most of them are unreliable in the same ways. The rep fills in the dropdown minutes after a disappointing call, often choosing the option that feels least like a mistake, and price becomes the default explanation. Independent interviews regularly find that the recorded reason and the buyer’s actual reason differ. A fair summary: reps remember losses as price, while buyers remember them as risk, timing, or a business case nobody believed.

What the CRM says	What a buyer interview might reveal
Price	The ROI wasn’t clear, so any price felt too high
Timing	The champion couldn’t get an executive sponsor
Went with a competitor	The competitor had an integration we didn’t mention
No response	Security review stalled and nobody helped them through it

That doesn’t make CRM fields useless. They’re good for volume and rough trends, and they help you choose which deals to interview. Treat them as labels that tell you where to look, not as findings.

What you can learn

Finding type	Example	Likely owner
Positioning and messaging	Buyers don’t understand how we differ from the alternative	Product marketing
Product gaps	A missing integration appears in many losses	Product
Pricing and packaging	The entry plan lacks one feature buyers expect	Product and finance
Sales process	We rarely reach the economic buyer	Sales leadership
Competitive	One competitor wins on onboarding speed	Competitive intelligence

How to run a win-loss analysis

1. Define the question and scope. A vague goal produces vague findings. Try something specific: “Why are we losing mid-market deals to Competitor X?” or “What makes wins in our new segment different?”
2. Select deals deliberately. Include wins, losses, and no-decisions, across deal size, industry, and rep. Interviewing only losses teaches you what went wrong but not what’s working.
3. Interview soon after the decision. Sources range from two to six weeks, and recall fades quickly after that. Aim for within a month.
4. Use a neutral interviewer. The account executive who owned the deal shouldn’t run it, and neither should their manager. Buyers soften criticism when they know who they’re talking to. A product marketer, researcher, or outside firm works better. Keep the rep debrief separate, and hold it after you have the buyer data.
5. Recruit with a clear, low-effort ask. Offer a 20 to 30 minute call, explain the feedback is confidential and used to improve, and don’t use it to win them back. Try more than one person on the buying committee.
6. Code every interview the same way. Use a fixed set of labels so you can compare across deals.
7. Triangulate with your data. Compare interviews with CRM stage history, cycle length, and competitors, and note where they agree and contradict.
8. Report with sample size and confidence, then act. Run a workshop where each priority finding gets an owner and a change to a specific asset: a deck, a pricing page, a playbook, a roadmap item.

Questions to ask buyers

Topic	Sample question
Trigger	What was going on that made you start looking?
Alternatives	What options did you consider, including doing nothing?
Criteria	What mattered most in your decision, and how did that change along the way?
Committee	Who was involved, and who had the final say?
Experience	What was it like working with our team compared with the others?
Turning point	Was there a moment when you knew where this was heading?
Concerns	What worried you most about choosing us?
Advice	If you could change one thing about how we sold to you, what would it be?

Ask about behavior and specific moments, not opinions in the abstract. “Walk me through what happened after the demo” gets better answers than “Did you like our product?” And listen more than you talk.

A simple coding frame

Pick one primary reason per interview, plus an optional secondary one, from labels like these. Adapt them to your business, and keep them fixed from quarter to quarter.

Category	Meaning
Competitive loss	The buyer chose a named competitor
No decision	The buyer kept the status quo
Product gap	A needed capability or integration was missing
Value and price	Cost was hard to justify against the expected return
Evaluation and process	We didn’t reach decision-makers or support the evaluation well
Champion and sponsor	The internal advocate left or lacked influence
Timing and priority	The project was deprioritized or delayed
Trust and risk	Security, vendor stability, or implementation risk worried the buyer

Track timing and no-decision outcomes separately from true competitive losses. A deal pushed to next quarter isn’t the same as a deal lost to a rival, and mixing them hides what’s really going on.

A worked example

Imagine a team interviews 24 buyers from lost and no-decision deals. In the CRM, 14 of the 24 were logged as “price.” The numbers below are illustrative.

Primary reason from interviews	Deals	Action
Value and price	4	Review packaging at the entry tier
Business case unclear	6	Create an ROI template and train reps to use it
Product gap (integration)	5	Publish an integrations guide; raise on the roadmap
Champion or sponsor lost	5	Multithread earlier; require a named executive sponsor by a set stage
Security review stalled	3	Build a security answer pack
Other	1	None

The CRM said price in 14 of 24 deals. Buyers named it as the main reason in four. The biggest actionable themes were an unclear business case and a missing integration, and none of them would have shown up in the dropdown. With 24 interviews, treat the percentages as directional, not precise. Say so in the report.

Connect it to deal slippage and pipeline hygiene

Win-loss findings are most useful when they feed your day-to-day data. Three links are worth making:

• Standardize the closed-lost field. Replace free-form or generic reasons with the categories from your coding frame, and make the field required. Add a competitor field. Our guide to closed-loop reporting covers how those outcomes flow back to marketing.
• Watch for slippage. Deals that keep moving to the next quarter often end as no-decisions. Interviews can reveal why, and our explanation of deal slippage shows how to catch the signs earlier.
• Tighten pipeline hygiene. If interviews show you rarely reach the economic buyer, require that field before a deal enters Commit. Qualification frameworks like BANT and MEDDIC turn findings into required evidence.

Each quarter, compare your CRM loss reasons with the interview findings. If they diverge, recalibrate the dropdown. Over time the CRM field gets closer to reality, and you can use it for ongoing trend tracking between interview rounds. The customer journey map is also a useful companion, since interview answers often point to specific stages where buyers got stuck.

In-house, third-party, or AI-assisted?

Option	Advantages	Watch for
In-house (product marketing or research)	Low cost, deep product knowledge	Buyers may be less candid; programs fade when people get busy
Third-party firm	Neutrality and reach to lost buyers	Cost, and a smaller sample of deals
AI-moderated interviews or surveys	Scale and speed	Depth and nuance vary; review transcripts yourself
Hybrid	Interviews for depth, surveys for breadth	More to coordinate

Whichever you choose, the same rules apply: someone neutral asks the questions, the labels stay consistent, and each finding has an owner.

How many interviews are enough?

Guidance varies. Some sources suggest 15 to 20 interviews per quarter to see clear patterns, and others suggest at least 10 to 15 deals before drawing conclusions about any single pattern. A thinner round is still useful if you label it directional. Fewer than about eight interviews per cycle starts to look more like anecdotes than patterns. Start small, keep the process steady, and let the sample grow.

Mistakes to avoid

• Letting the account executive or their manager run the interview
• Interviewing only losses, so you never learn what’s working
• Waiting months, so memories fade and buyers stop responding
• Trusting the CRM dropdown without checking it against buyers
• Reporting percentages from a tiny sample as if they were precise
• Producing a report without owners or follow-up
• Using the interview to try to win the deal back

Summary

Win-loss analysis interviews buyers after wins, losses, and no-decisions to find the real reasons behind outcomes. It matters because CRM loss reasons are written by reps in a hurry and tend to default to price or timing, while buyers describe different drivers, such as unclear business cases, missing integrations, lost champions, and stalled security reviews.

To run one, define a specific question, select a mix of recent deals, use a neutral interviewer, interview within about a month, code every conversation with a fixed frame, and triangulate with CRM data. Report sample size and confidence, then assign owners to each finding. Feed the results back into your closed-lost field, your qualification rules, and your deal reviews so the CRM gets closer to the truth.

Frequently asked

What is win-loss analysis?+

It’s the practice of interviewing buyers after a deal closes, whether won, lost, or ended in no decision, to learn the real reasons behind their choice and use them to improve positioning, product, pricing, and sales process.

Why isn’t the CRM loss reason enough?+

Reps usually choose it quickly and tend to cite price or timing. Buyer interviews often reveal different reasons. Use CRM fields for volume and trends, and validate them with real buyer conversations.

Who should conduct win-loss interviews?+

Someone neutral: a product marketer, researcher, or outside firm. The rep who owned the deal and their manager should not, because buyers soften feedback when they know who is asking.

How soon after a deal should we interview the buyer?+

Ideally within two to six weeks. Memory fades quickly, and recruiting gets harder with time, so aim for within about a month.

How many interviews do we need?+

Some sources suggest 15 to 20 per quarter for clear patterns. Smaller rounds are still useful if labeled directional. Keep the process consistent and grow the sample over time.

Should we interview wins as well as losses?+

Yes. Wins show what’s working and what to protect, and they give you a baseline to compare losses against. Also include no-decision deals, which are often the largest hidden source of lost revenue.

How do we get buyers to agree to an interview?+

Keep the ask short, offer a 20 to 30 minute call, explain that feedback is confidential and used for improvement, not for selling, and send the request from a neutral person. Try multiple contacts on the buying committee.

What do we do with the findings?+

Hold a short workshop, rank the findings, and map each to an owner and a specific change, such as a messaging update, an ROI template, a required CRM field, or a roadmap request. Then check next quarter whether the pattern moved.