Skip to content
growth logo

ID8GROWTH - Growth Engine

growth

Growth engine for ID8Labs. Systematic experimentation and optimization to scale products through data-driven decisions, retention focus, and sustainable acquisition channels.

SKILL.md

Full skill instructions

ID8GROWTH - Growth Engine

Purpose

Scale your launched product through systematic experimentation. Growth is not magic—it's methodology.

Philosophy: Retention beats acquisition. One channel mastered beats five attempted. Data over intuition.


When to Use

  • Product is launched and has initial users
  • User needs to grow user base
  • User asks "how do I get more users?"
  • User wants to improve retention
  • User needs help with analytics
  • User wants to optimize conversion
  • Project is in LAUNCHING or GROWING state

Commands

/​growth <project-slug>

Run full growth analysis and planning.

Process:

  1. BASELINE - Understand current metrics
  2. MODEL - Map growth mechanics
  3. DIAGNOSE - Find bottlenecks
  4. HYPOTHESIZE - Generate experiments
  5. PRIORITIZE - ICE scoring
  6. EXECUTE - Run experiments
  7. LEARN - Analyze and iterate

/​growth metrics

Audit current analytics and define key metrics.

/​growth funnel

Analyze conversion funnel and identify drop-offs.

/​growth experiment <hypothesis>

Design a specific growth experiment.

/​growth retention

Deep dive on retention and engagement.


Growth Philosophy

Solo Builder Reality

What WorksWhat Doesn't
Focused effort on one channelSpray-and-pray multi-channel
Retention optimizationEndless acquisition
Organic/​content marketingExpensive paid acquisition
Personal touchAutomated spam
Slow compoundingViral hacks

Growth Priorities

Stage 1: Pre-PMF (< 100 users)

  • Focus: Finding users who love it
  • Metric: Qualitative feedback, NPS
  • Don't worry about: Scale

Stage 2: Early Traction (100-1000 users)

  • Focus: Retention and activation
  • Metric: Day 1/​7/​30 retention
  • Don't worry about: Growth rate

Stage 3: Growth (1000+ users)

  • Focus: Scalable acquisition
  • Metric: CAC, LTV, growth rate
  • Now optimize: Everything

Process Detail

Phase 1: BASELINE

Establish current state:

MetricValueSource
Total users{N}Database
Active users (DAU/​WAU/​MAU){N}Analytics
Activation rate{%}Funnel
Retention (D1/​D7/​D30){%}Cohort
Conversion (free→paid){%}Funnel
Revenue (MRR/​ARR)${X}Payments
NPS{score}Survey

If no tracking:

  • Set up analytics first
  • Use analytics-tracking skill
  • Minimum: Sign-ups, activation, retention

Phase 2: MODEL

Map your growth mechanics:

ACQUISITION
How do users find you?
├── Organic search
├── Social/​content
├── Referrals
├── Paid (if any)
└── Direct

ACTIVATION
What's the "aha moment"?
├── First action completed
├── Value received
└── Setup finished

RETENTION
Why do they come back?
├── Core value loop
├── Notifications
├── Habit formation
└── New content/​features

REVENUE
How do you monetize?
├── Subscription
├── Usage-based
├── One-time
└── Freemium conversion

REFERRAL
How do they spread it?
├── Word of mouth
├── Built-in sharing
├── Incentivized referral
└── Social proof

Phase 3: DIAGNOSE

Find the bottleneck:

StageBenchmarkYour RateStatus
Visitor → Sign-up2-5%{%}{OK/​LOW}
Sign-up → Activated20-40%{%}{OK/​LOW}
Activated → Day 720-30%{%}{OK/​LOW}
Day 7 → Day 3050-70%{%}{OK/​LOW}
Free → Paid2-5%{%}{OK/​LOW}

Diagnosis framework:

  1. Compare to benchmarks
  2. Identify biggest drop-off
  3. That's your focus

Phase 4: HYPOTHESIZE

Generate experiment ideas:

For each bottleneck, generate 3-5 hypotheses:

If we [change]
Then [metric] will [improve/​increase/​decrease]
Because [reasoning]

Example:

If we add an onboarding checklist
Then activation rate will increase by 20%
Because users will know what to do next

Phase 5: PRIORITIZE

ICE Scoring:

ExperimentImpactConfidenceEaseScore
{exp 1}{1-10}{1-10}{1-10}{avg}
{exp 2}{1-10}{1-10}{1-10}{avg}

Definitions:

  • Impact: How much will this move the metric?
  • Confidence: How sure are we it will work?
  • Ease: How easy is it to implement?

Rule: Do highest ICE score first.

Phase 6: EXECUTE

For each experiment:

  1. Define hypothesis clearly
  2. Define success metric
  3. Define sample size needed
  4. Implement change
  5. Run for sufficient time
  6. Analyze results
  7. Document learnings

Minimum experiment duration:

  • High traffic: 1-2 weeks
  • Low traffic: 2-4 weeks
  • Statistical significance matters

Phase 7: LEARN

After each experiment:

QuestionAnswer
Did it work?{Yes/​No/​Inconclusive}
What was the lift?{X}%
Why did it work/​fail?{reasoning}
What did we learn?{insight}
What's next?{next experiment}

Framework References

Growth Loops

frameworks/​growth-loops.md - Viral, content, flywheel mechanics

Analytics

