Usage-Based or Per-Seat Pricing for a SaaS With AI Features? A Decision Guide for 2026
Charge per seat when AI helps each user work faster. Charge by usage when AI does the work itself. Use a hybrid when both are true. Here's how to decide.
If your AI features help each person do their job faster, charge per seat. If your AI does the work itself and the output grows without more people, charge by usage. If both are true, charge per seat with a usage allowance and a clear overage. Then test the version you pick with buyers before launch. RightPrice does that test in minutes.
The old per-seat versus usage debate assumed your costs were flat. AI changed that, because every AI action costs you money. So the choice now has two sides: what your buyer values, and what each heavy user costs you.
Test your pricing model in RightPrice before you commit to it on the pricing page.
Who this is for
You're launching or repricing a SaaS product where AI features are part of the value. Maybe it's an AI writing assistant inside a team tool, an agent that processes documents, or a copilot for a specific job. You have to pick a pricing model and you're stuck between seats and usage.
If your product has no AI costs and you want the general comparison, read B2B SaaS pricing models explained.
What's the one question that decides it?
Ask this: when your customer gets more value, do they add people or do they run more jobs?
- A sales team that gets more value from an AI call-notes tool hires more reps. Value follows headcount. Per seat fits.
- A finance team that gets more value from an AI invoice processor feeds it more invoices. The team stays the same size. Value follows volume. Usage fits.
When value follows volume and you charge per seat, your best customers pay the same as your lightest ones while costing you far more to serve. When value follows headcount and you charge by usage, buyers start rationing the product to control the bill, which kills adoption.
How to choose, step by step
- Name what the AI does in one sentence. "Helps a rep write follow-ups faster" is assistive. "Writes and sends follow-ups on its own" is autonomous. Assistive points to seats. Autonomous points to usage.
- Estimate your cost for a light, typical and heavy user. Count AI calls per user per month and multiply by your current cost per call. Write down all three numbers.
- Check the spread. If a heavy user costs you many times what a typical user costs, flat per-seat pricing will lose money on your best customers. You need a usage component.
- Pick a usage unit the buyer understands. Buyers don't think in tokens. They think in documents, conversations, reports, minutes of audio. Charge in the unit they'd count, and convert to your cost behind the scenes.
- Decide how predictable the bill has to be. Buyers with a fixed budget, often in larger companies, want a number they can approve once. Give them a plan with an included allowance. Buyers who start small and grow are fine paying as they go.
- Write the hybrid if you need it. For example, a per-seat price that includes a monthly allowance of AI actions, with a fixed price for extra packs. Seats keep the bill predictable. The allowance protects your margin.
- Test the whole model along with the number. Show buyers the full pricing structure and see which part they question.
Which model fits which AI product?
| How the AI creates value | Example | Model that fits | Watch out for |
|---|---|---|---|
| Speeds up each user | AI drafting inside a team workspace | Per seat | Heavy users eating your margin. Add a fair-use cap |
| Does the work with no extra people | Document extraction, AI agents running tasks | Usage | Bill anxiety. Show a calculator and a monthly cap |
| Both | A support tool with agent seats plus an AI that answers tickets alone | Seat plus usage allowance | Too many moving parts. Keep it to two numbers |
| AI is a small add-on | Summaries inside a project tool | Per seat, AI included | Don't add usage billing for a minor feature |
A worked example
For example, say you sell an AI tool that reads supplier contracts and flags risky clauses for small legal teams.
- One lawyer can review 20 contracts a month or 200. The team doesn't grow when volume grows. Value follows volume.
- Illustrative costs: a light user runs 10 contracts and costs you $2 a month. A heavy user runs 300 and costs you $60.
- Per seat at $49 makes money on the light user and loses it on the heavy one.
So you test two structures:
- Usage: $2 per contract, no seats.
- Hybrid: $79 per seat including 50 contracts, then $1.50 per extra contract.
When you test them, you're listening for whether buyers can predict their bill. A legal team head who has to get a budget approved may prefer the hybrid even if usage would cost them less, because the hybrid gives them a number to put in a budget.
What goes wrong after launch, and how to fix it
| Symptom | Likely cause | Fix |
|---|---|---|
| A few accounts make your gross margin negative | Flat seats with expensive AI usage | Add an allowance per seat and charge for extra |
| Trial users stop using AI features before paying | Usage billing makes them ration | Include a free allowance during the trial |
| Buyers ask "what will this actually cost me?" on calls | Usage unit is too abstract | Switch to a unit they count, add a cost estimator |
| Big accounts want a fixed annual price | Procurement needs predictability | Offer an annual commit with a usage pool |
If your AI costs keep moving, read how to price an AI SaaS when your model costs keep changing.
How to test it with RightPrice
Put your pricing structure into RightPrice exactly as a buyer would see it: the seat price, the allowance and the overage. Describe your target buyer. RightPrice builds personas for that audience, including a skeptic and a buyer who's comparing you to competitors, and they discuss the offer while you watch.
Run one simulation for the per-seat version and one for the usage or hybrid version. Compare the confidence scores, the willingness-to-pay analysis and, most useful here, the objections. If buyers keep asking how the bill could change, you have a predictability problem. If they say "I'd pay per seat but not for AI on top," your AI isn't yet seen as the core value.
A Quick run takes about 10 minutes and uses 1 credit. Use it as a first read, then take the winning structure into real buyer conversations.
FAQ
Is usage-based pricing better for AI products?
Only when the AI does work that grows without more people. If your AI helps each user do their job, per seat is simpler to sell and simpler for buyers to budget.
Should I charge separately for AI features?
Charge separately when the AI is a distinct job buyers would pay for on its own. If it's a convenience inside your main product, include it and protect your margin with a fair-use limit.
Should I show prices in tokens or credits?
Show them in the unit your buyer counts, like documents or conversations. Credits work when you have several AI actions with different costs, as long as you tell buyers what one credit gets them.
Can I switch from per seat to usage later?
Yes, but every existing customer's bill changes, and some will pay more. It's easier to start with a hybrid that has a usage component from day one.
Your next step
Estimate what your light, typical and heavy user costs you per month in AI calls. If the heavy number is many times the typical one, build a hybrid. Run both structures through RightPrice and keep the one your buyers can explain back to you. For the broader model choice, see how to choose a SaaS pricing model.