
Short answer: HubSpot’s forecast is as accurate as the deal stages, amounts and close dates feeding it. The tool itself is sound. To find out how far you can trust yours, compare last quarter’s week-one forecast with what actually closed. Then fix the stage definitions and close-date habits causing the gap.
The short version
- The forecast tool needs Sales Hub or Service Hub Professional or Enterprise, plus an assigned Sales or Service seat.
- It forecasts by deal stage by default, using each stage’s likelihood to close.
- Pipeline coverage is built in. It shows in the forecast tool once goals are set.
- Most forecast misses come from three habits: loose stage definitions, optimistic close dates and stale deals left open.
- A simple back-test tells you how far off you are today.
- Claude can flag the deals most likely to slip before the forecast call.
The forecast is one of the five numbers that close the executive reporting gap, and it’s the one leaders most often stop believing.
What do you need to use HubSpot’s forecast tool?
You need Sales Hub or Service Hub Professional or Enterprise, an assigned Sales or Service seat, and Forecast permissions on your user. Super Admins can use it regardless of seat.
You also need forecastable revenue goals assigned to the team. Without goals, there’s no gap to goal, so coverage can’t be worked out. Forecast categories are optional.
How does HubSpot calculate the forecast?
By default, HubSpot forecasts by deal stage, using each stage’s likelihood to close. You can show the weighted amount or the total amount. Weighted means each deal’s amount multiplied by its stage probability, so a £50k deal in a 40% stage counts as £20k.
There are three views worth knowing, and they answer different questions. (For where the forecast sits alongside the other Monday numbers, see the five reports a CEO should see.)
| View | What it shows | Best for | Where it goes wrong |
|---|---|---|---|
| By deal stage | Weighted or total pipeline by stage | A quick read of what’s in play | Stage probabilities nobody has checked in years |
| By forecast category | Deals grouped by the category reps assign | Separating commit from best case | Reps who never update the category |
| Forecast submissions | A custom amount each rep or manager expects to close | The number leadership signs off on | Submissions entered without looking at the deals |
The forecast tool also shows open pipeline coverage: open pipeline divided by the gap to goal. Say the quarter’s goal is £300k and you’ve closed £100k. The gap is £200k, so £600k of open pipeline is 3x coverage. Whether that’s enough depends on your win rate. If you win about a third of pipeline by value, 3x only just gets you there (I’d want more).
It’s one of the most useful numbers in HubSpot. It sits in the forecast tool rather than on your dashboards, though, so it’s easy to forget it’s there.
Why do HubSpot forecasts miss?
HubSpot forecasts miss because the inputs drift, not because the maths is wrong. We see the same three habits in most portals.
Stage definitions are loose. If “proposal sent” can mean a PDF or a quick email with a price, the stage probability is meaningless.
Close dates are wishful. Reps set the end of the month, then push it a month at a time. The forecast keeps counting deals that were never closing this quarter.
Dead deals stay open. A deal with no activity for 90 days is still in the weighted pipeline. (Everyone in the room knows it’s not closing. The forecast doesn’t.)
How do you test your forecast’s accuracy?
Compare what you forecast at the start of last quarter with what actually closed. That one number tells you how much to trust this quarter’s.
- Pull the forecast as it stood in week one of last quarter. Use the forecast tool’s submission history, which goes back up to a year.
- Pull closed won for the same quarter.
- Work out the gap as a percentage of the forecast.
- Repeat by rep and by pipeline. The gap is rarely spread evenly.
- Check stage probabilities against history. If 40% of deals at “proposal” usually close, the stage should say 40%.
Here’s a made-up example. In week one of last quarter the team submitted £450k and went on to close £360k. The gap is £90k, or 20% of the forecast. Split by rep, one rep forecast £150k and closed £60k, while the other three closed what they forecast. So the fix starts with one rep’s close dates, not the whole team’s process.
If the gap is big, don’t adjust the forecast by gut. Fix the inputs.

How do you make the forecast more accurate?
Tighten the inputs, then review them every week.
- Write exit criteria for every stage and make the key properties required when a deal moves.
- Make close dates earn their place. A date pushed twice gets a conversation in the pipeline review.
- Close out stale deals. Set a rule, such as no activity in 60 days means closed lost or a reason why not.
- Reset stage probabilities each quarter from your actual conversion history.
- Use forecast categories for judgement and deal stages for process. Don’t let one stand in for the other.
Two built-in features help the weekly habit. Super Admins can set a forecast submission schedule, so reps get a reminder before each review. And when you drill into a rep’s deals, a green or red dot under the deal stage shows it moved forward or back in the period, which makes “why did the forecast change?” a quicker conversation.
The definitions behind all of this are covered in one version of revenue truth.
Where does Claude help with forecasting?
Claude connected to HubSpot can read the open pipeline and flag the deals most likely to slip before the forecast call. It can also explain why the forecast moved since last week.
Useful questions to ask it:
- “Which deals in this quarter’s commit have had their close date pushed more than once?”
- “Which open deals over £20k have had no activity in 30 days?”
- “Why is this week’s forecast lower than last week’s?”
A HubSpot Super Admin (or a user with App Marketplace Access) has to connect or approve the connector first. Set write tools to Needs Approval so Claude can’t change deals without someone signing it off. The setup is in how to connect Claude to HubSpot using MCP, and the wider method is in advanced revenue reporting.
How far off is your forecast? Free until 12 January, book a 30-minute Day One session. We look at your HubSpot live with Claude, then send you the three fixes worth making first, in writing, within 48 hours.
Key takeaways
- The forecast tool needs Sales Hub or Service Hub Professional or Enterprise, an assigned seat and team goals.
- Coverage lives in the forecast tool, so put it in the weekly review deliberately.
- Back-test last quarter before trusting this one.
- Fix stage definitions, close dates and stale deals before adjusting the number.
Frequently asked questions
How accurate is HubSpot forecasting? HubSpot forecasting is as accurate as the deal stages, amounts and close dates behind it. The calculation is sound. To measure your own accuracy, compare last quarter’s week-one forecast submissions with what actually closed, then break the gap down by rep and pipeline.
Which HubSpot plan includes the forecast tool? The forecast tool is included with Sales Hub or Service Hub Professional or Enterprise. Each user also needs an assigned Sales or Service seat and Forecast permissions. Super Admins can access it regardless of seat. Forecastable revenue goals must be assigned to the team.
What are forecast submissions in HubSpot? Forecast submissions are the amounts reps and managers expect to close in a month or quarter, logged in the forecast tool. Each submission has a pipeline, a period, an amount and an optional note. The history view goes back up to a year, which makes it useful for back-testing.
Where does HubSpot show pipeline coverage? In the forecast tool. Once forecastable revenue goals are set, it shows open pipeline coverage, calculated as open pipeline divided by the gap to goal. It isn’t on the dashboards most leaders already look at, so the simplest habit is to open the forecast tool during the weekly pipeline review.
How often should you review the forecast? Review the forecast weekly, ideally on the same day as the pipeline review. Check stage probabilities against actual conversion every quarter. Back-test the previous quarter’s forecast at the start of each new one. A weekly leadership report is the easiest place to make it a habit.


