Add a usage-based component to your pricing

Flat per-seat pricing works until your customers use the product very differently. A small team that sends a handful of reports and a small team that runs thousands of jobs a day pay the same, even though one gets far more value and costs you far more to serve. A usage component lets revenue track value without forcing every customer into a bigger plan.

Why it works

When the price follows a metric the customer already values, the bill feels fair. Small customers start cheaply, and customers who get a lot of value pay more without a sales conversation. Revenue grows inside existing accounts as they succeed.

The base fee keeps that growth on solid ground. It covers your fixed costs, gives the customer a clear entry price, and limits how far revenue can fall in a slow month.

How to do it

1. Pick a value metric customers understand. Good metrics are things the customer already counts, such as invoices sent, contacts stored, API calls or hours processed. Avoid internal measures like compute units that buyers cannot predict.
2. Check that the metric grows with success. When a customer gets more value, usage should rise. If usage can climb while value stays flat, customers will resent the bill.
3. Keep a base fee with included usage. Charge a monthly platform fee that includes a sensible allowance, then price the overage per unit or in blocks. This keeps the entry price clear.
4. Model bills for your current customers. Run last quarter’s usage data through the new pricing. Look for accounts whose bill would jump sharply and decide how you will handle them before launch.
5. Build visibility into the product. Add a usage meter, emails at set thresholds and an optional cap. Make the invoice show units and rates line by line.
6. Roll out to new customers first. Move existing accounts later with notice and a transition period, or let them keep their plan until renewal.

Example

A B2B invoicing tool charged per seat, yet its value came from the volume of invoices each account sent. Two-person agencies sending a few dozen invoices paid the same as two-person wholesalers sending thousands. The team moved to a base fee that included a monthly invoice allowance, with blocks of extra invoices priced above it. Before launch they modelled every current account and found a small group whose bill would rise a lot. Sales called each of those customers, offered annual commitments at a discount, and moved them over at renewal.

Metrics to track

• Net revenue retention. Revenue this year from last year’s customers, including expansion. Should rise as heavy users pay for more usage.
• Share of accounts paying overage. Shows whether the included allowance is set sensibly. Very high or very low both call for a review.
• Billing disputes and support tickets about invoices. Should stay low. A rise means bills are confusing or metering is wrong.
• Usage per account over time. Should keep rising. A drop after launch can mean customers are rationing to save money.
• Win rate on new deals. Should hold steady or improve. A fall can mean buyers fear unpredictable bills.

When it backfires

• Unpredictable bills. Finance teams hate invoices they cannot forecast. Without caps, alerts or committed tiers, usage pricing slows deals and raises churn.
• A metric that punishes adoption. If customers ration use of your product to save money, they get less value and are more likely to leave.
• Billing you cannot run reliably. Metering errors and disputed invoices create support load and erode trust. Test the billing pipeline before you charge anyone.
• Revenue that swings with seasons. Usage drops in quiet months. Make sure your plans for cash and hiring can absorb that.

Questions people ask

Should I switch fully to pay-as-you-go?

Most small SaaS teams do better with a hybrid. A base subscription keeps revenue steady and covers your fixed costs, and a usage component lets heavy users pay more as they get more value.

How do I stop customers from fearing a surprise bill?

Show live usage in the product, send alerts as they approach thresholds, and let them set a spending cap. Customers accept variable pricing far more readily when they can always see where they stand.

How often should usage be billed?

Monthly in arrears is the simplest for most products, with the base fee charged up front. Very high-volume products sometimes bill when usage crosses a threshold to limit unpaid balances.