Open-deal value with closedate in current calendar month. Real-time forecast.
At a glance
The forecast that drives the Monday-morning sales standup. Sum ofamountacross every open deal whereclosedatefalls within the current calendar month. Updates in real time as reps push or pull dates and move stages.
| What it counts | SUM(amount) of open deals with closedate >= start_of_current_month AND closedate <= end_of_current_month. Excludes already-closed (closedwon, closedlost) deals. |
| HubSpot Hub scope | Sales Hub. Pulls from /crm/v3/objects/deals filtered on closedate. |
| Forecast variants | This card returns the unweighted sum. Probability-weighted forecast is exposed inside the deal-pipeline drill-down (sum of amount × stage_probability). Unweighted is the figure most B2B founders read for sandbagging buffer. |
| Calendar month boundary | Aligned to the portal account.timezone setting. A US-Pacific portal reading on 1 May 26 at 02:00 PT shows the May figure even though UTC is already 09:00 1 May. |
| Already-closed deals from this month | Excluded. Once a rep marks a deal closedwon or closedlost, it leaves this number. The Pipeline-vs-Realised cross-channel card surfaces actual closed-won totals. |
| Pulled / pushed deals | Reflects current state. If a rep moves closedate from May to June this morning, the May figure drops by that deal’s amount within one sync cycle. |
| Multi-pipeline aggregation | All open pipelines combined (new-business, renewal, expansion). |
| Currency | Home-currency-normalised via amount_in_home_currency. Multi-currency portals see one figure, FX-converted by HubSpot daily. |
| Time window | 30D (current calendar month). Re-baselines on the 1st of each month. |
| Alert trigger | drop >20% vs last month at the same day-of-month. Tracks pacing rather than absolute. A 20% drop on the 14th compared with last month’s 14th flags real slippage. |
| Roles | owner, sales, finance |
Calculation
Calculated automatically from your HubSpot data. See the At a glance summary above for what the metric tracks and the worked example below for a typical reading.Worked example
A B2B services agency with $400k MRR running a single new-business pipeline. Reading this card on 14 Apr 26 (mid-month):| Stage | Open deals (closedate in April) | Sum amount | Stage probability | Weighted |
|---|---|---|---|---|
| Appointment Scheduled | 4 | $32,000 | 20% | $6,400 |
| Qualified to Buy | 6 | $84,000 | 40% | $33,600 |
| Presentation Scheduled | 5 | $96,000 | 60% | $57,600 |
| Decision Maker Bought-In | 3 | $58,000 | 80% | $46,400 |
| Contract Sent | 2 | $44,000 | 90% | $39,600 |
| Total this card (unweighted) | 20 | $314,000 | $183,600 weighted |
| Period | Day-14 figure | Final-month figure |
|---|---|---|
| April (this month) | 183,600 weighted | (forecast) |
| March (last month) | 198,000 weighted | $228,000 closed-won actual |
| February | 172,400 weighted | $204,500 closed-won actual |
- $314k unweighted is 8.2% behind March’s day-14 figure. Below the 20% drop threshold, no alert. The shape is comparable; the team is on pace.
- **Probability-weighted forecast of 228k actual on 204.5k on $172.4k weighted = 119%). For the team this is sandbagging; for the CFO it is conservative book.
- 96k Presentation Scheduled bucket is one deal. Concentration at later stages amplifies single-deal risk. If that one deal slips to May, weighted forecast drops by 58k), and the WoW alert may fire.
- **Contract Sent (39.6k is near-realised. But “Contract Sent” can stick for 30+ days at procurement-heavy enterprises; pair with
Deals Stuck >30dto detect when deals are aging in the final stage. - **The April unweighted is 237k while March hit $342k, that signals real slippage (deals pushed into May or lost), not just timing noise.
Sibling cards merchants should reference together
This is the short-horizon sibling of Total Pipeline. Pair them:| Card | Why pair it with Deals Closing This Month |
|---|---|
| Total Deal Pipeline Value | The full-funnel view. This card is the slice with closedate in current month; that one is everything open. The ratio (this / total) is the “near-term concentration”, a healthy ratio is 15-30% for a 90-day-cycle business. |
| Deals Closing in Next 14 Days | The Monday-standup shortlist. Deals here that have not progressed in 7+ days flag the at-risk deals that may slip out of the month. |
| Average Deal Cycle | The velocity view. A growing month-end forecast with slowing cycle times is artificial, deals are stuck, not progressing. |
| Win Rate by Stage | Provides the historical conversion rate. Apply it to current-month deals at each stage for a calibration check against the unweighted figure. |
| Pipeline Drop Alert | Surfaces the specific deals that caused a sudden contraction in this card. |
| Pipeline-vs-Realised Revenue Gap | The cross-channel reality check. Closed-won from this card should approximate Stripe / Shopify revenue from the same primary-contact emails within 30 days. |
| Stripe MRR | For SaaS, the closed-won amount this month should approximate the Stripe MRR delta. |
| Top 10 Deals by Amount | The concentration check, if 60%+ of this number is in 3 deals, single-deal slippage is your biggest forecast risk. |
Reconciling against the vendor’s own dashboard
Where to look in HubSpot: Two native views give the closest comparison:HubSpot → Reports → Sales analytics → Deal forecast (filter “closedate” to current month, status = open) HubSpot → Sales → Deals → Board view → Forecast tabThe deal-forecast tile per pipeline, summed across pipelines, should match this card to within a few thousand. Why our number may legitimately differ from HubSpot’s:
| Reason | Direction | Why |
|---|---|---|
| Pipeline visibility | Theirs lower | HubSpot’s UI shows pipelines the user has access to. Vortex IQ reads through a portal token and sees all pipelines. |
| Sync lag | Ours lower for the most recent 5-15 minutes | Reps moving deals between stages or pushing closedate update HubSpot in real time; Vortex IQ trails by one sync cycle. |
| Portal timezone vs UTC | Boundary days off | The current-month definition uses portal timezone for boundary calculation. On the 1st of the month at midnight UTC, a US-Pacific portal still sees the prior month’s data for a few hours. |
| Already-closed deals | Ours lower | If a deal closed closedwon this morning with a closedate of 14 Apr 26, HubSpot’s report may include it under “this month closed-won” while this card excludes it (only open). |
| Currency conversion | Either | HubSpot’s Forecast view shows raw amount per pipeline; this card sums home-currency amounts. Multi-currency portals see a divergence equal to FX shifts. |
| Card | Expected relationship | What causes legitimate divergence |
|---|---|---|
| Pipeline-vs-Realised Revenue Gap | After month-end, closedwon $ from this month should approximate Stripe / Shopify revenue from the same customer emails within 30 days | Annual prepays (one Stripe charge but recognised as MRR over 12 months), terms with delayed billing, refunds that hit Stripe but not HubSpot, contract amendments. |
| Stripe MRR | New-business closedwon ÷ 12 (for annual) should approximate the Stripe MRR delta this month | Annual prepays land as one-time Stripe charges; expansions land mid-month at proration. |
| Shopify Total Revenue | For commerce-attached B2B (sales-assisted DTC), closedwon should approximate high-AOV Shopify orders from sales-assisted customer emails | Self-serve checkouts never reach a HubSpot deal; coupon-driven orders may not match closedwon amount exactly. |
Known limitations / merchant FAQs
Why is my deal pipeline number different from my dashboard? Three usual causes: (a) you are looking at one pipeline in the UI; this card sums all open pipelines. (b) HubSpot’s Forecast view may show probability-weighted while this card is unweighted. (c) Permission filtering, your HubSpot user account may not see all pipelines, but Vortex IQ reads through a portal-wide token. Why does this number drop on the 1st of every month? Because the calendar-month window resets. Deals withclosedate in the prior month leave this card and join the closed-won historical series. Combined with reps creating new deals for the current month, the number can drop 60-80% overnight. This is expected, not a bug. The pacing-vs-prior-month alert is the right way to spot real slippage.
How is this different from “Total Pipeline”?
Total Pipeline is everything open. This card is the slice with closedate falling in the current calendar month. A deal with closedate of 23 Sep 26 contributes to Total Pipeline today but not to this card until September.
Is this probability-weighted?
No, this card returns the unweighted sum. The weighted figure is computed alongside but exposed separately in the deal-pipeline drill-down. Most B2B founders prefer the unweighted figure for sandbagging.
Multi-portal aggregation, what does this show?
One card per portal. Vortex IQ does not aggregate forecasts across HubSpot portals because the same currency code may map to different home-currency rates per portal, and pipeline integrity matters more than aggregate convenience.
Today-volatility, why does this swing during the day?
Reps moving deals between stages, pushing close-dates, or marking deals closedwon / closedlost all update this number on the next sync. A 5-15% intra-day movement on an active sales day is normal. Outside business hours the number should be flat.
Why is the alert pacing-based and not absolute?
Because absolute month-over-month variation is high (May day-1 will be much lower than April day-30). Pacing comparison (this month at day-N vs last month at day-N) is the right discipline. Below 20% drop is the threshold; configurable per merchant.
Sequence enrolment vs send timing, does this affect deals?
No. Sequences are 1-to-1 outreach automations in Sales Hub, separate from deals. A sequence that emails 50 contacts does not create 50 deals. Deals are created manually or via deal-creation workflows.
Why is my deal pipeline number different from my CFO’s spreadsheet?
Most CFO spreadsheets use HubSpot’s CSV export at month-start, then manually subtract closed-won as the month progresses. This card is real-time. A 5-15% mid-month divergence between a static CFO view and this card is normal; the gap closes at month-end.