Pricing and packaging AI in a per-seat world

Why seats and AI do not mix

For twenty years, SaaS pricing was elegant. You paid per user (a "seat"), and each seat cost the vendor almost nothing to serve. A Slack user who sent 10 messages cost about the same as one who sent 1,000. Marginal cost was near zero, so seat pricing printed money.

Inference (the compute cost of running an AI model to generate an answer) changes the math. Every AI feature you ship has a variable cost per use, usually measured in tokenstokensA token is the basic unit of text that language models process, often a word fragment, whole word, or punctuation mark rather than a single character.Voir la définition complète → (the chunks of text a model reads and writes, roughly 3/4 of a word each).

Two customers on the same plan can now have wildly different costs to serve:

• A sales rep who asks an AI assistant to draft 5 emails a week.
• A rep who runs 50 AI-summarized call transcripts a day, each one thousands of tokenstokensA token is the basic unit of text that language models process, often a word fragment, whole word, or punctuation mark rather than a single character.Voir la définition complète →.

Under flat seat pricing, the heavy user is subsidized by the light user. When AI adoption is low, you absorb it. When adoption scales, and it always scales faster than you expect, your margins bleed.

The margin problem, concretely

Say your blended AI feature costs roughly $0.02 per action in model fees (an illustrative figure). At 200 actions per user per month, that is $4 of cost on a seat you may be selling for $30. If your target gross margingross marginGross margin is the share of revenue left after subtracting the direct cost of producing goods or services, expressed as a percentage of revenue.Voir la définition complète → is 75 percent or higher (typical for healthy SaaS), a single feature can eat a meaningful slice of it before you count support, hosting, or the rest of your product.

The trap: usage is not evenly distributed. A small fraction of "whale" users often drive the majority of consumption. Flat pricing means you cannot charge those whales more, but you still pay for them.

The pricing models on the table

There is no single right answer. There is a spectrum, and each point trades off simplicity against margin protection.

1. Pure seat pricing (the old world)

Simple, predictable for the buyer, easy to forecast. But it exposes you fully to variable AI cost. Only safe when AI usage is light or capped hard.

2. Pure usage pricing (consumption)

Charge per unit consumed: per tokentokenA token is the basic unit of text that language models process, often a word fragment, whole word, or punctuation mark rather than a single character.Voir la définition complète →, per query, per document processed. This is how the underlying model providers (OpenAI, Anthropic, Google) charge you, so it passes cost through cleanly.

The problem: buyers hate unpredictable bills. A procurement team cannot approve a line item that might be $2,000 one month and $9,000 the next. Usage-only pricing also punishes adoption, exactly the behavior you want to encourage.

3. Hybrid: seat plus usage (the emerging default)

This is where most successful AI SaaS is landing in 2026. The structure:

• A seat or platform fee for baseline access and predictability.
• Included usage bundled into that fee (a credit allowance).
• Overage or add-on packs when a customer exceeds the allowance.

The buyer gets a predictable floor. You get a mechanism to charge heavy users more. Margins are protected because usage above the allowance is priced to cover incremental inference cost plus markup.

Notion, GitHub Copilot, and many CRMCRMCustomer Relationship Management: software and strategy to manage and analyse customer interactions throughout their lifecycle.Voir la définition complète → vendors have shipped versions of this: a base subscription plus AI capabilities gated by credits, tiers, or add-on seats.

Designing the hybrid model

Step 1: Know your cost to serve per action

You cannot price what you cannot measure. Instrument every AI call. Log tokenstokensA token is the basic unit of text that language models process, often a word fragment, whole word, or punctuation mark rather than a single character.Voir la définition complète → in, tokenstokensA token is the basic unit of text that language models process, often a word fragment, whole word, or punctuation mark rather than a single character.Voir la définition complète → out, model used, and mapmapUsing software to automate repetitive marketing tasks and campaigns, enabling personalisation at scale across channels like email, web, and social.Voir la définition complète → it to a customer. This is the single most important operational change AI forces on a SaaS finance team.

A simplified logging record looks like this:

Aggregate this and you can see your true gross margingross marginGross margin is the share of revenue left after subtracting the direct cost of producing goods or services, expressed as a percentage of revenue.Voir la définition complète → per customer, per feature, and spot the whales before they become a problem.

