Tag: deal slippage

  • What Is Pipeline Coverage? How Much Pipeline Do You Need?

    Pipeline coverage is the ratio of qualified open pipeline to the revenue target for a period, calculated as pipeline value divided by quota. A 3x ratio means three dollars of pipeline for every dollar you need to close. How much you actually need depends on your win rate: required coverage is roughly 1 divided by your historical win rate.

    Every pipeline review asks the same question: do we have enough? Teams usually answer with a number borrowed from a blog post, most often 3x, and then discover in the last month of the quarter that it wasn’t enough. The ratio is simple. The mistake is treating one number as universal.

    This guide explains how to calculate coverage, how to find your own target, why the mix of stages matters as much as the total, and how to set it up in HubSpot.

    The formula

    Pipeline coverage = qualified open pipeline value ÷ quota (or remaining quota) for the period

    An example: a team with a $2M quarterly quota and $7M of qualified open pipeline closing in that quarter has 3.5x coverage. Two details matter. “Qualified” needs a written definition, such as every deal at or beyond a named stage, or the number can be inflated by early-stage noise. And the pipeline must be tied to the period, meaning deals with close dates inside it, so you’re comparing like with like.

    How much coverage do you actually need?

    If you close 25% of qualified pipeline, you need four dollars of pipeline to expect one dollar of revenue. That’s the whole idea:

    Required coverage ≈ 1 ÷ win rate

    Win rate on qualified pipeline Coverage needed to expect to hit target Typical motion
    60% About 1.7x High-velocity, small deals
    40% 2.5x Efficient mid-market
    33% 3x The rule-of-thumb case
    25% 4x Typical B2B SaaS
    20% 5x Longer, more competitive cycles
    15% About 6.7x Enterprise
    10% 10x Complex enterprise

    That’s why the famous 3x rule doesn’t travel well. It implicitly assumes a win rate of about one in three, which many B2B teams don’t reach, especially on cold-sourced pipeline. Win rate and required coverage move in opposite directions: improve one and the other falls. Some teams also add a buffer, around 20%, for slippage and attrition, which turns a 4x requirement into roughly 4.8x. Treat the buffer as a judgment call you can test against your own history.

    Which win rate should you use?

    • Use qualified win rate, measured from the same stage you use to define qualified pipeline. A win rate calculated from all leads will understate what you can expect from pipeline.
    • Split by segment. SMB, mid-market, and enterprise often win at very different rates, so one blended number misleads.
    • Use the last four to six quarters, and check for trends. A win rate that has fallen means yesterday’s coverage target is now too low.
    • Match the window to your cycle. If deals take 90 days, measure the win rate of deals that were in the pipeline 90 days ago, not today’s mix.

    The same coverage can be very different pipeline

    Total coverage ignores stage. A pipeline that’s mostly early-stage at 3x coverage is much weaker than one that’s half late-stage at the same ratio. Here are two illustrative teams, each with $7M against a $2M quota, using assumed stage win rates.

    Stage group Assumed win rate Team A pipeline Team B pipeline
    Early (discovery, qualified) 15% $5.6M $2.1M
    Middle (evaluation) 35% $0.9M $1.4M
    Late (proposal, negotiation) 65% $0.5M $3.5M
    Total pipeline $7.0M $7.0M
    Coverage on a $2M quota 3.5x 3.5x
    Expected closed revenue about $1.48M about $3.08M
    Expected share of quota 74% 154%

    Team A looks fine on the headline ratio and is on course to miss. Team B has the same ratio and a comfortable cushion. The math multiplies each stage’s pipeline by its win rate, which is the idea behind weighted pipeline. The figures are illustrative and assume stable stage win rates, so use your own.

    Coverage changes through the quarter

    When What to check
    Start of the period Total coverage against the full quota, and the stage mix
    Mid-period Coverage of remaining quota, and how much pipeline has slipped out
    Final month Late-stage coverage only, since early-stage deals rarely close in time
    Next period Coverage for next quarter’s quota, built from pipeline you create now

    As the period progresses, measure coverage against remaining quota instead of the full target. If $1.2M of quota is left and $3.6M of pipeline can close in time, that’s 3x of what remains. Also remember your sales cycle. With a 90-day cycle, the pipeline for next quarter has to be created this quarter, so coverage for the following period is a leading indicator of the one after.

    Slice it, don’t just total it

    Slice What it reveals
    By rep Who has too little pipeline, or too much to work well
    By segment or region Where the team is exposed even if the total looks healthy
    By source Whether coverage depends on one channel
    By age How much pipeline is stale and unlikely to close
    By close-date movement How much is slipping from period to period

    Aging and slippage matter because pipeline that has sat for months inflates the ratio without adding real chance. Our guides to deal slippage and forecast categories cover how to spot and handle it.

    What to do when coverage is short

    Lever Example action
    Create more pipeline Outbound pushes, events, partner referrals, reactivating closed-lost accounts
    Improve conversion Tighter qualification, deal reviews, coaching on late-stage deals
    Shorten the cycle Remove stalls, bring in executive sponsors, simplify security reviews
    Clean the pipeline Remove stale deals so the real ratio is visible
    Reset expectations Revisit the forecast or the plan early, not in the last week

    The last lever gets skipped most often. A shortfall visible in week four is a planning problem. The same shortfall in week twelve is a missed number. Coverage is also a useful check on quota design, since a quota with no realistic pipeline behind it is a target nobody believes. See our guides to setting quotas reps believe and sales capacity planning.

    Setting it up in HubSpot

    • Standardize your stages and define “qualified.” Our guide to HubSpot deal stages covers designing them.
    • Require amount and close date on deals, since coverage depends on both.
    • Build a report that sums open deal amounts by close month, filtered to qualified stages, and compare it with targets by owner or team. Sales goals, where your plan includes them, can hold the quota side.
    • Add stage and age views, and a list of deals with past close dates.
    • Review it weekly. Make it a fixed item in your RevOps meeting cadence.

    Coverage is only as honest as your pipeline data, so tighten pipeline hygiene first: no stale deals, no blank amounts, and close dates that reflect buyer actions.

    Mistakes to avoid

    • Borrowing 3x without checking it against your win rate
    • Counting unqualified or early-stage pipeline as coverage
    • Ignoring stage mix and aging
    • Using one blended ratio across very different segments
    • Comparing today’s pipeline with the full quota late in the period
    • Letting stale deals inflate the number
    • Waiting until the last month to act on a shortfall

    Summary

    Pipeline coverage is qualified open pipeline divided by quota for a period. The right target is about 1 divided by your qualified win rate: roughly 4x at a 25% win rate, 5x at 20%, and 3x at 33%. The widely quoted 3x rule assumes a win rate many teams don’t reach, so calculate your own by segment from recent quarters, and consider a buffer for slippage.

    Total coverage hides stage mix. Two teams with the same 3.5x ratio can be on course for 74% or 154% of quota. Track coverage of remaining quota as the period goes on, slice it by rep, segment, source, and age, and fix shortfalls early by creating pipeline, improving conversion, shortening cycles, cleaning data, or resetting expectations. In HubSpot, standardize stages, require amount and close date, and review coverage weekly.

    FAQ

    What is pipeline coverage?

    It’s the ratio of qualified open pipeline value to the revenue target for a period. For example, $7M of pipeline against a $2M quota is 3.5x coverage.

    What is a good pipeline coverage ratio?

    It depends on your win rate. Divide one by your qualified win rate: 25% suggests 4x, 20% suggests 5x, and 33% suggests 3x. Many B2B SaaS teams land between 3x and 5x.

    Is the 3x rule wrong?

    It’s right only if you win about one in three qualified deals. If your win rate is lower, 3x leaves you short on average, so calculate your own requirement.

    Should I include early-stage deals in coverage?

    Only if you define qualified pipeline to include them and use a win rate that matches that stage. Otherwise early deals inflate the ratio without adding real chance of closing.

    How do I calculate coverage mid-quarter?

    Divide the open qualified pipeline that can close in time by the quota still remaining, instead of the full quota.

    What is the difference between pipeline coverage and weighted pipeline?

    Coverage compares total qualified pipeline with quota. Weighted pipeline multiplies each deal by its win probability to estimate expected revenue. Using both gives you volume and quality.

    How often should we review coverage?

    Weekly during the period, with a deeper review by segment and stage in your monthly and quarterly meetings. Check next period’s coverage early, because pipeline takes a full sales cycle to build.

  • What Is Win-Loss Analysis? How to Run One

    Win-loss analysis is the practice of systematically interviewing buyers after a deal closes, whether you won, lost, or ended in no decision, to understand the real reasons behind the outcome. It compares what buyers say with what your CRM and sales team say, and turns the gaps into changes in positioning, product, pricing, and process.

    Ask a sales leader why the team lost last quarter and you’ll often hear “price” or “timing.” Ask the buyers and you’ll hear something different: a business case nobody believed, a missing integration, a champion who left, a security review that stalled. The gap between those two stories is where win-loss analysis earns its keep.

    This guide explains what win-loss analysis is, why CRM data alone isn’t enough, and how to run a simple program, with a question guide, a coding frame, and a worked example.

    What is win-loss analysis?

    Win-loss analysis means picking a set of closed deals, interviewing the people who made the decision, labeling each conversation with the same reason categories, and comparing wins with losses inside a segment. It covers three outcomes: won deals, lost deals, and no-decisions, where the buyer chose to do nothing.

    It’s not the same as a deal review, where the team talks about its own deal, or a post-mortem driven by the rep’s memory. The defining feature is the buyer’s voice, collected by someone who didn’t sell to them.

    Why CRM loss reasons aren’t enough

    Almost every CRM has a “closed lost reason” field, and most of them are unreliable in the same ways. The rep fills in the dropdown minutes after a disappointing call, often choosing the option that feels least like a mistake, and price becomes the default explanation. Independent interviews regularly find that the recorded reason and the buyer’s actual reason differ. A fair summary: reps remember losses as price, while buyers remember them as risk, timing, or a business case nobody believed.

    What the CRM says What a buyer interview might reveal
    Price The ROI wasn’t clear, so any price felt too high
    Timing The champion couldn’t get an executive sponsor
    Went with a competitor The competitor had an integration we didn’t mention
    No response Security review stalled and nobody helped them through it

    That doesn’t make CRM fields useless. They’re good for volume and rough trends, and they help you choose which deals to interview. Treat them as labels that tell you where to look, not as findings.

    What you can learn

    Finding type Example Likely owner
    Positioning and messaging Buyers don’t understand how we differ from the alternative Product marketing
    Product gaps A missing integration appears in many losses Product
    Pricing and packaging The entry plan lacks one feature buyers expect Product and finance
    Sales process We rarely reach the economic buyer Sales leadership
    Competitive One competitor wins on onboarding speed Competitive intelligence

    How to run a win-loss analysis

    1. Define the question and scope. A vague goal produces vague findings. Try something specific: “Why are we losing mid-market deals to Competitor X?” or “What makes wins in our new segment different?”
    2. Select deals deliberately. Include wins, losses, and no-decisions, across deal size, industry, and rep. Interviewing only losses teaches you what went wrong but not what’s working.
    3. Interview soon after the decision. Sources range from two to six weeks, and recall fades quickly after that. Aim for within a month.
    4. Use a neutral interviewer. The account executive who owned the deal shouldn’t run it, and neither should their manager. Buyers soften criticism when they know who they’re talking to. A product marketer, researcher, or outside firm works better. Keep the rep debrief separate, and hold it after you have the buyer data.
    5. Recruit with a clear, low-effort ask. Offer a 20 to 30 minute call, explain the feedback is confidential and used to improve, and don’t use it to win them back. Try more than one person on the buying committee.
    6. Code every interview the same way. Use a fixed set of labels so you can compare across deals.
    7. Triangulate with your data. Compare interviews with CRM stage history, cycle length, and competitors, and note where they agree and contradict.
    8. Report with sample size and confidence, then act. Run a workshop where each priority finding gets an owner and a change to a specific asset: a deck, a pricing page, a playbook, a roadmap item.

    Questions to ask buyers

    Topic Sample question
    Trigger What was going on that made you start looking?
    Alternatives What options did you consider, including doing nothing?
    Criteria What mattered most in your decision, and how did that change along the way?
    Committee Who was involved, and who had the final say?
    Experience What was it like working with our team compared with the others?
    Turning point Was there a moment when you knew where this was heading?
    Concerns What worried you most about choosing us?
    Advice If you could change one thing about how we sold to you, what would it be?

    Ask about behavior and specific moments, not opinions in the abstract. “Walk me through what happened after the demo” gets better answers than “Did you like our product?” And listen more than you talk.

    A simple coding frame

    Pick one primary reason per interview, plus an optional secondary one, from labels like these. Adapt them to your business, and keep them fixed from quarter to quarter.

    Category Meaning
    Competitive loss The buyer chose a named competitor
    No decision The buyer kept the status quo
    Product gap A needed capability or integration was missing
    Value and price Cost was hard to justify against the expected return
    Evaluation and process We didn’t reach decision-makers or support the evaluation well
    Champion and sponsor The internal advocate left or lacked influence
    Timing and priority The project was deprioritized or delayed
    Trust and risk Security, vendor stability, or implementation risk worried the buyer

    Track timing and no-decision outcomes separately from true competitive losses. A deal pushed to next quarter isn’t the same as a deal lost to a rival, and mixing them hides what’s really going on.

    A worked example

    Imagine a team interviews 24 buyers from lost and no-decision deals. In the CRM, 14 of the 24 were logged as “price.” The numbers below are illustrative.

    Primary reason from interviews Deals Action
    Value and price 4 Review packaging at the entry tier
    Business case unclear 6 Create an ROI template and train reps to use it
    Product gap (integration) 5 Publish an integrations guide; raise on the roadmap
    Champion or sponsor lost 5 Multithread earlier; require a named executive sponsor by a set stage
    Security review stalled 3 Build a security answer pack
    Other 1 None

    The CRM said price in 14 of 24 deals. Buyers named it as the main reason in four. The biggest actionable themes were an unclear business case and a missing integration, and none of them would have shown up in the dropdown. With 24 interviews, treat the percentages as directional, not precise. Say so in the report.

    Connect it to deal slippage and pipeline hygiene

    Win-loss findings are most useful when they feed your day-to-day data. Three links are worth making:

    • Standardize the closed-lost field. Replace free-form or generic reasons with the categories from your coding frame, and make the field required. Add a competitor field. Our guide to closed-loop reporting covers how those outcomes flow back to marketing.
    • Watch for slippage. Deals that keep moving to the next quarter often end as no-decisions. Interviews can reveal why, and our explanation of deal slippage shows how to catch the signs earlier.
    • Tighten pipeline hygiene. If interviews show you rarely reach the economic buyer, require that field before a deal enters Commit. Qualification frameworks like BANT and MEDDIC turn findings into required evidence.

    Each quarter, compare your CRM loss reasons with the interview findings. If they diverge, recalibrate the dropdown. Over time the CRM field gets closer to reality, and you can use it for ongoing trend tracking between interview rounds. The customer journey map is also a useful companion, since interview answers often point to specific stages where buyers got stuck.

    In-house, third-party, or AI-assisted?

    Option Advantages Watch for
    In-house (product marketing or research) Low cost, deep product knowledge Buyers may be less candid; programs fade when people get busy
    Third-party firm Neutrality and reach to lost buyers Cost, and a smaller sample of deals
    AI-moderated interviews or surveys Scale and speed Depth and nuance vary; review transcripts yourself
    Hybrid Interviews for depth, surveys for breadth More to coordinate

    Whichever you choose, the same rules apply: someone neutral asks the questions, the labels stay consistent, and each finding has an owner.

    How many interviews are enough?

    Guidance varies. Some sources suggest 15 to 20 interviews per quarter to see clear patterns, and others suggest at least 10 to 15 deals before drawing conclusions about any single pattern. A thinner round is still useful if you label it directional. Fewer than about eight interviews per cycle starts to look more like anecdotes than patterns. Start small, keep the process steady, and let the sample grow.

    Mistakes to avoid

    • Letting the account executive or their manager run the interview
    • Interviewing only losses, so you never learn what’s working
    • Waiting months, so memories fade and buyers stop responding
    • Trusting the CRM dropdown without checking it against buyers
    • Reporting percentages from a tiny sample as if they were precise
    • Producing a report without owners or follow-up
    • Using the interview to try to win the deal back

    Summary

    Win-loss analysis interviews buyers after wins, losses, and no-decisions to find the real reasons behind outcomes. It matters because CRM loss reasons are written by reps in a hurry and tend to default to price or timing, while buyers describe different drivers, such as unclear business cases, missing integrations, lost champions, and stalled security reviews.

    To run one, define a specific question, select a mix of recent deals, use a neutral interviewer, interview within about a month, code every conversation with a fixed frame, and triangulate with CRM data. Report sample size and confidence, then assign owners to each finding. Feed the results back into your closed-lost field, your qualification rules, and your deal reviews so the CRM gets closer to the truth.

    FAQ

    What is win-loss analysis?

    It’s the practice of interviewing buyers after a deal closes, whether won, lost, or ended in no decision, to learn the real reasons behind their choice and use them to improve positioning, product, pricing, and sales process.

    Why isn’t the CRM loss reason enough?

    Reps usually choose it quickly and tend to cite price or timing. Buyer interviews often reveal different reasons. Use CRM fields for volume and trends, and validate them with real buyer conversations.

    Who should conduct win-loss interviews?

    Someone neutral: a product marketer, researcher, or outside firm. The rep who owned the deal and their manager should not, because buyers soften feedback when they know who is asking.

    How soon after a deal should we interview the buyer?

    Ideally within two to six weeks. Memory fades quickly, and recruiting gets harder with time, so aim for within about a month.

    How many interviews do we need?

    Some sources suggest 15 to 20 per quarter for clear patterns. Smaller rounds are still useful if labeled directional. Keep the process consistent and grow the sample over time.

    Should we interview wins as well as losses?

    Yes. Wins show what’s working and what to protect, and they give you a baseline to compare losses against. Also include no-decision deals, which are often the largest hidden source of lost revenue.

    How do we get buyers to agree to an interview?

    Keep the ask short, offer a 20 to 30 minute call, explain that feedback is confidential and used for improvement, not for selling, and send the request from a neutral person. Try multiple contacts on the buying committee.

    What do we do with the findings?

    Hold a short workshop, rank the findings, and map each to an owner and a specific change, such as a messaging update, an ROI template, a required CRM field, or a roadmap request. Then check next quarter whether the pattern moved.

  • What Is Deal Slippage? Causes and How to Prevent It

    Deal slippage is when a sales opportunity that was forecasted to close in a specific period (say, this quarter) doesn’t close on time and gets pushed to a later date. The deal isn’t dead. It’s still open. But it’s no longer where your forecast said it would be, and that gap is where revenue predictability goes to die.

    If you’ve ever walked into a quarterly business review with a pipeline that looked great on paper, only to watch half your “committed” deals quietly move to next quarter, you already know this problem. It’s one of the most common and most avoidable issues in sales pipeline management, yet most teams don’t even track it as its own metric.

    What is deal slippage, exactly?

    Deal slippage describes opportunities that were forecasted to close within a specific time period but fail to do so and get pushed into a future date. It’s different from a lost deal. A lost deal is closed and gone. A slipped deal is still alive, still in your pipeline, just not where you said it would be.

    This matters because slipped deals quietly distort your numbers. Unlike lost deals, slipped deals remain in the pipeline but introduce uncertainty in revenue forecasting and pipeline accuracy. You can have a pipeline that looks perfectly healthy in total dollar value while hiding a forecast that’s falling apart underneath.

    Slippage shows up most in B2B sales, where long sales cycles, multiple stakeholders, and complex approvals often delay decision-making. If you’re selling into mid-market or enterprise accounts with procurement, legal, and multiple approvers, some slippage is just part of the territory. The question is how much, and whether it’s getting worse.

    Why slippage hurts more than a single missed date

    It’s tempting to treat a slipped deal as a minor scheduling issue, since the deal is technically still alive. The damage shows up in three places at once. First, your forecast for the current period just lost revenue it was counting on, which means someone has to explain the gap to leadership. Second, next period’s forecast just inherited a deal it didn’t plan for, which can crowd out new pipeline that would have closed on its own schedule. Third, the deal itself is now less likely to close at all, because the momentum that existed when the close date was set has already started to fade.

    That third point is the one teams underestimate most. A slipped deal doesn’t sit frozen in time waiting patiently for the buyer. Priorities shift, champions change roles, budgets get reallocated, and a competitor gets a second look. Every week a deal drifts past its original date is another week for something to change that wasn’t in your forecast.

    How do you measure a deal slippage rate?

    You calculate it with a simple formula: divide the number (or value) of slipped deals by the total number (or value) of deals forecasted to close in that period, then multiply by 100. For example, if your team forecasts 40 deals to close in Q3 and 12 of them push to Q4, your slippage rate for that quarter is 30%.

    There’s no single universal benchmark, since the right number depends on your industry, deal size, and typical sales cycle length. That said, most high-performing sales organizations target a slippage rate below 20% on committed pipeline, and rates consistently above 30% usually point to deeper problems with qualification, forecast discipline, or rep coaching rather than a few unlucky deals.

    Worth noting: slippage has been trending the wrong way across the industry. Deal slippage has nearly doubled in recent years, rising from 12% to 22%, largely driven by more stakeholders like CFOs and procurement officers getting involved later in the deal cycle. More separate research found win rates plummet by 113% once deals extend beyond two months past their expected close, which tells you slippage isn’t a neutral delay. It actively kills deals the longer it drags on.

    Measure it both ways if you can, by deal count and by deal value. Count-based slippage tells you how reliable your reps’ close dates are in general, while value-based slippage tells you whether the biggest deals are the ones slipping, which usually matters more for the forecast. A team can look fine on count and still be in trouble if the three largest deals of the quarter are the ones that moved.

    Why does deal slippage happen?

    Slippage usually isn’t one big dramatic event. It’s a handful of small gaps that compound. The most common causes include:

    • No compelling event. A large share of slipping deals lack a clear reason for the buyer to act now, so there’s nothing forcing a decision by any particular date.
    • Weak qualification. Reps pursue opportunities without confirming real budget, timeline, or fit, so the “close date” in the CRM was more of a guess than a commitment.
    • Missing stakeholder engagement. If the economic buyer or final approver hasn’t been identified and looped in, the deal stalls in internal review.
    • Reactive selling. Some reps wait for the buyer to drive the process instead of proactively pushing it forward, and momentum just evaporates.
    • Stale CRM data. Sometimes a deal already slipped weeks ago in reality, but nobody updated the close date, so it looks like a surprise in this week’s pipeline review when it’s actually old news.

    Honestly, most slippage I’ve seen traced back to qualification, not closing skill. Reps get excited about pipeline volume and let deals sit in the forecast that never should have been there in the first place. Low-performing reps are 217% more likely to experience slippage than top performers, which tells you this is a coachable, process problem rather than bad luck.

    What are the early warning signs of a deal about to slip?

    Because most pipeline reporting looks backward, by the time a close date moves, the warning signs have usually been visible for weeks. A few patterns are worth building into your weekly deal review:

    • No next meeting on the calendar. A late-stage deal with no scheduled next step is drifting, whatever the CRM stage says.
    • Single-threaded contact. If the rep only talks to one person at the account, any delay on that person’s side stalls the whole deal.
    • Legal or procurement not yet involved. A deal forecast to close in three weeks that hasn’t touched contracts or procurement is almost certainly going to slip.
    • Vague language from the rep. Phrases like “they’re just busy” or “should be soon” usually mean the rep doesn’t have a specific buyer action to point to.
    • Close date already moved once. A deal that has slipped before is statistically more likely to slip again than one that hasn’t.

    None of these signs prove a deal will slip, but each one is a reason to ask a direct question during review rather than accepting the close date at face value.

    How do you prevent deal slippage?

    You can’t eliminate slippage entirely, especially in longer enterprise cycles, but you can catch it early and shrink it. Here’s a practical sequence:

    1. Define a real close date, not a wish date. A close date should be tied to a specific buyer action (contract signed, PO issued), not just “end of quarter” because that’s when your fiscal period ends.
    2. Require a compelling event before a deal enters forecast. If the rep can’t name why the buyer needs to act by that date, it shouldn’t count as committed.
    3. Map the full buying committee early. Identify the economic buyer, legal, procurement, and any other approver before the deal reaches late stage, not after it stalls there.
    4. Track slippage rate as its own metric, by rep and by stage. Don’t bury it inside win rate. A rep with a great win rate but high slippage is still a forecasting risk.
    5. Review stalled deals weekly, not just at quarter-end. Deals that sit too long in one stage usually show warning signs (no next meeting booked, no recent activity) well before the close date actually moves.
    6. Keep CRM close dates current. Make updating a close date part of the deal review ritual, not an afterthought reps do only when asked.

    Pro tip: if a deal has pushed its close date more than once, stop trusting the new date at face value. Ask the rep to walk through the actual next buyer action and who owns it. If they can’t answer specifically, that deal probably needs to come out of your committed forecast entirely.

    Getting this right connects directly to [TODO LINK: How to accurately forecast revenue] your overall forecasting accuracy. If you’re still fuzzy on how forecasting and pipeline fit together, it helps to start with sales forecasting basics, and if you’re not sure how pipeline differs from a funnel in the first place, our post on sales pipeline vs. sales funnel breaks that down. Understanding your weighted pipeline also helps, since slipped deals often inflate weighted totals long after they should have been discounted.

    At Revlyn, we see this come up constantly in RevOps conversations: teams have plenty of pipeline data but no clean way to separate “deal is genuinely progressing” from “deal is just sitting there waiting to slip.” Fixing that distinction is usually a bigger forecast-accuracy win than adding more top-of-funnel volume.

    Summary

    Deal slippage happens when a deal forecasted to close in one period moves to a later one without being lost. It distorts forecasts, crowds the next period’s pipeline, and lowers the odds the deal ever closes, since momentum fades with every week past the original date. The slippage rate is simple to calculate: slipped deals divided by deals forecasted to close in the period. Many strong teams aim for under 20% on committed pipeline, while consistently above 30% usually signals a qualification or forecast-discipline problem.

    Most slippage traces back to a short list of causes: no compelling event, weak qualification, missing stakeholders, reactive selling, and stale CRM data. Prevention comes down to setting close dates tied to real buyer actions, requiring a compelling event before a deal enters the forecast, mapping the buying committee early, tracking slippage as its own metric, reviewing stalled deals weekly, and keeping close dates current. A deal that has already slipped once should never be trusted at its new date without a specific next buyer action behind it.

    FAQ

    Is deal slippage the same as a lost deal?

    No. A lost deal is closed and done. A slipped deal is still open, it just didn’t close in the period it was forecasted for and got pushed to a later date.

    What’s a healthy deal slippage rate?

    There’s no single number that applies to everyone, since it depends on deal size and sales cycle length. As a general guide, many high-performing teams aim to keep slippage under 20% of committed pipeline, and anything consistently above 30% is worth investigating.

    Does deal slippage always mean the deal will eventually close?

    Not necessarily. Repeated slippage often signals poor qualification, internal delays, or customer misalignment, and every slip increases the chance of churn, reprioritization, or a competitor stepping in before the deal ever closes.

    How is deal slippage different from pipeline leakage?

    Pipeline leakage is when prospects drop out of your pipeline entirely without buying. Slippage is different: the deal stays in your pipeline, it just takes longer to close than expected.

    Can CRM data alone catch slippage early?

    Not reliably on its own. Most pipeline tools report stage, velocity, and conversion rates, which are retrospective, so you also need to watch for behavioral warning signs like missing stakeholder engagement or stalled next steps well before the close date actually moves.

    Should slipped deals stay in the committed forecast?

    Only if the rep can name a specific next buyer action, who owns it, and when it will happen. A deal that has slipped once with no concrete path to the new date is better moved to a lower forecast category until the evidence supports it.