The Real Economic Threat Isn’t AI — It’s Automation at Scale

Once you accept that we’re not in a speculative bubble — that what we’re watching is big tech finally deploying capital that’s been sitting idle for years — the next fear shows up quickly: if all this capital is being deployed, won’t AI wipe out jobs and crash the economy anyway?

I think that fear is misdirected. The existential threat to labor isn’t large language models. It’s physical-world automation, and it has very little to do with chatbots.

AI Makes You Faster. It Doesn’t Replace You.

I use AI every day. Claude Code is a core part of my workflow — I talk about it across this entire blog series. And I can tell you honestly: it makes me faster, but it doesn’t replace what I do.

AI is faster at writing code than me. That’s true. But I’m constantly correcting or questioning decisions — formatting, styling, making the code modular. The 0→1 is where AI struggles. The 10→100 is where it thrives. And the 1→10 is where, with good guidance, it can do well — but it needs guardrails.

The difference is direction. If you tell an AI “build me an app that does X,” you’ve given it too much liberty — it’ll confidently build you something that doesn’t work. But “I need to build feature X using Y in our application code that lives here at Z” — that’s where AI shines. It needs the constraints. It needs the existing codebase, the chosen libraries, the architecture decisions already made. A seasoned engineer with a good environment already set up and clear opinions about their stack turns AI into a force multiplier. A blank canvas with no direction turns it into a confident mess.

Does it reduce the number of people a startup needs? I’m unsure. It lowers the barrier for entry in some cases and allows builders to build faster — but that’s not the same as eliminating roles.

This is Jevons’ Paradox playing out in real-time: when technology makes something more efficient, we don’t use less of it — we use more.

The pattern is everywhere. Coal in 1865: Watt’s steam engine made coal 3x more efficient, economists predicted consumption would drop, and instead it increased 10x over the next 50 years because steam engines became viable for more applications. Spreadsheets in the 1980s: VisiCalc and Lotus 1-2-3 didn’t eliminate financial analysts — they made analysis so cheap that every department started doing it, and finance teams grew. Cloud computing in the 2010s: AWS didn’t reduce total IT spending — it eliminated the barrier to spinning up infrastructure, so companies launched more projects, ran more experiments, and spent more overall. I lived through that last one. The cloud didn’t shrink teams. It gave them more to build.

LLMs will likely follow the same pattern. As AI makes certain tasks faster, organizations won’t fire everyone — they’ll find more tasks worth doing. The bottleneck moves, but the work expands. White collar work shifts. It doesn’t vanish.

The “AI in Everything” Problem

Here’s the tension I see from the inside: there’s a clear direction from leadership to use AI and build AI products. AI in everything — even just throwing it in for buzzwords.

I watched a PE make a demo of something that used AI. I rewrote it with regex and parsing rules. Made it deterministic, cheap, and faster.

That’s the dirty secret of a lot of AI integration right now. LLMs are wonderful pieces of technology, but the last thing they are is deterministic. You can use the same large prompt multiple times and get different results. For a lot of use cases — data validation, parsing, rule-based processing — that’s a problem, not a feature. The companies I’ve been in pitch rooms with understand this: humans don’t scale, but AI isn’t good enough to replace them yet. The cost to process all this data with humans doesn’t make sense, but LLMs aren’t deterministic enough to do it reliably either.

That gap — between “humans are too expensive” and “AI isn’t reliable enough” — is where a lot of the real opportunity lives right now. Not in replacing people, but in building the tooling that bridges that gap.

The Real Automation Shock Is Physical

The fear that AI will eliminate white collar jobs misses what’s actually happening. There’s a movie called Hidden Figures where the women had the job title “Calculator” — that was literally their role. Now we have advanced calculators in our pockets. Nobody mourns the loss of that job title because the work evolved. The people evolved with it. That’s what AI is doing to knowledge work — it’s not eliminating roles, it’s changing what those roles focus on.

But physical automation is a different story entirely. When a robot replaces a warehouse picker, there’s no “evolution” of that role. The role is gone.

If you want to talk about an existential labor shock, stop looking at chatbots and start looking at warehouses.

The trucking industry employs 8.5 million people, including 3.55 million professional drivers. Studies predict anywhere from 400,000 to 60-65% of heavy truck driving jobs could be displaced by full automation. Warehouse roles involving repetitive tasks have already declined 29% since 2023 due to AI-integrated systems.

Amazon is the clearest case study. According to internal documents reported by The New York Times, Amazon plans to automate roughly 75% of warehouse operations by 2033 — potentially eliminating over 600,000 jobs. The company already operates more than 1,000,000 robots, approaching parity with its 1.56 million human workforce.

At a pilot facility in Shreveport, Louisiana, a thousand robots allowed Amazon to employ 25% fewer workers than traditional warehouses. By 2026, that number drops to 50%. The company plans to replicate this design across 40 facilities by 2027, starting with a massive warehouse in Virginia Beach.

The projected savings: $12.6 billion from 2025-2027 — about 30 cents per item shipped.

