Table of Content

Table of Content

Hybrid Pricing: The Complete Guide for SaaS and AI Companies (2026)

Hybrid Pricing: The Complete Guide for SaaS and AI Companies (2026)

Hybrid Pricing: The Complete Guide for SaaS and AI Companies (2026)

Hybrid Pricing: The Complete Guide for SaaS and AI Companies (2026)

• 28 min read

• 28 min read

Ayush Parchure

Content Writing Intern, Flexprice

Hybrid pricing is a billing model that combines a fixed recurring fee, typically a platform or base subscription, with variable charges that scale based on actual product usage. It gives SaaS and AI companies the revenue predictability of subscriptions alongside the expansion upside of usage-based billing, which is why it has become the fastest-growing pricing model in software: over 60% of SaaS companies now use some form of hybrid pricing, up from under 30% in 2021.

The shift is especially pronounced in AI, where consumption is inherently unpredictable. API calls, token usage, compute minutes, and agent executions don't map to seat counts but customers still want a predictable monthly baseline. Hybrid pricing solves both sides of that equation.

This is the most complete guide to hybrid pricing on the internet. At Flexprice, we build the monetization infrastructure that AI-native companies use to ship hybrid billing in hours, not quarters, and we've distilled everything we know into this page.

TL;DR

  • Hybrid pricing = subscription + usage + credits combined into one flexible billing model

  • Flat pricing breaks in AI because costs scale with every token, API call, and inference run

  • Hybrid gives predictable base revenue while capturing upside as customer usage grows

  • It solves the core tradeoff: fairness for customers + predictability for the business

  • AI makes per-seat pricing inefficient by reducing headcount but increasing product usage

  • Top companies like OpenAI, Vercel, and Cursor already use hybrid as their default model

  • Revenue scales automatically with usage without constant plan upgrades or sales touchpoints

  • Hybrid improves margins by aligning pricing directly with infrastructure and AI costs

  • Core building blocks: base fee, usage metering, credits/tokens, and add-on tiers

  • Multiple models exist (subscription + usage, credits, tiered + overage, outcome-based)

  • Choosing the right value metric is critical, like tokens, API calls, tasks, or outcomes

  • Success depends on a billing infrastructure that supports real-time metering, credits, and flexible pricing changes 

What is hybrid pricing?

Hybrid pricing is a billing model that combines subscription, usage-based, and credit-based pricing into a single plan. It gives businesses the flexibility to charge customers a flat recurring fee for baseline access while billing additionally for actual product or service consumption.

Think of it like your phone bill: you pay a fixed monthly rate for your plan, but when you exceed your limit, you're charged based on how much you use. In SaaS and AI, the same logic applies: a platform fee covers core access, while API calls, token usage, or compute minutes are billed on top.

How it differs from pure subscription and pure usage models

When you hear about hybrid pricing, the one question that comes to your mind is how exactly it differs from pure subscription or usage models. Most pricing models force a trade-off. Hybrid pricing exists because neither extreme really works on its own.

  • Flat fee: Predictable revenue, easy to sell, simple to budget. But it breaks when usage varies; heavy users get undercharged, light users feel overcharged.

  • Pay-as-you-go: Customers pay for exactly what they use, which feels fair. But revenue becomes volatile, and forecasting gets messy, especially for finance teams.

Hybrid pricing sits in the middle. You get a stable base from subscriptions, while usage-based components scale revenue with actual value delivered.

  • Predictability for the business

  • Fairness for the customer

  • Flexibility as usage grows

It’s not just a compromise, it’s a way to align pricing with how modern products are actually consumed.

The core building blocks of a hybrid model

Hybrid pricing isn’t one fixed structure. It’s a combination of a few core components that you can mix depending on your product. Here are some of the core building blocks that structure the pillar of hybrid pricing:

  • Base/platform fee: A fixed recurring charge that runs monthly or annually. It covers access, core features, and sets a predictable revenue floor.

  • Usage-based charges: Variable fees tied to consumption, which are API calls, minutes, seats, data processed, etc. This is the place where your revenue scales with value.

  • Credits/tokens: Prepaid units that customers can spend over time. Useful for smooth billing, offering discounts upfront, or giving customers more control over spend.

  • Add-on tiers: An optional upgrade that includes premium features like higher limits and priority support. It helps you monetize advanced use cases without complicating the base plan.

The real power comes from how you combine these:

  • Base fee + usage, which is the most common pricing method used for AI and SaaS

  • Credits + overage that is good for predictable yet flexible billing

  • Add-ons layered on top that help to capture expansion revenue cleanly

A good hybrid model doesn’t feel complex to the customer. It feels intuitive to pay a base to get started, then scale as you grow.

Why hybrid pricing became the default in 2026

Ask a SaaS founder in 2023 how they priced their product, and the answer was almost always flat-rate subscriptions or per-seat licensing. Simple, predictable, easy to slap on a pricing page. But somewhere between the explosion of AI-native products and the collapse of seat-based economics, hybrid pricing stopped being an experiment and became the only model that actually works.

The market shift: from 27% to 41% in 12 Months

According to Growth Unhinged's 2025 State of B2B Monetization report, hybrid pricing adoption surged from 27% to 41% in just twelve months. During the same window, seat-based pricing dropped from 21% to 15%, and flat-fee subscriptions fell from 29% to 22%. Growth unhinged Chargebee's 2025 report projects hybrid adoption hitting 61% by the end of 2026. Companies that are clinging to single-dimension pricing are paying for it:

  • 2.3x higher churn among seat-only models versus hybrid or usage-based billing 

  • 40% lower gross margins on AI products priced exclusively per seat 

  • 21% median growth rate for hybrid billing companies, outperforming both pure subscription and pure usage-based approaches

If you are still running a single pricing dimension in 2026, you are actively losing customers to competitors who price the way modern buyers expect to buy.

