Skip to content

borghei/Claude-Skills / business-growth/commercial-policy

commercial-policy

Verified

Commercial policy: the governance framework defining what terms sales can offer and what triggers approval. Use when authoring a policy charter, defining discount/payment/liability rules, auditing deals, or generating a regional policy.

references/discount-and-terms-policy.md

View on GitHub
# Discount and Terms Policy

Deep reference on discount-percentage policy, MFN clauses, performance-based rebates, multi-year discount mechanics, payment-term flexibility (with revenue-recognition implications), and renewal pricing policy.

---

## Discount-percentage policy

### Standard approach: discount thresholds by ACV

| ACV bracket | Max standard discount | Beyond standard requires |
|-------------|----------------------|--------------------------|
| < $25k | 10% | Sales Manager |
| $25k - $100k | 15% | Director |
| $100k - $500k | 20% | VP Sales |
| $500k - $2M | 25% | CRO |
| > $2M | 30% | CRO + CFO |

The "max standard" is rep authority — anything more requires approval per matrix.

### Reasoning for the brackets

- Smaller deals: tight margins (more of revenue eaten by CAC); less discount tolerance
- Larger deals: more strategic value; more justifiable to discount; more approvers needed
- Enterprise deals: strategic significance often justifies bigger discounts but with proportional commitment from customer

### Alternative: industry-vertical discount policy

For sales models heavily segmented by vertical:

| Vertical | Max standard discount | Note |
|----------|----------------------|------|
| Government / public sector | 25% (often via GSA schedule) | Predictable; published |
| Education | 25-40% | Mission-aligned; common practice |
| Non-profit | 15-25% | Verified non-profit status |
| Startup (revenue < $5M) | 30% | Sometimes; with revenue audit |
| Enterprise (Fortune 500) | 15-25% | Larger contracts justify standard discount |

### What "standard" means in practice

"Standard discount" doesn't mean every deal gets a discount. It means:
- Deals offered at list usually win at list (especially when value is compelling)
- Discounts are the exception, not the rule
- When discount is offered, "standard" amount is calibrated to ACV and segment

If 50%+ of deals are discounted, your list pricing is wrong — fix pricing strategy.

---

## MFN (Most Favored Nation) policy

### What MFN means

Customer is guaranteed to get the best price you offer to any other customer with comparable scope. If you give competitor's customer a lower price, customer with MFN demands match.

### Why MFN is dangerous

