Most pricing conversations start with the wrong question. For example, organizations may debate whether to charge $99 or $149 per month, whether to offer annual discounts, or to add a free tier. The more important question, and one that rarely gets the attention it deserves, is if a fixed recurring charge is the right structure at all.
Subscription billing and usage-based billing aren’t just different business models. They’re different bets about how value is created in your business. Getting that choice right has long-term consequences for revenue growth, customer retention, financial reporting, and the infrastructure you’ll need to support it. Getting it wrong is expensive to fix after contracts are signed and customers are live.
This guide covers how the two models, subscription and usage-based billing, actually work, where each one fits, and how to think through the decision.
How Subscription Billing Works
Subscription billing is when you charge a fixed amount on a fixed schedule such as monthly, quarterly, or annually, regardless of how much the customer uses the product. The customer knows exactly what they’ll pay. You know exactly what you’ll get for recurring revenue.
That predictability is the model’s main advantage. Monthly recurring revenue compounds reliably and sales forecasting is straightforward. This benefits finance teams because they can forecast cash flow without modeling customer behavior.
The model works best for products where value doesn’t vary much with consumption. For example, a project management tool, a CRM, and a document editing platform all deliver roughly consistent value across customers regardless of how often they log in, which makes a flat fee feel fair to both sides.
There are risks, however. Customers paying a flat fee for a product they underuse will eventually question if the spend is justified. That’s where subscription churn actually starts, not because the product is bad, but because the price stopped feeling proportional to the value received. On the other hand, customers who use the product heavily pay the same as light users, which means you’re leaving revenue on the table from your most engaged accounts.
Related: What is subscription billing?
How Usage-Based Billing Works
Usage-based billing charges based on actual consumption. The usage metric can vary by product, such as API calls, tokens, compute hours, transactions processed, data stored, and minutes used, but the principle is the same in that the bill reflects what the customer actually used.
The commercial thinking with usage-based billing is fairly straightforward. For example, a startup processing 10,000 API calls pays less than an enterprise processing 10 billion. The cost increases with value, which makes it easier for a new customer to say yes at the start and removes the most common reason customers leave, which is paying for things they don’t use.
The operational side of usage-based models is a bit harder. Variable revenue takes more work to forecast than fixed revenue. Usage data needs to be captured at the event level, validated, rated against pricing rules, and turned into an invoice. This process requires billing infrastructure most subscription platforms weren’t built to handle. In addition, revenue recognition under ASC 606 and IFRS 15 is more complex for variable consumption than for fixed fees. Customers without real-time visibility into their usage will get surprised by their invoices, and bill shock is one of the most reliable causes of churn in usage-based products.
These aren’t reasons to avoid usage-based billing. They’re reasons to implement it with the right solution.
Related: What is usage-based billing? | Usage-based billing software guide
Where Revenue Growth Actually Comes From
The practical difference between the two models isn’t just about the pricing structure. It’s also about where revenue growth comes from.
With subscription billing, revenue growth requires a sales motion. You can either acquire more customers or upsell existing ones to a higher tier or more seats. When a customer’s business grows and they get more value from your product, that doesn’t show up in your revenue unless someone actively captures it in sales.
With usage-based billing, your revenue grows with the customer’s success. For example, a customer who doubles their usage generates roughly twice the revenue without a new sale or a contract renewal. Net revenue retention above 100%, meaning existing customers spend more this year than last year, becomes easier to achieve. In fact, the best usage-based businesses sustain NRR above 120%.
That also changes how customer acquisition works. Without a large upfront commitment, it’s common for deals to move faster. A customer can start small, prove value, and expand, which lowers friction and compresses sales cycles, particularly for enterprise deals where procurement scrutiny scales with contract size.
Subscription vs. Usage-Based: At a Glance
These two models are often described as opposites, but most enterprise companies end up using both.
| Subscription | Usage-based | |
|---|---|---|
Charge structure |
Fixed amount per period | Variable — based on consumption |
Revenue predictability |
High — stable MRR | Variable; predictable at scale with the right analytics |
Expansion revenue |
Requires a separate upsell motion | Grows automatically with usage |
Acquisition friction |
Higher upfront commitment | Lower — customers pay for what they use |
Churn Risk |
Underutilization such as “we don’t use it enough” | Bill shock if no real-time usage visibility is offered |
Billing Infrastructure |
Relatively simple | Requires mediation, rating, event ingestion |
Revenue Recognition |
Straightforward under ASC 606 | More complex with variable consideration |
Best fit |
Stable, predictable products | Product where value varies with consumption |
When Subscription Is the Right Model
Subscription is the better fit when the value your product delivers doesn’t vary much with how intensively customers use it. If a customer logging in once a week is getting roughly the same value as one logging in ten times a day, a flat fee is the honest pricing structure.
It also fits when customers prioritize predictability. For example, a CFO approving a $50,000 annual software contract knows exactly what the company will spend. That certainty has real value, especially for enterprise buyers with fixed budget cycles. Usage-based billing introduces variability that finance teams have to model and manage, and some buyers will pay a premium to avoid it.
Subscription is also the lower-infrastructure choice. There’s no mediation layer to build, no event ingestion to manage, and no per-event rating engine to configure. For early-stage teams focused on product, a clean subscription model is a reasonable starting point.
The signal that a subscription model is right is if your customers’ value from the product doesn’t track with how much they use it.
When Usage-Based Billing Is the Right Model
Usage-based billing fits when value scales with consumption. If the customer is getting more value from your product, they naturally use more of it, so pricing that grows with usage is simply more accurate than pricing that doesn’t.
It also fits when your customer base has wide variation in consumption. Charging the same flat rate to a startup processing a thousand events a month and an enterprise processing a billion is pricing that ignores a 1,000x difference in value delivered. Usage-based billing solves this issue without separate SKUs, custom contracts, or manual negotiation for every account.
The AI industry has made this dynamic fairly common. Every company using a foundation model API has a billing challenge that subscription systems can’t handle, like pricing based on tokens with different input and output rates, specific rates for different model versions, and frequent usage events that need to be tracked and billed all the time. A flat monthly fee doesn’t map to this, but usage-based billing does.
The signal that usage-based billing is right is when your most valuable customers are also your heaviest users, and your current pricing model doesn’t capture the full value they receive.
Related: Consumption-based pricing guide
Why Most Enterprise Companies End Up Running Both
The subscription vs. usage-based decision is often framed as either/or. In reality, most mature enterprise businesses run a hybrid model that combines elements of both.
The hybrid typically has a base subscription that provides a revenue floor and gives customers a predictable monthly cost, plus usage-based components that capture expansion as customers grow. The subscription base keeps revenue predictable for finance and removes the ‘we paid but didn’t use it’ churn trigger. The usage component means revenue grows automatically with customer success without requiring a new sales motion.
This isn’t a compromise, however. It’s the model OpenAI, Snowflake, Twilio, and most major AI and infrastructure companies have converged on because it solves for what both sides of the invoice actually care about, which is predictability for the seller, fairness for the buyer, and expansion revenue that grows automatically.
One timing point worth flagging is that retrofitting a hybrid model onto a business that started with pure subscription is significantly harder than building for it from the start. Adding usage-based components to existing subscription contracts requires renegotiation, new billing infrastructure, and changes to how revenue is recognized. The teams that avoid this problem think through the hybrid architecture before the first enterprise contract is signed.
Related: BillingPlatform hybrid billing capabilities
The Infrastructure Question That Usually Gets Ignored
The business model decision and the infrastructure decision tend to get treated separately. They shouldn’t be.
Subscription billing runs on relatively simple infrastructure. Usage-based billing requires event ingestion, mediation, rating, and revenue recognition that work together at whatever volume your product generates. Hybrid models require all of that simultaneously, with subscription and usage components consolidated into a single invoice.
The billing platform you select needs to support the model you’re building toward, not just the one you have today. A platform that handles subscriptions cleanly but requires engineering for every usage-based pricing change will become a bottleneck the moment you try to iterate, and most companies iterate on pricing at least once in the first year after launch.
BillingPlatform handles subscription, usage-based, and hybrid models natively in a single system. Finance teams configure pricing through a visual interface without involving developers or costly professional services, and revenue recognition is built into the billing workflow.
For a full breakdown of platform requirements, see the Usage-Based Billing: The Definitive Enterprise Guide.
To see how BillingPlatform handles it, visit the usage-based billing overview page or request a demo.
Additional resources
