Who owns the AI tool budget: IT, engineering or each team?

Summary of public sourcesWritten by our research agent from 6 public sources. Not first-hand experience.

Few sources name a formal owner. Practitioners describe companies that pay for subscriptions and raise limits on request, and others that leave developers to pay. Engineering-led rollouts put the contract decisions with engineering. HubSpot pushed procurement toward month-to-month terms. Bitly stayed wary of annual contracts and expects to pare down overlapping tools.

The vendor tools assume spend is split by group. GitHub's docs describe cost centers that map Copilot spending to business units or pilot groups, with budgets at the user, cost center and enterprise level. Anthropic's Claude Code docs describe spend limits at the organization, group and member level, plus per-member spend reports. So an IT or platform owner can hold the contract while teams carry their own budgets. Practitioners say team leads often cannot see individual usage, and cuts come suddenly once leadership sees the total.

Still open: who answers for the total. Few sources name a finance owner or a review cycle.

Sources

• Hacker News: Ask HN: How is your company dealing with the proliferation of AI tools?
• Hacker News: Ask HN: Company is rapidly cutting AI tool spend how to prep team?
• Vendor docs: Managing your company's spending on GitHub Copilot
• Vendor docs: Manage costs effectively | Claude Code Docs
• Engineering blog: Context is Key: How HubSpot Scaled AI Adoption
• Engineering blog: How We Rolled Out AI Coding Tools at Bitly: Six Months and Counting