← All Articles
Sign in
SaaS Economics Blog

Per-Seat, Usage or Hybrid Pricing: How to Compare AI SaaS Quotes

By AI SaaS Radar Team · Nov 2026 · 5 min read

Two AI SaaS quotes are rarely priced in the same unit. One vendor charges per user, another per credit, a third per resolved conversation. To compare them, convert every quote into the same question: what would this cost us in a month of our own real usage, and what is the worst month? This guide shows the method, using three public price pages as worked examples. Prices below were read on 12 November 2026 and change often, so check each page before you decide.

Key facts

The three models in plain terms

Per-seat: you pay for each named user. The bill is predictable but does not follow how much work the AI does.

Usage: you pay for what the software consumes, counted in credits, tokens, actions or outcomes. The bill tracks activity, so it can outrun your budget.

Hybrid: a seat fee or platform fee for access, plus a usage allowance and a price for going over. Oliver Wyman's analysts describe hybrid models as combining seat minimums or platform fees for recurring revenue with usage mechanisms that grow with adoption. Our earlier piece on why per-seat pricing is breaking covers why vendors are moving this way.

Step 1: find the billing unit and what counts as one

Every quote hides a definition. Intercom's page says a Fin outcome is counted when a customer confirms the issue is resolved, when they do not ask for more help after Fin responds, or when Fin completes a workflow, including handoffs, and that you are charged once per conversation. That is not the same as "a resolved ticket", and the gap affects your bill.

Salesforce shows why the unit matters. Its page lists two ways to pay for the same agent: Flex Credits, or Conversations at $2 each. Our own arithmetic: at $500 per 100,000 credits, one credit costs $0.005, so a 20-credit action costs $0.10. A conversation that triggers more than 20 actions would cost more under Flex Credits than the $2 flat rate, and one with fewer would cost less. The page says the two cannot be used in the same org, so you choose one.

Step 2: price your own volume in each model

Take a month you know well and count the units. Then multiply.

These figures cover different jobs, so do not add them up. They show the pattern: a flat seat bill in one tool, a bill that scales with tickets in another.

Step 3: ask what happens at the limit

For any usage or hybrid plan, get the answer to four questions in writing.

Step 4: stress-test the bill

Oliver Wyman recommends that vendors stress-test margins at three and five times current usage. Buyers can use the same idea from their side. Multiply your expected volume by three and by five, recompute each quote, and see which one still fits your budget. A seat plan will barely move. A per-outcome plan will not. A flat price protects you if usage explodes, while a usage price protects you if adoption stays low.

The same research found that nearly two-thirds of current customers view usage pricing favorably, so the aim is not to avoid it. Take it with a cap, a clear unit and a tested number.

Step 5: compare on cost per result

Divide each monthly figure by something you value: tickets handled, documents processed, pull requests merged. A cheaper quote that needs more human review can cost more per finished task. Pilot identical work before you commit, and use the AI tool directory to shortlist candidates. More buyer guides are on our articles page.

What to do this week

Questions people ask

Is per-seat pricing always cheaper to predict?

It is easier to forecast, but it ignores how much AI work you use. Oliver Wyman notes that automation could shrink seat counts, which is why vendors add usage components.

What is a hybrid pricing model?

A base fee for access, usually per seat or per platform, plus a usage mechanism such as credits that you pay for as adoption grows.

How do I make a usage quote predictable?

Get a spending cap and a defined billing unit in writing, then test the bill at higher volumes. Oliver Wyman's authors recommend caps, true-ups and contractual flexibility.

Sources

Stay ahead of the AI SaaS market

Sourced, dated analysis on security, funding, and benchmarks. Straight to your inbox.

No spam. Unsubscribe anytime.