Our view
The largest enterprise software vendors have started to report AI agents (software that plans steps and acts through tools) by how much customers consume, not by how many seats they buy, and that changes what a buyer is signing when a vendor sends forward deployed engineers (FDEs), engineers who work inside the customer's systems until the software runs in production.
An engineer whose employer is paid per unit of use is, in part, building the meter. Buyers in the US, UK, Europe, India and Australia should negotiate spending limits, ownership of the agents and an exit route before the work starts, not after the first invoice.
The quarter the Copilot count went quiet
Microsoft's results for the quarter to 30 September were strong on the usual measures: revenue of $92.3 billion, up 19%, with Azure up 48%. What was missing was a number. Asked directly on the earnings call, the chief financial officer said Microsoft "did not disclose" an update on the Copilot figure this quarter. Microsoft 365 commercial seats grew 5% year on year, slower than the 7% of a year earlier. Seat growth had run at 6% to 7% in each of the four previous quarters.
Microsoft 365 commercial seat growth, % year on year (Microsoft fiscal quarters; Q1 FY27 ended 30 September 2026)
Source: Microsoft Investor Relations, FY27 Q1 metrics, 2026-10-28
Instead, the chief executive led with usage. More than 50 million agents now sit in Microsoft's agent registry, and the number of Copilot customers consuming credits through usage-based billing grew by more than 75% in the quarter, as stated by the vendor. Neither figure came with a baseline.
The same pattern appeared across the market. Revenue at AWS, Amazon's cloud unit, rose 39% to $46.0 billion, and Amazon said its agent service, AgentCore, deployed twice as many agents in the third quarter as in the previous three quarters combined, as stated by the vendor. ServiceNow raised its 2026 target for annual contract value from AI to $1.7 billion and said consumption of agentic AI in production was up more than 13 times year to date, as stated by the vendor.
FDE AI reads this as a change of business model, not of vocabulary. A seat licence caps what a customer pays regardless of how hard the software works. Adding consumption billing alongside the licence, as Microsoft is doing for new Copilot Business licences, removes that fixed cap: what remains is a limit the customer has to set, and the vendor's revenue grows with every task an agent takes on.
The meter arrives by default on 1 December
The change is not only in investor presentations. Microsoft's partner announcements state that from 1 December 2026, usage-based billing will be enabled by default for new Microsoft 365 Copilot Business licences bought through Cloud Solution Provider partners, with a default limit of 4,000 Copilot Credits per user per month that administrators can adjust. The date was moved from 2 November. On Microsoft's own worked example, a firm with 100 such users could consume up to 400,000 credits a month under the default.
The rollout will initially exclude 11 markets, including Australia, India, France and Germany. For buyers there, the delay is time to set policy before the default reaches them. For firms buying new Copilot Business licences through partners in the US, the UK, Canada, Singapore, the Gulf and other markets not on the list, the window is one month.
- 13 OctoberAccenture and Workday launch an FDE programme
- 28 OctoberMicrosoft and ServiceNow results lead with usage
- 29 OctoberAmazon results: AgentCore deployments
- 1 DecemberUsage billing on by default for new Copilot Business licences bought through CSP partners
Source: Accenture, Microsoft, ServiceNow, Amazon; compiled by FDE AI
None of this makes consumption pricing wrong. Paying for work done can be fairer than paying for licences nobody opens. The point is that the unit of control has moved. Under seats, a buyer controlled cost by deciding who got a licence. Under consumption, cost is controlled by how agents are designed: how many steps a task takes, how often an agent retries, and which model it calls. Those are engineering decisions, usually taken on site, often by someone the buyer does not employ.
A default is a decision someone else has made for you. FDE AI reads the default spending limit as a ceiling the vendor considers reasonable, not one the customer has tested against a budget. Finance teams used to forecasting AI spend as seats multiplied by price will need a second line: expected tasks multiplied by credits per task, with a hard stop.
Who builds the meter
Vendors and their partners are also investing in the people who wire agents into a customer's systems. Accenture and Workday launched a joint forward deployed engineering programme on 13 October, describing engineers who work "within clients' actual processes, data, policies and controls" and feed what they learn back into the product. Anthropic has committed $100 million to train 10,000 engineers, which it calls Frontier Deployed Engineers, by the end of 2027, as stated by the company. (FDE AI is a paying customer of Anthropic and OpenAI, holds no shares in either company, and receives no free credits or commissions from either.)
The FDE model can work well. It also has a structural incentive built in, whatever the intentions of any particular programme. Where the engineer's employer is paid by consumption, the engineer who decides how many agents to deploy, how often they run and which model tier they call is shaping the customer's bill.
Analysts have raised a related concern. According to Techstrong.ai, Gartner expects up to 70% of enterprises to abandon agentic AI systems built through vendor-assisted models by 2028, as maintenance costs rise and internal teams struggle to change the technology on their own. The Register reported a Gartner analyst warning of lock-in and intellectual property risk in these engagements.
The services side may be next. Infosys reported that AI was 10.5% of its revenue and grew 29% on the previous quarter, while guiding to revenue growth of 1% to 2% for the year in constant currency. FDE AI reads that combination as one sign, among others, that buyers are moving spend towards AI-led work; if that work is priced by outcome or usage, clients in the UK, US and Australia who buy from Indian IT firms are likely to see the same meter appear in services contracts.
Assumptions and risks
This view rests on three assumptions: that the usage figures vendors highlighted this quarter reflect a lasting shift in how they price agents; that vendor engineers have real influence over how agents are configured once deployed; and that those engineers work for, or alongside, a vendor whose revenue rises with consumption. The 1 December default applies to Copilot Business, which Microsoft offers to small and medium-sized businesses. FDE AI expects the incentive argument to matter most in larger engagements, where on-site engineers are more common.
The strongest counter-argument is that consumption pricing protects buyers: they pay only for what they use, and a seat licence for software nobody opens is the worse waste. That is true for light users. FDE AI holds its view because the vendors' own disclosures emphasise growth in consumption, not savings, and because the default spending limit is set by the vendor.
The usage multiples cited here are vendor claims without published baselines. Gartner's forecast is cited as reported by Techstrong.ai.
Impact on enterprises
Small and mid-sized firms buying Microsoft 365 Copilot Business through partners outside the excluded markets face the most immediate change, because the usage-billing default applies to new Copilot Business licences from 1 December. The effect lands first in budgeting: AI spend becomes variable, and a successful pilot can raise the bill rather than settle it. It lands second in procurement. Contracts for forward deployed engineering need terms that most statements of work do not yet contain: who owns the agents and prompts built on site, who controls consumption limits, what usage reports the vendor must provide, and how the customer takes over or leaves. Firms in Australia and India have a grace period, of a length Microsoft has not announced, before the default reaches them. Firms buying from Indian IT services providers may see usage and outcome pricing raised at renewal.
Impact on FDE professionals
Vendors and consultancies are training and fielding more engineers who deploy agents inside client systems, which FDE AI reads as a bet that demand will keep growing. The skill that will set people apart is cost engineering: designing agents that finish a task with fewer calls, choosing cheaper model tiers where they are good enough, and showing the client a usage forecast they can defend to their finance team. Engineers employed by vendors that are paid on consumption face a potential conflict of interest that clients will increasingly ask about; those who can document how they kept consumption in check may find it easier to get hired. Independent and client-side FDEs gain a new role as the person who audits the vendor's deployment. None of this guarantees a job or a pay level.
Recommended actions
Enterprises
- Before 1 DecemberReview the default limit
IT and finance leads at firms buying Copilot Business through a partner outside the excluded markets should, before 1 December, review the default limit of 4,000 Copilot Credits per user per month, set a lower per-user limit where usage does not justify it, and name the person who approves increases. IT leads in Australia, India and the other excluded markets should decide their per-user limit and approver now, before the default reaches them.
- This quarterFour clauses in every FDE contract
Procurement teams signing any forward deployed engineering engagement this quarter should add four clauses: client ownership of agents, prompts and configuration; client control of consumption limits; monthly usage reports by agent; and a handover plan with a named internal owner.
- 2027 budgetForecast tasks, not seats
Finance teams preparing 2027 budgets should forecast agent spend as expected tasks multiplied by credits per task, and set a threshold at which a pilot must be reviewed before it scales.
FDEs and engineers
- First week on siteAgree a usage forecast
FDEs starting a client deployment should, in the first week, agree a usage forecast with the client's finance contact and report actual consumption against it every month.
- Before handoverDocument model tier choices
Engineers building agents on consumption-priced platforms should, before handover, document which model tier each agent uses and why, so the client can lower cost without rebuilding.
What to watch
If Microsoft, AWS or ServiceNow publish usage metrics with baselines or unit prices in their next results, buyers will be able to compare costs, and this view on the need for contract protections would soften; if they continue to report multiples only, it would strengthen.
Baselines would soften the viewIf Microsoft extends the usage-billing default to Australia, India and the other excluded markets in early 2027 without changing the default limit, the view that the vendor sets the ceiling would strengthen.
Wider rollout would strengthen itIf Gartner, buyers or regulators report enterprises abandoning vendor-built agents at scale in 2027, the case for client ownership and exit terms would strengthen; if abandonment stays rare, FDE AI would revise towards treating vendor FDEs as low-risk.
Abandonment would strengthen it
Sources
- Microsoft|Microsoft announces first quarter results ↗ · Originally published:
- Microsoft Investor Relations|Microsoft Fiscal Year 2027 First Quarter Earnings Conference Call ↗ · Originally published:
- Microsoft Investor Relations|FY27 Q1 Metrics ↗ · Originally published:
- Microsoft Learn|October 2026 announcements, Partner Center announcements ↗ · Originally published:
- Amazon.com, Inc.|Amazon.com Announces Third Quarter Results ↗ · Originally published:
- ServiceNow|ServiceNow Reports Third Quarter 2026 Financial Results ↗ · Originally published:
- Accenture|Accenture Launches Forward Deployed Engineering Program with Workday to Reinvent Work for the Agentic AI Era ↗ · Originally published:
- Anthropic|Anthropic invests $100 million to train 10,000 engineers and tackle the enterprise AI talent gap ↗ · Originally published:
- Infosys|IFRS USD Press Release Q2 FY27 ↗ · Originally published:
- Techstrong.ai|Gartner warns 70% of vendor-built AI agent projects face abandonment by 2028 ↗ · Originally published:
- The Register|Vendors asking forward deployed engineers to make good on trillion-dollar AI bet ↗ · Originally published:
This article sets out FDE AI's analysis and views. It does not constitute professional investment, legal, accounting, tax, labor or hiring advice. Disclaimer