Writing/Article
·21 min read·growth

The First 90 Days as Head of Growth at a Startup (and How Founders Should Judge You)

A practical 30/60/90 playbook for startup growth hires. What to audit, where to find quick wins, and how to build credibility without becoming the "hacky growth person".

TL;DR

18 min read
  • Days 0-30: Understand how the startup actually grows. Don't ship anything yet.
  • Days 30-60: Fix measurement. You can't optimize what you can't see.
  • Days 60-90: Ship 2-3 real experiments with documented learnings.
  • The first 90 days determine whether the next 900 will matter.

I've walked into four different startups as the "growth person" over the past decade. Each time, the same pattern plays out: there's a flurry of introductions, a firehose of context dumps, vague expectations about "unlocking growth," and an unspoken clock ticking in the background. Everyone is watching to see if you're the real deal or another marketing hire who'll spend six months optimising Facebook ads, produce some dashboards nobody looks at, and quietly leave when things don't "scale."

The first 90 days determine whether the next 900 will matter.

The uncomfortable truth that most growth hires don't want to hear - and that most founders don't explicitly say - is that those first 90 days reveal whether you understand how to build compounding systems or whether you're just a bag of tactics looking for a place to land.

I've been on both sides of this. I've been the growth hire who got it right - who spent the first month doing things that looked slow but paid dividends for years. And I've been the growth hire who sprinted into campaigns too early, got some quick wins that didn't compound, and found myself six months later still unable to explain what was actually driving the business. The difference wasn't intelligence or work ethic. It was approach.

This piece is the playbook I wish I'd had for my first growth role. It's built for three audiences:

1

Newly-hired Heads of Growth

Trying to figure out what to actually do in your first 90 days

2

Founders evaluating growth hires

Use the 'For Founders' sections as an evaluation rubric

3

Growth leads at earlier stages

Wondering how to scope and structure your work

Let's get into it.


01

What a Head of Growth Really Owns

And why the title is maddeningly vague

Before we dive into the 90-day playbook, we need to address the elephant in the room: nobody actually agrees on what "Head of Growth" means.

I've seen the title applied to someone who runs paid acquisition and reports to a CMO. I've seen it applied to someone who owns the entire customer journey from first touch to expansion revenue and reports directly to the CEO. I've seen it mean "the marketing person at a company that doesn't want to say marketing" and I've seen it mean "a product-minded operator who happens to care about distribution."

My Definition

A Head of Growth owns the strategy and execution for how the company acquires, activates, and retains customers in a scalable, measurable way.

That's a mouthful, but each word matters:

  • "Strategy and execution" means you're not just coming up with ideas - you're accountable for making them real
  • "Acquires, activates, and retains" means you care about the full customer journey, not just top of funnel
  • "Scalable" means you're building systems that compound, not just running one-off campaigns
  • "Measurable" means you can actually prove what's working

This is distinct from adjacent roles in important ways. A VP or Head of Marketing is often more brand and awareness-focused, particularly at larger companies - they might not own activation or retention at all. A CMO is typically a broader executive role that encompasses brand, communications, PR, and marketing operations, often with less hands-on experimentation. A Product Manager owns the product experience but usually not distribution or acquisition channels. The Head of Growth sits at the intersection of all of these, which is why the role is so hard to hire for and so easy to misdefine.

At an early-stage startup - Seed through Series B - the Head of Growth typically needs to be a generalist with an unusual combination of skills:

1

Understand the product deeply

Identify activation bottlenecks and talk credibly with engineers

2

Build or oversee acquisition channels

Paid media, organic content, partnerships, or product-led growth mechanics

3

Work with product and engineering

Write clear specs, respect bandwidth, know when to push and when to back off

4

Create measurement infrastructure

Get your hands dirty with analytics tools to know what's actually working

5

Communicate a coherent growth narrative

Translate complex data into stories that drive alignment


02

The Core Framework

Model, Measurement, Motion

I've tried various frameworks for structuring the first 90 days, and the one that's consistently worked best is what I call Model → Measurement → Motion.

The 90-Day Growth Framework

Model

Days 0-30

Measurement

Days 30-60

Motion

Days 60-90

