Tag: sales forecasting

  • 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 Sales Capacity Planning? A Beginner’s Guide

    Sales capacity planning is the process of modeling how many sellers you need to hit a revenue target, accounting for ramp time, attrition, quota attainment, and territory coverage. It answers a deceptively simple question: how many reps do we actually need?

    If you’ve ever hired a team that looked big enough on a spreadsheet and still missed the year, you’ve run into the gap this process exists to close. Headcount is not capacity. Some reps are still learning the product, some will leave, and not everyone hits quota. A plan that ignores all three overstates what the team can deliver.

    This guide explains the core terms, the formulas, and a worked example, then walks through how to build a first plan. It’s written for founders, sales leaders, and RevOps teams who’ve never done this before.

    Why headcount is not capacity

    Three things chip away at the number you get from multiplying reps by quota:

    • Ramp time. A new rep takes months to reach full productivity. During that stretch they produce a fraction of a ramped rep’s output.
    • Attrition. Reps leave, and each departure creates a coverage gap and a fresh ramp for the replacement.
    • Attainment. Not every rep hits quota. If your plan assumes they all do, it’s built on the best case.

    There’s also a timing problem. Because of ramp, the reps you need to be productive in the first quarter of next year had to be hired well before it, often around the middle of the current year. Capacity planning is partly a math exercise and partly a calendar exercise.

    The key terms

    Term What it means
    Quota The revenue target assigned to a rep for a period
    Attainment Actual sales divided by quota, usually shown as a percentage
    Ramp time How long a new hire takes to reach full productivity
    Attrition The share of reps who leave in a year
    Ramped rep equivalent A way to count headcount as productive full-time reps, so a half-productive new hire counts as 0.5
    Quota capacity Total quota across all reps, before adjusting for ramp, attrition, or attainment
    Productive capacity What the team can realistically deliver after those adjustments

    The core formulas

    The simplest version looks like this:

    Sales capacity = number of reps × quota × attainment

    It’s a useful start, but it treats every rep as fully ramped and permanent. A more realistic version counts only productive reps:

    Productive capacity = (fully ramped reps + ramping reps at partial capacity − expected departures) × quota × attainment

    And when you’re working backward from a target, rearrange it:

    Ramped reps needed = revenue target ÷ (quota × attainment)

    A worked example

    The numbers below are illustrative, not benchmarks. Say a SaaS company wants $12M in new ARR this year.

    • Quota per fully ramped AE: $800,000 a year
    • Expected attainment: 70%, so each ramped AE is expected to deliver $560,000
    • Ramped AEs needed: $12,000,000 ÷ $560,000 = about 21.4 AE-years of capacity
    • Current team: 16 fully ramped AEs
    • Expected attrition: 25%, or about 4 departures, which if spread evenly costs roughly 2 AE-years of capacity

    That leaves 14 AE-years from the existing team against a need of 21.4, a gap of about 7.4. How many hires close it depends on when they start. Assume a new hire produces at 25% in months one to three, 50% in months four to six, and 100% from month seven.

    Hire starts Share of a full year’s capacity delivered this year Hires needed to close a 7.4 gap
    Start of Q1 About 69% About 11
    Start of Q2 About 44% About 17
    Start of Q3 About 19% About 40
    Start of Q4 About 6% More than 100

    The lesson is that timing matters as much as headcount. Reps hired late in the year barely move this year’s number, though they’ll matter next year. This simplified model ignores backfill ramp, seasonality, and territory fit, which a real plan would add, but it shows why “we’ll just hire more” is rarely an answer to a gap that shows up in Q3.

    Where each input comes from

    Input Where to find it Common mistake
    Quota Compensation plan Using a quota that doesn’t match the segment or territory
    Attainment CRM closed-won data over the last four to six quarters, by segment Assuming 100%, or using one blended figure
    Ramp time and curve Historical cohorts: how long past hires took to reach normal output Using the offer-letter ramp instead of actual results
    Attrition HR data from the trailing 12 months Planning on zero, or ignoring the timing of departures
    Hiring lead time Recruiting history: approved requisition to start date Forgetting that hiring itself takes months
    Sales cycle CRM deal history Ignoring that a long cycle delays a new rep’s first deals

    One caution on benchmarks. Published figures vary widely depending on who was surveyed and how attainment is defined. Reported rep attrition often falls somewhere around 20 to 35%, ramp times commonly run from about four to nine months or more depending on segment, and attainment figures range from well under half of reps to a clear majority. Use these as sanity checks only. Your own data, by segment, is what belongs in the model.

    Capacity problem or pipeline problem?

    Missing a number doesn’t always mean you need more reps. Capacity and demand are separate constraints, and adding sellers to a thin pipeline just spreads the same leads thinner.

    What you see Likely issue First check
    Reps near quota, but too few of them for the target Capacity The capacity model and hiring timeline
    Plenty of reps, thin pipeline per rep Demand or coverage Lead flow, routing, and pipeline coverage by rep
    Wide gaps between top and bottom reps Enablement or territory fairness Territory design, coaching, and ramp quality
    Deals regularly slip to next quarter Qualification or forecast discipline Your deal slippage rate

    If you also run SDRs, include the ratio of SDRs to AEs in the plan, because AE capacity is only useful when enough qualified meetings reach them.

    How to build your first capacity plan

    1. Start with the revenue target, not last year’s quota. Split it by segment or product if they behave differently.
    2. Calculate productive capacity per ramped rep using quota and realistic attainment from your own history.
    3. List the current team with each rep’s start date, so you can count ramped and ramping reps separately.
    4. Apply a ramp curve to new and planned hires, using your historical data.
    5. Subtract expected attrition, including when departures are likely to happen.
    6. Find the gap and work backward through hiring lead time to the dates reqs must be approved.
    7. Test the plan with a downside case, such as lower attainment or slower ramp, and decide what you’d do if it happened.

    Pro tip: build the model in a spreadsheet you can change in a meeting, with every assumption in its own labeled cell. Leaders will challenge the assumptions, not the arithmetic, and you want to show the effect of a change in seconds.

    Once a plan exists, review it on a schedule. The quarterly review in a RevOps meeting cadence is the natural home for checking actual attainment, ramp, and attrition against the plan. Forecast definitions matter too, so make sure your team shares an understanding of forecast categories and weighted pipeline, since capacity plans and forecasts should tell a consistent story.

    Mistakes to avoid

    • Counting headcount instead of productive, ramped reps
    • Assuming every rep hits 100% of quota
    • Using a single blended ramp, attainment, or quota across very different segments
    • Ignoring hiring lead time, so the gap is identified too late to close
    • Planning without attrition, then absorbing departures as surprises
    • Treating capacity as a one-time exercise instead of reviewing it every quarter

    Summary

    Sales capacity planning models how many reps you need to hit a revenue target after accounting for ramp time, attrition, and quota attainment. The basic formula is reps × quota × attainment. A realistic one counts only productive reps and subtracts expected departures. Working backward, ramped reps needed equals the target divided by quota times attainment.

    The worked example shows that hire timing matters as much as headcount: a gap that 11 early-year hires could close takes dozens of late-year ones. Pull quota, attainment, ramp, and attrition from your own data, distinguish capacity problems from pipeline problems, test a downside case, and review the plan every quarter.

    FAQ

    What is sales capacity planning?

    It’s the process of modeling how many sellers you need to hit a revenue target, accounting for ramp time, attrition, quota attainment, and territory coverage, instead of simply counting headcount.

    How do you calculate sales capacity?

    At its simplest: reps × quota × attainment. For accuracy, count fully ramped reps plus ramping reps at partial capacity, subtract expected departures, and multiply by quota and realistic attainment.

    What’s the difference between quota capacity and productive capacity?

    Quota capacity is the sum of every rep’s quota. Productive capacity adjusts that for ramp, attrition, and attainment, so it reflects what the team can realistically deliver. Planning from quota capacity alone overstates the number.

    How long does it take a new rep to ramp?

    It varies by segment and sales cycle. Published figures commonly range from about four months to nine or more, with enterprise sales on the longer end. Measure your own cohorts instead of relying on a benchmark.

    How many reps do I need to hit my target?

    Divide your target by quota times realistic attainment to get ramped reps needed, then add enough headcount to cover ramping hires and expected attrition. Plan for hires to start early enough to ramp before you need them.

    Is a missed target a capacity problem or a pipeline problem?

    Check both. If reps are near quota but there aren’t enough of them, it’s capacity. If there are enough reps but each has thin pipeline, it’s demand or coverage. Adding reps to a pipeline problem spreads the same leads thinner.

    How often should we update the capacity plan?

    Review it at least quarterly against actual attainment, ramp, and attrition, and update it whenever you change quotas, territories, or hiring plans.

  • Forecast Categories Explained: Commit, Best Case, Pipeline

    Forecast categories are labels your CRM uses to sort open deals by how confident a rep is that each one will close in a given period. The five standard labels (used by Salesforce and mirrored by most other CRMs) are Pipeline, Best Case, Commit, Closed, and Omitted. They’re related to the deal’s sales stage, but they aren’t the same thing.

    If you’ve ever opened a forecast report and seen a deal sitting in “Qualification” stage but tagged as “Commit,” you’ve probably wondered what’s going on. That’s not necessarily a bug. Stage and forecast category measure two different things, and mixing them up is one of the most common reasons forecasts go sideways.

    This post breaks down what each category means, how they roll up into a number leadership actually trusts, and how to set definitions your whole team can agree on.

    What is a forecast category, exactly?

    A forecast category is a classification tag attached to an opportunity that signals how likely the rep thinks it is to close within the current forecast period, usually a month or a quarter. Salesforce, which popularized this model, uses categories to group opportunities by confidence of closing. Most other CRMs, including HubSpot, use some version of the same idea, though the labels can differ slightly, so check your own naming.

    Here’s the distinction that trips up most new reps and managers. A pipeline stage (like “Proposal Sent” or “Negotiation”) describes where a deal sits in your sales process. A forecast category describes how sure you are it will close on time.

    The two are connected, though. In Salesforce, each stage maps to a default forecast category, and that mapping drives how opportunities roll up into a rep’s or manager’s forecast. Admins can also allow users to override the category on a deal. So a deal in a late stage can still be tagged Pipeline if the rep isn’t confident, and a deal in an early stage can be tagged Best Case if the rep has unusually strong conviction. The override is where judgment enters the forecast, which is also where most of the trouble starts.

    Stage (example) Default category (example)
    Discovery Pipeline
    Qualification Pipeline
    Demo Best Case
    Proposal Best Case
    Negotiation Commit
    Closed Won Closed
    Closed Lost Omitted

    That mapping is an illustration, not a recommendation. Yours will differ. One useful check: make sure every active stage maps to a category, because an unmapped stage defaults to Pipeline, which can quietly understate late-stage deals.

    What does each category mean?

    Pipeline is the broadest, lowest-confidence category. These are opportunities that are actively being worked but haven’t earned a stronger label yet. They might close this period, next period, or not at all. In most CRM configurations, every new opportunity starts here by default. Think of it as the “still in progress, don’t bank on it yet” bucket. It’s useful for understanding total potential revenue, but it typically gets excluded from the number you’d present as a committed forecast.

    Best Case sits one notch up. These are opportunities with real interest and a plausible path to closing this period, but still some risk. It’s also the category most prone to inflation, and that tracks with what most RevOps teams will tell you: it requires less evidence than Commit and feels better to report than Pipeline, so reps lean on it. Writing down what specifically disqualifies a deal from Commit keeps Best Case from becoming a dumping ground for hopeful deals.

    Commit is the rep’s public promise. These are opportunities the rep is telling their manager, in effect, “this one is closing this period, you can count on it.” In cumulative rollups, the Commit total usually becomes the floor that leadership plans around, because it includes Commit plus anything already Closed. Commit is better understood as an accountability signal than a probability estimate, which is exactly why it needs the strictest bar of any category.

    Closed covers deals already won in the period. There’s no projection involved. It’s the booked outcome. In the standard setup, Closed means Closed Won only.

    Omitted covers opportunities excluded from the forecast. That’s typically where Closed Lost deals land, along with deals that are on hold, stalled, or pushed to a future period. Some Salesforce orgs also enable an optional “Most Likely” category between Commit and Best Case, so check whether yours does before you compare numbers across teams.

    Define categories by evidence, not by percentage

    Different reps calibrate confidence differently, so one rep’s 80% might be another’s 55%. Defining a category by required evidence makes the label mean the same thing no matter who fills it in. Here’s an illustrative starting point:

    Category Example evidence required Example disqualifiers
    Pipeline Qualified need and an identified contact None, this is the default
    Best Case Confirmed need, budget discussed, a proposed timeline, a next meeting booked No buyer contact in the last two weeks; no identified approver
    Commit A mutual close plan, confirmed budget, known approvals and signers, and a dated next step Dependency on an unconfirmed event; legal or procurement not yet engaged

    Pro tip: don’t let a close date inside the quarter be the only reason a deal reaches Commit. The date is a hope. The evidence is what turns it into a commitment.

    How do forecast categories roll up into a number?

    Most CRMs let you view totals by category in two ways. A single rollup shows only the deals in each category. A cumulative rollup shows each category plus everything more certain than it. Here’s an illustrative example with made-up numbers:

    Category Single rollup Cumulative rollup
    Closed $400K $400K
    Commit $600K $1.0M (Commit + Closed)
    Best Case $1.1M $2.1M (Best Case + Commit + Closed)
    Pipeline $2.3M Open pipeline: $4.0M (Pipeline + Best Case + Commit)

    Leadership can compare a conservative scenario (Commit, cumulative) against an optimistic one (Best Case, cumulative). Definitions of “open pipeline” vary, with some setups excluding Closed and some including it, so check which version your report uses before you compare numbers across teams or periods. A cumulative total and a single-category total can look very different for the same pipeline.

    Weighted pipeline is a related but different idea: instead of sorting deals into buckets, it multiplies each deal’s value by a probability to produce a blended number. Teams often use both, and it’s worth understanding how weighted pipeline works alongside forecast categories.

    Check whether the labels are earning their meaning

    A label is only useful if it predicts something. One simple measure compares your Day One Commit forecast with what actually closed by the end of the period. If you started the quarter with $1.0M in cumulative Commit and $900K closed, that’s a 10% miss. Track it every quarter, along with how often Commit deals closed and how often Best Case deals closed. Here’s an illustrative history:

    Quarter Commit deals that closed Best Case deals that closed
    Q1 85% 35%
    Q2 71% 40%
    Q3 64% 28%

    A declining Commit close rate like the one above suggests the definition is loosening, not that reps got worse at selling. Tighten the evidence requirements before you coach individuals. Decide on a target close rate for each category and review the numbers in your forecast meeting.

    Warning signs in your categories

    • A Commit total that sits on a thin Best Case and shallow pipeline. A healthy-looking Commit with little behind it is a fragile forecast.
    • Deals jumping from Pipeline straight to Commit. That’s worth a second look in review.
    • A growing Omitted bucket. It can mean deals are slipping or qualification is breaking down.
    • Pipeline padded with stale deals whose close dates keep sliding forward each month.
    • Overrides nobody explains. If categories change without a note, the label stops carrying information.

    Five questions for a Commit review

    1. What has the buyer actually done in the last seven days?
    2. Who signs, and have we spoken to them?
    3. Is budget confirmed, and by whom?
    4. What is the next step, and when is it scheduled?
    5. What could still stop this deal from closing this period?

    If a rep can’t answer three of these, the deal probably belongs in Best Case. These questions draw on the same logic as qualification frameworks like BANT and MEDDIC, and a poorly qualified deal will fool even the best category definitions.

    A simple checklist for defining your own categories

    1. Write a one-sentence definition for each category your team uses (Pipeline, Best Case, and Commit at minimum).
    2. List the specific, observable evidence required to qualify for each one. Avoid relying on probability percentages alone.
    3. List disqualifying conditions, especially for Best Case and Commit (stale buyer contact, no confirmed budget, dependency on an unconfirmed event).
    4. Map every active stage to a default category, and decide whether reps may override it.
    5. Decide whether your forecast rollup will be cumulative or single-category, and make sure everyone reading the report knows which.
    6. Review quarterly how often Commit deals and Best Case deals actually closed. If the numbers are way off from what the labels imply, your definitions need tightening, not your reps.

    If you’re still getting oriented on forecasting basics, our beginner’s guide to sales forecasting is a good place to start.

    Summary

    Forecast categories sort open deals by how confident a rep is that each will close in the current period. The five standard categories are Pipeline (early and uncertain), Best Case (real interest with some risk), Commit (the rep’s public promise), Closed (won deals), and Omitted (excluded, usually including lost deals). They differ from sales stage, which describes where a deal sits in the process, although in many CRMs each stage maps to a default category that reps may or may not be allowed to override.

    Define each category by observable evidence rather than a probability, check whether your rollup is single or cumulative, and track how often Commit and Best Case deals actually close. When Commit close rates slip, tighten the definition before coaching individuals. Watch for deals jumping straight to Commit, a growing Omitted bucket, and unexplained overrides.

    FAQ

    Is a forecast category the same as a sales stage?

    No. Stage tracks where a deal sits in your sales process. Forecast category tracks how confident the rep is that it will close on time. They often correlate, since stages map to default categories, but they’re separate fields and shouldn’t be treated as interchangeable.

    What are the five standard forecast categories?

    Pipeline, Best Case, Commit, Closed, and Omitted. These are the standard categories Salesforce ships with, and most other CRMs use a similar structure even if some of the naming differs.

    Where do lost deals go?

    Typically into Omitted. Closed usually means Closed Won only, so lost deals are removed from the forecast by mapping Closed Lost to Omitted.

    Can a deal skip categories, like jumping straight from Pipeline to Commit?

    Technically yes, if overrides are allowed. Whether that’s a good idea is a different question. A deal that jumps straight to Commit without passing through Best Case is usually worth a second look in your forecast review.

    Why does Best Case get inflated so often?

    Because it requires less evidence than Commit but still feels more credible to report than plain Pipeline. Tight, written disqualification criteria are the best fix we’ve seen for this.

    Do I need all five categories, or can I use fewer?

    Some teams run a functional forecast with just Pipeline, Best Case, Commit, and Omitted, treating Closed separately since it’s an outcome rather than a projection. What matters more than the count is that every rep and manager applies the same definition consistently.

    Do forecast categories replace probability weighting?

    Not necessarily. Categories group deals by confidence, while weighted pipeline multiplies each deal’s value by a probability. Many teams use both, using categories for the call and weighting as a cross-check.

    Who should own the category definitions?

    Usually sales leadership and RevOps together. Sales owns the judgment about what evidence is meaningful, and RevOps owns the configuration, the stage mapping, and the tracking that shows whether the labels are working.

  • 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.

  • What Is Pipeline Hygiene and Why It Matters

    Pipeline hygiene is the ongoing practice of keeping your CRM’s deal data accurate, current, and reflective of reality: correct stages, real next steps, honest close dates, and no stale deals lingering for months. Without it, your forecasts, coaching, and revenue planning are all built on guesswork.

    If you’ve ever pulled up your CRM (customer relationship management software, the system where you track deals and customer info) and thought “wait, is this deal even still alive?” you’ve already run into a pipeline hygiene problem. It’s one of those unglamorous topics nobody gets excited about, but it quietly decides whether your forecast is trustworthy or fiction.

    What Is Pipeline Hygiene, Exactly?

    A sales pipeline is just a visual list of every open deal your team is working, organized by stage (like “Discovery,” “Proposal Sent,” or “Negotiation”). Pipeline hygiene is the discipline of keeping that list clean: every deal has an accurate stage, a real next step, a believable close date, and up-to-date contact info.

    Think of it like tidying a closet. If you never clean it out, old stuff piles up and you can’t find what actually matters. A CRM pipeline works the same way. Deals that should have been marked “closed lost” months ago just sit there, quietly inflating your numbers.

    Good hygiene isn’t a one-time cleanup either. It’s a habit: reps update deals as they happen, managers review flagged records weekly, and someone owns the process so it doesn’t slide.

    It’s also worth being specific about what “accurate” means here, since teams often conflate an updated CRM with a healthy one. A deal can be technically updated, a rep changed the stage last week, and still be dishonest in every way that matters, if the close date has quietly slipped forward for the fourth month in a row, or the “next step” field just says “follow up” with no date attached to it. Hygiene isn’t about activity in the CRM. It’s about whether that activity reflects what’s actually happening in the deal.

    Why Does Pipeline Hygiene Actually Matter?

    Here’s the blunt version: a messy pipeline makes every number downstream of it wrong. Forecasts, coverage ratios, quota planning, even your board deck. All of it inherits the pipeline’s dirt.

    The scale of this problem is bigger than most teams realize. One industry estimate puts it starkly: Gartner projected that 40-60% of pipeline in the average B2B CRM is stale, meaning those deals haven’t progressed in 30 or more days. That’s not a rounding error. If nearly half your pipeline is dead weight, your weighted forecast is essentially guessing.

    It also costs real time. Research cited by revenue teams shows reps spend up to 21% of their week just on CRM data entry, time that isn’t spent actually selling. When hygiene is bad, that time gets wasted twice: once entering data, and again when someone has to untangle it before a forecast call.

    The downstream cost shows up in places that don’t look like a data problem at first. A sales manager who spends a coaching session arguing about whether a deal is really at 70% or 40% probability isn’t coaching, they’re doing forensic accounting on a number that was never trustworthy to begin with. A board member who asks why last quarter’s forecast missed by 30% isn’t getting an honest answer if the real cause was a pipeline stuffed with deals that were dead for months but never marked as such.

    Honestly, most “our forecast is unreliable” complaints we hear aren’t a forecasting-methodology problem. They’re a hygiene problem wearing a forecasting costume. You can have the best forecasting model in the world (we cover the basics of that in What Is Sales Forecasting? A Beginner’s Guide to the Basics), and it still won’t save you if the inputs are fiction.

    What Does a “Dirty” Pipeline Actually Look Like?

    It’s rarely one big obvious mess. It’s small things that stack up:

    • A deal marked “Negotiation” that hasn’t had a single touchpoint logged in two months.
    • Close dates that get pushed forward every single month like clockwork, with no explanation.
    • Deals still sitting open in the CRM even though the prospect went dark, or worse, already bought from a competitor.
    • Missing next steps, so nobody (including the rep) actually knows what happens next.
    • Contact records that are outdated because the buyer changed jobs or companies.

    Each of these on its own seems minor. Together, they mean leadership can’t see which deals are real, coaching conversations become guessing games, and handoffs to customer success start from bad information.

    There’s also a pattern worth naming directly: reps rarely fabricate a healthy-looking pipeline out of malice. It usually happens gradually, a deal that was genuinely promising six weeks ago gets a little quieter, the rep assumes the prospect is just busy, and by the time it’s obviously dead, updating the record feels like admitting a loss nobody asked them to admit yet. Multiply that hesitation across twenty reps and a few hundred deals, and you get a pipeline that looks 40% healthier than it actually is, not because anyone lied, but because nobody wanted to be the one to say a deal was over.

    How Do You Build a Pipeline Hygiene Routine?

    You don’t need fancy tooling to start. You need a rhythm. Here’s a simple cadence to build:

    • Daily: Reps update any deal they touched that day with a note and a next step. No exceptions.
    • Weekly: Managers review deals flagged as stale (no activity for a set number of days) and decide: keep it active, push the date honestly, or mark it lost.
    • Monthly: Clean up duplicate records, review overdue close dates as a batch, and confirm deal owners are correct.
    • Quarterly: Step back and audit the whole process. Are your stage definitions still accurate? Is the CRM structure still matching how your team actually sells?

    A common threshold teams use to flag a deal as stale is 30 days without contact activity, or 60 days sitting in an early stage like discovery. Set your own thresholds based on your typical sales cycle length, but pick something concrete. “It feels stale” isn’t a rule your team can act on consistently.

    Each cadence layer is solving a slightly different problem, which is worth being explicit about so the routine doesn’t collapse into just one habit. The daily layer keeps the data current in real time, so nobody’s reconstructing a week-old conversation from memory during Friday’s pipeline review. The weekly layer is where accountability actually happens, a manager looking at a specific stale deal and asking a rep directly what’s really going on with it, rather than letting the deal quietly age another week. The monthly layer catches the structural mess, duplicate contacts, deals assigned to a rep who left the company three months ago, that individual reps have no reason to notice on their own. And the quarterly layer is the one teams skip most often, even though it’s where you catch a bigger problem: stage definitions that drifted out of sync with how the team actually sells now, which no amount of weekly cleanup will fix.

    Pro tip: don’t let automation delete deals on its own. Automatically flagging stale deals is great, but let a manager make the final call on removing them during the pipeline review. Auto-deleting deals without a human check tends to create distrust in the system fast.

    This routine also feeds directly into how much pipeline you actually need. If you’re not sure how to size your pipeline against quota, our guide on What Is Pipeline Coverage Ratio? A Beginner’s Formula and Benchmarks walks through the math, but none of that math means anything if half the deals in your coverage number are zombies.

    Who Should Own Pipeline Hygiene?

    Someone needs to own it, or it won’t happen. In most orgs that’s the sales manager for day-to-day coaching and review, with RevOps (revenue operations, the function that manages the systems and processes behind sales, marketing, and customer success) setting the standards, building the automation, and reporting on hygiene metrics across the team.

    Reps should never be punished for marking a deal lost. If closing out a dead deal hurts someone’s numbers, they’ll just leave it open forever, and you’re right back where you started. Reward accuracy, not the appearance of a full pipeline.

    This incentive point is worth taking seriously rather than treating as a nice-to-have. If a rep’s activity metrics, or worse, their perceived pipeline health going into a QBR, are judged by raw pipeline volume, you’ve built a system that quietly rewards exactly the behavior you’re trying to eliminate. The fix isn’t a policy memo, it’s making sure the metrics a manager actually looks at, like weighted pipeline and stage-to-stage conversion, don’t get worse when a rep does the honest thing and closes out a dead deal.

    Summary

    Pipeline hygiene is the discipline of keeping every open deal’s stage, next step, close date, and contact info honest and current, not just technically updated. Without it, an estimated 40 to 60% of pipeline in the average B2B CRM sits stale, which means forecasts, coverage ratios, and quota planning are all built on top of deals that were never really alive. The problem rarely shows up as one obvious mess, it accumulates through small habits: a close date pushed forward every month, a deal left open after the prospect went dark, a missing next step nobody chases down.

    Fixing it doesn’t require new tooling, it requires a cadence: daily updates from reps, weekly manager review of stale deals, monthly cleanup of duplicates and ownership, and a quarterly audit of whether stage definitions still match how the team actually sells. RevOps typically sets the standards and builds the automation, while sales managers own the day-to-day accountability, and neither works if reps are penalized for marking deals lost honestly. An inflated pipeline was never real revenue, it just delayed the moment everyone found out.

    FAQ

    Is pipeline hygiene the same thing as CRM data hygiene?

    They overlap but aren’t identical. CRM data hygiene is broader, covering contacts, leads, and accounts across your whole database. Pipeline hygiene is specifically about the health and accuracy of open deals.

    How often should we run a pipeline hygiene review?

    At minimum, do a quick pass weekly. If your team relies heavily on near-term forecasts, review the highest-value deals even more often than that.

    What’s a stale deal, exactly?

    Most teams define it as a deal with no activity logged for 30 days or more, though some set stage-specific thresholds, like 60 days for a deal stuck early in discovery. Pick a number and stick to it.

    Doesn’t cleaning up the pipeline just make our numbers look worse?

    Short term, maybe. But an inflated pipeline was never real revenue, it was just an inflated number. Getting honest now is a lot less painful than a forecast miss later.

    Can automation fix pipeline hygiene for us?

    Automation helps a lot with flagging stale deals, reminding reps to update records, and reducing manual entry. But it works best paired with a human review step, not as a replacement for one.

    What’s the fastest way to tell if our pipeline has a hygiene problem right now?

    Pull every deal with no logged activity in the last 30 days and see what percentage of total pipeline value that represents. If it’s anywhere close to the 40 to 60% range commonly cited for stale pipeline, that’s a strong signal your forecast is currently built on deals that aren’t actually moving.