Win/Loss analysis template
Most win/loss programs are a dropdown the rep fills in at close, and "price" wins that dropdown every time because it is the least uncomfortable answer. Real win/loss data comes from the buyer, gets coded against a fixed taxonomy by someone other than the rep, and is sampled on a rule instead of whoever agreed to talk. This template gives you all three.
Download it
What you get
- A buyer interview guide with opening, decision-process, and competitive questions plus the probes that get past the polite answer
- A reason taxonomy with codes and definitions, so two coders tag the same interview the same way
- A coding sheet that records primary and secondary reasons with a verbatim quote as evidence
- A sampling rule covering wins, losses, and no-decisions so the sample is not just the friendly accounts
- A quarterly tally table that compares what reps said against what buyers said
Who it's for
- RevOps and product marketing leads who own the win/loss program
- Sales leaders who suspect the CRM closed-lost reasons are not telling the truth
- Product leaders deciding which gaps actually cost deals
What's inside
6 sections, each listed with its own size. The first is previewed below; the remaining 5 come with the download, with blank rows ready to fill in.
| Section | Size | Previewed |
|---|---|---|
| Buyer interview guide | 3 columns, 6 worked example rows | Below |
| Reason taxonomy | 4 columns, 8 worked example rows | In the download |
| Coding sheet | 10 columns, 3 worked example rows | In the download |
| Sampling rule | Guidance notes | In the download |
| Quarterly tally | 6 columns, 6 worked example rows | In the download |
| Coding and reporting rules | 9-point checklist | In the download |
Preview of section 1
Buyer interview guide
Run it in 30 minutes. Ask the questions in order; the probes are for when the first answer is vague or polite.
| Section | Question | Probe |
|---|---|---|
| Trigger | What was happening in your business that made you start looking? | Who first raised it, and what would have happened if you did nothing? |
| Shortlist | Which options did you consider, and how did you narrow the list? | Was anyone eliminated before a demo? Why? |
How to use it
1. Fix the taxonomy before the first interview
Agree the reason codes with sales, product, and marketing up front and do not add codes mid-quarter. If a reason does not fit, code it Other with a note and review the Other pile at quarter end. A taxonomy that changes every month cannot show a trend.
2. Sample by rule, not by availability
Pick deals from the sampling rule the week they close. Interview within 30 days, while the buyer still remembers the shortlist. Do not let the rep choose which buyers get called.
3. Keep the rep out of the interview
The interviewer should be RevOps, product marketing, or an outside party. Buyers will not tell the person who sold to them that the discovery call felt scripted.
4. Code from evidence, then compare to the CRM reason
Two people code each interview independently from the transcript and reconcile disagreements. Then put the buyer's primary reason next to the rep's closed-lost reason. The gap between the two columns is often the most useful finding in the program.
5. Report patterns only when the count supports them
Do not present a reason as a trend until it appears in several deals in the same segment. One vivid loss story is an anecdote; report it as one.
Frequently asked questions
What is a win/loss analysis?
A structured review of closed deals, usually through buyer interviews, that codes why each deal was won, lost, or ended in no decision. Its value comes from comparing coded reasons across many deals, not from any single story.
What questions should you ask in a win/loss interview?
Ask what triggered the search, how the shortlist was built, who made the final call, which criteria mattered most in the end, how our process compared with others, and the one reason for the final choice. Follow up with "if price had been equal, would the decision have changed?"
Who should conduct win/loss interviews?
Someone other than the rep on the deal, typically RevOps, product marketing, or an outside interviewer. Buyers are more candid when they are not criticising the person who sold to them.
How many deals should be in a win/loss analysis?
Enough per segment that one deal does not swing a pattern. Use a fixed sampling rule (all large deals plus a random sample of the rest, including wins and no-decisions) and pool quarters if volume is low.