What is the operator playbook for a CRO inheriting a Salesforce-based discount approval workflow that everyone bypasses via exception emails?
Quick take: Don't tighten the workflow. First spend two weeks proving — with data — that the bypass is happening, what it's costing in margin, and which managers are signing off via Slack. Then redesign the policy in three layers: a clear authority matrix, a fast-path SLA the workflow CAN meet, and a no-exception rule that the CFO signs personally. Most "everyone bypasses approval" problems are policy-design failures, not enforcement failures.
The Detail
When a new CRO inherits this mess, the temptation is to send a Monday-morning all-hands email saying "all discounts must go through CPQ approval, no exceptions." That email will be ignored within 4 weeks. Reps bypass workflows for two real reasons: the workflow is slower than the buyer's patience, and the policy itself is unclear about who has actual authority. Both are fixable.
Week 1-2: Diagnose
Pull the data. You need three views:
- Discount distribution by deal size. What % of deals close at >15% discount? >25%? >40%? Use a Tableau or Salesforce Reports cohort by quarter. Compare to your stated policy.
- Approval log vs actual discounts given. Match the CPQ-approved discount per quote to the final invoiced ASP. The delta is your bypass surface.
- Exception email volume. Search the corporate Gmail or O365 for "approve this discount" + "needs approval" in the past 90 days. Quantify.
In one engagement I saw, the inherited policy said "max 25% AE discount, manager approves 25-35%, CRO approves >35%." Actual data: 41% of deals closed at >35% discount, 88% of those had no CPQ approval recorded. The bypass was via Slack DMs to the VP of Sales who would forward to ops with "approved." None of it was tracked in Salesforce.
Week 3: Redesign the Policy
Three principles:
1. Authority matrix tied to ACV bands, not just discount %. A 30% discount on a $500K deal is different from a 30% discount on a $25K deal. Pavilion's 2025 GTM Comp Report shows the operator-standard pattern is a 2D matrix: discount % on one axis, ACV band on the other.
2. Auto-approve fast-path for low-risk deals. If a deal is in the bottom band (under $50K ACV, under 15% discount) and the AE has 80%+ quota attainment LTM, auto-approve in CPQ. Most reps bypass approval because it takes 3 days for a 10% discount on a $40K deal. Stop punishing the easy stuff.
3. Hard stop for high-risk deals. Anything above 35% discount OR with non-standard terms (custom MSA, payment terms past Net 60, multi-year prepay request) must route through Deal Desk and get a CFO signature. No CRO override. No email approval.
Week 4: Tooling
- Salesforce CPQ Advanced Approvals — the right product for this. Allows ACV × discount bands, parallel approvals, dynamic approver lookup based on deal attributes, and a Slack-integrated approval channel via the Salesforce + Slack connector.
- DealHub or Tackle.io if you're CPQ-shopping. DealHub handles complex routing more elegantly than native Salesforce CPQ for orgs under 50 AEs.
- Outreach or Salesloft — wire the approval notification into the rep's daily cadence tool so they see "Quote pending DD review" without leaving their workflow.
- Pavilion's Deal Desk Operator community — for benchmarking your SLAs against peers.
The Workflow
The SLA That Kills Bypass Behavior
Reps bypass because the workflow is too slow. The fix:
| Tier | Discount Band | Approver | SLA | Volume Expected |
|---|---|---|---|---|
| Auto | 0-15% on under $50K ACV, AE >80% attainment | None (CPQ rule) | Instant | 55-70% of deals |
| Manager | 15-25% on under $250K, OR 0-15% on $250K-$1M | Direct manager | 24 business hours | 20-30% |
| Deal Desk | 25-35% any band, OR custom terms | DD lead + RevOps | 48 business hours | 5-10% |
| CFO/CRO | >35% OR margin under 60% | DD + CFO + CRO | 5 business days | < 3% |
Enforcement Without Becoming the Bad Guy
The political move: bring the CFO in early. The CFO co-signs the policy memo in week 4. Then when a manager tries to email-approve a 40% discount, the response isn't "the CRO said no" — it's "the CFO and CRO agreed on this policy in March." Politically harder to fight.
Second move: publish a monthly margin scorecard at the leadership offsite. Show discount % by manager by quarter. Public visibility ends most bypass behavior faster than any threat email. Gartner's pricing research consistently shows that transparency on discount performance is the single highest-impact governance lever.
Third move: tie a 5-10% manager commission accelerator to staying within discount policy, not just hitting number. Reps optimize for what's measured AND incented.
What NOT to Do
Don't add more approval layers — that increases bypass. Don't make the CRO the bottleneck. Don't roll out the new policy mid-quarter. Don't grandfather existing deals (creates a precedent that next quarter's "in-flight" deals will bypass again).
Sources
- Salesforce CPQ Product Overview: https://www.salesforce.com/products/cpq/overview/
- Gartner Sales Research — Pricing and Discount Governance: https://www.gartner.com/en/sales/research
- Pavilion 2025 GTM Compensation Report: https://www.joinpavilion.com/compensation-report
- OpenView SaaS Benchmarks: https://openviewpartners.com/blog/saas-benchmarks/
- SalesforceBen — CPQ Advanced Approvals: https://www.salesforceben.com/cpq-approvals/
- Bridge Group Blog: https://www.bridgegroupinc.com/blog
You can't enforce a policy your tooling can't support inside the rep's deal window — fix the SLA first, then enforce the rule.
TAGS: discount-governance, approval-workflow, cpq, cro-playbook, deal-desk