frameworks/​analytics.md - Metrics, tracking, dashboards

Acquisition

frameworks/​acquisition.md - Channels, CAC, scale

Retention

frameworks/​retention.md - Engagement, churn, habit

Optimization

frameworks/​optimization.md - A/​B testing, CRO


Output Templates

Growth Model

templates/​growth-model.md - Growth strategy document

Metrics Dashboard

templates/​metrics-dashboard.md - KPI tracking structure


Tool Integration

MCPs

Supabase:

  • Query user data for analysis
  • Cohort analysis
  • Funnel tracking

Perplexity:

  • Research growth tactics
  • Find benchmarks
  • Competitor analysis

Skills

analytics-tracking:

  • Set up tracking
  • Define events
  • Create dashboards

Handoff

After completing growth analysis:

  1. Save outputs:

    • Growth model → docs/​GROWTH_MODEL.md
    • Metrics → docs/​METRICS.md
  2. Log to tracker:

    /​tracker log {project-slug} "GROWTH: Analysis complete. Focus: {bottleneck}. Top experiment: {experiment}."
    
  3. Update state:

    /​tracker update {project-slug} GROWING
    
  4. Next steps:

    • Execute top-priority experiments
    • Review results weekly
    • When stable, transition to ops

Key Metrics Cheat Sheet

AARRR Funnel

StageWhat to Track
AcquisitionTraffic, channels, CAC
ActivationSign-up rate, onboarding completion
RetentionDAU/​MAU, D1/​D7/​D30, churn
RevenueMRR, ARPU, LTV
ReferralK-factor, invite rate

Benchmarks

MetricPoorOKGoodGreat
D1 retention<10%10-20%20-30%>30%
D7 retention<5%5-10%10-20%>20%
D30 retention<2%2-5%5-10%>10%
Free→Paid<1%1-2%2-5%>5%
NPS<00-3030-50>50

Anti-Patterns

Anti-PatternWhy BadDo Instead
Vanity metricsDon't drive businessFocus on actionable metrics
Too many experimentsNo learningsOne experiment at a time
No hypothesisCan't learnAlways have clear hypothesis
Short experimentsInconclusiveRun to significance
Ignoring retentionLeaky bucketFix retention first
Copying othersContext mattersAdapt to your situation

Quality Checks

Before finalizing growth plan:

  • Baseline metrics established
  • Biggest bottleneck identified
  • Hypotheses are testable
  • Experiments are prioritized
  • Success metrics defined
  • Realistic timeline set
  • Learning process planned

More skills from majiayu000

xiaohongshu logo
majiayu000/claude-arsenal

xiaohongshu

xiaohongshu

286 148
View
agent-task-conductor logo
majiayu000/claude-skill-registry

agent-task-conductor

Conduct multi-agent task orchestration and workflow coordination.

663 1
View
conductor-setup logo
majiayu000/claude-skill-registry

conductor-setup

Initialize project with Conductor artifacts (product definition,

663 1
View
animation-designer logo
majiayu000/claude-skill-registry

animation-designer

Expert in web animations, transitions, and motion design using Framer Motion and CSS

663 1
View
diagramming logo
majiayu000/claude-skill-registry

diagramming

Creates Mermaid and ASCII diagrams for flowcharts, architecture, ERDs, state machines, mindmaps, and more. Use when user mentions diagram, flowchart, mermaid, ASCII diagram, text diagram, terminal diagram, visualize, C4, mindmap, architecture diagram, sequence diagram, ERD, or needs visual docume...

663 1
View
h3-pg logo
majiayu000/claude-skill-registry-data

h3-pg

PostgreSQL bindings for H3 hexagonal grid system. Use when working with H3 cells in Postgres, including spatial indexing, geometry/geography integration, and raster analysis.

23 1
View
conductor-development logo
majiayu000/claude-skill-registry

conductor-development

Context-Driven Development skill for projects using Conductor. Use this skill when you detect a `conductor/` directory in the project, when working on tasks defined in a `plan.md` file, or when the user asks about tracks, specs, or plans. Automatically applies TDD workflow, tracks task completion...

663 1
View
conductor-status logo
majiayu000/claude-skill-registry

conductor-status

Display project status, active tracks, and next actions

663 1
View
dockerization logo
majiayu000/claude-skill-registry

dockerization

Official Stakpak application containerization standard operating procedure, a step-by-step guidline to properly dockerize applications. This is a rule book curated by the Stakpak Team.

663 1
View

Popular AI tools

Kaiber logo
Video

Kaiber

Generate, edit, and beat-sync AI video with leading models in one workspace.

Paid
View
Vimcal logo
Productivity

Vimcal

The world's fastest calendar for remote work

Free
View

Transform Your Design with AI Designer by ImgCreator.ai

Freemium
View
Akool AI logo
Content & writing

Akool AI

Revolutionizing Video Production with AI-Powered Creativity

Paid
View

Extend an image past the frame and let AI fill the new aspect ratio.

Freemium
View
StarByFace logo
Security

StarByFace

Discover your celebrity doppelgänger with StarByFace!

Free
View
C

ChainClarity explains 700+ crypto whitepapers in plain English, with layered summaries, comparisons, research tools, alerts, and a $4.99 Pro plan.

Freemium
View
Opus Clip logo
Coding & apps

Opus Clip

Opus.ai: Revolutionize Your Web Experience

Free
View