Cloudflare cut 20% of its workforce. Then grew engineering 45%. Your org chart is about to flip.

Cloudflare cut 1,100 people in May.

Same quarter it posted $639.8 million in revenue. Up 34% year over year.

But here's what nobody's talking about.

While cutting those 1,100 roles, Cloudflare simultaneously grew its engineering headcount from 1,308 to 1,894. A 45% increase in engineers. During a layoff.

CEO Matthew Prince reached back to Peter Drucker's 1954 framework to explain it.

Every company has three kinds of workers: builders who make things, sellers who find buyers, and measurers who handle everything else. Finance. Compliance. Legal review. Middle management.

Cloudflare kept its builders and sellers. It cut its measurers. Not because those people performed poorly. Because AI tools made an entire category of coordination work redundant.

Internal AI usage surged 600% in three months. Thousands of AI agent sessions running daily across engineering, finance, HR, and marketing.

Prince says this pattern will repeat at every company. Fewer coordinators. More engineers who can direct and evaluate AI agents.

Restructuring charges: $140 to $150 million. But Prince expects Cloudflare to have more total employees by 2027 than any point in 2026. The growth just won't look like it did before.

Audit your org chart through Drucker's lens. Count your builders, sellers, and measurers. If your measurers outnumber your builders, you're carrying overhead that AI is about to make obsolete.

SOURCE: https://startupfortune.com/cloudflare-cut-20-of-its-workforce-while-growing-its-engineering-team-and-matthew-prince-says-every-company-will-do-the-same/
VERIFIED: Startup Fortune (Jun 28, 2026), Cloudflare Blog "Building For The Future" (May 7, 2026), SecurityWeek (May 11, 2026)
SIGNAL: This is the first mass layoff where the CEO publicly framed cuts as a Drucker-style role reallocation rather than cost-cutting. The 45% engineering growth during a 20% workforce reduction is the new template. Every enterprise leader needs to understand this pattern before their board asks why they haven't done it.