Sales Play

Nov 17, 2026

Underpriced Minimums: The Hidden Cost of a Small Commitment

Idea in Brief

The Problem. To close a nervous buyer, sellers often cut the minimum commitment. It feels harmless, because the customer will still pay for what they use.

Why It Matters. The minimum is the predictable part of a usage-based contract, and it's where next year's negotiation starts. Set it too low and you give away the renewal. Set it too high and you create unused spend the customer resents.

The Fix. Before you sign, calculate coverage: expected usage divided by the commit. Aim for a little above 1.0.

Why the Minimum Matters

In a usage-based business, customers pay for what they use: API calls, records, credits, compute. That is fair to the customer, but it is hard on the seller, because usage goes up and down. Revenue that moves around every month is hard for finance to plan on.

The minimum commitment (the commit, for short) fixes that. The customer agrees to pay at least a set amount over the contract, whether they use it or not. In return, they usually get a better price: the committed rate.

For the seller, the commit does two jobs:

  • It is the predictable revenue. Finance can count on it.
  • It is the starting point for renewal. Next year's negotiation begins from the number on this year's contract.

That makes the commit one of the most important numbers on the order form. It is also one of the easiest to give away.

How It Gets Given Away

The conversation usually goes like this. The buyer likes the product but isn't sure how much they will use. "We can't commit to $100K. Can we do $50K?"

The rep wants the deal closed, and $50K feels harmless. The customer will still pay for whatever they use above it. So the rep says yes.

It isn't harmless. The problem is that nobody did the math on what the customer is likely to use. That math has a name: coverage.

What Coverage Is

Coverage compares what a customer uses with what they committed to.

Coverage = Usage ÷ Commit

Measure it over the period the commit covers: month by month for a monthly allotment, over the year for an annual pool. Value usage at the committed rate, and if one commit covers several products, use total dollars. If the commit ramps, compare each period's usage with that period's commit.

Take a customer who will use about $120K next year:

  • Commit of $100K: coverage of 1.2. They clear the commit with room to spare. At renewal, the conversation is about growing.
  • Commit cut to $50K: coverage of 2.4. They blow past it. If overage is billed at list, the customer may even pay more this year. What the seller loses is predictability, and the starting point for renewal: the contract now says $50K is "normal," not the $120K they are expected to spend. And if overage costs about the same as the commit, they have no reason to raise it at renewal (see Overage Discounts).
  • Commit of $150K: coverage of 0.8. They pay for $30K they never used. If the commit was paid or billed up front and unused credits expire with no refund, that $30K becomes what accountants call breakage (see Breakage). If credits can roll over, the seller still owes them (see Rollovers). Either way, the customer feels overcharged, and the renewal starts with an argument.

A good target is coverage of about 1.0 to 1.3: the customer clears the commit, with some room to grow. That band is our rule of thumb, not a published benchmark.

Why Coverage Matters to Revenue

Coverage is one number, but it tells you three things about the revenue behind a deal:

  • How predictable it is. Near 1.0, the commit and the real revenue match, so finance's plan holds.
  • How the renewal will go. Well above 1.3, the customer has outgrown the contract and will negotiate from the old, low number. Below 1.0, they will negotiate from frustration.
  • How much you gave away. A commit cut changes no rate, but it gives up predictable revenue and the starting point for renewal. That costs real money, even though the price never moved.

What Public Companies Have Disclosed

Usage-based companies report both sides of coverage.

  • Coverage below 1.0: MongoDB. Some MongoDB customers committed to more than they used. On its Q1 FY25 call, CFO Michael Gordon said growth would be "impacted by the absence of over $40 million in revenue related to unused customer commitments" recognized the year before. MongoDB had already de-emphasized upfront commitments in its sales incentives. Revenue from unused commitments showed up once, then didn't repeat.
  • Coverage above 1.0: Snowflake. Snowflake's FY26 Q3 10-Q says customer consumption "often exceeds" initial capacity commitments, which can lead customers to renew early and commit to more.
  • Letting usage lead: MongoDB again. On its Q2 FY24 call, Gordon described pulling back on large upfront commitments. Atlas revenue grew "38% year over year, while Atlas dollars committed upfront actually declined by 15%." When the commitment follows the customer's real usage, he said, "the leverage in that negotiation shifts... better pricing for us... less discounting to the customer."

The lesson isn't that smaller commits are better. It's that a commit sized to real usage beats one pushed up to hit a target or cut to close a deal.

How to Calculate Coverage Before You Sign

You can't know next year's usage, but you can estimate it well enough to catch a bad commit. Start with the best evidence you have:

  1. The customer's own usage. Trial or proof-of-concept usage, or what they spend today on the system you are replacing.
  2. Similar customers. What customers of the same size and use case actually used in their first year.
  3. Their rollout plan. How many teams, users or workloads go live, and when.

Turn that into an expected usage number for the period, then divide it by the proposed commit. If the result lands between about 1.0 and 1.3, the commit fits. If it is well above, the commit is too small. If it is below 1.0, it is too big.

Now the buyer's "Can we do $50K?" has an answer. Expected usage is about $120K, so $50K means coverage of 2.4. That is a commit sized for a much smaller customer, and the rep can say so.

When a Smaller Commit Is the Right Call

Sometimes it is. A new customer with no usage history, or a genuine risk that the rollout slips, can justify starting lower. Then treat it as a concession and give it a condition: a step-up to the full commit later in the term, written into the contract, or a mid-term check that raises the commit if usage is running ahead. A concession without a condition is just a discount.

Where AI Helps

The math is simple. A spreadsheet handles it for a few deals. The hard part is doing it at the moment the rep is building the quote, with the right comparable customers in hand. With usage data and coverage targets built into the playbook, AI can calculate expected coverage as the rep sets the commit, and flag a commit that falls outside the band before it reaches the customer.

Try it this week: take your last ten renewals and divide each customer's actual usage by their commit, both at the committed rate. Anything well above 1.3 was sold too small. Anything below 1.0 was sold too big. Count which side your team misses on.

Close the Loop

Once a quarter, calculate coverage for every contract you signed a year ago:

  • If most land well above 1.3, your team is setting commits too low.
  • If many land below 1.0, your estimates are too optimistic.
  • If one segment or rep misses more than the rest, that is where to coach.

Vantage Point

A single sales team sees an underpriced commit once or twice a quarter, which makes each one feel like a one-off. At Revolear, we help usage-based businesses set up dozens of new order forms every quarter, so we see the same mistake across many teams at once. Coverage is the number that catches it.

The Takeaway

The commit is the predictable part of a usage-based contract and the starting point for every renewal. Don't set it by feel or shrink it to get a signature. Estimate usage, calculate coverage, and aim for a little above 1.0. When you do go lower, attach a condition.

Related in this series: this post is part of the Usage-Based Contracting series on credit pricing guardrails. Read more from the series:

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

Which Credit-Pricing Terms Need Approval? A Discount Authority Matrix

The Deal Desk Glossary

Raja Singh is the Founder & CEO of Revolear, the AI deal desk that runs your commercial playbook on every deal.

Sources: Snowflake 10-Q FY26 Q3 · MongoDB Q4 FY24 Earnings Call · MongoDB Q1 FY25 Earnings Call, Michael Gordon · MongoDB Q2 FY24 Earnings Call, Michael Gordon

Experience Revolear

Explore our demos, discover our technology, get a quote, and meet our team—human and AI—in our Virtual Briefing Center.