TL;DR
Loss rate is the percentage of pipeline opportunities that close lost — the contra-metric to win rate. It measures sales engine inefficiency from the loss side: every percentage point of loss rate represents pipeline value that consumed sales effort but produced no revenue. For B2B SaaS, healthy loss rate runs 50–70% (corresponding to 25–40% win rates); the diagnostic value comes from segmenting losses by reason, stage, and competitor.
What is loss rate?
Loss rate (also called pipeline loss rate, deal loss rate, or closed-lost rate) is the percentage of resolved opportunities that ended in closed-lost — the mathematical inverse of win rate for resolved deals. A team with a 28% win rate has a 72% loss rate; the two metrics together describe how the engine resolves pipeline.
Loss rate's diagnostic value is greater than its accountability value. Win rate is what teams celebrate and benchmark; loss rate is where pipeline efficiency improves. Decomposing loss rate by stage, competitor, deal size, and ICP exposes the structural friction in the funnel — information that win-rate-focused analysis often misses.
Loss rate also has a related concept worth distinguishing: competitive loss, which is the subset of losses to specific named competitors. Competitive loss is the most actionable category of loss-rate analysis because it produces specific competitive-positioning, pricing, or product-gap remedies.
Why loss rate matters for operators
Loss rate is the diagnostic foundation for sales-process improvement. A team with 70% loss rate concentrated in the discovery-to-demo transition has a different problem than a team with 70% loss rate concentrated at proposal — the first is a qualification problem, the second is a pricing or competitive problem. Without loss-rate decomposition, the diagnosis is invisible.
Loss rate also exposes ICP-fit problems. A team where loss rate is 65% on its core ICP but 88% on a recently-targeted secondary ICP is signalling that the secondary ICP needs different positioning, pricing, or product fit before scaling effort. Loss-rate-by-ICP is one of the most actionable segmentation cuts available.
The deeper signal in loss rate is rep-coaching specificity. A blanket 'improve your win rate' coaching conversation has no traction. A 'your Discovery-to-Demo loss rate is 78% vs the team's 55% — let's review what's happening at that transition' conversation has immediate focus. Loss-rate decomposition turns generic coaching into specific intervention.
Loss rate formula and decomposition
Loss Rate (%) =
Closed-Lost Opportunities / (Closed-Won + Closed-Lost) × 100
Loss rate + Win rate = 100% (for resolved deals only)
Stage-level loss rate (most diagnostic):
Stage 1 → Lost: opportunities that died at Discovery
Stage 2 → Lost: opportunities that died at Demo
Stage 3 → Lost: opportunities that died at Proposal
Stage 4 → Lost: opportunities that died at Negotiation
Stage 5 → Lost: opportunities that died at Close
Loss-reason categorisation (typical):
Lost to competitor (specific or general) 30–45%
Lost to no decision / status quo 20–35%
Lost on price / budget 10–20%
Lost on product fit / functionality 10–20%
Lost on timing / project deferred 5–15%
Example — mid-market SaaS, Q3 cohort (240 resolved deals):
Closed-won: 60 (25% win rate)
Closed-lost: 180 (75% loss rate)
Loss decomposition:
Lost to competitor: 68 (38% of losses)
Lost to no decision: 54 (30%)
Lost on price: 29 (16%)
Lost on product: 18 (10%)
Lost on timing: 11 (6%)
Highest-leverage intervention:
Competitive losses are the largest bucket.
Among them, 38 (56%) were to a single competitor.
Recommend competitive-positioning sprint focused on that competitor. Loss rate benchmarks and decomposition norms
| Sales motion | Healthy loss rate | Top-quartile (low loss) | Highest-leverage decomposition cut | Typical no-decision share |
|---|---|---|---|---|
| SMB / inside sales | 65–80% | <60% | By stage + ICP fit | 30–45% |
| Mid-market | 70–82% | <65% | By competitor + pricing | 25–35% |
| Enterprise | 78–88% | <72% | By competitor + buying-committee | 20–30% |
| PLG sales-assist | 50–70% | <45% | By activation + onboarding | 15–25% |
| Channel-led | 70–80% | <65% | By partner + co-sell quality | 30–40% |
Sources: Bridge Group SaaS AE Benchmarks 2024; Pavilion 2024 Sales Operations Survey; Gong State of Revenue Operations 2024; Fairview customer data.
Common mistakes when reading loss rate
1. Reporting loss rate as a single number. A 72% loss rate is meaningless without decomposition. The same loss rate could be concentrated in one transition (fixable), one competitor (fixable), one ICP (fixable), or distributed evenly (structural). Always report the breakdown.
2. Trusting CRM loss-reason fields without quality control. Reps often select loss reasons based on what's easiest, not what's accurate ('lost on price' is the convenient default). Audit loss-reason data quality regularly: spot-check 20 lost deals per quarter and verify the documented reason matches the actual loss cause.
3. Treating no-decision losses as wins. No-decision deals (prospect chose to defer or do nothing) consumed the same sales effort as competitive losses but are often not counted in loss-rate analysis because no competitor 'beat' the team. They should be counted; they represent real efficiency loss.
4. Not segmenting loss rate by deal size. Loss rate at $50K ACV vs $500K ACV is structurally different — larger deals have more decision-makers, more procurement friction, more ways to lose. Aggregating across deal sizes hides whether enterprise motion is structurally weaker than mid-market or simply has more inherent loss surfaces.
5. Optimising for loss-rate reduction without revenue impact. A team can reduce loss rate by qualifying out more deals upstream — at the cost of pipeline volume. The right target is win-rate-times-volume (revenue), not loss-rate alone. Watch for false improvements where loss rate drops but pipeline coverage and revenue also drop.
How Fairview tracks loss rate diagnostically
Fairview's Pipeline Health Monitor decomposes loss rate by stage, competitor, ICP, deal size, and rep cohort — surfacing the specific loss patterns that drive aggregate loss rate, with rolling baselines to detect drift.
The Next-Best Action Engine flags structural patterns: "Mid-market loss rate has risen from 72% to 81% over 90 days. Decomposition: competitive losses to one competitor doubled, concentrated at the proposal stage. Recommend a competitive-positioning review focused on that competitor's recent product launch and pricing changes before next month's pipeline."
Loss rate vs win rate vs competitive loss vs no-decision loss
Loss rate is the contra-metric to win rate; competitive loss and closed-lost analysis are the diagnostic decompositions that make loss rate actionable.
| Loss rate | Win rate | Competitive loss | No-decision loss | |
|---|---|---|---|---|
| What it measures | % of resolved deals lost | % of resolved deals won | Subset of losses to competitors | Subset of losses to status quo |
| Best for | Funnel diagnosis + coaching | Headline efficiency | Competitive positioning | Buyer-readiness / urgency |
| Lever | Stage qualification + competitive | Holistic execution | Differentiation + battlecards | Discovery + business case |
At a glance
- Category
- Revenue Operations
- Related
- 5 terms
Frequently asked questions
What is loss rate in simple terms?
Loss rate is the percentage of resolved sales opportunities that closed lost — the inverse of win rate. A team with 28% win rate has 72% loss rate. The metric is most diagnostic when decomposed by stage, competitor, ICP, and deal size; the aggregate number alone is hard to act on.
What's a healthy loss rate?
Motion-dependent and typically the inverse of healthy win rates. SMB B2B SaaS: 65–80% loss rate (corresponding to 20–35% win rates). Mid-market: 70–82%. Enterprise: 78–88%. PLG sales-assist: 50–70%. Compare against motion-specific benchmarks and your own trailing trend, not against absolute targets.
How do you decompose loss rate diagnostically?
Cut by: stage where the deal died (qualification vs late-stage friction), competitor (lost to whom?), loss reason (price, product, no decision, timing), ICP fit (which segment), deal size, and rep cohort. The most actionable cuts vary by motion: competitive losses dominate enterprise, no-decision dominates SMB, ICP-fit divergence dominates new-market expansion.
Should you count no-decision deals as losses?
Yes — they consumed sales effort and produced no revenue, just like competitive losses. Some teams exclude no-decision from loss rate because no competitor 'won' the deal, but the efficiency impact is the same. Track no-decision share separately as a sub-category; the % of losses that are no-decision is a valuable signal of buyer-readiness or urgency-creation issues.
How do you reduce loss rate?
Decompose first; intervene specifically. If competitive losses dominate: invest in competitive positioning, battlecards, differentiation. If no-decision dominates: tighten discovery to surface real urgency and business case. If pricing dominates: review pricing structure and discount discipline. If ICP-fit dominates: tighten qualification or rework positioning for the underperforming segment. Generic 'improve loss rate' programs without diagnosis rarely produce sustained improvement.
Sources
- Bridge Group SaaS AE Benchmarks 2024
- Pavilion 2024 Sales Operations Survey
- Gong State of Revenue Operations 2024
- Gartner Sales Process Effectiveness 2024
- Fairview customer data (B2B SaaS, 2025)
Fairview is an operating intelligence platform that decomposes loss rate by stage, competitor, ICP, and rep cohort — turning a generic loss percentage into specific intervention targets. Start your free trial →
Siddharth Gangal is the founder of Fairview. He built the loss-rate decomposition layer after watching a CRO chase aggregate loss-rate targets with team-wide coaching that produced no improvement — when the actual problem was a 22-percentage-point divergence in loss rate between two specific ICPs that nobody had segmented.
See it in Fairview
Track Loss Rate automatically.
14-day free trial. No credit card. First data source connected in 5 minutes.