SaaS Pricing Models in the Agent Era: Per-Seat Pricing Is Losing Its Anchor

What I keep noticing in software offers these days is that the price line changes more often than the feature list. Seats, credits, conversations, resolved cases: every vendor counts something different, and the unit can change in the middle of a contract term. Nobody trusts the counting anymore. SaaS pricing models are losing their common anchor, the price per seat.

Salesforce has tried three pricing logics for its agent platform in 18 months: $2 per conversation from October 2024, $0.10 per action from May 2025, and since late 2025 a user license starting at $125 per month². The agent business behind it reached a $1.2 billion annual recurring revenue run rate in the quarter ended April 2026, up 205% year over year¹. Among AI-native software companies, 83% already offer usage-based pricing⁵. The old default is visibly on its way out.

Why is per-seat pricing losing its anchor?

For three decades, the seat was a fair proxy for value. Software was operated by people, so more people meant more value and more licenses. Budgets were easy to plan, renewals were quick, and procurement knew exactly what to count.

In the agent era, that proxy breaks. An agent resolves support cases or qualifies leads without filling a single seat. The work still happens, it just stops showing up in the license count. That's also why the unit debate is so messy. What counts as a conversation when one customer query triggers eight backend processes²? What's a single action worth when it takes a whole chain of them to produce a useful result? Deloitte sees up to 75% as possible for 2026, against 39% that funded agentic AI in the preceding 12 months⁵.

The replacement is being tested in public. In a survey of 230 B2B software companies from May 2026, 37% already price hybrid, 29% have introduced a credit or token model, and another 33% plan to within 6 to 12 months⁴. Hybrid here means a predictable base fee combined with a usage component on top, and it's currently the most common answer to a question the market hasn't settled.

What do new SaaS pricing models mean for buyers and vendors?

Start with the vendor side, because that's where the pressure shows first. Expansion revenue used to ride on customers adding seats. In the routine work that agents absorb, seat counts flatten or fall. HubSpot drew the consequence in April 2026: two of its Breeze agents now cost money only when the result exists, $0.50 per resolved support conversation and $1 per lead recommended for outreach³. Outcome pricing shifts delivery risk to the vendor. You can carry that risk only if you own enough of the customer's workflow to influence the result, and if you can measure it cleanly.

Consumption models also rewire the finance mechanics. Revenue becomes a function of actual usage, forecasts get harder, and sales teams get measured on adoption. That's the squeeze behind the 37% hybrid figure⁴: companies want a plannable base and a usage engine that grows with the customer.

There's a budget-politics angle behind the vendor moves as well. SaaStr's read on the Salesforce reversal is blunt, the per-user license gives CFOs something they already know how to approve². Consumption line items compete with every other variable cost in the building, while a user license slots into a headcount-shaped budget. Anyone selling agents in 2026 is selling to that reflex as much as to any workflow.

Germany is no footnote here either. Bitkom's February 2026 study puts AI adoption at 36 percent of companies with 20 or more employees, double the 2024 figure, with 29 percent planning to raise their AI spending⁶. Every one of those companies meets the pricing question as a buyer first, long before it prices AI work of its own. That order matters: the terms they accept as buyers become the terms they later defend as vendors.

For buyers, a fixed cost block turns into a variable one. Gartner expects at least 40% of enterprise SaaS spend to shift toward usage-, agent-, or outcome-based pricing by 2030⁵. There's also a quiet double-payment risk. Contracts that combine a per-seat base with credits for agent work keep charging for both when agents take over routine seats, unless someone renegotiates the tiers. If you're renewing this year, you're negotiating units you've never budgeted before.

The upside for buyers is bargaining power. A vendor mid-migration needs reference customers on its new unit, and that buys pilot clauses, price caps, and switch-back rights that rarely existed under stable list prices. Procurement teams that treat the vendor's uncertainty as a negotiation window will get more out of this cycle than any volume discount used to deliver. That window closes once the new units settle into standard price lists.

A quick calculation shows what's at stake (my own math based on HubSpot's published rates³). A support team on 10 seats at $100 per month costs $12,000 a year. An agent resolving 4,000 conversations a month at $0.50 bills $24,000 a year. Outcome pricing can cost more than the licenses it replaces once volume grows, which is why every consumption or outcome contract needs a volume projection before anyone signs.

For investors and boards, the same shift creates a fresh diligence question. What share of recurring revenue sits on a unit the customer can actually budget, and what share rides on fluctuating consumption? Two companies with identical revenue can look very different through that lens, depending on how well their counting unit survives the next two years. This piece stays on the contract and pricing side. How the same question lands in the valuation of a software asset is covered in AI due diligence for software deals.

What we keep seeing at Convios is simpler than any model debate: most leadership teams can't say offhand which of their software contracts bill per seat, per device, per transaction, or flat. That list used to be trivia. Now it's the map of where the next renewal gets expensive.

How do you pressure-test your pricing model in four steps?

The same check works on both sides of the contract.

1. Build a contract inventory. List every product billed per seat and mark the areas where agents will absorb routine work over the next two years. That's where your seat counts will fall, and where tiers and exit windows belong on the negotiation table.
2. Run the value-metric test. Does your pricing unit count people or completed work? Can your customer budget the unit before signing? Can you measure the result you charge for? Three noes mean your model hangs on a number that's losing its meaning.
3. Put guardrails on consumption. Budget caps, alert thresholds, a contractually defined action unit and a monthly usage report belong in every credit contract, otherwise a pilot turns into an open-ended line item.
4. Convert one product first. As a vendor, pick the product with the most cleanly measurable result, learn forecasting and billing there, and only then widen the change.

My Take

My favorite comparison is the electricity bill. A standing charge for the connection, a working price for what you actually consume, and every household has budgeted that way for a century. Software is heading toward the same split: a base fee for access and platform, a working price for what agents get done. I expect the seat to survive as the standing charge, with the actual work priced separately.

Outcome pricing is the part I'd watch most closely, because it doubles as an honesty test. A vendor that can genuinely price the result owns the workflow and the measurement. Everyone else wears the label and bills consumption underneath. And honestly, the fact that the largest CRM vendor in the market added a user license on top after two consumption attempts² tells you how firmly CFOs insist on units they can budget. If I ran pricing at a software company right now, I'd spend more time defending the unit than the price level, because the unit is where the next two years of negotiations will be decided. Put a vendor's price sheets from the past two years side by side and you can watch that search happen. My bet is that more and more renewals will collapse into a single question, namely which unit even applies.

Which software business models survive the AI shift is the subject of our piece on business models under AI disruption. Why so many agent projects fail before production is covered in our analysis of AI agents in the enterprise. And how defensibility is built beyond the pricing model is the theme of the B2B SaaS castle article.

Sources

Have questions about this topic?