Credits vs. Seats vs. Pure Usage: How AI Companies Price Their Products
Key Takeaways
- Each model charges for something different. Seats charge for access, credits charge for a set allowance of work, and pure usage charges for every unit consumed. Pick the one that matches what your customers actually value.
- Seats are the easiest to sell and the easiest to break. One heavy user can cost more to serve than the seat brings in, and the better your AI gets at replacing manual work, the fewer seats customers need.
- Credits give both sides a ceiling. Customers know the most they can spend, and you can price heavy features higher than light ones. This only works if the credit rules are simple enough to explain in one sentence, and this Indie Hackers walkthrough shows how to set credits and limits from your cost per user.
- Pure usage matches your costs best and forecasts worst. Your margins stay safe, but customers dislike surprise bills and your own revenue moves with their activity.
- Most AI products end up with a mix. A base fee with included usage and clear overage rates is common, but it is not right for everyone. Choose based on how much usage varies, what each action costs you, and whether you can explain the bill easily.
Pricing an AI product is a different job from pricing normal software. When a tool costs almost nothing to serve one more person, a flat monthly fee per user works fine. When every click runs an AI model that costs real money, that same flat fee can quietly lose money on your busiest customers. Bain & Company looked at more than 30 established SaaS vendors that were adding generative AI. About 65% had added an AI charge based on usage or feature access on top of their seat pricing, while the other 35% had raised seat prices and bundled AI into existing tiers. None of them had moved fully to usage or outcome-based pricing. Per-Seat Software Pricing Isn’t Dead, but New Models Are Gaining Steam,
So the real choice for most founders sits between three building blocks: seats, credits, and pure usage. This guide puts credits vs seats vs usage-based pricing side by side. You will see how each one works, who it suits, where it breaks, and how to pick the right one for your own product. If you spend any time on Indie Hackers, you have seen this debate play out, including in a recent thread on AI tool pricing where builders argue about flat plans versus API costs and about usage bills that grow quietly once a tool becomes part of daily work.
Why AI Companies Are Rethinking Traditional SaaS Pricing
Traditional SaaS pricing rested on one idea: more users means more value and only slightly more cost. AI breaks both halves of that idea.
1.Variable costs on every request. Each time a customer uses an AI feature, the product pays to run a model. The bill depends on which model is used, how big the request is, and how long the answer runs. GitHub made this point in April 2026 when it explained that absorbing the rising cost of Copilot usage was no longer sustainable. It moved all Copilot plans to usage-based billing, with a monthly allowance of AI credits included in every plan.
2.User count is not the same as consumption. Two customers can each pay for ten seats and use the product in completely different ways. Pricing adviser Kyle Poyar has said that in his experience, 70 to 80 percent of AI token consumption comes from just 10 percent of users. A seat price treats all of them the same. Here is a simple, made-up example of what that does to your margin:
| Customer | Seats | Revenue at $30 per seat | Cost to run the AI | Result |
|---|---|---|---|---|
| Light-use team | 5 | $150 | $10 | $140 kept |
| Heavy-use team | 5 | $150 | $225 | $75 lost |
These numbers are for illustration only. They are not real customer data.
3.Predictable bills for customers versus healthy margins for you. Buyers want a bill they can plan around. Founders want revenue that rises when costs rise. In Poyar’s 2026 State of B2B Monetization survey of more than 230 companies, hybrid pricing was the most common main model, at 37%. Companies on seats worried their model would not last. Companies on usage found revenue hard to forecast. Companies with hybrid pricing were the happiest, but many struggled to explain their pricing to customers.
Seats, Credits, and Pure Usage: The Three Ways AI Products Charge
Most AI SaaS pricing models come down to these three. Each one below gets the same six questions, so you can compare them fairly.
Seat-Based Pricing: You Pay for Who Gets Access
1.How it works. The customer pays a fixed monthly or yearly fee for each person who can use the product. Some plans add a fair-use limit or a small AI allowance per seat. The bill only changes when the team size changes.
2.Who benefits most. Buyers with fixed budgets and finance teams who want to know the bill in advance. It also suits vendors whose value comes from individual people using the product every day.
3.Benefits and limits.
- Benefit: it is easy to explain, forecast, and sell. Procurement teams already know how to buy by headcount.
- Benefit: revenue grows naturally as customer teams grow.
- Limit: heavy users can cost more than their seat brings in.
- Limit: if your AI lets a customer do the same work with fewer people, your revenue shrinks as your product improves. Bain makes the same point: headcount pricing loses its logic when customers need fewer people to run the software.
4.Scenarios where it fits. The AI acts as a helper next to a person in their daily work. Usage per person is fairly even. The cost of serving one person is small compared with the seat price.
Examples. Zoom bundled AI features into its existing paid tiers and raised seat prices, according to Bain. Microsoft 365 Copilot is sold per user. Salesforce introduced a seat-based licensing option for Agentforce, which Zuora CEO Tien Tzuo linked to buyers asking for predictable bills.
5.When it works best. When every seat uses the AI at about the same level, the cost per user is low, and your buyer values a simple contract over perfect fairness.
Credit-Based Pricing: You Buy a Balance and Spend It
1.How it works. Customers receive credits with their plan or buy packs of them. Each action uses a set number of credits, for example 1 for a short draft and 10 for a long analysis. When the balance runs out, they top up or wait for the next cycle. Indie Hackers has a clear explanation of this in a post on SaaS pricing models, where an SEO tool charges one credit per website check and sells a monthly plan with a few credits included.
2.Who benefits most. Customers who use several features that cost different amounts to run, and teams that want a firm ceiling on spend. Vendors benefit too, because heavy features can cost more credits than light ones.
3.Benefits and limits.
- Benefit: one currency across all features, so you can add a feature without writing a new price list.
- Benefit: prepaid credits bring cash in early and cap how much any one customer can cost you.
- Benefit: you can change what an action costs behind the scenes without redoing your pricing page.
- Limit: customers often cannot tell what a credit is worth in real work.
- Limit: credit anxiety. Users of Lovable, which runs on credits, complained on Reddit after pricing changed roughly every month through 2025, and some said they avoided experimenting because each try cost credits.
- Limit: expiry and rollover rules add support work and can upset people.
4.Scenarios where it fits. Your product has many features with very different running costs, such as text, images, and video. Customers want a spending limit. You sell mostly self-serve.
Examples. Clay combines subscription packages with credits for extra usage. GitHub Copilot plans now include a monthly allowance of GitHub AI Credits, with the option to buy more. Lovable runs on credits, and ElevenLabs bills speech work in credits based on characters.
5.When it works best. When features differ a lot in cost, customers want to cap their spending, and you can show the balance and the price of each action inside the product before anyone clicks. If you cannot explain a credit in one sentence, simplify it.
Pure Usage-Based Pricing: You Pay for What You Use
1.How it works. You measure one clear unit, such as tokens, API calls, minutes of audio, or documents processed, and bill for the total at the end of the cycle. Rates often drop at higher volume. Indie Hackers has a walkthrough of usage-based billing that uses Zapier’s task-based tiers as an example.
2.Who benefits most. Developers and companies with spiky or fast-growing volume, and vendors whose cost per unit is clear. Customers also like starting small without a big commitment.
3.Benefits and limits.
- Benefit: it is the closest match between what you spend and what you earn.
- Benefit: the entry barrier is low, and revenue grows as customers succeed.
- Limit: bills can jump, and finance teams hate that. Tien Tzuo points out that AI usage can spike after one product issue or one marketing campaign.
- Limit: customers may start avoiding the product to save money. One commenter in an Indie Hackers thread on subscription fatigue said usage pricing makes them too aware of spending, so they use the product less.
- Limit: you need accurate measuring and invoicing from day one.
4.Scenarios where it fits. APIs, developer tools, and infrastructure-style products. One unit tracks the value customers get, and the customer understands that unit. Customers are comfortable with technical products.
Examples. OpenAI and Anthropic bill their APIs by tokens. Twilio is the long-running example of pay-per-use software. Intercom started its Fin AI agent at $0.99 per resolved conversation, which is a close cousin of pure usage because the charge follows results instead of raw inputs.
5.When it works best. When the unit is easy to measure and the buyer understands it. Per document processed is easier to grasp than per thousand tokens.
Credits vs. Seats vs. Pure Usage: A Side-by-Side Comparison
Here is the AI pricing models comparison in one table.
| Factor | Seats | Credits | Pure usage |
|---|---|---|---|
| Billing unit | Per user, per month | Credits spent per action | Each unit used (tokens, calls, tasks) |
| Customer predictability | High | Medium to high, capped by balance | Low |
| Revenue predictability | High | Medium, prepaid credits help | Low |
| Cost alignment | Weak | Good if credit costs match real costs | Strongest |
| Implementation complexity | Low | Medium: balances and credit rules | High: exact measuring and invoicing |
| Ideal use case | Daily-use tools with even usage | Many features with uneven costs | APIs and tools with one clear unit |
The two models people mix up most are credits and pure usage, so here is credit-based vs usage-based pricing on its own:
| Credit-based | Pure usage | |
|---|---|---|
| When the customer pays | Up front, or from an included balance | After use, at the end of the cycle |
| What the customer sees | A balance that goes down | A bill that goes up |
| Main risk for the customer | Paying for credits never used | A bill bigger than expected |
| Main risk for you | Credit rules that confuse people | Revenue that swings from month to month |
Seat-based vs usage-based pricing comes down to one question: are you charging for the right to use the product, or for the work it does?
How Each Pricing Model Affects Margins and Growth
1.The risk of heavy users under seat-based plans. On seats, your best-engaged customers are often your least profitable ones. You can limit the damage with a fair-use cap, a cheaper seat for occasional users, or a usage add-on for the top slice of users. Poyar suggests a lighter seat type for people who log in rarely.
2.The role of credit limits in controlling costs. Credits cap what one customer can cost you in a month. They also give you a lever: when a feature gets more expensive to run, raise its credit price instead of raising your plan price. For a floor, one commenter in an Indie Hackers thread on metered pricing suggests pricing at your cost plus the value you add, so you never lose money on a customer. Unused credits can lift margins, but customers notice, so a limited rollover period is a kinder middle path.
3.Why pure usage can make bills unpredictable. Your costs and revenue move together, but your customer’s bill moves too. HubSpot’s guide to credit-based tools warns that a low entry price says little about what you will pay once the product is fully rolled out. Spending caps, budget alerts, and a usage dashboard inside the product take most of the sting out of this.
How pricing choices influence expansion revenue. Each model grows differently:
- Seats: grows with headcount, which is slow, and can shrink if AI replaces people.
- Credits: grows when customers top up or move to a bigger bundle.
- Pure usage: grows on its own as customers do more, and falls just as fast when they do less.
When Should an AI Startup Choose Each Model?
- Choose seats when value scales with team adoption. If each new person who joins gets roughly the same benefit and costs you roughly the same, seats are fair and simple.
- Choose credits when customers need a bounded allowance across different tasks. If your product does text, images, and analysis at very different costs, credits let one balance cover all of it.
- Choose pure usage when consumption is measurable and closely tracks value. If you can point to one unit that customers already think in, such as a call, a document, or a minute, let them pay by that unit.
- Consider hybrid pricing when you need recurring revenue and variable usage charges. If you want steady monthly income but your costs rise with heavy use, a mix can cover both.
Why Hybrid Pricing May Be the Next Step for AI SaaS
Hybrid pricing mixes a base subscription with usage charges. Indie Hackers describes it simply in a post on subscription models: a base fee plus extra usage-based charges, balancing steady revenue with room to grow. Bain found the same pattern among established vendors, noting that hybrid lets companies start capturing AI value without rebuilding their whole pricing system. GitHub Copilot, with its included monthly credits and optional extra usage, and CodeRabbit, which pairs per-developer tiers with pay-as-you-go usage and a monthly spending cap, follow this approach.
| Part | What it does | Trade-off |
|---|---|---|
| Base subscription | Gives you steady monthly revenue | Customers may pay for access they barely use |
| Included usage | Lets customers start without worry | Too high and you lose margin, too low and people feel squeezed |
| Overages | Charges heavy users for extra use | Surprise bills if the rates are unclear |
| Enterprise commitments | Annual spend agreed up front, often at a discount | Takes sales effort and careful forecasting |
Hybrid is not the best answer for every company. It gives customers two or three things to understand instead of one, and it asks you to run more than one pricing system. A tool with even usage and low running costs can stay on seats. An API with one clear unit can stay on pure usage. Hybrid earns its extra complexity when your customers vary a lot in how much they use and you still want predictable income.
How to Choose the Right AI Pricing Model
Ask these five questions in order. They cover customer value, usage variation, your costs, predictability, and how easy the bill is to explain.
| Question | If the answer is… | Lean toward |
|---|---|---|
| Does value grow with team size or with work done? | Team size | Seats |
| Work done | Credits or usage | |
| How much does usage vary between customers? | Very little | Seats |
| A lot | Credits or usage | |
| What does one action cost you? | Small and steady | Seats or usage |
| Large or uneven | Credits | |
| How much do buyers need a fixed bill? | A lot | Seats or credits |
| Not much | Usage | |
| Can you explain the bill in one sentence? | Yes | Keep the model |
| No | Simplify it |
If your answers point in different directions, that is a sign hybrid pricing may fit. Before you have real customers, the simplest model that still shows you how people use the product is usually the right starting point, a view shared in CRV’s guide to AI pricing. If you are still working out your first price, this Indie Hackers breakdown of pricing models is a useful place to start.
Final Thoughts
The best AI pricing model is the one where what customers pay for matches the value they get and the costs you carry. Seats work when value follows people. Credits work when value follows different kinds of work with different costs. Pure usage works when one clear unit tracks both value and cost.
You do not have to get it perfect on day one. Start with the simplest model you can explain, track what each customer costs you, and be ready to adjust as you learn. Prices are easier to improve than to defend, so keep them clear enough that customers always know what they are paying for.
FAQ
- Is seat-based pricing dead for AI products?
No, but seats alone are risky when the AI does real work. A widely shared r/SaaS thread asked whether seat-only pricing is a trap for AI products in 2026, and the worry is fair when one customer can cost far more than a seat brings in. Seats still work when usage per person is even and the cost per user is low. Many teams keep a seat or platform fee for predictability and add usage on top for heavy users.
- What is the difference between credit-based and usage-based pricing?
With credits, the customer gets or buys a balance first and spends it down, and different actions cost different amounts of credits. With pure usage, you bill after the fact for what was consumed. Credits give the customer a spending ceiling and give you cash up front. Pure usage is fairer to light users but harder to predict. In practice, credits are often just usage billing paid in advance, and this Indie Hackers post on SaaS pricing models explains both side by side.
- Why do users complain about credits, and should credits expire?
The common complaints are that people cannot tell what a credit is worth, the rules keep changing, and they fear wasting credits on a bad result. Show the cost of an action before it runs, show the balance at all times, and avoid charging for failed actions, which HubSpot’s guide lists as a warning sign for buyers. Expiry encourages use but annoys customers. A limited rollover period, such as one extra month, is a fair compromise.
- How do I stop one heavy user from wiping out my margin?
Use a fair-use limit, an included allowance with a clear overage price, or a spending cap. A lighter, cheaper seat for occasional users also helps. Heavy use is usually concentrated in a small group of customers, so track the cost of each account from day one. That way you see the problem before it shows up in your monthly numbers.
- What should I use when I am just launching and do not know my costs yet?
Start simple. A low monthly plan with a clear usage cap, or a small credit pack, gives you room to learn without promising unlimited use. Record what each action costs you for a few months before you commit to a long-term structure. When you change prices later, keep early customers on their old terms for a set period so they do not feel punished for joining first.