HubSpot Forecast Tool: Setup, Categories and Limits

The HubSpot forecast tool is the Sales Hub and Service Hub feature, in Professional and Enterprise, that shows each rep's and team's forecast against a revenue goal for a month or a quarter. Deals roll up by deal stage or by forecast category: Not forecasted, Pipeline, Best case, Commit and Closed won. Reps submit a number and managers review it.

Many ORM customers run HubSpot as their CRM, so I see its forecast page often. This guide covers how it works, which plans include what, how to set it up, the limits HubSpot documents, and where the native forecast stops being enough. Every feature and plan claim below comes from HubSpot's own knowledge base, developer docs or pricing page, read in October 2026. If you run Salesforce instead, the matching guide is Salesforce forecasting.

How does the HubSpot forecast tool work?

HubSpot adds up the deals in a pipeline for a forecast period, shows them by deal stage or forecast category for each rep and team, and compares the total to a revenue goal. You open it under Sales, Forecast. The Team table shows Goal, Closed Won, Gap and Forecast Submission. The Pipeline table shows Open pipeline and Open pipeline coverage. Each user row adds goal attainment, weighted or total pipeline, the amount in each category, and their submission.

Eight pieces make it run:

Sources: HubSpot Knowledge Base, Set up the forecast tool, Use the forecast tool, Create a forecast to view multiple outcomes and Improve forecasting with AI projections; HubSpot forecasts API guide for the four-type limit.

Which Sales Hub tiers include forecasting?

The forecast tool comes with Sales Hub or Service Hub Professional or Enterprise, and each user needs an assigned Sales or Service seat. Super Admins can open it without a seat. Free and Starter do not include it. Here is what HubSpot's own pages say by tier: Sources: the knowledge base articles above; Split deal credit among users for deal splits; Set up and customize pipelines for pipeline counts on seat-based pricing; the Sales Hub pricing page and product and services catalog for prices. In October 2026 the pricing page showed Professional at $90 per seat per month with an annual commitment, against the $100 list price. Prices and promotions change, so check your quote.

Two practical points. First, the hierarchy line matters if you have managers of managers: HubSpot says the forecast "uses the team hierarchy set up in users and teams," and the pricing page lists hierarchy forecasting on Enterprise. Second, if you sell in teams and split credit, only Sales Hub Enterprise shows split amounts in the forecast.

Forecast categories vs deal stages in HubSpot

A deal stage says where the deal is in your process and carries a win probability. A forecast category says how confident you are it closes in the period. In HubSpot they are separate properties, and you decide how tightly to tie them. That is a real difference from Salesforce, where the category comes straight from the stage.

Deal stages live on the pipeline. HubSpot's default sales pipeline uses these probabilities: 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%. The weighted amount is the deal amount times that probability.

Forecast categories live on the deal, in the Forecast category property. In Settings, Objects, Forecast, on the Pipelines tab, you map each stage of each pipeline to a category. Turn on Automate forecast categories and HubSpot creates a workflow called "Forecast Category Mapping for Pipeline: [pipeline name]" that applies the mapping as deals move. A rep or manager can still open a deal, choose View all properties, and change the category by hand.

HubSpot leaves the mapping to you. Here is one common way to set it up on the default pipeline:

The forecast page has a Deal stage tab and a Forecast category tab, so you can read the same pipeline both ways. When the two disagree, for example a Contract sent deal the rep has moved down to Best case, that disagreement is the most useful thing on the page. If you automate the mapping and nobody overrides it, the category view is just the stage view with new labels. For the general case, see forecast categories vs pipeline stages, and for how teams define the two middle buckets, commit vs. best case.

You can rename the categories or add values (Setup tab, Edit forecast categories). HubSpot notes that only the last five additional values appear in the mapping, so reorder them if a value goes missing.

How do you set up the HubSpot forecast tool?

Pick the amount and period, map stages to categories in each pipeline, set permissions and goals, then decide on custom types and AI. You need Super Admin permissions to change forecast settings. These steps follow HubSpot's knowledge base:

1. Check seats and permissions. Every forecasting user needs a Sales or Service seat. Give the Forecast permission (View and Edit) in user permissions, scoped to forecasts the user owns or forecasts their team owns. HubSpot syncs forecast permissions between Sales and Service. 2. Build your teams. The forecast rolls up through the team structure in Users and Teams, so set it up before reps start submitting. 3. Choose the forecast deal amount. Settings, Objects, Forecast, Forecast deal amount: Weighted amount (the default) or Total amount. 4. Set the forecast period. In the same settings, choose monthly or quarterly for all pipelines. Decide this with Finance once, because changing it resets goals and submissions. 5. Map stages to categories. On the Pipelines tab, pick each pipeline and set a category for every stage, then Save. Turn on Automate forecast categories if you want the workflow to apply it. 6. Rename or add categories if needed. Setup tab, Edit forecast categories, then edit the dropdown options. 7. Create Forecastable Revenue goals. Sales, Forecast, Create goal, keep the Forecastable Revenue template, and configure it. Goals only show when their filters (dates, pipeline) match the forecast view and they cover one pipeline or all pipelines. 8. Turn on the submission status indicator. Under Forecast submissions, tick the indicator. It defaults to 8 days and can go up to 31, and shows only when the view is on the current period. 9. Set the table columns. Customize the forecast category table, and choose default columns for the forecasting deal table, so every manager sees the same fields. 10. Add custom forecast types (optional). Sales, Forecast, Create Forecast type, then pick a date property and a currency amount property, such as a services revenue field or a contract start date. 11. Turn on AI forecasting (optional). Opt the account into the public beta; a Super Admin then turns it on. It needs 24 hours or more to collect data.

If your team sells new business, expansion and renewals, consider separate pipelines for each before step 5. Professional allows 100 pipelines beyond the default, and each pipeline gets its own stage probabilities and mapping.

How do reps submit a forecast?

In Sales, Forecast, the rep clicks Submit in the Forecast Submission column, picks the pipeline and period, and enters a number or selects the deals that make it up. For a user's forecast, ticking deals in the Add to Forecast column sets the submitted amount to the sum of those deals, and the rep can add a note. Managers see submissions for their team alongside goal, closed won and gap.

A few behaviors worth knowing:

- Submission history is kept for one year, on the History tab. - Only Super Admins can set submission reminders or delete submissions. - Open deals and goals use current exchange rates; closed won deals use the rate on their close date; manual submissions keep the rate from when they were submitted.

The submission is the rep's call, which makes it a forecast submission in the classic sense: judgment, recorded on a schedule. That is useful. It is also the number to test against what the data says, which is what the next two sections are about. The Open pipeline coverage figure on the same page is worth reading with care too; see pipeline coverage for why a coverage ratio alone hides the composition of the quarter.

What do HubSpot's AI forecast and accuracy tracking do?

The AI forecast projects a range for the period from your recent closed won deals, and the accuracy view scores past submissions against what actually closed. Both sit on the forecast page.

The AI forecast is a public beta for Sales Hub and Service Hub Professional and Enterprise. In HubSpot's words, it uses "Breeze, HubSpot's AI, to project future sales based on closed won deals in the past three months." It shows a range, "with the midpoint of the range being where you are most likely to land," plus upper and lower bounds. HubSpot refreshes it on days 1, 7, 14, 21 and 28 of every month, and you find it on the Analyze tab. A Forecast accuracy over time table compares past AI projections to closed won totals, and it needs a monthly forecast cadence.

Accuracy tracking for submissions lives under Update, then View history, in the Forecast submission column. HubSpot defines it as:

Forecast accuracy = the greater of 0 and (1 minus |Actual minus Forecast| / Actual)

In Excel or Google Sheets: =MAX(0, 1 - ABS(Actual - Forecast) / Actual). A team that submitted $900,000 and closed $1,000,000 scores 90%. A team that submitted $1,100,000 and closed $1,000,000 also scores 90%, so the score does not tell you which way you missed. Track the sign of the error separately; forecast bias is the measure for that, and our forecast accuracy scorecard does both.

My read on the AI beta, not HubSpot's: three months of closed won deals is a short window. Seasonality moves a SaaS quarter a lot. Across ORM customers Q4 is usually the largest quarter, followed by Q2, Q3 and Q1, and within a quarter the third month is always the largest and the first the smallest. A projection made in January from the last three months has just watched Q4. Use the range as one input, which is also what HubSpot advises: projections should inform decisions, not be the only basis for them.

What limits and gotchas does HubSpot document?

The ones that cost you are resets and deletions: changing the period wipes goals and submissions, and deleting a forecast type deletes its history. Here is what HubSpot's docs say, in one place: Sources: the HubSpot knowledge base and developer docs linked above.

Where does the HubSpot forecast break?

The forecast is a sum of what reps have entered, weighted by stage probabilities or sorted by the categories reps chose. It is accurate when that input is disciplined and inherits every error when it is not. That is not a flaw in HubSpot. It is what a roll-up is. Here is where I see it break:

- Default probabilities are not your history. The weighted amount uses stage probabilities you or HubSpot set, not the rate at which your deals in that stage actually close. Few teams recalibrate them; see CRM stage probability vs historical conversion rates. - Stages are subjective. Stage weighting works if each stage has strict entry and exit criteria. When it does not, the stage is the rep's judgment, and you are applying an objective weight to a subjective input. You will miss at the end of the quarter. - One weight for every deal. New business, expansion and renewals often share one pipeline, even though they close very differently. Renewals close on a known date, usually within about 30 days either side of it. New business timing follows the last stage change. - The forecast only sees deals that exist. A quarter has three sources: carry-over deals open on day one, deals created and closed inside the quarter, and deals pulled forward from later quarters. Deals not yet created cannot roll up, so a quarter with a strong in-quarter motion looks thin early. - Amounts run high. Most deals close for less than the amount in the CRM. A pipeline can carry an average deal of $80,000 while closed-won deals average $40,000. - Close dates drift. Across ORM customers, only about 20% of the pipeline dated to close in the quarter on day one closes in that quarter. The best slip signal is a rep changing the close date, and the earliest one is no signal at all: no stage change, no amount change, no notes.

The submission and the manual category override exist for exactly this reason: a manager who knows a rep runs optimistic can change the number. That is judgment layered on a sum. It works when the manager is right and is hard to audit when the board asks why the number moved. The odds are not great for anyone: Gartner reports a median forecast accuracy of 70% to 79%, and only 7% of sales teams reach 90% or better.

Illustrative example: one quarter, three views

Take a quarter with a $1,200,000 goal, at mid-quarter, on HubSpot's default probabilities and the mapping in the table above. All amounts and rates are illustrative.

The weighted view says $1,630,000 against a $1,200,000 goal, 136% of it. The category view says Closed plus Commit is $800,000 and adding Best case reaches $1,200,000, exactly the goal.

Now suppose your own history says Commit deals close at about 75% of their amount within the quarter, Best case at 30% and Pipeline at 8%, and that you usually create and close about $120,000 of new deals in the second half of a quarter:

Weighted pipeline says $1,630,000. The categories say the goal is reachable if every Best case deal lands. A model built on your history says about $1,000,000, with a range around it, and a gap of about $200,000 to work on now. None of those is "the" answer. The value is seeing all three, and knowing that $120,000 of the expected number is not in HubSpot yet.

When do teams add a dedicated forecasting layer?

Usually after a missed quarter with no early warning, or when RevOps is buried in spreadsheets keeping the forecast alive. Those are the two triggers I hear most. A miss by itself is survivable. A miss nobody saw coming breaks trust. On the operations side, I have seen Sales Ops teams maintaining 37 spreadsheets with 12 tabs each, and then being asked to run the forecast call too.

Signs the native forecast is no longer enough:

- The forecast swings late in the quarter, and nobody trusts it until the last few weeks. - Commit regularly closes well below its total, and the real forecast lives in manager overrides. - New, expansion and renewal revenue need different logic, and stage probabilities cannot hold it. - A large share of the quarter comes from deals created inside it. - The board wants a range (low, on-target and high) that rolls up the same way from region to company.

Native HubSpot forecasting is the better choice when stages have strict criteria, the team closes a handful of deals a month (too few for a model to learn from), and managers run a disciplined weekly call. A model needs volume: at a minimum a couple of hundred closed-won deals, and at least a year of history to read seasonality.

There are two kinds of layer. A HubSpot-native app such as Forecastio sits inside HubSpot and is self-serve; we compare that approach in ORM vs. Forecastio. ORM is the other kind: it reads your HubSpot data, snapshots the pipeline every day, and models close timing, amount and seasonality from your own history, with your CRM and sales process left as they are. ORM targets 95% accuracy with no manual adjustments, from day 1 to day 90 of the quarter. Some teams keep the rep submission beside it on purpose: one view of what the field believes and one of what the data says. For the full comparison, see ORM vs. HubSpot, and for the wider market, the best sales forecasting tools.

How to get more out of HubSpot forecasting today

Most gains come from process, not settings. Five habits that help whichever tool sits on top:

1. Write entry and exit criteria for every stage, and enforce them with required properties, because the stage sets the probability and usually the category. 2. Split motions. Put new business, expansion and renewals in separate pipelines, so each gets its own probabilities, mapping and goal. 3. Recalibrate probabilities once a quarter from what your deals in each stage actually closed at, instead of keeping the defaults. 4. Read the stage tab and the category tab side by side. Review every deal where the rep's category disagrees with the stage, and every close-date push. A deal that slips from one quarter to the next is less likely to close, even in Commit. 5. Talk to sales leaders before the call. The RevOps person who owns the forecast should be talking to sales leaders daily, and always before the weekly forecast call, to test the assumptions behind the number. A forecast cannot be built in a vacuum.

If you are deciding whether the CRM's forecast should stay your main number, our guide to CRM forecasting vs. dedicated forecasting lays out the trade-off.