Where the money actually leaks
Most usage-based deals combine three elements: a minimum commitment (annual spend or unit volume), a discounted rate for usage inside that commitment, and an overage rate for anything above it. Each one creates a specific risk.
- Unused commitment (shelfware). You committed to 10 million API calls and used 6 million. The remaining 4 million are paid for and gone, unless the contract says otherwise.
- Overage at list price. The committed rate is discounted, but the contract is silent on overage, so the vendor bills at published rates. This is often the largest surprise on an invoice.
- Auto-escalating minimums. Renewal terms that raise the minimum to last year's actual usage, or by a fixed percentage, regardless of your plans.
- Definition drift. The billable unit (seat, active user, event, GB processed) is loosely defined, so what counts toward usage changes as the vendor updates its product.
Before negotiating price, identify which of these your deal is exposed to. The discount percentage matters less than the structure around it.
Size the commitment from your own data
Vendors will offer a forecast. Treat it as a sales document. Build your own.
- Pull 6 to 12 months of actual usage from the vendor's admin console, your invoices or internal logs. If this is a new vendor, use data from the tool you are replacing or from a paid pilot.
- Separate baseline from growth. Baseline is what you will use even if nothing changes. Growth depends on projects, hiring or launches that may slip.
- Commit to baseline, not the forecast. A common practitioner approach is to commit somewhere around 70 to 85 percent of expected usage and cover the rest with pre-agreed overage rates. The right number depends on how predictable your usage is and how steep the discount gap is between tiers.
- Model three scenarios: low (projects slip), expected and high. Calculate total cost under each for every commitment level the vendor offers.
- Check the break-even. If committing to the next tier saves 10 percent on unit price but you only reach that tier in the high scenario, you are paying for optimism.
Write down the assumptions. At renewal, you will want to show why the commitment was set where it was.
Negotiate flexibility into the commitment
A lower unit price with no flexibility often costs more than a slightly higher price with room to move. Ask for these, roughly in order of how often vendors agree:
- Ramped commitments. Lower minimums in year one, rising in years two and three as adoption grows.
- Rollover. Unused commitment carries into the next period, at least partially.
- Pooling. Commitment counts across products, regions or business units instead of per line item.
- Swap rights. The right to move committed spend from one product or SKU to another of equal value.
- Downward adjustment. A one-time right to reduce the commitment by a set percentage at a defined point, for example at the first anniversary.
Example rollover clause:
Any portion of the Annual Commitment not consumed during a Contract Year shall carry forward to the following Contract Year, up to a maximum of 25% of the Annual Commitment. Carried-forward amounts are consumed before current-year commitment.
Example pooling clause:
Customer's consumption of all Services listed in Schedule A shall count toward the Annual Commitment, regardless of the Service, region or Customer affiliate consuming them.
Lock overage pricing before you sign
Overage is where leverage shifts to the vendor. Once you are live and over the limit, you have no negotiating position. Settle it now.
- Overage at the committed rate. Ask for overage to be billed at the same discounted rate as committed usage. If the vendor refuses, negotiate a fixed premium, not list price.
- Tiered overage. If usage passes the next volume tier, the lower tier rate should apply to overage automatically.
- Retroactive tier pricing. If annual usage lands in a higher tier, the lower unit price applies to all usage for that year, not just the incremental units.
- Notification thresholds. The vendor must notify you at, for example, 80 percent and 100 percent of commitment.
- Hard caps or approval gates. For variable-cost services, require written approval before overage exceeds a set amount.
- Overage credit toward upgrade. Overage paid during a year can be credited toward a higher commitment if you upgrade mid-term.
Example overage clause:
Usage in excess of the Annual Commitment shall be invoiced at the Committed Unit Rate set out in Schedule B. Vendor shall provide written notice when Customer's usage reaches 80% and 100% of the Annual Commitment. Overage exceeding $[amount] in any calendar month requires Customer's prior written approval.
Run the RFP so pricing is comparable
Vendors structure usage pricing differently on purpose. Comparisons break down unless you set the format.
- Give every bidder the same usage scenarios. Provide your low, expected and high volumes and require a total cost for each over the full term.
- Require a pricing template. Columns for billable unit definition, committed volume, committed rate, overage rate, tier thresholds and annual escalator.
- Ask for the unit definition in writing. "Active user" means different things at different vendors. Ask how it is measured, when it resets and what counts.
- Ask about renewal pricing now. Request a cap on renewal price increases, commonly expressed as a fixed percentage or tied to an inflation index.
- Score total cost across scenarios, not the headline unit price.
Example RFP question:
For each scenario in Appendix C, state the total cost over the 36-month term, including committed spend, expected overage and any platform or minimum fees. State the rate that applies to usage above the commitment and whether tier discounts apply retroactively.
Manage the contract after signature
Most overpayment happens after the deal is signed because nobody is watching usage.
- Assign an owner for each usage-based contract, with access to the vendor's usage dashboard.
- Review usage monthly against a straight-line burn of the commitment. Flag if you are more than 15 to 20 percent off pace in either direction.
- Reconcile invoices against the contract rate card, especially overage lines and any new SKUs.
- Act mid-term. If you are trending over, use it to negotiate an upgrade at better rates before overage accrues. If you are trending under, check for swap rights, pooling or redeployment options.
- Start renewal 90 to 120 days out, which is a common practitioner window, with actual usage data in hand. Check the contract for auto-renewal and notice deadlines.
Let pingpong run it for you
pingpong drafts the RFP, finds and invites vendors, collects proposals through a private portal, scores them with five AI models and flags the gotchas above. It drafts every negotiation message for your approval, then keeps watching the market so you renegotiate before renewal. $100 for the first month, then $799 a month.
Common questions
Should I always commit to the lowest volume the vendor offers?
No. Commit to the volume you are confident you will use, which is usually your baseline rather than your forecast. If overage is priced at or near the committed rate, a lower commitment carries little risk. If overage is at list price, a slightly higher commitment may cost less overall, so model both.
What if the vendor refuses to negotiate overage rates?
Ask for alternatives: a notification threshold, a monthly approval cap, retroactive tier pricing or the right to upgrade mid-term with overage credited. If none are available, lower your commitment and budget for overage explicitly. Also treat the refusal as a scoring factor in the RFP.
How do I handle a true-up clause?
Read how true-up is calculated and when it is billed. Push for true-ups to be priced at committed rates, billed annually rather than quarterly, and to apply only forward, not retroactively to the start of the term. Make sure a true-up does not automatically raise your renewal minimum.