Why AI broke traditional pricing models

The shift to hybrid billing did not happen because VCs published thought pieces. It happened because AI fundamentally changed the cost structure of software, and traditional models could not absorb it.

Every AI feature carries a real, variable infrastructure cost: tokens consumed, GPU cycles burned, inference calls hitting your cloud bill. That creates three failure modes that make flat and per-seat pricing untenable:

  • Variable costs with fixed revenue. Flat subscription-based billing means margins erode with every heavy user. One enterprise customer running 50,000 API calls a day could cost more to serve than they pay, and your billing system was never designed to flag that.

  • Per-seat pricing punishes AI efficiency. AI promises to replace manual work. If your product reduces headcount, charging per seat cannibalizes itself. Enterprise billing teams see this immediately, and it stalls deals.

  • Tiered pricing creates misalignment. One customer uses 200 inference calls a month, another on the same plan uses 200,000. The first feels overcharged, the second destroys your margins. Credit-based billing and usage metering solve this, but only if your system supports hybrid models natively.

This is exactly why IDC forecasts that 70% of software vendors will refactor pricing away from pure per-seat models by 2028.

What top SaaS and AI companies are doing right now

The companies setting the standard are building modular hybrid billing architectures where a base subscription provides predictability and a usage or credit layer captures variable value:

  • OpenAI: ChatGPT subscriptions (Free to $200/month) with usage limits per tier, token-based usage-based billing on the API as a separate product, and custom enterprise pricing with unlimited model access and dedicated infrastructure

  • Vercel: $20/month base per seat plus metered bandwidth, serverless compute, and edge requests, with a $20 credit buffer smoothing the fixed-to-variable transition

  • Cursor: Monthly subscription with credit pools tied to actual model API costs, where premium model selection deducts from credits

  • Anthropic: Pro at $20/month and Max up to $200/month for individuals, Team seats from $25/seat/month, and self-serve Enterprise at $20/seat with API-rate usage billed separately

Key benefits of hybrid pricing for SaaS and AI

There is a reason nearly half of all SaaS companies have already made the switch to hybrid pricing. It is not a trend. It is a response to a fundamental shift in how software delivers value, how customers expect to pay for it, and how AI is rewriting the economics of both. Here is what changes when you move beyond a single pricing model.

Revenue scales automatically with customer growth

Think about what happens with flat subscription pricing. A customer signs up at $99 a month. They love your product. They triple their usage, invite their entire team, and push API calls through the roof. And you still collect $99.

Hybrid pricing fixes that by design. The subscription gives you a stable baseline, but the usage layer grows in lockstep with how much value each customer pulls from your product. When they process more documents, run more queries, or trigger more automations, the bill reflects it. Revenue expands without a sales rep picking up the phone, without a renewal negotiation, and without a pricing page redesign.

One of the hardest tradeoffs in pricing is serving a startup on a tight budget and an enterprise with deep pockets using the same product. Flat pricing forces you to pick a lane. The price is too high, and you lose the long tail of small customers who could become your biggest accounts in two years. The price is too low, and you leave enterprise money on the table.

Hybrid pricing removes the tradeoff entirely. The structure works like this:

  • For smaller customers: A low base fee (or even a free tier) gets them in the door. They pay for what they use, nothing more. The barrier to trying your product drops to nearly zero.

  • For enterprise buyers: Committed spend tiers, volume discounts, and annual contracts give them the predictability their procurement teams demand, while usage components still capture the full scope of their consumption.

Same model, two very different customer experiences. Both feel like the pricing was built for them.

AI features become profitable instead of a cost center

This one matters more in 2026 than it ever has. If your product uses large language models, runs inference on GPUs, or orchestrates AI agents, you know the reality: every API call, every token processed, every agent action costs you real money. Traditional SaaS margins of 80 to 90 percent do not apply here. AI products often operate at 50 to 60 percent gross margins, and that gap can swallow your business if the pricing does not account for it.

Hybrid pricing turns this around. Instead of absorbing variable AI costs inside a flat subscription and hoping the math works out, you meter every token, every compute cycle, every agent task, and bill accordingly. The subscription covers platform access and core features. The usage layer covers the actual cost of delivering AI to each customer. Suddenly, your most active users (the ones consuming the most resources) are also your most profitable accounts, not your most expensive ones.

Reduced churn and higher net revenue retention

Churn often has nothing to do with your product being bad. It happens when customers feel the price does not match the value they receive. Flat pricing creates two types of unhappy customers simultaneously: light users who feel they are overpaying for features they barely touch, and power users whose heavy consumption quietly erodes your margins. In contrast, they feel like they are getting a steal.

Hybrid pricing aligns the bill with reality. Customers who use less pay less, so they never hit that this isn't worth it moment of renewal. Customers who use more pay more, but they also see more value, which makes the higher bill feel earned rather than arbitrary. The result is lower churn across the board and a revenue base that compounds over time instead of leaking.

Types of hybrid pricing models

Not all hybrid models are built the same. The right structure depends on what you sell, who you sell to, and what metric best captures the value your product creates. Below are the five most common configurations, each suited to a different type of business. Most successful companies start with one and evolve over time, so think of these less as rigid categories and more as starting points.

Subscription + usage-based

This is the model most SaaS and AI companies land on first, and for good reason. It is the simplest version of hybrid pricing to understand, sell, and operate.

The customer pays a recurring subscription fee (monthly or annual) for platform access and a set of core features. On top of that, they pay per-unit charges based on actual consumption. The usage metric varies by product: API calls for developer tools, tokens processed for AI platforms, messages sent for communication software, or gigabytes stored for data products.

Why it works: 

The subscription provides revenue predictability for your finance team. The usage component captures the natural expansion as customers scale. It is the closest thing to a "default" hybrid model, and platforms like Flexprice make it straightforward to configure by combining subscription invoicing with real-time event metering on a single plan.

