The Real Bill for AI at Work

The invoice is the cheap part. A seat, some tokens, a line item the finance team can read in a second. I work with agents every day, and the number on that invoice has almost nothing to do with what the tools actually cost. The real bill arrives somewhere else, in a currency nobody puts on a purchase order.

You can feel the gap if you have lived inside it, and I have, directing agents across more than thirty of my own repositories, one repository at a time. The tool makes you faster on the thing in front of you, immediately and obviously, and you walk away sure the whole system just got faster too. It usually did not. This is the most consistent finding in the workplace research, and it is strange enough to sit with: in Glean's survey of digital workers, people said AI saves them hours every week, and only about one in eight said their organization was performing significantly better as a result. Denmark ran the cleaner test, linking adoption surveys to actual payroll and hours across thousands of workplaces, and in the first couple of years found no meaningful effect on wages or hours at all. Fast individual, flat organization. The same shape keeps coming back.

That gap is not a mystery once you stop looking at the invoice and start counting what the invoice leaves out. I have come to think of AI cost as four ledgers, not one. Three of them never show up in the budget, and they are where the money actually goes.

The four ledgers

Financial is the visible one. Seats, tokens, infrastructure, the security review, the integration work, the vendor contract. This is the cost everyone argues about and the only one most companies actually track. It is also, in my experience, the least interesting, because cheap tokens do not mean cheap adoption. The economists who study general-purpose technologies have a name for the trap: the modern productivity paradox, where the spending and the reorganizing come now and the visible gains come much later, if you do the reorganizing at all. The expensive part of AI was never the model. It is everything you have to rebuild around it. At my own one-person scale there is almost nothing to rebuild, which is exactly why the tool stays cheap for me. At the scale of a large organization, the rebuild is most of the bill.

Attention is the first hidden one, and it is the one I pay myself, every day: deciding what to ask, loading the context, reading the output closely enough to trust it, catching the confident mistake and steering it back. It feels like working and it is mostly supervising, and it has a name now, botsitting, where I wrote it out in full along with the felt speed that hides it.

Coordination is the second hidden ledger, and it is the one that eats the gains. AI makes you faster at the parts of your job you can change by yourself, and does almost nothing for the parts that need other people: the approval, the handoff, the review that is already a bottleneck. Worse, polished hollow output passed downstream, workslop, can make the system slower than before, and the coordination half of botsitting walks through the arithmetic of one incident.

Development is the slowest ledger and the one I worry about most for the people coming up behind me. It is the cost of what the work used to teach. The same tool that can fold a beginner's experience curve shorter can let them skip the repetitions that were quietly building their judgment, and which of the two happens is the subject of Compressed or Destroyed. Not all friction is waste. Some of it is training, and a company that strips out every repetition can save a great deal of time while hollowing out its own talent pipeline.

The skill that runs through all four

There is one skill that decides how heavy each of those ledgers gets, and it is not prompting. It is knowing where the tool is good and where it is quietly bad.

The research calls the boundary a jagged frontier: the tool is strong in one place and subtly broken half a step over, just as fluent on the problem it cannot do as on the one it can, and from the inside the two feel identical. The study behind the name, and the four moves I use at the edge, are in The Jagged Frontier.

So the real skill is judgment under uncertainty: knowing when to delegate, when to steer, when to verify, and when to close the tool and think alone. I do this constantly, mostly without noticing, and the days it goes well are the days I correctly guessed which side of the frontier I was on. The cognitive scientists frame the underlying move as value-based: we offload a piece of thinking when it feels effortful or low-value, weighing the cost of doing it ourselves against the cost of checking what the machine did. Good offloading frees you for higher work. Bad offloading weakens a muscle you still need. Telling them apart, in the moment, on a specific task, is the whole job now.

What the four ledgers are for

I keep coming back to a frame I have written about before, which is that most of the work of getting anything right is making the real state of a system visible so nobody has to go hunting for it. The four ledgers are that move pointed at AI cost. The reason companies buy AI and cannot find the return is not that the return is fake. It is that they are reading one ledger and getting billed on four. The gains are real and local. The costs are real and spread across attention, coordination, and development, where no dashboard is looking.

None of this is an argument to use less AI. I use more of it every year, and it has changed how the work actually feels. It is an argument to stop treating AI as a cheap answer engine and start treating it as a cognitive prosthetic, something that can genuinely extend you and can also, used badly, weaken the body around it. A prosthetic is worth a great deal. It is also not free in the way a subscription is free once you have paid for it.

The mature version of the question is not how much AI your people should use. It is which parts of human thinking you want to make cheaper, which parts you want to protect, and which parts you want to grow. The companies that win will not be the ones that buy the most. They will be the ones that redesign the work while keeping alive the human capacities that made the work worth doing in the first place. That decision does not live on the invoice. It never did.