Why this quietly breaks your forecast
A deal with no amount doesn't show up as zero in your forecast — it shows up as nothing. Most weighted-pipeline calculations multiply Amount × Stage Probability. When Amount is null, the row drops out of the sum entirely.
The result: your weighted-pipeline number is systematically low. You're working real deals that aren't represented in any forecast, on any dashboard, in any executive summary. The bigger the deal that's missing its amount, the more your team is flying blind.
Worst case is a high-stage deal — Negotiation, Contract Sent — with no amount. Statistically these are about to close. They're driving urgency and pulling rep time. And they don't exist in the report your VP is looking at.
What three filter conditions actually catch
Three filter conditions in combination:
- Deal stage is not Closed Won / Closed Lost.
- Amount is unknown OR equal to
0. - Created date more than 1 day ago — to exclude deals freshly created and being filled in.
Some teams use 0 instead of null when they don't know. Both render the same way in your sum, so check for both.
Why required-fields don't actually fix the underlying problem
Stage-required-property rules only enforce on manual edits. They don't fire when:
- A workflow advances the deal stage automatically.
- An integration updates the stage via API.
- A bulk import sets stage on existing deals.
Most teams using HubSpot have at least one of those automation surfaces, which means required fields are an honor system, not a guarantee.
The other friction: amount itself isn't always knowable at the moment a deal moves to a stage. Reps will sometimes enter a placeholder like $1 or $10,000 to satisfy the validation, then forget to update later. That looks like an "amount is set" deal in your filter, but the number is fictional. Catching that requires a separate audit — deals where amount is suspiciously round, or where amount hasn't changed since deal creation despite multiple stage advances. Those are rules a person would never run by hand.
The manual HubSpot recipe
Three filters and you're done with the basic view. Catching placeholder amounts is a separate audit that native filters can't express.
- Open Sales → Deals → Create viewNavigate to Sales → Deals. Click 'Create view' in the top right.
- Add filter: Deal stage is not closed won/lostFilter by Deal properties →
Deal stage→ 'is not any of' → 'Closed Won', 'Closed Lost'. Open deals only. - Add filter: Amount is unknown or equal to 0AND group →
Amount→ 'is unknown' OR 'is equal to' → 0. Catches both nulls and placeholder zeros. - Add filter: Create date is more than 1 day agoAND group →
Create date→ 'is more than' → 1 day ago. Excludes deals freshly created and being filled in. - Sort by Deal stage, descendingLate-stage no-amount deals at the top — those are the ones where missing amount distorts the forecast most.
- Save as 'Open deals — no amount'Pin to your sales-ops dashboard. Review weekly with each rep on their late-stage rows.
What Bloated does instead
No-amount AND placeholder-amount deals — separated by suspicious-value patterns.
Bloated flags both null Amount and suspiciously round placeholder Amount ($1, $10K, $100K) — the values reps use to satisfy required-field validation without actually knowing the deal value. Pair with a stage-progression check so a deal at Negotiation with the same $1 placeholder it had at Lead gets escalated to manager review.
amount · HubSpot deal property