This plan is best for: 

  • API-first companies

  • Developer tools

  • Data platforms

  • Any product where consumption naturally varies across customers.

Subscription + credit/token system

Instead of billing per unit after the fact, this model gives customers a monthly credit or token allowance bundled into their subscription. They spend those credits as they use the product. If they run out before the billing cycle ends, they either buy more credits or get charged per-unit for the overage.

This is the model that has taken over the AI industry. OpenAI, Anthropic, and dozens of AI-native startups use it because it gives customers a sense of budget control while still allowing flexible consumption. The psychology matters here: customers feel like they are "spending" from a balance rather than racking up an unpredictable bill.

What makes it tick: A robust wallet and credit system that tracks balances in real time, handles auto top-ups, manages expiration rules, and deducts usage accurately across multiple dimensions. Flexprice, for instance, supports prepaid and promotional credits with configurable conversion rates, so you can define your own unit (like "AI credits") and map it to real currency.

This plan is best for:

  • AI platforms

  • LLM-based products

  • Any product where customers want visibility and cost control.

Tiered subscription + overage charges

This is the "pick your plan" model with a safety valve. Customers choose a tier (Starter, Pro, Enterprise) that comes with a defined set of features and a usage allowance. As long as they stay within their tier's limits, the bill is predictable. If they exceed those limits, overage charges kick in on a per-unit basis.

The beauty of this model is familiarity. Customers already understand tiered pricing from personal experience (think mobile phone plans). Adding overage charges on top means you never have to turn away a customer who outgrows their tier mid-cycle. They simply pay for the extra usage until they are ready to upgrade.

It is best suited for: Products with clear feature differentiation across tiers and predictable usage patterns that occasionally spike.

Platform fee + outcome-based pricing

This is the frontier of hybrid pricing, and it is where things get genuinely interesting for AI companies. Instead of charging for inputs like API calls, tokens, and compute time, you charge for outcomes like tickets resolved, leads generated, documents processed, revenue influenced, and tasks completed.

The customer pays a flat platform fee for access. On top of that, they pay based on measurable business results the product delivers. An AI customer support agent, for example, might cost $200/month for platform access plus $2 per ticket it resolves autonomously. The customer only pays more when the product delivers more tangible value.

Why this is gaining traction: As AI agents become capable of performing entire workflows independently, charging per seat or per API call feels increasingly disconnected from the value being created. Outcome-based pricing ties the bill directly to ROI, which makes it the easiest model to justify to budget holders.

It is best suited for: AI agents, automation platforms, and any product where the output is a measurable business result rather than raw compute.

Freemium + pay-as-you-go

The product-led growth favorite. You offer a genuinely useful free tier with real functionality, but capped usage. Once a customer hits the limit or needs advanced capabilities, usage-based charges activate. There is no upgrade wall that is forcing them into a paid plan. They simply start paying for what they consume beyond the free allowance.

This model works brilliantly for bottom-up adoption, where individual developers or small teams discover the product, fall in love with it, and gradually ramp up usage until the account becomes a meaningful revenue source. The key is making the free tier generous enough to demonstrate value but constrained enough that growing teams naturally cross into paid territory.

The numbers speak for themselves: Companies using freemium with usage-based expansion report significantly higher conversion rates from free to paid compared to traditional free trial models, because the transition feels gradual rather than binary. 

It is best fit for: developer tools, PLG SaaS, collaboration platforms, and any product where individual adoption leads to team-wide expansion.

Hybrid pricing for AI products: what's different

If you have spent any time building a SaaS product in the last decade, you have gotten comfortable with a simple truth: software margins are incredible. The AI has rewritten the economics, and pricing models built for the old world are starting to crack.

Why AI changes everything

Every prompt processed, every inference run, every agent task burns through GPU compute and token processing that shows up on your cloud bill.

When COGS is near zero, you can afford to be lazy about pricing. Charge a flat $99 per month, and even if some customers use ten times more than others, the margin absorbs it. When COGS scales with usage, that flat fee becomes a ticking time bomb. Your heaviest users quietly become the accounts that cost you the most to serve.

Hybrid pricing exists in the AI era because it is the only model that ties revenue to the actual cost of delivery. The subscription covers fixed costs. The usage layer covers variable AI costs. Together, they keep the math honest as you scale.

Pricing AI agents and autonomous systems

AI agents add another layer of complexity. An agent does not just respond to a query. It performs work: researching leads, resolving support tickets, generating reports, writing code, and orchestrating multi-step workflows. In many cases, a single AI agent replaces tasks that previously required a full-time employee.

Charging per seat for a product that eliminates the need for seats is a contradiction that customers notice quickly. Instead, the pricing models emerging for agentic AI fall into three categories:

  1. Task-based pricing. The customer pays per completed task. An AI agent that resolves support tickets might cost $1.50 per resolution. An agent that processes invoices might cost $0.50 per document. The customer pays only when the agent delivers a tangible output.

  2. Per-action fees layered on a platform subscription. The customer pays a monthly platform fee for access, configuration, and a base allocation of agent actions. Beyond that allocation, each additional action (API call, workflow execution, document generation) is billed at a per-unit rate.

  3. Outcome-based pricing. The most ambitious model, where the bill is tied to measurable business results. Revenue influenced, time saved, leads qualified, deals closed. This works when the outcomes are clearly attributable, and both sides agree on the measurement.

Token and GPU-based metering

Unlike traditional SaaS, where seats or users are the default metric, AI products generate dozens of potential usage dimensions: input tokens, output tokens, GPU-seconds, model type, context window size, storage consumed, and more.

The key is choosing a metric that is both technically accurate and intuitively understandable to the customer, like:

  • Tokens processed work for LLM products because it maps directly to cost.

  • API calls work for developer tools

  • Documents processed or tasks completed work for vertical AI applications 

