1. What logic does HubSpot use to calculate the weighted amount?
2. The deal success rate and amount can be changed by the salesperson.
For example, if a deal with a 90% success rate in August is lost in October, the deal will not be included in the expected sales in the October report.
But what happens if the expected sales range is set to August?
Will the deal be included in the expected sales depending on the August time frame? Or will the deal not be included in the expected sales even if it is a past expected sales depending on the October time frame?
the weighted amount logic is the following: “the Amount multiplied by the Deal probability. This can be used as the default deal amount in the forecast tool, or in a custom single object report. It is recommended to use this property instead of Forecast amount when reviewing expected revenue on an individual deal record.”
Regarding your second question, this depends on the exact report filters. If those are based on the close date of the deal and the deal close date is outside of that range, then it will not be included.
I have an additional question regarding the second question.
1. Deal A created in August had a high success rate because the amount was
$100 and it was in the deal stage 4.
2. Deal A’s amount was reduced to $20 in November. The deal stage is still
in the 4th section.
If I check the expected sales for the past in November,
Will the expected sales for August be calculated as $100? Or will it be
calculated as the current November’s $20?
Is there a way to check the report with the past data regardless of the
current updated content?
@CChoi8 wrote:
If I check the expected sales for the past in November,
Will the expected sales for August be calculated as $100? Or will it be
calculated as the current November’s $20?
I can’t say because I’m not sure where exactly you are checking your expected sales. Can you please more context / details about where exactly? But generally, since the weighted amount is a reflection of the amount, and the probability is 100%, it will reflect whatever the latest edit to the amount field is.
@CChoi8 wrote:
Is there a way to check the report with the past data regardless of the
current updated content?
If you’re on a Sales Hub Professional or Enterprise subscription, you can see this information for non-closed deals via the ‘Historical snapshots’ report: Create sales reports in the sales analytics suite
The same goes for the ‘Deal change history’ report, open deals only. For closed deals or other HubSpot subscriptions, this is not possible.
Hi @CChoi8 , Weighted amount = Deal amount × Deal probability. By default the Deal probability comes from the win % set on the deal stage in your pipeline settings — so a “Proposal” stage set to 60% weights every proposal deal at 60% of its amount.
The catch: those stage percentages are usually untouched defaults. For a number you can trust, replace them with your actual historical win rate per stage — pull 2–4 quarters of closed deals and calculate (won from that stage ÷ reached that stage). It’s almost always lower than the default, and that gap is the most useful number in your pipeline. Happy to share how I calculate the per-stage win rates.
Hi @CChoi8, Weighted amount = deal Amount x Deal probability, and that probability comes from the deal stage (editable per stage in your pipeline settings, or overridable per deal). Reports pull it live from whatever the deal’s current probability and close date are at report run time, it’s not locked to a snapshot in time.
So for your scenario: if a deal is lost in October, its probability drops to 0% regardless of what stage/probability it had in August, and it will not count toward August’s expected sales retroactively. Reports filter by the deal’s close date field, so it’s whichever month the close date is currently set to that determines inclusion, not the month the deal was originally forecasted in. If you need historical accuracy (what was expected as of August, frozen in time), you’d need to track that separately since standard reports always reflect current state, not historical snapshots.