AI adoption

Nobody Budgeted for AI Usage Pricing For decades, enterprise software budgeting followed a simple rule. You pay per seat, per month. Ten licences cost ten times one licence. The number is fixed, predictable, and easy to forecast a year out. AI broke that rule quietly, and a lot of finance teams have not caught up yet. A Different Kind of Cost Entirely Most AI tools — the ones built on large language models — do not charge a flat fee for unlimited use. They charge based on consumption. Every prompt processed, every token generated, every agent action taken carries a cost, and that cost scales directly with how much the business actually uses the tool. This sounds like a minor technical detail. It is not. It is a fundamentally different financial model, closer to a cloud computing bill than a software licence — and cloud computing bills are notorious for exactly the kind of surprise finance teams are now discovering with AI. A team that budgeted for what looked like a reasonable monthly AI spend based on a pilot programme can find their actual bill has multiplied several times over within two quarters — not because pricing changed, but because usage did. The tool worked. People used it more. And the invoice reflected every single interaction. Why the Bill Grows Faster Than Anyone Expects The pattern shows up consistently across enterprises adopting AI at scale, and it follows a predictable shape even though almost nobody predicts it in advance. Early adoption looks cheap. A small team pilots a tool. Usage is light, contained, and the monthly cost is genuinely modest. Finance builds a budget line based on this number, reasonably assuming it will scale in a straightforward, linear way as more people start using it. Then adoption succeeds — and that is exactly when the maths stops being linear. Success means more employees using it more often, for more complex tasks, with longer conversations and larger volumes of data processed per interaction. An AI agent that made a handful of decisions during a pilot might be making thousands of decisions a day in full production. Each one carries a cost. None of those individual costs looks alarming. The sum of them, at scale, often does. Agent-based systems compound this further. A single customer service agent might make several API calls to complete one customer interaction — understanding the request, retrieving relevant data, drafting a response, checking it against policy. What looks like one interaction to the business is several billable actions to the system underneath it. When the Number Genuinely Rivals a Salary This is the part that catches finance teams off guard hardest. In high-usage scenarios, the AI cost for automating a role can approach — and in some documented cases exceed — the cost of the human role it was meant to make more efficient. This does not mean the AI investment was a mistake. It usually still delivers value beyond just labour cost — speed, availability, consistency, scale that a human role could not match regardless of price. But it means the original business case, often built on a simple comparison of AI subscription cost versus salary cost, was measuring the wrong number from the start. The right comparison was never “what does the tool cost per month.” It was “what does the tool cost per unit of actual usage, and how does that scale as adoption grows.” Why This Matters for How Enterprises Plan Finance teams that have run budgets on fixed software costs for years are applying that same mental model to AI spend, and it does not transfer. A usage-based cost structure needs usage-based forecasting. That means understanding not just what a pilot costs today, but modelling what the cost looks like at ten times the usage, fifty times the usage, and at whatever scale the business is actually targeting if the rollout succeeds. Most AI business cases skip this step entirely, because it requires technical usage data that finance teams do not typically have visibility into and do not know to ask for. It also means building monitoring into the AI deployment itself, not just the budget. Usage-based costs can spike without warning — a viral product moment, a seasonal surge, an internal team suddenly using an agent far more heavily than expected. Without real-time visibility into usage and cost, that spike shows up as a surprise on an invoice week later rather than a trend finance could have managed proactively. What Enterprises Getting This Right Are Doing The organisations avoiding this shock are treating AI cost the way mature companies treat cloud infrastructure cost — as a variable operating expense that requires active management, not a subscription line item that gets budgeted once a year and left alone. That means setting usage alerts and spending caps at the platform level before scale-up happens, not after a surprising bill arrives. It means involving finance in the technical scoping of AI projects early enough to model realistic cost curves rather than pilot-stage costs extrapolated naively. It means building cost-per-outcome metrics — what does it actually cost to resolve one customer ticket, process one transaction, generate one report — so the organisation can evaluate AI spend against the value it produces rather than against an arbitrary monthly number. And it means having the conversation between technology and finance leadership early, before the AI rollout scales, rather than after the board asks why the AI line item tripled in a single quarter. The Bottom Line AI usage-based pricing is not a temporary quirk of early-stage AI vendors. It is the pricing model for the category, and it is not going away as adoption matures — if anything, it becomes more consequential as usage grows. The enterprises that build their financial planning around this reality now are the ones who will scale AI adoption with confidence. The ones still budgeting for it like a traditional software licence are the ones heading toward an uncomfortable board conversation