Once you have the metric, the requirement is a metering system that ingests events at high volume, aggregates them in real time, and connects seamlessly to billing.

The per-seat paradox in AI

This paradox deserves its own spotlight because it is the single most common trigger for AI companies searching for hybrid pricing.

Imagine a customer service platform that charges $50 per agent seat. The company ships an AI copilot that helps each human agent handle three times more tickets. They reduce their team from 30 agents to 12 and get the same throughput. Their bill drops from $1,500 to $600 per month. The product delivered enormous value, and the vendor's revenue was cut by 60 percent.

Now imagine the same product with hybrid pricing: $200 per month for the platform plus $0.10 per AI-assisted ticket resolution. The customer reduces their team, their seat cost drops, but the AI resolution volume increases. The bill might land at $200 plus $800 in usage, totaling $1,000. The customer saves money compared to the old model. The vendor earns more because pricing reflects value delivered rather than headcount deployed.

This is not a hypothetical scenario. It is happening across every SaaS vertical where AI is automating human workflows. And it is why companies that cling to per-seat pricing in the AI era are watching their best feature become their biggest revenue liability.

How to design your hybrid pricing model

Knowing hybrid pricing is the right approach is one thing. Actually designing it is where most companies stall. The good news is that it follows a repeatable five-step process. You do not need perfection on day one. You need a structure solid enough to launch and then iterate with real data.

  1. Identify your value metric

Every hybrid model needs a usage unit, and the right one scales naturally with customer value. Not what is easiest to track internally, but what makes intuitive sense to the person paying.

API calls for API platforms. Documents generated for AI writing tools. Gigabytes processed for data pipelines. Tasks completed for AI agents. A quick test: if a customer uses twice as much, do they get roughly twice the value? If yes, you have a good metric. If the relationship feels loose, keep looking.

  1. Set your base fee

The base fee is your guaranteed revenue per account. It should cover platform access, core features, and baseline support.

The strategic question is what to include. A common structure: the base fee covers the product interface, a certain number of user seats, standard integrations, and an included usage allowance, say, 10,000 API calls or 50,000 tokens. Everything beyond falls under usage pricing.

The included allowance matters more than most companies realize. It gives customers a risk-free window before variable charges kick in. Set it too low, and customers feel nickel-and-dimed immediately. Set it too high, and you give away too much value in the base tier.

  1. Define usage tiers and rates

Three common approaches to variable pricing: Flat per-unit rate. $0.01 per API call, whether you make 100 or 1,000,000. Simple to understand, simple to bill. Works when the cost per unit is consistent.

Volume-tiered pricing. The rate decreases with scale. First 100,000 calls at $0.01, next 500,000 at $0.008, everything above at $0.005. Rewards growth and incentivizes expansion.

Credit packs. Predefined bundles: $50 for 100,000 calls, $200 for 500,000. Budget certainty for the customer, cash upfront for you. Enterprise buyers prefer volume tiers for the visible scale discount. PLG customers prefer simplicity: flat rates or credit packs.

  1. Build for enterprise and SMB separately

The same hybrid structure can serve both segments with different configurations. A startup needs a low base fee, self-serve signup, pay-as-you-go, and no annual commitment. 

An enterprise buyer needs a negotiated annual contract, committed spend minimums with discounts, custom usage rates, and dedicated support baked into the platform fee.

  1. Decide on prepaid vs. postpaid

The final structural decision is whether customers pay before or after consumption.

Prepaid, where customers buy a credit balance upfront and draw it down with usage. Full visibility, no bill shock, and you get cash before delivering the service. Dominant among AI-native companies, where usage costs can be unpredictable.

Postpaid, where usage is tracked and charged at period end. More flexible, but creates the risk of unexpected bills.

Many companies offer both. An included credit allowance in the subscription, with postpaid overage charges beyond it. Predictable baseline, expansion revenue captured.

Revenue forecasting under hybrid models

Hybrid pricing changes how your product earns money, and it also changes how your finance team predicts it.

Why traditional MRR forecasting breaks

With flat subscriptions, forecasting is mechanical. You know how many customers you have and what each pays. Growth means new logos, contraction means lost logos.

Hybrid pricing introduces consumption as a variable. When 40 to 60 percent of revenue depends on how much customers use each month, the math gets messy. A customer paying $500 in base fees might generate $200 in usage one month and $2,000 the next. Multiplying last month's total by twelve becomes dangerously misleading.

Metrics that matter: beyond MRR

When you are running a hybrid model, MRR alone does not tell the full story. The metrics that give your board and investors real clarity include:

  • Committed ARR tracks only the guaranteed subscription and contract revenue, giving you the floor.

  • Usage ARR annualizes the trailing usage revenue, showing the growth trajectory of consumption.

  • Net Revenue Retention (NRR) measures how much existing accounts grow or shrink over time, combining churn, contraction, and expansion into a single percentage.

  • Expansion Revenue isolates the revenue growth coming from increased usage within existing accounts, separate from new customer acquisition.

These metrics, tracked separately but reported together, paint a picture that a single MRR number simply cannot.

Unit economics and financial modeling

Getting the pricing structure right is half the equation. The other half is understanding whether the numbers actually work.

Calculating CAC and ltv in a hybrid world

In a pure subscription business, LTV is simple: average revenue per account multiplied by average lifespan. Hybrid pricing complicates this because revenue per account grows or occasionally shrinks based on consumption.

The accurate approach is cohort-based LTV modeling. Group customers by signup month, track total revenue subscription plus usage over time, and observe the expansion curve. Most hybrid-priced companies see usage revenue start low during onboarding, then increase steadily as customers integrate deeper. The LTV calculation must capture this ramp, not just the initial payment.

CAC stays the same in principle, but the payback period shifts. Hybrid customers often start with lower payments, so payback looks longer initially. But if usage expansion kicks in by month three or four, effective payback can actually be shorter than flat subscription models with no natural expansion path.

