Per-Seat Pricing Is on Borrowed Time.
Per-seat pricing is not dead. In AI-native categories, it is on borrowed time.
A seat prices access to a human doing work. That held for twenty years because humans were the bottleneck. When the software does the work, the seat stops measuring anything, and a price that does not track value cannot hold.
I direct agents. I do not manage people. A company running five humans and five hundred agent-hours a day cannot be metered by five seats. The seat count is now noise.
Per-seat is doomed, not dead. It survives tool SaaS. It breaks for AI-native. Not if, but when your category crosses the line.
Will per-seat pricing go away?
Not everywhere, and not soon. In AI-native categories, yes.
Start with what a seat actually is. A seat is a proxy for one person's labor. You charge for the login because the login is where the work happens, and more logins mean more work and more value captured. The proxy was honest as long as people did the work.
AI breaks the proxy. When the marginal unit of work comes from an agent instead of a person, headcount and value separate. Now per-seat does one of two things, and both are wrong. It overcharges the customer for idle seats nobody logs into, or it undercharges the customer who runs ten thousand automated tasks through three seats. Either way the meter has stopped reading the thing you are selling.
Why does the seat work for tool SaaS but break for AI-native?
One question settles it. Who, or what, does the next unit of work?
If a human does it, the seat is fine. Figma, Salesforce, Notion: a person logs in and produces something, so more people means more value, and per-seat tracks it cleanly. The product is a power tool. Value scales with the hands swinging it.
AI-native inverts that. The product is not the tool. It is the worker. Value scales with work produced, and work produced is no longer tied to how many people you employ.
I built Orbyt solo in 32 days, now over 425,000 lines and 11,372 tests, for about $400 in model spend, because agents did the labor instead of a fifty-person team. Price that company by its seats and you would charge it like a lemonade stand while it ships like a department. One operator now produces the output of fifty. The seat cannot see that.
Here is the trap AI-native vendors walk into. Per-seat is familiar and easy to forecast, so they keep it. Then a customer cuts seats while tripling automated output. Revenue falls as the value you deliver rises. That gap is the doom, and it shows up in the renewal, not the demo.
A meter that punishes you for delivering more value is not a pricing model. It is a leak.
What replaces the seat: usage, outcome, or hybrid?
Three successors, and which one fits depends on how cleanly you can measure value.
Usage pricing meters the work consumed: tokens, runs, tasks, documents. It fits when work is countable and value rises roughly with volume. The risk is the invoice nobody can predict, and finance hates a surprise. Caps, commitments, and a live dashboard fix most of that.
Outcome pricing charges for a result: a placement, a filing, a closed ticket. It commands the highest willingness to pay, because you are selling the value, not the effort. The risk is attribution fights, and margin exposure when your cost is per-run but your price is per-result.
Most durable AI-native businesses land in the middle.
| Model | Charges for | Best when | Watch out for |
|---|---|---|---|
| Usage | Work consumed (runs, tasks, tokens) | Value rises with volume | Unpredictable bills; cap and meter |
| Outcome | Verified results (a placement, a filing) | You can attribute the result | Attribution fights; margin if cost is per-run |
| Hybrid | A platform floor plus a meter on top | You want predictability and upside | More to explain; instrument both sides |
The decision rule is short. Can you cleanly attribute the result to your product? Lean outcome. Is value linear with volume but attribution fuzzy? Lean usage. Selling into regulated, risk-averse buyers? Lead with a platform floor so the bill never shocks them. We learned that pricing discipline building regulated software, and it holds.
How do you know when your category crosses the line?
Run three checks. Two yeses and the seat is already lying to your pricing.
One, architecture. Remove the AI from your product. If what is left still works, you are a tool with AI bolted on, and the seat is fine for now. If the product collapses without the model, you are AI-native and the seat is on borrowed time. It is the same load-bearing test from the AI-native diagnostic.
Two, labor. Is the next unit of work done by an agent? If your customers are deleting seats while doing more, the meter is already broken.
Three, revenue signal. Plot value delivered against seats sold. As long as the lines move together, per-seat is honest. The day they diverge, you are leaving money on the table, and a competitor who prices on usage will reach across and take it.
There is a clock on this. The vendor who switches the meter before the category forces it captures the automated-usage upside first. Wait too long, and a new entrant prices on outcomes, calls you overpriced and underpowered, and is not wrong.
What a CTO or founder can do Monday
You do not need to rip out per-seat this quarter. You need to start measuring value now so you can price it later.
Instrument consumption today, even while you still bill per seat. You cannot price usage you never logged. Count tasks, runs, documents, agent-hours.
Find your value metric. Ask one question: what number goes up for the customer when your product works? That number, not headcount, is your future meter.
Pilot a hybrid on one segment. Keep a platform floor for predictability, add a metered layer on top, and watch margin and churn for a quarter. Building Norhart's $70M investment platform and taking Taxa to $113M taught us the same thing: in regulated buying, predictability sells, so lead with the floor.
Protect your margin. If your cost is usage-based model spend and your price is per-seat, your heaviest automated users are quietly eating your gross margin. Match the price axis to the cost axis before a power user does that math for you.
Per-seat is not a villain. It is a meter that fit a world where people did the work. That world is narrowing.
Price the work, not the login.
Related reading:
- Are You Actually AI-Native? The Test the architecture test that decides whether your seat is on borrowed time
- The Rise of Small AI-Native Companies why one operator now out-ships fifty
- AI Is Not a Feature. It Is an Organizational Decision. pricing is one consequence of going AI-native
- The Token Bill Is the New Payroll. the cost side of the same ledger: what you pay for the work agents do
Originally published on justinbartak.ai on Jul 23, 2026.
Common questions
Will per-seat pricing go away?
Not everywhere, but in AI-native categories it is on borrowed time. Per-seat works when a human logs in to do the work, so seats track value. When software does the work, headcount and value decouple, and the seat stops measuring anything. Usage and outcome pricing take over as the category crosses that line.
What pricing model replaces per-seat for AI-native products?
Usually a hybrid: a fixed platform fee plus a metered layer for usage or outcomes. Pure usage pricing meters consumed work like tasks or runs. Outcome pricing charges for results like a placement or a filing. The hybrid wins most often because it gives finance predictability while capturing upside from heavy automated usage.
How do I know if my product should switch off per-seat pricing?
Run three checks. Remove the AI: if the product collapses, it is AI-native. Look at the marginal worker: if an agent does the work, the seat is the wrong unit. Plot value delivered against seats sold: when those lines diverge, the seat is underpricing your value and a usage-priced competitor can undercut you.
Why does per-seat pricing still work for traditional SaaS?
Because a human logs in and does the work, so value scales with the number of humans. Figma, Salesforce, and Notion get more valuable as more people use them to produce more output. The seat is an honest meter there. AI-native products break that link, because one operator directing agents produces what used to take a team. [Read the full article](https://justinbartak.ai/blog/per-seat-pricing-ai-native-usage-based) or fetch the [markdown source](https://justinbartak.ai/blog/per-seat-pricing-ai-native-usage-based.md).
Related research
- Building Orbyt, Part 4: The Numbers Don't Lie Data, Mar 2026.
- AI-Native Development, By the Numbers Data, Aug 2026.
- Every Fable Has a Moral. Mine Has Data. Experiment, Jun 2026.