Model (Days 0-30) is about understanding how the startup actually grows - not how the pitch deck says it grows, not how the founder hopes it grows, but the real mechanics of how customers discover the product, why they sign up, what makes them stick around, and what makes them leave. The deliverable is a clear, simple growth model document and a baseline understanding of your funnel metrics.

Measurement (Days 30-60) is about making growth legible to the entire company. Most startups I walk into have a measurement problem masquerading as a growth problem - they're flying blind, making decisions based on gut feel, last-touch attribution, or whatever metric the CEO happened to glance at in a board presentation. The deliverable is a single source of truth dashboard that people actually look at and a growth review ritual.

Motion (Days 60-90) is about converting understanding and visibility into action that compounds. You've earned the right to ship because you understand the model and can measure results. The deliverable is a prioritised experiment roadmap, concrete shipped work, and at least one measurable improvement you can point to.


03

Days 0-30: Understanding How This Startup Really Grows

Learning faster than anyone expects you to

The first 30 days are about one thing: learning faster than anyone expects you to.

You're not here to "make quick wins" yet - that comes later. You're not here to launch campaigns or redesign landing pages or spin up new channels. You're here to understand the growth model better than anyone else at the company. This understanding is the foundation that makes everything else possible. Skip it, and you'll spend the next year building on sand.

The reason this phase matters so much is that every startup grows differently, and the generic playbooks that work at one company will fail spectacularly at another.

The Week-One Growth Audit

The first two weeks should be an intensive discovery sprint. Here's my structured process:

The Discovery Sprint

1

Understand founders and narrative

Why does this company exist? Who is the 'hero' customer? What outcome defines success? Where does the CEO believe growth should come from?

The CEO's mental model of growth matters enormously, even if it turns out to be wrong. You need to understand it before you can evolve it.
2

Map users and segments

Who are the active customers? Break down by industry, company size, use case, acquisition source, signup date.

Talk to at least 5 churned customers and 5 NPS 9-10 customers. People who left will tell you things current customers won't.
3

Audit product and activation flow

Sign up fresh. Go through onboarding, hit empty states, interact with paywalls. Watch for friction AND moments of delight.

If 60% of users who sign up never complete onboarding, that's probably your biggest growth problem - not something you can solve with more acquisition spend.
4

Assess data and tracking

What events are tracked? Is there a standardised schema? Does anyone trust the data? Do definitions match across tools?

Most startups' data is worse than anyone admits. Numbers don't match between tools, definitions are fuzzy, attribution is broken.
5

Catalogue channels and campaigns

Where do customers come from? Traffic sources, CAC by channel, conversion rates through the funnel, previous experiments.

Dig into the archives of previous experiments. Usually a graveyard of random tests that didn't compound into learning.
6

Examine pricing and packaging

Current model, discount usage, upgrade paths, where revenue actually comes from.

Pricing is a growth lever. Often the pricing structure is actively hindering growth.
7

Understand team and operating rhythm

Who owns what? How do decisions get made? What rituals exist? How does work get prioritised and shipped?

A growth strategy requiring heavy engineering support won't work if eng bandwidth is locked for 6 months.

Synthesising Into a Growth Model

All of this discovery should synthesise into a simple document - one or two pages - that captures how the company grows. Aim to have this done by Day 30.

What Your Growth Model Should Include

  • How the company grows today - the actual mechanics, stripped of aspiration
  • Key customer segments - and how they differ in acquisition, activation, retention, LTV
  • The core loop - what's the repeatable motion that acquires and retains customers?
  • The primary bottleneck - where's the biggest constraint right now?
  • Top hypotheses - your early bets on what would move the needle

The Day 7 CEO Memo

The founder will either validate your hypotheses or push back on them. Both outcomes are valuable. If they validate, you've confirmed you're on the right track. If they push back, you learn something important about how they see the business.


04

Days 30-60: Making Growth Legible

Experiments without measurement aren't experiments - they're guesses

The second phase is about measurement, and it's where many growth hires get impatient and make mistakes. You've done your discovery. You understand the business. Now you want to do things.

Here's why you resist that pressure:

Experiments without measurement aren't experiments, they're guesses. You can launch ten campaigns in the next 30 days, and if your tracking is broken, you'll learn nothing.

