Growth Marketing skill 01 of 13

Growth Audit SKILL.md

The Growth Audit skill makes Claude, Codex or another AI agent review a company’s growth system end to end and name the single biggest constraint. It checks the north star, growth model, acquisition, activation, retention, monetisation, referral and loops, data and tracking, experimentation practice and reporting, labels every finding by evidence type and returns a ranked 90-day plan.

growth-audit/SKILL.md, version 1.0.0, 1,513 words.

Growth teams often start with tactics: a referral programme because a competitor has one, a new channel because someone read about it, an experiment because it was easy to ship. Without a clear picture of where growth comes from and where it leaks, those tactics are guesses. A growth audit builds that picture first: the metric that matters, the model that drives it, the biggest constraint, and the evidence the team has (or lacks) to act on.

This skill audits a company's growth system end to end: goals and metrics, the growth model, acquisition, activation, retention, monetisation and referral, data and tracking, experimentation practice and reporting. It returns the single biggest constraint and a ranked plan, and hands each finding to a specialist skill.

Operating principles

  1. Find the constraint. Growth is limited by one step at a time; improving anything else has little effect.
  2. Retention first. Acquiring users who leave quickly is the most expensive form of growth.
  3. Models over tactics. Understand how inputs (traffic, conversion, retention, referral) combine into outcomes before choosing work.
  4. Evidence labels. Separate what data shows, what tests proved and what the team believes.
  5. Speed of learning matters. A team that runs good experiments weekly outgrows one that ships big bets quarterly.

The audit areas

AreaKey questionsTypical finding
Goals and north starIs there one metric that reflects customer value and predicts revenue?Team chases sign-ups while revenue depends on weekly active teams
Growth modelDo we know how inputs produce the outcome, with numbers?No model; targets set top-down
AcquisitionWhich channels bring retained users, at what cost and scale?One channel provides most growth and is saturating
ActivationWhat share reach first value, and how fast?Most sign-ups never reach the value moment
RetentionDo cohort curves flatten, and at what level?Curves never flatten for some segments
MonetisationPricing, conversion to paid, expansionFew users hit the limits that trigger upgrades
Referral and loopsDo users bring other users?No loop; growth is linear with spend
Data and trackingAre key events reliable and defined?Activation event fires inconsistently
ExperimentationHow many tests, how rigorous, how quickly?Few tests, mostly underpowered
ReportingDoes the team review the right metrics weekly?Dashboards of vanity metrics

When to use, and when not to

Use it when growth stalls, when a new growth lead joins, before planning a quarter, after product-market fit when scaling begins, and when leadership asks where to invest.

Don't use it to fix one funnel step in depth (use funnel-analysis), to run a single experiment (experiment-design) or for paid media accounts (the Performance Marketing skills).

Inputs to ask for, in one message

  1. Business model, customer types, pricing and revenue for 12 to 24 months.
  2. Current goals and the metrics the team reviews.
  3. Acquisition data by channel: volume, cost and downstream retention.
  4. Funnel data from visit or sign-up to activation, paid and retained.
  5. Cohort retention curves by sign-up month and segment.
  6. Tracking plan or event list, and the analytics tools in use.
  7. Experiment history: what was tested, results and decisions.

Raw SKILL.md file

.md

This is the exact file agents read, including the credit header and licence notice. Save it as growth-audit/SKILL.md.

---
name: growth-audit
description: "Audit a company's growth system end to end: north star and goals, growth model, acquisition, activation, retention, monetisation, referral and loops, data and tracking, experimentation practice and reporting, find the single biggest constraint with evidence, check retention before acquisition and produce a scored, ranked 90-day plan. Use whenever someone asks for a growth audit, why growth stalled, where to focus growth efforts, how to plan a growth quarter, what the biggest growth lever is, or for a review of a growth team's work."
license: CC-BY-4.0
metadata:
  author: Afeez Adebayo
  author_url: https://afeezadebayo.com
  author_linkedin: https://www.linkedin.com/in/afeez-adebayo/
  author_x: https://x.com/za_icon
  source: https://afeezadebayo.com/skills-md/marketing/growth-marketing/growth-audit/
  category: marketing
  subcategory: growth-marketing
  version: "1.0.0"
  created: "2026-10-10"
  updated: "2026-10-10"
---

# Growth Audit

