Usage-based billing
DEFINITION
Usage-based billing charges customers based on how much of a product or service they actually consume, rather than a fixed amount agreed to in advance.
RELATED TERMS
Usage-based billing charges customers based on how much of a product or service they actually consume, rather than a fixed amount agreed to in advance.
It is different from quantity-based pricing, even though the two often get confused. With quantity-based pricing, a customer commits to a set amount upfront and is billed for that quantity at the start of the billing cycle, no matter how much they end up using. With usage-based billing, the customer is billed for what they actually consumed, measured against a specific unit such as API calls, gigabytes of storage, transactions processed, or another trackable metric.
Usage-based billing rarely stands entirely on its own. Many subscription businesses combine it with a fixed base fee in a hybrid model: a predictable platform charge covers the baseline, and usage charges scale with how much a customer uses the product above that baseline. Recurly does allow a $0 base plan fee for a fully usage-based plan, but hybrid remains the more common setup.
Why it matters
Usage-based billing lines up what a customer pays with the value they actually receive, which reduces the friction and resentment that come from paying for capacity that goes unused. It also gives a business a pricing model that scales with customer growth. As a customer's usage increases, so does the revenue from that account, without a manual plan upgrade.
The tradeoff is predictability. Revenue under a pure usage-based model varies more than a fixed subscription fee, and a business needs accurate, real-time tracking of the metric it bills against, or customers won't trust the invoice. This is why API access to log and retrieve usage records in near real time matters so much for any usage-based billing implementation.
Recurly's usage record API lets a merchant log usage against a subscription add-on, with an amount that can be positive, negative, or zero and a defined measured unit tied to that add-on. Each add-on also has a calculation method — cumulative, which sums every usage record logged in the period, or last recorded, which bills only the most recent record — letting merchants bill both consumption metrics and point-in-time metrics like seat count.
Each usage record carries separate timestamps for when the usage actually happened and when it was recorded in the merchant's own system, and the actual usage date is what determines which billing period, and which revenue recognition period, the usage is billed under.
How to use
Implementing usage-based billing generally follows this sequence:
Choose the metric that best represents the value a customer receives, such as API calls, storage consumed, or transactions processed.
Configure the pricing model for that metric: a flat per-unit rate, or a tiered, stairstep, or volume-based structure where the rate changes based on how much is consumed.
Track usage as it happens, recording each usage event against the customer's account or subscription.
Distinguish between when usage was recorded in your system and when it actually occurred, since the actual usage date typically determines which billing period and revenue recognition period the charge belongs to.
Aggregate usage over the billing period and generate an invoice that reflects the total.
Give customers visibility into their usage before the invoice arrives, so charges aren't a surprise.
Benefits and examples
Revenue scales with customer value. As a customer's usage grows, so does what they pay, without a manual upgrade conversation.
The barrier to entry is lower. Customers can start small and pay only for what they use, which reduces hesitation at signup compared with committing to a larger fixed plan.
It fits infrastructure and API products. Cloud storage, messaging, and API platforms map cleanly to a countable usage metric, which makes usage-based billing a natural default for that category.
Pricing stays flexible on a single metric. Recurly supports multiple usage-based pricing structures on the same add-on, including flat, tiered, stairstep, and volume pricing models, so a merchant isn't limited to a single flat per-unit rate.
For an example of a hybrid model, a B2B software platform might charge a fixed monthly fee for core access plus a per-unit charge for a specific high-volume action, such as every campaign sent or every thousand records processed. The base subscription stays predictable while heavy usage still generates proportional revenue.
Frequently asked questions
What's the difference between usage-based billing and quantity-based pricing? Quantity-based pricing bills a customer in advance for a committed amount, regardless of how much they use. Usage-based billing bills based on what a customer actually consumed during the period, measured against a specific metric.
Does usage-based billing work well as a standalone pricing model? It can, but many subscription businesses combine it with a fixed base fee in a hybrid model. That gives customers a predictable baseline cost while still letting the business capture more revenue from high-usage accounts.
What kind of businesses use usage-based billing? It's common for infrastructure, API, and cloud platform products, such as messaging, storage, or compute services, where usage naturally maps to a countable unit. It also shows up in media and publishing for microtransaction-style charges.
How does usage-based billing affect revenue recognition? Because the amount owed depends on when usage actually occurred, not just when it was recorded in a system, the timing of usage events matters for determining which period the associated revenue belongs to.
What's the risk of usage-based billing? Revenue becomes less predictable than with a fixed subscription fee, and the business depends on accurate, timely usage tracking. If customers don't trust how their usage was measured, billing disputes and chargebacks become more likely.
