How to Run a Win/Loss Analysis: Step-by-Step Guide

Author: Inputly

What is a win/loss analysis?

A win/loss analysis is a structured review of the deals you closed and the deals you lost, built from interviews with the people who actually decided, not from the gut feeling of the rep who ran the deal. Its output is a ranked, evidence-based answer to one question: why do buyers choose us, and why do they choose someone else. A useful analysis covers product gaps, pricing, onboarding, sales process, competitive pressure and timing. It is the buyer-side counterpart to voice of customer work, with one clear difference: VoC listens to customers you already have, win/loss listens to everyone who was in the room when the decision happened, including the people who walked away.

Why does win/loss analysis matter?

Because the internal version of the story is biased. Reps rationalize losses, buyers soften their feedback, and CRM reason codes like "no budget" or "no decision" hide the real causes. Most teams report price and timing as the top loss reasons while buyers describe a failure to prove value, a missing integration, or a slow and confusing evaluation. When those two stories drift apart, you spend the next quarter building the wrong thing, discounting to save deals you were never going to win, and losing customers to the same avoidable causes, which is how churn compounds over time. Win/loss evidence also feeds the backlog honestly, because it gives you demand data for prioritizing feature requests that did not come from your loudest existing account.

How do you run a win/loss analysis?

1. Choose the window and the sample. Review the last two quarters and include wins, losses and no-decisions. Interviewing only losses tells you what to fix and never what to protect.
2. Own it outside sales. Product, research or a founder should run the program. A rep interviewing their own lost deal learns politics, not reasons.
3. Ask within 90 days. Memory decays fast. Invite within a month or two of the decision, while the evaluation is still sharp.
4. Use a script and open questions. Keep the buyer talking and resist defending the product.
5. Record and tag every call. Code each transcript by theme: product gap, pricing, integration, trust, implementation, support, timing.
6. Report themes with counts. "Eight of twenty buyers raised SSO" is a decision. "We heard some SSO feedback" is a mood.
7. Route the output. Product takes gaps, marketing takes messaging, sales takes objections. Then tell the team what changed, the same discipline that makes closing the feedback loop work with existing customers.

Who should you interview and how do you get them to talk?

Interview the decision maker or the strongest champion, not only the friendly evaluator who liked the demo. Offer 25 minutes, say plainly that the call is research and not a sales pitch, and explain what you will do with the input. In lost deals, a small incentive lifts response rates. Expect to hear back from roughly a fifth to a third of the buyers who left, so build the ask into a routine rather than treating each interview as a favor. Two people should be on the call: one to ask the script and one to take notes, so the conversation keeps its pace and nothing gets lost in a rushed summary.

What questions should you ask in a win/loss interview?

| Stage | Question | | --- | --- | | Decision process | Walk me through how you evaluated the options. | | Criteria | What mattered most when you compared us? | | Alternatives | Who else was on the shortlist, and why? | | Product | What did you expect us to do that we did not? | | Proof | What convinced you, or what was never proven? | | Price | How did pricing feel next to the value you saw? | | Outcome | What would have changed your decision? |

Keep the questions open and let silence do work. The discipline is the same one that makes good user interviews useful: ask about behavior and past decisions, not about intentions or hypothetical features. When you hear a product gap, ask what the buyer did instead, since workarounds, spreadsheets and competitor features tell you how urgent the need really was. When you hear price, ask what value they expected to see proven before the number felt fair.

What are common win/loss analysis mistakes?

• Interviewing only losses. You lose the pattern behind what actually wins deals.
• Letting the rep write the summary. It becomes a defense of the deal, not a read on the buyer.
• Asking closed questions. Yes and no answers give you nothing to tag or count.
• Treating one loud loss as a trend. One angry buyer is an anecdote until four more say the same thing.
• Running it once. Buyers, competitors and pricing change, so the analysis is a quarterly habit, not a project.
• Never sharing the findings. If the team sees no change, nobody keeps volunteering time for interviews.

Frequently Asked Questions

1. Can a small team run this without a research budget? Yes. Ten interviews, a spreadsheet and one owner cover the basics. Start with the deals you lost for reasons nobody can explain.
2. Should you interview no-decisions too? Always. Deals that stall often hide the clearest signal, since the buyer cared enough to evaluate and still found no reason to move.
3. How do you keep it from becoming a sales blame exercise? Report themes and counts, never names tied to losses, and frame the program as learning about buyers rather than grading reps.
4. How does this connect to the roadmap? Themes with counts become inputs next to your request board, so roadmap debates compare evidence from buyers with evidence from users instead of opinions from whoever is in the room. A customer journey map helps you see where in the evaluation each theme showed up.
5. What is a realistic cadence? Interview continuously as deals close, review themes monthly, and publish a short quarterly summary with the top five reasons for wins and losses.

Turn every closed deal into evidence instead of opinion. Collect the reasons on a shared board, let your team see the patterns, and start on Inputly for free.