TL;DR
AI coding bills now combine a fixed seat with metered usage, and the metered part varies widely between developers and grows with agent work. Budget each developer as three lines: the seat, a usage allowance sized from your own pilot data, and a reserve for heavy users and agent runs. Put review and rework time on the same sheet, cap by team rather than cutting access, and agree with finance beforehand which delivery measures decide each quarter whether the spend grows, holds or shrinks.
In this article
8 min read
Split the fixed seat from the metered usage
Whether the tools are worth their cost has no market answer; it depends on what your team ships with them, which only your own before-and-after data shows. What you can do this quarter is make the budget legible: a cost per developer that separates what is fixed from what moves, and a rule, agreed with finance in advance, for reading that cost against delivery.
The separation matters because the main vendors now bill in two parts. GitHub moved Copilot to usage-based billing on 1 June 2026: chat, the CLI and the cloud agent consume AI Credits calculated from tokens at each model’s API rate, while completions stay unmetered (GitHub blog, 27 April 2026). Prices below are examples of pricing models, read on the vendors’ pages on 9 October 2026, not a recommendation. Vendor list prices are USD-based.
Comparison
| Tool (list prices, 9 Oct 2026) | Fixed part per seat | What is metered | Spend caps documented |
|---|---|---|---|
| GitHub Copilot Business or Enterprise | $19 or $39 per user per month, including the same value in AI Credits | Token use beyond the credits, pooled across the organisation | Enterprise, cost centre and user budgets |
| Cursor Teams | $40 (Standard) or $120 (Premium) per user per month | On-demand use beyond each user’s own allowance, at API list prices plus a Cursor token fee | Team-wide monthly limit; per-member limits on Enterprise only |
| Claude Team or Enterprise | Team: $25 a month ($20 billed annually), Premium $125 ($100). Enterprise: $20 a seat plus usage at API rates | Usage credits beyond the seat allowance | Organisation, group and member limits |
| ChatGPT Business (Codex) | $25 a month ($20 billed annually) per user | Credits after the included limits, priced per million tokens | Not checked for this article |
The seat is the small, predictable line. The metered line is the one that surprised an IT manager who wrote on r/EngineeringManagers in April 2026 that a rollout to roughly 500 developers had produced a bill far above expectations, and the CFO now wanted a return-on-investment breakdown.
Size the usage line from your own spread
An average per developer hides the shape that drives the bill. Anthropic’s own cost guidance for Claude Code puts the enterprise average at around $13 per developer per active day and $150 to $250 per developer per month, with 90% of users below $30 per active day, and it tells teams to establish a baseline with a pilot group before a wider rollout (Claude Code docs, read 9 October 2026). That is a vendor’s figure for its own tool, and it describes a skewed distribution: a minority cost several times the median.
Other companies’ spend is no benchmark either. When someone asked on Hacker News in March 2026 what people actually spend, prompted by a chip maker’s chief executive suggesting $250,000 a year in tokens for a $500,000 engineer, the replies came from different tools, plans and kinds of work, so they cannot set your number.
Size the line from your own data: two or three months of per-user usage, active developers only, with the median and the 90th percentile per month. Then check how your contract treats allowances: GitHub pools included credits across the organisation, so light users offset heavy ones, while Cursor Teams allowances stay with each user, so a heavy user moves onto on-demand billing while colleagues leave theirs unused.
Count the costs that never reach the invoice
Licences are the visible part. A developer’s AI cost also includes configuring and supporting the tools, review time on AI-assisted changes, and rework when a change comes back. The last two can exceed the licence and land in engineering hours, not on a vendor bill. The cost model for almost-right AI code breaks verification into the separate tasks that make up that work.
The research supports putting them on the same sheet. Google’s 2025 DORA report, from nearly 5,000 survey responses, found a positive relationship between AI adoption and software delivery throughput, and a continuing negative relationship with delivery stability (Google Cloud, 23 September 2025). Those are survey relationships, not causes, but they describe a budget that can look cheap on licences while review and rework absorb part of the gain.
Be as careful with the benefit side. In METR’s study of 16 experienced open-source developers, their own estimates of how much AI had sped them up did not match measured task times; METR calls it a snapshot of early-2025 tools, not a general result (METR, 10 July 2025). A survey saying the tools save time is a reason to measure.
Give finance a model, not a usage dashboard
Adoption, satisfaction and a merge-time improvement, what the r/EngineeringManagers poster could show, establish that the tools are used. Finance needs four other things, on one page:
- Spend by team and type. Seats, metered usage and agent runs per month, naming the line that grows.
- A unit cost. Cost per active developer and per merged change that was not reverted or reworked within the period.
- The assumption, written as a break-even. In the example above, at an invented loaded cost of €82 an hour, €194 a month pays for itself if it frees about two and a half hours per developer that turn into delivered work.
- The decision rule and its owner. What result keeps, changes or cuts the spend, and who signs it.
The break-even line is where the conversation becomes honest. Hours saved are not cash unless they show up as delivery the team could not otherwise have done, or as hiring or contractor work no longer needed. Said plainly, that gives finance a claim it can test. The article on measuring AI coding value rather than activity covers which delivery measures to pair with each other.
Cap by team without moving the cost elsewhere
The vendors provide the controls; the design decides whether they save money. GitHub supports budgets per user and per cost centre, but an exhausted user budget halts that person even while the organisation’s pool has credits, and nothing switches them to a cheaper model (GitHub Docs, read 9 October 2026). A hard cap reached on a Thursday afternoon stops work, it does not reduce it.
Three choices usually hold up:
- Budget per team, alert before blocking. Give each team a monthly line, send alerts at agreed thresholds, and keep hard stops for runaway cases.
- Show costs before charging them. The FinOps Foundation describes showback, showing a group the costs it is responsible for, as required everywhere, and formal chargeback as optional when costs map to few cost centres (FinOps Foundation).
- Test model restrictions on rework, not on price. A cheaper default model saves money only if the changes it produces are not reviewed and redone more often.
The failure case is an abrupt cut. In May 2026 a developer asked on Hacker News how to prepare their team after the company removed most Claude Code access over cost and forbade personal plans, while expecting the same output from teams that had built workflows around the tool. Pushing work onto personal accounts moves the cost into data exposure; slowing delivery moves it into the roadmap.
Let finance and engineering sign the review rule together
Agree the review before the numbers arrive. Engineering proposes the measures and the thresholds; finance owns the budget line; both sign the rule for keeping, changing, cutting or expanding the spend, and the review lands before seat contracts renew. A few measures are enough: cost per active developer, review time per change, the share of changes reverted or reworked, and the delivery measure the team already reports.
The AI Delivery Programme addresses this part. In week 1 (Align) the team agrees a baseline of how it delivers today and the measures for week five; in week 5 (Hand over) the outcome is compared with that baseline in writing, including what the evidence cannot establish. It does not lower licence costs or set your budget, the tool and model costs stay yours, and no team’s before-and-after comparison exists yet to quote. Explore the Programme if you want your own baseline in place before the next budget review; fees and dates are not published, and the first step is a fit conversation.
Frequently Asked Questions
Are our AI coding tool costs worth it?
Treat it as two questions. Whether the spend is proportionate can be checked against list prices and your own usage spread. Whether it pays can only be answered against your own delivery baseline, so if none was taken before the rollout, start one now and say so to finance.
How do we see what we are paying for, by tool, team and type of use?
Export per-user usage from each vendor’s admin reporting, such as GitHub’s billing reports, Claude’s spend report or Cursor’s dashboard, and map users to teams through your identity provider’s groups. Where usage runs through a cloud provider, per-user attribution needs OpenTelemetry export or a gateway, according to the Claude Code documentation.
What would we have to believe for the spend to be worth it, and what would cutting access cost?
Write the belief per team as hours freed and rework avoided, then ask the reviewers whether it matches what they see. Cutting has its own price: workflows built around a tool, retraining on a replacement, and the risk that people move to personal accounts.
How can per-team budgets, model restrictions or chargebacks fail?
Allowances that do not roll over invite spending at month end. Chargeback can make teams avoid a tool that saves them time because the cost is visible and the benefit is not. Restrictions that make the approved route harder than a personal subscription push work outside your controls.
Which outcome measures should we review against cost each quarter, and who decides?
Pair each cost figure with a quality figure, for example cost per merged change with the share of those changes reworked, so a cheaper quarter cannot hide slower or worse delivery. Engineering owns the measures, finance owns the budget, and the decision is recorded with the evidence it used.
