The program exists because the reasons reps record at close and the reasons buyers actually acted on usually disagree. Win-loss analysis is the system for reconciling the two and turning the gap into action.
Win-loss analysis is a structured review of closed-won and closed-lost deals that combines post-close buyer interviews with CRM data analysis. It identifies why buyers chose or rejected a vendor, groups the findings by segment, product gap, competitor, and pricing, and feeds those themes back into product, sales, and marketing. The program runs quarterly against a sample of deals above a size threshold.
The six things to know about a win-loss program before you commission interviews or stand up the CRM workflow, including who should actually run it.
Win-loss analysis pairs a structured post-close conversation with the buyer with a quantitative read of the lost-reason field and win-rate data in the CRM. One source is narrative and sampled, the other is coded and complete. Both are needed because each one lies in a different direction.
A program that interviews only lost deals produces a list of complaints and no model for what actually makes the team win. Mature programs cover both closed-won and closed-lost at a ratio of roughly one won to two lost, so the themes include the reasons buyers chose the product, not just the reasons they walked.
An external firm removes the rep-sympathy bias and buyers tell them more. Internal RevOps or sales enablement runs it cheaper and faster but has to work hard to earn candor. Most programs start internal and graduate to a hybrid where a firm handles the interviews and RevOps owns the data and the quarterly review.
The deliverable is a themed report grouped by segment, product gap, competitor, and pricing, with evidence quotes under each theme. Transcripts live in the CRM for drill-down. The report ends with three to five committed actions that go to product, enablement, and marketing with named owners and dates.
Themes about missing capability go to product as a prioritized roadmap input. Themes about competitor claims and pricing objections go to enablement as compete and discounting updates. Themes about which segments buy and which do not go to marketing to tighten targeting and ICP.
The CRM has to carry the quantitative half. A required lost-reason field on every closed-lost deal, plus a workflow that routes qualifying deals into an interview queue, plus a transcript attachment on the opportunity record. Without the plumbing the program never scales past the first quarter.
The question of who runs win-loss decides almost everything else about the program: the candor you get from buyers, the speed of the quarterly cycle, and the budget line it sits on. The three common models all work, but each has a tradeoff that leadership should understand before signing off.
A specialist firm runs interviews with your buyers under their own brand. Buyers tell an outsider things they would never tell your reps, especially about trust, process, and competitor claims. Cost usually runs $800-$1,500 per interview and the firm delivers themed reports on a quarterly rhythm.
Sales ops or RevOps runs the interviews, usually by a dedicated analyst or a part-time program lead. Costs almost nothing in cash, costs real headcount time, and depends on the interviewer being someone the buyer does not confuse with a rep. Works best for mid-market teams with a disciplined owner.
Enablement runs the interviews so the loop into coaching, battle cards, and compete content is short. Risk is the same as internal RevOps on buyer candor, plus the structural question of whether enablement should be investigating losses on behalf of the reps it also trains. Clean separation matters.
Most mature programs land here. An outside firm runs the interviews so buyer candor is high. RevOps owns the CRM data, the quarterly report, and the action tracker. The firm supplies narrative, RevOps supplies the quantitative frame, and the quarterly review brings both into one meeting.
The rep who worked the deal cannot interview the buyer. The buyer will soften the real reason, the rep will hear what they want to hear, and the data will reinforce the account team's existing story. The account owner contributes context before the interview, not the interview itself.
Programs die when win-loss is "a few people's side project." One named owner, usually in RevOps or product marketing, holds the sample list, the interview schedule, the themed report, and the action tracker. Every program that survives three quarters has that single owner.
A good win-loss interview is a 30 to 45 minute structured conversation with the economic buyer or primary evaluator. The framework below works for both won and lost deals with minor wording changes. Keep the questions open, the follow-ups patient, and the interviewer out of defense mode when the buyer criticizes the product or the process.
The interviewer opens by explaining this is a learning conversation, not a sales call. No one will contact them about buying. The findings go into aggregate research, with quotes attributed only on explicit permission. Framing the call this way is what unlocks the honest version of the story.
Why did the buyer look at the category in the first place? What problem were they trying to solve, how long had it been a problem, and what prompted the search right now? The trigger answer separates buyers with real urgency from buyers who were doing research. The pattern across interviews is marketing gold.
Which vendors did the buyer consider, and how did they end up on the shortlist? Which were ruled out early and why? The answer tells marketing what categories buyers are comparing you to and which content or source first introduced the vendor name.
What criteria did the buyer use to decide? What weight did each criterion carry? Which ones were stated out loud in the process and which ones mattered privately? Buyers often reveal a quiet criterion, trust or vendor stability, that no RFP captured but that drove the choice.
On each criterion, how did the vendors compare? Where did each strongly win or lose? This is where buyers reveal whether a competitor overpromised, where your demo missed, or where a pricing structure confused the committee. Specific, criterion-level comparison beats generic "who won" answers.
What single factor or event tipped the final decision? A particular reference call, a demo moment, a pricing concession, a security review, a champion's recommendation? Many deals are decided on one specific event the losing vendor never saw. Finding those moments is the point.
If the losing vendor had done one thing differently, would it have changed the result? This question gets the buyer to volunteer the actionable gap, which is usually more specific than the rep's version. For won deals, the inverse: what could have cost you the deal that you narrowly avoided?
For won deals, how is adoption going and was the sales promise accurate? For lost deals, is the chosen vendor delivering as promised? Both answers calibrate how durable the win or loss really was, and whether a lost deal is already turning into a reclaimable account.
A win-loss report that lists reasons without grouping them cannot be acted on. The output is organized along the axes the business already uses for decisions: segment, product, competitor, and pricing. Within each axis the themes are ranked by frequency and by deal value, so the top three themes capture most of the signal.
Win rate and loss themes grouped by segment, size, geography, and vertical. Marketing and leadership read this to decide which segments are ICP and which are a lead-gen bill. A segment with high loss rates and loss themes that cluster on "no decision" rarely becomes a good market with more marketing spend.
Themes grouped by missing or weak capability. Each theme includes the frequency, the deal value lost against it, and three to five buyer quotes. Product reviews the list quarterly and decides which gaps become roadmap. The report replaces anecdotal "we need this" lobbying with evidence.
Win rate against each named competitor, the arguments that beat you most often, and the ones you win on when you lean in. Compete content, battle cards, and discount guidance all read from this axis. A spike in losses to one competitor is a quarterly action, not an annual review item.
Themes grouped by pricing objection: packaging confusion, discount expectations, total-cost perception, procurement blocks. The report separates true price losses from losses coded as "price" that were really trust, process, or product fit. The pricing committee reads this; the compete team reads this; neither reads it alone.
A theme few programs run but most should: how the sales process itself showed up in the decision. Was the demo compelling? Did the rep multi-thread? Did security and legal reviews move at the right speed? Process themes feed enablement and sales management directly.
The axis that programs skip and should not. Across won deals, what consistently showed up: a specific champion profile, a particular trigger, a demo moment, a reference call. The winning pattern is as valuable as the losing pattern because it tells sales what to replicate.
Win-loss analysis is only worth running if the themes become action. Programs die when the report lands in an inbox and no one has committed to doing anything about it. The quarterly review is the forcing function: product, sales, marketing, and leadership in one room, with the report and the action tracker from last quarter on the table.
Product reviews the capability-gap themes and decides which ones become roadmap items for the next cycle. The report format matters: frequency, deal value lost, buyer quotes. "We need this feature" without evidence becomes an opinion. The win-loss report converts opinions into prioritized inputs with numbers behind them.
Enablement reviews competitor and pricing themes and ships updated battle cards, discounting guidance, and objection handling the same quarter. Process themes feed coaching plans. The win-loss cycle shortens from annual to quarterly, which is what makes compete content actually useful instead of six months stale.
Marketing reviews segment themes and decides which segments to lean into, which to pull back from, and where the messaging is pulling in deals the product cannot close. Attribution loops close here: the leads marketing is proud of are the ones that convert, not just the ones that fill a stage.
Leadership reads the report for the signals pipeline coverage cannot show: positioning drift, pricing threat, competitor momentum, ICP shift. The quarterly review is often the first place leadership sees a positioning problem before it shows up in the forecast two quarters later.
Every quarterly review opens with the action tracker from last quarter. Which commitments were shipped, which slipped, which were killed on purpose. Without the tracker the program becomes a reporting ritual with no accountability. With it, win-loss becomes one of the highest-trust meetings on the leadership calendar.
A quarterly deep review for themed analysis and committed actions, plus a monthly scan of the lost-reason data for spikes that need faster response. A sudden shift in competitor losses or a new product-fit theme does not wait for a quarterly cycle. The two cadences stack cleanly.
A win-loss program without CRM plumbing lives on a spreadsheet and dies when the owner leaves. The configuration below is the minimum that makes the program durable: a required lost-reason field, a routing workflow for interview candidates, and an attachment surface for transcripts and themed reports. Set once, pays back for years.
A required picklist on every closed-lost deal with six to ten mutually exclusive options and a required free-text detail field. The CRM blocks the stage transition to closed-lost until both are filled. The field is the quantitative half of the program and is what makes themed analysis possible across hundreds of deals.
A short required field on closed-won deals that captures the primary reason the buyer chose. Three to five options, aligned to the loss categories so comparison is clean. Mature programs track "primary win driver" and "primary competitor avoided," which make the won-versus-lost axis of the report possible.
A workflow that sets an "interview candidate" flag on deals that exceed a size threshold, hit a target segment, or involve a strategic competitor. The flag drops the deal into an interview queue the program owner works down each week. Nothing in the process depends on a rep remembering to nominate.
A dedicated view of flagged deals grouped by status: pending outreach, outreach sent, scheduled, completed. The queue runs on the same CRM so the deal context is one click away. The program owner works from the queue the same way a rep works a sales pipeline.
The transcript or interview summary is attached to the opportunity record. Future reps who open the account see the win-loss history for that account. Product reviewers who drill into a theme can read the specific interview behind the quote in the report. Nothing is in a shared drive that disappears.
The themed report is both a quarterly PDF with the narrative themes and a live dashboard with the quantitative cuts: win rate by segment, loss reasons by competitor, lost deal value by product gap. The report is for the review; the dashboard is for the day-to-day owner and the readers who want to drill.
Strkr enforces the required lost-reason field, auto-flags interview candidates by value and segment, and attaches transcripts to the opportunity record. Pricing is published. The platform tour shows the workflow end to end.
The lost-reason field is a coded value a rep sets at the moment of close. Win-loss analysis is the full program: the field plus post-close buyer interviews plus a themed quarterly report plus a committed action tracker. The field is the quantitative input, interviews are the narrative input, and the analysis is what reconciles the two for product, enablement, and marketing.
Twenty to thirty is the typical band for a mid-market team. Enough to find patterns, not so many that the program drowns in logistics. Mix roughly one won deal for every two lost deals, weight the sample toward larger deals and strategic segments, and interview the economic buyer or primary evaluator rather than the rep's coach.
Both work, with a tradeoff. An external firm gets more candor from buyers and costs more. An internal RevOps or enablement team moves faster and costs less but has to work hard to earn honest answers. Many mature programs run hybrid: an external firm handles interviews so buyer candor is protected, and internal RevOps owns the CRM data and the quarterly report.
No. The rep who worked the deal cannot interview the buyer: the buyer softens the real reason, the rep hears what they want to hear, and the data reinforces the existing story. The rep contributes context before the interview and reads the themed report after. The interview itself is run by someone the buyer does not confuse with the sales motion.
A good framework covers eight areas in 30 to 45 minutes: what triggered the evaluation, who was on the shortlist, what decision criteria mattered, how the vendors compared on each criterion, what tipped the final decision, what the counterfactual change would have been, how the first ninety days with the chosen vendor have gone, and what one piece of feedback the buyer would give the losing vendor.
Quarterly for the deep themed review, monthly for a lighter scan of the lost-reason field data to catch spikes. The quarterly review pairs the themed report with the action tracker from last quarter and ends with three to five committed actions. The monthly scan is a RevOps-owned check for emerging competitor or product-fit patterns that cannot wait a full quarter.
Four pieces: a required lost-reason picklist with six to ten options on every closed-lost deal, a short required win-driver field on closed-won, a workflow that auto-flags qualifying deals for interview based on value and segment, and an interview queue plus transcript attachment surface on the opportunity record. Without the plumbing the program is a spreadsheet that dies when the owner leaves.
Yes, at a smaller scale. A ten-person sales team can run a lightweight program with ten interviews per quarter, an internal owner, and the same required-field CRM setup. The report is shorter and the action tracker is three items, not fifteen. The scale changes; the discipline of pairing coded field data with buyer interviews does not.
No sales call, no migration consultant, no four-month implementation. Enter your card, get 14 days of the full Pro tier, cancel any time before day 14 with zero charge. Spin up a workspace, import your CSV, and have something useful before lunch.
