Insights

What should AI cost my business in year one?

For chief financial officersVerified July 2026

Far less than a transformation, and far more than the licence fee. The gap between those two numbers is where most AI budgets go wrong. The per-seat price is what everyone quotes, because it is the number a vendor puts in front of you. It is also the smallest line in the true cost of getting value from AI in the first year. Budget only for the licences and you will either underspend and get no adoption, or overspend on seats nobody uses.

The cost structure below covers the whole thing, so you can budget for it rather than for the visible tip.

The licence is the cheap part

A business AI plan runs roughly the price of another productivity subscription per person. That is real money at scale, but it is not the expensive part, and treating it as the budget is the classic mistake. The tool makes value possible. Capturing that value takes the work around it: enabling your people, wiring it into your systems, and governing how it is used. Fund the licence alone and you have bought the possibility and none of the delivery.

The four cost lines

Budget across four lines, not one.

Cost line What it covers Rough weight in year one
Tools & licences Per-seat plans, API usage, any platform fees The smallest line, and the only one most budgets include
Enablement & change Training, adoption support, redesigning how work is done Usually the largest line, and the most forgotten
Integration & data Connecting AI to your systems, readying the data it draws on Varies most: trivial for off-the-shelf use, significant for grounding AI in your own data
Governance & risk Policy, EU AI Act work, security review, oversight Modest but non-optional; skipping it is a false economy

The exact split depends on what you are doing, but the shape holds: the line you can see (licences) is rarely the line that costs the most.

The hidden line: change and adoption

The single most under-budgeted cost is getting people to actually use the thing. A tool that is bought and not adopted returns nothing, and adoption does not happen for free. It takes training, support, and the redesign of how the work is done around what the tool now makes possible. Firms that budget for licences and skip enablement reliably reach the worst outcome: full cost and no return, plus a verdict that "AI didn't work for us" when what didn't work was the budget.

If you cut one line, do not let it be this one.

Budget for outcomes, not seats

The temptation is to buy licences for everyone and hope value follows. It rarely does, and you end up paying for hundreds of seats with a handful of active users. The better shape is to fund a narrow, high-value use properly, all four cost lines included, prove it pays back, then let the returns fund the next expansion. That turns AI from a fixed cost you are hoping to justify into an investment that earns its own scale-up, which is a far easier number to defend.

A sensible year-one shape

For most mid-market companies, a defensible first year looks less like a platform rollout and more like a focused programme: a modest licence spend, a larger enablement and change spend, whatever integration your chosen use genuinely needs, and a small but real governance line, all aimed at one or two uses that pay back rather than a wall-to-wall deployment. Start there, measure it, and let the evidence set the second-year budget.

The headline for the board: the useful question is what it costs to make one valuable use actually pay back, and whether the budget covers all four lines of that or only the one on the invoice.

Get the year-one number right, across all four cost lines and pointed at a use that pays back. That costing sits inside the board-ready roadmap Firestarter produces in six weeks.

Sources and verification. This guide describes the general cost structure of adopting AI in a mid-market business as of July 2026. It gives proportions and structure, not a quote; actual figures depend heavily on your tools, scale, and integration needs, so build your own numbers against current vendor pricing and your specific use before you set a budget.

  • Risk & security lead

    How is shadow AI affecting my company?

    Shadow AI, the use of unapproved AI tools by employees, has become one of the fastest-growing data-governance risks for mid-market firms. A risk manager's guide to detecting it and protecting the business.

    Read the guide

  • Risk & security lead

    Does AI train on my business data?

    Whether an AI provider trains on your business data depends almost entirely on which plan you buy. A risk manager's guide to the safe tiers across Anthropic, OpenAI, Google, and Microsoft.

    Read the guide

  • Risk & security lead

    Which AI is right for my company?

    A cost and risk comparison of AI from Anthropic, OpenAI, Google, and Microsoft for business: API and per-seat pricing, plus which fits a manufacturing, financial services, or software company.

    Read the guide

  • Risk & compliance lead

    Does the EU AI Act apply to my company?

    The EU AI Act reaches companies well beyond the EU, and several of its obligations are already live. A risk lead's guide to whether you are in scope, which tier your AI use falls into, and the deadlines that matter.

    Read the guide

  • Risk & compliance lead

    What does an AI policy need to say?

    A good AI policy fits on a page and gets followed. A risk lead's guide to the essentials: approved tools, the data line that matters most, disclosure, and accountability, without the forty pages nobody reads.

    Read the guide

  • Chief financial officer

    Why do AI pilots fail to pay back?

    Most AI pilots never reach production, and fewer still return value the board can see. A CFO's guide to why AI pilots stall short of payback, and the four things the ones that pay back do differently.

    Read the guide

  • Chief executive

    How do I build a board-ready business case for AI?

    A board funds a decision it can vote on. A chief executive's guide to the four things an AI business case must contain (value, cost, risk, and the ask) and how to size it so the board can act.

    Read the guide

  • Change & people lead

    Why do employees resist AI?

    AI adoption stalls on people rather than technology. A change lead's guide to the four real reasons employees resist AI, why training alone doesn't move them, and what actually changes behaviour.

    Read the guide

  • Chief executive

    How AI-literate does my leadership team need to be?

    Leaders need enough AI literacy to make good decisions, without learning to build. A chief executive's guide to what a leadership team actually has to understand, why it's now a legal duty too, and how to get there.

    Read the guide

  • Chief operating officer

    How AI-ready is my organisation, really?

    AI readiness is more than data and tools. A COO's guide to the five dimensions that decide it (leadership, people, data, process, and governance) and an honest way to score your own.

    Read the guide

  • Board & executive

    Who owns AI risk in a mid-market company?

    In most mid-market firms, AI risk falls between IT, legal, and the business, so it belongs to everyone and no one. An executive's guide to assigning ownership without hiring a Chief AI Officer.

    Read the guide

  • IT & data lead

    Is my data ready for AI?

    Whether your data is ready for AI depends entirely on what you ask AI to do with it. An IT lead's guide to the four things that actually matter, the permissions trap that catches everyone, and where to start.

    Read the guide

  • Operations lead

    What is an AI agent, and what should we automate first?

    An AI agent does more than answer: it takes actions across steps and systems. An operations lead's guide to what agents actually are, where they help and where they don't, and how to choose what to automate first.

    Read the guide

  • Technology lead

    Should we build or buy AI agents?

    For most mid-market companies, building AI agents from scratch is the wrong instinct. A technology lead's guide to the build-buy-configure spectrum, the hidden cost of building, and a pragmatic default.

    Read the guide