
Win-Loss Analysis: Closed-Lost Reasons, Interview Guide & Template (2026)
Win-loss analysis is the practice of systematically finding out why buyers chose you, chose a competitor, or chose to do nothing—by interviewing the buyers themselves, surveying them, and checking what they say against your CRM and deal data—and then turning the recurring patterns into changes in sales, product, marketing, and pricing.
Key takeaways:
- The CRM "closed-lost reason" is a starting point, not an answer. In Clozd's comparison of 1,000 closed-lost deals, the rep-entered reason matched what the buyer said in an interview only 15% of the time (Clozd, 2023).
- Fix the picklist before you analyze it. Record a primary reason, a secondary reason, whether it was controllable, the stage the deal died at, and the real competitor (including "no decision").
- Talk to buyers, not just reps. Interview 2–6 weeks after the decision, with someone other than the rep who owned the deal, using the 12-question guide below.
- Study wins too. Wins tell you what to repeat; losses alone skew you toward discounting and feature-chasing.
- Every finding needs an owner. Route themes to sales, product, marketing, or pricing with a due date, and re-measure next quarter.
- Small team? Still doable. Five interviews a quarter plus a clean picklist beats a program that never starts.
What win-loss analysis is (and what it is not)
Win-loss analysis answers one question: why did the buyer decide the way they did? It covers won deals, deals lost to a competitor, and deals lost to "no decision," and it gets the answer from the buyer's side rather than from the seller's memory.
It is not the same as a pipeline review or a deal post-mortem. A pipeline review looks forward at open deals. A post-mortem is usually an internal conversation among the people who worked the deal. Win-loss analysis adds the one voice both of those lack—the buying group's—and looks for patterns across many deals instead of explaining one.
| Pipeline review | Internal deal post-mortem | Win-loss analysis | |
|---|---|---|---|
| Looks at | Open deals | One closed deal | Many closed deals (won and lost) |
| Main source | Rep and CRM | Deal team | Buyers, plus CRM and deal data |
| Output | Forecast and next steps | Lessons for that team | Cross-deal themes with owners |
| Typical owner | Sales manager | AE / sales manager | Product marketing, RevOps, or sales leadership |
Related terms:
- Closed-lost reason: the field in Salesforce, HubSpot, or another CRM that records why an opportunity was marked lost.
- Lost deal analysis: the subset of win-loss that looks only at losses. Useful, but half the picture.
- Competitive win-loss: win-loss focused on head-to-head deals against a named competitor, often owned by competitive intelligence.
- No-decision loss: the buyer did not pick anyone and kept the status quo. It needs its own category, because the fix (usually a stronger business case) differs from the fix for a competitive loss.
If you want the numeric side—how to calculate and benchmark win rate itself—see the sales win rate guide. This article is about the why behind that number.
Why rep-entered closed-lost reasons are unreliable
The closed-lost field is filled in by the person closest to the loss and the strongest incentive to explain it away, usually in a few seconds as they close out the opportunity. That makes it useful as a pointer but weak as evidence.
One published comparison comes from Clozd, a win-loss vendor, which compared CRM data to buyer interview feedback across 1,000 closed-lost deals (Clozd, "Your CRM buyer data is bad," 2023). Because this is a vendor's analysis of its own data, treat it as directional, but the findings match what most sales leaders suspect:
- The rep's closed-lost reason and the buyer's stated reason aligned only 15% of the time.
- 44% of closed-lost reasons in the CRM were outcomes, not reasons—for example "went with competitor" describes what happened, not why.
- The competitor tagged in the CRM was incorrect in nearly 7 out of every 10 deals when compared with the competitors buyers said they considered.
- In interviews, the average buyer described 4–5 primary factors in their decision, while the CRM typically holds one.
Even without that data, the structural reasons are easy to see:
- "Price" is the socially easy answer. Buyers often say "budget" or "price" on the phone because it ends the conversation politely. The underlying reason—weak business case, lost champion, a competitor's better implementation story—rarely surfaces in that call.
- Reps are not neutral. "Bad timing" or "no budget" protects the rep; "we never reached the economic buyer" does not. This is not dishonesty, it is attribution bias.
- The picklist forces one answer. Real decisions are multi-causal. A single-select field throws away the second and third factors, which are often the controllable ones.
- Outcome-style values leak in. Values like "Lost to competitor" or "Went dark" tell you nothing you can act on.
- Buying groups are large. Forrester's State of Business Buying 2024 reports that on average 13 people are involved in a purchase decision, with 89% of purchases involving two or more departments (Forrester, 2024). Your rep may have spoken with three of them. The reason the deal died may sit with someone they never met.
The fix is not to abandon the CRM field. It is to redesign it so it is analyzable, and then to verify it with buyer interviews and objective deal data.
A closed-lost reason taxonomy you can actually analyze
An analyzable closed-lost picklist has five core fields, not one—primary reason, secondary reason, controllable or not, stage lost, and the competitor or alternative chosen—plus a required notes field and a buyer-verified flag. Reasons should describe why, never what happened.
Field design
| Field | Type | Values / notes |
|---|---|---|
| Primary loss reason | Required picklist | From the reason list below (one value) |
| Secondary loss reason | Optional picklist | Same list; blank allowed |
| Controllable? | Required, auto-derived | Controllable / Partly / Uncontrollable (set by the reason) |
| Stage lost | Auto-captured | The last active stage before Closed Lost (see sales deal stages) |
| Chosen alternative | Required picklist | Named competitors, "Built in-house," "Status quo / no decision," "Unknown" |
| Loss notes | Required text, min. 1 sentence | "What would have had to be true for us to win?" |
| Verified by buyer? | Checkbox | Ticked only after an interview or survey response |
The "Verified by buyer?" checkbox is the most useful field on this list. It lets you compare rep-entered reasons with verified ones over time and see where your team's instincts are off.
Reason list (primary and secondary)
Keep it to roughly 15–20 values grouped into categories. More than that and reps pick the first plausible option; fewer and everything lands in "Other."
| Category | Reason value | Controllable? |
|---|---|---|
| Value / business case | Business case not strong enough to justify change | Controllable |
| Value not quantified for the economic buyer | Controllable | |
| Product fit | Missing required capability (name it in notes) | Partly |
| Integration or technical requirement not met | Partly | |
| Security / compliance requirement not met | Partly | |
| Price & commercial | Total cost higher than alternative | Partly |
| Pricing model mismatch (per-seat vs. usage, etc.) | Partly | |
| Contract terms / legal / procurement blocker | Partly | |
| Sales execution | Never engaged the economic buyer | Controllable |
| Champion left or lost influence | Partly | |
| Slow or weak follow-up / proposal | Controllable | |
| Did not address a key objection | Controllable | |
| Competitive | Competitor's product stronger on decision criteria | Partly |
| Competitor's relationship / incumbency | Uncontrollable | |
| Competitor's implementation or services story | Controllable | |
| Buyer situation | Priorities changed / project deprioritized | Uncontrollable |
| Budget frozen or reallocated | Uncontrollable | |
| Reorg, acquisition, or key sponsor left | Uncontrollable | |
| Qualification | Poor fit—should have been disqualified earlier | Controllable |
Three rules keep this list useful:
- Ban outcome values. Remove "Lost to competitor," "Went dark," "No response," and "Other" as primary reasons. If a rep does not know the reason, the honest value is "Unknown—needs verification," which flags the deal for an interview.
- Separate "no decision" from "lost to competitor." Capture it in Chosen alternative, then use the reason field to explain why the status quo won (weak business case, priorities changed, and so on).
- Catching "poor fit" early is a qualification win; catching it late is a qualification problem. A rising share of "should have been disqualified" losses at late stages means the deal should have been screened out sooner—see MEDDPICC for a structure that catches this earlier.
Why the stage lost matters
The same reason means different things at different stages. "Price" lost at discovery is a targeting or positioning problem. "Price" lost after a proposal and a verbal yes is a negotiation, procurement, or economic-buyer problem. Always cut your reasons by stage. If you track stage-to-stage conversion, the opportunity conversion rate guide shows how to spot where deals leak.
How to run a win-loss program, step by step
A working program has six steps: set a goal, pick the sample, gather the buyer's view through interviews and surveys, pull CRM and deal data, analyze across deals, and route findings to owners. Start small and repeat every quarter.
Step 1: Set one or two questions you want answered
A win-loss program without a question produces a pile of transcripts. Pick one or two, for example:
- "Why are we losing to [Competitor] in mid-market deals?"
- "Why did no-decision losses rise this half?"
- "Is our new pricing model helping or hurting late-stage deals?"
The question decides your sample, your interview emphasis, and who needs to see the output.
Step 2: Select the sample
Choose deals deliberately rather than interviewing whoever says yes.
- Include wins. A common starting mix is roughly half losses, a quarter wins, and a quarter no-decision losses, adjusted to your question.
- Qualified deals only. Exclude deals that never reached a real evaluation stage (for example, disqualified at first call). They add noise.
- Recent decisions. Target deals decided in the last 2–6 weeks. Memory fades fast after that, and the people involved move on.
- Meaningful size. Prioritize deals above your median deal size or in the segment your question is about.
- Balance by rep and region. Otherwise one rep's style reads as a company-wide pattern.
How many? Themes usually start to repeat after a handful of interviews per segment. For a first quarter, 8–15 interviews across wins and losses is a realistic target for most teams, and even five will surface the most obvious themes. Treat these as qualitative findings, not statistics.
Step 3: Interview the buyers
Buyer interviews are the core of win-loss. Surveys and CRM data help you scale and verify, but only a conversation surfaces the second and third reasons behind a decision.
Who should conduct them. Not the rep who owned the deal. Buyers soften their answers for someone they built a relationship with, and reps understandably steer toward reasons outside their control. Good options, from most to least neutral:
- A third-party win-loss firm
- Product marketing, competitive intelligence, or research
- RevOps, customer success, or a sales leader from a different team
- As a last resort, a sales manager who was not involved in the deal
Who to interview on the buyer side. The person who ran the evaluation is ideal. The economic buyer is better still if you can reach them. Your champion is useful but will be the most generous voice.
Timing. 2–6 weeks after the decision. Earlier, and a lost buyer may still be negotiating with the winner; later, and details blur.
Format. 30 minutes on video or phone, recorded with permission, with a promise that feedback will not be used to re-open the sale. Recording and consent laws vary by state and country (some require all parties to consent, not just one); confirm your obligations before recording. Some teams offer a modest thank-you such as a gift card or charity donation; check the buyer's gift policy first, especially for public-sector and regulated buyers.
Interview request email (copy and adapt):
Subject: 30 minutes of feedback on your [Category] evaluation?
Hi [First name],
Thank you again for considering [Company] during your recent [category] evaluation.
I lead [team, e.g. product marketing] and I'm not part of the sales team. I'd value 30 minutes of candid feedback on how you made your decision—what worked, what didn't, and what we could have done better. This is not a sales call, and nothing you share will be used to re-open the deal.
Would any of these times work? [Time 1] / [Time 2] / [Time 3]
Or pick a slot here: [scheduling link]
Thank you,
[Name]
[Title], [Company]
Step 4: Add a short survey for scale
Surveys cannot replace interviews, but they let you hear from buyers who will not take a call and from more members of the buying group. Keep it to five or six questions, send it within two weeks of the decision, and include one open-text question. Example questions:
- Which options did you seriously consider? (multi-select, including "keep current approach")
- What were the top three factors in your decision? (pick up to 3 from a list that mirrors your reason taxonomy)
- How did we compare on each of those factors? (better / same / worse)
- How well did we understand your business needs? (1–5)
- Was there one thing that would have changed your decision? (open text)
Step 5: Pull CRM and deal data
For each deal in the sample, capture the objective record next to the interview: stage history and time in each stage, deal size and discount requested, competitors logged, activity volume, which stakeholders were contacted, and—if your team shares proposals digitally—engagement data such as who opened the proposal and when activity dropped off. This is what lets you test a buyer's recollection ("we never saw pricing until late") against facts.
Step 6: Analyze across deals and route the findings
Code every interview against the same reason taxonomy you use in the CRM, count how often each theme appears in wins versus losses, and pull representative (anonymized) quotes. Then assign each theme to an owner with a due date. The analysis template and the action table below cover both.
Win-loss interview guide (12 questions, copy and paste)
A good win-loss interview moves chronologically through the buyer's journey—trigger, evaluation, decision, and what would have changed it—and asks open questions that invite stories rather than ratings. Use these 12 questions as a 30-minute guide and follow the energy rather than the order.
WIN-LOSS INTERVIEW GUIDE — [Deal name] — [Won / Lost / No decision]
Interviewer: [Name, not the deal owner] Date: [MM/DD/YYYY] Length: 30 min
Recording consent: [Yes / No]
OPENING (2 min)
"Thank you for your time. I'm not in sales, and this isn't a sales call. I want
to understand how you made your decision so we can improve. There are no wrong
answers, and I'd rather hear the uncomfortable parts."
CONTEXT AND TRIGGER
1. What was happening in your business that made you start looking for a
solution at that point?
2. What would have happened if you had done nothing?
EVALUATION
3. Walk me through how the evaluation worked—who was involved, and what role
did each person play in the final decision?
4. Which options did you seriously consider, including keeping things as they
were? How did the shortlist form?
5. What were the most important criteria, and did they change during the
process?
OUR PERFORMANCE
6. How well did we understand your problem compared with the others?
7. Where did we come across as strongest? Where were we weakest?
8. How did our proposal, pricing, and commercial terms compare?
9. Was there a moment in the process when you felt your decision start to lean
one way?
DECISION
10. What ultimately tipped the decision? If you had to rank the top three
reasons, what would they be?
11. Who had the final say, and what did they need to see to approve it?
LOOKING FORWARD
12. If you could give us one piece of advice to win a deal like yours next
time, what would it be?
CLOSING (1 min)
"Is there anything I didn't ask that I should have?" Thank them. Confirm how
the feedback will be used and that it stays anonymized internally.
Probing tips that separate useful interviews from polite ones:
- When you hear "price," ask: "Price compared with what, and relative to what value?" Then: "If we had matched their price, would you have chosen us?" The answer often reveals the real reason.
- When you hear "features," ask for the specific use case the feature was needed for, and who on the buyer side cared.
- Ask "What else?" at least twice after the first answer to question 10. The second and third reasons are where the controllable issues live.
- Never defend, correct, or pitch. If you catch yourself explaining a feature, you have stopped learning.
Win-loss analysis template
The analysis template has two parts: a deal-level record for each interview, and a cross-deal summary that counts themes in wins versus losses. Paste them into a spreadsheet; one row per deal, one row per theme.
Part 1: Deal-level record
| Field | Example entry |
|---|---|
| Deal / account | [Account name] — [Deal name] |
| Outcome | Lost to competitor |
| Segment / deal size | Mid-market / $48K ARR |
| Stage lost | Proposal |
| Chosen alternative | [Competitor A] |
| CRM reason (rep-entered) | Price |
| Buyer's top 3 reasons | 1) Weak ROI case for CFO; 2) Competitor's onboarding plan clearer; 3) Price |
| Mapped primary / secondary reason | Value not quantified for economic buyer / Competitor's implementation story |
| Controllable? | Controllable |
| CRM reason matches buyer? | No |
| Economic buyer engaged? | No — never met, proposal not opened by CFO |
| Key quote (anonymized) | "We liked the product, but I couldn't take it to our CFO without numbers." |
| Recommended action | Add ROI calculator to proposal stage; require EB meeting before pricing |
| Owner / due | [Name], Sales enablement / [MM/DD] |
The example values above are illustrative, not from a real deal.
Part 2: Cross-deal theme summary
| Theme (from taxonomy) | Mentions in losses | Mentions in wins | Stage most seen | Controllable? | Owner | Action | Status |
|---|---|---|---|---|---|---|---|
| Value not quantified for EB | [n] | [n] | Proposal | Controllable | Sales enablement | ROI template + EB meeting gate | In progress |
| Competitor's implementation story | [n] | [n] | Evaluation | Controllable | Product marketing | Onboarding plan one-pager | Not started |
| Missing capability: [X] | [n] | [n] | Evaluation | Partly | Product | Roadmap review | Scheduled |
| Pricing model mismatch | [n] | [n] | Negotiation | Partly | Pricing / Finance | Test usage-based tier | Not started |
How to read it:
- A theme that appears in losses but also in wins (for example "price") is probably not your deciding factor. Look for themes that are frequent in losses and rare in wins.
- Compare the "CRM reason matches buyer?" column across reps. A low match rate for one rep is a coaching conversation; a low rate everywhere means the picklist or the incentive is wrong.
- Weight by stage. Five losses at proposal stage cost more than five at discovery.
How to turn win-loss findings into action by function
Win-loss only pays off when each theme lands with a team that can change something. Route findings by function, give every action an owner and a date, and report back on what changed at the next quarterly readout.
| Function | Typical findings | Example actions |
|---|---|---|
| Sales | Economic buyer never engaged; weak discovery; objections left unanswered; slow follow-up | Add an "EB met" exit criterion to the proposal stage; update talk tracks and objection handling playbooks; coach with real anonymized quotes |
| Product | Missing capability, integration gaps, usability concerns during trial | Feed verified, quantified requests into roadmap reviews (count of deals and pipeline value affected, not anecdotes) |
| Marketing / PMM | Messaging does not match how buyers describe the problem; competitor's story is clearer | Rewrite positioning in buyers' words; refresh battlecards; build proof assets for the most-cited criteria |
| Pricing / Finance | Pricing model mismatch; late-stage surprises on total cost; procurement friction | Test packaging changes; show pricing earlier; pre-approve standard contract variations |
| Sales leadership / RevOps | Poor-fit deals lost late; forecast surprises | Tighten qualification criteria; clean up the closed-lost picklist; review pipeline hygiene (see the pipeline management guide) |
| Customer success | Implementation risk cited by lost buyers | Publish a clear onboarding plan and timeline used in late-stage deals |
Two habits make this stick:
- A quarterly readout of 30–45 minutes with sales, product, and marketing leaders: top three themes, what changed since last quarter, and what each team commits to next.
- A running "you said, we did" log that ties each action to the theme that triggered it. It keeps the program funded and gives reps a reason to keep the CRM fields honest.
What to do after a lost deal: follow-up email and re-engagement timing
Send a short, gracious note within a few days of the decision, ask for feedback, and set a specific reason to reconnect later. Do not argue the decision or re-pitch.
Lost-deal follow-up email (from the rep):
Subject: Thank you — and one quick ask
Hi [First name],
Thank you for letting us know, and for the time your team put into evaluating [Company]. I know these decisions take real effort.
Two things:
1. Our [product marketing / research] team runs short feedback conversations with buyers so we can improve. Would you be open to 30 minutes with [Name]? It's not a sales call.
2. I'd like to check in around [month], after you're up and running, in case anything changes. Is that OK?
Wishing you a successful rollout.
[Name]
Re-engagement timing. Tie your next touch to an event, not the calendar:
| Situation | When to reconnect | What to bring |
|---|---|---|
| Lost to competitor | Around the end of their implementation or first renewal window (ask when that is) | What has changed in your product or offer that relates to their stated reasons |
| No decision / deprioritized | When they said priorities would be revisited—often next budget cycle or quarter | A refreshed business case using their numbers |
| Lost on a missing capability | When that capability ships | A short note showing it, addressed to the person who asked for it |
| Champion or sponsor left | When a new leader is in place (varies widely; check in periodically) | An intro to the problem, not a re-run of the old proposal |
Log the re-engagement date and reason in the CRM so it survives rep turnover.
Win-loss for small teams (no dedicated PMM)
You do not need a research team to run win-loss. A small B2B team can get most of the value with a clean picklist, five buyer conversations a quarter, and a one-hour review.
A lightweight version:
- Week 1: Replace your closed-lost picklist with the taxonomy above (a RevOps or admin task of an hour or two in most CRMs).
- Every month: A founder, sales leader, or customer success lead—anyone who did not own the deal—requests interviews on one or two recent decisions, mixing wins and losses, aiming for around five completed conversations a quarter.
- Each interview: 30 minutes using the 12 questions. Take notes directly into the deal-level template.
- End of quarter: Fill the cross-deal summary, pick the top two themes, assign one action each, and share a one-page summary with the whole company.
Trade-off to accept: an internal interviewer gets somewhat less candid answers than a third party. Offset it by being explicit that the call is not sales, by asking "what else?" repeatedly, and by checking claims against deal data.
Common win-loss mistakes
Most win-loss programs fail for process reasons, not because the interviews were bad. These are the mistakes to avoid.
- Only studying losses. You learn what to stop doing but not what to repeat. Include wins in every cycle.
- Letting reps interview their own buyers. Candor drops and the findings drift toward uncontrollable reasons.
- Trusting the CRM field as ground truth. Use it to select deals and to measure how far rep perception is from buyer reality—not as the conclusion.
- Treating "price" at face value. Probe until you know whether price was the reason or the polite exit.
- Waiting too long. Interviews three months after the decision produce vague answers.
- Making it a blame exercise. If reps fear the output, they stop entering honest reasons. Share themes, not scorecards of individual reps.
- No owner, no follow-through. A slide of themes without owners and due dates is where most programs quietly die.
- Counting quotes like statistics. Eight interviews are strong qualitative evidence, not a percentage you should put in a board deck.
Pairing interviews with deal-room engagement data
Buyer interviews tell you what the buyer remembers; engagement data from a shared deal room tells you what the buying group actually did. Used together, they make loss reasons much harder to misread.
If your team shares proposals and project materials with buyers in a digital sales room, you already have an objective record for each deal. In Terasu, for example, documents shared in a Room record who viewed what and for how long, with page-level heatmaps and per-member engagement, and a daily view trend shows when activity dropped off. That gives you questions to test in the interview:
- Did the economic buyer ever see the proposal? If the CFO never opened the pricing section, "price" may really mean "the business case never reached the person who approves budget."
- When did engagement fall? A drop right after a pricing page view or a security questionnaire points to a different reason than a slow fade after the demo.
- Which pages got attention? Heavy time on implementation or integration pages suggests where the buyer's concerns sat, even if they did not voice them.
Terasu's Stakeholder Map adds the other half: a visual map of the buying group with each person's role (such as decision-maker, champion, or technical evaluator), influence, and sentiment. Reviewing it at close—alongside the "Economic buyer engaged?" field in your template—quickly shows whether a loss was really a single-threaded deal. Treat all of this as evidence to discuss with the buyer, not a verdict on its own.
See who in the buying group actually engaged
Share proposals in a Terasu Room, see who viewed what and when, and map the buying group with a Stakeholder Map. Free plan available, or start a 14-day trial.
Start freeFAQ
What is win-loss analysis?
Win-loss analysis is a structured way to learn why buyers chose you, a competitor, or no one at all. It combines buyer interviews and surveys with CRM and deal data, codes the reasons against a consistent taxonomy, and routes recurring themes to sales, product, marketing, and pricing owners.
What are common closed-lost reasons?
Useful closed-lost reasons describe why the deal was lost, not what happened. Typical categories are value or business case, product fit, price and commercial terms, sales execution (for example, never engaging the economic buyer), competitive factors, buyer situation (priorities or budget changed), and poor qualification. Avoid outcome values like "lost to competitor" or "went dark" as reasons.
How accurate are CRM closed-lost reasons?
Often not very. In Clozd's comparison of 1,000 closed-lost deals, the rep-entered reason aligned with the buyer's interview answer only 15% of the time, and 44% of CRM reasons were outcomes rather than reasons. That is a single vendor's dataset, so treat it as directional, but it is a strong argument for verifying reasons with buyers.
Who should conduct win-loss interviews?
Someone who did not own the deal: a third-party firm, product marketing, competitive intelligence, RevOps, customer success, or a leader from another team. Buyers are more candid with a neutral interviewer, and the findings are less likely to drift toward reasons outside sales' control.
When should you do a win-loss interview?
Roughly 2–6 weeks after the decision. That is late enough that the buyer is no longer negotiating and early enough that they still remember who was involved and what tipped the decision.
How many win-loss interviews do you need?
For a first quarter, 8–15 interviews across wins, losses, and no-decision losses is realistic for most B2B teams, and even five can surface the most obvious themes. Treat the results as qualitative evidence and keep interviewing each quarter rather than trying to reach statistical significance.
Should win-loss analysis include won deals?
Yes. Wins show which strengths actually decide deals, so you can repeat them. Comparing theme frequency in wins versus losses also stops you from over-reacting to factors, like price, that come up in both.
What is the difference between win-loss analysis and lost deal analysis?
Lost deal analysis looks only at losses, usually from internal and CRM data. Win-loss analysis covers wins, losses, and no-decision outcomes and centers on the buyer's own account of the decision.
How do you follow up after losing a deal?
Send a short thank-you within a few days, ask whether the buyer would share feedback with someone outside sales, and agree on a specific reason and time to reconnect—such as after their implementation, at the next budget cycle, or when a missing capability ships. Do not re-pitch or argue the decision.


