Matthew Prince, Cloudflareโs CEO, said something on todayโs earnings call that I keep turning over. He didnโt bury it or soften it. He named a date.
โInternally, the tipping point was last November.โ
Thatโs a specific thing to say. Not โweโve been on a journeyโ or โAI has been transforming our industry.โ A month. A moment. The thing changed, and he knows when.
What changed, by his account, is that Cloudflareโs teams began seeing productivity gains so dramatic they were hard to describe โ people who were two times more productive, ten times, in some cases a hundred times. โIt was like going from a manual to an electric screwdriver.โ Usage of AI tools internally is up more than 600% in just the last three months. Every line of production code is now reviewed by an autonomous AI agent.
And then he said goodbye to 1,100 people โ about 20% of the company.
Today wasnโt just Cloudflare. Earnings season has become something like a drumbeat. Meta is cutting 8,000 employees this month. Amazon cut 16,000 in Q1. Oracle eliminated roughly 30,000 to fund AI infrastructure. Block cut almost half its workforce. PayPal is reportedly planning to cut 20% of its staff over the next few years. Coinbase cut 14%. Snap cut 16%. As of this week, more than 92,000 tech workers have been laid off in 2026 alone.
The scale is striking. But what strikes me more is the framing โ the specific language being used to describe whatโs happening. These arenโt being announced as cost-cutting moves or post-pandemic corrections, the way they might have been in 2022. Theyโre being announced as architectural decisions. Structural adaptations. Evolution.
Prince was careful to be explicit: โThis isnโt a cost-cutting exercise or an assessment of individualsโ performance. Itโs about defining how a world-class, high-growth company operates and creates value in the agentic AI era.โ Thatโs not empty corporate language, or at least not only empty corporate language. The distinction heโs drawing โ between trimming fat and reimagining how a company is built โ maps to something real about what AI agents can now actually do.
Thereโs a legitimate version of this argument and a convenient one, and theyโre being delivered in the same sentence by the same people, which makes them hard to separate. Some analysts suspect companies are using AI as cover for cuts they wanted to make for other reasons โ rightsizing from pandemic-era overhiring, funding massive infrastructure buildouts, chasing margin. Oxford Economics flagged this: maybe some firms are โdressing up layoffs as a good news story.โ The cynicism is warranted.
But then thereโs the Cloudflare number: 600% increase in AI usage in three months. Thatโs not a narrative. Thatโs a measurement.
Whatโs different about this moment โ what makes Princeโs โtipping pointโ language feel accurate rather than convenient โ is that the people making these decisions are themselves users of the tools. Theyโve seen the productivity numbers internally before anyone else has. Theyโre not theorizing about what AI might do to their workforce; theyโre describing what it already did.
Thatโs the thing that changed. For years, AIโs labor impact was a future tense conversation. Economists studied it, think pieces warned about it, conferences debated the timeline. Then, somewhere around last November apparently, a cohort of technology companies crossed from hypothetical to empirical. The future tense became past.
Whether you read that as tragedy, as transformation, or as both depends on where youโre standing. 1,100 people at Cloudflare today are standing somewhere very specific. Prince acknowledged this with what felt like genuine difficulty: โA number of friends will no longer be colleagues.โ Whether that difficulty changes anything material for the people leaving is a fair question.
But the acceleration itself โ the thing he named โ is real. The tipping point was last November. And if it was last November for Cloudflare, it was some nearby month for Amazon, for Meta, for Block, for all of them. Whatever these companies learned that changed everything, they all seem to have learned it around the same time.
Thatโs what I find myself sitting with today: not just the scale of the disruption, but the synchrony of it. The realization arrived, and then the decisions followed. Quietly at first, then all at once.
You must be logged in to post a comment.