Biology of Business

↗ Door 1: GROW 1.4

Growth Execution Playbook

"I need to actually execute growth"

What you'll get

A phased execution timeline with specific milestones, resource commitments, sequencing decisions, and pivot criteria at each stage — from initial commitment through scaled growth.

When to use this

When you have decided where to grow (use Growth Opportunity Radar first) and whether to expand (use Expansion Decision Framework first) and now need a concrete execution plan. When the strategy is set but the question is 'how do we actually do this?' When transitioning from founder-led sales to scalable growth. When launching into new markets and needing to sequence the rollout.

The process

1

Commitment and Scarification

Weeks 1-2

Questions to answer

How to do this
Seeds require scarification — the breaking of the seed coat — before germination can begin. The business equivalent is crossing the point of no return. Half-committed growth initiatives consume resources without achieving escape velocity. Commit reserves: allocate specific budget and headcount to this growth initiative with an explicit ceiling. Announce publicly: tell the organization, the board, and key stakeholders. This creates accountability and prevents the quiet retreat that kills most initiatives. Burn the ships: make dormancy impossible by creating commitments that cannot be easily reversed (hiring a growth leader, signing contracts, announcing to customers). Define the kill criteria simultaneously: at what point do you prune? What specific metrics, at what thresholds, over what timeframe? Writing pruning triggers before emotional attachment develops is the single most important discipline in growth execution.
What you'll need
  • Approved growth strategy and target opportunity
  • Available resources (budget, headcount, leadership bandwidth)
  • Risk tolerance and maximum investment ceiling

What you'll have when done

  • Irrevocable commitment: resources allocated, team assigned, public announcement made
  • Kill criteria: specific metrics, thresholds, and timeframes for pruning
  • Maximum investment ceiling before mandatory review
  • Growth leader hired or assigned
2

Germination — Root Before Shoot

Months 1-6

Questions to answer

How to do this
Seeds push the radicle (root) downward before the shoot upward. The invisible infrastructure comes first. Month 1-3: Radicle emergence. Build the absolute minimum viable product for validation, not scale. Target 10 customers who love it over 1,000 who are lukewarm. Validate that people will use what you build. Month 3-6: Cotyledon deployment. First revenue, first pilots, first payment validation. These are temporary energy sources — like cotyledons (seed leaves) that sustain the seedling until true leaves develop. The goal is not profitability but proof that the organism can extract energy from the environment. Month 6-12: True leaf development. The seedling produces more energy than it consumes. Product-market fit. Repeatable customer acquisition. Sustainable unit economics emerging. If true leaves have not emerged by month 12, revisit kill criteria from Step 1.
What you'll need
  • Committed resources from Step 1
  • Target customer profile and initial pipeline
  • MVP definition and build plan

What you'll have when done

  • MVP validated with 10+ passionate users (Month 3)
  • First revenue and payment validation (Month 6)
  • Product-market fit signals: retention above 70%, NRR above 100% (Month 12)
  • Unit economics trajectory: path to sustainable acquisition visible
3

Pioneer-to-Scale Codification

90 days (Months 12-15)

Questions to answer

How to do this
Forest succession follows a predictable sequence: pioneer species colonize disturbed ground, then modify the environment for successors. Slack grew from zero to $1 billion valuation in 8 months with founder Stewart Butterfield personally handling customer feedback. Marc Benioff built Salesforce on his Oracle sales playbook. Both understood: you codify what works before trying to scale it. Month 1 (Foundation): Document what is actually working. Record customer conversations. Map the buyer journey. Identify best-converting segments. Write the sales playbook v1 (10-15 pages). Hire VP Sales. Do not hire sales reps before the system exists. Month 2 (Infrastructure): CRM operational with pipeline loaded. Lead routing established. Complete enablement package: pitch deck, demo flow, ROI calculator, case studies, competitive battlecards. Month 3 (First Hires): Two SDRs and one AE. Shadow selling, role reversal, begin outbound. The first SDR-sourced meeting confirms the system works. Entry criteria are strict: over $10M ARR growing over 100% per year, over 70% retention, NRR over 100%, CAC payback under 18 months. Miss any threshold and this transition fails — you are forcing succession before the ecosystem is ready.
What you'll need
  • Product-market fit evidence from Step 2
  • Customer conversation logs and buyer journey data
  • Current sales process (likely informal, founder-led)
  • Metrics: ARR, growth rate, retention, NRR, CAC payback

