Most AI budget questions get answered at the wrong altitude. *What does an agent cost* has a specific answer. *What should our AI line item be for the year* is a different question, and it's the one a CFO is actually asking.
For a 20-to-500-person company getting serious in 2026, a realistic first-year AI budget lands between $75,000 and $300,000 all-in — and the way it's split matters more than the total, because the split is what determines whether year two builds on year one or starts over.
Why the total is smaller than you'd fear
The number that scares people is the model bill, and it's a rounding error: processing ten thousand conversations on a fast model costs about $37 (Anthropic), and the price of a given capability level has been falling roughly 40× per year (Epoch AI, 2025). You are not buying compute. You are buying engineering, integration, and someone to operate the result.
The number that *should* scare you is waste. 95% of enterprise generative-AI pilots deliver no measurable P&L impact (MIT Project NANDA, 2025), so the dominant risk isn't overspending — it's spending correctly-sized amounts on things that never reach production.
A first-year split that works
| Line | Share | Typical first year |
|---|---|---|
| Diagnose — find the workflow, prove it | 10–15% | A fixed-price sprint |
| Build — one or two production systems | 50–60% | Flat-fee per system |
| Operate — keep them working | 25–30% | Monthly, starts at go-live |
| Contingency | 10% | The integration you didn't know about |
Two things about this split surprise people.
Operate is a quarter of the budget, not an afterthought. A system nobody watches degrades silently — models get deprecated, data drifts, someone changes the workflow — so an unoperated build is a depreciating asset with a roughly one-year half-life. We put real numbers on this in why AI systems break after launch. Budget it from go-live or you'll fund it from next year's build money.
Diagnose is small but load-bearing. Ten percent spent proving which workflow deserves the other ninety is the cheapest insurance available. Our AI Transformation Sprint is $25,000 and ends in a deployed pilot rather than a document, which is the version of diagnosis worth paying for.
Sizing it against your revenue
A useful sanity check rather than a rule: mid-market companies getting real value are typically committing 1–3% of revenue to AI in the first serious year, weighted toward the build. Below about 1% you generally can't fund a production system plus its operations, and you end up with a pilot — the most expensive outcome available, because it costs real money and returns nothing.
Above 3% in year one usually means buying more surface area than the organisation can absorb. The constraint is rarely money; it's how many workflows you can change at once without the change management collapsing. 91% of mid-market firms use generative AI but only 25% have it integrated into core operations (RSM, 2025) — that gap is an absorption problem, not a budget one.
What year two looks like
If year one worked, year two is cheaper per unit of value and shaped differently: operate grows because you're running more systems, build stays flat or drops because the integration groundwork is done, and diagnose shrinks to near zero because you now know your own workflow inventory.
If year one didn't work, year two is identical to year one — which is the actual cost of getting it wrong. Not the wasted budget: the wasted *year*, spent re-learning what a properly scoped first engagement would have told you in two weeks.
Build the number for your business
Start from the workflow, not the budget. Find the one already costing you 15+ hours a week, model the return, and let the build cost fall out of that rather than allocating a round number and looking for somewhere to spend it. Then add operations from day one and a real contingency.
Our prices are published — a Gigabit Agents build is a flat fee from $8,000 per agent, the Sprint is $25,000, managed operations run $3,000–$20,000 a month — so you can assemble a defensible annual figure without a single sales call. If the arithmetic on your first workflow doesn't clear, that's a useful answer too, and how to calculate the ROI honestly will tell you before you commit.
