The May-2026 AI-restructuring cohort gained a developer-tools company on Monday evening, May 11, when GitLab CEO Bill Staples sent an internal memo — and an SEC 8-K filing — titled 「GitLab Act 2」.
Per Bloomberg, The Register, and The Next Web, the letter announced four simultaneous structural changes for a company that had 2,580 employees as of January 2026:
- Layoffs of an undisclosed number, to be finalized on or before June 1, 2026.
- Up to three management layers removed in certain areas.
- The R&D organization broken up into approximately 60 smaller autonomous teams.
- The company’s country footprint cut by up to 30% — GitLab currently operates in roughly 60 countries and will exit regions where it maintains only small teams.
Staples’s framing line, repeated in every reporter’s writeup:
「The cuts are not an AI optimization or cost cutting exercise. We intend to reinvest the vast majority of savings back into the business to accelerate our unique opportunity in the agentic era.」
The other sentence that got quoted, from the GitLab Act 2 blog post:
「Software will be built by machines, directed by people.」
Markets did not buy the framing distinction. GitLab shares dropped ~7% in after-hours trade the same evening, per Yahoo Finance Canada. The company’s next quarterly earnings call is June 2, which is also the day after the new org chart is supposed to be finalized.
What 「Act 2」 actually does to the org chart
The structural shape, holding the framing aside for a moment:
A 2,580-person company removes up to three management layers. In a company that size, that’s not a tweak — it’s typically Director→Senior Director→VP collapsed into a much shorter chain, with the surplus headcount in those layers either reassigned as ICs or exited. The 60-autonomous-teams split below it is consistent with a span-of-control target around 30–45 ICs per VP, which is roughly what you get if you assume each of the ~60 teams has a single tech lead and 25–40 engineers around it.
The 30% country-footprint cut is the part that’s hardest to reconcile with the 「not a cost-cutting exercise」 line. Per The Register’s reporting, GitLab is “exit regions where it maintains only small teams.” That sentence describes a real-estate-and-payroll cost line item with a specific dollar value attached. GitLab is all-remote — there’s no real estate, only employment costs and local-entity costs (legal, tax, HR, payroll providers) — so the 30% number is functionally a headcount math problem: the cohort of countries where GitLab has 1–5 employees gets closed, and those 1–5 employees per country either relocate to a remaining-supported country or are terminated. Either way it shows up as cost savings.
「Open restructuring」 is the other phrase Staples used. Yahoo Finance quoted the framing approvingly — GitLab has a public handbook culture and is doing the layoff out loud rather than via leaks. That’s a real cultural choice and worth crediting. It does not, however, change the underlying transaction.
Why this looks structurally identical to the cohort the framing rejects
Staples explicitly distanced GitLab’s Act 2 from the broader May cohort — Cloudflare, Bill.com, Freshworks, PayPal, Coinbase, Fidelity, GM. His claim is that GitLab is reinvesting savings into agentic-era growth rather than harvesting them as margin.
Compare the structural shape, four months in:
| Element | GitLab Act 2 | Fidelity May 7 | GM May 11 | Cloudflare April |
|---|---|---|---|---|
| Layoff number stated? | No | 1,000 | 600 | 1,100 |
| Net hiring number stated? | No | 5,300 | No | No |
| New-skills framing? | Agentic-era engineers | AI-native operations | Prompt eng + AI agents | AI workflow |
| Cost-savings reinvestment claim? | Yes | Yes | No | No |
| Management-layer flattening? | Yes (up to 3) | Implied | Partial | No |
GitLab’s only structural difference from the Gartner-disproven cohort — at the moment of the announcement — is the stated reinvestment intent. There is no announced net-hiring number, no published headcount target for end-of-2026, and no quantification of the 「vast majority of savings」 reinvested. June 2 will tell us more; until then, the structural shape is the same as the cohort the letter is trying to distance itself from.
The 「software will be built by machines」 sentence, said by a developer-tools CEO
The line is novel because of who said it. GitLab sells the platform that human developers use to write, review, merge, and deploy code. Its recent product positioning has leaned hard into Duo (GitLab’s AI assistant) and into an agentic-CI vision in which an AI agent reviews and merges pull requests. Telling a workforce of 2,580 — most of them software engineers who use the product they build — that 「software will be built by machines, directed by people」 is a coherent product thesis. It is also a coherent layoff thesis, and the company has not separated the two.
There is a Jevons-paradox version of this argument that holds: cheaper code production expands the addressable market for code faster than the per-line cost falls. Dario Amodei walked back his May-2025 half-of-white-collar-jobs prediction on similar grounds. If Staples means the Jevons version — GitLab needs more total software output to capture an expanding market, and agents are how it scales — then 「Act 2」 is a growth-and-amplification story.
But if Staples means the substitution version — fewer humans per unit of software, with the savings booked as margin — then 「Act 2」 is the same story as every other letter in May 2026, only with a more polished blog post.
GitLab announced one number on Monday and is sitting on the other one. The number it announced was the cut. The number it is sitting on is the headcount target for end-of-2026. Until those two numbers are published next to each other, the framing does not yet have evidence behind it.
What to watch
- June 2 earnings call. Staples committed to share「more details about the restructuring and its impact」 then. The key disclosure will be whether GitLab publishes a net-hiring or headcount-growth figure against the cuts, the way Fidelity did.
- Whether the 60-team R&D structure publishes its team manifests — GitLab’s handbook culture would normally dictate that it does. If the team grid is published, the granular distribution of engineers across product surfaces will reveal where investment is concentrating and where it is being withdrawn.
- The country list. GitLab is all-remote and the 30% country-footprint cut is the most operational of the four announced changes. Which countries get exited will tell us more than the slogan.
- Whether Duo’s pricing or capability roadmap shifts in the back half of 2026. If the 「reinvestment」 dollars flow into Duo Agentic, that’s the test of the reinvestment claim — not a press release, a product gate.
The honest read on the morning after is that GitLab has done two things at once: announced a structurally standard May-2026 AI-cohort layoff and labeled it differently. The labeling may turn out to be earned. It is not yet earned. The 7% after-hours move is the market saying the same thing.