Skip to content
Faisal Mahmud TusherDigital marketing, SEO & analytics
with Faisal Tusher

Templates

Win-Loss Review Template

A win-loss review template: the deal and outcome, who was interviewed, alternatives weighed, what decided it, coded reasons, themes, owners and changes made.
Templateintermediate10 min readUpdated

What this template is for

Use the record for every win-loss interview, and the roll-up whenever enough interviews have accumulated to read patterns, at the cadence product, sales and marketing leadership agree. The sales content and training guide describes the programme in one section: buyers interviewed after a decision, both those who chose the product and those who did not, by someone other than the representative; a short conversation on how they found the company, the alternatives, what mattered, how each option performed and what decided it; and themes reviewed with leadership, each assigned to an owner. It records that the Product Marketing Alliance treats win-loss analysis as a core product marketing practice. The guide to researching business buyers covers reaching each role in a Buying Committee, confidentiality and lost prospects.

The review sits beside other documents rather than replacing them. A Win Rate says how often deals are won; the review says why. The competitor analysis template compares competitors from desk evidence, reviews and interviews, and takes win-loss notes as one input to its customer view. Competitive battlecards arm sellers against one competitor and draw their why-we-win and why-we-lose sections from themes this review produces. The messaging house holds the messages a win theme may change. The general customer interviews tutorial holds the discussion guide and interviewing technique; this template records what the interview found, not how to conduct it.

The template

The first seven fields make one record per interview. The last two are filled across interviews, in a roll-up kept with the records. Copy the table into the programme's working document and keep the field names, so records from different interviewers can be read together.

FieldWhat to write
Deal and outcomeThe opportunity, segment, stage reached, the outcome and, for a loss, the alternative chosen as the buyer named it
Interviewee and roleWho was interviewed, their role in the purchase and what their position lets them answer
Invitation and consentHow the buyer was approached on a research footing, what they were told and agreed to, and who may see the notes
How they found and judged usHow the buyer came across the company, the alternatives they weighed and what mattered most, in their words
How each option performedHow each alternative did on the things that mattered, including doing nothing or doing the job another way
What decided itThe moment or reason the buyer names as decisive, kept separate from the seller's account of the deal
Coded reasonsEach reason given, coded to a short shared list so interviews can be counted together
Themes and ownersPatterns across interviews, each assigned to an owner in product, product marketing, sales or marketing
Changes madeWhat changed because of each theme, such as a battlecard, a demo step, a message or a target segment, and when

Keep each record to a page, with the buyer's words quoted where they matter. Recordings and full notes sit elsewhere, under the access rules the consent field sets.

How to fill each section

Deal and outcome

Copy the facts from the CRM: the account, the segment, the stage the deal reached, the outcome and the representative. For a loss, write the alternative the buyer chose in the buyer's words, which may be a competitor, a build of their own, or doing nothing. The sales content and training guide sets out why interviews are more reliable than opportunity notes, so note the CRM's recorded reason here too; the gap between it and the buyer's account is one of the review's findings. Select deals for interview by a rule, not by which representative volunteers, so the records are not a sample of the friendliest accounts.

Interviewee and role

Record the person's role in the purchase, not only their job title. The business-buyer research guide tabulates what each role can and cannot answer: users know how the product fits daily work, the champion knows why the search started and who resisted, the approver knows what the business case had to show, and procurement knows how suppliers were compared. Note which roles the interview did not reach, because a finding from one role is one part of the decision. Long sales cycles make memory fade, so note how long after the decision the interview took place.

Write how the buyer was approached, what they were told and what they agreed to. The business-buyer guide asks that lost prospects are contacted on a research footing only: the invitation promotes nothing and taking part does not reopen the sale. It also notes that participants speak about an employer, under that employer's rules on what may be shared and what may be accepted as a thank-you. The tutorial on participant information and consent prepares the information, the consent statement for each use, such as quoting the buyer internally, and the separation of identities from notes. Record who may read the notes; buyers often say more when the representative will not see their name beside a criticism.

How they found and judged us

Record, in the buyer's words, how they came across the company, which alternatives they weighed and what mattered most to them. This field is the core of the interview the customer interviews tutorial prepares for, and it is where buyers name criteria the seller never heard. Keep the buyer's language rather than translating it into product terms; that language is what messaging and battlecards later reuse.

How each option performed

For each alternative, record how the buyer felt it did on the things they said mattered. Include doing nothing and doing the job another way, such as a spreadsheet or an existing system, which often win more deals than any competitor. Themes from this field feed the why-we-win and why-we-lose sections of competitive battlecards, which ask that each claim be traceable to its source; keep the record's reference so it can be.

What decided it

Write the moment or reason the buyer names as decisive, separately from the representative's account of the deal. The jobs-to-be-done framework helps here: its switch interview walks back from the decision to the first thought and listens for the workarounds, the anxieties that nearly stopped the purchase and the people involved. A decisive reason is often an anxiety resolved or unresolved, such as doubt about implementation, rather than a feature.

Coded reasons

Code each reason the buyer gave to a short, shared list, so that interviews can be counted together. The tutorial on coding open-text answers gives the method: codes with a definition, an exclusion and an example, a second person coding a portion to check the frame is applied the same way, and counts of interviews per code rather than mentions. Allow more than one code per interview, and mark which reason was decisive. Keep the list stable between rounds, adding codes only when a new reason genuinely appears.

Themes and owners