Growth teams often start with tactics: a referral programme because a competitor has one, a new channel because someone read about it, an experiment because it was easy to ship. Without a clear picture of where growth comes from and where it leaks, those tactics are guesses. A growth audit builds that picture first: the metric that matters, the model that drives it, the biggest constraint, and the evidence the team has (or lacks) to act on.

This skill audits a company's growth system end to end: goals and metrics, the growth model, acquisition, activation, retention, monetisation and referral, data and tracking, experimentation practice and reporting. It returns the single biggest constraint and a ranked plan, and hands each finding to a specialist skill.

## Operating principles
1. **Find the constraint.** Growth is limited by one step at a time; improving anything else has little effect.
2. **Retention first.** Acquiring users who leave quickly is the most expensive form of growth.
3. **Models over tactics.** Understand how inputs (traffic, conversion, retention, referral) combine into outcomes before choosing work.
4. **Evidence labels.** Separate what data shows, what tests proved and what the team believes.
5. **Speed of learning matters.** A team that runs good experiments weekly outgrows one that ships big bets quarterly.

## The audit areas
| Area | Key questions | Typical finding |
|---|---|---|
| Goals and north star | Is there one metric that reflects customer value and predicts revenue? | Team chases sign-ups while revenue depends on weekly active teams |
| Growth model | Do we know how inputs produce the outcome, with numbers? | No model; targets set top-down |
| Acquisition | Which channels bring retained users, at what cost and scale? | One channel provides most growth and is saturating |
| Activation | What share reach first value, and how fast? | Most sign-ups never reach the value moment |
| Retention | Do cohort curves flatten, and at what level? | Curves never flatten for some segments |
| Monetisation | Pricing, conversion to paid, expansion | Few users hit the limits that trigger upgrades |
| Referral and loops | Do users bring other users? | No loop; growth is linear with spend |
| Data and tracking | Are key events reliable and defined? | Activation event fires inconsistently |
| Experimentation | How many tests, how rigorous, how quickly? | Few tests, mostly underpowered |
| Reporting | Does the team review the right metrics weekly? | Dashboards of vanity metrics |

## When to use, and when not to
Use it when growth stalls, when a new growth lead joins, before planning a quarter, after product-market fit when scaling begins, and when leadership asks where to invest.

Don't use it to fix one funnel step in depth (use `funnel-analysis`), to run a single experiment (`experiment-design`) or for paid media accounts (the Performance Marketing skills).

## Inputs to ask for, in one message
1. Business model, customer types, pricing and revenue for 12 to 24 months.
2. Current goals and the metrics the team reviews.
3. Acquisition data by channel: volume, cost and downstream retention.
4. Funnel data from visit or sign-up to activation, paid and retained.
5. Cohort retention curves by sign-up month and segment.
6. Tracking plan or event list, and the analytics tools in use.
7. Experiment history: what was tested, results and decisions.

## Workflow

### Step 1. Agree the goal and north star
Check whether the current north star reflects delivered customer value and predicts revenue. If not, propose one (`north-star-metric-tree`).

### Step 2. Build a quick growth model
Map inputs to outcome with current numbers: new users by channel × activation rate × retention × monetisation, plus referral or loop contributions (`growth-model`).

### Step 3. Read retention first
If cohort curves don't flatten, fix retention before scaling acquisition (`cohort-retention-analysis`).

### Step 4. Find the biggest leak
Compare each step's conversion and volume with benchmarks from your own history and segments; find where the most value is lost (`funnel-analysis`).

### Step 5. Review acquisition
Which channels bring users who retain? Where is the next scalable channel? (`acquisition-channel-testing`).

### Step 6. Check loops and referral
Do users invite, share or create content that brings others? (`growth-loops`, `referral-programmes`).

### Step 7. Check data and experimentation
Are events reliable (`tracking-plan`)? Are experiments well designed, powered and read correctly (`experiment-design`, `experiment-readout`)? Is there a steady experiment cadence (`growth-experiment-backlog`)?

### Step 8. Name the constraint and plan
One sentence: "Growth is constrained by X because Y." Then a 90-day plan focused on it.

## Scoring rubric
| Score | Meaning |
|---|---|
| 0 | Missing or unknown |
| 1 | Present but unreliable or unused |
| 2 | Solid and used in decisions |
| 3 | Strong, measured, improving through experiments |

