We Spend on Intelligence Either Way

The first time the AI bill made sense to me, it was not because I found a cheaper model.

It was because I stopped looking at the bill like software spend.

I had spent about $537 in metered AI usage over four days. On its face, that number looks high if your mental model is “employee asks chatbot questions.” It looks very different if your mental model is “professional delegates work to a team of intelligence.”

That is the shift most leaders are still underestimating.

AI is not just a tool. A spreadsheet is a tool. A dashboard is a tool. A search bar is a tool.

AI reads, plans, drafts, critiques, delegates, revises, remembers, and synthesizes. That does not make it a person. It does not make it safe by default. It does not remove human accountability. But it does mean the management frame has to change.

We already spend on intelligence every day. We call it salary, billable time, utilization, leverage, margin, and delivery cost. Human intelligence has a price. AI intelligence has a price.

The strategic question is not whether intelligence should cost money.

It always does.

The question is which work should be done by human agency, which work should be done by AI agency, and how we know the difference.

That is where AI ROI actually begins.

The Wrong Question Is “What Did the Tokens Cost?”

Most AI reporting still starts with consumption.

How many users? How many prompts? How many conversations? How much model cost?

Those are useful operating signals. They are not ROI.

Nobody measures a consulting team by counting keystrokes. Nobody looks at a senior manager’s salary and says, “We need fewer sentences.” We ask what work got done, what quality came back, what cycle time changed, what risk was reduced, what client value was created, and whether the economics make sense.

AI should be measured the same way.

A token is not value. A token is a unit cost of applied intelligence. The ROI question is whether that intelligence produced useful work at a better cost, speed, quality, or scale than the alternative.

This is why “reduce AI spend” can be the wrong instinct. Sometimes the right answer is to spend less. Sometimes the right answer is to spend more because more of the work has moved into the system.

The real management question is more precise:

What did this intelligence cost, and what did it produce?

What Changed in My Four-Day Experiment

In my four-day work burst, the spend did not come from asking a chatbot a lot of clever questions.

The largest category was structured analytical production: decision maps, long-form synthesis, report writing, evidence shaping. That represented about 37 percent of the metered spend.

The second-largest category was context infrastructure: project memory, status logs, decision capture, and the machinery that lets agents work across projects. That was about 26 percent.

That second bucket matters more than it looks.

In ordinary chatbot work, the human carries most of the context. The model gets a prompt, maybe a file, maybe a summary, and answers inside that narrow window. The human remembers the client history, the last meeting, the open questions, the political constraints, the source quality, and the shape of the deliverable.

Agentic knowledge work flips more of that into the system.

The system has to read across documents, emails, transcripts, research, slides, spreadsheets, prior decisions, and partially stated preferences. It has to infer what matters. It has to leave some things out. It has to build enough context to act.

That costs more because the work is bigger.

Anthropic’s Claude Code cost guidance is useful context here. Their enterprise deployments average about $13 per developer per active day, and 90 percent of users stay below $30. But they also note that agent teams can use roughly seven times the tokens of standard sessions because each teammate maintains its own context.

That is the mechanism.

Agents cost more when they are not just answering. They are carrying context, coordinating steps, and doing work in parallel.

The Breakout Example: Research Synthesis

Here is the example that made the economics click for me.

One workflow in the four-day window was research synthesis and source review. In plain English, the work looked like this:

1. Build a research pack.

2. Run a deeper research pass.

3. Review market pressure and current-source evidence.

4. Create an evidence base.

5. Produce a source brief that could support a real argument.

The metered AI cost for that workflow was about $63.

Now compare that with human intelligence.

If a senior consultant did the same work manually, a conservative estimate is 24 to 36 hours. At a $150,000 salary benchmark, that is about $72 per hour. So the human-cost equivalent is roughly $1,700 to $2,600 before overhead, and much higher at a billable rate.

That does not mean the AI “saved” $2,500 by itself. That would be too easy.

The output still has to be reviewed. Sources have to be checked. The synthesis has to be challenged. The recommendation has to be shaped by someone with judgment.

But even if a human spends three or four hours reviewing and improving the output, the economics are still different. The human is no longer spending most of the time gathering, sorting, and drafting. The human is spending time deciding.

That is the point.

AI ROI is not only labor replacement. In professional work, the better frame is intelligence redeployment.

Take the work that humans do because someone has to grind through the context. Move the first pass into an AI workflow. Then move the human to the parts where human judgment is actually scarce: source skepticism, client implication, risk, taste, trust, and the final recommendation.

That is where the return shows up.

Not in cheaper words.

In better use of judgment.

This Is Also Why Humans Stay in the Loop

The best evidence for AI in consulting also explains why blind automation is dangerous.

In the BCG field experiment with researchers from Harvard, Wharton, and MIT, 758 consultants using AI completed 12.2 percent more tasks, completed them 25.1 percent faster, and produced work rated more than 40 percent higher in quality when the task was inside the model’s capability frontier.

That is the upside.

But on a task outside the frontier, consultants using AI were 19 percentage points less likely to produce correct solutions.

Same technology. Opposite result.

That finding should shape the operating model. AI agency is powerful when the workflow is legible, evidence can be checked, and quality gates are built into the process. Human agency matters most where the work is ambiguous, the stakes are high, the context is political, or the answer has to be owned.

The question is not “human or AI?”

The question is “what mix of human and AI agency does this workflow deserve?”

