agentleFS
CodeAlive-AICodeAlive-AI/ceo-ai-os/skills/designing-growth-loops/SKILL.md

designing-growth-loops

Skill9 starsChanged 6 months agoMITView on GitHub

Design and optimize growth loops — viral mechanics, referral programs, product-led acquisition, content loops. Use when building PLG growth engine, figuring out how to make the product grow itself, or evaluating organic vs paid acquisition ratio. For PLS conversion, see product-led-sales. For pricing, see pricing-strategy.

2 other projects use a version of this, 2 of them edited.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

5 rules. About 0 are common, 4 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Before helping, read MEMORY.md for: current wedge, ICP, competitors, PMF stage, system constraint.

    line 7
  2. Distinctive:

    Follow output preferences from USER.md (language, format, platform constraints).

    line 9
  3. Distinctive:

    When the user asks for help with growth loops:

    line 19
  4. Distinctive:

    Assess prerequisites: - Check if they have the LTV, network effects, or product stickiness to support the loop

    line 22
  5. Distinctive:

    Design for compounding: - Ensure the loop feeds back into itself for sustainable growth

    line 24

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

[YOUR_PRODUCT] Context

Before helping, read MEMORY.md for: current wedge, ICP, competitors, PMF stage, system constraint. Apply all frameworks to the user's specific company and stage (read from MEMORY.md). Follow output preferences from USER.md (language, format, platform constraints). For chat platforms: max 15 lines, no markdown tables, be concrete and actionable.

Designing Growth Loops

Help the user design effective growth loops using frameworks from 54 product leaders who have built viral and product-led growth engines at companies from Dropbox to LinkedIn to Calendly.

How to Help

When the user asks for help with growth loops:

  1. Identify the loop type - Determine if they need viral, paid, content, or product-led acquisition loops
  2. Assess prerequisites - Check if they have the LTV, network effects, or product stickiness to support the loop
  3. Find the natural sharing moment - Help them identify where users would naturally want to bring others in
  4. Design for compounding - Ensure the loop feeds back into itself for sustainable growth

Core Principles

One dominant loop matters most

Luc Levesque: "It's usually just one loop that you need to get right. Most successful companies scale primarily through one dominant, well-executed growth loop." Focus on identifying and dominating one primary channel before diversifying.

Viral growth is a learnable science

Nikita Bier: "With certainty, if you're good at your job, you can make an app grow and go viral." Develop a library of growth tactics based on platform-specific mechanisms.

LTV unlocks paid loops

Yuriy Timen: "If you have really healthy LTVs, then there is a big opportunity to play paid and lean into paid growth loops." Calculate if single-player LTVs are high enough to support sustainable paid acquisition.

Product-led acquisition has zero marginal cost

Julian Shapiro: "By me trying to use PayPal in its everyday intention, I'm automatically enticing someone else to become a PayPal customer." PLA is the most scalable channel because it's entirely within the company's control.

Innovation over optimization in fast markets

Elena Verna: "I feel like only 30 to 40% of what I've learned transfers here because we need to invest in such bigger bets and innovate and create new growth loops." In fast-moving AI categories, shift from 95% optimization to 95% innovation.

Word-of-mouth requires frequency

Uri Levine: "Word-of-mouth you can only have if you have high frequency of use." Sustainable word-of-mouth is tied to how often users engage with the product.

40-50% organic is the healthy ratio

Gokul Rajaram: "A good metric is that 40 to 50% of your new customers should ideally come from organic channels. If 90% come from paid, at some point the music is going to stop."

Questions to Help Users

  • "What's the natural moment when users would want to bring others in?"
  • "Does your product become more valuable when more people use it?"
  • "What percentage of your growth is organic vs paid?"
  • "What's your customer LTV and payback period?"
  • "Is there an action users take that automatically exposes your product to others?"
  • "Can you identify where users already share your product organically?"

Common Mistakes to Flag

  • Paid acquisition on freemium - Consumer subscriptions relying on paid acquisition will predictably fail
  • Manufacturing network effects - Network effects are usually inherent; hard to add as an afterthought
  • Diversifying too early - Early-stage companies should focus on one working engine
  • Single-channel dependency - Late-stage companies with 90%+ reliance on one channel are at extreme risk
  • Referral programs without organic WOM - Referrals amplify existing word-of-mouth; they can't create it

Deep Dive

For all 84 insights from 54 guests, see references/guest-insights.md

Related Skills

  • measuring-product-market-fit: PMF signals drive loop selection
  • pricing-strategy: Pricing affects LTV which unlocks paid loops
  • product-led-sales: PLS is a growth loop type
  • user-onboarding: Onboarding quality determines loop conversion
  • community-building: Community is a growth loop amplifier

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.