Outcome. A deal with a discount above the agreed threshold cannot reach Closed Won until a named approver signs off, so oversized discounts stop slipping through at quarter-end.
Workflow map
Enrollment, branches and actions at a glance
deal-hygiene-015
flowchart TD
A[Deal in pre-Closed-Won stage, discount above threshold, not approved] --> B[Notify approver]
B --> C[Create approval task]
C --> D[Delay 2 business days]
D --> E{Still not approved?}
E -->|yes| F[Escalation notification]
E -->|no| G[Exit, deal can advance to Closed Won]
When to use it, when not to
- UseUse it when finance or sales leadership has flagged uncontrolled discounting as a margin problem, not just a reporting annoyance.
- UseUse it together with the native required-property-per-stage setting, that is the only part of this build that actually blocks the stage change, the workflow itself only manages the approval routing and reminders.
- SkipDo not use it if your portal is on Sales Hub Professional without Enterprise features, native record approvals and hierarchy-based routing are Enterprise-tier. Deal pipeline approvals require Sales Hub Enterprise, and quote approvals sit in Revenue Hub Professional and Enterprise (https://knowledge.hubspot.com/account-management/overview-of-approvals-in-hubspot).
- SkipDo not use it if there is no agreed discount threshold yet, build the policy with finance first, the workflow enforces a number, it does not decide what that number should be.
The preview ends here. Six sections are in the library.
counted, not blurred
PrerequisitesEvery property with its label, internal name, type and options, plus the assets the workflow needs before you start.6 items
EnrollmentThe trigger, the criteria exactly as they are ticked in the UI, the re-enrollment rule and the suppression list.4 parts
StepsEach action in order with its parameters, its branches and its delays, written as you tick them.6 numbered actions
Known pitfallsTraps seen in production, each with what breaks and what to do instead.5 pitfalls
Test plan, variants and build specHow to prove it works in a test portal, where to look when it does not, the variants for other objects or tiers, and the YAML build spec.3 variants, 3 sections
FilesThe properties JSON creates the fields in one API call, the workflow JSON documents the build.PDF, Markdown, JSON
Install1 click. The installer creates the properties this spec declares and the workflow itself, switched off, then opens a task for the prerequisites that are assets rather than properties, such as a team, a static list or a marketing email. What it created is listed on the install page.1 click, switched off
Unlock the full library,
149 EUR
or the deal hygiene pack, 39 EUR
One-time, excl. VAT. 30-day refund, no questions asked. Founding prices until 31 October, then 199 and 59 EUR. Includes every spec added later, up to the full 500, and the one-click installer on the full library. Building on client portals? The agency licence at 449 EUR covers unlimited client portals.
