Deal Slippage

What is deal slippage?

Deal slippage (also called pipeline slippage, forecast slippage, or deal push) occurs when a deal that was forecasted to close in a specific period fails to close by the expected date and is pushed to a future period. The deal is not lost — the buyer has not said no. But the revenue arrives later than planned, creating a gap between the forecast and actual results.

Slippage matters because it is the most common cause of forecast misses. Deals rarely fall apart overnight. They slip — one week, then two, then the quarter ends and the deal appears in next quarter's pipeline at the same value. The cumulative effect is a forecast that looked achievable at month start but comes in 20-35% short at month end.

For mid-market B2B SaaS companies with 30-90 day sales cycles, quarterly deal slippage typically runs 20-30%. Meaning roughly one in four forecasted deals closes in the following quarter instead of the current one. Above 40% quarterly slippage, the problem is systemic — not a matter of individual deals taking longer.

Deal slippage is different from deal loss. A slipped deal is still alive. A lost deal is closed-lost — the buyer chose a competitor, decided not to buy, or went dark permanently. Conflating the two leads operators to overreact (treating slipped deals as losses) or underreact (treating lost deals as slippage and carrying them forward indefinitely).

Why deal slippage matters for operators

Deal slippage is the gap between what the forecast promised and what the quarter delivered. Every slipped deal creates a downstream problem: revenue targets miss, cash flow projections break, and hiring plans built on expected bookings lose their foundation.

The financial impact is direct. An operator planning for $850K in quarterly bookings who sees 35% slippage collects roughly $553K. The $297K shortfall cascades: the marketing budget calibrated to bookings velocity gets cut, the customer success hires planned for new logos get delayed, and the board conversation shifts from growth strategy to pipeline diagnosis.

Slippage also damages forecast credibility. After two quarters of 30%+ slippage, the CEO and board stop trusting the number. They apply their own haircut — discounting the forecast by whatever margin they believe is "realistic." The sales team loses influence over resource allocation decisions because their predictions no longer inform planning.

The root cause is usually not rep failure. It is process failure: close dates set based on seller timelines rather than buyer timelines, no validation of buyer decision processes, or missing milestones that would catch stalling deals before the close date passes. Operators who track slippage by stage, rep, and deal size identify which part of the process creates the most slippage — and fix the root cause instead of managing symptoms.

Deal slippage formula

Deal Slippage Rate = (Deals That Moved Close Date Beyond Original Period / Total Deals Forecasted for Period) x 100

Example:
- Deals forecasted to close in Q1: 38
- Deals that actually closed in Q1: 24
- Deals lost in Q1: 5
- Deals pushed to Q2 (slipped): 9

Deal Slippage Rate = 9 / 38 x 100 = 23.7%

Revenue-weighted slippage:
- Total forecasted pipeline for Q1: $1,420,000
- Revenue from slipped deals: $485,000

Revenue Slippage Rate = $485,000 / $1,420,000 x 100 = 34.2%

What each component means:

• Deals That Moved Close Date: Deals that were forecasted to close in the period, did not close, were not marked closed-lost, and were pushed to a future close date. Count only deals that had a confirmed close date in the period — not pipeline that was loosely targeted.
• Total Deals Forecasted: All deals with a close date in the current period at the start of the period (or at forecast lock). Use the snapshot from forecast submission, not the end-of-period view.

Why revenue-weighted slippage matters: A company that slips 5 deals out of 40 has a low deal-count slippage rate of 12.5%. But if those 5 deals represent $800K of a $2M forecast, revenue-weighted slippage is 40%. Large deals slip more frequently and carry disproportionate forecast impact.

Deal slippage benchmarks by company type

How deal slippage varies across B2B segments. Measured quarterly as a percentage of forecasted pipeline.

Sources: Clari 2025 Revenue Accuracy Report, Gartner Sales Forecasting Study 2025, industry-observed ranges from operator benchmarks.

Common mistakes when tracking deal slippage

1. Not snapshotting the forecast at period start

If you measure slippage using the end-of-period pipeline view, you miss deals that slipped and were subsequently lost. The only accurate measurement compares the beginning-of-period forecast snapshot against actual outcomes. Without the snapshot, you're measuring the current state, not the change.

2. Counting lost deals as slippage

A deal that was forecasted to close in Q1 and went closed-lost in Q1 is a loss — not slippage. Conflating the two inflates slippage rates and hides the true loss rate. Track them separately. The remedies are different: slippage is a timing problem; losses are a qualification or competitive problem.

