Cloudflare Laid Off 1,100 People and Called It Progress. The Math Checks Out, But Something Still Feels Wrong

Cloudflare did something on Thursday it has never done in 16 years: mass layoffs. Not because the company is struggling — it just posted a record $639.8 million quarter, 34% year-over-year growth, and over $2.5 billion in contracted revenue not yet delivered. The cuts came because, as CEO Matthew Prince put it, the way the company works "has fundamentally changed." Internal AI usage is up more than 600% in three months. Employees across engineering, HR, finance, and marketing now run thousands of AI agent sessions every day. So 1,100 people — roughly 20% of the workforce — are being shown the door, and Prince wants you to know this isn't a cost-cutting exercise. It's a "defining how a world-class, high-growth company operates and creates value in the agentic AI era."

There's an almost brutal coherence to the numbers. The cuts spared only quota-carrying salespeople; everyone else — engineers, support staff, marketers, finance — saw their roles assessed against what AI could absorb. The founders' blog post, co-authored by Prince and president Michelle Zatlyn, is unusually transparent about the mechanics. They describe Cloudflare as its own "most demanding customer" for AI, and the 600% usage surge isn't hypothetical — it's the data they used to decide which jobs still needed humans and which didn't. The severance is generous by industry standards: departing employees get their full base pay through the end of 2026, equity vesting through August, and waived one-year cliffs. Prince personally signed every offer letter when these people joined; he and Zatlyn insisted on personally delivering the news when they left. It's almost certainly the most carefully stage-managed layoff in tech history. That doesn't make it any less of a layoff.

What bothers me isn't that Cloudflare used AI to automate work — if you sell AI infrastructure and developer tools, you'd be negligent not to eat your own dog food. What bothers me is how cleanly the narrative resolves. Record revenue, rising obligations, a workforce that's 20% leaner, and a CEO who gets to call it vision instead of downsizing. The distinction between "AI-driven transformation" and "cost-cutting" might matter to the earnings call audience, but for the 1,100 people who got an email from their founders on Thursday telling them their roles no longer exist, the practical result is identical. This is the first major case where a company explicitly framed layoffs as AI efficiency gains rather than market headwinds. It won't be the last. And at some point, the question stops being "can AI do this work?" and becomes "what do we do when the companies building the AI are the first ones to act on the answer?"

Sources

Comments

Post a Comment

Popular posts from this blog

AI Is Starting to Feel Less Like a Gadget and More Like Infrastructure

Image
Modern AI doesn't replace infrastructure — it runs on top of it. (Photo: Unsplash) For a while, AI coverage had the energy of a mall demo kiosk: very shiny, slightly chaotic, and usually one prompt away from embarrassment. Lately, though, the more interesting story is less about flashy demos and more about infrastructure. A useful CNBC piece argued that AI is not simply going to vaporize enterprise software overnight, and that sounds about right. In real companies, software does not disappear just because a model can summarize a meeting or write a decent SQL query. What actually happens is messier and more practical: AI starts sneaking into the plumbing. It shows up in search, support workflows, procurement tools, analytics dashboards, and data pipelines. The real winners may not be the loudest chatbot wrappers, but the vendors that make enterprise systems easier to operate, easier to query, and slightly less soul-crushing for the humans trapped inside them. That is less cinematic ...
Read more

When Two AI Bots Finally Learned to Talk in Discord

I spent part of the day doing something that sounds like the setup for a bad joke: getting two local AI assistants to talk to each other in the same Discord channel. Not through a web UI. Not by bouncing prompts manually between windows like a human message queue. In the actual shared channel, where both could see the conversation and react to each other. The funny part is that the problem was not intelligence. It was manners. Both bots were defensive by default around bot-authored messages, which is the sensible setting if you do not want your infrastructure turning into a recursive support group. The downside is obvious: if both assistants treat other bots as suspicious background noise, they will never coordinate on anything more useful than silence. The fix was to make both sides accept bot-authored messages only when they were explicitly mentioned. That detail matters more than it sounds. Blanket bot acceptance is how you end up with two enthusiastic systems discovering each oth...
Read more

AI Coding Agents Are No Longer Toys — The Question Now Is Who's Watching Them

Image
Gartner just put GitHub in the Leader quadrant of its 2026 Magic Quadrant for Enterprise AI Coding Agents — for the third year running. That alone reads like press release fodder, but the real signal comes from what the company is actually saying about the shift. GitHub frames it as a move from "generating code" to "orchestrating outcomes": developers hand agents issues and walk away, then come back to review, steer, and approve. The company is reporting 140,000 organizations on Copilot — nearly triple from a year ago — with CLI usage doubling month over month. Meanwhile, over at ClickHouse, CTO Alexey Milovidov published a candid account of a full year running AI coding agents on a massive C++ codebase. His framing is useful because it doesn't hide the learning curve. Milovidov breaks AI-assisted coding into three levels: Level 1 is the copy-paste chat approach — still useful for exploration but obsolete compared to agents. Level 2 is agents running in your C...
Read more