Pricing

Pricing & Discount Governance

Protect margin, keep deals moving, and stop end-of-quarter chaos.

Leadership team reviewing a pricing board showing price floors, discount bands and give-get trades

Introduction

Discounts are not the problem — unmanaged discounts are. In many teams the loudest buyer or the most creative rep dictates price. Floors are unknown, approvals are ad hoc, and every quarter-end becomes a scramble where margin quietly disappears. The board asks why gross margin missed; the team blames “market pressure”.

A good governance system removes drama. You define floors and approval bands in advance, set clear give-get rules, and publish legal guardrails for non-standard terms. Reps know what they can trade and for what. Managers inspect decisions with proof, not opinion. Finance and Legal are involved at the right moments, not as last-minute blockers.

Price should be anchored in value and segmentation. The same product sold to different segments under different conditions should not carry the same realized price. Governance turns this from a hidden tribal rule into visible price fences: region, segment, volume, term, and channel. With fences in place, you can allow flexibility without losing control.

Approvals must be fast or they become a tax on revenue. That means a simple matrix, documented SLAs, and a small pricing council to handle true exceptions. If a deal meets the criteria, approval is a formality. If it doesn’t, the rep knows what they need to trade to earn it — longer term, prepay, a reference, expanded scope.

Legal risk is part of pricing. Concessions like MFN, unlimited liability or broad termination rights are price in disguise. The governance system prices those risks with predefined fallbacks and requires a higher approval tier. When Legal and Sales read from the same playbook, cycle time drops and “legal surprise” slips go away.

Measurement closes the loop: realized discount, price variance, approval cycle time, and attachment rate of give-gets. You want fewer big, late exceptions and more disciplined trades that preserve value. Over a few cycles you’ll see margin stabilize, deal velocity improve, and quarter-end become boring — in a good way.

This article gives you a complete, light-weight system you can implement in your current CRM and contract process in two weeks: definitions, approval matrix, give-get menu, legal guardrails, inspection scripts, cadence, and dashboards — plus detailed worked examples across SMB, mid-market, enterprise and channel motions.

At a glance

What good looks like

Area Good looks like Proof / Artifact System fields
Floors & fences List, Floor, Walk-away by segment, region, tier, term. Price card; fence table published. price_floor, walkaway_pct, segment, term_months
Approval bands Simple matrix with SLAs; auto-approval under thresholds. Matrix doc; audit log of approvals. discount_pct, approval_level, approval_dt
Give-get Mandatory trade for any discount beyond manager band. Deal summary lists Get(s) and owners. trade_term, prepay, ref_case
Legal guardrails Pre-approved fallbacks; redline checklist. Clause library; SoW templates. risk_flag, mfn, liability_cap
Inspection Evidence-based review; pricing math visible. Deal review sheet; pricing waterfall. price_waterfall_ok, give_get_ok

Approval matrix (example)

Discount vs List Who approves Give-get required Notes
0–5% AE No Within fence; auto in CRM
6–10% Manager Yes Any one: 24-month term, prepay, or 2× reference
11–15% Director Yes Two trades, one must be term ≥24m or scope↑
16–20% VP Sales + Finance Yes Risk review; price waterfall attached
>20% or below Floor Pricing Council (CRO, Finance, Legal) Yes Exception memo; council only Wed/Fri
Risky terms (MFN, unlimited liability, broad termination) Legal + Council Yes Priced as additional discount for approval level

Tune thresholds by segment and product. The point is simplicity and speed, not bureaucracy.

Give-get menu (trade rules)

Give (concession) Get (value you receive) Proof
Extra discount 24–36 month term and prepay Order form term; prepay clause
Extended pilot Paid pilot or signed rollout plan with date SoW; mutual plan
Non-standard terms Case study + 2 live references + upsell commit Addendum; ref schedule
Partner margin increase Volume commitment or multi-year resale Partner addendum
Feature roadmap ask Co-funding or tier upgrade now Order form

Playbook: implement governance

1) Set floors and fences

Publish List, Floor and Walk-away per segment, tier and region. Add fences for volume, term and channel. Make the card visible to all managers and in the quote tool.

2) Ship the approval matrix

Keep it to five bands. Add SLAs (e.g., Manager 4 business hours, Director 1 day, Council Wed/Fri only). Auto-route approvals from CRM and log outcomes.

3) Enforce give-get

No discount beyond the manager band without a trade. Use the menu and record the Get as a field in CRM and a line in the order form.

4) Guardrails for risky clauses

Publish a redline checklist with pre-approved fallbacks (liability, termination, MFN, data). Flag risky clauses as additional “price” requiring a higher approval band.

5) Inspection script (weekly)

6) Cadence & council

Run a 30-min weekly pricing council: review exceptions, trends by segment, and stuck approvals. Publish decisions and update the card monthly.

Cadence (overview)

Keep it predictable. Same days, same script, same artifacts.

When Audience Focus Artifacts
Weekly Pricing council (Sales, Finance, Legal) Exceptions, approval SLAs, leakage trends Exception log, price waterfall dashboard
Bi-weekly Managers Deal inspection; give-get compliance Deal review sheet, approval audit
Monthly Exec Floor updates, segment strategy, risks Price card vNext, legal heatmap
Situational diagram: team in a pricing council reviewing approval matrix and give-get trades on a whiteboard

Simple rules, fast approvals, and visible trades keep prices healthy without slowing deals.

Worked examples (detailed)

1) Mid-market SaaS — 12% discount ask

Situation: Prospect wants 12% off list for a 12-month term. Procurement references a cheaper tool.

2) Enterprise — MFN + 25% demand

Situation: Procurement asks for 25% and Most-Favored-Nation clause.

3) Channel deal — partner margin vs end-customer price

Situation: Partner requests extra margin to win a competitive bake-off.

4) Quarter-end panic — 30% request

Situation: Rep asks for 30% on the last day of the quarter to “save the number”.

5) Services-heavy implementation

Situation: Customer negotiates hard on software and wants services free.

6) Competitive RFP — low-price rival

Situation: Rival bids 20% lower headline price.

Metrics to watch

Common mistakes

90-day rollout

One-page checklist

Tip: show each rep their realized discount vs team median and % of deals at/above floor.