Sales forecasting in HubSpot: how to build a forecast you can defend

Sales forecasting is predicting how much revenue will close in a period from the deals already in your pipeline. In HubSpot, the forecast multiplies each open deal's amount by its stage probability, or groups deals into categories like Commit and Best case. It is only as accurate as the stage rules, deal data and probabilities underneath it.

Somebody is going to ask why last quarter came in under forecast. Usually a board member, sometimes an investor, occasionally the bank. The honest answer, most of the time, is that nobody ever wrote down what the deal stages mean, so every rep made their own call, and the number you presented was the sum of those guesses.

That makes forecast accuracy a governance question before it is a sales one. People make hiring, spending and lending decisions on a number your CRM produced. If you cannot explain in a meeting how that number was built, you cannot defend it in one either. This guide covers how HubSpot forecasts, why its forecasts miss, and the fixes in the order we make them: stage rules, GST, a data audit, calibrated probabilities, the automations that keep it all maintained, the reports and the weekly review.

How does HubSpot forecast sales?

Two ways, and most teams use both.

The first is the weighted pipeline. Every stage in a HubSpot deal pipeline carries a probability, and HubSpot multiplies each deal's amount by it. A $50,000 deal in a 60% stage counts as $30,000. Add them up and you have a weighted total, shown on the board view and available in reports on every plan.

The second is the forecast tool, included with Sales Hub and Service Hub Professional and Enterprise. Managers set revenue goals per rep and per team, and deals roll up into forecast categories: Not forecasted, Pipeline, Best case, Commit and Closed won. Reps submit their own call on a schedule, and the manager sees goal attainment, the gap to goal and pipeline coverage side by side.

HubSpot's default sales pipeline ships with these stage probabilities. They are a starting point someone at HubSpot chose, and they say nothing about how your team converts.

Source: HubSpot Knowledge Base, set up and manage object pipelines, checked 9 November 2026.

Why do HubSpot forecasts miss?

Almost never because of the forecasting tool. The error sits in what feeds it. These are the five causes we keep finding in Australian portals:

• Stages nobody defined. Each rep moves deals on their own judgement, so a deal in Contract sent means different things depending on who owns it.
• Mixed GST treatment. Some amounts include GST and some do not, so the pipeline never reconciles with the accounts.
• Probabilities nobody revisited. The percentages set at implementation, or HubSpot's defaults, never checked against real win rates.
• Stale deal data. Close dates in the past, amounts from the first conversation, dead deals nobody closed out.
• The wrong year. Reporting cut on January to December while finance closes the books on 30 June.

The diagram shows how those inputs reach the number you present, and where the corrections come back in.

The order we work in on a HubSpot forecasting fix. The dashed line runs once a quarter: the forecast against what closed tells you which input to correct.

How do you define deal stages a forecast can rely on?

Give each stage entry and exit criteria that someone other than the rep could check. A deal moves from Qualified to buy into Presentation scheduled when the discovery call has happened and a formal meeting is booked in the calendar. Two checkable facts. Once that holds across the pipeline, a deal in a given stage represents the same amount of progress no matter who owns it, and the numbers underneath start to mean something.

Then make HubSpot hold the line. On Professional and Enterprise you can make properties required when a deal enters a stage, so a rep cannot move a deal forward without entering the proof: budget confirmed, decision maker identified, close date revised. Required fields should match the information the rep genuinely has at that point. Ask for it too early and you get guesses typed in to clear the gate.

Most portals are a long way from this, which is why what is actually wrong with most HubSpot deal stage setups is the first thing to read, and how to build a HubSpot pipeline your reps use covers the build itself.

Should HubSpot deal amounts include GST?

Pick one rule for everybody and write it on the Amount property's description. Most teams are better off holding the amount ex GST, so the pipeline reconciles with the profit and loss, and letting the quote carry the GST inclusive figure the client sees.

Here is why it matters. Take a $180,000 contract, GST inclusive. The revenue in it is about $163,600, because the other $16,400 belongs to the ATO. If that deal sits in Contract sent at 90%, your weighted forecast books $162,000 when the revenue behind it is about $147,000, which is $15,000 too high. A pipeline that reports GST inclusive amounts as revenue is overstated by 10% before anyone has argued about probability. Mix the two treatments across deals and the error changes size from one month to the next, which is worse, because nobody can correct for it.

The same rule has to cover the deals that came across in a migration, and any amount an integration writes from your quoting or accounting system.

How do you audit HubSpot data before you forecast?