- Constrains future pricing flexibility (can't price-discriminate based on willingness-to-pay)
- Discount in one deal cascades through all MFN customers
- Customer with MFN can audit your pricing → confidentiality / competitive exposure
- "MFN forever" creates open-ended liability

### Standard MFN policy

**Default**: not granted.

**If granted, mandatory scope**:
- Same product (not "all products")
- Same volume tier
- Same contract term length
- Same geography
- Same customer segment (enterprise vs SMB)
- **Disclosure-only** (you tell customer of equivalent offer; customer can choose to match)
- **Excludes**: pilot pricing, beta program pricing, acquisition pricing, government pricing

**Approval**: CRO + CFO + GC jointly. Document strategic rationale.

**Time-bound when possible**: MFN expires at next renewal unless re-negotiated. Customer pushes for perpetual; resist.

### Alternatives to MFN

- **Volume discount commitment**: instead of MFN, commit to specific discount at volume tier (predictable; finite)
- **Reference customer status**: customer gets early access to new features in exchange for case study
- **Locked-in pricing**: customer's price stays at current for N years, regardless of list-price changes
- **Tier guarantee**: customer placed in top tier; tier benefits don't deteriorate

These are usually acceptable to customers while protecting your pricing flexibility.

---

## Performance-based rebates

Rebates are deferred discounts earned by achieving specific behaviors / volumes.

### Common rebate structures

#### Volume rebate

Partner / customer achieves $X in annual revenue → earns Y% rebate retroactively.

```
$100k revenue: 0% rebate
$250k revenue: 2% rebate on amount > $100k
$500k revenue: 4% rebate on amount > $250k
$1M revenue: 6% rebate on amount > $500k
```

Encourages volume growth; protects margin on lower commitment.

#### Renewal rebate

Customer renews → earns rebate at renewal.

```
- Renewal year 1: 2% rebate (auto-renew + on-time payment)
- Renewal year 2: 4% rebate
- Renewal year 3+: 5% rebate
```

Encourages multi-year retention; cheap incentive vs winning new customer.

#### Reference / case study earn-back

Customer completes case study / reference call → rebate applied to next invoice.

```
Case study published: $X credit (or % of ACV)
Reference call: $X per call
Speaking commitment: $X per speaking engagement
```

Trades referenceable value for discount. Customer feels earned (more durable than discount given upfront).

#### Behavior rebate

Customer achieves usage / adoption metric → rebate.

```
50% feature adoption by users: 1% rebate
80% adoption: 2% rebate
```

Ties customer success to your incentive; encourages stickiness.

### Rebate operational requirements

- Tracked centrally (rebate liability is real)
- Paid quarterly or annually
- Audited (don't take customer's word; verify against your data)
- Documented in contract
- Recognized appropriately for accounting (typically reduces revenue)

### Rebate anti-patterns

- **Rebate stacking**: customer earns multiple rebates that compound
- **Rebate-as-discount-disguise**: nobody believes the rebate is "performance-based"; just builds in a discount
- **Untracked rebates**: customer claims rebate; you can't verify
- **Excessive rebates**: more than 5-7% of revenue going to rebates dilutes margin meaningfully

---

## Multi-year discount mechanics

### Standard pattern

Customer commits to multi-year; gets discount.

```
1-year contract: list price
2-year contract: 5% off (locked for 2 years)
3-year contract: 10% off (locked for 3 years)
5-year contract: 15% off
```

### Trade-offs

| Pattern | Pros | Cons |
|---------|------|------|
| Discount on year-1 ACV, escalates with usage | Customer-side cash flow okay; revenue recognition simple | Smaller discount overall; less locked-in |
| Discount on total contract value | Customer cash-flow advantage; bigger commitment from customer | Revenue recognition complex; larger upfront discount |
| Annual escalator (5% per year) | Inflation protection; expected pricing growth | Customer pushback if usage doesn't grow proportionally |
| Locked pricing (no escalator) | Customer-friendly; predictable | You lose pricing power; bad if market shifts |

### Multi-year termination rights

Customer wants exit if business changes.

- **Termination for convenience with penalty**: pay remaining contract or partial (e.g., 50%)
- **Termination for cause**: standard 30-day cure
- **No termination**: customer locked; risk for both sides
- **Customer-favorable termination** (no-fault, 30-day notice): expensive for vendor; resist or charge

### Multi-year deal anti-patterns

- **Locked-in pricing that customer outgrows**: customer's usage triples; they're paying 30% under market; renewal is painful
- **Year-1 discount that resets at renewal**: customer surprised; churn risk
- **No mechanism to handle customer growth**: should expansion price at locked rate or market rate?
- **Multi-year with no payment-up-front**: cash flow benefit of multi-year disappears

---

## Payment terms

### Standard

- Net 30
- Annual prepay
- ACH preferred (lower fees than wire / check)

### Customer requests

| Customer ask | Standard response |
|--------------|-------------------|
| Net 45-60 | Acceptable with manager approval |
| Net 90 | CFO approval; may price in (small premium or larger upfront fee) |
| Quarterly billing (vs annual prepay) | Acceptable; CFO approval; revenue recognition implications |
| Monthly billing | Discouraged; small customers only; impacts cash flow + ops |
| Pay on acceptance / milestone | CFO + GC approval; revenue recognition deferred |
| Custom invoice schedule | Case-by-case; ops impact |

### Revenue recognition implications

For multi-year deals, payment terms affect ASC 606 / IFRS 15 treatment.

- **Annual prepay, multi-year contract**: revenue ratable over contract; cash up-front
- **Quarterly billing**: revenue ratable; cash quarterly
- **Pay on acceptance**: revenue deferred until acceptance; cash on acceptance
- **Milestone-based payment for services**: revenue recognized as milestones met; not standard for SaaS

CFO involvement essential for non-standard payment terms — incorrect rev-rec can require restatement, audit findings, and material misstatement issues.

---

## Renewal pricing policy

### Standard renewal pricing

- Same product, same volume → same price (no automatic increase)
- Customer-requested expansion → at current published pricing for the new units
- Customer-requested contraction → re-priced (lose volume discount)

### Pricing escalators

| Escalator | When |
|-----------|------|
| None (price-locked) | Standard for multi-year contracts |
| Annual cost-of-living (CPI) | Common in enterprise; 2-4% per year |
| 5% per year | More aggressive; common in older SaaS pricing |
| Tied to consumption (price per seat scales with users) | Common for usage-based models |

### Renewal price hold

Vendor decides to not increase price → price held flat → customer pleased.

**Risk:** If you hold price for some customers and increase for others, MFN-like dynamics emerge.

**Best practice:** Hold price publicly (announce "X% increase in YYYY") or for all renewals of a vintage.

### Renewal contraction

Customer wants to reduce contract size at renewal.

- < 10% contraction: usually allow at same per-unit price
- 10-25% contraction: deal-desk review; may require revisiting volume discount
- > 25% contraction: deal-desk + CS review; investigate churn risk

### Renewal expansion

Customer wants to expand at renewal.

- < 20% expansion: usually allow at same per-unit price
- > 20% expansion: deal-desk review (could trigger tier change, custom terms)
- Land-and-expand pattern: customer started small; renewal is 5x larger; review for strategic-customer designation

### Renewal customer commitments

Renewals are an opportunity to re-affirm or upgrade customer commitments:
- Continue reference / case study?
- New strategic partnership?
- Customer advisory board participation?
- Multi-year commitment in exchange for renewal discount?

---

## Cross-cutting principle: trade for everything

Every customer ask should trade for something:

| Customer wants | We get |
|----------------|--------|
| Discount | Longer commitment / case study / reference / multi-year |
| Net 60+ | Pricing premium OR commitment to specific use case |
| MFN | Multi-year + strategic-tier designation + reference |
| Custom SLA | Higher pricing tier |
| Liability cap > 1x | Higher pricing OR specific scope |
| Multi-product bundle | Commit volume / multi-year / single contract |
| Termination flexibility | Higher pricing OR shorter initial term |
| Free implementation | Multi-year commitment |

Trade is the basis of healthy commercial negotiation. Concession without trade is a giveaway.

---

## Cheat sheet

| Question | Answer |
|----------|--------|
| What's the absolute max discount? | 50% standard; 60%+ needs CEO + board awareness |
| When grant MFN? | Almost never; if at all: strategic-tier + CRO+CFO+GC + scoped |
| When use rebates vs discounts? | Rebates when behavior matters (volume, retention); discounts when winning matters |
| Multi-year discount range? | 5-20%; bigger for longer; less if customer also wants other concessions |
| Net 30 vs Net 60? | Net 30 standard; Net 60 acceptable with manager approval |
| Pay on acceptance? | Last resort; defers revenue; complicates rev-rec; sometimes needed |
| Renewal escalator? | 3-5% per year typical; depends on industry norms |
| Customer wants to contract at renewal? | OK if small; deal-desk review if material |
| Trade for everything? | Yes |
rea-analysis-optimizationmorluto/reaOptimize REA providers and shared analysis workflows for agent context, latency, CPU, and memory while preserving correctness and Evidence. Use for analysis bottlenecks and cache or query design; CI/test-suite optimization belongs to rea-ci-tests-audit.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
rea-ci-tests-auditmorluto/reaAudit REA CI and test suites for correctness, fixture drift, false passes, and measured performance; use for suite or workflow investigations and efficiency changes, rather than ordinary feature testing or a single test failure.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first.Stars: 196kUpdated Claude CodeCodexVerifiedInstall