Overage
OH-ver-ij
Charges that kick in when a customer exceeds their plan's included usage limits. The bill that surprises people.
Overage is what you pay when you exceed your plan limits. Your plan includes 100GB of storage. You use 150GB. The extra 50GB is overage, billed at the overage rate. Overage rates are almost always higher than the per-unit cost of upgrading to the next tier.
Overage is a deliberate pricing mechanism. It discourages customers from staying on plans that are too small while generating additional revenue from customers who burst above their limits. But overages can also destroy trust. A $29/month plan that generates a $500 overage bill will create an angry customer and a support ticket.
The best companies handle overage gracefully. They send alerts at 80% and 100% of limits. They offer automatic tier upgrades when usage consistently exceeds the plan. They cap overage charges so bills never spiral out of control. Bad companies let customers discover overage charges on their invoice.
Examples
A startup gets an unexpected overage bill.
A startup on Vercel's Pro plan gets a $2,000 overage bill after a blog post goes viral. Their plan included 1TB of bandwidth. The viral traffic consumed 5TB. At $0.50/GB overage, the extra 4TB cost $2,000. The CTO scrambles to add a CDN and enable caching.
Overage as a growth signal.
A customer on Datadog's $15/host plan consistently uses 30% more hosts than their contracted amount. The AE uses overage data to justify an upgrade conversation: "You are paying overage rates for 15 hosts every month. An annual contract at scale pricing would save you 25%."
A company designs overage-free pricing.
Netlify offers "soft limits" where they notify you when you exceed bandwidth but do not charge overage on the first occurrence. This builds goodwill. Customers upgrade voluntarily because they trust Netlify will not surprise them with a bill.
In practice
Read more on the blog
Frequently asked questions
Should I charge overage or hard-cap usage?
It depends on the consequences. For billing (Stripe), hard-cap usage and your customer's business stops. Bad idea. Charge overage. For bandwidth (a marketing site), hard-cap and show a friendly upgrade page. For storage, send warnings and give a grace period. Never let a customer's production system go down because of a billing limit.
What is a fair overage rate?
1.5-2x the per-unit cost of the next tier up. This makes overage slightly expensive (encouraging upgrades) without being punitive. If your $99 plan includes 100k API calls and your $199 plan includes 500k, the overage rate should be about $0.003-0.004 per call, not $0.01.
Related terms
Charging customers based on how much they consume. Pay for what you use. The model behind Snowflake, Twilio, and AWS.
Offering multiple pricing plans at different price points, each with more features or higher limits. The classic Good/Better/Best model.
A virtual currency customers buy upfront and spend as they use your product. The bridge between subscriptions and pure usage-based pricing.
Tracking and measuring customer usage in real time for billing purposes. The plumbing that makes usage-based pricing work.
Want the complete playbook?
Picks and Shovels is the definitive guide to developer marketing. Amazon #1 bestseller with practical strategies from 30 years of marketing to developers.