Win-Loss Analysis Template
Why the deal went the way it did, in the customer’s words rather than yours.
Details
win loss analysis templateUploads
Your logo
A photo or picture
Goes on this page only. Drag it anywhere and pull its corner to resize it.
Your signature
Draw it with a finger, a mouse or a trackpad, and it goes on the page like a picture.
Pictures and signatures stay on this device. Nothing is uploaded to a server.
Red highlights mark what is still blank. Click anything on the page to change it. Your draft is kept on this device as you work.
| Deal | [deal] |
| Value | $ [amount] |
| Outcome | [won or lost] |
| Competing against | [who else was bidding] |
| Reviewed on | October 14, 2026 |
1. Why it went that way
[what the customer told you — ask them, do not infer it]
2. What we take from it
[add one lesson per line]
3. What changes
| Change | Owner | By when |
|---|---|---|
| [add one change per line] |
What is a Win/Loss Analysis?
A win/loss analysis records why a deal went the way it did, in the customer's words rather than the account manager's. It exists because the reason written into the CRM at close is almost always price, and price is almost always the polite answer. Done regularly it tells you which objection actually kills deals, which competitor claim you have no response to, and which part of your process buyers quietly dislike.
Product marketing teams, sales leaders and founders run these, usually as a short interview with the buyer a week or two after the decision. Both outcomes matter: wins reveal what the deciding argument was, which is often not what you thought you were selling. Companies with long cycles run them continuously against a sample; smaller teams do a batch at the end of each quarter. The interviewer should be someone other than the person who owned the deal.
Interviews create obligations. Recording one requires consent in many places and the requirements differ by jurisdiction and sometimes within a country, so check before pressing record. The notes are personal data under regimes including the UK and EU GDPR, India's Digital Personal Data Protection Act and the Australian Privacy Principles. There is a competition-law dimension too: systematically collecting competitors' pricing, and above all exchanging it with them, can raise issues under EU, UK, US, Indian and Australian competition rules. Take advice before building a competitor price database.
This is not a satisfaction survey and not a save attempt. Reopening the sale during the interview ends both the interview and the goodwill that made it possible. It is not a post-mortem for allocating blame, and it is not statistically representative — a handful of interviews shows you what to look into, not what proportion of buyers think something. It also does not explain churn: a customer who left after two years did so for different reasons than a prospect who never bought.
What to put in a Win/Loss Analysis
These are the details this template asks for. Anything left blank is marked in red on the preview so you can see what is still missing.
| Field | What goes in it |
|---|---|
| Business name | For example: Barton Supply Co. |
| Your address | For example: Unit 7, Barton Road, Columbus, OH 43212 |
| Account owner | For example: Sarah Chen |
| The deal | For example: Northgate Fit-Out — framework supply |
| Value | For example: 425,000 |
| Outcome | Free text |
| Who else was in it | For example: National Merchant Co and Pennine Timber |
| Why it went that way | For example: They bought on delivery reliability, not price — our two late deliveries in Q2 came up in… |
| What we take from it | One per line |
| Actions | One per line: Action | Owner | By when |
How to write a Win/Loss Analysis
Choose the deals and a neutral interviewer
Pick a mix of wins and losses, including the ones you think you already understand, and use someone who was not on the deal — another team, a colleague from marketing, or an outside interviewer. Buyers say things to a neutral party that they will not say to the person who sent them a proposal, and hearing it second-hand is easier for the rep too.
Ask them to walk through the timeline
Start with how the project began and what happened at each stage, rather than opening with why you lost. The narrative surfaces the moments that mattered — the internal meeting where the shortlist was cut, the demonstration that went badly — which a direct question about the reason never reaches. Let them talk, and write the detail down as they say it.
Find where it could have gone differently
Ask directly: was there a moment when the decision could have gone the other way, and what would have had to change? This is the highest-value question in the interview. Answers are usually specific and actionable — a missing integration, a reference in their sector, a response that took four days — where the general reason is neither.
Separate stated reasons from real constraints
Price is what buyers say when the answer is complicated. Probe it: was the budget available and spent elsewhere, was the value never established, or was it genuinely unaffordable? Those three need three different responses from you. Record the stated reason and your own assessment as separate fields, so nobody has to guess later which is which.
Code the answers and report the pattern
Use a fixed short list of reason codes so answers can be counted across quarters, and keep the verbatim quotations underneath — the quotations are what change minds internally. Report by segment and by competitor rather than as one total, and end with two or three specific changes rather than a list of themes.
Common mistakes
- Letting the account manager conduct the interview, which produces a polite version of events and almost no new information.
- Accepting price as the reason without probing it, which sends the whole business chasing a discount problem it does not have.
- Interviewing only losses, so you never learn which of your arguments actually wins deals and quietly stop making it.
- Waiting three months to interview, by which time the buyer remembers the outcome but not the reasoning that produced it.
- Collecting the findings and never reporting them to the people who write the product and the pitch, which turns the whole exercise into an archive.
Frequently asked questions
Who should conduct win loss interviews?
Anyone except the person who owned the deal. Product marketing, customer research, a sales operations analyst or an external interviewer all work. The requirement is neutrality and the ability to hear criticism without defending. If the team is too small to separate roles, have people interview each other's deals, and tell the buyer at the start that nothing they say will be used to reopen the sale.
How soon after a decision should I interview?
One to three weeks. Sooner and the buyer may still be in contract negotiations with the winner and unwilling to talk; much later and the reasoning fades into a tidy summary. For losses, wait until the alternative has been signed, which removes any suspicion that the call is an attempt to reverse the decision.
What questions should I ask in a win loss interview?
How the project started, who was involved, what the shortlist criteria were, how the vendors compared on each, what the deciding factor was, and what would have had to change for the outcome to be different. Keep it to six or seven open questions in twenty to thirty minutes. Resist adding a satisfaction rating, which changes the register of the conversation.
How many interviews do I need before drawing conclusions?
Enough that you start hearing the same thing without prompting, which within a single segment often happens sooner than people expect. Treat early findings as hypotheses to test rather than facts, and be careful about splitting a small sample by segment and competitor at once. Report counts honestly — four of seven buyers said this — rather than converting small numbers into percentages.
Will customers actually agree to a win loss interview?
More often than teams expect, particularly on losses, because buyers who went through a long evaluation usually want the process to have been worth something. Ask briefly, offer twenty minutes, be explicit that it is not a sales call, and have someone other than the rep make the request. A short note afterwards about what you changed makes the next request easier.
This page explains general practice and is not legal advice. Requirements differ between countries and, in some cases, between states — check what applies where the document will be used.