Pricing for AI Products

Per-seat is dead and you can stop pretending

The data is clear and has been for about a year. Companies still pricing AI per-seat in 2026 are running gross margins 40 percentage points below companies that moved to hybrid or outcome-based pricing. The market figured it out. Customers figured it out. Most PMs are still building roadmaps assuming the seat count is the lever, because that's what the 2018 SaaS playbook said.

The 2018 playbook was written for a world where marginal cost was zero. That world is over.

Why per-seat breaks

Per-seat pricing optimized for predictability. Customer knew what they'd spend. Sales knew what to forecast. Finance knew what to model. It priced access to a tool in a world where the tool's cost-to-serve was negligible.

Now cost-to-serve is the largest line item on my COGS, and it scales with what the user does, not whether they have a license. A power user at $50 a seat might cost me $200 a month to serve. A dormant seat costs me $50 and earns me the same. I'm subsidizing my power users with my dormant ones, until the power users add a few more, the subsidy collapses, and my gross margin disappears in a single quarter.

The customer figured this out faster than I did. They're buying fewer seats and using them harder. Seat count goes down as usage goes up. That's the death spiral.

The four models that work now

Hybrid: base fee plus usage. A floor that covers fixed costs and basic access. Usage on top that scales with a value-aligned metric. Adoption jumped from 27 percent to 41 percent of AI software companies in a single year. This is the safest move from per-seat. Customers tolerate it because the base is predictable and usage is "fair."

Outcome-based. You charge when the agent succeeds. Customer pays per resolved support ticket, per successful translation, per document processed, per qualified lead. Highest alignment between price and value. Hardest to instrument. Highest pricing power if you can pull it off, because the customer is paying for the result they would have hired a human to deliver, at a fraction of that cost while you still earn a software margin.

Tiered consumption. Customers buy a bucket of usage units up front, with overage at a higher rate or a forced tier upgrade. Familiar to anyone who's bought a cell phone plan. Predictable bill, predictable revenue, easy to sell. Mediocre value alignment but still better than seats.

Pure usage. Pay for what you use, no minimum. Strongest alignment with cost-to-serve, worst predictability. Use this only when you have a genuine self-serve product where churn is low because value is concrete every time. Most B2B SaaS doesn't have this and pure usage will burn you on evaluator customers.

Picking the value unit is the actual hard work

Most teams pick the wrong unit and discover six months later that customers are optimizing against it.

Bad value units:

• Tokens. Customers don't think in tokens. Bills feel arbitrary.
• API calls. Customers batch to avoid charges and break the product.
• Compute time. Punishes customers for using your product.

Good value units:

• Successful outcome. A resolved ticket, a closed deal, a published article, a translated document.
• Active workflow run. The agent did the thing. Customer paid. Failed runs don't bill (non-negotiable; bill on failure once and the customer never trusts you again).
• Document, conversation, or session. Discrete, value-coherent, easy to count, easy to explain.

The litmus test I use: can the customer tell me, before signing, what 100 of my value units would do for them? If yes, the unit is right. If no, I'm pricing on something they don't understand and I'll churn them on their first big bill.

The instrumentation requirement

You can't price what you don't measure. Before I change pricing on anything, I need:

• A defined "successful outcome" for every billable surface.
• Real-time tracking of outcomes per customer, per workspace.
• Cost-per-outcome telemetry (so I know margin per unit, per customer).
• A billing system that can ingest usage and reconcile to invoices.
• A customer-facing dashboard so they see usage in real time.

The last one is the trust contract. Customers will accept usage pricing if and only if they can see usage as it happens. Surprise bills are the killer. Build the dashboard before you change the price.

How to migrate without losing the book

You can't just switch pricing. You'll lose half your accounts at renewal. What works:

1. Grandfather existing customers. Their pricing stays. Stop selling that pricing to new customers the same day.
2. Sell hybrid to all new accounts. Watch the unit economics for a full quarter.
3. Offer existing customers an opt-in to the new model with a discount. Many move because the new model is cheaper for them at their usage. The ones who would pay more either stay grandfathered or churn. You learn who was unprofitable.
4. Re-price expansion seats and new modules on the new model only. Within 18 months, half your revenue is on the new model without a single forced migration.

Skipping step 1 is how companies make headlines for "raising prices." Be slow on migrations, fast on new-customer pricing.

The outcome-based endgame

The endgame for most AI products is outcome pricing. The economics are unbeatable: perfect alignment with the customer, competitors look like rent-seekers, and I can capture a fraction of the value I create, which is much larger than cost-plus margin allows.

Path I run: start with hybrid (base plus usage on a value-aligned unit). Tighten the value unit until it's an outcome, not an action. Add an SLA on the outcome (success rate). Charge premium pricing on the SLA tier. Within two product cycles, you've moved a meaningful surface to outcome pricing without a marketing campaign about it. The customer just sees a product that works and a bill that feels fair.

Pick one thing this week

Don't redesign your pricing page. Do this instead.

1. For one billable surface, write down the value unit the customer actually cares about. Not tokens. Not API calls. The thing they came to get.
2. Instrument that unit. Start tracking it today, even if you don't use it in billing yet.
3. Pull your top 10 customers by revenue. Calculate what they'd have paid on the new unit over the last 90 days versus what they actually paid. Find the outliers.
4. You'll find two patterns: customers you're under-pricing (high usage, low revenue) and customers you're over-pricing (low usage, high revenue). That asymmetry is your pricing redesign, sitting in front of you.
5. Sketch what a hybrid model would look like. Share with your CFO. Watch the conversation get a lot more concrete.

In an AI product, you don't price the seat. You price the work the seat is no longer doing.