What you'll have when done

  • Sales playbook v1: documented process that someone other than the founder can execute
  • VP Sales hired and operational
  • CRM operational with full enablement materials
  • First non-founder sales team (2 SDRs + 1 AE) producing results
  • System validation: SDR-sourced deals closing at acceptable rate
4

Phototropic Reallocation

8 weeks (can run in parallel with Step 3)

Questions to answer

How to do this
As growth signals validate, redirect resources toward the strongest gradient in staged increments — like a plant bending toward light. Week 1-2: Run gradient audit. Rank opportunities by signal strength. Identify top 3 highest-gradient directions. Calculate current allocation across opportunities and identify misalignment with gradient strength. Week 3-4: Draft reallocation plan. Determine target allocation using the principle that resources should flow proportionally to gradient strength, not proportionally to historical allocation. Map the transition path. Week 5-8: Stage the reallocation in 25% increments. Shift 25% of the target reallocation immediately. Measure impact over 2 weeks. If positive, shift another 25%. If negative, reassess whether the gradient signal was wrong or the execution was flawed. Repeat until fully reallocated or signal invalidated. Then sustain: re-run the gradient audit every 90 days. Accelerate if the gradient is strengthening, maintain if stable, begin pivoting if weakening.
What you'll need
  • Current resource allocation by initiative
  • Gradient strength data from Growth Opportunity Radar
  • Validated growth signal from Steps 2-3

What you'll have when done

  • Resource reallocation plan with staged 25% increments
  • Gap analysis: current allocation vs gradient-optimal allocation
  • 90-day gradient monitoring cadence established
  • Pivot criteria: what gradient weakening triggers reallocation review?
5

Branching Execution

Months 6-36 (overlaps with earlier steps for established businesses)

Questions to answer

How to do this
For growth that involves creating a new business branch (not just scaling existing product), execute the full 36-month branching timeline. Month 1-3: Validate trunk strength. Confirm the core business can support the metabolic load of a new branch. If trunk metrics are weak, stop and fix the trunk. Month 3-6: Define branch business case. Market analysis, financial projections (base, bull, bear scenarios), IRR calculation, payback period, opportunity cost analysis. Month 6-9: Allocate resources and install leadership. Assign specific capital percentage, hire or assign branch leader, define decision authority matrix (what can the branch decide independently?). Month 9-21: First-year execution. Build infrastructure, launch MVP, acquire customers, validate product-market fit within the branch context. Month 21-30: Monitor and optimize. Run branch independence tests quarterly. Measure against kill criteria. Month 30-36: Scale or prune decision. This is not optional — every branch gets a formal scale-or-prune review at 36 months. The decision uses the independence test from the Expansion Decision Framework (1.2): pass all four dimensions (P&L, customer, decision, economic independence) and scale; fail any and either restructure or prune.
What you'll need
  • Trunk strength score from Expansion Decision Framework
  • Branch business case with financial projections
  • Leadership capacity assessment

What you'll have when done

  • 36-month branching timeline with specific milestones
  • Branch leader hired with clear decision authority
  • Quarterly independence test schedule
  • 36-month scale-or-prune decision point with pre-defined criteria
6

Expansion Sequencing

Ongoing — applies to multi-market or multi-product expansion

Questions to answer

How to do this
Choose between all-at-once expansion (Airbnb model: 50+ countries in 2-3 years) and stepwise expansion (Spotify model: one market at a time, prove then expand). Assess four factors. Network effects structure: if winner-take-all dynamics exist and first-to-global-scale wins, favor all-at-once. Capital availability: all-at-once requires $500M+, stepwise works with under $100M. Product-market-fit certainty: if PMF is proven and the model copies globally without adaptation, favor all-at-once; if adaptation is required per market, favor stepwise. Competitive velocity: if competitors are moving fast, match their speed; if competitors are slow, take time to learn. Default to stepwise — it is lower risk and allows learning. Only choose all-at-once when you have proven PMF, winner-take-all dynamics, massive capital, and fast competitors simultaneously. Within stepwise expansion, sequence by: adjacent markets first (culturally and geographically close), then prove the model works, then expand to next tier. Each market must reach defined milestones before resources shift to the next.
What you'll need
  • Validated growth model from Steps 2-5
  • Market priority list from Growth Opportunity Radar
  • Capital availability and fundraising capacity
  • Competitive landscape and velocity analysis

