A discount discipline framework for B2B SaaS.

Most B2B SaaS companies treat discounting as a habit. Sales gives 15% to close one deal, then 20% to close the next, then 25% because the prospect “saw what the other one got.” Within a year, the price list is a fiction. Within two years, the company has accumulated ten or more different effective prices for the same product, and nobody can explain how each one was set.

I have walked into this situation more than once, and the pattern is consistent. The company is not failing on revenue, so the problem is not visible in the top-line. It shows up in margin and in the inability to forecast next year. The CFO cannot model a price increase because there is no price to increase from. The sales VP defends every discount as “necessary to win the deal” and insists removing them will tank the pipeline. The CEO does not have a counter-narrative because they do not have a framework.

Here is the framework I would use to fix it. It applies to any B2B SaaS or B2B subscription business, and the principles transfer cleanly to BaaS infrastructure, vertical SaaS, and platform plays.

The two prices that matter

A B2B SaaS contract typically has two revenue components: setup (one-time) and MRR (recurring). Both look like discountable revenue to a sales team, but they have very different effects on enterprise value.

A 20% discount on setup is a one-time loss. If your setup is €20k, you lose €4k once. Painful, but recoverable.

A 20% discount on MRR compounds. If your MRR is €11k a month, the same 20% costs €2,200 a month. Over a five-year customer lifetime, the €4k setup discount looks small next to the €132k of recurring revenue you gave away. And the discount does not reset on renewal, because most contracts default to renewing at the prior price. A discounted MRR stays discounted forever unless explicitly renegotiated.

The valuation effect is worse than the cash effect. SaaS companies are valued on ARR multiples. A 20% MRR discount on a €11k a month account at a 5x ARR multiple destroys €132k of enterprise value, far more than the €26k of annual revenue it costs. For a deal that closes faster, a sales team is trading enterprise value for short-term wins at a 5-to-1 ratio.

The first principle of the framework follows from this math. The right place to discount is setup, please leave MRR alone.

The three tiers

Tier 1: target price.

The price you ask for, on every deal, with no discount language attached. This is what your pricing page should show, what your sales team should quote first, and what your contracts should default to.

Target price is set by what the product is worth to the buyer, not by what your costs are. Cost-based pricing is a separate failure mode and one of the more expensive ones, but it is outside the scope of this essay.

Tier 2: with-discount price.

A second price, between 15% and 20% below target, applied only to setup. MRR stays at target.

The 15% to 20% range is not arbitrary. Below 10%, a discount feels insulting and does not move the deal. Above 25%, you are signalling that your target price was inflated and the buyer should suspect the next round of negotiation. The sweet spot is 15% to 20%: real concession, defensible reasoning, does not cheapen the brand.

Tier 3: C-level approval floor.

A third price below tier 2, available only with C-level approval. This is for strategic deals: anchor clients, geographic expansion, a buyer that opens a category. Always on setup, never on MRR.

The floor exists because every sales team will eventually face a deal that justifies more than 20% off. The framework should accommodate that without normalising it. The C-level approval gate ensures these deals are deliberate, not drift.

If you find yourself approving floor deals more than once a quarter, the policy is not working. Either the target price is wrong, the sales team is using the floor as a default, or the deal pipeline does not fit the product.

Ramp pricing instead of MRR discount

The single most useful tool for closing a deal that “needs” an MRR discount is ramp pricing. A ramp gives the buyer a lower MRR for a defined period, after which it returns to target. A typical structure: 50% of MRR in month 1, 75% in month 2, 100% from month 3.

The economics are different from a permanent MRR discount. The ramp gives the buyer time to deploy your product, see value, and absorb the cost. By the time they are at full MRR, they are committed and renewing them at target is straightforward. The total revenue concession is small, the deal closes faster, and the contract does not carry a permanent discount.

Three rules for ramp pricing.

Typically, the ramp should not exceed three months, as anything longer is a permanent discount in disguise. The ramp must be in the contract, with explicit dates and amounts. Verbal agreements about ramps are renegotiation traps at renewal.