## Common constraints and first moves
| Constraint | Sign | First move |
|---|---|---|
| Retention | Curves keep falling | Find the value moment; improve onboarding and core experience |
| Activation | Many sign-ups, few reach value | Remove friction to first value |
| Acquisition scale | Good retention, slow volume | Test new channels; build loops |
| Monetisation | Engaged users don't pay | Packaging, limits and upgrade prompts |
| Learning speed | Few, slow experiments | Backlog, cadence and sizing discipline |
| Data | Numbers disagree | Fix the tracking plan before anything else |

## Edge cases and judgement calls
| Situation | What to do |
|---|---|
| Pre product-market fit | Focus on retention of a narrow segment, not scale |
| B2B with few large customers | Use account-level metrics; fewer, deeper experiments |
| Marketplace | Audit both sides and the liquidity between them |
| Very low traffic | Prefer qualitative research and big changes over A/B tests |
| Seasonal business | Compare like periods; model seasonality explicitly |

## Handoffs to specialist skills
- North star and metric tree: `north-star-metric-tree`
- Growth model and forecasts: `growth-model`
- Experiment backlog and cadence: `growth-experiment-backlog`
- Experiment design: `experiment-design`
- Experiment analysis: `experiment-readout`
- New channels: `acquisition-channel-testing`
- Loops: `growth-loops`
- Referral: `referral-programmes`
- Funnels: `funnel-analysis`
- Retention cohorts: `cohort-retention-analysis`
- Tracking: `tracking-plan`
- Reporting: `growth-reporting`

## Worked example
A B2B scheduling SaaS had flat revenue despite growing sign-ups. The audit found the team optimised for sign-ups, the activation event (first booking received) fired for only 18% of new accounts within 14 days, cohort curves flattened at a low level for solo users but much higher for teams, and most acquisition came from one paid channel near saturation. The constraint: activation for solo users. The 90-day plan made weekly active teams the north star, rebuilt onboarding around receiving a first booking, added a team invite loop after first value and tested two new channels with retention as the success metric.

## Output format
```
# Growth audit: <company>, <date>
## The constraint (one sentence) and evidence
## North star and growth model snapshot
## Area scores
| Area | Score 0-3 | Key findings | Evidence label |
## 90-day plan
| # | Action | Area | Expected impact | Effort | Skill | Owner | Re-check |
```

## Common mistakes
- Scaling acquisition before retention flattens.
- Copying tactics without a model.
- Treating sign-ups as growth.
- Running many small, underpowered tests.
- Ignoring data problems until decisions go wrong.

## Questions to ask before you recommend changes
- What customer behaviour best predicts revenue?
- Where do cohort curves flatten, and for whom?
- How many experiments did the team run last quarter, and what changed because of them?

## Self-check before you answer
- Did I name one constraint with evidence?
- Did I check retention before acquisition?
- Is each finding labelled by evidence type?
- Does every action have a skill, owner and re-check date?

## Further reading
- Reforge growth frameworks: https://www.reforge.com/blog
- Amplitude North Star Playbook: https://amplitude.com/books/north-star

---
Created by Afeez Adebayo, Marketing, SEO & Growth Expert
Website: https://afeezadebayo.com
LinkedIn: https://www.linkedin.com/in/afeez-adebayo/
X: https://x.com/za_icon
Source: https://afeezadebayo.com/skills-md/marketing/growth-marketing/growth-audit/

Licence: CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/). You may copy, share and adapt this skill, including for commercial use, as long as you credit Afeez Adebayo and link to the source URL above. Keep this notice in any copy or adapted version.

Workflow

Step 1. Agree the goal and north star

Check whether the current north star reflects delivered customer value and predicts revenue. If not, propose one (north-star-metric-tree).

Step 2. Build a quick growth model

Map inputs to outcome with current numbers: new users by channel × activation rate × retention × monetisation, plus referral or loop contributions (growth-model).

Step 3. Read retention first

If cohort curves don't flatten, fix retention before scaling acquisition (cohort-retention-analysis).

Step 4. Find the biggest leak

Compare each step's conversion and volume with benchmarks from your own history and segments; find where the most value is lost (funnel-analysis).

Step 5. Review acquisition

Which channels bring users who retain? Where is the next scalable channel? (acquisition-channel-testing).

Step 6. Check loops and referral

Do users invite, share or create content that brings others? (growth-loops, referral-programmes).

Step 7. Check data and experimentation

Are events reliable (tracking-plan)? Are experiments well designed, powered and read correctly (experiment-design, experiment-readout)? Is there a steady experiment cadence (growth-experiment-backlog)?

Step 8. Name the constraint and plan

