Win/Loss Analysis Framework

Example

A CRM platform analyses 30 deals (15 wins, 15 losses) in Q1:

Wins:

• Primary reason: 9 of 15 wins cited "easy to customise without code" versus competitors that required a development team.
• Secondary reason: 7 cited "existing Zapier integrations saved us 4 weeks" versus competitors with a limited integration ecosystem.
• Tertiary reason: 5 praised support responsiveness, specifically citing a sub-two-hour first response time during the trial.

Losses:

• Primary reason: 8 of 15 losses chose Salesforce because "it's what our enterprise parent company mandates," a decision made above the buyer's authority.
• Secondary reason: 5 lost to HubSpot because "an all-in-one marketing and CRM platform was easier than integrating two separate tools."
• Tertiary reason: 4 cited that the competitor's total cost of ownership was 30% lower over a three-year term.
• Surprise finding: 3 losses mentioned "we didn't know you could do X," meaning the product already had the capability, but messaging never surfaced it during the evaluation.

Actions taken:

• Messaging shift: lead with "no-code customisation" in the first sales call to differentiate clearly from Salesforce's developer-heavy approach.
• Content: develop a comparison guide, "Zapier integrations as a native alternative to custom development," to directly counter HubSpot's all-in-one argument.
• Sales enablement: build a short script to address "enterprise mandate for Salesforce" objections, positioning the product as a complement rather than a replacement.
• Product messaging: surface the integration and customisation examples that the three surprised losses didn't know existed, adding them to the standard demo script within two weeks.
• Pricing review: analyse why HubSpot's total cost of ownership came in 30% lower, checking whether the gap is driven by list pricing, the pricing model's structure, or implementation time.

Twelve weeks after these actions, the team ran a smaller follow-up sample of 10 deals and found zero losses citing "didn't know you could do X," confirming the messaging fix had closed that specific gap.

Benchmarks: These are illustrative ranges commonly cited in B2B SaaS sales-performance benchmark reports (for example, those published by sales-methodology vendors and RevOps analyst firms), not a single authoritative figure; validate against your own segment and category before treating them as a target. For context, a 50% win rate (15 wins from 30 total deals) would be strong for a mid-market CRM platform. Commonly cited win rate ranges by segment are roughly: SMB 40 to 60%, mid-market 30 to 50%, and enterprise 15 to 35%, reflecting the longer sales cycles and larger buying committees at the top end. In this example, losing 8 deals to "enterprise mandate" is a normal, largely unavoidable pattern rather than a messaging problem, but losing 3 deals because customers didn't know about existing features is fixable within 30 days through better demo scripting and sales messaging.

Pitfalls

• Asking leading questions. A question like "Why didn't you choose us because of our great support?" will bias the answer toward what the interviewer wants to hear. Recovery: Use open-ended questions and have someone outside the deal team, ideally a PMM or a third-party researcher, conduct the interview so the buyer feels safe being candid.
• Analysing losses but not wins. You learn as much from why customers buy as from why they don't, and a losses-only analysis produces a defensive, gap-focused strategy rather than a balanced one. Recovery: Always interview an equal or near-equal number of wins and losses in every cycle, even when losses feel more urgent.
• Not following up. Collecting data and not acting on it wastes the time of every customer interviewed and erodes their willingness to participate next time. Recovery: Commit publicly, inside the company, to updating positioning, messaging, and the sales playbook within 2 weeks of completing the analysis, and report back on what changed.