Margin analysis when AI COGS are variable

In traditional SaaS, margins are static, but in AI products, every interaction has a cost. The margin equation becomes:

Gross profit = base fee + usage revenue - fixed costs + variable cost per unit x total usage

More usage means more revenue AND more cost. Profitability depends on the spread. Charge $0.01 per API call with $0.004 inference cost, and your usage margin is 60 percent. Every additional call is profitable. If pricing does not maintain that spread, volume makes you less profitable, not more.

Break-even analysis by customer segment

Not all customers reach profitability at the same speed. A startup on $50/month with light usage might take eight months to cover acquisition costs, but on the other hand, an enterprise on a $5,000 annual commitment might break even in month two.

Model break-even by segment: plan tier, company size, industry, and acquisition channel. This reveals where to concentrate sales spend and which segments need pricing adjustments. Hybrid pricing makes this analysis more actionable than flat pricing because usage data gives you a granular view that subscriptions hide.

Get started with your billing today.

Get started with your billing today.

Technical architecture for hybrid billing

Hybrid pricing is conceptually elegant but operationally demanding. Combining fixed subscriptions with real-time usage tracking, complex pricing rules, and unified invoicing requires an architecture that most off-the-shelf tools were never built for.

Event ingestion and real-time metering

Every billable action, whether an API call, a token processed, or an agent task completed, must be captured as an event and sent to your billing system. At scale, three requirements are non-negotiable: 

  • Reliability, a dropped event is lost revenue

  • Idempotency, duplicate events from retries must be counted once

  • Low latency, customers expect near real-time usage visibility

Rating engine: turning events into charges

Raw events are just data. A rating engine transforms them into money by applying pricing rules: flat rates, volume tiers, package bundles, credit deductions, and proration for mid-cycle changes.

Consider a single customer with a base subscription billed in advance, usage charges billed in arrears, credits drawing down simultaneously, and a mid-cycle plan upgrade requiring proration. All of this must be resolved into a single accurate number. Add per-customer overrides for enterprise accounts with negotiated rates, and the rating engine becomes the most complex piece of the billing stack.

Invoice generation that combines fixed and variable

A hybrid invoice must clearly display the base subscription charge, each usage line item with quantities and rates, credit deductions, taxes, and the total due. Generating it accurately requires tight coordination between the subscription system, metering pipeline, rating engine, and payment processor.

Timing matters. Usage charges billed in arrears need a finalization window after the billing cycle ends. Too short and you miss late-arriving events. Too long and customers wait for their bill.

Developer-friendly APIs and webhooks

Your engineering team should not need to become billing experts. The platform must expose clean APIs for ingesting events, querying balances, previewing invoices, and managing subscriptions.

Webhooks should fire on key events: invoice finalized, payment received, credit balance low, and usage limit approaching.

The goal is billing as a service your team integrates with, not a system they build internally.

Migration playbook

Deciding on hybrid pricing and actually transitioning to it are very different challenges. The execution, especially with existing paying customers, requires careful planning.

Auditing your current model and identifying what's broken

Pull your customer data and look for three patterns:

  • Revenue leakage:  Which customers consume significantly more resources than they pay for? If your top 10 percent of users generate 60 percent of your infrastructure costs but pay the same flat fee as everyone else, that gap is your most urgent problem.

  • Undermonetized expansion. Which accounts have grown their usage dramatically since signing up but never upgraded? In a flat model, these accounts are a missed opportunity. In a hybrid model, there is automatic expansion of revenue.

  • Churn signals are tied to pricing. Look at exit surveys and cancellation reasons. If too expensive for what I use or not enough value for the price appears frequently, your pricing is misaligned with perceived value, exactly the problem hybrid pricing is designed to fix.

Designing the transition

There are two fundamental approaches, and each carries a different risk.

  • Parallel run: You keep existing customers on their current plans and introduce hybrid pricing only for new signups. This is the lowest-risk approach because no current customer sees an unexpected change. The downside is that you run two pricing systems simultaneously, which adds operational complexity and delays the full benefits of hybrid pricing.

  • Hard switch: With advance notice, you set a date, communicate the change well in advance, and move all customers to the new hybrid model at once. This is faster and cleaner operationally, but it carries a higher churn risk if the communication is not handled well or if some customers see a price increase.

Grandfathering, phasing, and sunset strategies

Existing customers need a transition that feels fair. Three common approaches that help are:

  • Grandfathering: Lock current customers into their existing rates for 6 to 12 months. They see no change initially and get time to understand the new model before it applies to them. This builds goodwill but delays revenue uplift.

  • Phased introduction: Start by adding a usage component alongside the existing subscription without removing anything. Customers get their current plan plus a usage allowance. If they stay within the allowance, their bill does not change. This makes the transition feel like an addition, not a replacement.

  • Sunset with notice: Announce that legacy plans will be discontinued on a specific date, which is typically 90 to 180 days out. Offer a migration path that is clearly better for the majority of customers. Provide dedicated support for accounts that need help understanding the new model.

Customer communication templates and timelines

Give at least 90 days notice. Lead with the benefit to the customer, not to your business. Be specific about what changes and what stays the same.

A strong announcement that addresses what is changing, when, and why. How does it affect my bill? What if I do nothing? Who can I talk to?

Frame it around fairness, like we are updating pricing so customers who use less pay less, and those who use more get full platform access. It lands far better than that generic statement, like we are adding usage-based charges.

Compliance, tax, and global billing considerations

Billing customers across multiple countries with mixed fixed and variable charges introduces compliance complexity that pure subscriptions rarely face.

Multi-currency and multi-region billing

A customer in Germany expects euros. A customer in Japan expects yen. And the usage rate that feels fair in the US might need adjustment for purchasing power elsewhere.

