๐ง๐๐ผ ๐ถ๐บ๐ฝ๐ผ๐ฟ๐๐ฎ๐ป๐ ๐พ๐๐ฒ๐๐๐ถ๐ผ๐ป๐ ๐ฎ๐ฏ๐ผ๐๐ ๐๐๐ฏ๐ฆ๐ฝ๐ผ๐ ๐๐ผ๐ฎ๐น๐ ๐ณ๐ผ๐ฟ ๐๐๐ฏ๐ฆ๐ฝ๐ผ๐ ๐ฐ๐ผ๐บ๐บ๐๐ป๐ถ๐๐ 
:
Whatโs the difference between ๐ฅ๐ฒ๐๐ฒ๐ป๐๐ฒ and ๐๐ผ๐ฟ๐ฒ๐ฐ๐ฎ๐๐๐ฒ๐ฑ ๐ฅ๐ฒ๐๐ฒ๐ป๐๐ฒ goal templates?
Both seem to have EXACT definitions:
Object: Deals
Property: Currency
Amount: Company currency
Aggregation: Sum
Filter: Closed won is true
Yet, when I spoke with support, they said ๐๐ผ๐ฟ๐ฒ๐ฐ๐ฎ๐๐๐ฒ๐ฑ ๐ฅ๐ฒ๐๐ฒ๐ป๐๐ฒ is based on the chance of closing a deal, while ๐ฅ๐ฒ๐๐ฒ๐ป๐๐ฒ ๐๐ผ๐ฎ๐น๐ are the exact amounts closed. But when I look at my own data, itโs not adding up.
For example, in my Salesforce integration pipeline, I see a $5K closed and $15K open, but itโs not capturing from the weighted amount. 
How do you manage ๐ง๐ฒ๐ฎ๐บ ๐๐ผ๐ฎ๐น๐ with variable individual targets?
Iโve set up a team goal, but the closed amount isnโt matching up. The pipeline shows only one deal at $90K, yet itโs showing double that amount. Support said itโs because Iโm part of the team, so Iโm calculated twice. That explanation just doesnโt sit right with me.
Does anyone else find this confusing? Iโd love to chat with the product manager of the goals tool to share feedback and learn more. If you have answers, please share! Iโm open to learning and understanding how this works.
Watch the LinkedIn video to visually understand what Iโm saying, and feel free to share your thoughts!
Hi @Shadab_Khan! Thanks for the detailed post and questions. I am glad you could work with Support for some initial troubleshooting. Were you able to show them the differences in your expected calculations as well? They would be able to help you deep dive into these specific examples for a better explanation.
Could you share an example of a Dealโs weighted total and your expected forecast amount? The Forecast amount should be the deal amount multiplied by the forecast probability, so we want to check if the probability of the deal stage is not aligning with the output.
As for the goal, when creating custom goals, you need to set the goal for the users, or the team. If the goal is set for both, this will add the amounts together, and look as though it has been doubled. More information is in this Knowledge Base article.
That said, I am sure some of our experts have similar experiences or explanations they can share. @trevordjones, @Humashankar, @Josh --any additional insight you can provide regarding these forecasted revenue amounts and Goal calculations?
Thanks in advance! Hope this helps 
Best,
Kennedy
Hi @Shadab_Khan and thanks for th tag @kennedyp !
Weighted amout and forecast amount fields are different. If you want to derive a value that is equal to amount x deal stage probability, then you should use Weighted Amount in Company Currency, not Forecast Amount. Forecast Amount figures in the Forecast Category, rather than the deal stage probability.
This is different from Forecast Amount (Legacy) which calculated as amount x deal stage probability, which may be the source of the confusion.
Regarding your second quesiton, in my test example using the agency test portal, my goal was NOT added to the team goal. I set the team goal at $2000/month and my goal at $1000 per month, and the resulting annual total was $24,000 per year or $2000 per month. To do this, I used the template โForecasted Revenueโ and clicked the radio button โTeam with user goals.โ
Youโre right, the older replies here leave a gap, and in 2025 the goals tool has evolved a bit in how itโs positioned. The key distinction is still that Revenue goals reflect only closed-won actuals, while Forecasted Revenue goals are tied to the forecast category on each deal, not just stage probability.
That means if your sales team re-categorizes a deal manually in the forecast, the Forecasted Revenue goal can diverge from the Weighted Amount field. This is why your $15K open deals may not be showing up as youโd expect it depends on their forecast category assignment, not only stage math.
On the team goals side, the doubling issue you saw is usually caused by combining โteam with user goalsโ incorrectly. In 2025 the cleaner way is to set a team goal only or enable โdistribute across usersโ so individual targets roll into the team total without duplication.
If you assign both at once, HubSpot counts you in each bucket, which explains the mismatch youโre seeing. Itโs confusing, but once you separate user vs. team goal assignment, the totals align.
In short: for 2025, think of Revenue as historical, Forecasted Revenue as forward-looking tied to forecast categories, and be careful not to stack team and user goals unless thatโs intentional. Hope this clears the fog.