Budgeting for AI: one-off, recurring and hidden costs
AI budgets fail because they contain one line. The three columns a real budget needs, and the hidden items that appear in month four.
The short answer
AI budgets fail in a predictable way: they contain one line, the project, and the project is approved. Then month four arrives with usage bills, a model update that needs retesting, documents that need refreshing, a quality review nobody scheduled, and a team that has spent forty hours reviewing exceptions. None of it was in the line. A real AI budget has three columns: the one-off build, the recurring running costs for the life of the system, and the hidden costs in your own people’s time and in organisational change. Size the first year across all three, and hold a reserve for the second project the first one will reveal.
The three columns
| Column | What is in it | When it appears |
|---|---|---|
| One-off | Discovery, data preparation, integration, build, evaluation, guardrails, launch | Before and at launch |
| Recurring | Model usage, hosting, monitoring, monthly quality review, document refresh, retests after model updates, small changes | Every month, for the life of the system |
| Hidden | Experts labelling cases, staff reviewing exceptions, procedure rewrites, training, adoption dip, management attention | Mostly in the first six months, some forever |
The hidden items, in hours
- Labelling the evaluation set: your best people, a few hours each, once, plus additions monthly.
- Reviewing exceptions: daily in the pilot, tapering as the gate widens; estimate the first six months.
- Rewriting the procedure and training the team: a few days of someone’s time.
- The adoption dip: two to four weeks of lower output while people learn.
- Owning it: someone reads the monthly sample, the guardrail log and the cost report. An hour or two a month, forever.
- Managing the vendor or partner: meetings, decisions, approvals.
Sizing the first year
Build cost from a proposal that shows integration, data work, evaluation and guardrails, not just “AI”. Twelve months of running costs from a usage estimate at expected volume, plus hosting, monitoring and a monthly review. People time in hours, valued honestly. Add a reserve: the first project always reveals a second, usually the process next to it, and having budget ready is what turns a win into momentum. The total is the number to approve. The build alone is the number that gets you to month four.
What this means for you
Budget in three columns, not one. Build, running for the life of the system, and your own people’s time. Size the first year across all three, hold a reserve for the second project, and make the running line as normal as the hosting bill. The businesses that get returns from AI are not the ones that spent the most; they are the ones whose systems were still running and still owned a year after launch.
Frequently asked questions
How much should a small business budget for AI?
Enough for one well-chosen first project with its full first year of running costs and the people time around it, and a reserve for what it reveals. There is no meaningful percentage of revenue; the number follows from the project chosen. What matters is that the three columns are all present, so the budget survives contact with month four.
Why does the running cost matter so much for a small system?
Because it never stops and it is usually invisible in the proposal. Usage grows with adoption, models get updated and need retesting, documents go stale and need refreshing, someone must look at the quality sample monthly. An automation with no running budget decays until it is quietly switched off, and the build money is wasted.
What are the hidden costs, concretely?
Your best people spending hours labelling the evaluation cases. Staff reviewing exceptions daily for the first months. Someone rewriting the procedure and training the team. A dip in output while people learn the new way. None of these appear on a vendor invoice and all of them are real. Estimate them in hours and put a value on the hours.