Across interviews, read the codes for patterns, and give each theme one owner. The sales content guide gives the routing: a missing capability goes to product, a confusing demo to product marketing, a pattern of losing to one competitor into the battlecard, and a win reason the messaging does not mention may be a positioning opportunity. The sales and marketing alignment guide makes closed-lost reasons part of the feedback loop between the two teams; this review is where the buyer's version joins that loop. Write how many interviews support each theme beside it, and say when a theme rests on too few to act on.

Changes made

Record what changed because of each theme and when: a battlecard section rewritten, a demo step changed, a message added, a training session, a product request. Some themes point further. Wins that cluster in one type of account can sharpen the Ideal Customer Profile, and the tutorial on building an ideal customer profile adds reasons from win-loss notes to the numbers. A win reason the position does not claim, or losses where buyers cannot say what sets the company apart, are signs the guide to refreshing a positioning treats as evidence. A theme with no change recorded by the next review is the review's unfinished business.

Filled example

Below, the review is completed for an invented business. The figures, dates and results are illustrative.

Illustrative example — not a real result

Fyrnlode Rota Software: a quarter of win-loss interviews

Fyrnlode Rota Software is an invented company selling staff rota software to care homes. Its product marketing manager interviewed 14 buyers in one quarter, 8 losses and 6 wins, within six weeks of each decision. One loss record is shown in full, followed by the quarter's roll-up.

FieldFyrnlode's record
Deal and outcomeA group of four care homes, mid-size segment; reached the final demo; lost. Buyer's alternative: "the system our sister group already uses". CRM reason recorded by the representative: price
Interviewee and roleThe group's operations manager, the champion, who ran the evaluation and presented it to the owner. Did not reach the owner who approved the purchase or the home managers who would use it
Invitation and consentInvited by email from product marketing, stating the conversation was research, nothing would be sold and the deal would not be reopened. Agreed to a recorded call and to anonymised quotes being used internally; notes readable by product marketing and the head of sales, not by the representative
How they found and judged usFound Fyrnlode through a care sector newsletter. Weighed Fyrnlode, the sister group's system and staying with spreadsheets. "What mattered was whether night staff could swap shifts without ringing me"
How each option performedFyrnlode: strongest on reporting, "the demo of swaps was confusing; it took three screens". Sister group's system: simpler swaps, weaker reports, known to staff. Spreadsheets: free but "I'm the bottleneck"
What decided itThe shift swap demo. "I couldn't picture a carer doing that on a phone at 3am." Price was mentioned only when asked
Coded reasonsDecisive: DEMO-SWAP (shift swap shown as complex). Also: FAMILIAR-ALT (alternative already known to staff), PRICE (mentioned when prompted)

Quarter roll-up, across the 14 interviews: DEMO-SWAP appeared in 5 of 8 losses and was decisive in 4; PRICE appeared in 3 losses and was decisive in none, although the CRM recorded price as the reason for 6. ONBOARD-SUPPORT (help setting up rotas in the first weeks) appeared in 5 of 6 wins and in none of the messaging.

FieldFyrnlode's roll-up
Themes and ownersShift swaps shown as complex in the demo: product marketing manager. Onboarding support as a win reason missing from the messaging: head of marketing. Price over-recorded as the loss reason: head of sales, with the revenue operations lead
Changes madeDemo rebuilt to show a swap on a phone in one screen, and representatives trained, by 14 May. Onboarding support added as a proof point under the ease-of-use pillar in the messaging house, 2 June. Closed-lost field gained a "demo" option and a required note, 20 May. Battlecard against the sister group's system updated with the swap comparison, 21 May

At the next quarter's review, DEMO-SWAP appeared in 1 of 7 losses, and two buyers who won cited the onboarding support they had read about on the website.

Common mistakes

  • The representative runs the interview. Buyers soften criticism for the person who sold to them. Use product marketing or an independent researcher, and keep the representative's account in its own field.
  • Interviewing only losses. Without wins there is no way to tell whether a loss reason is also common among buyers who chose you, and win reasons the messaging misses go unheard.
  • Trusting the CRM field. A closed-lost reason chosen from a dropdown at the end of a deal is the seller's summary. Record it, then compare it with the buyer's account.
  • Reasons left uncoded. Records that are only notes cannot be counted, so themes become whichever stories were most memorable. Code every reason to a shared list.
  • Treating one role as the whole decision. A champion's account misses what the approver weighed. Note the roles each interview reached and did not.
  • Themes without owners or dates. A theme that is not owned becomes a slide in a quarterly deck. Give each one an owner and record the change made.
  • Using the interview to reopen the sale. It breaks the research footing the buyer agreed to and makes the next buyer less willing to talk.

The competitor analysis, messaging house and other templates that take this review's themes are in the templates library.

Frequently asked questions

Who should run win-loss interviews?

Someone other than the representative who ran the deal, usually product marketing or an independent researcher. The site's sales content guide notes that representatives record what they believe happened while buyers describe what did, and buyers speak more freely to someone without a stake in the sale. The representative still contributes: their account of the deal goes in the record beside the buyer's, so the two can be compared.

Should we interview wins as well as losses?

Yes. Losses show what to fix, but wins show what is working and often reveal reasons the messaging never mentions, which can be a positioning opportunity. Interviewing only losses also makes every theme sound like a problem, and it hides whether a reason given for a loss is just as common among wins.

Can the interview be used to win the deal back?

No. Lost buyers are approached on a research footing, as the site's business-buyer research guide describes: the invitation promotes nothing and taking part does not reopen the sale. If a buyer asks to talk to sales during the interview, note it and pass it on afterwards with their agreement, but the interview itself stays research.

Terms used on this page

Frameworks

Where this page is used

Also related

Sources

  1. Product Marketing Alliance — Product Marketing Alliance
  2. Market Research Society — MRS

Related