The Discount Approval That Stalls Deals
Ridgeline Equipment sells industrial equipment with deal sizes from $40k to $400k. Its 22 reps send quotes from HubSpot. Any discount above 15% requires VP approval. Today reps encode discount in the line-item unit price, then email the VP and wait. Deals move to Contract Sent before approval, so 28% sit in that stage for more than four days. There is no field recording the approved discount or approver, and finance cannot reconcile quoted versus approved prices. Two reps split one deal into three smaller deals to stay under the 15% threshold. The VP wants approvals to happen inside HubSpot, with an audit trail, but does not want to slow down small deals. Sales Hub Professional is in use; the team has not adopted quotes consistently, and 19% of open deals have no line items. The CFO wants discount reporting by rep and segment next quarter.
1. Diagnose the approval bottleneck. Which parts are tool configuration, which are policy design, and which are behavioral workarounds?
Read the worked answer
The bottleneck is mostly policy and data design, not just tooling. Reps encode discount in unit price, so there is no clean discount field to trigger on and finance cannot reconcile. Moving to Contract Sent before approval is a stage-definition error: the stage means commitment, but it is being used as a waiting room. Email approvals create no audit trail. Deal splitting is a behavioral workaround caused by a hard threshold with no visibility. Tool configuration can enforce required fields and create approval tasks, but policy must define what counts as discount, who can approve, and what happens when a deal is split. I would separate: configuration - discount field, approval status, stage gates; policy - thresholds, approver matrix, split-deal rules; behavior - manager review and consequences. Fix the data model before automating approvals.
2. Design an approval process in HubSpot that preserves speed for small deals and creates an audit trail. Specify thresholds, stage rules, data captured, and how to handle split deals.
Read the worked answer
Create a deal-level discount field calculated from list price versus quoted price, and an approval status property with values Not Required, Pending, Approved, Rejected. Keep the 15% threshold but add a fast lane: discounts up to 15% require manager notification only; above 15% requires VP approval; above 30% requires VP plus finance. Require approval status = Approved before a deal can enter Contract Sent. Capture approver, approval date, approved discount, and rationale. If native quote approvals are available in the subscription, use them; otherwise use a deal-based workflow to create a VP task and block stage progression until the property is set. For split deals, require a parent-child or program ID and flag multiple open deals at the same company within 30 days. This preserves speed for small deals while creating an audit trail.
3. What reporting and governance would you put in place to satisfy finance and prevent deal splitting?
Read the worked answer
Report discount by rep, segment, and approval status, and compare quoted discount to approved discount. Add a split-deal exception report: more than one open deal at the same company domain, created within 30 days, with combined discount above threshold. Review it monthly with sales managers, not just finance. Require line items on all deals above a dollar threshold and use a stage gate for Contract Sent. Track cycle time in Pending Approval and the percentage of deals that skip approval. Governance should include a documented approval matrix, a quarterly threshold review, and an audit sample of approved deals. Finance gets reconciliation; sales gets faster small-deal approvals; the VP gets visibility into exceptions. Without the split-deal report, the policy is easy to game.