Agents as paid seats

A Microsoft executive is floating a simple idea with a big invoice attached: if an artificial intelligence agent does the work of a worker, it may need its own software seat instead of riding free on a human’s login. Business Insider reported the comment this week as Microsoft pushes companies to treat agents less like features and more like digital staff. (businessinsider.com) That sounds abstract until you remember how enterprise software is usually sold. A company might buy 10,000 Microsoft 365 seats because it has 10,000 employees, and the budget math is built around human headcount. (microsoft.com) Artificial intelligence agents break that model because one employee can spin up several task-specific bots. A sales manager could have one agent drafting emails, another updating customer records, and a third preparing meeting notes, which means software usage can grow faster than payroll. (learn.microsoft.com) Microsoft has been inching toward this for months. Chief Executive Officer Satya Nadella said on the Dwarkesh Podcast in late 2025 that Microsoft was rethinking pricing from “per user” toward “per agent,” which is the clearest sign yet that the company sees agents as a billable unit, not just a product feature. (businessinsider.com) The company’s product lineup is already moving in that direction. Microsoft announced in March 2026 that Agent 365 would be generally available on May 1 for $15 per user, while the new Microsoft 365 E7 bundle would launch at $99 per user per month with agent governance and control built in. (blogs.microsoft.com) Microsoft’s current agent billing is still a mix of seat licenses and usage meters. Its Copilot Studio licensing guide says organizations need to forecast agent consumption with “Copilot Credits,” which means some agent costs already behave more like cloud computing than like old software subscriptions. (learn.microsoft.com, microsoft.com) Microsoft is not alone here. Salesforce says Agentforce can be priced by consumption, by conversations, or by per-user licensing, and its help documentation has listed a $2 price for each conversation under one payment model. (salesforce.com, salesforce.com) That is why this debate is really about who pays when software starts doing labor. If a finance team deploys 500 agents that work across customer support, procurement, and legal, the old question of “how many employees need access” turns into “how many digital workers are we willing to fund.” (businessinsider.com, salesforce.com) Inside companies, that changes chargebacks as much as vendor contracts. Information technology departments that once split costs by employee count may start billing business units by agent count, agent usage, or task volume, which makes artificial intelligence adoption look less like buying software and more like hiring a variable workforce. (learn.microsoft.com, microsoft.com) The risk for customers is that agent economics can balloon quietly. A company that replaces one $30-per-month tool with ten low-friction agents may discover that “automation savings” disappear once every agent needs a seat, credits, storage, security controls, and audit logs. (microsoft.com, blogs.microsoft.com) The prize for software vendors is just as obvious. If agents become a standard budget line like employees, the biggest software companies do not lose revenue when humans stop clicking through menus; they just sell the same stack to a new class of worker that never sleeps. (businessinsider.com, salesforce.com)