When to hire a dedicated growth team instead of growing the product through marketing

The short answer: you need a dedicated growth team once you have found product-market fit and have at least your first proven ways to acquire customers. Until then, growth remains the job of the founders and marketing.

a16z partner Andrew Chen, who previously led growth at Uber, puts it bluntly: if people don't use the product, optimizing growth is pointless. First you need a base of satisfied users, and only then do you scale it. That is why, as practitioners say, a growth team should scale PMF, not search for it.

How is a growth team different from marketing? Marketing handles channels and campaigns. A growth team works at the intersection of product, engineering and data: it changes the product itself, onboarding, invitations and retention. One article puts it this way: you need a dedicated team when such work comes up often enough that keeping a standing team is cheaper than asking others for help every week.

Signs that it's time:

• retention and NRR are stable, meaning the market needs the product;
• you have at least one working channel and want to scale it rather than search for one from scratch;
• experiments constantly require developers and analytics, not just ad setup;
• growth has hit a ceiling, and you need hypotheses, not just a bigger budget.

Signs that it's too early: you don't have PMF yet, there is no budget for channels, or the person you hire is expected to simply “sort out the marketing.”

Who should you hire first? The usual advice is to hire not a head of the function but a hands-on specialist who runs experiments themselves and understands data.

An example is Facebook. In 2007–2008, its audience stalled at around 90 million users. Chamath Palihapitiya then assembled the first growth team, which included engineers. They looked for the “aha moment,” that is, the action after which a user stays: adding seven friends in ten days. According to Palihapitiya himself, the team took Facebook from 50 million to more than 700 million users. Note the order: first a product people need, then a team that scales it.

Sources:

1. Andrew Chen (a16z) — You don't need a growth hacker
2. Lenny's Newsletter — How to hire your first growth team
3. Product-Led Alliance — 4 tried and tested ways to structure a growth team
4. StackMatix — Building a growth team at a startup
5. GoPractice — The history of growth hacking and Facebook's growth team (in Russian)
6. Chamath Palihapitiya — Deep Dive: A Primer on Mag7