3. Tracking only deal-count slippage, not revenue-weighted

Five slipped deals out of 40 looks minor at 12.5%. But if those 5 deals represent 40% of the forecasted revenue, the financial impact is severe. Always calculate revenue-weighted slippage alongside deal-count slippage. The revenue view drives planning decisions.

4. Allowing close dates to be reset without investigation

Some CRMs let reps push close dates forward with a single click — no note, no reason, no manager review. When moving a close date requires a logged reason and manager approval, slippage rates drop because reps are forced to evaluate whether the deal genuinely has a path to close.

5. Treating all slippage as equally concerning

A deal that slips one week because the buyer's legal review took longer is different from a deal that has slipped three consecutive months. First-time slippage is normal. Repeated slippage on the same deal is a signal the deal may not close at all. Track slip count per deal.

How Fairview tracks deal slippage automatically

Fairview's Pipeline Health Monitor connects to your CRM (HubSpot, Salesforce, Pipedrive) and tracks every close date change across your pipeline. When a deal's close date moves beyond the current period, Fairview flags it as slippage — and calculates both deal-count and revenue-weighted slippage rates in real time.

The Forecast Confidence Engine uses slippage patterns to adjust forecast confidence scores. A pipeline with 35% historical slippage gets a lower confidence rating than one with 15% — giving operators a more honest view of expected revenue.

The Operating Dashboard surfaces repeat-slip deals (deals that have pushed close dates 2+ times) as a distinct risk category. These are the deals most likely to be stalling permanently — and the ones that need immediate rep and manager attention.

→ See how the Pipeline Health Monitor works

Deal slippage vs deal loss

Operators sometimes group slipped deals and lost deals together as "pipeline that didn't close." They require different responses.

Deal slippage delays revenue. Deal loss eliminates it. Track both, but separate them. A quarter with 25% slippage and 10% loss is very different from a quarter with 10% slippage and 25% loss — even though both result in 65% of forecasted deals closing on time.

FAQ

What is deal slippage in simple terms?

Deal slippage happens when a deal you expected to close this month or quarter does not close on time and gets pushed to a future period. The deal is not lost — the buyer has not said no. But the revenue arrives later than planned, creating a gap between your forecast and actual results.

What is a normal deal slippage rate for B2B SaaS?

For mid-market B2B SaaS companies, 20-30% quarterly slippage is typical. SMB-focused companies with shorter sales cycles should aim for 10-20%. Enterprise companies with long sales cycles see 30-40% as normal. Above 40% for any segment signals a process problem, not just deal timing.

How do you calculate deal slippage?

Divide the number of deals that pushed past their original close date by the total deals forecasted for the period. Multiply by 100. For revenue-weighted slippage, use the dollar values instead of deal counts. A $485K slippage against a $1.42M forecast equals 34.2% revenue-weighted slippage.

What is the difference between deal slippage and deal loss?

Slipped deals are still active — they pushed to a future close date but remain in the pipeline. Lost deals are closed-lost — the buyer chose a competitor, cut the budget, or stopped responding. Slippage delays revenue. Loss eliminates it. The corrective actions are different for each.

How often should you track deal slippage?

Weekly during forecast review meetings. Snapshot the pipeline at period start and compare against current status each week. Monthly for trend analysis. Quarterly for board reporting and process improvement. Tracking weekly catches slippage while there is still time to accelerate stalled deals.

How do you reduce deal slippage?

Set close dates based on buyer-confirmed timelines, not seller targets. Require logged reasons for every close date change. Implement stage milestones that validate buyer commitment before advancing deals. Flag deals with no buyer activity for 10+ days. Track slippage by rep and deal size to identify patterns.

Related terms

• Pipeline Health — The overall quality and progression rate of deals in the pipeline
• Forecast Accuracy — The difference between projected and actual closed revenue; slippage is the primary driver of inaccuracy
• Sales Cycle Length — The average time from deal creation to close; longer cycles correlate with higher slippage
• Win Rate — The percentage of deals that close successfully; complements slippage as a pipeline health metric
• Forecast Confidence — A score reflecting how likely the current forecast is to be accurate given historical patterns

Fairview is an operating intelligence platform that tracks deal slippage alongside forecast accuracy and pipeline health automatically. Start your free trial →

Siddharth Gangal is the founder of Fairview. He built the slippage detection view after watching a quarterly forecast miss 32% of target — driven entirely by 7 deals that each slipped "just one more week" until the quarter was over.