What you'll have when done

  • Sequencing decision: all-at-once or stepwise
  • If stepwise: ordered market entry list with milestone gates between entries
  • If all-at-once: parallel execution plan with centralized coordination
  • Resource allocation plan per market with defined success criteria
  • Sequencing review cadence: when to reassess the order
✓ Framework complete

Why this works — the biology

Sunflowers demonstrate the execution sequence this framework encodes. Young sunflower stems track the sun through differential growth: cells on the shaded side elongate faster than cells on the illuminated side, causing the stem to bend toward light. This is not a passive response but an active growth program — the plant commits cellular resources in a specific direction based on environmental signals. During the day, the stem bends east to west following the sun. At night, the east side grows faster, resetting the stem to face east for dawn. As the plant matures and the stem stiffens, this tracking stops and the flower faces permanently east — the plant has committed to a direction and built structural support for it. The business parallel is precise: early-stage growth should be flexible and responsive to signals (phototropic tracking), but as the organization matures and the growth direction validates, resources should lock in and build permanent infrastructure (stem stiffening). The pioneer-to-scale transition draws from ecological succession: pioneer species like fireweed and alder colonize disturbed ground, then literally modify the environment for successors. Alder fixes nitrogen in the soil, creating conditions for larger trees. The founder who personally handles every customer conversation is the pioneer species — modifying the environment (building relationships, learning the buyer journey, fixing the product) so that successor species (hired salespeople, scalable systems) can thrive.

See it in action: salesforce

Salesforce's growth execution from 1999 to 2005 maps precisely to this playbook. Commitment and scarification: Marc Benioff quit Oracle and committed publicly to 'the end of software' — a scarification so dramatic it defined the company's identity and made retreat impossible. Germination: the first year focused on a deliberately simple CRM product (radicle), targeting small businesses that enterprise vendors ignored (10 customers who loved it). By year two, early adopters were paying (cotyledon deployment), validating that businesses would trust a web application with their customer data — which in 2000 was not obvious. Pioneer-to-scale codification: Benioff personally developed the sales playbook from his Oracle experience, documenting objection handling, demo flows, and closing techniques before hiring a sales team. The V2MOM framework (Vision, Values, Methods, Obstacles, Measures) codified the execution system that every new hire could follow. Infrastructure was built before replication: Salesforce invested heavily in the AppExchange platform and developer tools — root investment that would sustain decades of shoot growth. Phototropic reallocation: Salesforce systematically tracked which customer segments showed the strongest retention and expansion signals, then reallocated resources accordingly — the shift from small business to mid-market to enterprise was a series of phototropic pivots following the strongest gradient. Expansion sequencing: Salesforce chose stepwise over all-at-once for both product and geographic expansion, proving each product (Sales Cloud, then Service Cloud, then Marketing Cloud) and each market (US first, then Europe, then Asia) before committing to the next.

Adapt to your context

first startup

Steps 1-2 (commitment and germination) are your entire focus. Do not think about branching or sequencing until you have product-market fit. The pioneer-to-scale codification becomes critical at $10M ARR. Everything before that is germination.

scaling saas

Step 3 (pioneer-to-scale codification) is your critical moment. Most SaaS companies fail the founder-to-VP-Sales transition. Codify ruthlessly before hiring. The 90-day sprint structure prevents the common mistake of hiring 10 reps with no playbook.

geographic expansion

Steps 5-6 (branching + sequencing) are primary. The sequencing decision between all-at-once and stepwise is the highest-leverage choice. Default to stepwise unless you have compelling evidence for all four all-at-once criteria.

product line expansion

Steps 1 and 5 (commitment + branching) are primary. Each new product line is a branch that must pass the independence test. The 36-month timeline with mandatory scale-or-prune review prevents zombie product lines.

turnaround growth

Start with Step 4 (phototropic reallocation) — you are not building from zero but redirecting existing resources toward the strongest signal. The staged 25% reallocation prevents the shock of overnight restructuring while still producing measurable change.

Related

Mechanisms

Phototropism

Companies

SalesforceSlackAirbnbSpotify