In 2025, 42% of companies abandoned most of their AI initiatives. Roughly double the year before. The models worked. The licenses were paid. What nobody had funded was the work of getting several hundred people to change how they do their jobs.
That's the whole story, and it's about to repeat itself in a lot of 2027 budgets that are being drafted right now.
How much should a company budget for AI transformation?
In a serious AI transformation budget for a 1,000-person company, expect to spend roughly $430,000 on people, against a total budget near $6.6M. That's about 6.5%. Everything else is platform seats and consumption, which is to say everything else is a bet that the six and a half percent works.
So what does the people side actually include?
It's not a training line. That's the first thing to fix, because "AI training" is how this gets underfunded. Nobody's problem is that they can't write a prompt.
What you're actually buying is four distinct pieces of work.
A continuous enablement and coaching capability, one that measures fluency across the organization rather than counting course completions, paired with activation sessions a couple of times a year because what "good" looks like keeps moving. Around $200,000.
Change execution with an owner. Manager enablement, office hours, working sessions, hackathons. Roughly $130,000, whether that's an internal hire or outside support. Managers are the transmission mechanism for all of this, and most plans skip them entirely. Your people aren't stalling because they lack curiosity. They're stalling because their manager can't answer "what does this mean for my job," so they wait, which is the rational move.
A champions program. Somewhere in your finance team, someone has already rebuilt a reporting process on their own time and hasn't mentioned it because they're not sure they're allowed. Find that 5-10% of your workforce, make it a real role, pay them about $2,000 a year for it. Proof that travels is proof from the desk next door.
And leadership that can actually drive it. A Head of AI at $200,000 to $400,000 fully loaded, senior enough to tell an executive peer their function is behind and have it land.
Yes, the technology costs money. Seats run around $480 per employee and consumption at maturity lands somewhere in the range of 2-5% of salary for knowledge workers and 5-7% for technical roles. Those numbers are real, and your vendors will help you build them. But they're the easy part of the budget, and they're not the part that determines whether any of this works.
Why can't we just run this ourselves?
Most organizations can't run AI transformation entirely in-house, because it requires capacity, objectivity, and sequencing that internal teams rarely have all three of at once. Some of you can, and should. If you have a Head of AI already, a people team with genuine capacity, and executives who agree on what's changing, run it internally and don't pay anyone to tell you what you already know.
Most organizations aren't in that position, and the reasons are pretty consistent.
Capacity is the obvious one. Your people team is running comp cycles, open roles, and whatever fire started this morning. Transformation work is the thing that gets moved to next quarter every quarter until someone external puts dates on a calendar.
Objectivity is the harder one. You cannot diagnose your own culture. Everyone inside the building has a position on which teams are the problem, and those positions are mostly wrong in interesting ways. The manager who reports enthusiastic adoption and the manager who reports resistance are frequently describing the same behavior with different incentives around what they say out loud.
And sequence is the one that quietly ruins programs. There's an order to this work. Diagnose, then redesign, then optimize workflows, then embed the change. Do it in a different order and you get what most companies get, which is tool deployment followed eighteen months later by an urgent change management engagement that's really just damage control.
The other thing worth naming: outside help gives you a way to hear things your employees won't say to you. They will tell a third party they think this is a layoff in a trench coat. They will not tell their VP.
What does a real AI transformation process look like?
A real AI transformation process runs in four phases, in order: diagnose, redesign, rebuild workflows, then embed the change. Each phase produces something the next one needs.
Start with a baseline. A structured readiness diagnostic across people, culture, capability, and structure, delivered as a findings report and a prioritized 90-day roadmap. Four weeks, and it should happen before any major AI investment is finalized. This is the least glamorous line in the budget and the one that protects everything after it. It also solves a problem you'll hit in about six weeks, when your CFO asks how you'll know if this is working. You can't show movement without a starting line.
Then redesign the org. Roles, teams, reporting lines, decision rights, governance. Role-level impact analysis so you know honestly which jobs are being augmented and which are genuinely being restructured. Reskilling plans for the people in the second category. Who approves an agent going into production. Who owns the output when a model wrote the first draft. Adoption doesn't stall on skill. It stalls on ambiguity.
Then rebuild the workflows. Map where AI replaces, augments, or hands off work, then redesign the human process around it, with human and AI swim lanes drawn explicitly. Run hackathons here, not for morale but because your people already know which parts of their jobs are wasteful and will surface better use cases in a day than an outsider finds in a month. Pilot two or three workflows with a real path to scale and an ROI model attached.
Then embed the change. Role-based learning tracks, a manager toolkit, the champions program, and an adoption dashboard tracking business impact at 30, 60, and 90 days. This is the phase everyone wants to buy first, and it works considerably better fourth.
You don't have to buy all of it, and you shouldn't buy it as one undifferentiated block. But the sequence matters more than the vendor.
How do you fund an AI transformation budget?
Your CFO won't argue about whether AI works. That debate ended. She'll ask about return and about what's being cut.
Be straight about the curve. The first six months produce very little you could defend in a board deck, and hunting for ROI that early mostly teaches you to fool yourself. Six to twelve months, specific workflows that measurably changed. Twelve to twenty-four, capacity absorbed without adding headcount. Commit to the staging rather than to a number you'd have to invent.
Then show her the funding, and start with the one that's already yours. Most companies carry $1,000 to $2,000 per employee in L&D. Leave the compliance portion alone; it's required. The discretionary half is usually a course library nobody finishes. On 1,000 people, that's real money sitting in a budget line that is already labeled "helping employees build skills," which is precisely what you're doing. AI fluency also happens to be the rare training investment where you can watch the output change.
There's more where that came from. According to Zylo's 2026 SaaS Management Index, built on 40 million licenses and $75 billion in spend, found 36% of SaaS licenses go unused, and that's before you count the categories AI absorbs outright. McKinsey estimates indirect spend at 10-18% of revenue, a real slice of which is outsourced content, research, design, and support, exactly the work agents take first. Hold a quarter of your backfills selectively, only in roles where something has been demonstrably handling part of the work for two straight quarters, and on 120 annual departures, you've funded a large piece of this without a layoff or an announcement.
And when you make the ask, ask for a ramp. Forty percent of run rate in Q1, gated on adoption thresholds you define now, full rate by Q3. She's being asked to fund a curve she can watch instead of a cliff she has to trust.
Where to actually start
Not with a platform decision. With an honest read on where your organization stands.
Everything above gets tested against a single question, which is what this feels like for the person doing the work. That's where the value is captured or lost, and it's the part no vendor demo will ever tell you about.
The 42% who walked away last year didn't pick the wrong technology. They funded a purchase when what they needed was a partner and a process.