> For the complete documentation index, see [llms.txt](https://docs.nalpeiron.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.nalpeiron.com/education-and-training/licensing-education/usage-billing-basics-ubb.md).

# Usage Billing Basics (UBB)

Learn how usage-based billing (UBB) works, what counts as usage, and how to combine consumption pricing with subscriptions using Zenmeter.

Usage-based billing charges customers for what they actually consume rather than a flat subscription fee, and this page breaks down the model, its common metrics, and how it fits alongside hybrid pricing strategies.

## **What is Usage-Based Billing, often called UBB?**

### **A Complete Guide to Consumption and Metered Pricing Models**

#### **Understanding Usage-Based Billing**

**Usage-based billing** is a pricing model where customers are charged according to how much of a product or service they actually consume. Rather than paying a fixed monthly subscription or purchasing a predefined number of seats, customers pay in direct proportion to measurable usage.

This model is also commonly referred to as:

* **Usage-based pricing**
* **Consumption-based billing**
* **Metered billing**
* **Utility pricing**
* **Pay-as-you-go pricing**

At its core, usage-based billing aligns price with value delivered.

If a customer uses more and receives more value, they pay more.

If they use less, they pay less.

This built-in scalability makes the model attractive to both fast-growing startups and enterprise buyers who want pricing that reflects operational growth.

{% hint style="info" %}

### Learn more about UBB/Usage-based billing and pricing

<https://nalpeiron.com/zenmeter/usage-based-pricing/>
{% endhint %}

***

### **Why Usage-Based Billing Is Gaining Popularity**

The growth of cloud computing, APIs, AI workloads, and digital infrastructure has accelerated demand for pricing models that scale dynamically.

Traditional subscription models often require customers to:

* Estimate future usage
* Overcommit to capacity
* Purchase unused seats
* Renegotiate contracts when scaling

Usage-based billing removes these constraints.

Instead of debating capacity forecasts, businesses can:

* Start small
* Scale naturally
* Pay for actual consumption
* Align costs with measurable outcomes

This flexibility is one reason **pure usage-based pricing models** are becoming increasingly common across SaaS, infrastructure, AI, fintech, data platforms, and enterprise software.

***

### **What Counts as “Usage”?**

“Usage” depends on the nature of the product and the value it delivers.

Common usage metrics include:

#### **Infrastructure-Based Metrics**

* API calls executed
* Compute hours consumed
* Data processed
* Storage used
* Bandwidth transferred

#### **Business Activity Metrics**

* Contacts reached
* Emails delivered
* Transactions processed
* CRM records enriched
* Reports generated

#### **Media and Event Metrics**

* Minutes of video processed
* Events tracked
* Sessions recorded
* Files converted

#### **AI and Modern Workload Metrics**

* Prompts submitted
* Tokens consumed
* Inference calls
* Model training cycles

The key principle is that usage represents measurable activity directly tied to customer value.

***

### **How Usage-Based Billing Aligns Pricing With Value**

One of the most powerful aspects of consumption-based billing is value alignment.

Instead of charging for access alone, companies charge for outcomes or activity.

This creates several advantages:

* Customers perceive pricing as fair
* Growth translates directly into revenue expansion
* ROI conversations become clearer
* Procurement friction decreases
* Pricing scales with business success

In contrast to rigid subscription tiers, usage-based billing adapts to real-world variability.

***

### **Usage-Based Billing Across SaaS and B2B Software**

Usage-based billing appears across multiple SaaS categories:

* Cloud infrastructure platforms
* API-first products
* AI platforms
* Data analytics solutions
* Marketing automation systems
* Developer tools
* Enterprise productivity software

It supports a range of go-to-market strategies:

* Freemium models
* Self-serve onboarding
* Credit-based pricing
* Enterprise minimum commitments
* Usage commitments with overage pricing
* Hybrid subscription + consumption models

However, successfully implementing usage-based billing requires more than invoicing logic.

It requires accurate, real-time tracking of customer activity.

***

### **The Importance of Real-Time Usage Tracking**

To ensure fair, transparent, and auditable billing, companies must:

* Track customer usage in real time
* Validate usage events accurately
* Prevent double-counting or missed events
* Provide customers with visibility dashboards
* Offer proactive threshold alerts
* Maintain audit logs

Without reliable tracking mechanisms and periodic validation, usage-based pricing can create mistrust or disputes.

This is especially critical in B2B environments where contracts, procurement policies, and compliance requirements demand accuracy.

***

### **Pure Usage-Based Pricing vs Hybrid Models**

Despite the rise of consumption pricing, usage-based billing is rarely implemented in isolation.

Most SaaS companies adopt **hybrid pricing models** that combine:

* Fixed subscription fees (for base platform access)
* Consumption-based charges (for scalable components)
* Minimum spend commitments
* Tiered pricing discounts
* Overage thresholds

Hybrid models balance:

* Flexibility for customers
* Predictability for revenue teams
* Transparency for finance
* Control for product teams

For example, a company may charge:

* A base subscription fee for platform access
* Additional usage charges for API calls
* Tiered discounts for higher consumption volumes
* Minimum annual commitments for enterprise accounts

This blended approach allows businesses to capture the benefits of usage-based billing while maintaining revenue stability.

***

### **Usage-Based Billing Is a Monetization Strategy, Not Just a Pricing Model**

While often discussed as a billing feature, usage-based pricing is fundamentally a strategic monetization decision.

It influences:

* Sales motion
* Customer acquisition strategy
* Expansion planning
* Revenue forecasting
* Product design
* Data architecture
* ERP integration
* Entitlement management

For simple SaaS businesses, usage billing can be implemented directly through billing systems.

For complex B2B environments — especially those involving ERP-driven contracts, offline deployments, hybrid monetization models, and enterprise compliance requirements — usage-based billing must be architected at the product level.

That means:

* Usage enforcement must align with entitlements
* Contract terms must flow from ERP systems
* Billing must receive validated usage records
* Customers must see real-time visibility

When built correctly, usage-based billing becomes a growth engine.

***

### Pricing vs. billing

"Usage-based pricing" and "usage-based billing" get used interchangeably, but they're not quite the same thing:

* Pricing is the cost structure: the metric you charge for, and the rates or tiers attached to it.
* Billing is the operational system that meters actual consumption, applies that structure, and turns the result into a charge.

Pricing defines the model; billing is what makes it run day to day. A common shape combines both: a fixed base rate plus a variable rate applied to usage, often called a hybrid or two-part charge.

***

### The four jobs of a UBB system

Whatever the pricing model, a working usage-based billing setup has to perform four distinct jobs:

1. Define the metric: decide what gets charged for, whether that's API calls, tokens, events, or seats.
2. Collect and reconcile usage: capture consumption accurately, without gaps or double-counting.
3. Track and rate usage: apply prices, tiers, caps, and credit balances to what was collected.
4. Bill the customer: turn the rated usage into an invoice and collect payment.

Platform vendors typically handle the first three jobs, metering, tracking, and rating usage in real time, while a separate commerce or billing vendor handles the fourth: producing the invoice and collecting payment.

***

### **Final Thoughts**

Usage-based billing is redefining how SaaS and B2B companies monetize software.

By charging customers based on actual consumption, businesses create:

* Fairer pricing
* Natural expansion revenue
* Better alignment with customer value
* Greater flexibility during growth cycles

But its success depends on:

* Accurate tracking
* Transparent reporting
* Clear usage definitions
* Scalable monetization architecture

In today’s enterprise landscape, usage-based billing is not just about metering activity.

It is about building a flexible, data-driven revenue model that grows with your customers.

***

### Explore Usage Billing Topics

[**Benefits of Usage-Based Billing**](https://docs.nalpeiron.com/education-and-training/licensing-education/usage-billing-basics/benefits-of-usage-based-billing)

Usage-based billing aligns price with measurable customer activity rather than fixed seats or subscription tiers. When implemented effectively, it can reduce purchasing friction, accelerate sales, generate organic expansion revenue, improve retention, and provide valuable insight into customer behavior.

[**Types of Usage-Based Pricing Models**](https://docs.nalpeiron.com/education-and-training/licensing-education/usage-billing-basics/types-of-usage-based-pricing-models)

Usage-based pricing can take several forms, including pay-as-you-go billing, prepaid credits, tiered usage pricing, minimum commitments, and hybrid subscription-and-usage models. The right structure balances customer flexibility with revenue predictability, transparency, and operational requirements.

[**Usage-Based Pricing: Pros and Cons**](https://docs.nalpeiron.com/education-and-training/licensing-education/usage-billing-basics/usage-based-pricing-pros-and-cons)

Usage-based pricing can align costs with customer value, reduce barriers to adoption, and support natural account expansion. However, it requires understandable value metrics, dependable metering, transparent reporting, manageable cost economics, and controls that prevent unpredictable customer bills.

[**Two Architectures for Usage-Based Billing**](https://docs.nalpeiron.com/education-and-training/licensing-education/usage-billing-basics/two-architectures-for-usage-based-billing)

Usage-based billing can use a billing-side architecture focused on metering, rating, and invoicing or a product-side architecture focused on real-time enforcement, entitlements, and billing-system integration. The appropriate approach depends on product complexity, deployment environments, customer contracts, and operational requirements.

[**Best Practices for Adopting Usage-Based Billing**](https://docs.nalpeiron.com/education-and-training/licensing-education/usage-billing-basics/best-practices-for-adopting-usage-based-billing)

Successful usage-based billing starts with a value-aligned usage metric and reliable infrastructure for collecting, validating, and reporting consumption data. Organizations should also provide transparent usage visibility, integrate relevant business systems, maintain auditability, and plan for operational change across product, sales, finance, and customer success teams.

[**Why Usage-Based Billing Is Taking Over SaaS—and What Most Companies Get Wrong**](https://docs.nalpeiron.com/education-and-training/licensing-education/usage-billing-basics/why-usage-based-billing-is-taking-over-saas-and-what-most-companies-get-wrong)

Usage-based billing is growing because customers increasingly want pricing that reflects the value they receive, while vendors benefit from consumption-driven expansion revenue. A common mistake is treating it only as an invoicing project instead of also addressing product enforcement, entitlements, data architecture, and customer transparency.

[**ERP-Driven Monetization: The Missing Layer in Enterprise Usage Billing**](https://docs.nalpeiron.com/education-and-training/licensing-education/usage-billing-basics/erp-driven-monetization-the-missing-layer-in-enterprise-usage-billing)

Enterprise contracts and commercial terms often originate in ERP systems, but those terms must also reach the product’s entitlement and usage controls. Connecting ERP data to a product-side monetization layer can automate provisioning, align access with contracts, produce validated usage records for downstream billing, and improve auditability.

[**Consumption Pricing vs. Subscription Pricing: A B2B Decision Framework**](https://docs.nalpeiron.com/education-and-training/licensing-education/usage-billing-basics/consumption-pricing-vs-subscription-pricing-a-b2b-decision-framework)

Subscription pricing offers simplicity and predictable recurring revenue, while consumption pricing connects revenue more directly to customer usage and growth. Many B2B companies use a hybrid model that combines a base subscription, usage charges, minimum commitments, overage rules, and volume discounts.

[**How to Implement Usage-Based Billing Without Breaking Your Product Architecture**](https://docs.nalpeiron.com/education-and-training/licensing-education/usage-billing-basics/how-to-implement-usage-based-billing-without-breaking-your-product-architecture)

A scalable implementation separates product access and usage enforcement from invoicing. It centralizes entitlement logic, defines auditable usage metrics, integrates commercial terms, gives customers real-time usage visibility, and sends validated, rated usage to downstream billing systems.

[**Usage-Based Billing Frequently Asked Questions**](https://docs.nalpeiron.com/education-and-training/licensing-education/usage-billing-basics/usage-based-billing-frequently-asked-questions-faqs)

These frequently asked questions address value-aligned usage metrics, hybrid pricing, customer bill shock, usage visibility, spending controls, forecasting, and other practical implementation concerns. The guidance helps businesses balance flexible consumption pricing with transparency and predictability.

### Here are some other useful resources

**Go here to learn more about tools to use for usage-based billing (UBB):**

[The Dummies Guide to Usage-Based Billing](https://nalpeiron.com/blog/usage-based-billing-pricing-guide/)

* [Zenmeter - a tool to implement UBB](https://nalpeiron.com/zenmeter/)
* [UBB Monetization Infrastructure](https://nalpeiron.com/platform/monetization-infrastructure/)
* [Usage-Based Pricing](https://nalpeiron.com/zenmeter/usage-based-pricing/)

{% hint style="info" %}

### Learn more about UBB/Usage-based billing and pricing

<https://nalpeiron.com/zenmeter/usage-based-pricing/>
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.nalpeiron.com/education-and-training/licensing-education/usage-billing-basics-ubb.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