Incomplete, stale or inconsistent data produces a forecast with the same flaws, presented as a confident chart. Run these checks before the number goes in front of anyone, and again 90 days later to see whether the fixes are holding.

1. Amounts and close dates. Every open deal has an amount, and a close date in the future with a reason behind it. Put any deal more than 60 days past its original close date in front of a manager.
2. A decision maker on the record. If nobody on the buying side is associated with the deal, nobody has qualified it.
3. Stalled deals. HubSpot's stage calculated properties record the date each deal entered each stage and how long it has spent there, retroactively. Sort by time in stage. A deal with no client contact in 30 or more days should either get a specific next action with a date, or be closed lost with a reason. HubSpot also sets an Is Stalled After Timestamp property automatically, at the moment a deal's time in stage runs 20% past the owner's closed won average for that stage, so you can filter or alert on it.
4. Duplicates and dead deals. Merge the duplicates and close out the dead. They inflate the top line and hide the real one.
5. Contacts still at MQL on live deals. In the custom report builder, report on contacts whose lifecycle stage is still lead or marketing qualified lead while an associated deal is open. If you find many, lifecycle stages are not syncing with deal activity, which is common when Marketing Hub and Sales Hub were set up separately. Turn on the lifecycle stage sync in the contact settings, so a contact becomes an opportunity when a deal is created and a customer when it closes won. Fixing lifecycle stages before you trust a forecast covers the criteria and who owns them.
6. Attribution gaps. Report on open deals whose contacts have no original source. The usual causes are tracking code that was not on the site when the contact arrived, or an import that skipped a tracked conversion. Reconnecting an ad account can switch off auto tracking without any warning, so check the connected ad accounts monthly. Capturing UTM parameters in HubSpot forms closes most of the gap.
7. The financial year. HubSpot's reporting periods start in January unless someone changed the fiscal year in the account defaults, and the Australian income year runs 1 July to 30 June. A Super Admin can set the fiscal year to July to June under Settings, Account Defaults. Then re-run your saved pipeline reports and check the totals against the period finance reports on. A forecast that straddles two financial years is one of the most common reasons the numbers never reconcile at EOFY.

Hand the fixes to deal owners with a five business day deadline. Structural changes go in order: required properties first, so no new bad data arrives, then the automation below, then probability calibration, which needs clean data to mean anything.

Integrations need the same discipline. Decide which system is the source of truth for each kind of data before you connect it: HubSpot for deals and pipeline, the ERP or accounting system for billing. Map the fields, test with a sample and watch the sync status in HubSpot's connected apps view. An integration that labels the same stage differently in two systems leaves deals sitting in the wrong stage. If you are an APRA regulated entity, CPS 230 has applied since 1 July 2025 and expects you to understand the data your critical operations depend on, which is covered in whether your AI vendor is a material service provider under CPS 230.

How do you set stage probabilities from your own win rates?

Use your history, not HubSpot's defaults. In the custom report builder, build a report of deals closed in the last 12 months, grouped by the last stage each deal reached before it closed. Compare the share that closed won from each stage with the probability configured in your pipeline settings.

Where the gap is wide, change the probability. If your Contract sent deals actually close 65% of the time, a 90% setting overstates every quarter by the same amount in the same direction, and that gap is what you end up defending when the quarter lands under the weighted number. Recalibrate at least once a year, and after any real change to how you sell, such as a new product, a new price or a new sales team.

Stage is not the only input you can use. For one client we replaced stage-based probability with a score built from their own qualification questions: each yes or no moves the deal's probability, and the result sits in its own property beside HubSpot's. We also keep snapshots of that probability at 30, 60 and 90 days, so the team can see whether the score is getting more accurate over time.

Which HubSpot automations keep a forecast honest?

The ones that remove the human memory from the process. A forecast that depends on reps remembering to update deals gets tidied up the day before the meeting. These are the six we set up:

A few notes from setting these up. Automate forecast categories is a switch in the forecast settings, and once it is on, a deal's category follows its stage, so map each stage to a category that matches your real confidence. Deal scores are AI generated predictions of the chance of winning each open deal. On their own they are a column. A workflow that creates a task for the manager when a Commit deal's score drops is what turns them into pipeline management. Stall alerts use the time in stage properties from the audit as the trigger, with a named person who gets the task and a clear expectation of what happens next.

Every automation here amplifies what is already there. Put it on top of undefined stages or dirty data and it produces the wrong number faster.

Which reports belong on a forecasting dashboard?

Start with three: deals closed against goal, the deal funnel, and deal stage probability. That is enough to see whether the current trajectory hits the target and where deals slow down. Then add the reports that make the forecast checkable:

Take the push rate to your board yourself. It is the most honest number in the portal, and it buys credibility for everything else you present. For the build, HubSpot's custom report builder and its data sources and five HubSpot dashboards for running revenue go step by step. If you also want to forecast the effect of marketing spend, the split between marketing sourced and sales sourced pipeline comes from HubSpot attribution reporting and what each model tells you.

Our walkthrough shows how to build a custom sales forecasting dashboard in HubSpot, report by report.

Should you trust HubSpot's AI forecast?

Treat it as a second opinion. The forecast tool in Sales Hub Professional and Enterprise can project revenue from your history, independent of the number your team typed in, and deal scores work one level down. Their real use is finding the deal that looks fine on the board and is in trouble: the champion has gone quiet, the meetings stopped three weeks ago, the stage never changed.

If part of the number you hand your board comes from a model, somebody has to be able to say what it used and why it was believed. The National AI Centre's Guidance for AI Adoption, published in October 2025, sets out essential practices for Australian businesses, including keeping a human in control, and it is a better starting point for that conversation than a vendor deck. The market is still early. The ABS found around 12% of Australian businesses used AI in 2024-25. Point a predictive forecast at data you have not cleaned and you get a confident wrong number, faster.

How should a weekly forecast review run?

Same agenda every week: the current pipeline and forecast, confirm the Commit deals, then work through Best case and Pipeline and what would move each one. Weekly is enough for most teams.

Then the part no report gives you. A rep knows the CFO who championed the deal has left, or that a budget freeze hit one segment last week. Those facts change the forecast and never appear in a field. Custom properties help with the rest: record what actually moves your number, such as the competitor you are up against, the new product in the deal or the segment you are betting the year on, and put them on the dashboard. Then you can answer the board's second question. Where is the number coming from, and what happens if that one segment goes quiet?

Once a quarter, open the forecast against actuals report. Across four or five quarters the patterns show up: optimism of a consistent size, one segment that always underperforms, a stage where deals are habitually overvalued. Correct the model rather than the story. A leader who can state their own forecast accuracy over the last four quarters, before being asked, is in a different meeting from one who cannot.

Timing matters too. If you want a full financial year of clean data, start the fixes a couple of months before 1 July, while the June quarter is still ahead of you.

Frequently asked questions

What is sales forecasting? Predicting how much revenue will close in a coming period from the deals in your pipeline, usually by weighting each deal by how likely it is to close. A good forecast also shows which deals carry the number and how accurate past forecasts were.

What is the difference between a weighted pipeline and forecast categories in HubSpot? A weighted pipeline multiplies each deal's amount by its stage probability. Forecast categories group deals by confidence, from Pipeline through Best case to Commit, and let reps submit their own call. Most teams compare the two each week.

Which HubSpot subscription includes the forecast tool? Sales Hub or Service Hub Professional or Enterprise. Weighted deal amounts and pipeline reports are available on every plan.

Should HubSpot deal amounts include GST? Choose one rule for every deal and write it on the property. Most Australian teams hold amounts ex GST so the pipeline reconciles with the profit and loss, and show the GST inclusive figure on the quote.

How often should you recalibrate HubSpot stage probabilities? At least once a year, and after any real change to how you sell. Compare the share of deals that closed won from each stage over the last 12 months with the configured probability.

Read next

• Fix your lifecycle stages before you trust another HubSpot forecast
• HubSpot deal stages: what to fix and what is new
• How to run HubSpot deals so your pipeline stops lying
• HubSpot attribution reporting: what each model tells you
• How HubSpot and Forecast.app close the sales to delivery gap

Sources

• Set up and manage object pipelines, HubSpot Knowledge Base, for default stages, probabilities and the weighted amount.
• Use the forecast tool and Set up the forecast tool, HubSpot Knowledge Base, for subscriptions, forecast categories, automated categories and submission reminders.
• Stage calculated properties, HubSpot Knowledge Base.
• Predict likelihood to close with deal scores, HubSpot Knowledge Base.
• Use lifecycle stages, HubSpot Knowledge Base.
• Create reports with the custom report builder, HubSpot Knowledge Base.
• Business adoption of artificial intelligence accelerates, Australian Bureau of Statistics, for AI use in 2024-25.
• Guidance for AI Adoption, National AI Centre, October 2025.

---

Neighbourhood rebuilds pipelines, audits the data behind them and sets up forecasting in HubSpot for Australian businesses, as part of our RevOps and HubSpot work.