discount-threshold-monitoring

Discount approval routing compares a HubSpot deal's proposed discount against configured YAML thresholds for the relevant segment, then determines the required authority tier—standard, elevated, or executive—without autonomously approving the discount.

Discount frequency monitoring summarizes how often reps or CSMs apply discounts over a trailing window, flagging above-threshold behavior to identify out-of-policy discount patterns across multiple deals.

Yes, Linear issues are created for elevated and executive discount approvals to capture and manage the required approval workflow, but this write-tier issue creation is gated by user confirmation before executing.

CS expansion deals support optional cs_expansion_discount_ threshold fallback behavior, allowing you to apply specific discount governance thresholds for customer success expansion flows separate from standard deal segments.

Discount threshold monitoring enforces RevOps governance constraints by ensuring no revenue commitments are made and no autonomous approvals are granted, operating with read-only connector usage on HubSpot deal data.

Automated discount approval routing cannot autonomously approve discounts or make revenue commitments; it only flags threshold exceedances and routes the required approval tier, with Linear issue creation gated by explicit user confirmation.