Win/Loss Analysis
Pattern-match outcomes before you change positioning or pricing.
Win/loss analysis synthesises why deals close or fail using structured evidence: decision criteria, alternatives considered, objections, champion vs blocker dynamics, and timing. It turns sales anecdotes into patterns product, marketing, and leadership can act on.
A solid analysis balances wins and losses, uses third-party or neutral interviews when possible, and ends with owned actions — not a filing-cabinet report.
Teams remember the dramatic win and forget quiet losses. Without win/loss, positioning drifts, pricing stays wrong, and roadmap chases features that do not affect outcomes. For consultants and founders, it is also how you refine ICP and messaging before burning CAC.
After a quarter of pipeline activity, after a cluster of similar losses, before repositioning or a pricing change, or when entering a new segment. Minimum sample: often 8–20 recent decisions with mixed outcomes.
- Define scope — segment, motion (PLG vs enterprise), date range.
- Sample wins and losses — aim for balance; include no-decisions if common.
- Capture decision process — who decided, alternatives, timeline.
- Tag themes — price, product gap, trust, timing, incumbent bundle, compliance.
- Compare patterns — what appears only in wins vs only in losses?
- Quote anonymised evidence — 1–2 lines per theme.
- Recommend actions — GTM, product, enablement; assign owners and dates.
- Balanced sample; not victory-lap interviews only.
- Themes backed by counts, not one memorable call.
- Actions are specific (battlecard, security one-pager, case study) with owners.
- Feeds competitor matrix and persona updates.
- Only interviewing wins — survivorship bias.
- Blaming sales without product or positioning signal.
- Too few deals — patterns are noise.
- No follow-through — same loss reason repeats next quarter.
Northvale Systems (12 deals, Q2). Wins (5): ERP-native sync, existing vendor master data. Losses (7): 4 lost to bundled SRM; 2 stalled on security review; 1 price vs suite. Pattern: win when procurement owns budget; lose when IT mandates suite. Actions: security one-pager; compliance demo for suite-heavy accounts.
PulseWell (18 opps). Wins (6): HRIS integration, anonymised team view, peer reference. Losses (12): 5 "feels clinical"; 4 bundled incumbent; 3 budget timing. Pattern: wins with People Ops champion. Actions: reposition copy; marketplace listing; operational nudges case study.
Harbor Consulting (8 proposals). Wins (3): manufacturing network + grant deadline ≤90 days. Losses (5): Big Four brand, capex delay, DIY templates. Actions: diagnostic SKU; grant-calendar marketing.
Clearwater Initiative (4 grants). Wins (2): volunteer trust + maintenance metrics. Losses (2): climate-only donor framing; IoT preference. Actions: climate co-benefits appendix; phased IoT roadmap.
Run /winloss for WINLOSS-001 or /interview first for transcripts. Link themes to competitor-matrix and personas updates.
Related techniques
Sources & further reading
- Dixon, M., & Adamson, B. (2011). The Challenger Sale. Portfolio.
- Spencer, S. (2004). The Win/Loss Review. Pragmatic Marketing.