
Product
AI Billing is (mostly) token plumbing
Raffi Sarkissian • 5 min read
May 23, 2025
/9 min read
Pricing AI is genuinely hard. The cost structure is different from SaaS. The value is harder to define. And the model that worked at $1M ARR often breaks at $10M.¹
This article covers the pricing models that actually work for AI products in 2026 — what each model assumes, where it breaks, and how to pick the right one for your stage and cost structure.
One disclosure upfront: Lago builds billing infrastructure for AI companies. We benefit when you pick a model that requires real metering. Read accordingly.
Value-based pricing is a strategy in which you set the price of your AI product based on the value it delivers to your customers. It's the opposite of cost-plus, where you mark up your infrastructure costs. With value-based pricing, you start with the customer's problem and work backward.
To use value-based pricing for AI, you need to understand your customers' challenges and how your AI solution helps solve them. Are you saving them time? Improving accuracy or efficiency in their processes? These are the kinds of questions that get to the heart of the value you provide.
Putting a number on that value requires careful research. Look at your industry: Are there benchmarks for how much similar problems cost businesses? You can also survey your customers, seeking to quantify their frustrations with their current process and excitement about what your AI could provide.
When your price accurately reflects the value you're creating, it becomes much easier for customers to justify the expense. This can mean faster sales cycles, higher win rates, and increased customer satisfaction.
For instance, imagine a predictive analysis AI tool for sales teams. If your AI model helps close 10% more deals per quarter, you could price based on the average revenue per deal, factoring in the boost provided by your solution. Since the price is tied to specific outcomes, it highlights the ROI of your AI product, motivating customers to adopt and fully engage with the solution.
The hard part: value-based pricing requires you to actually know your customer's economics. Most early-stage teams don't. Start with usage-based pricing and layer in value-based logic once you have the data to back it up.
Unlike a flat subscription fee, usage-based pricing directly aligns cost with the amount the customer uses your AI solution. Without accurate metering, you leak revenue. Lago's research shows companies on usage-based models lose 2–5% of ARR to metering gaps alone. Customers' use of your AI product is identified as events (think individual API calls), and you add them all up as individual costs, which will show up in your clients' bills.
Three common usage metrics: data processed (images, tokens, documents), API calls (per query), and compute time (GPU-seconds, inference minutes). The right metric is the one that most clearly tracks value delivered, not the one that's easiest to instrument.
It works because cost scales with consumption. A customer doing a one-off project pays for one-off usage. A customer growing 10x pays 10x. That alignment is hard to fake with a flat subscription. The trade-off is revenue unpredictability, which is why most mature AI companies end up at a hybrid model with a subscription floor.
At Lago, we've seen Mistral, Groq, and Together.ai all run token-based usage models with subscription floors. The pattern is consistent: start usage-based, add the subscription layer once you know what "a typical customer" looks like.
Subscription models are a tried-and-true way to price products, and they're just as powerful for AI solutions. Subscriptions are convenient because they allow you to create different tiers that align with how customers get value from your solution, make pricing accessible, and foster long-term customer relationships.
Three common subscription structures: feature-based tiers (basic vs. premium capabilities), usage-based tiers (included allocation + overage), and service-based tiers (self-serve vs. dedicated support). Most AI companies use a combination. The important thing is that tiers track value, not arbitrary limits customers hit accidentally.
The core problem with pure subscription pricing for AI: your heaviest users can create far more infrastructure cost than light users, even at the same plan tier. If your top users consume 20x the median usage, flat plans misprice them, in your favor or theirs. Model the distribution before setting limits.
This is a popular approach, especially for getting new AI products off the ground. The idea is simple: you offer a free basic version of your AI solution while locking advanced or expanded capabilities behind a paid subscription.
This free tier is incredibly powerful for attracting users. People are naturally drawn to trying things at no cost, removing that initial hurdle to adoption. It's a low-risk way for businesses to dip their toes in the water, experience your AI in action, and see if it solves some of their problems.
The real challenge with freemium lies in converting those free users into paying customers. You need to design the free tier to be helpful but also leave users wanting more. This might mean limiting data processing in the free version, offering only the most basic output, or withholding integrations with other tools they might already use.
The main goal is to create that "aha!" moment when someone hits a limit within the free tier and realizes the value of upgrading to unlock the full potential of your AI solution.
Freemium only works if the cost of serving free users is genuinely low. For AI products with real inference costs, free tiers need hard caps, otherwise you're subsidizing usage with no conversion path. Many AI companies have learned this the expensive way.
This is one of the AI pricing models that involves customers paying either a one-time upfront fee or recurring licensing fees to access your software. It's a good fit for specific markets and customer needs.
Licensing works best for enterprise buyers with strict data security or compliance requirements, customers who expect deep integration, want deployment on their own infrastructure, and are willing to pay upfront for that control. These are often the same customers who prefer self-hosted deployments.
However, traditional licensing does come with some logistical considerations. You'll likely need a system to issue and manage individual software licenses. This means ensuring customers are adhering to the terms (how many users, how it's being deployed) and providing updates and patches as needed. There's often a compliance aspect, making sure only those who have paid have ongoing access.
Performance-based pricing is a model that tightly links revenue with the success of your customer's AI implementation. Rather than paying for the AI solution upfront, the customer's cost is determined by the value it generates, such as increased efficiency and reduced errors.
Establishing the right metrics is crucial for this to work. Before deploying your AI, you'll collaborate with the customer to define their baseline performance.
This is increasingly called outcome-based pricing, and it's becoming the dominant model for AI agents in 2026. Salesforce Agentforce charges per conversation. Intercom's Fin charges per ticket successfully resolved. Anthropic's Claude API is priced per token, but the enterprise layer is moving toward per-outcome billing.³ The logic: when agents act on behalf of customers, customers want to pay for results, not compute.
The trade-off is attribution. Outcome pricing requires you to define what "success" means, measure it reliably, and handle disputes when the AI partially succeeds. It's the hardest model to operationalize, but the one most aligned with customer value. Most companies work toward it rather than starting with it.
6b. Why seat-based pricing breaks for AI
Seat-based pricing was the default for SaaS: CRM, project management, collaboration tools. Value tracked with headcount. One user, one seat, one charge.
AI breaks this. An engineer running 50,000 inference calls a day consumes vastly more infrastructure than a manager who logs in once a week. Same seat, wildly different cost. Flat seat pricing creates a margin problem that compounds as your heaviest users grow. It also caps your upside, a team that doubles its AI usage doesn't automatically pay you more.
This isn't theoretical. A recent Stripe survey found 56% of AI company leaders use hybrid pricing and 38% use purely usage-based pricing.³ Almost nobody is doing pure seat-based pricing for AI-native products, because the math doesn't work.
Hybrid pricing models recognize that there's rarely a one-size-fits-all solution, especially in AI. Combining aspects of the pricing models we've discussed allows you to create a truly tailored offering for your AI product.
Hybrid models are where mature AI companies land. A subscription floor gives you predictable ARR. A usage component captures upside when customers grow. The combination also removes the conversion barrier, customers aren't afraid of a runaway bill, and you aren't subsidizing heavy users on a flat plan.
The Stripe data is directional here: companies on hybrid models (subscription + usage) report 21% higher median growth rates than pure-play subscription or pure usage models.³
Let's take a look at a few hybrid pricing combination examples well-suited for different types of AI products:
Picking the suitable pricing model for your AI business is critical, so let's break down how to make the best decision.
Start with your customer segment. Enterprise buyers want predictability, a subscription floor with capped overages. Developer-first buyers want low friction, usage-based with no minimums. Consumer AI usually lives on freemium. Competitive pricing is a reference point, not a constraint, if you have a meaningfully better product, you can charge more.
Identify your charge metric first. What single unit increases as your customer gets more value? Tokens, API calls, documents processed, outcomes delivered? Your pricing model should be built around that metric. If costs scale with usage, usage-based or hybrid protects your margins. If costs are relatively fixed regardless of usage, a subscription is defensible.
The mistake most teams make: choosing the metric that's easiest to instrument rather than the one that best tracks value. Tokens are easy to count. But customers don't think in tokens, they think in documents summarized, conversations resolved, code reviewed. Price in the unit closest to how your customer describes the value.
Pricing isn't a one-time decision. A Stripe survey found 92% of AI companies that charged for usage had subsequently adjusted their pricing.³ Start with the simplest model that fits your customer. Add complexity only when data justifies it. The companies that iterate fastest on pricing usually win.
When selecting the right pricing approach for your AI solution, it helps to see how different models stack up against each other.
| Pricing Model | Revenue Predictability | Customer Acquisition | Implementation Complexity | Best For |
|---|---|---|---|---|
| Value-based | Medium | Medium | High | Solutions with clear ROI metrics |
| Usage-based | Low to Medium | High | Medium | APIs, processing services |
| Subscription | High | Medium | Low | SaaS platforms, ongoing services |
| Freemium | Low | Very High | Medium | Mass-market AI tools |
| License Fee | High | Low | Medium | Enterprise solutions |
| Performance/Outcome-based | Low | Medium | Very High | AI agents, outcome-focused AI |
| Hybrid | Medium | High | High | Complex AI ecosystems |
The pattern: companies move left to right over time. They start with usage-based or freemium (easier to acquire, harder to forecast). They add a subscription floor (predictability). Eventually the best-positioned ones move toward outcome-based billing for their agent layer. That's where AI monetization is heading.
After understanding the various pricing models available for AI products, the next challenge is implementation. This is where a robust billing infrastructure becomes essential.
For companies looking to implement complex AI pricing models, Lago provides open-source metering and billing infrastructure designed for AI, SaaS, and tech companies with complex billing needs.⁴ It supports all the models covered here: subscriptions, usage-based billing, prepaid credits, hybrid plans, and add-ons. Mistral, Groq, and Together.ai all run on Lago.
Start with your charge metric. Build billing infrastructure that can instrument it at scale. Test with a small segment first. Adjust. The 92% of AI companies that change their pricing don't regret the change, they regret how long they waited to make it.
Content