Cloudflare Cut 20%. Atlassian Cut 10%, Mostly Engineers. Bending Spoons Cuts Up to 75%. All Three Are Growing Faster or Earning More. So How Lean Can B2B Teams Really Get?

The Era of the Bloated B2B Giant is Ending

For a decade, the tech industry operated on a simple, flawed logic: more funding equals more hiring, and more hiring equals a better product. We treated headcount like a status symbol. If you had 500 engineers, you were a serious player. If you had 2,000, you were a juggernaut. But as the market corrected, a painful truth surfaced. Most of those people weren't building; they were managing the friction of having too many people.

We are currently witnessing a radical experiment in efficiency, and the results are uncomfortable for anyone who values job security in middle management. Bending Spoons, the Italian firm that recently acquired Airtable, just swung a heavy axe, cutting nearly 75% of the staff. This isn't just a trimming of the fat; it’s a total reconstruction of how a software company operates. And they aren't alone. Cloudflare and Atlassian have made similar, albeit less drastic, moves. The takeaway is the same across the board: these companies are actually performing better after the cuts.

The Bending Spoons Blueprint

When Bending Spoons takes over a product, they don't look for synergies or cultural alignment. They look for drag. Their recent moves with Airtable follow a pattern we saw with Evernote. They fired almost everyone and replaced them with a lean, hyper-focused core team. The justification from their leadership is simple: small teams ship more and they ship it better.

According to their recent updates, a tiny "Core" team at the restructured Airtable managed to ship over 30 major customer requests in just three weeks. For context, large B2B organizations often spend three weeks just debating the color of a button in a Slack channel. By eliminating the layers of product managers, sub-directors, and internal communications specialists, the distance between a customer's problem and an engineer's solution becomes zero.

Why Big Teams Fail to Ship

In my experience building and advising startups, there is a phenomenon I call the "Coordination Tax." As a team grows, the number of communication channels grows exponentially, not linearly. Once you hit a certain threshold, engineers spend 60% of their day in meetings explaining why they haven't had time to code. The product becomes a reflection of the organization’s internal bureaucracy rather than the user's needs.

Cloudflare’s 20% cut and Atlassian’s 10% reduction—which notably targeted engineering roles—weren't just about saving money. They were about reclaiming speed. These companies realized that a smaller group of high-output individuals can outpace a massive army of average performers who are constantly stepping on each other's toes. If you are a founder today, you have to ask yourself: how much of your payroll is dedicated to actually building, and how much is just managing the weight of the company itself?

The Founder’s Dilemma: Lean or Mean?

This trend is terrifying if you’re an employee, but it’s a masterclass for builders. The "lean startup" methodology was always supposed to be the goal, but easy venture capital made us lazy. We hired for roles we didn't need because we were told that's what "growth" looked like. Now, we are seeing that growth is actually decoupled from headcount. In many cases, headcount is a lead weight on growth.

However, there is a human cost and a brand risk here. Bending Spoons is often criticized for being cold and mercenary. They aren't trying to win "Best Place to Work" awards. They are trying to build highly profitable, highly efficient software machines. As a founder, you have to decide where you fall on that spectrum. You don't have to be ruthless, but you do have to be honest. If your team has doubled in size but your roadmap hasn't accelerated, you have a structural problem, not a talent problem.

What This Means for the AI Era

The timing of these cuts isn't a coincidence. We are entering an era where AI-assisted engineering allows one developer to do the work that previously required three. If an engineer can use LLMs to handle boilerplate, debugging, and documentation, the need for large "support" engineering teams vanishes. The bar for staying on a team is getting higher. You can no longer be a "cog in the machine." You have to be the one operating the machine.

For builders, this is actually good news. It means the barrier to entry for creating a world-class product is lower than ever. You don't need $50 million in Series A funding to hire a team of 100. You need a handful of obsessed builders and a clear understanding of your customer's pain points. The "Bending Spoons" model proves that even legacy products with massive codebases can be managed by small, elite squads.

The Takeaway for Builders

Stop measuring your success by the size of your office or the number of people reporting to you. Those are liabilities disguised as assets. The new B2B meta is high revenue per employee and extreme shipping velocity. If you can’t ship 10 customer requests in a month, your team is likely too big, not too small.

The goal of a software company isn't to employ people; it's to solve problems. When the employment becomes the primary focus, the problem-solving suffers.

We are heading toward a future of "Unicorns of One" or at least "Unicorns of Ten." The companies that survive the next five years will be the ones that embraced the lean model before they were forced to by a private equity firm or a predatory acquirer. Look at your org chart today. If you deleted a department, would your customers even notice? If the answer is no, you know what you need to do.

Read the original at SaaStr →