How should discount governance evolve as the company scales from founder-led to a hired VP Sales or CRO — what gets locked in now to make the handoff clean?

Quick take: Lock four things before the CRO arrives: (1) the written guardrails document with margin floor and max discount; (2) the discount distribution baseline (rolling 4-quarter data); (3) the CPQ approval matrix as it exists today; (4) the exception log with rationale for each material override in the past 12 months. The CRO will modify the policy — that's expected — but they should INHERIT a documented system, not a verbal tradition.

The Detail

The clean CRO handoff fails most often because the founder ran discount governance as an undocumented set of judgments. The CRO walks in, asks "what's the policy on multi-year discounts?" and gets four different answers from four different people. They spend their first 90 days reverse-engineering the system instead of running it. Worse: every existing rep has a different mental model of "what the founder allowed," and the CRO can't tighten without picking fights they're not yet positioned for.

What to Lock In BEFORE the CRO Arrives

1. The Guardrails Document (1 page, signed by founder + CFO).

Contents:

• Maximum allowable discount on any single deal
• Margin floor below which CFO+CEO co-sign required
• ACV thresholds triggering escalation
• Multi-year discount limits
• Payment terms variance limits
• Effective date and review cadence
• Signature lines

This is the founder's risk tolerance encoded in numbers. It outlasts the founder being in the day-to-day. The CRO will modify the tactical policy but the guardrails are the constitutional layer.

2. The Baseline Distribution Data.

Pull rolling 4-quarter data on:

• Discount % distribution (P25, P50, P75, P90) by segment
• Average discount by ACV band
• Discount by AE (anonymized; coded by manager)
• Discount trend by month
• Margin trend
• Deals approved vs deals self-served (if you track it)

This is the CRO's starting picture. They can't change what they can't see. Documented data prevents the political fight of "the discount has been creeping up" vs "no it hasn't."

3. The CPQ Approval Matrix (as currently configured).

Export the current CPQ approval rules:

• Trigger conditions (discount %, ACV band, terms variance)
• Approver tiers
• SLA targets
• Override authorities
• Exception process

Document any rules that exist in spirit but not in CPQ (e.g., "everyone knows the founder approves anything > 30% via Slack" — capture that, even though it's bad practice).

4. The Exception Log (last 12 months).

For each material exception (any deal that went outside policy):

• Customer name
• ACV
• Approved discount
• Approver
• Documented rationale
• Outcome (closed-won, lost, renewed at full rate, churned)

This is the most valuable artifact for the CRO. It tells them: who's been bending rules, what the consequences were, and which customers expect the "founder rate" at renewal.

The Transition Sequence

What the CRO Will (and Should) Change

In their first 6 months, expect the CRO to:

• Refine the approval tier definitions (typically tighter mid-bands, more lenient auto-approve floor)
• Update the AE autonomy framework (move to a more formalized attainment-based model)
• Renegotiate the SLA targets (often tightening to 24-hour for Velocity)
• Implement a Deal Desk if one doesn't exist
• Modify the exception process (typically more written, less verbal)

What they should NOT change without founder + CFO alignment:

• The guardrails (margin floor, max discount, ACV thresholds)
• The fundamental pricing structure (list prices, packaging)
• The accounting treatment of discounts

The Handoff Conversation

A 90-minute meeting with the new CRO at week 1, in this order:

1. Guardrails review (30 min): founder walks through the document and the rationale for each band. CRO asks questions. CFO joins for margin discussion.
2. Baseline data review (30 min): RevOps presents distribution data. CRO identifies 2-3 metrics they want to watch.
3. Exception log review (30 min): founder walks through 3-5 material exceptions and what they learned.

This meeting alone saves the CRO 60-90 days of reverse-engineering.

Pre-Handoff Checklist

What NOT to Hand Off

• "Well, the founder always said yes for our top customers." Not a handoff item; that's an oral tradition that needs to be either codified or killed.
• "We don't have approval rules for that case." Document the gap explicitly so the CRO knows what's unsystematic.
• "The CFO has been signing off on those quietly." Surface it; politicized handoffs fail.

Vendors and Tooling

• Salesforce CPQ — primary source of approval matrix data
• Tableau / CRM Analytics — for the baseline distribution dashboards
• Notion or Confluence — for the guardrails doc and policy library
• DocuSign CLM / Ironclad — for the side-letter index
• Pavilion CRO community — for CRO transition peer support

What Pavilion and Bessemer Data Show

Pavilion 2025 CRO transition data: CROs who inherited documented governance (4 artifacts) reached steady-state policy operation by month 4. Those who didn't averaged month 9. The 5-month delta represents roughly 2 quarters of avoidable governance noise and AE confusion.

Bessemer Atlas notes that founder-to-CRO transitions in the early scaling phase ($5M-$15M ARR) are among the highest-impact organizational moments — discount governance done well at the handoff compounds into the next 3 years; done badly, it requires a re-do at $25M ARR with much higher cost.

The 12-Month Founder Check-in

Even after handoff, the founder should review pricing health quarterly with the CRO. Not to override — to ensure the guardrails are still holding. The CFO sits in. Three questions:

1. Are we within the guardrails this quarter?
2. What's changed in the discount distribution?
3. What policy changes are you proposing for next quarter?

That's it. The founder maintains visibility without being in operational flow.

Sources

• Pavilion 2025 GTM Comp Report: https://www.joinpavilion.com/compensation-report
• SaaStr — Founder + CRO Transition: https://www.saastr.com/
• First Round Review — CRO Handoff Playbooks: https://www.firstround.com/review/
• Bessemer Atlas Memos: https://www.bessemerventurepartners.com/atlas
• Gartner Sales Research: https://www.gartner.com/en/sales/research
• OpenView SaaS Benchmarks: https://openviewpartners.com/blog/saas-benchmarks/

A CRO handoff without documented governance is a CRO setup for 12 months of avoidable politics — lock the four artifacts and your incoming hire spends their time operating, not archaeologizing.

TAGS: discount-governance, cro-handoff, founder-transition, policy-evolution, scaling