Show all

Usage-Based Pricing: The Licensing Layer Your Billing Tool Doesn’t Cover

Usage-Based Pricing

In two of our recent posts, we looked at why seats break down for AI features and why access and consumption should be priced separately. Both point to the same conclusion: more software is moving to usage-based pricing. According to McKinsey, the number of software companies using consumption-based pricing more than doubled between 2015 and 2024. And the shift is speeding up: Gartner forecasts that by 2030, at least 40% of enterprise SaaS spend will move toward usage-, agent- or outcome-based pricing.

Most guides on the subject focus on billing, but that's only half the system. Before you can invoice for usage, your application has to know what each customer is allowed to consume, count it accurately, and act when they reach the limit. That's a licensing problem.

 

What is usage-based pricing?

Usage-based pricing (also called consumption-based or metered pricing) charges customers for how much they use a product, rather than how many users they have or how long they subscribe. Common units include API calls, files processed, compute hours, AI tokens and session time.

Customers pay in line with the value they get, and vendors gain revenue that grows with adoption, while a lower barrier to entry is created.

 

Usage-based billing vs usage-based licensing

Billing and licensing are often treated as the same thing. They aren't.

Usage-based billing works after the fact. It collects usage records, applies your rate card and produces an invoice.

Usage-based licensing works before and during use. It decides whether a customer can use a feature right now, tracks consumption against what they bought, and stops or flags overuse.

The difference shows up in three consumption modes:

  • Enforced: the license holds a fixed quantity, such as 15,000 document exports or 500 compute hours. When it runs out, access stops until the customer renews or upgrades.
  • Enforced with overage: the same quantity applies, but customers can exceed it by a defined amount, and the extra usage is billed in arrears.
  • Metered: there is no hard cap. Usage is tracked and reported so it can be billed later.

A billing platform alone gives you the third mode, but it cannot stop a customer from consuming far beyond what they've paid for, because it never sits in the path of the request. If your app is a desktop product, it may not even see the usage until long after it happened.

 

Common usage-based pricing models

Most ISVs combine several of these:

  • Pay-per-use: each discrete action costs a unit, such as opening a file or running a report. Units can also scale with the action, so a 4 GB upload might consume 4 units.
  • Time pools: customers buy a block of hours, and each session draws it down.
  • Credits or tokens: a shared balance that different actions consume at different rates. This is the model we explored for AI features.
  • Base allowance plus overage: a subscription includes a set amount of usage, with extra consumption billed separately.
  • Hybrid: seats or subscriptions for access, combined with metered consumption for high-value features.

Hybrid is where most B2B products land. Pure usage pricing can make costs hard for customers to predict, while a base subscription gives them a floor they can budget for.

 

How to implement usage-based pricing in your app

  1. Choose the unit. Pick something customers understand and that tracks the value they receive. If they can't predict it, they'll resist it.
  2. Model it as an entitlement. Each customer's quantity, term and features should live in one place, not across your billing system, CRM and code. (What is entitlement management?)
  3. Check out, report, release. Your application requests a license before use, reports consumption while it runs, and confirms the final quantity at the end.
  4. Enforce in real time. Decide whether a limit blocks usage or allows a defined amount of overage. Make that a configuration choice, not a code change.
  5. Plan for offline use. Desktop and on-premise customers won’t always be connected. Long-lived, signed license tokens let your application keep enforcing license terms while offline.
  6. Connect your commerce stack. When a customer buys, renews or changes their plan in your billing or CRM system, their entitlements should update to match, without manual re-keying.
  7. Show customers their usage. Usage pricing without visibility creates bill shock, which drives churn. Track consumption in your application as requests are granted, and check the current license balance whenever you need an up-to-date figure.

 

Build or buy?

Many ISVs start by adding a usage counter to their in-house licensing system. It works until pricing changes. Then a new credit model, an overage tier or a hybrid bundle becomes an engineering project, and sales waits for the next release.

Usage-based pricing only works if you can change it quickly. That means moving licensing logic out of your codebase and into a platform built for it.

 

Frequently asked questions

Is usage-based pricing the same as consumption-based pricing?
Yes. The terms are interchangeable, as is metered pricing. See our guide to
consumption-based licensing.

Can desktop software use usage-based pricing?
Yes. Use count and use time licenses work in desktop applications, and signed license tokens let licensing terms apply even when the application is offline.

What happens when a customer reaches their usage limit?
That depends on how you configure it. Further usage can be blocked until the customer renews or upgrades, or you can allow a set amount of overage above the purchased quantity and bill for it later. When a limit is reached, your application receives a clear response it can use to inform the user, so make sure customers can see their remaining balance before it runs out.

 

Price for usage without rebuilding your licensing

10Duke lets you define usage metrics, enforce or meter consumption, and combine usage-based licensing with subscription, feature-based or concurrent models, all from one platform. Book a demo to learn more.