Watching two budget lines converge in opposite directions, one falling slowly and one rising fast, I keep arriving at the same thought experiment. On one side, the salary line. Visible, audited quarterly, debated in board meetings, tracked to the cent. On the other side, the token spend line. Invisible, scattered across dozens of cost centers, buried in cloud invoices, attributed to nobody. These two lines are moving toward each other like scissors, and the interesting question is not whether they cross, but who notices when they do.

The salary line is declining for reasons that have nothing to do with a single cause. Economic pressure compresses headcount. Efficiency mandates from boards demand more output per person. Post-pandemic restructuring continues to unwind inflated teams. Natural attrition goes unreplaced, quarter after quarter, because the backfill request gets quietly deprioritized. AI productivity gains compound on top of all of this, making it possible for smaller teams to absorb work that previously required new hires. No single force is driving the salary line down. Several forces are pushing in the same direction, and they reinforce each other.

The token line is climbing, and nobody is watching the meter. Every developer running GitLab Duo consumes tokens. Every OpenAI Codex session consumes tokens. Every Claude Code agent running overnight on a refactoring task consumes tokens. The product managers using AI chat to draft specs, the designers generating variations, the QA engineers using agents to write test cases, all of them consume tokens. And the bill lands in a dozen different budget lines because nobody set up unified tracking. I wrote about this visibility gap in The Billing Problem Nobody Talks About, and the problem has only gotten worse since.

The small end is already there

For one-person operations and early-stage startups, the scissors have already crossed. I know founders whose monthly AI token bill, spread across coding agents, research tools, content generation, and automated workflows, exceeds what a first hire at minimum wage would cost. The founder chose tokens over headcount, not as a philosophical statement but as an economic one. The tokens produce output at 3 AM, do not need health insurance, and scale down to zero when the sprint ends.

This is not theoretical. It is the current reality for a growing number of solo operators and two-person teams, that the AI infrastructure bill is their largest expense after rent. The first hire they do not make is the clearest signal, that the ratio has inverted at the small end of the market.

The enterprise middle

In large organizations, the convergence is messier and slower. Headcount does not shrink cleanly, it redistributes. Teams consolidate. Attrition goes unreplaced. Contractors are not renewed. The salary line moves like a glacier, visible only in year-over-year comparisons, because nobody announces “we are spending less on people.” They announce “we are investing in efficiency” and the headcount quietly drops by 8% through non-replacement.

The token line, meanwhile, moves fast but remains invisible. Engineering has its own AI tooling budget. Product management expenses AI through a different cost center. Marketing’s AI writing tools land on a third. The data science team’s model inference costs sit in cloud compute. Nobody aggregates these into a single number and holds it next to the salary line, because nobody has been asked to. The organizational machinery for tracking consumption-based AI spend simply does not exist in most enterprises, and the FinOps teams that could build it are still focused on cloud infrastructure.

So the two lines are converging, but the organization cannot see it because it is looking at each line through a different lens, owned by a different team, reported in a different cadence.

The signal to watch for

Here is the thought experiment that I cannot stop running. Imagine that a company the size of Salesforce or SAP, with hundreds of thousands of employees and tens of billions in salary obligations, reaches a quarter where the aggregated token spend across all AI tools and services exceeds the aggregated salary spend. That is the moment the industrial era’s core assumption, that companies are fundamentally made of people, visibly inverts.

I do not know when this happens. I do not know if it happens within five years or fifteen. I am honestly uncertain whether it happens at all, because salary lines are enormous and sticky, and token costs might decline faster than usage grows. The honest answer is that nobody knows, and anyone claiming certainty about the timeline is selling something.

What I believe is that the directionality is clear, even if the timeline is not. The salary line appears to trend down across most knowledge-work-heavy industries. The token line appears to trend up across all of them. Whether and when they converge is genuinely open.

The cloud precedent, imperfect but instructive

Cloud infrastructure spend followed a similar trajectory. Within a decade, cloud went from a rounding error to a top-three line item at most enterprises, overtaking on-premises hardware budgets that had seemed immovable. The FinOps discipline emerged specifically because organizations discovered, too late, that they had no governance framework for consumption-based spend that grew faster than anyone had modeled.

But the analogy breaks in an important place. Cloud replaced bare metal capital expenditure and operations teams. It shifted workforce composition (fewer sysadmins, more cloud engineers, often fewer people overall but higher-paid), but it replaced infrastructure, not the core output of the workforce. Token spend is different. Tokens potentially replace the work product itself, the code, the analysis, the documentation, the decisions that knowledge workers produce. Cloud restructured teams. Tokens may compress them.

The trajectory is instructive (invisible consumption becoming a dominant cost line), even where the analogy is imperfect. Snowflake proved that consumption pricing can sustain 127% net revenue retention when the product is valuable enough, and enterprises will pay the bill even when it grows faster than forecast. The question is whether the same dynamic applies when what is being consumed is not data warehousing but the output of work itself.

The question nobody is asking

I have one ask, directed at anyone who controls a budget. CFOs, engineering VPs, finance partners sitting in quarterly business reviews: what is the ratio of salary spend to token spend in your organization today? Not an estimate. An actual number. Aggregated across every AI tool, every cost center, every team.

My prediction is that most cannot answer this question, not because the data does not exist, but because nobody has been asked to assemble it. And that is precisely the problem. The salary line has a department, a VP, a board-level review, and a quarterly forecast. The token line has a dozen scattered invoices and no owner.

Track the ratio. I suspect it is the leading indicator that nobody is watching, and by the time someone thinks to check, the scissors may have already crossed.