What ClickUp's bet really means for your team

Ready to transform artificial intelligence from a buzzword into your personal revenue generator?

HubSpot’s groundbreaking guide "200+ AI-Powered Income Ideas" is your gateway to financial innovation in the digital age.

Inside you'll discover:

Download your guide today and unlock a future where artificial intelligence powers your success. Your next income stream is waiting.

Get Your Guide

Two days ago, ClickUp laid off 22% of its workforce.

What makes this worth an entire edition is not the layoff itself. Layoffs happen. What makes it worth your attention is how the CEO framed it, because the framing is either the clearest articulation yet of where every company is heading, or the most sophisticated piece of layoff branding the industry has produced this year. It is probably a little of both, and untangling which part is which is genuinely useful for anyone who runs a team.

Here is what happened. Zeb Evans, ClickUp's founder and CEO, announced the cut in a long post on X. He was unusually direct about the framing. This was not, he insisted, a cost-cutting move. The business, he said, is the strongest it has ever been. He made the decision proactively because, in his words, the way to operate at the highest level of productivity is changing, and he would rather restructure now than have the market force it later.

Then came the part that made the whole tech industry stop scrolling. Most of the savings from the layoffs, Evans said, would not go to the bottom line. They would flow back to the employees who stayed, in the form of new salary bands reaching one million dollars a year in cash, available to almost anyone in the company who produces what he called 100x impact through AI.

He called the new structure the 100x org. AI agents now outnumber human employees at ClickUp by roughly three to one. The remaining humans are being reorganized into three categories. And he closed with a warning to the rest of the industry. Nearly every company, he said, will make changes like these.

This edition is about whether he is right, what the 100x org actually is underneath the branding, and what it means for how you should be thinking about your own team structure, whether you run a five-person startup or a five-hundred-person company.

Strip away the language, and ClickUp's new org has three kinds of people in it.

The first tier is builders. These are the engineers, product leaders, and designers who use AI agents to turn ideas into products. The important shift Evans is describing here is that the builder's value is no longer in the act of production. It is in judgment. An engineer is valuable not because they type code but because they decide what the agents should build and whether what the agents built is good. A designer is valuable not because they push pixels but because they have taste and customer intuition. Evans goes further and says product management and design are merging into a single role, the product builder, because once agents handle the production, the distinction between the person with the design skill and the person with the product skill collapses.

The second tier is system managers. This is the most interesting category and the one most relevant to readers of this newsletter. A system manager is an employee who automated a meaningful part of their own job with AI, and then became the owner of the system they built. Evans says ClickUp already has several of these internally. The logic he attaches to it is sharp. The safest career move inside the 100x org is to automate yourself, because the company cannot afford to lose the institutional knowledge of how the automated system actually works. The person who built the system that replaced their old job is now more valuable, not less, because they own the thing the company now depends on.

The third tier is front-liners. These are the people who spend their time with customers. Evans makes an argument here that is easy to miss and genuinely important. In a world where AI-generated communication is flooding every channel, genuine human contact becomes a scarce, premium thing. So front-liners are not being automated. They are being concentrated. Evans says front-liners should spend close to 100% of their time in actual customer conversations, while every system around those conversations, the scheduling, the notes, the follow-up, the research, is fully automated.

That is the structure. Builders who direct agents. System managers who own the automation. Front-liners who hold the human relationships. Everything in between, the coordination work, the production work, the repeatable execution, is absorbed by agents or eliminated.

I want to be fair to the substance here, because underneath the branding, there is a real and correct observation.

Evans is right that most companies have been adding AI incorrectly. They have been layering AI tools on top of an unchanged org chart. The same roles, the same team structure, the same workflows, with AI bolted on as an accelerant. We covered this in the AI Tool Tax edition. Adding AI to a structure designed for a pre-AI world produces marginal gains at best because the structure itself is the constraint.

Evans is arguing for something more honest. If AI genuinely changes what a single person can produce, then the unit of the team has to change too. You cannot get a step change in output from a structure designed around the old unit of production. The org chart has to be redrawn around the new reality, not decorated with it.

He is also right about the specific shape of the change. Judgment is becoming more valuable than production. The merging of adjacent roles once the production bottleneck between them disappears. The rising value of genuine human customer contact is precisely because everything else is being automated. These are not hype. These are accurate observations about what AI does to the structure of knowledge work, and a lot of companies are going to arrive at similar conclusions over the next two years, whether they want to or not.

The system manager idea in particular is worth sitting with. The reframe that automating your own job is the safest move rather than the most dangerous one is genuinely useful, and it is the opposite of how most employees instinctively think. If you run a team, communicating this clearly to your people is one of the highest-value things you can do this year. The person who hides what they automated and pretends the old job still takes 40 hours is the fragile one. The person who automates openly and becomes the owner of the system is the durable one.

