Will agents need licences?
A Microsoft executive suggested AI agents might be treated like human users for software licensing—meaning vendors could charge per agent 'seat' rather than per person—potentially reshaping SaaS economics. If adopted, that model would force companies to factor agent counts into licence costs and could reduce some expected productivity gains from automation. (businessinsider.com)
If software companies charge by the number of people using a product, one human with 20 artificial intelligence agents looks like a revenue problem. A Microsoft executive just floated the opposite idea: count the agents as users too. (businessinsider.com) The executive was Rajesh Jha, Microsoft’s head of experiences and devices, and the argument was simple: if an agent logs in, reads data, takes actions, and completes work, it starts to look less like a feature and more like another worker with a badge. (businessinsider.com) That hits the core of software as a service pricing. A company with 500 employees might buy 500 Microsoft 365 licenses today, because the basic unit is still a person sitting at a keyboard. (microsoft.com) Artificial intelligence agents scramble that math because one employee can supervise several bots at once. If the company cuts 100 human seats but adds 1,000 agents, vendors have to decide whether revenue falls, usage-based billing rises, or new agent seats appear. (businessinsider.com) Microsoft has been moving in this direction for months. Satya Nadella said in late 2025 that the company was starting to think less about charging “per user” and more about charging “per agent” as software begins serving both humans and artificial intelligence coworkers. (businessinsider.com) The timing is not random. Microsoft already sells Microsoft 365 Copilot as an add-on priced per user per month, and its enterprise pages now describe plans that bring chat, app assistance, and agents into the same work stack. (microsoft.com) Other software companies are testing different answers to the same problem. Salesforce’s Agentforce pricing page offers consumption-based charging, conversation-based charging, and per-user licensing, which shows the industry has not settled on one meter for digital labor. (salesforce.com) The fight underneath all this is about what an agent actually is. If an agent is just a smarter button inside software, customers will resist paying for a separate seat; if an agent has its own identity, permissions, audit trail, and workload, vendors have a stronger case for billing it like a named employee. (businessinsider.com) That identity piece matters because large companies already track who can open files, approve payments, and access customer records. Giving an agent its own account would fit existing security rules, but it would also make the agent easy to count on an invoice. (learn.microsoft.com) The awkward part for buyers is that automation was supposed to lower labor costs without blowing up software budgets. If every new agent needs its own license, some of the savings from replacing repetitive human work could flow straight back to Microsoft, Salesforce, Workday, and the rest of the software industry. (businessinsider.com) That does not mean every vendor will copy Microsoft’s logic. Some will push usage pricing, some will bundle agents into premium plans, and some will charge for outcomes, but the old idea that “seat” means “person” is now under direct attack. (salesforce.com)
