Your AI Budget Is Already A Headcount Decision

Prashant Jalan is the founder of Guickly and previously led applied AI teams in the mapping technology industry.

When I was a tech lead manager at Google, adding even one person to my team took almost a quarter. I had to write the justification, defend the scope in a planning meeting and then wait. Sometimes the answer came back as “yes”; at times, it didn’t. Every person on that team was a number somebody had signed their name to.

The same money moves very differently now. AI tools can be purchased through a corporate card or software subscription, often without the review or accountability that comes with adding a person to the team.​

The Decision Nobody Is Calling A​ Decision

​I hear a version of this from almost every company I talk to. A role opens up and never gets backfilled, because the team found a way to cover it. A manager who cannot get a requirement approved grows the AI tooling budget instead. Nobody questions it, because tooling is not headcount.

Those are labor decisions. They are just never called that.

It is also not little money anymore. Bain & Co. has modeled a scenario in which AI tokens eventually replace roughly a quarter of headcount operating expenses. Nothing reaches a quarter of operating expenses without displacing some other line item. In most companies, that line item is payroll.​​

​Two Key Numbers That Never Meet: Payroll And AI Spend

The uncomfortable part is that nobody can actually compare the two options, because the two options do not live in the same place.​

The cost of an employee is relatively straightforward to calculate. Finance tracks a fully loaded cost tied to a specific person, with a manager, a start date and a place in the budget.​​

​Where The Obvious Solution Breaks Down

​The standard advice is to measure cost per unit of work and compare. Everyone tries this now, but it has limitations.