This also creates a governance test many organisations are not ready for. Usage-based charging is only manageable if non-human identities, agent actions and workflow volumes are observable enough to audit. Otherwise, enterprises risk replacing shelfware with a different problem: opaque automation spend that scales faster than controls. The commercial conversation therefore cannot be separated from identity governance, policy enforcement and telemetry design.
For IT leaders, the practical question is not whether seat-based pricing disappears everywhere, but where outcome or consumption pricing is acceptable and where predictability still matters more. A sensible decision framework includes:
- whether usage can be tied to a measurable business process or unit outcome;
- whether agent activity can be attributed to an accountable owner or cost centre;
- whether the platform exposes enough operational data to support budgeting and policy controls;
- whether spend volatility is tolerable compared with the simplicity of fixed licensing.
Vendors may present usage pricing as alignment with value, but buyers should test whether the meter reflects real business benefit or merely another proxy for activity. In the AI era, pricing model selection becomes part of enterprise control design, not just procurement negotiation.
Software pricing has always worked like office rent: Count the people who need access, charge per head, done. Per seat, per user, per month. Simple, auditable, defensible in a procurement review.
That model worked when humans were the only workers in the system. AI agents have changed that.
The seat never fit the work
Today’s enterprise runs on more than human workers: Service accounts automate workflows. Bots execute tasks. AI agents process requests, access systems and take action around the clock. They have no badge, no login, no seat.
Industry data puts non-human identities at anywhere from 25 to 50 times the number of human users in an average enterprise. Those systems do real work and consume real resources. They require governance, but none of them has a seat license.
Most enterprises still budget for software based on head count and planned employee growth. But agents — not humans — are now the fastest-growing group in most environments. That creates a structural problem: The activity driving real value inside the platform is not the activity the pricing model is designed to measure.
When you price software by head count and the workforce increasingly has no head, you get a disconnect between what you pay for and what you actually get. That assumption is collapsing.
Two traps buyers fall into
Per-seat pricing creates two failure modes. Most organizations live in one of them.
The first is shelfware. Licenses sit idle because team members only occasionally use the platform, yet they still need licenses. You pay for potential usage. Finance notices. IT leaders get uncomfortable questions in budget reviews.
The second failure mode is access restriction. To avoid the shelfware problem, teams limit who gets a license. The platform’s value gets capped. You bought a tool to solve a problem, then rationed access to make the math work.
Both traps have the same root: a pricing model disconnected from the work being done.
What happens when pricing reflects reality
The shift to usage-based pricing is usually framed as a vendor story. That misses the more important question: What changes for the organization buying the software?
The first change is organizational alignment. Seat-based models obscure an urgent question: Who actually owns the AI consumption budget? Is it IT? Operations? Finance? When cost is tied to activity, that question has a real answer. You can see which teams are driving usage, where value is being created, and who should be accountable for the spend.
The second change is governance. You monitor human workers; you should be able to monitor AI workers the same way. Usage-based pricing surfaces the data that makes that possible, telling you what ran, when, at what volume, against which policies.
The third is economic alignment. When agents are your primary users, the value of a platform is no longer about how many employees have access. It is about what the platform enables those agents to accomplish. Pricing built around consumption starts to reflect that. What you pay for maps to what you get.
What happens if enterprises don’t make this shift? The current model does not just become inaccurate; it actively works against AI adoption. Every new automation carries a licensing cost. Procurement cannot see where value is created because the pricing model wasn’t built to show it. Organizations end up optimizing for licensing efficiency instead of business outcomes, meaning the incentives run backward.
The future of work is not a head count story
Cloud infrastructure was priced on consumption two decades ago, and databases followed. API platforms charge per call. The pattern holds: Measure the value, price accordingly. Enterprise software has been the laggard; that is changing.
AI has fundamentally changed the relationship between people and work. For decades, enterprises measured software value by counting users. Now, meaningful work is performed by automations that do not collect a paycheck or occupy a seat. The question is no longer how many people log in, but what gets accomplished.
Companies that adapt will no longer measure software success by who or what logs in, but by what gets accomplished. The rest are still counting seats in a world that has moved on.
How is your organization adapting software pricing for the AI era? Share your insights: [email protected].
Enjoyed this article? Sign up for our newsletter to receive regular insights and stay connected.