Why amount drops without context are a forecasting and coaching problem
Deal amounts go up and down for legitimate reasons: scope changes, multi-year-to-annual conversions, customer pushback on pricing, line-item adjustments. None of those are bad — they're normal sales motion.
What is bad is when the amount drops significantly and nothing in the deal history explains why. No note, no email, no logged call discussing the change. That's a sign of one of:
- Undocumented price concession — the rep gave a discount to keep the deal alive but didn't loop in the manager or update the proposal trail. Margins are taking a hit nobody can see.
- Forecast sandbagging — the rep is lowering the amount to under-promise and over-deliver at quarter-end. Manageable but coaching-worthy.
- Data correction the rep didn't flag — the original amount was wrong, the new one is right, but the audit trail makes it look like a concession.
All three are forecast-distorting. The first one is also a margin leak you'd want compensation/finance to know about.
What three signals together actually identify
Three signals together:
- Current Amount is lower than the peak Amount — peak being the highest value the property has ever held.
- Drop is at least 20% of the peak (smaller drops are usually noise).
- No notes, calls, or emails logged within a few days of the amount change. If there's an explanatory artifact, the drop is documented.
The 20% threshold is conservative — real concessions are often steeper. Some teams tighten to 10% for late-stage deals where every dollar is carefully tracked.
Why the engagement-cross-reference is the expensive half
The amount-history portion is doable with custom workflows. The "is there a documented reason?" portion is what makes this rule expensive in native HubSpot:
Notes, emails, and calls are separate object types. No single filter says "this deal has any logged engagement of any type within X days of date Y." You'd build three separate checks and OR them together.
Many teams' engagement logging is inconsistent. Some reps note every concession. Others rely on Slack DMs or verbal updates that never reach HubSpot. The "no notes = problem" rule generates false positives in those cultures, and tightening to "no notes AND no calls AND no emails" generates false negatives in the disciplined ones.
Bulk amount changes via integration. A CPQ tool pushing pricing updates can change Amount without leaving an engagement trail. Whether that's a "silent drop" or just "the system did its job" depends on whether your CPQ logs back to HubSpot when a quote is revised. Most don't, by default.
The rule is most useful when paired with a manual review. The view surfaces 20-50 deals per quarter; sales-ops triages them in 30 minutes; ~70% are real concessions worth discussing, ~30% are noise. Worth running. Not worth blindly automating action on.
The manual HubSpot recipe
A custom property tracks the peak. A calculation property computes the drop ratio. The engagement cross-reference is API work — native filters don't get you there.
- Create the custom propertySettings → Properties → Deals → Create property. Name:
amount_peak. Type: Number. Default value: 0. - Build the peak-tracking workflowWorkflows → Create → Deal-based. Trigger:
Amountchanged. - Branch: new value is greater than amount_peakIf/then branch:
Amount is greater than amount_peak. Action: copyAmounttoamount_peak. The property only ever increases — captures the peak. - Build the drop-detection viewSales → Deals → Create view. Calculation property (Operations Hub Pro+):
current_to_peak_ratio = Amount / amount_peak. Filter:current_to_peak_ratio < 0.8ANDDeal stage is not closed won/lost. - Cross-reference engagements (advanced)The 'no notes' check requires the CRM Engagements API. Query: for each deal in the drop view, fetch notes/calls/emails within ±3 days of the most recent Amount change. Flag deals where the result is empty.
- Triage weeklySales-ops reviews the flagged deals; about 70% are real concessions worth discussing, 30% are noise (CPQ updates, data corrections). Worth running. Not worth blindly automating.
What Bloated does instead
Quiet amount drops, with engagement context cross-referenced automatically.
Bloated tracks Amount property history AND cross-references engagements within a 3-day window of the change in one pass — no custom property setup, no API plumbing. Documented concessions don't fire; undocumented ones do. Pair with the suggested action: confirm concession with manager, log retroactive context, or revert the amount if the change was an accident.
amount (history), notes · HubSpot deal properties