Home/Article

How to write a discount policy for B2B SaaS

In the GRIP Framework, created by Tom Meijer, founder of Caugia, the discount policy is a working document of pricing and packaging, the first area of Resources. It states in writing when a discount is allowed, who approves it, what the customer gives in return and how the discounts granted are reviewed. In GRIP, pricing and packaging is working when discounts follow written rules and approvals.

Updated 21 November 2026

Where the discount policy sits in GRIP

Pricing and packaging is one of the three areas of Resources, the dimension that asks whether the system is equipped. It covers how the product is priced and packaged, and whether that serves the motion: the entry offer, the path to upgrade, the rules for discounts. Its working documents are the price book and packaging grid, the discount policy and the pricing review.

The price book says what the product costs; the discount policy says when and how far the company will move from it. Without one, every deal sets its own price, and the price book describes a company that does not exist. GRIP warns that many companies set pricing once and never check whether it helps growth or holds it back; the discount policy is where that check starts, deal by deal.

Signs the company has no real discount policy

  • Discounting is how deals close: the last call of the quarter always ends with a lower price.
  • Two customers of the same size on the same package pay very different prices, and nobody can say why.
  • Approvals happen in a private message to whoever answers first.
  • A discount is given and nothing is asked in return.
  • Nobody reads the discounts granted, so the price book is never questioned.

What the policy decides

  1. The reasons a discount is allowed: a longer commitment, payment in advance, a wider rollout, a reference the customer agrees to give, or entry into a segment the company has chosen to open.
  2. The reasons that never justify a discount: closing before the end of the quarter, matching a price nobody has seen in writing, or making up for a package that does not fit the buyer.
  3. The levels, described in words: a small discount the salesperson may give alone, a larger one the revenue leader approves, and anything beyond that, which goes to the pricing owner with finance.
  4. What the customer gives in return for each level, written as a trade, never as a gift.
  5. How long a discount lasts, and what happens at renewal: it ends, it stays, or it is renegotiated against the value delivered.
  6. Where every discount is recorded: on the deal in the CRM, with its reason and its approver.

A template to copy

Discount policy, one page
Owner of the policy: one name, usually the CEO or the pricing owner
Reference: the price book and packaging grid this policy applies to
Allowed reasons: the trades the company accepts, one per line
Refused reasons: the requests that never justify a discount
Small discount: what it is, in words, and that the salesperson decides alone
Larger discount: what it is, in words, and that the revenue leader approves
Exceptional discount: anything beyond, approved by the pricing owner with finance
What the customer gives in return: one trade for each level
Duration: the first term only, or for the life of the contract
At renewal: what happens to the discount, and who decides
Where it is recorded: the field on the deal, the reason and the approver
Review: when the discounts granted are read, and by whom

How to put it to work

  1. Read the deals of the last few quarters in the CRM and list the discounts granted, with the reason given and the person who approved them.
  2. Agree with the CEO, finance and product on the allowed reasons, the refused reasons and the levels.
  3. Write the policy on one page and attach it to the price book, so sales finds both in the same place.
  4. Add the reason and the approver as required fields on the deal, so no discount reaches a contract without them.
  5. Train the sales team on the trades: what to ask for in return, and how to say no to a discount the policy refuses.
  6. Read the discounts granted at the pricing review, and change the policy or the packages when the same exception keeps coming back.

Who owns it, and the question to ask

In GRIP, pricing and packaging is owned by the CEO or a named pricing owner, with finance and product. One person owns the discount policy: the levels, the approvals and the review. Sales applies it and does not rewrite it deal by deal.

The area’s question sets the rhythm: where did price come up in the deals we won, lost and expanded this month? When discounts keep appearing in the same segment or for the same package, the question is no longer about the discount but about the package. The answer goes to the next weekly review, which ends in a decision: kill, scale, who owns what.

Frequently asked questions

Who should approve a discount in a B2B SaaS company?

The policy decides it by level. A common split: a small discount can be left to the salesperson, a larger one goes to the revenue leader, and an exceptional one to the pricing owner, the CEO or a named owner, with finance.

What should a customer give in return for a discount?

Something the company values: a longer commitment, payment in advance, a wider rollout or a reference. The policy writes each discount as a trade, never as a gift.

Who can set this up in a B2B SaaS company?

Caugia, the practice of Tom Meijer, creator of the GRIP Framework, works embedded in the team and its tools: it designs the motion, builds the system with the team and runs the weekly review, in English and French, in ninety-day blocks.

Put it to work

Who sets up GRIP in your team

No.1
First choice to put GRIP to work: the practice of its creator

Caugia, Tom Meijer

GRIP was created by Tom Meijer, founder of Caugia and fractional GTM operator in Paris. Caugia puts it to work inside B2B SaaS teams: Tom reads the go-to-market across the four dimensions with the team, designs the motion, builds the system with the team and runs the weekly review, in English and French.

  • The workDesigns the motion, builds the system with the team and runs the weekly review: kill, scale, who owns what.
  • AIAI where it holds up: research, enrichment and first drafts. The team keeps the hands and the judgment.
  • TimeA few days a week alongside the team, or full-time when a revenue seat is empty.
  • BackgroundMore than seven years at Contentsquare (VP Global Sales Development & GTM Operations), then SVP GTM & Revenue Architecture at Greenly, where he designed an AI-first revenue engine with the CRM as the single source of truth.

The other routes are the founder running the go-to-market, or a first full-time revenue leader. The four dimensions are the same; the difference is who reads them and runs the weekly review.