These systems don’t “assist” humans. They replace them. And unlike white collar roles, there’s no ambiguity — a truck either drives itself or it doesn’t, a warehouse either needs pickers or it doesn’t.

Why Amazon Needs This to Work

Here’s the business reality that makes this inevitable. AWS is roughly 15-17% of Amazon’s revenue but was 57% of the company’s profits. The retail and distribution side of Amazon is a massive revenue engine, but the margins are thin. Any reduction in labor costs on the distribution side is a welcome one — it reduces the overall shipping and storage cost per item.

If Amazon figures out physical automation at scale, they become the most profitable company in the world. That’s not speculation — that’s arithmetic. The infrastructure spending I talked about in Part I isn’t just about AI models and cloud compute. It’s about building the physical automation layer that turns Amazon’s revenue machine into a profit machine.

The autonomous truck market is projected to reach $1.5 trillion by 2034, growing at 16% annually. That’s not a chatbot making emails faster. That’s industrial transformation with a timeline and a spreadsheet attached.

Why AI Gets Blamed Anyway

AI becomes the villain because it’s visible. People interact with models daily. They feel replaced. They feel diminished.

But most of the capital isn’t flowing into replacing humans with chatbots. It’s flowing into machines, buildings, power, and logistics — the same places automation has always lived. AI is just the interface layer people see.

And inside these companies, the messaging doesn’t help. Leadership says “ruthless prioritization” and “use AI for everything” in the same breath. Engineers go through layoff after layoff — I’ve been through three rounds at Amazon — and then get told to be more efficient. The layoffs aren’t because of AI. But the narrative conflates them, and it’s easy to see why people connect the dots even when the dots don’t actually connect.

Capital Spending Creates Jobs — Just Not the Same Ones

Infrastructure spending creates work, but not evenly or immediately.

The jobs show up as construction, electrical work, hardware manufacturing, networking, power engineering, and data center operations. These aren’t jobs eliminated by AI — they’re jobs created by capital deployment. I think there will be more of a focus on servicing the robots, maintaining the hardware, and humans building things — furniture, art, anything handmade. When machines handle the repetitive physical work, the value of human craftsmanship goes up, not down.

But the mismatch is temporal and geographic, not existential. The uncomfortable truth is that the workers displaced from trucking and warehousing aren’t automatically qualified for robotics maintenance roles. The net job count might be positive while individual lives are disrupted. Aggregate statistics can hide a lot of pain.

Where This Argument Could Be Wrong

“What if AI is different this time?” Jevons’ Paradox assumes the technology is a tool that amplifies human capability. But what if LLMs become capable enough to fully substitute for knowledge workers — not just assist them? I’m skeptical this happens in the near term based on what I see daily in my own workflow, but I can’t rule it out at longer time horizons.

“White collar resilience might be temporary.” The jobs that feel safe today — strategy, judgment, relationship management — might be precisely the ones AI targets next. If models get significantly better at reasoning and context, the “ambiguity buffer” protecting white collar work could shrink faster than expected.

“The transition costs are still real.” Even if Jevons’ Paradox holds and new jobs emerge, the transition isn’t free. The net job count might be positive while individual lives are disrupted. That’s cold comfort if you’re a truck driver in your 50s.

“Policy rarely catches up.” I argue that physical automation is the bigger risk — but that assumes policymakers focus on the right problem. History suggests they usually don’t. We might end up regulating chatbots while autonomous trucks reshape logistics unimpeded.

What to Watch

If you want to track whether physical automation is actually reshaping the economy, here are the signals that matter:

Near-term (2025-2027): Amazon’s Virginia Beach facility goes live — does it hit the 50% labor reduction target? Waymo and Cruise expansion beyond Phoenix and San Francisco — watch regulatory approval velocity. Warehouse robotics density passing 1:1 robot-to-human ratio at major retailers.

Medium-term (2027-2030): First autonomous trucking corridors operating at scale, likely Texas and Arizona first. Port automation reaching 80%+ in major hubs — Rotterdam is already there, LA and Long Beach lag behind. Last-mile delivery economics flipping — when does robotic delivery cost less than human delivery in dense metros?

Policy signals: State-level autonomous vehicle legislation — permissive or restrictive? Federal infrastructure bills that include automation transition funding. Union negotiations in logistics and transportation sectors.

The infrastructure spending happening now will determine the pace of these transitions. The money is already allocated. The question is execution.

The Conversation We Should Be Having

The real risk isn’t that AI replaces everyone. It’s that automation concentrates gains too quickly, labor transitions lag capital transitions, policy moves slower than machines, and we misdiagnose the problem and regulate the wrong thing.

AI will change how work feels. Automation will change whether some work exists at all. Those are very different conversations — and we keep mixing them up.

“Calculator” used to be a job title. Now it’s an app. The people who held that title didn’t disappear — they became analysts, engineers, programmers. The work evolved, and so did they. That’s the pattern AI is following for knowledge work. But the warehouse picker, the long-haul trucker, the port operator — those roles don’t evolve when a robot can do them faster, cheaper, and around the clock. They just end.

The question isn’t whether the money gets spent. It already is. The question is whether we’re watching the right part of the story while it happens.