Meta's Adam Mosseri thinks companies will soon put spending caps on AI tools, engineer by engineer
The head of Instagram says AI token budgets could become a standard line item on the corporate balance sheet, sitting right next to payroll.

Key points
- Adam Mosseri, head of Instagram, predicted in 2025 that companies will manage AI tool spending per engineer the same way they manage salaries.
- AI tokens, the tiny units of text an AI model processes each time someone uses it, cost money every time an engineer runs a query or generates code.
- Mosseri said engineers could soon face hard limits on how much AI they are allowed to use each month.
- The prediction signals that AI tool costs are already large enough to worry senior executives at companies like Meta.
Adam Mosseri, the executive who runs Instagram for Meta, has a prediction that will interest anyone who works in tech: the bill for AI tools is about to get personal.
Mosseri said he expects companies will one day track and cap AI token spending on a per-engineer basis. A token is the smallest unit of text an AI model reads or writes. Every time a developer asks an AI coding assistant a question, the system burns through thousands of tokens, and each one costs a fraction of a cent. Those fractions add up fast across an entire engineering team.
The comparison he reached for is blunt: treat it like payroll. Salaries are the single biggest cost on most company books, and finance teams track them obsessively. Mosseri thinks AI compute costs are heading toward the same level of scrutiny. TechCrunch AI first reported the remarks.
We covered Mosseri earlier this month in our report on Instagram's approach to AI-generated posts, which shows how consistently he's been at the centre of Meta's AI decisions.
What does this mean for engineers using AI tools right now?
For most developers today, AI coding assistants feel unlimited. Open a tool, ask for help, get an answer. No meter ticking.
That'll likely change. If Mosseri is right, companies will start assigning monthly token allowances to individuals, much like a corporate travel budget or an expense card limit. An engineer who burns through their allocation writing code with AI assistance might have to wait, or justify the spend to a manager.
It's not a fringe concern. Companies across Silicon Valley are discovering that equipping hundreds of engineers with AI coding tools can run to millions of dollars a year in API fees, the charges vendors collect each time their model answers a question. That's a budget line demanding control.
For engineers, the practical implication: start paying attention to which tasks genuinely need AI and which are habit. A quick syntax check probably doesn't need a full reasoning model; a complex architectural review might. Learning to match the tool to the task, before someone else is assigned to track it for you, is the sensible move now.
For anyone outside tech, this is a useful signal about how real AI costs have become. The technology isn't free to run, and the companies building on top of it are racing to keep those costs from ballooning before the budget meeting arrives.