The billing platform must handle currency conversion at the transaction level, apply correct exchange rates at invoicing time, and ensure base fees and usage charges appear in the same currency on a single invoice.

Tax compliance: sales Tax, VAT, GST

In many jurisdictions, subscription fees and usage charges fall under different tax categories. A platform access fee might be classified as a software subscription, while per-unit usage charges for data processing get different treatment.

Configure tax rules at the line-item level, not the invoice level. Flexprice supports tax rate associations linked to specific entities, allowing different treatments for subscription and usage components on the same invoice. Rules vary by jurisdiction and change frequently, so working with a tax advisor who understands digital services taxation is essential.

Audit trails and data requirements

Metering customer usage means collecting behavioral data, and the regulatory requirements are strict.

SOC 2 requires every billing event to be logged, traceable, and tamper-evident. If a customer disputes a charge, you need an audit trail showing which events were ingested, how they were aggregated, and what pricing rules applied. GDPR adds data minimization: collect only what is required for billing purposes, store only as long as needed, and delete upon request.

The practical requirement is immutable event logs, role-based access controls, and clear data export and deletion capabilities.

Real-world hybrid pricing examples in 2026

Theory is useful, but seeing how real companies structure their models is a better option when you are planning to switch your model.

AI native companies

The AI giants have converged on a consistent hybrid structure: platform access combined with granular token or compute-based usage charges.

  • OpenAI charges per token for API usage, with different rates for input vs. output tokens and across model tiers. 

  • Anthropic follows a similar per-token model with rates varying by capability.

  • Databricks combines a platform subscription with per-DBU charges that scale with compute consumption.

What we can clearly see here is that tokens and compute units work as value metrics because they map directly to cost and scale linearly with customer value. Publishing pricing calculators that let customers estimate spend before committing reduces buying friction significantly.

Developer tools

Developer tools have become the poster children for freemium plus usage hybrid pricing: a generous free tier for building real projects, then usage-based pricing as projects scale to production.

  • Vercel offers free hosting with limited bandwidth, then per-unit overages on paid plans.

  • Supabase provides a free database, auth, and storage with metered usage beyond limits.

  • Cursor offers free AI completions monthly, then charges for additional completions.

Now we can clearly understand that the free tier is a deliberate PLG mechanism. Individual adoption leads to team adoption, then company-wide contracts. Usage pricing ensures revenue scales with account growth without a sales conversation at every step.

Traditional SaaS 

The most interesting studies come from companies that migrated to hybrid as their products matured.

  • Salesforce anchors on per-seat CRM pricing but layers usage charges for Einstein AI credits, API calls, and storage overages. 

  • Slack combines per-user pricing with usage charges for Slack AI and additional storage. 

  • Twilio, always usage-first, now offers committed-use contracts with volume discounts, adding a subscription floor to a usage model.

Migration does not require a complete overhaul. The most successful transitions layer new usage components onto existing subscriptions. Customers experience an expansion, not a disruption.

Why Flexprice is the best hybrid pricing software for AI and SaaS companies

Flexprice is a enterprise grade monetization infrastructure that is specifically designed for AI native companies. It’s not just another billing tool. Flexprice is built for companies where pricing is part of the product itself, like AI platforms, APIs, and SaaS products with variable consumption.

Most traditional billing systems were designed for flat subscriptions. They struggle when you try to layer in usage metering, credits, or feature-based pricing.

Flexprice here takes a different approach.

It’s built from the ground up for hybrid pricing by combining subscriptions, usage-based billing, prepaid credits, and feature gating into a single system. Everything works together natively, instead of being stitched together with workarounds.

The result: you can experiment with pricing, launch faster, and actually align revenue with how your product delivers value.

Meter anything: tokens, API calls, GPU hours, agent actions

At the core of any hybrid model is the ability to track what customers actually use. Flexprice treats every billable action as an event, a lightweight JSON payload containing four things: a customer identifier, a feature name, a usage quantity, and a timestamp. Your product sends these events through SDKs available in JavaScript, Python, and Go, and the platform takes it from there.

What makes this powerful is the aggregation layer. Flexprice supports seven distinct aggregation types:

  • Count for tallying events (API calls made, messages sent)

  • Sum for totaling values (tokens consumed, data transferred)

  • Average for mean calculations (response times, session lengths)

  • Count Unique for distinct values (unique users, unique sessions)

  • Max for peak tracking (concurrent connections, highest compute load)

  • Weighted Sum for time-weighted capacity billing

  • Sum with Multiplier for rate-adjusted calculations

This means you are not locked into counting API calls and calling it a day. The aggregation fits your product's usage pattern rather than forcing your product to fit the billing tool's limitations.

Under the hood, events flow through a pipeline built on Kafka for reliable message delivery and ClickHouse for real-time analytics. This is not a batch job that reconciles usage overnight. Events are processed as they arrive, so customers see their consumption in near real time, and invoices are always accurate.

Combine subscriptions + usage + credits in one plan

This is where most billing tools break down entirely. They can handle a subscription. They might track usage. But combining a flat platform fee with metered usage charges and credit deductions on a single plan, resolved into one clean invoice? That requires architecture designed for it from the start.

Flexprice plans support multiple charge types simultaneously:

  • A recurring flat fee billed in advance for platform access

  • Usage-based charges are billed in arrears for metered features like API calls or tokens

  • Credit deductions are applied from the customer's wallet balance

All of this lives within the same subscription. The invoice that results shows each component clearly: base charge, usage line items with quantities and rates, credit applications, and the final total.

For the usage layer, the pricing engine supports three billing models. Flat fee charges a fixed price per unit. Volume-based tiered pricing reduces the per-unit rate at higher thresholds. Package-based pricing lets customers buy usage in predefined bundles. You can mix these across different metered features within the same plan, one feature using flat pricing while another uses volume tiers.

Credit wallets and token-based billing out of the box

