Usage-based billing is a pricing strategy where customers are charged based on their consumption of a product or service. This model, also known as metered billing or pay-as-you-go, directly links the cost of a service to the value a customer receives, moving away from traditional flat-fee subscriptions. It’s a fundamental shift that is redefining how modern software and services are sold and consumed.

Usage-based billing is a model that charges customers based on how much they use a product. Think of it like your home’s electricity bill: the more power you use, the higher your bill. In the software world, this “usage” could be anything from the number of API calls made, gigabytes of data stored, or hours of video streamed.

This approach has become increasingly popular for SaaS, infrastructure, and platform-as-a-service (PaaS) companies because it aligns the company’s revenue directly with customer success. As customers find more value and increase their usage, revenue grows organically.

Implementing usage-based billing involves a few core mechanical steps. First you must track usage, then aggregate the data, apply the pricing rules, and finally, send a bill.

Here’s a breakdown of the typical lifecycle:

• Track: The system must monitor and record every instance of a billable action. This requires robust, real-time event tracking.
• Aggregate: At the end of a billing period, all tracked usage data for a customer is collected and summed up.
• Rate: The aggregated total is multiplied by the pricing model’s rates. This could be a simple per-unit cost, a tiered structure, or a more complex volumetric model.
• Bill: An invoice is generated that clearly itemizes the usage and the corresponding charges, often alongside any fixed subscription fees.

This cycle requires a reliable system to ensure accuracy and avoid billing disputes.

The foundation of a successful usage-based model is the metric you choose to bill on. This metric should be easy for customers to understand, directly related to the value they receive, and predictable enough for them to manage their costs.

Select a metric that is simple, transparent, and grows with your customer’s success. Your goal is to find a fair and scalable proxy for value.

• Technical Metrics: These are tied to infrastructure or resource consumption. They are often straightforward to measure but can sometimes be difficult for non-technical customers to understand. Examples include:
  • Gigabytes of storage
  • CPU hours
  • API requests
  • Bandwidth used
• Transactional Metrics: These count business-level events or actions performed within your application. They are often a better proxy for value than purely technical metrics.
  • Transactions processed
  • Messages sent
  • Contacts added
  • Reports generated
• Value-based Metrics: This is the ideal, though often the most complex to implement. It ties billing directly to the business outcome the customer achieves.
  • Revenue generated
  • Ad impressions
  • Hours of video transcribed

A good approach is to start with a simple technical or transactional metric and evolve as you gain a deeper understanding of how customers derive value from your product.

Once you have your metric, you need a model to calculate the bill. The model determines how the price per unit changes (or doesn’t) as usage increases.

A poorly implemented usage-based model can cause more harm than good, leading to customer confusion, frustration, and churn. Here are some common pitfalls to watch out for.

One of the biggest risks is the “surprise bill,” where a customer’s usage unexpectedly spikes, resulting in a much higher invoice than they anticipated.

• Poor communication: Customers need to know exactly what they’re being billed for and how to track their usage. A real-time dashboard is essential.
• Choosing the wrong metric: Billing for something that doesn’t align with value can feel unfair. For example, charging per seat for a tool that only a few people use, but which provides company-wide value, is a classic mismatch.
• Lack of predictability: Without tools to forecast and control costs, customers can become anxious. Implement features like budget alerts, spending caps, or simulators to help them manage their spend.
• Overly complex models: If a customer needs a spreadsheet to understand their bill, your model is too complicated. Simplicity builds trust. Stick to one or two billable metrics and a straightforward model.

Kinde is an all-in-one platform for authentication, user management, and billing, designed to help you launch and scale your SaaS product. It provides the tools to implement flexible billing models without getting bogged down in the complexity.

With Kinde, you can easily combine fixed-price subscriptions with metered, usage-based components. Our platform handles the complexities of tracking usage, aggregating data, and generating accurate invoices, allowing you to experiment with and implement the pricing model that best fits your business.

Kinde lets you define your pricing, track usage through a simple API, and automatically handles the billing cycle, so you can focus on building your product, not your billing infrastructure.

• The Kinde billing model
• View plans and pricing
• Upgrade or downgrade subscriptions