The Infrastructure ROI Question

This is where the AI Chief of Staff idea becomes less futuristic and more practical.

Imagine it takes two people three weeks to build the operating system around a leader: memory, preferences, work intake, project context, source rules, reusable workflows, specialist agents, review loops, and reporting.

That build has a cost.

At the same $150,000 salary benchmark, two people for three weeks is roughly 240 hours, or about $17,000 of human build cost before overhead. Add AI usage, governance time, and implementation friction, and maybe the real internal investment is higher.

Fine. Then measure it like any other investment.

If one repeatable research workflow costs about $63 in AI usage and redirects $1,700 to $2,600 of human effort before review, the payback question becomes concrete.

Use a rough formula:

Payback runs = infrastructure build cost / net value per workflow run

For the research synthesis example, assume the AI workflow costs $63 and a human still spends three to four hours reviewing the work. At the same salary benchmark, that review time is about $216 to $288. So the combined AI-plus-review cost is roughly $280 to $350.

Compare that with $1,700 to $2,600 of manual human effort.

Very roughly, that workflow redirects $1,350 to $2,300 of human capacity each time it runs.

Against a $17,000 build cost, the infrastructure pays back in something like 8 to 13 successful runs before overhead. If one consultant runs that workflow every week, the payback is measured in a quarter. If a team uses it across repeated client work, the payback arrives faster.

The exact number will vary. The method matters more than the decimal.

Now the conversation is no longer “AI is expensive.”

It is: “Which workflows pay back the infrastructure fastest?”

That is a much better question.

It tells you where to build first. It tells you where to keep work human. It tells you where a cheaper model is good enough. It tells you where a stronger model is worth it. And it gives leaders a way to compare AI infrastructure investment against workforce deployment.

A Consultant With an AI Chief of Staff

Picture a senior consultant on a Monday morning.

Today, that consultant may spend the first hour reconstructing the week: client emails, meeting notes, half-finished deliverables, status updates, research tabs, and the lingering sense that something important is hiding in yesterday’s transcript.

In the AI Chief of Staff model, that first hour changes.

The Chief of Staff has already assembled the brief. It knows the consultant’s active projects, what changed overnight, which client question is urgent, which deliverable is at risk, and which follow-ups are still open. It has updated the memory layer. It has flagged what needs human attention.

Then it starts routing work.

A meeting synthesis agent turns yesterday’s transcript into decisions, risks, and next steps. A research agent builds the source pack for a market question. A writing agent drafts the client-ready narrative. A validation agent checks claims, assumptions, and source quality. A workflow agent updates the project log and prepares the next status note.

The consultant is not out of the loop.

The consultant is finally in the right loop.

Instead of being the person who remembers everything, finds everything, drafts everything, and then reviews everything at 9 p.m., the consultant becomes the orchestrator and reviewer of a small intelligence system.

That role is not smaller. It is more leveraged.

It also changes staffing economics. Some work still belongs with people: relationship management, trust-building, hard judgment, escalation, original strategy, and anything where the cost of being wrong is high. Some work should move aggressively to AI: first-pass research, synthesis, meeting capture, draft creation, comparison tables, source briefs, status updates, and repeatable analysis.

The firms that learn this fastest will not simply cut cost.

They will increase output per professional.

The Market Is Moving, But the Model Is Still Open

This shift is already visible.

Deloitte expects 25 percent of companies already using generative AI to launch agentic pilots in 2025, rising to 50 percent by 2027. EY says its EY.ai Agentic Platform will initially integrate 150 AI agents supporting 80,000 professionals. KPMG says its Workbench platform has a network of 50 AI assistants, agents, and chatbots, with nearly a thousand in development.

But I would be careful with what that proves.

It does not prove that everyone has solved the future of professional work. Most of what is public still looks like defined workflow automation, task agents, or delivery platforms. Valuable, yes. Directionally important, yes. But not yet the full personal operating model: a persistent Chief of Staff that understands one professional’s work surface and orchestrates across the whole day.

That layer is still open.

OpenAI’s B2B Signals report points in the same direction. Frontier firms use 3.5 times as much intelligence per worker as typical firms, but message volume explains only 36 percent of the gap. The difference is not just more chat. It is richer context, deeper work, and more delegation.

McKinsey’s 2025 AI survey found that 23 percent of organizations are scaling an agentic AI system somewhere, but no individual function has more than 10 percent reporting scaled agent use.

The window is open because almost nobody has turned this into a scaled operating model yet.

The New Management Discipline

The next management discipline is not prompt engineering.

It is intelligence allocation.

For each workflow, leaders need to know:

1. What output are we trying to produce?

2. What human intelligence does it require today?

3. What AI intelligence could produce the first pass?

4. What review or judgment must stay human?

5. What did the combined system cost?

6. What outcome changed?

Ask that at the workflow level, not the chatbot level.

The answer will not be the same everywhere. Some tasks deserve high intelligence spend. Some deserve cheap automation. Some should stay mostly human. Some should become hybrid workflows with tight review gates.

That is the work now.

Not “How do we get everyone to use AI?”

“How do we redesign work around the right mix of intelligence?”

The firms that win will not be the ones with the most prompts or the lowest token costs. They will be the ones that learn to spend intelligence well.

Human intelligence where it matters most.

AI intelligence where it scales best.

And a measurement system that can tell the difference.