Software Growth

Overage (fees)

Overage fees are the extra charges a customer pays when they use more than their plan includes, such as extra API calls, contacts or storage.

An overage is use above the amount included in a plan, and the overage fee is what you charge for it. If your $49 plan includes 10,000 emails and a customer sends 13,000, the extra 3,000 are overage, billed on top of the plan price at a per-unit rate. It is the bridge between a fixed subscription and usage-based pricing.

The five parts

Solvimon's guide breaks an overage system into: an included allowance, a threshold where charges begin, an overage rate, a billing frequency, and an optional cap (source). You need to decide each one.

How to calculate it

The plan includes 10,000 emails, the rate is $4 per 1,000 ($0.004 each) and usage is 13,000. Overage = 3,000 x $0.004 = $12, so the invoice is $49 + $12 = $61. If usage is 9,200, overage is zero and the invoice is $49.

Overage models

  • Per-unit. Transparent, but customers can be hit by a surprise bill.
  • Block. Customers buy extra usage in packs (for example 5,000 emails for $15). They control spending.
  • Tiered. The rate falls as overage grows, which rewards heavy users.
  • Auto-upgrade. Usage above the allowance moves the customer to the next plan. No surprises, though it can feel forced.
  • Hard cap. Usage stops at the limit. No bill shock, but the customer loses access at the worst moment.

Why overage fees help you

  • They capture revenue from heavy users whose costs are higher than the flat price covers.
  • They signal when to upgrade. Customers who regularly exceed limits are your best candidates for the next tier, which is expansion revenue you can predict.
  • They let you keep the entry price low for light users.

Why they backfire

The main complaint is bill shock. Solvimon's three fixes are real-time usage visibility, threshold alerts (it suggests 50%, 80% and 100%) and right-sizing recommendations. Beyond that:

  • Set the overage rate above the equivalent price on the next tier. If overage is cheaper per unit than upgrading, nobody upgrades.
  • Make it easy to see what counts as a unit. Disputes about metering cost more than the fee.
  • Avoid overage on things customers cannot control, such as spam sent through a form they host.

For a small SaaS

Overage is a good first step into usage pricing because the base fee keeps revenue predictable. Pick one value metric, include a generous allowance so most customers never see an overage charge, and notify before charging. Record usage with a billing system built for it, which is what metered billing tools do.

Sources

Back to the SaaS glossary