Two budget lines answer the adoption question before any usage dashboard does: what you pay for AI seats, and what you pay to teach people to use them. Divide the second by the first and you have a ratio. Most companies of 50 to 500 people have never computed it, and when they do the number lands near one dollar of AI enablement for every fifteen to twenty dollars of software.
The ratio that tracks with people using the tools is nearer to one to one in the first year. That figure is not pulled from a consultancy deck; it is what the one published threshold for behavior change in this field costs once you price the hours. Below: how to compute your own ratio from two invoice lines, what each band predicts, and the three ways the number misleads.
What the ratio is, and what goes on each side
The comparison people reach for, AI enablement vs software spend, only works if both sides are defined the same way every year. Two rules make it stable.
The denominator is the incremental AI seat bill, not your whole software estate. Count what you added for AI: assistant seats, premium tiers, any per-seat add-on you would cancel tomorrow if the program stopped. Leave out the base productivity suite you were paying for anyway. Count the whole Microsoft or Google bill and the ratio shrinks to a rounding error.
The numerator is everything you spend to change behavior. Four components, and most teams count only the first.
| Component | What it is | Usually counted |
|---|---|---|
| Delivery fees | Facilitator, course seat, or catalog subscription | Yes |
| Attendee payroll | Hours off the floor at a loaded rate | Almost never |
| Internal owner time | Scheduling, chasing, follow-through | Almost never |
| Measurement | Baselines before, re-measurement after | Almost never |
Report the ratio both ways, fees only and all-in. The fees-only number is what procurement recognizes; the all-in number is the real one, and it is typically double. The Bureau of Labor Statistics puts total employer compensation for private industry workers at $46.89 per hour worked as of June 2026, the defensible rate for the payroll line. Turning vendor quotes into comparable units is a related problem, worked through in cost per head against cost per hour saved.
The market runs at about one dollar of enablement to fifteen of software
Mid-market seat prices sit in a narrow band. Microsoft 365 Copilot lists at $30 per user per month on an annual commitment, which is $360 a year. Claude’s Team plan publishes $20 per seat per month billed annually, or $240 a year, with Enterprise at the same seat rate on a 20-seat minimum. Call the AI software line $240 to $360 per seat per year at list.
The enablement side has one published figure, from Training magazine’s 2025 Training Industry Report. AI training rose from 0.8% of total training hours in 2024 to 2.0% in 2025, against 40 training hours per employee. Two percent of 40 hours is 48 minutes a year. Applied to the report’s $874 per learner, the dollar share is roughly $17 per learner, and even at four times that weighting it stays under $70.
Divide one by the other. Seventeen dollars against $240 to $360 is a ratio of about 1:14 to 1:21. The shape matters more than the precision: the software line is an order of magnitude larger than the line that decides whether the software gets used. That is the argument in the case against treating a license rollout as a capability.
Two checks confirm the shape. The Atlanta Fed’s March 2026 survey of senior executives put AI spend per employee at $2,068 for 2026, but that covers software, subscriptions, hardware, worker training, and IT staff support, with training the smallest of the five. BCG’s Applied AI 2026 survey found AI’s share of the IT budget more than tripled in a year, from 5% to 17%, with no comparable jump in learning budgets. The per-head version of the comparison is in what companies actually spend per employee on AI enablement.
The only published threshold is five hours
Most writing on AI training ROI asserts a percentage. One study gives a quantity.
BCG’s AI at Work 2025 survey, covering more than 10,600 leaders, managers and frontline employees across 11 countries, reported that regular usage is sharply higher for employees who receive at least five hours of training and have access to in-person training and coaching. The 2026 edition, with close to 12,000 respondents, found 74% of frontline employees using AI daily or a few times a week, up 23 points in a year, while only 36% felt they had received adequate upskilling.
Five hours plus coaching is a specification, so it can be priced. A private session for 20 to 30 people, inside the $2,000 to $15,000 market range for the room, puts five hours of delivery near $150 to $400 a head. The payroll clock adds five hours at $46.89, or $234 a head.
| Side of the ratio | Per head, year one |
|---|---|
| AI software | $240 to $360 |
| Enablement, fees only | $150 to $400 |
| Enablement, all-in with payroll | $385 to $635 |
So the published threshold costs roughly what the licenses cost on fees alone, and more once the hours are counted. The target ratio is not a bold number. It is one to one. The market runs at a fifteenth of it.
BCG arrives at the same place from another direction: roughly 10% of value comes from technology, 20% from data and algorithms, and 70% from changes to people, process, and operating model. A 94/6 split inverts where the value is reported to sit.
What each band predicts
Ratios work better as a diagnostic than as a plan. Here is what each band produces, on the fees-only reading so it compares across companies that do not track payroll.
| Enablement : software | What it looks like in practice | What it predicts |
|---|---|---|
| Below 1:10 | Seats provisioned, an announcement email, a shared prompt doc | Use concentrates in the people who would have taught themselves; everyone else logs in once |
| 1:10 to 1:4 | A one-hour vendor demo, or catalog seats bought in bulk | Awareness without transfer. Completion data looks fine and work does not change |
| 1:4 to 1:2 | A half-day facilitated session, no follow-through | One changed week, measurably decaying by quarter end |
| 1:2 to 1:1 | Five or more facilitated hours on the team’s own work, plus scheduled practice | Where regular use holds, and the only band with published evidence behind it |
| Above 1:1 | Custom curriculum, repeated cohorts, internal facilitators | Fine, but read the absolute number instead of the ratio |
The bottom row is the one people misuse. A high ratio on a small base is not a strong program: a 60-person company with eight seats and one $9,000 workshop clears 3:1 and has still trained eight people. The ratio describes balance, not coverage, and coverage is what the usage report measures.
The top row is the common one. A company below 1:10 has already decided adoption would be self-taught. The flat usage curve six months later is that arithmetic working as designed, not a failure of the tool.
The denominator grows on its own and the numerator does not
The ratio decays without anyone choosing to let it, which is the part worth watching.
Gartner’s revised 2026 forecast put worldwide software spending at $1.44 trillion, up 15.1% in a year. Inside one company the same force shows up as seat counts expanding, premium tiers getting added, and a second assistant arriving because one team preferred it. Each grows the denominator and none requires a fresh approval.
The numerator moves only when someone schedules something. It has no renewal cycle, no account manager, no auto-expansion, and nobody sends a reminder that the workforce has not been trained since March. So a company that hit a sound ratio in year one drifts back toward 1:15 within four quarters just by buying seats. Two habits stop it:
- Make enablement a percentage, not a number. A line reading “AI enablement: 60% of AI seat spend, reviewed at renewal” scales with the thing it supports. A fixed dollar amount decays.
- Tie it to the renewal, not the fiscal year. Renewal is when headcount on the plan gets counted, and when nobody has trained the people added since the last session.
Finding the dollars when the total is fixed is its own problem, covered in our guide to funding enablement in a flat-headcount year.
Compute yours from two invoice lines
A worked example: a 180-person company, 60 licensed seats, one year.
Denominator. 60 seats at a blended $300 a year is $18,000, excluding the base productivity suite.
Numerator at the market ratio. 60 people at $17 a head is about $1,000, a ratio of 1:18. Companies this size usually find something close to it, which surprises them, because the discussion sounded like more money.
Numerator at the threshold. Two cohorts of 30, one five-hour session each on the team’s own documents, at $4,000 to $6,000 a room, is $8,000 to $12,000 in fees. Payroll adds 60 people times five hours times $46.89, or $14,067, and an internal owner at 30 hours adds roughly $2,250.
| Reading | Enablement | Software | Ratio |
|---|---|---|---|
| Fees only | $10,000 | $18,000 | 1:1.8 |
| All-in | $26,300 | $18,000 | 1.5:1 |
Both are defensible. Procurement recognizes the first; finance tests the second, because payroll is real money and the hours were going to be spent on something. Whether those hours beat the alternative is a separate calculation, run in train the team or add a headcount.
Three ways the ratio lies
It confuses balance with scale. The ratio is indifferent to how many people you reached. Report it beside two absolute figures: dollars per head and share of headcount trained. A 1:1 ratio covering 15% of the company is a pilot, and the usage data will read like one.
It is a correlation, not a controlled trial. BCG’s five-hour finding is survey data. Companies that fund five hours plus coaching also tend to have engaged leadership, clearer communication, and a named owner, and those travel together. Treat the ratio as a strong leading indicator and nothing more. Cause has to come from your own before-and-after measurement.
It is easy to game from either side. Moving the base productivity license into the denominator halves the ratio; counting an all-hands briefing as enablement doubles it. Write the definition down once and reuse it every quarter. A ratio compared against its own prior-year self is worth something; one compared against somebody else’s definition is worth nothing.
What to do with the number
Compute it, then decide which of three situations you are in.
- Below 1:10 and adoption is flat. Your spend pattern predicted that. The cheapest correction is rarely more seats or a different vendor; it is five facilitated hours for the people already licensed.
- Near 1:1 and adoption is still flat. The ratio is not the problem. Check coverage, whether the session touched the team’s own work, and whether practice was scheduled afterward.
- Above 1:1 with thin coverage. You are over-serving a small group. Spread the same dollars wider before adding depth.
In every case the ratio is an input. What gets reported upward is the output it bought, and that needs a measurement taken before the first session rather than reconstructed after. Seat activity is the wrong denominator, because measuring AI adoption through logins flatters a rollout that changed no work. The AI enablement metrics that survive a finance review, and the order to collect them in, are in our measurement playbook. For the model you will be asked to defend, see how to build an ROI model your finance team cannot dismiss.
Frequently asked questions
What is a good ratio of AI enablement spend to software spend?
About one to one in the first year, measured on fees against the incremental AI seat bill. That is what five facilitated hours plus coaching costs per head at market session rates, and it is the one training quantity with published evidence behind it.
Does the ratio include employee time or only vendor fees?
Report both. Fees only is what procurement recognizes. All-in, with attendee payroll at $46.89 per hour worked, runs roughly double and is what finance will test. Pick one definition and hold it across years.
Should our base Microsoft 365 or Google Workspace license count in the denominator?
No. Count only what you added for AI and would cancel if the program stopped. Including the base suite shrinks the ratio to nothing and hides the comparison you are making.
Our ratio looks good because we only bought a few seats. Is that real?
No. The ratio measures balance, not reach. Report it next to dollars per head and share of headcount trained. A strong ratio covering a tenth of the company produces usage data to match.
Does spending more on enablement cause higher adoption?
The link is strong and correlational. BCG found regular use sharply higher among employees with at least five hours of training plus coaching, across more than 10,600 respondents. Only your own before-and-after measurement establishes cause.
What should the ratio be in year two?
Lower, deliberately. Year one carries curriculum build and the full population; later years carry new hires, new tools, and refreshers. The 1:3 to 1:2 range is a reasonable steady state, provided year one happened.
Training was never a separate budget line. How do I compute the numerator?
Add up what was spent on behavior change wherever it sat: course subscriptions, facilitator invoices, conference tickets bought as upskilling, and the hours of whoever runs sessions as a second job. For most companies this size the total is under $5,000 and the exercise takes an afternoon.
The budget is flat. Can the ratio improve without new money?
Yes, through two levers. Fill rooms you have already paid for, since a private session is priced for the room rather than per head. And trim the denominator where it is idle: seats assigned to people who never open the tool fund the wrong half of the ratio.
Do I report the ratio or the cost per head to the board?
Lead with the ratio, because it frames the decision in one number, then support it with cost per head and share of headcount trained. The ratio wins the argument; the per-head figure survives the follow-up questions.
Key takeaways
- Divide what you spend changing behavior by what you spend on incremental AI seats. The market’s answer is about 1:15 to 1:20: $17 per learner against $240 to $360 per seat per year.
- The one published threshold is five hours of training plus in-person coaching. On fees alone it costs about what the licenses cost, and more once payroll is counted, which puts the defensible target near one to one in year one.
- Each band predicts a behavior: below 1:10 produces self-taught minorities, 1:10 to 1:4 awareness without transfer, and 1:2 to 1:1 is the only band with evidence behind it.
- The ratio decays on its own, because seat counts expand without a new approval and training does not. Budget enablement as a percentage of seat spend, reviewed at renewal.
- Never report the ratio alone. Pair it with dollars per head and share of headcount trained, or a thin pilot reads as a balanced program.
If you want your own ratio computed from your actual seat bill and headcount, with a view on which half is the constraint, book a free AI readiness call. We will say where the spend is already adequate and where it is predicting the adoption curve you are unhappy with.
Arthur Wandzel
