From OpenNova.
Many enterprise applications have traditionally been priced around the number of people using them. Companies purchase access for employees, negotiate subscription agreements and plan around relatively predictable licensing costs. CRM, ERP, service management and productivity platforms have long relied heavily on versions of this model.
Usage-based technology spending isn’t new. Companies have paid for cloud infrastructure, data processing and API services based on consumption for years. What is changing is that similar charges are appearing inside business applications traditionally associated with user-based subscriptions, tied to the activities AI agents perform.
Salesforce sells Agentforce per user or by consumption, with agent activity measured in credits. Microsoft bills Copilot agent usage in Copilot Credits and gives administrators tools to allocate the cost to departments, set budgets and monitor consumption. A Microsoft 365 Copilot license is not required.
Traditional subscriptions aren’t disappearing. But companies now have additional ways to pay for AI capabilities based on the work performed, rather than solely on the number of employees with access.
Seat-based pricing gives companies a relatively predictable cost tied to licensed access. With consumption-based pricing, the bill also depends on how much work the software performs. Once an agent is deployed, its activity can generate additional charges. Those costs depend on how frequently it runs, the complexity of the tasks and the capabilities it uses. The same agent is cheap in a quiet month and expensive when volume spikes or the workflow gets messy.
Comparing products becomes harder when vendors charge for different kinds of activity. One may bill for individual actions, another for conversations, and another through credits tied to consumption. A company evaluating two products needs to understand what each will actually cost to complete the work, not just compare subscription prices.
The tools to see the spending exist, from Microsoft’s departmental billing policies to the budget alerts and chargeback models many companies already use for cloud. But knowing where a charge originated is not the same as having decided who is accountable for it. Depending on the organization, IT may manage the platform, a business unit may control its use, and another group may oversee the budget or vendor agreement. The usage report does not establish how those responsibilities should be divided.
Before that spending grows, someone needs to establish who is responsible for it. Who signed for this?
If you are working through a decision other technology leaders could learn from, we’d like to hear it. A sentence or two is plenty: hello@opennova.com. We’ll ask before publishing anything you share.
The Pulse comes out every other Thursday, with the enterprise technology developments we think are worth your attention. Get The Pulse.