The job apocalypse hasn’t started. That’s what worries me.

I build with AI every day. My studio makes brand creative entirely with AI tools. My team ships agents and products for clients. I teach this at a graduate school, which mostly means I get asked questions I can’t answer yet.

That gives me a narrow but useful view. I’m not reading about capability curves. I’m watching my own invoice math change month by month.

From that seat, the “nothing happened” reading is hard to square with what’s on my screen.

Two years ago a single campaign asset needed a designer, a copywriter, a researcher, and someone to keep them on schedule. Four people, a week, plus revisions.

Today most of that sits with one person and a well configured setup. Not all of it, and not perfectly. The color grading still argues with me. But enough that the economics have moved.

When I look at what I produce in a week now, I find it hard to argue that no job disappears from this. To believe that, I’d have to believe the capability stops here. Nothing in the last three years suggests it stops here.

We’ve built agents and products across a wide spread of industries now, in Europe, in Asia, and for companies selling into the US. The functions repeat: marketing, finance, HR, sales, data analytics, customer service.

Here’s what surprised me. The feature sets rhyme.

In marketing it’s asset generation with brand rules enforced at the gate. In finance it’s document extraction and reconciliation with an exception queue. In HR it’s screening and policy answers with an audit trail. In sales it’s account research and proposal drafting. In analytics it’s querying messy data in plain language. In customer service it’s triage, draft, route, escalate.

Strip the labels off and you’re looking at the same six or seven parts. Retrieval over documents nobody has organized. Structured extraction. Drafting with a review gate. Routing. Summarizing with sources attached. A human at the end who approves.

Six functions. One skeleton.

The building blocks are converging. The value isn’t in the blocks. It’s in the context.

That’s what makes this different from earlier software waves. Generic capability gets cheap almost immediately. The expensive part is knowing how one particular company actually works, and that knowledge doesn’t transfer. Its vocabulary. Its exceptions. Its approval chains. Its bad habits.

We ship something that looks like the last one and behaves nothing like it, because the context belongs to that company and nobody else. That is also why these builds don’t turn into a product you can sell twenty times without touching it. I’ve tried.

Worth being careful here, because my claim is narrower than the headlines and, I think, more uncomfortable.

I have not seen a client fire a department because we shipped an agent. Not once, in any market.

What I have seen, every single time, is a client who comes out of it able to do more with the same headcount.

Then comes the part that matters. Somewhere between the pilot working and the rollout finishing, a conversation happens about an open role. Sometimes I’m in the room. The sentence is close to identical across sectors and across markets:

That’s not a layoff. It never reaches an unemployment number, because the only trace it leaves is a job posting nobody writes.

Deferral is the rational move here, which is why it spreads without anyone noticing.

Cutting a person costs money, takes months, damages the team, and forces a public admission that the role was a mistake. Not filling an open seat costs nothing. Nobody signs anything. Nobody gets a difficult conversation. The budget line simply goes unused, which in most companies makes you look disciplined rather than reckless.

So a manager who suspects a role might be automatable in a year has one obvious play. Wait. Run the existing team harder with better tools. Revisit at the next planning cycle.

The freeze isn’t a decision anyone announces. It’s a decision nobody has to defend.

Repeat that across a few thousand companies and you get what we have now. Stable employment. Stable unemployment. And a hiring market that everyone I talk to describes as strange without being able to say why.

Here’s my position, stated plainly.

Jobs are not disappearing at scale yet. What’s disappearing is the reflex to hire for anything that isn’t essential.

Essential roles still get filled, along with anything revenue critical and anything where a mistake gets expensive fast.

Everything in the middle waits. The coordination role. The second analyst. The junior who was going to do the first pass. The support hire. The “we probably need someone for this” job that used to get signed off without much argument.

That’s not destruction. It’s deferral, and it’s much harder to see.

So far this reads like an accounting story. It isn’t. Somebody absorbs it.

