Seat-based SaaS pricing rests on one quiet assumption: marginal cost is approximately zero. One more user, one more login, no meaningful change to your cost of goods. Twenty years of SaaS economics — the 80% gross margins, the land-and-expand playbook, the per-seat upsell — sit on top of that assumption.

AI features break it. Every generation, every retrieval, every agent step has a real unit cost, and that cost scales with usage, not with seats. Your most engaged customers — the ones every SaaS playbook tells you to celebrate — become your most expensive to serve. Pricing is no longer a go-to-market decision that product hears about later. It is a product architecture decision, and product leaders who treat it as someone else's spreadsheet will ship features that lose money at their moment of greatest success.

The three ways SaaS teams get it wrong

1. Bundling AI into existing seats

The path of least resistance: fold the AI features into current plans, call it product velocity, hope the retention lift covers the cost. Sometimes it does — briefly. Then a segment of power users discovers the feature, usage follows a power law (it always follows a power law), and your gross margin quietly bleeds out through the top decile of accounts. Worse, you have now taught the market that intelligence is free, and the first repricing conversation arrives after the anchor has set.

2. Pure usage metering

The opposite reflex: meter everything, pass the cost through, stay safe. Economically clean, behaviorally poisonous. A visible meter makes every use of the feature a small purchasing decision, and users respond the way they respond to all metered utilities — they conserve. Adoption stalls precisely where you need habit formation. You protected your margin on a feature nobody learned to rely on.

3. The bolt-on AI SKU

Packaging every AI capability into a single “AI add-on” tier feels tidy and demos well in a pricing deck. But it fragments value: workflow features that belong in the core product get held hostage to an upsell, sales teams discount the SKU to close, and the capabilities inside it never integrate deeply because they must remain detachable. An add-on is a packaging decision masquerading as a strategy.

Price the outcome where you can, the workflow where you must, and the token never. Customers don't buy inference. They buy finished work.

A packaging ladder that follows value

The pattern I recommend to SaaS leadership teams is a ladder with three rungs, each matching how much of the job the AI actually completes:

  • Assistive (included in seats). Copilot-style features that make a human faster inside your existing workflow — drafting, summarizing, suggesting. Include them. Their job is retention and differentiation, their cost per seat is bounded because a human is the throttle, and withholding them just invites a competitor to make them table stakes. Watch the margin, set generous-but-real fair-use ceilings, and move on.
  • Workflow (hybrid: platform fee + metered band). Features that complete a defined unit of work with light supervision — processing a document, triaging a ticket, generating a report. Price them per unit of work in bands: a platform fee that covers a healthy allotment, then predictable tiers. The unit must be one the customer already counts — documents, tickets, campaigns — never tokens or credits they have to learn.
  • Outcome (agent pricing). Agents that own a job end to end are not features; they are digital labor, and the comparison price in the buyer's head is a salary or a BPO contract, not a software line item. Price against the outcome — per resolved case, per qualified lead, per closed book month — with quality-linked terms. This is the rung where the margin structure of your company actually changes, and it deserves CFO-level partnership, not a pricing-page tweak.

The margin discipline behind the ladder

None of the ladder works unless someone owns the unit economics at the workflow level, and in an AI-era SaaS company that someone is product. Three numbers per AI feature, reviewed monthly:

  • Cost per completed task — fully loaded: inference, retrieval, retries, the failure paths. Demo-path cost is fiction; power-law users and retry storms are where the money goes.
  • Gross margin at the current price point — per rung, per segment. “Blended margin looks fine” is how the top decile eats you.
  • Cost trajectory — model prices fall, but your usage mix shifts toward heavier tasks as trust grows. Model both curves; the second one is usually steeper.

A note on credits, because every pricing meeting eventually proposes them: credits are a transitional currency, useful when your unit of work is still unstable. They buy flexibility at the cost of comprehension — every credit balance is a small anxiety generator, and customers who cannot predict their bill discount the product to compensate. Use credits to learn the real unit of work, then retire them into the ladder. A credit system that persists past year two is a pricing decision you are refusing to make.

Five questions before your next AI pricing decision

  • What unit does the customer already count that this feature maps to?
  • What is the fully loaded cost per completed task at the 90th-percentile account, not the median?
  • Which rung of the ladder is this — and are we pricing it on that rung, or on the rung that is easier to sell?
  • If usage grows 10x in our best accounts, does gross margin hold above the line the CFO signed up for?
  • What price anchor are we setting for the agentic version of this feature two years out?

Seat pricing is not dead — assistive AI arguably strengthens it. But the era when product could ship value and let finance find the price is over. In AI-era SaaS, the pricing model is part of the product architecture. Leaders who internalize that will fund their own compounding. Leaders who don't will discover their most successful feature is also their most expensive mistake.