The credit and token economy has become the standard for AI products, and bolting a wallet system onto a tool that was never designed for one is a recipe for billing errors and customer frustration.

Flexprice has a native wallet system that handles the full lifecycle of credits. Customers can receive prepaid credits purchased with real money or promotional credits granted for free as part of onboarding or campaigns. Each wallet tracks a real-time ongoing balance that accounts for the current balance, pending invoices, and current-period usage, so the number customers see always reflects reality.

The auto top-up feature is where the system truly shines. It monitors the ongoing balance continuously, and when it drops below a configured threshold, one of two things happens:

  • Direct mode: Credits are added to the wallet immediately. No waiting, no friction. Best for customers with reliable payment methods who need instant availability.

  • Invoiced mode: An invoice is generated first, and credits are added only after payment clears. Better for cash flow control and payment confirmation.

You configure the threshold, the top-up amount, and the invoicing mode per customer. Combined with low-balance alerts, this creates a self-sustaining credit system where customers never unexpectedly run dry.

Conversion rates let you define custom units. If your product bills in AI credits rather than dollars, you set the conversion rate between your unit and the base currency. The wallet handles the math, and the invoice displays both the credit usage and the equivalent monetary value.

Feature gating and entitlements per plan

Hybrid pricing is not only about how much customers pay. It is also about what they can access. A Starter plan should include different capabilities than an Enterprise plan, and those boundaries need to be enforced programmatically, not through honor systems or manual checks.

Flexprice defines three types of features:

  • Boolean features act as on/off switches. SAML SSO might be available only on Enterprise plans. Advanced analytics might unlock at Pro. These features are either enabled or disabled, with no usage dimension.

  • Metered features combine access control with usage tracking. A Starter plan might include 10,000 API calls per month. Pro includes 100,000. Enterprise gets unlimited. The same feature is available across tiers, but the usage limit changes, and the entitlement layer enforces the boundary at the API level.

  • Static features describe fixed plan attributes that do not change with usage. The list of available AI models, the number of included team seats, or the support response time SLA. These are plan descriptors that help customers understand what they get.

Features attach to plans through entitlements, and the entire configuration is manageable without code changes. Add a new feature or adjust a usage limit, and it takes effect across all relevant subscriptions automatically.

Built for AI and agentic companies

Flexprice is not a general-purpose subscription tool that added a metering checkbox to keep up with market trends. It was explicitly designed for the billing patterns AI companies encounter daily.

Consider what a typical AI company needs from its billing system:

  • High-volume event ingestion that handles thousands of events per second without dropping data

  • Token-based metering with multiple aggregation dimensions

  • A credit system with real-time balance visibility and auto top-ups

  • Per-customer price overrides for enterprise deals with negotiated rates

  • The ability to combine all of this on a single invoice that customers can actually read

That is not a feature list bolted onto an existing subscription tool. That is the architecture Flexprice was built around from day one. Kafka powers the event pipeline. ClickHouse handles real-time aggregation. Temporal orchestrates billing cycles and scheduled workflows. PostgreSQL stores transactional data. Each component was chosen for a specific purpose within the hybrid billing workflow, not repurposed from a simpler system.

Open source, self-hosted, no vendor lock-in

Billing is arguably the most trust-sensitive system in your entire stack. It touches every customer, every invoice, and every dollar of revenue. Handing that system to a closed-source vendor means trusting their code, their uptime, and their pricing decisions with your business.

Flexprice takes a different approach. The entire platform is open source. You can read every line of code, understand exactly how usage is aggregated, and how pricing rules are applied. If something looks wrong, you trace it yourself rather than filing a support ticket and waiting.

Self-hosting is fully supported on your own AWS infrastructure using ECS and Aurora, keeping billing data within your security perimeter. For teams that prefer managed infrastructure, Flexprice Cloud offers a hosted option. Either way, there are no surprise platform fees, no percentage-of-revenue charges, and no vendor lock-in. If you decide to move, your billing logic and data are yours.

Integrations that connect your entire revenue stack

A billing platform that cannot talk to your payment processor, your CRM, and your accounting software is a billing silo. Flexprice integrates natively with the tools that make up a modern revenue stack:

  • Payments and billing: Stripe, Chargebee, Razorpay, Paddle, Moyasar, and Nomod. Each integration handles customer synchronization, invoice syncing, and payment reconciliation so that charges calculated in Flexprice flow seamlessly to collection.

  • Accounting: QuickBooks integration syncs invoices and line items, keeping financial records aligned without manual data entry.

  • CRM: HubSpot integration syncs customer and deal data, connecting billing activity to the sales pipeline.

  • Data infrastructure: A Kafka-based collector streams usage events from your existing data pipeline into Flexprice. If you are already publishing events to Kafka for analytics or monitoring, the same events can feed your billing system without re-instrumenting your application.

  • Webhooks round out the integration layer, firing on key billing events (invoice finalized, payment received, subscription changed, wallet balance low) so your application can react in real time.

The result is a billing system that layers into your existing stack rather than demanding you rip and replace what is already working.

Top hybrid pricing tools in 2026

  1. Flexprice

  2. Orb

  3. Lago

  4. Metronome

  5. Chargebee

Choosing the right billing platform for hybrid pricing is not a generic software decision. It directly shapes how fast you can iterate on pricing, how accurately you can meter AI usage, and whether your billing infrastructure becomes a growth enabler or a bottleneck. Below is a detailed comparison of the five leading platforms, with honest pros and cons evaluated specifically 

Tool

Pros

Cons

