// BLOG / AI PRICING
Usage-Based vs Seat-Based Pricing for AI Products
Short answer. Seat-based pricing charges a fixed price per user. Usage-based pricing charges for what the product consumes. For AI, seat-based decouples revenue from the variable cost of compute, so the better and stickier your product gets, the worse your margin gets. Usage-based ties price to cost, which is why most AI products should price on usage or a hybrid of both.
This is the pricing decision that quietly decides whether an AI business has a future. Get it wrong and you can grow revenue while your gross margin collapses underneath you, which is the worst kind of growth because it looks like success on the way down. The reason is structural, and it comes down to one thing traditional software never had to price for: cost that moves with every use.
The structural difference
Classic SaaS has near-zero marginal cost. One more user on a seat costs you almost nothing, so seat-based pricing works: revenue goes up, cost barely moves, margin is fine. AI breaks that assumption. Every inference call burns real compute, and your most engaged users burn the most. Under seats, those power users pay the same flat price while consuming many times the cost, so your best, stickiest customers are the ones quietly eroding your margin. That is the full argument in AI pricing has to respect compute reality. Usage-based pricing fixes it by making revenue move with cost, so growth and margin stop fighting each other.
Side by side
| Dimension | Seat-based | Usage-based |
|---|---|---|
| You charge for | Number of users | What the product consumes (calls, tokens, compute, actions) |
| Revenue vs cost | Decoupled; cost rises with use, price does not | Coupled; price tracks the variable cost |
| Margin at scale | Erodes as power users consume more | Holds, because heavy use pays for itself |
| Predictability for the buyer | High; one fixed number | Lower; the bill moves with use (mitigate with tiers or caps) |
| Best fit | Stable usage per seat, compute a small share of price | Variable usage, compute a real share of cost to serve |
| AI fit | Risky alone | Default, often as a hybrid |
The hybrid most AI companies should run
Pure usage-based pricing has one real weakness: buyers dislike an unpredictable bill, and a meter with no ceiling can stall a deal in procurement. The answer most durable AI companies land on is a hybrid. A platform fee that covers the relationship and a baseline of usage, plus metered consumption above it, often with tiers or a cap so the buyer is never surprised. That keeps revenue tied to cost where it matters while giving the buyer the predictability they need to sign. The full structure, including how to price the baseline before a raise, is in how to price an AI product before Series A.
The test
You can settle this for your own product in one question: do your best customers cost the most to serve? If yes, your pricing has to capture that, and seats alone will not. If usage per seat is genuinely stable and compute is a small, predictable slice of the price, seat-based can survive. For almost every AI product, the honest answer points to usage or a hybrid.
Frequently asked questions
What is the difference between usage-based and seat-based pricing?
Seat-based pricing charges a fixed price per user, regardless of how much they use the product. Usage-based pricing charges for what the product actually consumes, such as API calls, tokens, compute, or completed actions. Seat-based revenue is predictable but disconnected from cost. Usage-based revenue tracks cost and scales with the value delivered.
Why is seat-based pricing risky for AI products?
Because AI has a real, variable cost per use that traditional software does not. Under seat-based pricing your heaviest users run up the biggest compute bill while paying the same flat price, so the better and stickier your product becomes, the worse your gross margin gets. Seat-based pricing decouples revenue from cost, and at scale that gap shows up as margin erosion.
Should AI startups use usage-based or seat-based pricing?
Most AI products should price on usage, or a hybrid of a platform fee plus usage, so revenue tracks the variable cost of compute. Pure seat-based pricing fits only when usage per seat is stable and the compute cost is a small, predictable share of the price. If your best customers cost the most to serve, your pricing has to capture that, and seats alone do not.
About the author
Jeff Brokaw is a Certified Chief AI Officer and technical-commercial operator who rebuilds the commercial layer of technically complex companies and ships AI in production, not slideware. He ran the commercial side of two media companies tied to more than $850M in associated exits, co-founded the AI fintech FaaStrak and took it from zero to $1M ARR in nine months, and authored and drove the go-to-market behind a $114M institutional raise that came together in under 30 days.