How Should a Company Set an AI Budget per Employee?

Set the budget role by role. Give each role the list price of the seat it needs plus an allowance for use, sized to how much of the role’s work AI can do, and adjust the allowance each quarter according to what the role produced. One figure for every employee fits few roles: Anthropic’s Claude Code documentation puts the average cost of its coding tool at $150 to $250 per developer a month, while the median US business on Ramp that pays for AI spent $16.32 per employee in October 2026, according to the Ramp AI Index.

A token is the unit AI vendors bill by, roughly a piece of a word. When a tool bills by the token, the cost of a seat depends on how it is used.

What have companies done about AI budgets per employee?

Most of what is public about employee AI limits in 2026 comes from press reports citing internal memos or unnamed people, so the table says who reported each item.

404 Media reported on October 15, 2026 that Accenture told many employees it would now spend only $29 a month per person on Claude. Forbes, relaying 404 Media, added that use above $29 is charged to an internal project or team code and that some staff had reportedly spent $500 to $1,000 a month. An Accenture spokesperson told Forbes that reporting suggesting “a firm limit on our people’s access to AI tools each month is incorrect,” and said the figure illustrated one part of the funding approach. Forbes also notes that what the $29 covers, and Accenture’s commercial terms, are not public.

As reported, that design settles who pays, with the center funding a base and the work that benefits funding the rest. It leaves open how much each role should use.

Why does one AI budget per employee misfit most roles?

Use depends on the kind of work. Anthropic’s cost guidance reports an average across enterprise deployments of about $13 per developer per active day, with 90% of users below $30 per active day, and advises admins to budget more for a coding seat than a chat seat. Treated as an allowance for use, $29 a month covers a little over two active days of the average developer’s use, while a role that asks AI for an occasional summary may not spend that much in a month.

Spend also concentrates. In one internal Accenture analysis of a single AI tool, reported by Fortune in July 2026, 19% of users accounted for roughly 80% of the spend. On those figures, the other 81% of users averaged about a quarter of the overall average. Between companies the spread is wider still: the Ramp AI Index, drawn from more than 85,000 US businesses on Ramp, puts the top tenth of those paying for AI at a median of $800.84 per employee a month in October 2026, against $16.32 for the median firm.

Two executives have tied the figure to pay. TechCrunch reported that Nvidia’s Jensen Huang suggested in March that engineers receive roughly half their base salary again in tokens, and that Mosseri said in July a strong engineer’s spend might equal their salary.

How do you set an AI budget by role?

Set the budget from two facts about each role. How much of the role’s work AI can do sets the starting allowance, and what the role produced moves it.

1. Group people by role, using the job codes in the HR system. The allowance applies to each person in the role and is reviewed for the role as a whole.
2. Find how much of the work suits AI, task by task, and which size of model those tasks need. O*NET lists the tasks in each occupation and the Anthropic Economic Index maps Claude conversations to those tasks, as set out in Is your AI spend in the right roles?. JobRoute scores each task on its role pages, using the method it publishes.
3. Price the starting allowance: the seat at list price plus expected monthly use at the list rate for that model. With no history, Anthropic’s guidance suggests a small pilot group to set a baseline.
4. Decide what happens above it: a hard stop, an approval, a charge to the project, or a pooled group budget. Anthropic’s consumption guide recommends starting with group-level and per-user limits. GitHub supports cost-center budgets on enterprise accounts and per-user budgets for Copilot AI credits.
5. Read what the role produced over the same period, using a measure its managers already track, such as tickets resolved or days to close the books. Our article on measuring AI value outside engineering covers the choice.

Worked example: an AI budget per employee at a fictional 400-person company

This is an example. Everything about the company is invented except the prices, which are list prices read on November 13, 2026; negotiated prices will differ.

Everyone uses Claude Enterprise, listed on Anthropic’s pricing page at $20 per seat per month, billed annually, plus use at API rates. Anthropic’s price list gives Sonnet 5.5 at $2 per million input tokens and $10 per million output tokens, Opus 5.5 at $4 and $20, and Haiku 5.5 at $0.10 and $0.50 for prompts up to 100,000 tokens. The developer allowance is an assumed $200, the middle of Anthropic’s published range for Claude Code. The other volumes are assumptions, and cached input, which costs less, is left out.

The example works out to $30,990 a month, or about $77 per person, while the per-person figures run from $23 to $220. Developers are a fifth of the staff and about 70% of the use budget ($16,000 of $22,990). A flat allowance of $29 a month for use, the size of the figure reported at Accenture, would fund about a seventh of the developer allowance and almost ten times what a technician in the example uses.

Model choice also changes the cost. If the support team found that Haiku 5.5 met its quality bar on reply drafts, with every prompt under 100,000 tokens, the same assumed volume would cost $2.25 per agent a month in use instead of $45 at Anthropic’s list rates. Test that on the role’s own work before switching.

JobRoute reads the usage reports of a company’s AI tools, joins them to each role’s tasks and output measure, and shows spend by role, the roles where spend deserves a question, and paid seats nobody is using, with dollar figures estimated from public list prices unless the company enters its own: see AI spend by role.

What should you review each quarter?

Amazon’s engineering leadership, in a memo published October 27, 2026, recommended watching the 10th and 90th percentiles of AI adoption across teams, the high end to check that delivery rose with heavy use. A budget review can do the same, role by role.

• Spend per person in each role against the allowance, as the median and the 90th percentile, since a few heavy users move an average.
• How often people reach the limit. Anthropic’s consumption guide suggests checking time at limit monthly. A role that keeps reaching it and shows higher output has a case for more.
• The role’s output for the same period. A rise alongside higher use is an association, because staffing and the mix of work change too.
• Low use where much of the work suits AI. Look for gaps in training and access before lowering the allowance.
• Which model the spend went to, set against the share of the role’s tasks that need the largest model.
• What the approvals and project codes paid for, and seats with no activity. A team well above its allowance may have found a use the task data has not yet recorded, so ask before cutting or reclaiming.

What should you be careful about?