The ramp applies only to MRR, never to setup. Setup is paid in full at signing, regardless of any MRR ramp. If a deal needs a ramp longer than three months, or a setup discount in addition to a ramp, you are negotiating against yourself.

Delegation: who can authorise what

The framework is enforced through approval thresholds. Asking the sales team to be careful is not a substitute, because every sales team will be careful in some quarters and less careful in others, depending on pipeline pressure.

A working B2B SaaS organisation has three approval levels.

BDM or account executive.

Can offer the with-discount price (tier 2) without escalation. Cannot offer ramps without manager sign-off. Cannot offer MRR discounts at all.

Sales manager or VP.

Can authorise a ramp up to three months. Cannot move below the with-discount price on setup.

C-level.

Authorises any deal below tier 2 on setup, any ramp longer than three months (rare and discouraged), and any deviation from the framework. Every C-level approved deal is logged with reason, expected return, and a one-line strategic rationale.

Delegation works because the people in different roles have different time horizons. BDMs are measured on closing this quarter’s deals, so they will optimise for closing this quarter’s deals. Quarter-by-quarter optimisation, repeated across many deals, produces the discount drift that destroys margin over years. Delegation thresholds put the people with longer time horizons in control of the longer-time-horizon decisions.

Implementation: the first 60 days

If you walk into a company with no discount policy and want to fix it, here I suggest a rough sequence.

Week 1.

Pull every active contract from the last 24 months. Calculate the effective discount on each, separately for setup and MRR, and build a histogram. The shape of that histogram tells you how bad the problem is and where the worst patterns are concentrated.

Weeks 2 to 3.

Define the three tiers for each product. Document the approval thresholds. Write a one-page memo for the sales team explaining what changes and what stays the same.

Week 4.

Roll the policy out. Communicate it once, clearly, with the rationale. Do not apologise for it.

Weeks 5 to 8.

Watch every deal in the pipeline. Discounts above tier 2 will be requested. The first three or four C-level approval requests are the highest-leverage moments of the rollout. If you approve them all, the policy is probably dead. If you decline one and the deal closes anyway, the sales team learns the new rules are real.

Week 8 onwards.

The policy survives if the CEO is willing to lose a small number of marginal deals to enforce it. If the CEO is not willing, the document is theatre.

The repricing of existing contracts is a separate project, longer and harder, and outside the scope of this framework. Get the new policy working on new deals first, then look at existing contracts in a deliberate program.

What changes when this works

A working discount discipline shows up in three places.

Margin per deal becomes consistent and forecastable. Your finance manager can model a price increase, sales operations can build accurate commission plans.

Pipeline conversation shifts from “what discount do we need” to “is this a deal worth winning at our price.” This is a healthier conversation and tends to produce better deals over time.

Enterprise value rebuilds slowly. The discount discipline does not recover overnight, because the prior contracts continue to drag. But every new deal closed at target adds back the value the prior policy was destroying.

The cost is also real. Some deals will be lost that the previous policy would have won. The sales team will push back, sometimes loudly. The first quarter under the new policy may show flatter or even lower bookings as the team adjusts. This is the cost of fixing the underlying problem, and it is worth paying.

The alternative is the slow erosion of margin and enterprise value. By the time it shows up in the numbers, the discount habit is institutionalised, the sales team is structurally dependent on it, and the cost of unwinding it is much higher.

What I would tell a CEO inheriting a discount mess

Pull the data first. Until you can see the shape of the discount distribution across your active contracts, you cannot have a credible conversation with sales or with the board about what to fix.

Define the policy in writing, including the delegation thresholds, before you announce anything to the sales team. A policy that has gaps will get exploited before the second quarter.

Decline the first borderline deal. Let the sales team see the policy applied. The first decision under the new framework establishes whether the framework is real, or whether you have just produced another internal document.

Discount discipline is one of the few decisions a CEO can make that compounds positively for the entire tenure. The cost is upfront and visible, the benefit is back-loaded and easy to under-credit. Most CEOs leave it for too long, or hand it off to sales leadership and let it become a sales-led conversation. Both mistakes are expensive. The framework above is what I would put in place, in the first 90 days where possible, in the first 180 days at the latest.