Is per-seat pricing dead for AI agents in 2026?
Short answer: not dead, just demoted. It still wins when a person is the one logging in. It breaks the moment your agent's output stops tracking headcount, and the fix isn't a raw meter either.
Worth building around, but only in a specific shape. Per-seat pricing still works wherever a human remains the primary user of the software. It breaks once an agent does work that no longer scales with your buyer's headcount, which is why Artisan's AI sales rep Ava and Intercom's Fin dropped seats for metered pricing, roughly 2 cents a credit rolling to 30 to 60 cents a lead, or $0.99 a resolved ticket. Raw usage billing has its own failure mode, though: real builders report it makes people use the product less. Bundle the meter into a prepaid credit, or you'll re-run the retreat Salesforce already made.
Is per-seat pricing actually dead for AI agents in 2026?
No, but it stopped being the default. maybe worth building has been tracking how the funded agent companies actually bill, not how their marketing pages describe it, and the pattern is consistent: seats survive exactly where a person is still the one opening the app. Artisan runs Ava, an AI sales rep that does the work of a BDR: finding leads, researching them, writing and sending outreach. A human BDR maxes out at some number of emails a day. Ava doesn't. Founder Jaspar Carmichael-Jack put it directly on More SaaStr in June 2026: he doesn't price her as a seat or a subscription, because a seat caps something that no longer describes what she does.
That's the actual mechanism, not a vibe. SaaS priced by seat because the product needed a human to log in and click around before it produced value, so counting logins was a reasonable proxy for value delivered. An agent removes the login. Once the thing doing the work isn't a person at a desk, "how many people bought access" stops correlating with "how much work got done," and the pricing model built on that correlation starts to misprice everyone. Underprice the buyer running one agent flat out, overprice the buyer running it lightly. Seats didn't get worse. The product they were built to measure changed underneath them.
Why does per-seat pricing break down once an agent does the work?
Watch what happened at Salesforce, because the company ran the experiment in both directions inside eighteen months. Agentforce launched in May 2025 with pricing at $2 per conversation, a straight usage bet: charge for the work, not the login. By December 2025, CEO Marc Benioff was telling investors the opposite lesson. "When we first started with Agentforce, we were talking about so much per conversation... but customers have pushed for more flexibility," he said, and that October Salesforce had already shipped the Agentic Enterprise License Agreement, folding agent credits back into a seat-shaped enterprise deal.
Salesforce didn't walk back the idea that agents should be priced on output. It walked back pure, granular, per-action billing, because its enterprise buyers wanted a number they could plan a budget around more than they wanted perfect fairness on every conversation. So "per-seat pricing is dying" is only half right. Billing by login count is dying. What's replacing it isn't a raw meter either. It's something in between.
What does that in-between pricing actually look like?
Artisan and Intercom arrived at nearly the same shape from opposite ends of the market. Artisan raised a $25M Series A led by Glade Brook Capital in April 2025, on top of an $11.5M seed, reporting roughly $5M in annual recurring revenue and 250 customers at the time. Ava bills by the action: about 2 cents a credit, stacking to roughly 30 to 60 cents per lead and a visible cost per meeting booked, so the customer sees exactly what each result cost. Ava 2.0, which shipped in May 2026, formalized this into what Artisan calls a credit-based model where "teams pay only for what they use."
Intercom's Fin, a customer-support agent, charges $0.99 per resolved conversation, full stop, no seats anywhere in the pricing page. Both companies picked a unit the buyer already tracks before AI ever entered the picture, a lead, a resolved ticket, not a raw API call or token count nobody outside engineering understands. That's the design choice doing the real work: meter something the buyer already believes in.
What's the catch with pure usage-based pricing?
It has its own failure mode, and it shows up in how people actually behave, not just in what they say they'd pay. A Hacker News comment from February 2026, on a thread about a different company's pricing change, laid out the mechanism plainly: "I feel like I'm spending money just by exploring... Every click feels billable. Every experiment feels risky. So people try less." The commenter, a builder shipping AI-heavy products, watched raw per-action billing quietly suppress usage even when the underlying economics were fine. Their fix was the same one Artisan and Fin landed on: "Credits turn invisible anxiety into something people can budget, plan, and mentally control."
Salesforce's retreat and this HN comment are describing the same problem from two different altitudes. One is a $300B company's enterprise sales motion, the other is one builder's honest read on why usage meters backfire. Both land on the same fix: don't show the customer a live number ticking down with every click. Sell them a bundle they can budget against, then meter quietly underneath it.
When is usage-based pricing worth building around?
- You can meter an action the buyer already values. A lead, a resolved ticket, a booked meeting. Not an API call or a token count nobody outside your own team understands.
- You wrap it in a prepaid, budgetable credit. Never a live meter tied straight to a card. That's the one design choice both Artisan and Fin made independently, and the one Salesforce had to relearn in public.
- Your buyer wants predictability as much as fairness. Enterprise procurement in particular will trade some precision for a number they can put in a budget line, so price that flexibility in from the start instead of bolting it on after a Benioff-style walk-back.
When does per-seat pricing still win?
- A human stays the primary user. If the AI makes a person faster rather than replacing what they do, the seat still maps to that person's judgment, not just to raw agent output.
- Your buyer explicitly wants budget certainty over granularity. Salesforce's own late-2025 retreat is the proof: enterprise buyers pushed a usage-first company partway back to seats.
- You can't instrument real outcomes cleanly. A metered price on a fake or noisy signal is worse than an honest flat seat. Don't meter for the sake of looking modern.
The test to run before you build on this
Run the same two-part check the engine runs on every idea. The space receipt: is a real, funded company already pricing this way and surviving on it? Yes, twice over. Artisan is doing roughly $5M in ARR on metered credits after a $25M Series A, and Intercom's Fin has scaled its resolution-based pricing across its whole customer support product. The pain receipt: can you find someone, in their own words, feeling the actual mechanism? Yes, the HN builder describing spend anxiety killing their own product usage, and Salesforce's own CEO describing the same pressure from the buyer's side eleven months later.
Here's the honest way this could be wrong: billing infrastructure like Stripe Billing, Metronome, or Orb could commoditize the credit-wrapping layer itself, turning outcome-based pricing from a hard design decision into a checkbox any SaaS bolts on. If that happens, the pricing shape stops being a differentiator, the same way free shipping did for ecommerce once every retailer offered it. The billing tooling won't decide which action to meter or how big to make the bundle before it starts feeling like a live meter again. Those two calls still have to be made by the founder, not the invoicing vendor.
Related: Is it worth building a vertical AI agent in 2026?, the workflow question this pricing question sits on top of. Also see Is it worth building an AI agent in 2026? for the harness-not-the-model test, and Is agent payments infrastructure worth building in 2026? for the billing rails sitting underneath all of this.
Frequently asked questions
Is per-seat pricing dead for AI agents in 2026?
Not dead, demoted. Per-seat pricing still works wherever a human stays the primary user of the software. It breaks once an agent's output no longer scales with your buyer's headcount, which is why Artisan's AI sales rep Ava and Intercom's Fin dropped seats for metered pricing. But raw usage billing has its own failure mode: it creates spend anxiety that makes people use the product less, which is part of why Salesforce partly retreated from its own usage-pricing bet in late 2025.
Why does per-seat pricing break down specifically for AI agents?
SaaS seats price the software by how many people log in, because a human had to open the app to get value from it. An agent doesn't need a login. One AI sales rep can run outreach around the clock at a volume no single human seat could match, so capping the plan by seats caps something that no longer reflects the work being done.
How does Artisan price its AI sales agent, Ava?
By the action, not the seat. Founder Jaspar Carmichael-Jack has described it as roughly 2 cents per credit, with each action Ava takes burning a credit that rolls up to about 30 to 60 cents per lead and a real, visible cost per meeting booked. Artisan raised a $25M Series A led by Glade Brook Capital in April 2025, on top of an $11.5M seed, and formalized the credit model with the May 2026 launch of Ava 2.0.
Why did Salesforce move away from pure usage-based pricing for Agentforce?
Salesforce launched Agentforce in May 2025 at $2 per conversation, a straight usage-based bet. By December 2025, CEO Marc Benioff told investors that customers had "pushed for more flexibility," and Salesforce introduced the Agentic Enterprise License Agreement that October, folding agent credits back into a seat-shaped enterprise deal. Enterprise buyers wanted predictable spend more than perfectly fair metering.
What's the actual problem with pure usage-based pricing?
It creates real spend anxiety. A Hacker News comment from a builder shipping AI-heavy products described it plainly: "I feel like I'm spending money just by exploring... Every click feels billable. Every experiment feels risky." People use a metered product less than a flat one, even at the same real cost, because every action feels like a purchase decision.
When should I still use per-seat pricing for an AI product?
When a human stays the primary user and the AI just makes them faster, the seat still maps to a person's judgment, not just to raw output. It also wins when your buyer explicitly wants budget predictability over granular fairness, the same reason Salesforce's own enterprise customers pushed back toward a seat-shaped deal.
What's the safest pricing shape for a new AI agent startup in 2026?
Meter an action that maps to a value your buyer already tracks, a lead, a resolved ticket, a booked meeting, not an arbitrary API call. Then wrap that meter in a prepaid, budgetable credit instead of a live ticking counter. That's the shape both Artisan and Intercom's Fin converged on independently, and it's the shape Salesforce is still relearning.
The free pack: 100 AI ideas actually worth building, each with the receipts and a clear verdict. No fake MRR screenshots.