What's the founder's role in setting the actual discount-policy numbers vs delegating to the CRO — and what happens when the CRO and founder disagree on risk tolerance?

Question

Pulse RevOps · The Machine · Accepted Answer

**Quick take:** Founder sets the GUARDRAILS (max discount, margin floor, deal-size thresholds where escalation kicks in). The CRO sets the TACTICAL POLICY inside the guardrails (band structure, approver tiers, SPIFFs, exception handling). When they disagree on risk tolerance, the founder wins on guardrails, the CRO wins on tactics, and the CFO is the tiebreaker on anything that affects gross margin or runway. The board sees the dispute only if it escalates beyond CFO mediation.

## The Detail

I've watched this argument play out at probably a dozen companies. The founder feels pricing leakage in their gut (they signed customers at much higher rates two years ago and now the team is at 25%+ off list). The CRO feels deal velocity in their gut (the policy is killing pipeline conversion). Both are partly right. The fix is to separate the layers of the decision so the argument has structure.

## The Three Layers

**Layer 1: Guardrails (Founder + CFO own).**
- Maximum allowable discount on any single deal (e.g., 50% absolute floor)
- Margin floor (e.g., gross margin under 55% requires CFO + CEO signoff)
- ACV threshold at which escalation is mandatory (e.g., any deal over $250K)
- Multi-year discount limits (e.g., 2x year-1 discount maximum on 3-year deals)
- These move once a year at most; they're effectively the founder's risk tolerance encoded in numbers.

**Layer 2: Tactical Policy (CRO owns within guardrails).**
- Discount band structure by ACV (0-10%, 10-20%, 20-30%, 30%+)
- Approver tiers (rep, manager, deal desk, CRO)
- SLA on approval (24/48/72 hours)
- AE autonomy levels and how they evolve with attainment/tenure
- SPIFFs and accelerators
- Exception process and frequency caps
- These move quarterly; the CRO has full authority inside the guardrails.

**Layer 3: Deal-by-Deal Decisions (Deal Desk + AE Manager own).**
- Individual deal approvals
- Specific exception requests
- The CRO and Founder are NOT in this layer except for the top 1% strategic deals.

## What "Risk Tolerance" Actually Means

When the founder says "I want a tighter policy" and the CRO says "we'll lose deals," they're making different operational claims:

- **Founder's risk:** long-term margin erosion, customer expectations of permanent discounts, brand value drift.
- **CRO's risk:** missed quarter, AE attrition, competitive losses, pipeline conversion collapse.

Both risks are real. They're different time horizons.

## The Disagreement Protocol

When the founder and CRO disagree, the resolution flow is:

```mermaid
flowchart LR
    A[CRO Proposes New Policy] --> B[Founder Reviews Guardrails Impact]
    B --> C{Within Guardrails?}
    C -->|Yes| D[CRO Has Authority]
    C -->|No| E[Negotiation Round 1]
    E --> F{Resolved?}
    F -->|Yes| G[CFO Signs Off]
    F -->|No| H[CFO Mediates with Data]
    H --> I{Resolved?}
    I -->|Yes| G
    I -->|No| J[Board Pricing Committee]
    J --> K[Final Decision]
    G --> L[Policy Live]
    K --> L
```

## The CFO's Role as Tiebreaker

The CFO arbitrates because the disagreement is fundamentally about margin and runway — the CFO's domain. The CFO brings data to the mediation:

- 4-quarter trailing GM by segment
- Discount distribution vs the proposed change
- Cohort NRR by initial-discount band
- Cash impact at projected pipeline conversion

If the data supports the CRO's claim (deal velocity is materially limited by current policy), the CFO sides with looser policy. If the data supports the founder's claim (margin is eroding and discounts aren't producing proportional ACV lift), the CFO sides with tighter policy.

## What Founders Get Wrong

- Trying to set the tactical policy themselves. The founder doesn't watch deals daily and can't calibrate by reading the policy doc.
- Overriding the CRO on a deal-by-deal basis. This undermines the CRO and trains reps to escalate to founder for exceptions.
- Setting guardrails by gut without anchoring to GM and CAC payback math.
- Changing guardrails mid-year. Guardrails should move at fiscal-year boundaries only.

## What CROs Get Wrong

- Trying to push past guardrails because of one quarter's pipeline shortfall.
- Loosening policy without first proving that activity (not pricing) is the bottleneck.
- Building policy that's too complex for the field to absorb.
- Resisting CFO mediation when the data is unambiguous.

## Comparing Common Failure Modes

| Failure Mode | Cause | Fix |
|---|---|---|
| Founder approves deals via Slack outside policy | No clear guardrails written down | Document guardrails; founder commits to not bypassing |
| CRO loosens policy quarterly to hit number | No CFO mediation; founder absent | Quarterly pricing review with CFO present |
| AEs route to founder for exception | Approval SLA too slow | Fix the SLA (see CPQ Q&A on this) |
| Discount policy contradicts comp plan | CRO and founder set them independently | Joint annual review syncing pricing audit + comp planning |
| Policy doesn't survive M&A | Acquirer/acquiree have diffe

What's the founder's role in setting the actual discount-policy numbers vs delegating to the CRO — and what happens when the CRO and founder disagree on risk tolerance?

The Detail

The Three Layers

What "Risk Tolerance" Actually Means

The Disagreement Protocol

The CFO's Role as Tiebreaker

What Founders Get Wrong

What CROs Get Wrong

Comparing Common Failure Modes

Vendors and Tooling

The Annual Guardrails Document

What Bessemer and SaaStr Operators Report

Sources

Failure Mode	Cause	Fix
Founder approves deals via Slack outside policy	No clear guardrails written down	Document guardrails; founder commits to not bypassing
CRO loosens policy quarterly to hit number	No CFO mediation; founder absent	Quarterly pricing review with CFO present
AEs route to founder for exception	Approval SLA too slow	Fix the SLA (see CPQ Q&A on this)
Discount policy contradicts comp plan	CRO and founder set them independently	Joint annual review syncing pricing audit + comp planning
Policy doesn't survive M&A	Acquirer/acquiree have different risk tolerance	Pre-define guardrail revision protocol pre-close

What's the founder's role in setting the actual discount-policy numbers vs delegating to the CRO — and what happens when the CRO and founder disagree on risk tolerance?

The Detail

The Three Layers

What "Risk Tolerance" Actually Means

The Disagreement Protocol

The CFO's Role as Tiebreaker

What Founders Get Wrong

What CROs Get Wrong

Comparing Common Failure Modes

Vendors and Tooling

The Annual Guardrails Document

What Bessemer and SaaStr Operators Report

Sources

What does the score mean?