Get your free personalized podcast brief

We scan new podcasts and send you the top 5 insights daily.

Contrary to traditional scaling, adding people to an early-stage AI project often slows it down. When the product concept is small enough for one or two people to hold in their heads, the cost of coordination and alignment with a larger team outweighs the benefits of more builders.

Related Insights

AI tools dramatically reduce the resources needed for idea validation. Leaders should restructure teams by creating small, nimble 'discovery' pods (1-2 people) for rapid idea generation and validation. Successful ideas are then passed to larger, traditional 'execution' teams for scaling and implementation.

Resist hiring quickly after finding traction. Instead, 'hire painfully slowly' and assemble an initial 'MVP Crew' — a small, self-sufficient team with all skills needed to build, market, and sell the product end-to-end. This establishes a core DNA of speed and execution before scaling.

If hiring more people isn't increasing output, it's likely because you're adding 'ammunition' (individual contributors) without adding 'barrels' (the key people or projects that enable work). To scale effectively, you must increase the number of independent workstreams, not just the headcount within them.

Contradicting the common startup goal of scaling headcount, the founders now actively question how small they can keep their team. They see a direct link between adding people, increasing process, and slowing down, leveraging a small, elite team as a core part of their high-velocity strategy.

According to the 'dark side' of Metcalfe's Law, each new team member exponentially increases the number of communication channels. This hidden cost of complexity often outweighs the added capacity, leading to more miscommunication and lost information. Improving operational efficiency is often a better first step than hiring.

Gamma's CEO resists the pressure to scale headcount aggressively, arguing that doubling the team size does not guarantee double the speed. He believes a smaller, more agile team can change direction faster, which is more valuable than raw speed in a rapidly evolving market.

The study's finding that adding AI agents diminishes productivity provides a modern validation of Brooks's Law. The overhead required for coordination among agents completely negated any potential speed benefits from parallelizing the work, proving that simply adding more "developers" is counterproductive.

The belief that adding people to a late project makes it later (Brooks's Law) may not apply in an AI-assisted world. Early reports from OpenAI suggest that when using agents, adding more developers actually increases velocity, a potential paradigm shift for engineering management and team scaling.

The narrative of tiny teams running billion-dollar AI companies is a mirage. Founders of lean, fast-growing companies quickly discover that scale creates new problems AI can't solve (support, strategy, architecture) and become desperate to hire. Competition will force reinvestment of productivity gains into growth.

As you scale a team or delegate more, communication overhead and misalignments will inherently reduce efficiency. This is a fundamental trade-off. The goal isn't perfect efficiency; it's greater total output, which requires a higher tolerance for these diseconomies of scale.