When should a CRO enforce a discount cap across the org vs. delegating authority by segment, and how do you prevent regional/vertical teams from creating their own shadow pricing?

When to Enforce a Hard Discount Cap vs. Delegate by Segment

A CRO should enforce an org-wide hard cap (typically 20–25% max) when the company has fewer than 3 distinct GTM segments or is pre-$50M ARR. Delegate by segment when enterprise, mid-market, and SMB motions have genuinely different competitive dynamics, deal sizes, and margin profiles — but only with CPQ enforcement, not handshake agreements.

---

THE DETAIL

The core mistake CROs make: they treat discounting as a *sales problem* rather than a pricing architecture problem. Heavy discounting across the pipeline is usually a symptom — pricing isn't clearly tied to value, packaging is confusing so reps "solve" confusion with a discount, or competitors are used as the pricing reference point.

When to enforce a hard org-wide cap:

1. Pre-$50M ARR / <3 segments — insufficient data to differentiate by vertical; one rogue region can poison your comp benchmarks
2. Post-audit showing >20% price dispersion — run a price dispersion analysis: calculate how much of the variation in observed prices can be accounted for by your documented pricing and discounting factors. If you can't explain the spread, lock it down
3. Brand is the moat — data shows SaaS discounting lowers LTV by over 30%, and if your ICP is premium-sensitive, caps protect brand integrity

When to delegate authority by segment:

1. Enterprise vs. MM vs. SMB have >2x ACV spread — a 30% discount on a $500K deal is structurally different from 30% on a $12K deal
2. Competitive displacement motions in a specific vertical — give the vertical leader a separate "competitive override" bucket, not a blanket expansion of authority
3. Tie discounting guidelines clearly to deal size, customer segment, and approval levels — segment leaders get authority *within* those rails, not around them

The discount authority matrix (benchmark):

Killing shadow pricing — the operational kill shots:

• If approvals take days, reps will find workarounds or create side deals. Speed = compliance. Get CPQ (Salesforce CPQ, DealHub, Cacheflow) enforcing rules at quote generation, not after
• Break your discounting rules for one customer today, and you'll find that same buyer a year later prospecting another organization — or worse, a different active customer
• 73% of high-performing SaaS companies maintain "structured flexibility" in their pricing governance — clear rules with well-defined paths for exceptions when strategic opportunities arise
• Run monthly price realization reviews in QBRs — publish regional net ARR vs. list ARR so shadow pricing becomes visible, not buried in attainment numbers

The nuclear option to prevent regional drift: establish a cross-functional pricing committee with representatives from product, finance, sales, marketing, and customer success — any regional "exception program" requires committee ratification, not just a VP email chain.

---