Tag: forecast categories

  • HubSpot Deal Stages: How to Set Up Your Sales Pipeline.

    HubSpot deal stages are the ordered steps a deal moves through inside a sales pipeline, from first conversation to closed won or closed lost. Each stage carries a win probability, which HubSpot uses to weight your pipeline and forecast, and each can require specific properties before a deal moves forward.

    Most teams inherit the default pipeline, rename a stage or two, and never look at it again. Then the forecast misses, reps argue about what “Qualified” means, and the pipeline fills with deals that haven’t moved in months. The fix usually isn’t a new tool. It’s a pipeline designed around evidence.

    This guide covers how deal stages work, how to design them, how to set probabilities from your own data, how they connect to lifecycle stages and forecast categories, and how to set it all up.

    Deal stage vs. lifecycle stage vs. forecast category

    These four fields get mixed up constantly, so it’s worth separating them before you build anything.

    Field Lives on Question it answers
    Deal stage Deals How far along is this specific deal?
    Lifecycle stage Contacts and companies What is our overall relationship with this person or company?
    Lead status Contacts and companies What is a rep doing with this lead right now?
    Forecast category Deals How confident are we that this will close this period?

    HubSpot’s default deal stages

    HubSpot’s default sales pipeline ships with seven stages and a default probability for each. The sales pipeline is available in every Sales Hub tier.

    Default stage Default probability
    Appointment Scheduled 20%
    Qualified to Buy 40%
    Presentation Scheduled 60%
    Decision Maker Bought-In 80%
    Contract Sent 90%
    Closed Won 100%
    Closed Lost 0%

    They’re a reasonable starting point, but they mostly describe what the rep has done: scheduled, presented, sent. They don’t say what the buyer has done, which is what actually predicts a close. And the percentages are generic, not yours.

    Design principles for deal stages

    • Use buyer milestones, not rep activities. “Buyer confirmed budget range” is more reliable than “demo given.”
    • Keep it to roughly five to eight stages. Too few and you lose visibility. Too many and reps skip stages.
    • Write entry and exit criteria for every stage, in one sentence each.
    • One pipeline per genuinely different motion, such as new business versus renewals. Avoid creating pipelines for every segment.
    • No graveyard stage. A “follow-up” stage where stalled deals sit forever hides risk. Close them or define a rule for moving them out.

    An example B2B SaaS pipeline

    Here’s one illustrative design. Yours should reflect your own sales process.

    Stage Entry criteria (buyer evidence) Required properties
    Discovery The buyer agreed to a first conversation about a specific problem Deal source, use case
    Qualified The buyer confirmed the problem, a rough budget, and a decision process Budget range, decision maker, timeline
    Evaluation The buyer is testing or reviewing the product with named stakeholders Champion, competitors considered
    Proposal The buyer has a written proposal and agreed to review it Amount, close date, next step date
    Negotiation Terms are being discussed, and legal or procurement is involved Procurement path, signer
    Closed Won Contract signed Contract start date, billing contact
    Closed Lost The buyer chose another option or no decision Closed-lost reason (dropdown), competitor

    For help defining the qualification evidence behind these gates, see our comparison of BANT and MEDDIC.

    Set probabilities from your own data

    HubSpot multiplies each deal’s amount by its stage probability to produce weighted pipeline. If the probabilities are guesses, so is the forecast. Replace the defaults with your actual history. Pull the closed deals from the last 12 months and, for each stage, calculate the share of deals that reached it and eventually closed won. Here’s an illustrative example in which 60 deals were won:

    Stage Deals that reached it Eventually won Win rate (use as probability)
    Discovery 400 60 15%
    Qualified 250 60 24%
    Evaluation 150 60 40%
    Proposal 100 60 60%
    Negotiation 75 60 80%

    Every won deal passed through every stage here, which is why the “won” column is constant. In real data, some deals skip stages, so adjust for that. Recalculate each quarter, and consider separate pipelines or probabilities where deal size or segment changes the odds. For more on how weighting works, see our guide to weighted pipeline.

    How deal stages connect to lifecycle stages

    Deals drive part of the lifecycle stage on the associated contact and company. In HubSpot, a record becomes an Opportunity when it’s associated with a deal, and a Customer when it has at least one closed deal, provided you’ve turned on the settings that update lifecycle stage from associations. Lifecycle stages only move forward by default, so a customer isn’t pushed back to Opportunity when a new deal is created. Decide up front which of these updates you want, and review them in your settings. Our explanation of HubSpot lifecycle stages covers the details.

    How deal stages connect to forecast categories

    Stage probability is a statistical estimate based on history. A forecast category is a person’s judgment about this deal this period. They’re different, and many teams use both. HubSpot’s forecast can use a forecast category property on deals, and some teams add their own custom category property as a confidence overlay. Check how your forecast is configured before you rely on either.

    One way to keep them consistent is to map each stage to a default category and let reps adjust only with a stated reason. Here’s an illustrative mapping:

    Stage Default category
    Discovery, Qualified Pipeline
    Evaluation, Proposal Best Case
    Negotiation Commit, if the evidence criteria are met
    Closed Won Closed
    Closed Lost Not forecasted

    Our guide to forecast categories explains how to define each label by evidence, so Commit means the same thing for every rep.

    Enforce and automate

    A pipeline is only as good as the rules behind it. HubSpot lets you require properties when a deal enters or leaves a stage, which on Professional and Enterprise plans is one of the most useful and most overlooked settings. Pair it with automation:

    • Required properties at the stages shown above, including close date and amount before Proposal, and a closed-lost reason before a deal can be marked lost.
    • Workflows on stage change: create a task for the next step, notify the account team, or alert finance when a deal reaches Closed Won.
    • Stale-deal alerts: notify the owner when a deal has sat in a stage longer than your typical time.
    • Close-date checks: flag deals whose close date has been pushed more than once. Our explanation of deal slippage covers why this matters.

    Make the closed-lost reason a dropdown, not free text, so you can report on it. It’s also the raw material for win-loss analysis.

    Reports worth building

    • Weighted pipeline by stage and by owner
    • Stage-to-stage conversion rates
    • Average days in each stage, with a list of deals beyond your normal range
    • New pipeline created against target
    • Closed lost by reason, with deal count and value

    How to set it up in HubSpot

    1. Write your stages first. Draft names, entry and exit criteria, and required properties in a document, with sales leadership signing off.
    2. Open the pipeline settings. Go to Settings, then Objects, then Deals, then Pipelines. Deal stages are managed there, not through the general Properties menu.
    3. Create or edit the pipeline. Rename stages, add new ones, and drag to reorder.
    4. Set a probability for each stage from your historical data.
    5. Set required properties for the stages that need them, if your plan supports it.
    6. Move existing deals before deleting a stage. A stage that still holds deals can’t simply be removed, so map old stages to new ones first.
    7. Brief the team, then review conversion and days-in-stage after a month and adjust.

    Mistakes to avoid

    • Keeping HubSpot’s default probabilities without checking them against your data
    • Naming stages after rep activities instead of buyer milestones
    • Creating a stage for every possible situation, so reps skip around
    • Making a closed-lost reason optional or free text
    • Letting deals sit in stages with no close date or next step
    • Building several pipelines when properties or segments would do
    • Changing stage definitions mid-quarter without telling the team

    Summary

    HubSpot deal stages track how far along each deal is, and each carries a win probability that feeds weighted pipeline. The defaults, from Appointment Scheduled at 20% to Contract Sent at 90%, describe rep activity and use generic percentages. Better pipelines use five to eight stages tied to buyer milestones, with written entry and exit criteria, required properties, and probabilities calculated from your own closed deals.

    Deal stage differs from lifecycle stage, which describes the overall relationship, and from forecast category, which captures confidence this period. Deals move contacts and companies forward through lifecycle stages when associations settings are on. Enforce the design with required properties, workflows, stale-deal alerts, and a required closed-lost reason, then review the pipeline monthly.

    FAQ

    What are the default HubSpot deal stages?

    Appointment Scheduled (20%), Qualified to Buy (40%), Presentation Scheduled (60%), Decision Maker Bought-In (80%), Contract Sent (90%), Closed Won (100%), and Closed Lost (0%). They’re editable starting points.

    How many deal stages should a pipeline have?

    Most B2B teams do well with roughly five to eight. Fewer than that limits visibility, and more than that encourages reps to skip stages or guess.

    How do I change deal stage probability in HubSpot?

    Open Settings, then Objects, then Deals, then Pipelines, edit the pipeline, and set the probability for each stage. Base the numbers on how often deals at each stage actually closed in your last 12 months.

    Is deal stage the same as lifecycle stage?

    No. Deal stage tracks one deal’s progress. Lifecycle stage describes a contact or company’s overall relationship with you. A deal being created or closed can update lifecycle stage if the related settings are on.

    Can I require fields before a deal moves to the next stage?

    Yes. HubSpot lets you set required properties at the point a deal enters a stage, available on Professional and Enterprise plans. Use it for close date, amount, next step, and closed-lost reason.

    Should I use more than one pipeline?

    Only for genuinely different sales motions, such as new business and renewals. For differences like segment or region, use deal properties and filters instead, because more pipelines make reporting harder.

    How do deal stages relate to forecast categories?

    Stage probability is a historical estimate, while a forecast category is a judgment about confidence this period. Many teams map each stage to a default category and let reps adjust with a reason. Check how your HubSpot forecast is configured.

    What should I do with deals stuck in a stage?

    Set a normal time per stage, alert the owner when a deal exceeds it, and require a next step and close date. If nothing is happening, move the deal back to an earlier stage or close it with a reason.

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