Experience Revolear
Explore our demos, discover our technology, get a quote, and meet our team—human and AI—in our Virtual Briefing Center.
The Problem. Most approval rules watch one number: the discount off list. In a usage-based deal, the commit, the overage rate, rollover and expiry move price and revenue just as much.
Why It Matters. A deal can pass the discount check and still give away more than it looks, lock in less predictable revenue, or push revenue into later periods.
The Fix. Judge every term through two lenses, effective discount and revenue recognition, attach a condition to every concession, and decide who approves each one.
Discounts get watched for good reason: small price cuts take bigger volume gains to make up. (McKinsey's well-known example puts it at 18.7% more volume for a 5% cut at typical company margins; at software margins it is closer to 7%, but the direction holds.)
But in a usage-based deal, the discount off list is only one of the terms that set what the customer really pays and what the seller can count on. This series covered the others:
None of these show up on the discount line.
Every term in a usage-based deal can be judged with two questions:
The first tells you how much you gave away. The second tells you how much you can count on, and when.
Here is how the terms stack up for one customer. List price is $1.25 a credit. The customer commits to 100,000 credits a year at $1.00, which is 20% off, granted monthly. Their usage is uneven: between 6,000 and 13,000 credits a month, 110,000 for the year. As each term is added, the real discount off list grows:
Every deal shows the same 20% discount on the order form. But the 30-day rollover alone added more discount than the commit did, and none of it shows up on the discount line. Illustrative numbers; assumes the oldest credits are used first.
Every term rolls up into three numbers:
Take two deals for another customer. List price is $1.00 per unit, the committed rate is $0.80 (a 20% discount), and the customer will use 150,000 units. Illustrative numbers.
Both deals show the same 20% discount on the order form. Deal B gives away $6K more this year, has $16K less committed value, and gives the customer no reason to commit to more at renewal. A discount-only approval rule sees no difference.
Here is who can offer each term, when it needs approval, and the condition to attach. The thresholds are examples; set your own.
| Term | Rep can offer | Needs approval (owner) | Condition to attach |
|---|---|---|---|
| Discount off list | Within the standard band | Above the band (sales leadership) | A bigger commit or a longer term |
| Commit size | Expected coverage of about 1.0 to 1.3 | Expected coverage outside that band (deal desk) | A step-up to the full commit later in the term, or a mid-term check that raises it if usage runs ahead |
| Ramped commit | Your standard ramp schedule | A longer or steeper ramp (deal desk) | Firm step-up dates and amounts in the contract |
| Overage rate | Above the committed rate | At or below the committed rate, or tiers that undercut it (deal desk) | A cap on discounted overage, or moving overage into a bigger commit before renewal |
| Rollover | Finance's standard rollover terms: capped, with an expiry, tied to renewal | Anything else (deal desk, with finance) | A cap, an expiry, and a renewal sized to real usage |
| Expiry and refunds | Credits that expire (the default) | Any refund right, or a deal priced to rely on breakage (finance) | A refund limited to a stated amount |
And here is what each term does through the two lenses:
| Term | Effective discount | Revenue recognition |
|---|---|---|
| Discount off list | The discount itself | Same timing; lower revenue per unit |
| Commit size | None directly, but a small commit lowers where renewal starts | Less committed value |
| Ramped commit | None directly | Less committed value early; revenue still follows usage, not the billing ramp |
| Overage rate | A lower rate deepens the discount on growth and shrinks the commit incentive | Growth recognized at a lower rate |
| Rollover | Raises it by cutting the cost of expired credits, and reduces the commit needed: 1 − (commit with rollover ÷ commit without) | Revenue generally stays deferred while credits carry; conditional rollovers can change the accounting |
| Expiry and refunds | Planned breakage raises the customer's effective price (committed rate ÷ coverage); a refund removes that cost | Credits expected to go unused become breakage revenue, gradually or at expiry; refundable credits stay a liability until used or refunded |
Guardrails on each term are necessary, but not enough. Deals that hurt rarely break one rule. They bend several at once: a smaller commit, cheaper overage, a generous rollover, each under its own threshold. Together, they add up to a bigger effective discount, less committed value, and more revenue pushed into later periods.
The rule that runs through this series applies here too: a concession without a condition is just a discount. The matrix shows which condition belongs with each concession, and who decides.
And sometimes the concession is right. A new customer with no usage history, genuinely seasonal usage, or a slow start the seller caused can all justify one. The point isn't to say no. It's to know what you're giving, and to get something back.
A spreadsheet can run these three numbers for one deal. Running them on every deal, as the rep builds it, is harder. With the rate card, coverage targets and these rules built into the playbook, AI can calculate effective discount, committed value and commit incentive as the deal takes shape, so in-policy deals can clear faster and the rest reach an approver with the whole picture, not just a percentage.
Try it this week: take your last five usage-based deals and calculate the three numbers for each, using expected usage for deals less than a year old. Flag two patterns. First, usage above the commit but an effective discount equal to the order-form discount: overage is priced at the committed rate, so the commit incentive is gone. Second, usage below the commit: coverage is under 1.0, so the effective discount falls below the order-form discount, and turns negative once coverage drops below (1 − the discount). The customer is paying for credits they won't use, and the renewal is at risk.
Once a quarter, look at the whole book:
The deals that hurt are rarely the ones with a big discount. In the deals we see at Revolear, they are the ones where several small concessions rode together, each under its own threshold, and nobody added them up.
In a usage-based deal, the discount on the order form is only part of the price. Judge every term by its effective discount and what it does to revenue recognition. Attach a condition to every concession, decide who approves each one, and add up the whole deal before it goes out.
Related in this series: this post is part of the Usage-Based Contracting series on credit pricing guardrails. Read more from the series:
Underpriced Minimums: The Hidden Cost of a Small Commitment
Overage Discounts: Why Cheaper Excess Undermines Renewals
Rollovers, Expiry, and Refundability: The Terms That Move Revenue
Planned Unused Credits: Breakage Is a Finance Call, Not a Sales One
Raja Singh is the Founder & CEO of Revolear, the AI deal desk that runs your commercial playbook on every deal.
Sources: McKinsey, "The Power of Pricing", plus the sources in each post in the series.
Explore our demos, discover our technology, get a quote, and meet our team—human and AI—in our Virtual Briefing Center.