Running a Win/Loss Interview That Gets the Real Story
The loss reason in your CRM says price. It usually isn't the real reason, or at least not the whole reason. Deals are lost for reasons buyers rarely explain to the rep who just spent months trying to sell them something, and the only way to find out what actually happened is to ask someone who wasn't in the room for the sales process.
Why your CRM's loss reasons are almost always wrong
A rep filling out a loss reason field is working from a mix of guesswork and self-protection. Price is the easiest box to check because it doesn't implicate anything the rep did, and buyers often cite price as a polite way to end a conversation without explaining the real objection, which might be a stalled internal champion, a feature gap nobody surfaced during the evaluation, or a competitor who simply built a stronger relationship earlier in the process.
None of that shows up in a dropdown menu, which is exactly why a real interview, conducted separately from the sales process, catches what the CRM field never will.
Who should conduct the interview, and why it shouldn't be the AE
The rep who worked the deal is the worst person to ask about it, not because they'd lie, but because a buyer won't tell an invested salesperson the unflattering version of events. Have someone with no stake in the outcome, a product manager, a customer research role, or a peer AE from a different team, run the conversation instead. Frame it clearly as a research call meant to improve the product and process, not a review of the specific rep's performance, and the buyer will typically be far more candid.
The five questions that actually surface the truth
- Walk me through what happened from the first time you considered a change, to the moment you made a decision.
- What was the specific moment you decided this wasn't going to be us, and what triggered it?
- Who else was involved in the decision, and did everyone agree, or was there disagreement internally?
- What would have needed to be different for the answer to be yes?
- If you're comparing us to what you chose instead, where did we actually fall short, specifically?
Open with the narrative question first. It gets the buyer talking chronologically instead of jumping straight to a defensive summary, and the real reason usually surfaces somewhere in the middle of the story, not in the first sentence.
How to ask without sounding like a win-back pitch
The moment a buyer suspects the call is a disguised attempt to reopen the deal, they'll retreat to the same safe, vague answers your CRM already has. Say directly, early in the call, that the deal is closed and this is purely to understand the decision for internal purposes, not to change their mind. Then actually hold to that. If a genuinely reopenable issue comes up, follow up separately days later, rather than pivoting mid-interview and confirming the buyer's suspicion that the whole call was a pitch in disguise.
Turning individual interviews into a pattern you can act on
One interview is an anecdote. A dozen interviews, tagged consistently by theme, feature gap, pricing structure, competitor strength, internal champion turnover, is a pattern you can bring to product, marketing, or your own sales process with actual evidence behind it. Keep a simple shared log of every interview's key theme, and review it quarterly with the people who can actually act on what it shows, not just within the sales team that already knew something was off.
Getting past a scripted, polite non-answer
Buyers often start an interview with the same safe summary they'd give anyone: it came down to budget, or the timing wasn't right. Don't stop there. Ask a specific follow-up tied to something concrete from the actual sales process: a feature they asked detailed questions about, a stakeholder who went quiet after a certain call, a competitor they mentioned by name earlier in the cycle. A specific question about a real moment is much harder to answer with a generic deflection than an open-ended one is.
Silence is useful too. When a buyer pauses before answering a direct question, resist the urge to fill the gap with your own guess about what they mean. Let the pause sit, and the more specific, more honest answer often comes after it, once they've decided how much detail they're actually willing to share about what really happened internally.
What Good Looks Like
Every material loss, and a sample of wins, gets a real interview conducted by someone outside the deal, using a consistent set of open-ended questions, with themes logged and reviewed quarterly by the teams that can act on them.
Building The Capability (5-Stage Skill Ladder)
How to Get Started
Frequently Asked Questions
How soon after a loss should we conduct the interview?
Within a week or two, while the decision is still fresh but after the immediate disappointment or relief on the buyer's side has settled. Waiting months means the buyer reconstructs a tidier story than what actually happened, losing exactly the detail that makes these interviews worth doing.
What if the buyer declines to do the interview at all?
Respect that and don't push, but do ask if a shorter, written version would work instead, like three quick questions over email. Some of the most candid feedback comes in writing from a buyer who wouldn't have agreed to a call, since it takes less of their time and feels lower pressure.
Should we also interview buyers after a win, not just a loss?
Yes, and it's often easier since there's no awkwardness to navigate. A win interview tells you which parts of your pitch and process actually moved the decision, which is just as useful for repeating what works as a loss interview is for fixing what doesn't.
How many win-loss interviews do we need before a pattern means anything?
There's no fixed number, but avoid drawing conclusions from fewer than eight to ten interviews in a given segment. A couple of loud, specific complaints can feel like a trend when they're really two outlier accounts with an unusual situation. Tag each interview by theme, and wait until the same theme recurs across several buyers before acting on it.
About the numbers
This guide doesn't quote a sourced benchmark. Figures in it are estimates or general guidance, so check them against your own numbers.
Related Guides
Running Exit Interviews That Get Past the Polite Excuse
A question order and coding method for customer churn interviews that gets past budget as the reason, so you can act on what actually happened.
How Enterprise Deal Cycles Are Actually Changing
What's genuinely changing enterprise deal velocity right now, from AI-assisted buying committees to procurement automation, and what hasn't changed at all.
Negotiating Indemnification Caps Without Losing the Deal
A decision guide for setting a reasonable indemnification cap and carve-outs on enterprise contracts, checked against real insurance coverage.
Running a Quarterly Pipeline Scrub Without Losing Real Deals
A repeatable process for clearing dead deals out of your pipeline every quarter, without accidentally purging opportunities that just need a longer timeline.
Executive Sponsorship: When to Put Your CEO on a Late-Stage Deal
When bringing in your own CEO or a senior executive actually helps close an enterprise deal, and the specific situations where it backfires instead.
Closing Deals Around Your Customer's Budget Deadline
How to time and structure a deal around a buyer's use-it-or-lose-it fiscal year budget, without pressuring them into a purchase that falls apart later.