I've lived this. Early in my career, I joined a startup and immediately started running paid acquisition experiments. The campaigns looked like they were working - cost per signup looked great, we were acquiring users. Six months later, we discovered our attribution was completely broken. Most signups we'd attributed to paid were actually coming from organic. We'd wasted significant budget scaling a channel that wasn't actually performing.

The State of Data at Most Startups

Let me paint an honest picture of what you'll typically find:

3+

Different names for the same event across tools

0

Documentation on what metrics mean

Last-touch

Attribution model (massively flawed)

Rare

Cohort analysis capabilities

Event tracking is inconsistent. Attribution is either missing or dangerously oversimplified. Cohort analysis is rare. Data freshness varies wildly. And definitions are fuzzy - ask three people what an "active user" is and you'll get three different answers.

Your job in Days 30-60 is to fix enough of this to make growth legible. Not all of it - but the critical gaps.

What to Fix First

1

Conversion funnel tracking

Visit → signup → activation → paid → retention. Everything else depends on this.

2

Cohort retention

Retention curves by week of signup. This tells you if users are sticking or if you're filling a leaky bucket.

3

Channel attribution

Some way to understand where customers come from and which channels drive valuable conversions.

4

Segment breakdowns

Slice data by plan type, company size, use case, acquisition source.

The Growth Dashboard

By Day 60, you should have a single dashboard that shows the health of the growth engine at a glance. One source of truth, not five different dashboards showing five different versions of reality.

The dashboard should be scannable in under a minute. Include:

  • Acquisition: Volume of visitors, signups, leads by source. Week-over-week trends.
  • Activation: Conversion rate from signup to activated. Time to activation. Drop-off points.
  • Retention: Cohort retention curves at week 1, 4, 8. Month-over-month trends.
  • Revenue: MRR/ARR, new vs expansion vs churn. CAC and LTV if calculable.

Establishing the Growth Review

A dashboard nobody looks at is just decoration. Establish a weekly growth review, typically 30 minutes:

