Win-Loss Interview Questions Template
Four documents and three sheets that join what the rep logged at close to what the buyer actually said, deal by deal.
Free download · No account needed
Rep-reported versus Buyer-reported Reason
Before a Single Interview Is Coded
Every closed-lost deal holds two reason codes once an interview completes: what the rep logged at close, and what the buyer confirmed.
| Deal | |
|---|---|
| Rep-Logged Reason (CRM) | |
| Buyer-Confirmed Reason (Interview) | |
| Match? |
The two codes are not always the same thing, and the gap between them is usually where the actual finding is.
Every win-loss template on page one gives you a CRM-linked deal log and an interview script for buyers. One of them, Oden's, states the finding in words: sales reps have one view of why deals close, buyers have another. It stops there, telling you to interview both, with nowhere to put both answers on the same row. Amberfield Systems, a fictional supply-chain vendor, ran 28 buyer interviews on a quarter's closed-lost deals. Reps logged Price as the reason on 13 of 28, 46.4%. Buyers confirmed Price as the actual driver on just 5, 17.9%.
This pack's Rep-reported versus Buyer-reported Reason sheet is that missing row: the rep's code at close and the buyer's confirmed code, side by side, with a match flag. Interviews scheduled two to four weeks after close catch the decision while memory is still accurate. Coding then waits for a follow-up question past the buyer's first answer, since a first answer defaults to whatever is easiest to say. Pushed one question further, 7 of Amberfield's 13 rep-logged Price deals turned out to be Unclear Differentiation, a category the CRM's picklist has never had.
Theme Frequency then checks every confirmed reason against that picklist: 53.6% of this quarter's confirmed causes could never have been logged at all. Recommendation Note routes each theme to an owner by the ARR behind it, and keeps a competitor's name separate from a reason. Three deals logged as Lost to Competitor confirmed a scheduling delay and a missing report, not anything the competitor did differently. A pattern tied to the same named competitor more than once belongs on the competitive battlecard instead of staying a one-off line here.
What's in the pack
Interview Guide
The fixed four-part flow, the two-to-four-week timing window, and why a confirmed reason waits for a follow-up question past the buyer's first answer.
Interview Register
Every contacted deal, its rep-logged CRM reason, and whether the interview completed, was declined, or never got a response.
Synthesis Report
The worked Amberfield write-up in full, including the reclassification that moved 7 deals off price and onto a reason the CRM had no field for.
Rep-reported versus Buyer-reported Reason
The join: both codes on the same deal, a match flag, and one sentence on what the buyer actually said when the two disagree.
Theme Frequency
Every confirmed reason aggregated by deal count and ARR, flagged against whether the CRM's own picklist has ever had that option at all.
Recommendation Note
Each theme routed to the team that can act on it, ordered by ARR at stake. The largest theme, differentiation buyers cannot articulate, routes into the positioning canvas rather than a pricing conversation nobody needed.
How to use it
- 1
Send your closed-lost export
Or take it blank and replace the worked example, 28 interviews on a fictional supply-chain vendor's quarter, with your own deals and their rep-logged CRM reason.
- 2
Interview buyers on the fixed flow
River runs the four-part sequence and holds the buyer's first answer separate from the confirmed reason until a follow-up question has been asked.
- 3
Read the join, not just the average
Rep-reported versus Buyer-reported Reason shows the match rate and names the single biggest reclassification, rather than one blended agreement percentage.
- 4
Route each theme by ARR, not by deal count
Recommendation Note orders themes by ARR at stake and keeps a confirmed mechanism separate from a competitor's name, so the fix reaches the team that can act on it.
Frequently asked questions
Is this template free, and what format are the downloaded files?
Free, and the download is not cut down. The zip holds all seven files, four documents in Word and three sheets in CSV, no signup and no card required. Edit with AI is the optional half: send River your own closed-lost export and interviews, and it runs the same join on your deals. Every pack sits in the template library.
What does Edit with AI actually do?
It installs this pack as a private Space and asks for your closed-lost export with the rep-logged reason already on it. As interviews come in, it codes the confirmed reason from the follow-up answer, joins it to the rep's code, and writes each mismatch into Theme Frequency and Recommendation Note.
Why doesn't a rep's logged reason match the buyer's confirmed reason more often?
Because the rep logs a reason from what the buyer said in the room, often a first, unprompted answer like price. This pack's own worked quarter shows the pattern: reps logged Price on 13 of 28 deals, but a follow-up question reclassified 7 of those 13 to Unclear Differentiation once the buyer could not say what set the alternative apart.
Why doesn't "lost to competitor" ever count as a matching reason?
Because a competitor's name records who won, not why. On this pack's own worked quarter, the three deals logged as Lost to Competitor confirmed a missing report and Amberfield's own scheduling delay during the evaluation. Neither cause was something the competitor did, so neither counts as a match against that label.
Why does Unclear Differentiation route to Product Marketing instead of Pricing?
Because most of those buyers had already been logged as lost on price, and pushing past that answer found no distinct claim they could recall, not a number they balked at. The fix belongs in a sharper messaging framework, not a discount that would not have changed the outcome.
How many interviews do I need before a theme is worth acting on?
This pack's own worked quarter ran 28, enough to separate a theme with 11 deals behind it from one with 2. A theme with only one or two confirmed deals is worth watching, not restructuring a roadmap or a price list around, until the next quarter's interviews either confirm or drop it.
Find out whether the rep's reason and the buyer's reason actually agree
Send your closed-lost export with the rep-logged reason on it. River joins it to your buyer interviews and shows where the two disagree.
Edit with AI