Monday.com cut somewhere between 620 and 630 jobs last week, roughly 20% of its roughly 3,000-person workforce, with about 350 of those roles in Tel Aviv. The company's own filing discloses only the percentage; the headcount depends on which outlet you read. The restructuring will run the company $45–55 million in charges. Most outlets that covered it filed the story under the same heading tech media has used all year: another company blaming AI for layoffs.
Co-founder and co-CEO Eran Zinman went out of his way to say that's not what happened.
"The result of a management decision about how to structure the company for its next chapter."
— Eran Zinman, Co-CEO, Monday.com, in his note to departing employees, via Storyboard18
He was specific about what the cut wasn't: it wasn't AI replacing the people who got laid off. What actually happened is a management-layer flattening — fewer layers between the company's smaller teams and its decision-makers, more ownership pushed down to the people who remain. And the money isn't going to margin. Zinman's own words: "We intend to reinvest the vast majority of the savings in our people, our products, AI, and future growth."
Read past the headline number and the interesting detail isn't the cut. It's where the reinvestment is pointed: increased customer implementation support, specifically to help enterprise customers adopt the company's new AI agents and workflow automation.
Sit with that for a second, because it cuts against the entire assumption baked into this year's AI-layoff coverage. The working theory has been that AI products let companies serve more customers with fewer humans. The model does the work the support team used to do. Monday.com's own restructuring says the opposite is true for at least one function: selling an AI product to an enterprise customer creates more implementation burden, not less. Someone has to help a client's ops team figure out what the AI agent should actually be configured to do, catch it when it does the wrong thing, and translate "the chatbot can generate reports" into a workflow their business actually trusts. That's a harder, more technical version of customer success than the one it's replacing, and it doesn't get automated away by the same product that created the need for it.
This is the same mistake as reading the Thomson Reuters restructuring as a pure replacement story. The headline number always describes the org chart's past, never its next hire. What's different here is which direction the surprise runs. Most of this year's "AI restructuring" stories turn out to be cost-cutting wearing AI vocabulary once you check the hiring math. Monday.com's checks out the other way: a company shedding a management layer while explicitly growing a customer-facing function that only exists because its AI product needs humans standing next to it.
If you're a CTO or VP of Engineering shipping agents, automation layers, or "does the task for you" features that touch enterprise customer workflows, don't assume the support headcount curve bends down. Ask what your customer's ops team needs to trust the thing enough to rely on it, and staff that role before the complaints do. It's not a classic support hire and it's not a classic solutions-engineer hire either: it's someone fluent enough in your AI product to debug it in front of a client and translate the failure mode into a fix. Most companies don't have a job description for that yet. Monday.com just told you, in public, that it's building one.
VC5 Consulting places the customer-facing technical hires that AI product launches quietly require — the implementation and support roles that don't exist in your org chart until the product ships and the first enterprise client needs a human who can debug it live. If you're staffing that function from scratch, let's talk.