Overage

Overage is what a customer pays for going past the allowance in their plan. A contract including 1,000,000 API calls per month at $2,000, with overage at $0.0025 per call, bills $2,250 in a month with 1,100,000 calls.

The design questions

• Reset or accumulate? Does the allowance reset each billing period, or can unused volume roll forward? Rolling allowances are customer-friendly and materially harder to model in forecasting.
• Annual or monthly measurement? A customer with an annual commitment of 12,000,000 calls who uses 1.4M in March and 0.8M in April has no annual overage but two months of monthly overage. Which applies must be explicit in the contract.
• Tiered overage rates? Rates that step down as overage volume rises soften the penalty for genuine growth, at the cost of complexity.

Overage is a renewal signal, not just revenue

Sustained overage means the customer has outgrown their plan. Treating that purely as incremental revenue is a short-term view: the customer eventually notices they are paying a premium rate for volume they consume every month, and arrives at renewal annoyed.

The better motion is to treat repeated overage as an expansion trigger and proactively quote a higher commitment at a better unit rate. The customer gets a lower effective price, you get committed revenue instead of variable, and the renewal conversation starts from a favour rather than a grievance. That only works if someone — or something — is watching the overage pattern across the whole book of business rather than discovering it invoice by invoice.