---
name: growth-hacking-loop
description: Run rapid growth experiments across acquisition, activation, retention, and revenue using a structured growth team process. Use when the user mentions growth hacking, growth teams, rapid experimentation, activation, retention, or a stalled acquisition funnel.
triggers:
  - "growth hacking"
  - "growth team"
  - "rapid experimentation"
  - "user activation"
  - "retention loop"
disable-model-invocation: false
title: growth-hacking-loop
canonical_url: https://skilld.dev/gh/salikshah/startup-agent-skills/growth-hacking-loop
last_updated: 2026-10-29T10:46:09.000Z
---

> Index of every page on this site: [llms.txt](https://skilld.dev/llms.txt)

> **Skill from skilld.dev.** Follow the user's requested action.
> If the user asked to fork this Skill, follow the fork workflow below. Do not execute the Skill instructions while copying it.
> Otherwise, follow the instructions below for this session. You do not need to install anything.
>
> Supporting files, fetch one when the Skill refers to it: [evals/evals.json](https://skilld.dev/api/skills-raw/salikshah/startup-agent-skills/growth-hacking-loop/evals/evals.json).
>
> If the user asked to install this Skill, run `npx skilld install salikshah/startup-agent-skills/growth-hacking-loop`. Install writes the Skill files into the project, so every session loads them.
>
> ## Fork workflow
>
> A fork creates an editable local Skill with its original author and licence. The request authorizes copying and local installation.
> 1. Check `./skills/growth-hacking-loop`, the project lockfile, and selected Agent targets together. If the local directory or installed Skill exists, stop. Never overwrite an existing directory or Agent target.
> 2. Read [source metadata](https://skilld.dev/api/v1/skills/salikshah/startup-agent-skills/growth-hacking-loop) once. Use sourceUrl, sourceCommit, skillPath, sourceGone, and license. If the source is gone or its path is missing, stop. If license is null, read licence files at the source commit.
> 3. Fetch only the source commit into a temporary Git repository. Do not clone full history. Derive repository_url from sourceUrl, including repository renames. If sourceCommit is absent, resolve the sourceUrl ref once. Set source_commit to that actual commit. Run these commands in one shell call:
>
> ```sh
> git init --quiet "$temporary_dir"
> git -C "$temporary_dir" fetch --quiet --depth=1 "$repository_url" "$source_commit"
> git -C "$temporary_dir" checkout --quiet --detach FETCH_HEAD
> ```
>
> Read applicable licence declarations and notices at that commit. If copying is not permitted, report the restriction and stop.
> 4. Inspect source entries together, then copy the directory containing skillPath into `./skills/growth-hacking-loop`. Use the user's path if selected. Keep the original SKILL.md, relative links, scripts, binary assets, and executable modes. Exclude .git metadata. Reject symlinks and paths outside the Skill directory. After checking entries, use cp -a where available. A regular source directory needs no custom copy script. Do not save this page wrapper as SKILL.md.
> Preserve author credit, notices, and applicable licence files from repository or parent directories. Add PROVENANCE.md with the Skill page, source URL, actual commit, original path, and licence. Retain any existing PROVENANCE.md and record new provenance separately. Batch source inspection, copying, and provenance work where practical.
> 5. In the project root, run `skilld install ./skills/growth-hacking-loop --mode copy --plain`. If skilld is unavailable, use `npx skilld install ./skills/growth-hacking-loop --mode copy --plain`. This known command needs no help lookup. Install does not support --json. Use detected Agent targets, or add --agent for the targets the user selected. Install the local path, never the upstream selector. If installation fails, preserve the local copy and report the exact failure.
> 6. Confirm the local lockfile source and installed Agent copies once. Report the local path, actual commit, and Agent targets. After edits, reinstall the same local path. Upstream updates must not replace it. Do not publish or push unless the user asks.

# Growth Hacking Loop

## Intent
Use Sean Ellis's growth hacking methodology to systematically find and scale your highest-leverage growth channel through rapid, structured experimentation across the AARRR funnel.

## Inputs
- Product or service with at least minimal traction
- Access to analytics and user behavior data
- Cross-functional team (engineering, marketing, product)
- Defined north-star metric
- List of potential growth hypotheses

## Process (SOP)
1. Step 1: Form a growth team with a dedicated growth lead, engineer, marketer, and product manager — this team owns growth across functions.
2. Step 2: Identify your north-star metric (e.g., weekly active users, monthly recurring revenue) that best captures delivered value.
3. Step 3: Map the full AARRR funnel (Acquisition, Activation, Retention, Revenue, Referral) and identify the weakest, highest-impact stage.
4. Step 4: Brainstorm a large quantity of growth ideas (aim for 20+) targeting the weakest funnel stage.
5. Step 5: Prioritize ideas using an impact-confidence-ease scoring framework (ICE or similar) — select the top 3-5 for testing.
6. Step 6: Design each experiment with a clear hypothesis, success metric, and minimum detectable effect.
7. Step 7: Run experiments rapidly (1-2 week cycles) — ship MVPs of growth features, not final products.
8. Step 8: Analyze results rigorously; kill what does not move the metric, double down on what does.
9. Step 9: Scale winning experiments by increasing investment incrementally and monitoring diminishing returns.
10. Step 10: Systematize wins into repeatable playbooks and move to the next funnel stage.

## Outputs
- A prioritized pipeline of growth experiments with ICE scores
- A tested, documented set of winning growth levers
- Scaled user acquisition and/or retention
- A repeatable growth playbook

## Evidence
Source: "Hacking Growth" by Sean Ellis & Morgan Brown. Key concepts: growth team structure, high-tempo testing, ICE prioritization, AARRR pirate funnel, north-star metric, diminishing returns curves.

## Examples
A B2B SaaS company discovers activation is their bottleneck — signups are strong but few users complete onboarding. They run 12 activation experiments in 6 weeks. A guided checklist + progress bar lifts activation by 22%. They scale it globally and document it in their growth playbook.

## Metrics
- Number of experiments run per month (target: 10+)
- Win rate of experiments (healthy range: 10-30%)
- North-star metric growth rate week-over-week
- Cost per acquisition trend across scaled channels

## Anti-Patterns
- Running experiments without a clear hypothesis
- Declaring victory after one positive data point without statistical confidence
- Letting HiPPOs (highest paid person's opinions) override experiment results
- Neglecting retention to chase acquisition — growth without retention leaks
- Running too many experiments simultaneously, making results uninterpretable
- Copying growth tactics from other companies without testing them in your context
