Skip to Content

WHEN AI COSTS MORE THAN THE PEOPLE IT REPLACED: NOTES FROM THE PASSENGER SEAT

September 11, 2026
Martin Kastenbaum

In my last post, I compared AI to handing the car keys to an enthusiastic child — eager, overconfident, and blissfully unaware of consequences.

It turns out some companies didn’t just hand over the keys. They handed them over, went back inside, and are now stunned that the kid burned through a tank of premium in 20 minutes.

Welcome to the moment when AI token bills exceed the salaries of the employees AI supposedly replaced.

And just like before, the problem isn’t the kid. It’s the adults who forgot to stay in the car.

The Myth of “AI as Cheap Labor”

Somewhere along the hype cycle, AI became framed as a cheaper worker — tireless, scalable, and conveniently non‑human.

But AI isn’t a worker. AI is a workload.

And workloads don’t get cheaper when you scale them. They get bigger. Especially when they’re built on top of large models that bill by the token, not by the hour.

Companies thought they were eliminating labor costs. What they actually eliminated was friction — the human kind that prevents systems from spinning out of control.

Why Token Spend Is Exploding

Architects have seen this pattern before.

Cloud lift‑and‑shift. Microservices sprawl. Kubernetes clusters that look like spilled Legos.

AI is simply the latest chapter.

The real cost drivers are architectural, not magical:

  • Unbounded inference loops — agents calling agents calling agents, like a kid circling the block because it “felt right.”
  • Oversized models — giving the child a Ferrari instead of a go‑kart.
  • Prompt bloat — stuffing the trunk with every piece of context ever written.
  • Hallucination retries — missing the driveway and looping until the model feels confident.
  • Chatty orchestration — narrating every thought back to the model.
  • No caching — forgetting every turn and re‑navigating from scratch.

This isn’t an AI failure. It’s an architecture failure.

The Architectural Paradox: AI Needs Total Access

To be useful, AI needs visibility into everything — systems, data, workflows, contracts. To be safe, enterprises need to restrict everything.

That tension is the new architectural battleground.

It’s the same paradox as giving a child the keys:

You want them to learn. You want them to explore. But you also want your car back in one piece.

AI autonomy without boundaries isn’t innovation. It’s negligence.

The Human Layer Was Never Optional

In my last post, I argued that adults need to stay in the car — not because the kid is dangerous, but because the kid is inexperienced.

That point has aged remarkably well.

Over the past few months, the industry has shifted from “AI will replace us” to a quieter, more uncomfortable realization: AI has no judgment, no memory, no sense of cost, and no intuition for when to stop. It doesn’t know your history, your constraints, or your risk tolerance.

It just drives.

Humans bring:

  • Judgment
  • Context
  • Institutional memory
  • Accountability

AI brings:

  • Speed
  • Scale
  • Pattern recognition

Remove the humans, and the AI doesn’t become more efficient. It becomes unbounded — a child behind the wheel with no adult in the passenger seat.

The New Role of the Architect: Designing Boundaries, Not Boxes

AI shifts the architect’s job from designing systems to designing limits.

  • Bounded inference design
  • Token budgets as cost guardrails
  • Semantic caches as efficiency layers
  • Policy engines as ethical governors
  • Human‑in‑the‑loop checkpoints as the new brakes

The future of architecture isn’t about controlling intelligence. It’s about containing it.

The Punchline: AI Didn’t Replace People — It Replaced Predictability

And predictability is what keeps the car on the road.

The companies now panicking over AI costs aren’t victims of AI. They’re victims of their own assumptions.

They believed AI would drive itself responsibly. They believed autonomy was free. They believed the hype instead of the architecture.

But the truth is simple:

AI doesn’t eliminate the need for architects. AI makes architects indispensable. Because someone still needs to sit in the passenger seat, watch the road, and say, “Ease up — you’re burning fuel.”

About the author

Applications & Cloud Technology | United States
As a Senior Manager in the Applications & Cloud Technology practice and a Fellow at Sogeti Labs, Martin specializes in Kubernetes, DevOps, and AI-assisted development, helping shape technology strategy and mentor teams across the organization.

Leave a Reply

Your email address will not be published. Required fields are marked *

Slide to submit