Weekly Growth Review Agenda

  • Walk through the dashboard (what moved, what didn't)
  • Review active experiments (what did we learn this week)
  • Align on priorities for the coming week

05

Days 60-90: Standing Up a Repeatable Growth Machine

You've earned the right to ship

You've earned the right to ship. You understand how the business grows, you can measure results reliably, and you've built credibility with the team. Days 60-90 are about converting all that preparation into motion that compounds.

Designing an Experiment Backlog

I use a simple ICE framework for prioritisation:

Impact

How much could this move the needle?

Confidence

How sure are we this will work?

Effort

How hard is it to build and ship?

Score each dimension 1-10 and multiply. It's not scientific, but it forces explicit trade-offs.

For the initial backlog, focus on three categories:

1

High-impact, high-confidence bets

Fixing obvious friction. You've identified a step where 60% of users drop off - that's a high-confidence opportunity.

2

Learning experiments

Validate or invalidate key hypotheses. Might not produce immediate improvements but builds understanding.

3

Incremental improvements

Smaller wins that build momentum and demonstrate execution capability.

Shipping Your First Experiments

Aim to ship 2-3 meaningful experiments in Days 60-90. "Meaningful" means connected to your growth model, properly instrumented, and documented.

Good First Experiments

  • Onboarding optimisation - simplify confusing steps, reduce form fields
  • Messaging tests - A/B test value propositions based on customer interviews
  • Conversion funnel fixes - address specific drop-off points you've identified

Bad First Experiments

  • Launching a TikTok channel because it's trending
  • Redesigning the entire website at once
  • Running 15 unfocused tests simultaneously

Documenting and Communicating Results

Every experiment needs written documentation: hypothesis, design, results, learnings. This creates institutional memory and holds you accountable.

We tested whether adding social proof to the pricing page would increase plan selection rates. It didn't - the variant performed 5% worse. Our hypothesis was that social proof would increase trust, but users at this funnel stage already have trust. We're pivoting to simplify plan comparison instead.
E

Example of a failed experiment

That produced valuable learning


06

Quick Wins That Don't Sabotage Long-Term Growth

Not all wins are created equal

I want to address quick wins directly because I know the pressure is real. You want to prove you were a good hire. The CEO wants movement. But chasing the wrong wins creates long-term problems.

Good Quick Wins

  • Clarify the core metric - propose 1-3 primary metrics with rigorous definitions
  • Fix obvious UX friction - remove unnecessary form fields, clarify confusing copy
  • Improve an existing channel - rewrite emails, optimise landing pages
  • Create a monthly growth memo - builds credibility before you have results

Quick Wins That Backfire

  • Buy low-quality traffic to inflate signup numbers
  • Heavy discounting to hit a revenue target
  • Launch new channels before the core funnel is measured
  • Aggressive popups and dark patterns that erode trust

A good quick win strengthens the system. A bad quick win bypasses it.

The litmus test: "Will this quick win help us learn something that compounds, or is it just a number we can point to?"


07

Building Credibility Across the Organisation

Trust is earned systematically

The first 90 days are as much about building trust as driving results. You need to build credibility with different stakeholders who care about different things.

Credibility with Founders/CEO

1

Day 7 memo

Share initial hypotheses proactively. Shows you're synthesising, not just absorbing.

2

Day 30 growth model

Articulate how the business actually grows. Founder should think 'this person gets it.'

3

Day 60 dashboard

Make things tangible. Discovery needs to produce artifacts that change how the company operates.

4

Day 90 growth thesis

Strategic point of view on where growth will come from over the next year.

Credibility with Product and Engineering

Instead, lead with user insight: "I talked to 20 churned customers and found the most common friction point is the project setup flow. Here's the data showing where drop-offs happen. Can we talk through solutions together?"

When you do make requests, make them well. Write clear experiment specs with hypotheses, success metrics, and implementation considerations. And deliver on your promises - if an experiment doesn't work, be honest about it.

Credibility with Sales and Customer Success

In the first 30 days, listen to at least 10 sales calls. Take notes on what prospects ask, what confuses them, what objections come up. Create a simple document summarising what you've heard and share it with the team.


08

Special Cases

Adjustments for different contexts

Fractional and Part-Time Growth Leads

Adjustments for 10-20 hours/week

  • Compress discovery - focus on 2-3 key questions, not comprehensive audit
  • Identify the 3-5 metrics that matter most and ensure those are trustworthy
  • Lean heavily on async communication and documentation
  • Be explicit about the 2-3 highest-leverage areas you're focusing on

Interim Growth Leaders

Priorities when filling a gap

  • Documentation is paramount - create clarity for whoever comes next
  • Avoid major strategic pivots unless something is actively on fire
  • Measurement infrastructure is the biggest gift you can give your successor

First-Time Growth Leaders

Advice for your first growth role

  • Over-invest in the Model phase - your inexperience means you have less pattern recognition
  • Find a mentor or advisor who's done the role before
  • Be transparent about what you don't know - it builds more trust than faking expertise

09

Before You Accept the Role

Non-negotiables for alignment

For growth candidates evaluating an offer, align on these points before you start. Misalignment here is the most common reason growth hires fail.

Questions to Answer Before Starting

  • Explicit success criteria for 90 days - what does the CEO expect by Day 30, 60, 90?
  • Data visibility - is there basic tracking, or will you build from zero?
  • Scope clarity - marketing only? Product growth? Pricing? Sales enablement?
  • Resource reality - what team, budget, engineering bandwidth, tools?
  • PMF status - are you scaling something that works, or still searching?

10

The 90-Day Contract

What founders and growth leaders owe each other

Let me close with something rarely made explicit: the first 90 days are a mutual evaluation.

What Founders Owe Growth Hires

Create the conditions for success

  • Access to customers, data, and key stakeholders
  • Clear feedback on whether expectations are being met
  • Patience for the Model and Measurement phases
  • Resources to actually run experiments

What Growth Hires Owe Founders

Demonstrate structured progress

  • Structured discovery and clear artifacts by Day 30
  • Measurable infrastructure by Day 60
  • Real motion and early results by Day 90
  • Honest communication about what's working and what isn't

If both sides hold up their end, you get a partnership that can actually drive growth. If either side falls short, you get the all-too-common pattern: a growth hire who's gone in 12 months, a founder who's convinced "growth people don't work here," and a company no closer to solving its acquisition problems.

The Bottom Line

The first 90 days set the trajectory. Get them right.

growth