Now, the other side, because the 100x org also has a clear failure mode, and most companies that copy it will walk directly into it.

The failure mode is this. A smaller team only moves faster if the systems around it actually work. If the agents produce vague, mediocre, or subtly wrong output, then the remaining humans do not get 100x leverage. They get buried. They spend their days reviewing agent output, catching agent errors, handling the customer escalations that the automated systems mishandled, and cleaning up the mess that gets produced at AI speed. In that scenario, the 100x org is not a productivity breakthrough. It is a layoff with better branding, and the remaining employees are doing more work than before, not less.

This is the honest risk, and it deserves to be named plainly. The 100x org is a bet that the systems are good enough to carry the load that the laid-off people used to carry. If that bet is right, ClickUp gets a genuine step change. If that bet is wrong, ClickUp has just removed a fifth of its capacity and handed the remaining people an impossible amount of review work, and the damage will show up on a delay, in product velocity, in enterprise renewals, in customer satisfaction scores, and in the quiet departure of the strongest people who did not sign up to be full-time agent supervisors.

There is also a question that the framing carefully avoids. The million-dollar salary bands are real, and they are the headline. But they are available to the people who produce 100x impact, which is, by definition, a small minority. For everyone else in the building, the message underneath the inspiring language is simpler and colder. Produce extraordinary leverage with AI, or you are in the next 22%. The 100x org is not just an opportunity structure. It is also a pressure structure, and the pressure is the part the announcement does not dwell on.

And the timing detail matters. ClickUp also did layoffs in 2022, which were described at the time as a one-time decision to reach profitability. A company doing its second major workforce cut in four years, now reframed as visionary restructuring, deserves to be read with a small amount of skepticism about how much is strategy and how much is narrative.

You are probably not going to lay off 22% of your company this quarter. So the useful question is not whether to copy ClickUp. It is what to actually take from this, and what to leave.

Take the diagnosis. The observation that AI bolted onto an unchanged org chart produces marginal returns is correct. If your team has added AI tools but kept the same roles, workflows, and team structure as two years ago, you are getting a fraction of the available leverage. The structure is the constraint, and at some point, the structure has to be redesigned, not decorated.

Take the three-tier lens as a thinking tool rather than a layoff plan. Look at your own team through it. Who are your builders, the people whose value is judgment and taste, who should be directing AI rather than doing production work by hand? Who are your potential system managers, the people who could automate a chunk of their own role and become the owner of that system? Who are your front-liners, the people whose value is a genuine human relationship and who should be protected from automation and concentrated on the human work? This lens is useful even if you never cut a single role. It tells you where to invest, where to automate, and where to protect.

Take the system manager's message to your people directly. Tell your team, explicitly, that automating their own work is safe and rewarded, not dangerous. The companies that get the most from AI over the next two years will be the ones whose employees automate openly because they trust that doing so makes them more valuable. The companies that get the least will be the ones whose employees hide their automation out of fear, because fear is the enemy of the exact behaviour you need.

Leave the layoff-first sequencing. The mistake to avoid is doing this in the order ClickUp did it, cut first and assume the systems will hold. For almost every company that is not ClickUp's size and stage, the right sequence is the reverse. Build and prove the systems first. Let your people automate their work and demonstrate that the automation genuinely holds at quality. Let the team shrink through natural attrition and through people moving into higher-leverage roles, rather than through a dramatic cut that bets the systems are ready before they have been proven. The 100x org, if it is real, can be arrived at by building up rather than by cutting down. The building-up path is slower and far less risky, and it does not require you to be right about the systems before you have evidence.

Here is the way I would hold all of this.

Evans is probably right that the org chart of a knowledge company is going to be redrawn by AI, and that judgment, system ownership, and human relationships are the three things that hold their value while repeatable production gets absorbed. That part is worth taking seriously, and the companies that ignore it will find themselves restructured by the market on a less favourable timeline.

But the 100x org, as ClickUp has executed it, cut first, restructure second, is a high-stakes bet with a real and specific failure mode, and the inspiring language around the million-dollar salaries is doing a lot of work to make a 22% layoff feel like a vision rather than a risk. Whether it was visionary or merely well-branded will be visible in about three quarters, in ClickUp's product velocity and renewal numbers, and not before.

For your own team, the lesson is not to copy the layoff. It is to take the diagnosis seriously, redesign around the three tiers deliberately, tell your people that automating themselves is safe, and build the systems up before you ever consider shrinking the team down.

The org chart is changing. That much is real. But changing it well looks like patient restructuring around proven systems, not a dramatic cut followed by hope.

The companies that get this right will not be the ones that cut the fastest. They will be the ones who rebuilt the most carefully.

See you at the next edition, Arindam