One sentence: "Growth is constrained by X because Y." Then a 90-day plan focused on it.

Scoring rubric

ScoreMeaning
0Missing or unknown
1Present but unreliable or unused
2Solid and used in decisions
3Strong, measured, improving through experiments

Common constraints and first moves

ConstraintSignFirst move
RetentionCurves keep fallingFind the value moment; improve onboarding and core experience
ActivationMany sign-ups, few reach valueRemove friction to first value
Acquisition scaleGood retention, slow volumeTest new channels; build loops
MonetisationEngaged users don't payPackaging, limits and upgrade prompts
Learning speedFew, slow experimentsBacklog, cadence and sizing discipline
DataNumbers disagreeFix the tracking plan before anything else

Edge cases and judgement calls

SituationWhat to do
Pre product-market fitFocus on retention of a narrow segment, not scale
B2B with few large customersUse account-level metrics; fewer, deeper experiments
MarketplaceAudit both sides and the liquidity between them
Very low trafficPrefer qualitative research and big changes over A/B tests
Seasonal businessCompare like periods; model seasonality explicitly

Handoffs to specialist skills

  • North star and metric tree: north-star-metric-tree
  • Growth model and forecasts: growth-model
  • Experiment backlog and cadence: growth-experiment-backlog
  • Experiment design: experiment-design
  • Experiment analysis: experiment-readout
  • New channels: acquisition-channel-testing
  • Loops: growth-loops
  • Referral: referral-programmes
  • Funnels: funnel-analysis
  • Retention cohorts: cohort-retention-analysis
  • Tracking: tracking-plan
  • Reporting: growth-reporting

Worked example

A B2B scheduling SaaS had flat revenue despite growing sign-ups. The audit found the team optimised for sign-ups, the activation event (first booking received) fired for only 18% of new accounts within 14 days, cohort curves flattened at a low level for solo users but much higher for teams, and most acquisition came from one paid channel near saturation. The constraint: activation for solo users. The 90-day plan made weekly active teams the north star, rebuilt onboarding around receiving a first booking, added a team invite loop after first value and tested two new channels with retention as the success metric.

Output format

# Growth audit: <company>, <date>
## The constraint (one sentence) and evidence
## North star and growth model snapshot
## Area scores
| Area | Score 0-3 | Key findings | Evidence label |
## 90-day plan
| # | Action | Area | Expected impact | Effort | Skill | Owner | Re-check |

Common mistakes

  • Scaling acquisition before retention flattens.
  • Copying tactics without a model.
  • Treating sign-ups as growth.
  • Running many small, underpowered tests.
  • Ignoring data problems until decisions go wrong.

Questions to ask before you recommend changes

  • What customer behaviour best predicts revenue?
  • Where do cohort curves flatten, and for whom?
  • How many experiments did the team run last quarter, and what changed because of them?

Self-check before you answer

  • Did I name one constraint with evidence?
  • Did I check retention before acquisition?
  • Is each finding labelled by evidence type?
  • Does every action have a skill, owner and re-check date?

Further reading

When to use this skill, and when not to

Use it when growth stalls, when a new growth lead joins, before planning a quarter, after product-market fit when scaling begins and when leadership asks where to invest.

Growth teams often start with tactics: a referral programme because a competitor has one, a channel someone read about, an experiment that was easy to ship. The audit builds the picture first, because growth is limited by one step at a time and improving anything else barely moves the outcome.

Don’t use it to fix one funnel step (use Funnel Analysis) or to run a single experiment (use Experiment Design).

Example prompts

  • “Sign-ups grow but revenue is flat. Run a growth audit.”
  • “I just joined as head of growth. Where should I focus first?”
  • “What is the biggest constraint on our growth right now?”
  • “Score our growth system and give me a 90-day plan.”
  • “Review our growth team’s experiments and metrics.”

Example output

The skill returns a fixed structure. A shortened example for an imaginary site:

# Growth audit: example scheduling SaaS, 10 October 2026

## Constraint
Activation for solo users: only 18% receive a first booking within 14 days (data)

## Area scores
| Area | Score | Finding |
| North star | 1 | Team optimises sign-ups |
| Retention | 1 | Solo cohorts flatten low; team cohorts much higher |
| Acquisition | 2 | One paid channel near saturation |
| Loops | 0 | No team invite loop |

## 90-day plan
1. North star: weekly active teams (north-star-metric-tree)
2. Onboarding to first booking (funnel-analysis)
3. Team invite loop after first value (growth-loops)

