Usage-based pricing lives or dies on one choice: what you charge for

Usage-based pricing depends on the unit you charge for. Public examples from Twilio, AWS, Stripe, Notion and GitHub, four tests and the questions to ask.

Instant Expert EditorialPublished Updated 5 min read

Usage-based pricing succeeds or fails on one choice: the unit you charge for. It bills customers for how much they use, such as messages sent, requests processed or payments handled, instead of a flat fee per seat or per month. The unit, often called the value metric, should rise and fall with the value the customer gets. Choosing it means learning how customers measure results, how they budget and how much a surprise bill would hurt.

Four common models, with public examples

We read these pricing pages on September 30, 2026. Prices change, so check the live pages.

Pay per unit. Every unit has a price. Twilio's US SMS pricing lists $0.0083 per outbound or inbound SMS segment on long codes, toll-free numbers and short codes, with carrier fees added on top depending on the destination network.

Several meters plus a free allowance. AWS Lambda charges for requests and for compute time in GB-seconds (memory multiplied by run time). Its page lists $0.20 per million requests and a monthly free tier of one million requests and 400,000 GB-seconds. The allowance lets people build and test for free.

A percentage of the transaction. Stripe's pricing page lists 2.9% + 30¢ per successful transaction for domestic cards, with no setup or monthly fees. Stripe earns more when its customer sells more, which ties the price closely to the customer's results.

A subscription with usage on top. Many seat-based products add a metered part. Notion's pricing page sells plans per member and prices its Custom Agents separately at $10 per 1,000 monthly Notion credits after a free trial. GitHub's plans include a monthly allowance of CI/CD minutes that grows with the tier, and Codespaces compute starts at $0.18 an hour.

Stripe's usage-based billing documentation calls usage-based billing a common pricing model for SaaS businesses and lists features such as prepaid credits, usage alerts and tiered pricing.

A good value metric passes four tests

  1. It rises when the customer gets more value. Stripe's percentage grows with the customer's sales. A per-seat price for a tool one person runs for the whole company does not.
  2. The customer can predict it. Finance teams need to budget. A unit they already track, such as orders or invoices, is easier to forecast than one they have never measured, like API calls.
  3. The customer can control it. People accept a bigger bill when it follows something they chose to do. A bill that jumps because of a background process feels unfair.
  4. You can measure it accurately. If you can't count the unit reliably and show customers the count, disputes follow.

The tests often conflict. The unit closest to value, such as money saved, may be the hardest to measure and predict, so most companies settle on a stand-in customers already count.

A made-up example: an invoice-processing API

Here is a made-up example, numbers included. You sell an API that reads supplier invoices and extracts the line items for accounting teams. You are choosing between per-seat, per-invoice and a monthly plan with an invoice allowance.

At $0.40 per invoice, a customer processing 2,000 invoices a month pays 2,000 x $0.40 = $800. If the same customer processes 6,000 invoices at year-end, that month costs 6,000 x $0.40 = $2,400, three times the usual bill. Whether finance shrugs or escalates depends on how they budget, and only they can tell you.

Ask accounting leads and the people who approve software spending:

  • "How do you count invoices today, and do you know last year's monthly numbers?" This checks whether they can predict the unit.
  • "What happens in your busiest month?" This shows how much the bill would swing.
  • "How did you budget for the last tool you paid for by usage?" A real past purchase beats a hypothetical reaction.
  • "If your bill doubled in one month, who would notice and what would they do?" This shows whether you need caps, alerts or prepaid bundles.
  • "Would you rather pay a fixed amount that covers most months, with a charge for extra invoices?" This tests a hybrid plan.

Suppose the interviews show that finance teams know their invoice volumes, dislike surprises and approve annual budgets. That points to a monthly plan with an included allowance, for example 2,500 invoices for $900, a per-invoice rate above that, and an alert when a customer nears the limit. Test the numbers themselves with real quotes; how to research willingness to pay covers that step.

Use it when usage varies a lot, and avoid it when usage scares people off

It fits when usage varies a lot between customers, when small customers need a cheap way to start, and when your costs rise with usage, as with messaging, compute or payments.

It fits poorly when customers can't predict usage and hate variable bills, when usage and value are only loosely linked, or when heavy use would make customers avoid the product. If a team starts rationing a collaboration tool to save money, the price is working against adoption.

That is why hybrid plans exist: the subscription gives predictability and the meter captures heavy users.

Your next step

List three candidate units for your product and score each against the four tests. Then use current customers' usage data to see how much each unit's bill would vary by customer and by month.

If you need to check your unit with people who budget for this kind of software, describe them to Instant Expert, such as "accounts payable managers at mid-size companies." The budgeting questions in the example work as a 30-minute call. A single question, such as "what happens to your software bill in your busiest month?", can go out as a written request, which they answer in text or by voice note. Each person sees the amount you set and your note; our fee is added on top for you (a $100 offer costs you $125), and nothing is charged until they book or answer. The directory pages for finance professionals in enterprise SaaS and product professionals in financial technology are one place to start.