How usage-based pricing works for SaaS

Usage-based pricing means the customer's bill follows how much they use your product: emails sent, subscribers stored, API calls made, payments processed. Flat plans charge the same amount no matter what. With usage pricing, revenue from an existing customer grows when their usage grows, with no upgrade pitch. It fits products where usage tracks the value the customer gets and where you can count that usage cleanly.

How to do it

1. Pick one usage metric that rises when the customer gets more value. Good metrics are easy for the customer to see and hard to game: contacts, messages, transactions, seats actively used, or API requests. Avoid metrics the customer cannot check themselves.
2. Check that your costs move with the same metric. If the metric grows and your costs do not, you leave margin on the table. If costs grow faster than the metric, you lose money on your biggest customers.
3. Choose the shape. The common ones are pay per unit, tiers (price steps up at set volumes), and a base fee plus included usage with overage. Tiers are the easiest shape for customers to predict.
4. Set a free or low entry point so people can try it. Then publish the price at each volume on one page, with an example bill.
5. Build metering before you launch. Count every billable event once, store it, and show the customer their current usage inside the product. Stripe documents this as recording usage and billing for it, and it also covers alerts when a customer passes a usage threshold, which you can use for warnings before the invoice.
6. Add a spending cap or alert option. Customers who fear a surprise invoice will pick a flat competitor.

Examples

Stripe charges a percentage of what it processes. Its public pricing lists "2.9% + 30¢" per successful domestic card transaction, so Stripe earns more as the merchant sells more. See Stripe pricing.

EmailOctopus prices email by volume. Its pricing page lists a free plan of 2,500 subscribers and 10,000 emails per month, and a paid Pro plan priced by subscriber count. The page says plans upgrade automatically as the mailing list grows, so a growing customer pays more without talking to anyone.

When it backfires

• Bills become hard to predict. Finance teams want a budget. If a customer cannot guess next month's invoice, they may leave or ask for a flat contract. Caps, alerts and prepaid credits help.
• Your revenue gets lumpy. A customer's usage can fall as easily as it rises. Forecasting is harder than with flat plans.
• The wrong metric punishes the behavior you want. If you charge per project, customers delete projects. Charge for the thing that signals success.
• Billing errors cost trust. Double-counted usage creates support tickets and refunds. Test your metering against a second source before you bill real money.
• It is more work to build. Stripe's docs now recommend its Metronome product for new usage-based integrations and keep the older Billing Meters for existing ones. Check which is current before you start.

For a middle path, look at progressive pricing, where price steps with growth, or add a flat base fee so you always have a floor.

Questions people ask

What is usage-based pricing? A pricing model where the amount a customer pays depends on how much of a defined unit they consume, such as messages, requests or transactions, rather than on a fixed plan.

Is usage-based billing the same as usage-based pricing? Pricing is the model you choose and publish. Billing is the system that meters usage and produces the invoice. You need both.

What tools manage usage-based billing? Stripe Billing supports it through its usage-based billing docs, including Metronome, which Stripe now owns. Dedicated billing vendors exist, so compare what each handles before picking.

Sources

• Stripe pricing, read Oct 8, 2026
• EmailOctopus pricing, read Oct 8, 2026
• Stripe docs: basic usage-based billing, read Oct 8, 2026