Instead of building massive teams around one or two products, Anduril launches dozens of products, each with a small, lean, autonomous team. The founder finds this approach easier to manage as it avoids middle management bloat, keeps the 'cooks in the kitchen' to a minimum, and leverages natural team dynamics.
To scale to a multi-product company, Grammarly treats each acquired product as its own "startup" with its own P&L. They are tightly aligned on vision but loosely coupled in execution, preserving founder autonomy while leveraging shared platform services like billing and identity.
Legora has successfully scaled its product organization by hiring former YC founders to lead autonomous 'pods.' This strategy leverages the fact that founders excel in environments with high ownership and delegated responsibility, allowing them to operate their product area like a mini-startup and maintain development velocity.
Large companies like Rippling and TripActions maintain innovation velocity by creating "carved out" teams for new, "zero to one" initiatives. This organizational strategy provides singular focus, empowering a small group to execute with the intensity and speed of an early-stage startup without corporate distractions.
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.
Instead of a single centralized growth team, ElevenLabs creates dedicated "sharded" growth teams for each product line (e.g., consumer app, creator tools). These pods act as mini-CMOs for their product, supported by a horizontal team of channel specialists like SEO and performance marketing leads.
To innovate at scale, Harness treats each new product as a semi-independent entity. These "startups" have a founder-like PM, go through internal seed/Series A funding stages tied to revenue milestones (e.g., $1M ARR), and are responsible for their own initial founder-led sales.
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.
PostHog manages its 16+ product suite by assigning small, autonomous teams of roughly three engineers to each product. This "compound startup" approach allows them to go wide, competing with multiple point solutions while remaining flat and avoiding bureaucracy. The small team structure fosters ownership and rapid development.
Staying lean is a deliberate product strategy. Bigger teams may build more features and go-to-market motions, but smaller, focused teams are better at creating simpler, more intuitive user experiences. Focus, not capital, is the key constraint for simplicity.
To avoid bureaucratic bloat, organize the company into small, self-sufficient "pods" of no more than 10 people. Each pod owns a specific problem and includes all necessary roles. Performance is judged solely on the pod's impact, mimicking an early-stage startup's focus.