Usage-Based Billing

Usage-based billing charges a customer for how much they actually consume — API calls, gigabytes, seats used, messages sent — rather than a flat recurring fee. Consumption is metered over a billing cycle and totaled into a charge when the period closes, so the invoice reflects real usage.

How it works

You report usage events to your billing system as they happen, and at the end of each period the system multiplies the metered quantity by a price and writes an invoice item.

• Metering — record each unit of usage against the subscription (Stripe's meters aggregate raw usage events into a billable total).
• Aggregation — sum, max, or last-value over the period determines the billable quantity.
• Rating — the quantity is priced, often with tiered pricing so higher volumes cost less per unit.

Many products combine a fixed base fee with a usage component — a hybrid model that guarantees some recurring revenue while still scaling with consumption.

Why it matters

Usage-based pricing aligns cost with value: light users pay little, heavy users pay more, and there's a low barrier to starting. The trade-off is predictability. Because revenue depends on behavior, pure usage-based MRR is harder to forecast, and a customer's bill can spike unexpectedly. Committed spend, minimums, and caps are common ways to add stability.

What to watch

• Bill shock — a sudden usage spike can produce a surprise invoice and a payment failure.
• Revenue volatility — usage revenue swings with seasonality and customer activity.
• Reconciliation — metered totals must match what customers see, or disputes follow.