If you want to know who pays for this first, it isn’t the senior person whose judgment the company is buying. It’s the person who was going to be hired in order to learn.

Entry level knowledge work was built on a simple trade. The junior does the first pass, the research, the draft, the cleanup. That work is slow and imperfect, and companies tolerate it because in three years the junior becomes the person who can do the hard part.

An agent does the first pass now. Faster, cheaper, at two in the morning, without asking for feedback. The immediate math is obvious to everyone in the room. Nobody’s job description covers the three year math.

I don’t have a clean answer to this. When the question comes up in client conversations, the answers don’t survive much pressure, and I don’t think that’s carelessness. The cost lands in a future quarter. The saving lands in this one. Almost nobody is paid to optimize for the first.

Two things shifted at once, and they compound.

The first is capability. A good share of the tasks that used to justify a headcount can now be done well enough by a configured system, on demand, at a monthly cost closer to a software license than a salary. That is the comparison the budget holder is making, whether or not it’s fair.

The second is harder, and it’s about value.

If a role was mostly production, that contribution is now cheap. Making the deck. Writing the report. Building the campaign variant. Drafting. Reconciling. Answering the ticket. Those were real jobs built on real effort. The effort has collapsed.

Justifying the hire is getting harder. Justifying a premium for the value that position used to represent is getting harder still.

What survives is judgment. Deciding what to build, when to stop, what’s wrong, what to risk. I do believe that.

But judgment was never the thing that got billed. It rode along inside the hours and the headcount, invisible, priced by accident. Remove those and the vehicle that carried judgment to the invoice goes with them. I haven’t solved that for my own business either, and I’m not going to pretend I have.

If the effect is a hire that never happens, then the standard dashboard can’t see it.

Unemployment is a lagging measure, and a blunt one. It counts people who lost a job. It doesn’t count jobs nobody ever created.

If I wanted to catch this early, I wouldn’t watch the unemployment rate. I’d watch:

That last one is the most underrated signal I know. A role that sits open for nine months has been eliminated in everything but paperwork, and nobody sends a memo about it.

This next part matters, because I’m inside the industry and inside the incentive.

I sell AI capability. That’s a reason to discount my forecast, not to accept it. People who build a thing tend to overestimate how far and how fast it travels. I’ve been early before, and being early is just being wrong with better excuses.

The current architecture may plateau. This isn’t a fringe position. The leaders of the largest AI labs have each said publicly, in the past year, that reliable long horizon autonomy will need something beyond the architecture behind today’s chatbots. None of them has shown that successor working at scale. If the plateau arrives first, the deferral I’m describing partly reverses. Companies wait, find out the systems can’t close the gap, and hire again.

There’s also a version where the shift is real but lands somewhere nobody expects. Cheaper intelligence could grow demand instead of shrinking employment. That has happened before with other inputs. The spreadsheet was supposed to end bookkeeping and instead produced more financial analysts than the world had ever employed.

I don’t know which of these lands. Nobody does. What I’d rather not do is find out by waiting, because the cost of being wrong isn’t symmetrical. If I overprepare and the plateau arrives, I’ve lost some evenings. If I underprepare and it doesn’t arrive, I spend the rest of my career explaining what I used to do.

None of that is a reason to sit still. Here’s what I’d do, and roughly what I am doing.

The thing I keep coming back to is that this transition won’t feel like an event.

No announcement. No dramatic morning. Just roles that stop getting posted, teams that stop growing, and career paths that lose their first rung while nobody’s looking. By the time it’s measurable, it’s finished.

I’m not predicting an apocalypse. I’m saying the apocalypse framing is what lets everyone relax, because when the apocalypse misses its date, we decide nothing is happening.

Something is happening. I see it in my own P&L, in my delivery, and in most client conversations I’ve had this year. It just isn’t loud enough to make anyone act.

Written at the end of July 2026. I’ll revisit this in six months and mark up what I got wrong. If you want that follow up, it goes out to mynewsletter list.