Is It the Rate or the Total? Two Different Fears, Two Different Answers

Idea in Brief

The Problem. Customers pushing back on overage terms almost always phrase the objection the same way — "we don't want surprises" — but the fix a deal desk reaches for depends on which surprise they actually mean.

The Instinct That's Wrong. Treating every true-up objection as the same objection and reaching for a single default answer, usually a flat discount on overage.

The Fix. Diagnose whether the customer fears an unpredictable unit rate or an unpredictable total bill — they're different problems, and the clause that fixes one doesn't fix the other.

Two Fears That Sound Identical

"We don't want a surprise bill" collapses two distinct concerns into one sentence. The first is a rate fear: the customer worries that once they cross their allotment, every additional unit costs more than they budgeted for — a punitive, unfamiliar number per credit. The second is a total fear: the customer isn't worried about the per-unit rate at all; they're worried about not knowing the aggregate size of next month's invoice until it lands. A clause that fixes the rate fear (honoring the discount on overage) does nothing for a customer who's actually worried about the total, and vice versa.

Metronome's enterprise commit guide documents this exact fork in how vendors design overage policy: "Some vendors continue billing overages at the same discounted rate, which encourages usage growth. Others revert to standard or premium rates to prompt renewals or upsell discussions. A hybrid model can also work — honoring the discount for moderate overages while retaining the right to renegotiate when usage consistently exceeds the committed amount." McKinsey documents a parallel, complementary shift: leaders are moving away from billing overages immediately and toward "true forward" mechanisms that adjust the next commitment based on actual prior-period consumption, paired with re-pricing enterprise agreements every six to twelve months rather than every three to five years — a structural answer to the total-bill fear rather than the rate fear. L.E.K. Consulting's "drawdown model" formalizes the same idea from the vendor side: bill overages at the end of the cycle based on actual usage, with an annual true-up that either charges for the overage or credits the unused allotment.

Why the Wrong Fix Doesn't Land

A rep who hears "we don't want surprises" and offers a bigger discount on overage has fixed the rate fear and left the total fear completely unaddressed — the customer still won't know the size of the bill until it arrives, discount or not. Conversely, a rep who offers usage alerts and a defined true-up cadence without touching the rate has fixed the total fear but left a customer worried about punitive per-unit pricing no better off. Getting the diagnosis right before proposing a fix is the entire job.

The Exhibit: True-Up / Overage Reconciliation

Plain-English variants of the same order-form clause, sized for a roughly $100K Order Form. All three share one clause title — True-Up / Overage Reconciliation — so switching tiers means swapping the body text only.

Preferred: List-Rate Overage With Proactive Alerts

If Customer's actual usage in a given month exceeds the Monthly Credit Allotment, Vendor will invoice the overage at the standard list rate per credit, billed in the month following the overage period. Vendor will notify Customer within five (5) business days of Customer reaching eighty percent (80%) and one hundred percent (100%) of its Monthly Credit Allotment.

Use this when: the objection is really a total-bill fear, not a rate fear — the alert cadence removes the "surprise" before the invoice arrives, while list-rate overage preserves margin. This is the standard opening structure Metronome documents across enterprise commit contracts.

Fallback: Discounted, Capped Overage Rate

Overage usage in any given month will be billed at Customer's contracted discounted rate (rather than list), provided cumulative overage across the Term does not exceed twenty percent (20%) of the Total Commit Amount. If cumulative overage exceeds this threshold, the parties will conduct a true-up review and adjust the Total Commit Amount for the following Term accordingly.

Use this when: the objection is a genuine rate fear — the customer is comfortable with the aggregate exposure but doesn't want to pay a punitive per-unit price for going over. This mirrors Metronome's documented hybrid model of honoring the discount for moderate overages while retaining the right to renegotiate at sustained excess.

Approval-Required: Custom Annual True-Up Cadence

In lieu of monthly overage billing, the parties agree to a single annual True-Up at the end of the Term: Customer will be invoiced for actual usage exceeding the Total Commit Amount, or credited (in the form of renewal credits, non-refundable) for any unused committed amount below ninety percent (90%) utilization, at the then-current discounted rate.

Use this when: the account is strategic and shows strong expansion signal — this is McKinsey's "true forward" pattern, deferring reconciliation to renewal instead of monthly billing. It requires sign-off because it defers revenue recognition and introduces renewal-timing risk.

A defined trigger, cap, or cadence should appear in every tier above. An open-ended "we'll true up whenever" clause with no cadence is not a fallback — it is the absence of a clause, and it should never be offered without escalation.

The Vantage Point

Revolear sets up dozens of new Order Forms every quarter for usage-based businesses and assists our customers' sellers in structuring exactly this clause. The rate-versus-total distinction is the single most common misdiagnosis we see on true-up objections — reps reach for the discount lever because it's the most familiar one, even when the customer's actual concern is about predictability, not price.

The Takeaway

"We don't want surprises" is not a clause request — it's a diagnostic question. Ask which surprise the customer means before proposing a fix, and the true-up clause you draft will actually resolve the objection instead of just moving it to the next renewal.

Related in this series: this post is part of Revolear's Usage-Based Contracting series on the business clauses governing the primary subscription term. Read more from the series:

What Contract Terms Are Becoming Standard in AI/Credit-Based SaaS? (pillar post)

When a Customer Won't Commit to a Minimum

Making Usage Revenue Look More Like SaaS