The audit names one constraint in one sentence, because a plan that tries to fix everything at once usually fixes nothing.

What the agent needs from you

The skill asks for your business model, pricing and 12 to 24 months of revenue, current goals and the metrics the team reviews, acquisition data by channel with downstream retention, funnel data from sign-up to activation and paid, cohort retention curves, your tracking plan or event list and your experiment history.

How this skill hands off to related skills

The audit routes every finding to a specialist: goals to North Star Metric, models to Growth Model, experiments to Experiment Backlog, Design and Readouts, acquisition to Channel Testing, Growth Loops and Referral, analytics to Funnels, Cohorts and Tracking, and reporting to Growth Reporting.

How to run the Growth Audit step by step

  1. Install the skill as growth-audit/SKILL.md, with the other 12 Growth Marketing skills so handoffs work.
  2. Share revenue, goals and metrics the team reviews.
  3. Export acquisition, funnel and cohort data.
  4. Add your event list and experiment history.
  5. Review the constraint, area scores and 90-day plan.
  6. Run the plan with the specialist skills and re-audit next quarter.

Situations this skill handles

Growth stalls for different reasons. The audit handles these situations:

SituationWhat the skill does
Sign-ups grow, revenue flatChecks activation and retention before acquisition
One channel provides most growthFlags concentration risk and plans channel tests
Few, slow experimentsFinds learning speed as the constraint
Numbers disagree between toolsPuts tracking first
MarketplaceAudits both sides and liquidity
Pre product-market fitNarrows to retention of one segment

What makes this skill different

Most growth audits end with a long list of ideas. This skill ends with one constraint, stated in a sentence with evidence, and a plan focused on it. It checks retention before acquisition, builds a quick model to see which input matters most, and labels every finding by whether it comes from data, tests or belief.

It also audits the team’s ability to learn: tracking quality, experiment design and cadence, because a team that learns faster outgrows one that guesses better.

Practical tips from real projects

  • One constraint at a time.
  • Retention before acquisition.
  • Model before tactics.
  • Learning speed is a growth lever.

A worked example: a B2B scheduling SaaS had flat revenue despite growing sign-ups. The audit found the team optimised for sign-ups, the activation event (first booking received) fired for only 18% of new accounts within 14 days, cohort curves flattened low for solo users but much higher for teams, and most acquisition came from one paid channel near saturation. The constraint was activation for solo users. The plan made weekly active teams the north star, rebuilt onboarding around a first booking, added a team invite loop after first value and tested two new channels judged on retention.

Common constraints have common first moves. Falling retention calls for finding the value moment and improving the core experience. Low activation calls for removing friction to first value. Slow acquisition with good retention calls for new channels and loops. Engaged users who don’t pay call for packaging and upgrade prompts. Slow learning calls for a backlog and cadence. Disagreeing numbers call for a tracking plan before anything else.

The scoring rubric keeps reviews comparable: 0 for missing or unknown, 1 for present but unreliable, 2 for solid and used in decisions, 3 for strong and improving through experiments. Re-running the audit each quarter shows whether the growth system itself is getting healthier.

Edge cases change the focus. B2B companies with few large customers need account-level metrics and fewer, deeper experiments. Marketplaces need both sides audited. Very low traffic favours qualitative research and big changes over A/B tests. Seasonal businesses need like-for-like comparisons.

Every action in the plan has an owner, a specialist skill and a re-check date, so the audit turns directly into work.

The audit covers ten areas: goals and north star, growth model, acquisition, activation, retention, monetisation, referral and loops, data and tracking, experimentation and reporting.

Frequently asked questions

A structured review of how a company grows: goals, model, acquisition, activation, retention, monetisation, referral, data, experimentation and reporting, ending with the biggest constraint and a plan.

Users who leave quickly make every acquisition pound leak away. If cohort curves don’t flatten, scaling acquisition mostly scales losses.

The one step that currently limits growth most, such as activation, retention or acquisition scale. Improving other steps has little effect until it is fixed.

With data ready, a first version takes one session. Agreeing the constraint and plan with the team usually takes longer than the analysis.

Yes, but the focus shifts to retention of a narrow segment rather than scale.

Each finding is marked as coming from data, from experiments or from beliefs and assumptions, so the team knows how much weight to give it.

Changelog

  • 1.0.0, 10 October 2026: first release.

Use, adapt and share this skill under CC BY 4.0: credit Afeez Adebayo and link to this page.