Step 2: Choose a metric the buyer understands

Do not bill customers in raw tokenstokensA token is the basic unit of text that language models process, often a word fragment, whole word, or punctuation mark rather than a single character.Voir la définition complète →. TokensTokensA token is the basic unit of text that language models process, often a word fragment, whole word, or punctuation mark rather than a single character.Voir la définition complète → are an internal engineering unit; buyers cannot reason about them. Translate to a value metric the customer already cares about:

• "AI actions" or "credits"
• "Documents summarized"
• "Reports generated"
• "AI-assisted tickets resolved"

The best value metric scales with the value the customer receives, not just your cost. If more usage means more value to them, they will accept paying more.

Step 3: Set the allowance and the overage

Bundle enough included usage that the typical customer never thinks about limits. This keeps the experience feeling like flat SaaS for the 80 percent. Then set overage pricing that comfortably covers your marginal inference cost with margin on top.

Watch the gross margin floor. Price overage so that even at unlimited consumption, you never sell AI below your cost to serve. This is your insurance policy against runaway usage.

Step 4: Protect against abuse and surprise

• Rate limits per user prevent a single script or power user from generating catastrophic bills.
• Soft caps with alerts warn customers before they blow past their allowance, avoiding angry surprise invoices.
• Model routing: send simple requests to a cheaper, smaller model and only escalate to expensive frontier models when needed. This can cut inference cost substantially without the customer noticing.

For a deeper primer on how model providers price the inputs you resell, see OpenAI's pricing documentation, which shows the per-tokentokenA token is the basic unit of text that language models process, often a word fragment, whole word, or punctuation mark rather than a single character.Voir la définition complète → structure your costs inherit.

🎬 [VIDEO: "How to Price AI Products" — https://www.youtube.com/results?search_query=how+to+price+ai+products — Overview of usage-based and hybrid pricing strategies for AI features]

Packaging: how you present it matters as much as the price

Pricing is the number. Packaging is how you bundle and name it. Two moves matter most.

Do not make AI a separate line item customers can decline. If AI is a checkbox add-on, budget owners will cut it in a downturn. Weave AI into the core tiers so it becomes part of why customers stay. Reserve add-on packs for genuine overage, not baseline access.

Use tiers to segment by usage intensity. A "Pro" tier with a modest AI allowance and an "Enterprise" tier with a large allowance lets customers self-select into the cost band that matches their behavior. Heavy users naturally migrate up.

Communicating change to existing customers

If you already sell flat per-seat and now need to add usage components, this is a sensitive migration. Customers reasonably fear a price increase disguised as "innovation."

Practical guidance:

• Grandfather generously at first. Give existing customers a large included allowance so most feel no change. This buys goodwill and time.
• Frame usage as value, not tax. "Your team ran 12,000 AI actions last month" reads better than "you owe overage."
• Show the dashboard before you show the bill. Give customers visibility into their consumption for a full billing cycle before any charge applies. Surprise is the enemy of retention.

The companies handling this well treat usage transparency as a feature, not a threat. A customer who can see and manage their consumption trusts the pricing more than one who is kept in the dark.

The forecasting challenge for your own business

One underappreciated consequence: your cost of goods sold now moves with customer behavior, not just your headcount or infrastructure choices. Finance teams used to forecasting flat hosting costs must now model variable inference as a function of adoption curves. Build scenarios for low, medium, and high AI adoption, and stress-test your margins in each. If a viral spike in usage would break your unit economics, you have a pricing problem, not a demand problem.

Key Takeaways

• Seat pricing assumes flat cost to serve; AI inference destroys that assumption. A single power user can turn a profitable seat unprofitable.
• Instrument cost per AI action before you price anything. You cannot protect a margin you cannot measure per customer and per feature.
• Hybrid (seat plus included usage plus overage) is the emerging default. It gives buyers predictability while letting you charge heavy users more and defend a gross margingross marginGross margin is the share of revenue left after subtracting the direct cost of producing goods or services, expressed as a percentage of revenue.Voir la définition complète → floor.
• Bill in a value metric the customer understands (credits, actions, documents), never in raw tokens, and weave AI into core tiers rather than as a cancelable add-on.
• Manage migration with transparency: grandfather existing customers, show consumption dashboards before invoices, and frame usage as value delivered.