Flexprice

  • Hybrid-native subscriptions + usage + credits + entitlements in one unified system

  • Handles 60K+ events/sec with Kafka + ClickHouse built for high-scale AI workloads

  • Full credit/wallet system, prepaid, promo credits, auto top-ups, real-time balance tracking

  • 100% open source with full control + transparency

  • AI-native MCP server, integrates with Cursor, Claude, and VS Code workflows

  • Enterprise-ready, ramped contracts, parent-child billing, shared credit pools

  • Global payment support (Stripe, Razorpay, Moyasar, Nomod)

  • Newer platform compared to legacy tools 

  • Smaller ecosystem, fewer tutorials, community resources

Orb

  • Strong usage-based billing engine with flexible charge models

  • Real-time processing with threshold-based billing triggers

  • Revenue simulation to test pricing changes before rollout

  • Enterprise features (tiered pricing, commitments, credit pooling, custom rate cards)

  • Stripe-only payment processing limits global coverage

  • Closed source, no visibility or extensibility

  • No recurring/rollover credits for hybrid pricing models

  • No AI-native tooling or MCP integrations

Lago

  • Open source foundation with self-hosting flexibility

  • Solid usage billing with aggregations and event-based pricing logic

  • Wallet system with scheduled credits and expiration rules

  • Event property filtering (different pricing by model/type within one metric)

  • Feature gating in cloud (RBAC, portal, invoices locked behind paid tier)

  • No parent-child hierarchy or org-level billing support

  • Limited credit flexibility (no multi-level alerts, conversion rates)

  • Lower throughput ~15K events/sec vs higher-scale systems

  • Pricing iteration requires plan duplication and manual migration

Metronome

  • Built specifically for AI and infrastructure billing use cases

  • Strong aggregated metering for compute-heavy workloads

  • Backed by Stripe's reliable infrastructure and ecosystem alignment

  • Focused product does one thing well: metering + pricing

  • Stripe-only ecosystem, no support for regional gateways

  • Not a complete billing system relies on external tools for invoicing/payments

  • Slower pricing iteration due to the aggregated data model

  • Closed source with limited integrations beyond Stripe

  • No native credit/wallet system for token-based pricing

Chargebee

  • Mature subscription billing with strong dunning, invoicing, and lifecycle management

  • Well-known brand with enterprise trust, compliance, and support

  • Large integration ecosystem (payments, CRM, accounting, tax tools)

  • Basic CPQ and quotes support for sales-led workflows

  • Subscription-first architecture limits real-time usage billing at scale

  • No true credit wallet system, only credits/adjustments, not balances. 

  • Revenue-based pricing (cost increases as you scale usage)

  • Slow pricing experimentation, plan duplication, and long setup cycles

  • Feature gating in lower tiers (advanced features locked behind enterprise)

  • Closed source, no self-hosting or billing logic visibility

How to choose the right hybrid pricing software

Not every platform that claims hybrid support actually does it well. Some bolt usage onto a subscription engine. Others handle metering but collapse at invoicing. Six filters to apply before committing.

Does it support your pricing model natively?

Can it combine a flat fee, usage charges, and credit deductions on a single plan and invoice without workarounds? Many tools require duct-taping separate features together, and that fragility breaks the moment anything changes. Demo your exact pricing structure, not a generic one.

How does it handle metering at scale?

If your product generates thousands or millions of usage events, basic API-based metering will not cut it. Ask:

  • What is the maximum event throughput per second?

  • Is ingestion idempotent (duplicates counted only once)?

  • How close to real time is aggregation?

  • Does it support bulk ingestion for high-volume scenarios?

A platform handling 15K events/sec versus 60K+ is the difference between billing that works now and billing that survives your next growth phase.

Credit and wallet support

If your model includes prepaid credits, token packs, or promotional balances, you need native wallet functionality:

  • Auto top-ups with configurable thresholds

  • Expiration rules and rollover logic

  • Low-balance alerts at multiple levels

  • Custom conversion rates, example 1 AI credit = $0.01

Bolting a credit system onto a platform not designed for it creates accounting nightmares and balance errors that erode customer trust.

Flexibility to iterate

Your pricing will change. In 2026, the best companies revisit it quarterly. The platform should let you modify tiers, adjust usage rates, add new metrics, and run A/B experiments without an engineering sprint every time. Ask whether changes require creating new plans and migrating customers, or whether updates roll out to existing subscriptions in place.

Open source vs. closed Source

Open source billing gives you full visibility into billing logic, self-hosting, and zero vendor lock-in. Closed-source provides managed infrastructure and reduces operational overhead. The right choice depends on how critical billing transparency and data control are to your business.

Integration with your existing stack

A billing platform that cannot talk to your payment processor, CRM, and accounting software becomes a silo requiring manual reconciliation. Check for native connectors to your payment gateway, like Stripe, Razorpay, Paddle, accounting tools like QuickBooks, CRM (HubSpot, Salesforce), and data pipelines, which are Kafka and webhooks. Fewer custom integrations means faster time to launch.

Frequently Asked Questions

Frequently Asked Questions

What is the difference between hybrid pricing and pure usage-based pricing?

How does hybrid pricing work for AI companies that sell tokens or API credits?

Is hybrid pricing better than per-seat pricing for AI and SaaS products?

What billing infrastructure do you need to support hybrid pricing?

Can you migrate from flat subscription pricing to hybrid without losing customers?

Ayush Parchure

Ayush Parchure

Ayush is part of the content team at Flexprice, with a strong interest in AI, SaaS, and pricing. He loves breaking down complex systems and spends his free time gaming and experimenting with new cooking lessons.

Ayush is part of the content team at Flexprice, with a strong interest in AI, SaaS, and pricing. He loves breaking down complex systems and spends his free time gaming and experimenting with new cooking lessons.

Share it on:

Ship Usage-Based Billing with Flexprice

Summarize this blog on:

Ship Usage-Based Billing with Flexprice

Ship Usage-Based Billing with Flexprice

More insights on billing

More insights on billing

Get Instant Feedback on Your Pricing | Join the Flexprice Community with 300+ Builders on Slack

Join the Flexprice Community on Slack