Working · 2026-11PrimaryGrowth opsProcess

Early growth team: prove value, then scale

Start with one or a few people who cover both business thinking and implementation, win visibly, and scale to 10 to 20 once results justify it.

Also called: growth team zero to fifty

Claim and evidence

The claimStart with one or a few people who cover both business thinking and implementation, win visibly, and scale to 10 to 20 once results justify it.

No dated example yet. Treat this tactic as a hypothesis.

What the numbers show

No published number for this tactic has passed our word-for-word check yet, so there is no chart.

Why it works

Diagram, not data
Start smallwithstrategyandexecutionPicklikely-to-winprojectsCelebratewinspubliclyEarnresourcesto growSplit intolifecyclesub-teams
Start small with strategy andexecutionPick likely-to-win projectsCelebrate wins publiclyEarn resources to growSplit into lifecycle sub-teams

Early teams must earn trust and resources, so choosing high-probability projects and celebrating wins publicly builds buy-in. Later, sub-teams map to the user lifecycle and some take bigger bets.

How to run it

  1. Pick high-impact, likely-to-succeed first projects
  2. Cover both strategy and execution skills
  3. Celebrate wins regularly and publicly
  4. Scale to sub-teams along the user lifecycle
  5. Invest in analytics and experiment infrastructure

Ways to run it

Design options to test, not promised results.

  1. Option ASingle growth lead

    One person who can both plan and build takes the first projects end to end.

  2. Option BSmall cross-skill team

    A handful of people covering analysis, engineering and design, focused on one lifecycle stage.

  3. Option CLifecycle sub-teams

    Once results justify it, split into teams for acquisition, activation, retention and monetisation.

Timeline

  1. 12017 first documented: Brian Balfour
  2. 22026-11 status checked: Working

Dated examples

No dated example yet. Treat this tactic as a hypothesis.

Does it still work?

Workingas of 2026-11

Essay is from 2017; the ratios and sizes are the author's guidance, not a measured benchmark. source

Risks

  • Guidance from one practitioner
  • Sizing varies by company

Sources

  1. brianbalfour.com · Brian Balfour · Brian Balfour · 2017-05-24
    “Early growth teams need to prove themselves, so think hard about project impact and likelihood of success.”
    ✓ quote checked word-for-word on the page
  2. brianbalfour.com · Brian Balfour · Brian Balfour · 2017-05-24
    “Early teams need to regularly and publicly celebrate victories to increase buy-in and continue to get resources to expand”
    ✓ quote checked word-for-word on the page

Change log

  • 2026-11-20 — harvest v0.1 (ops-ai)