growth-loops · git:20261108.7feb18f · 2026-11-08 · sha256 52bd8d876bed230f
growth-loops git:20261108.7feb18fA
Immutable. This exact content never changes and is served at /api/v1/blob/52bd8d876bed230f.
No tool to install first
claude plugin marketplace add https://markdownregistry.com/mp/a/art_nycuv4qvwyj3pt6v/52bd8d876bed230fe9c4cca830607295ab097122b5e1b09bb88d1dd182380be5.json
Then /plugin install growth-loops@markdownregistry-nycuv4qvwyj3pt6v in Claude Code. It installs this exact version, the one graded A here, pinned to the commit it was graded at, and leaves it there.
--- name: growth-loops description: "Designing how a product grows: loops that compound (viral, usage, collaboration, user-generated, referral)." --- # Growth loops ## Overview **Identify and design growth loops (flywheels) that compound user acquisition through the product.** Evaluate five proven mechanisms for sustainable traction, reducing reliance on paid acquisition and building product-led growth. ## When to use Use this analysis for: - Designing growth mechanisms for a product - Building sustainable viral or referral traction - Reducing reliance on paid acquisition - Analyzing competitor growth strategies - Optimizing a product for product-led growth ## The 5 growth loop types ### 1. Viral loop **Shared user-created product content brings new users back to the product.** Users share it on external platforms. | Aspect | Details | |---|---| | Mechanism | Users create content in-product → Share on social/external platforms → New users discover and signup | | Example | Figma designs shared as links, Loom videos shared in emails | | Strength | Exponential user acquisition if content is inherently shareable | | Challenge | Requires highly shareable output and strong incentive to share | ### 2. Usage loop **Sharing content or value created in-product invites new users or drives re-engagement.** | Aspect | Details | |---|---| | Mechanism | User creates → Shares creation → Others consume → Become engaged users | | Example | Twitter threads, Medium articles, Notion templates shared publicly | | Strength | Growth tied directly to product usage and network effects | | Challenge | Requires content creation friction to be very low | ### 3. Collaboration loop **Inviting colleagues to co-create expands the user base within organizations.** Users invite them to collaborate within the product. | Aspect | Details | |---|---| | Mechanism | User creates → Invites colleagues for collaboration → Colleagues discover product value | | Example | Google Docs invitations, Figma team projects, Slack channels | | Strength | Deep organizational penetration and high retention | | Challenge | Works best for collaborative/team-based products | ### 4. User-generated loop **Users discover others' creations, then create and share their own content.** They discover new content or features through those creations. | Aspect | Details | |---|---| | Mechanism | User discovers content → Creates similar content → Shares creation → Others discover | | Example | TikTok, Pinterest, YouTube trends driving creator participation | | Strength | Creates content flywheel and network effects | | Challenge | Requires critical mass of quality content to sustain | ### 5. Referral loop **Users invite potential users for rewards, incentives or social recognition.** | Aspect | Details | |---|---| | Mechanism | User refers → Referred user joins → Referrer gets reward → Shares more referrals | | Example | Dropbox referral bonus, Uber rider referrals, PayPal signup bonuses | | Strength | Directly incentivizes acquisition; easy to measure ROI | | Challenge | Requires valuable incentive without eroding unit economics | ## How it works ### Step 1: Define product value **Clarify the core value users experience.** Identify: - The primary action users take in your product - Value created per user action - Network effects present (if any) - Friction points in the experience ### Step 2: Evaluate loop fit **Assess which growth loops align with your product.** Consider: - Product type (collaborative, content-based, utility, etc.) - Target user behavior and sharing habits - Network effects already present - Existing user base and engagement ### Step 3: Design loop mechanics **Design the specific mechanics of the loop.** Include: - The trigger that initiates sharing or invitations - Incentive for participation (intrinsic or extrinsic) - Ease of the sharing mechanism - Conversion rate from invite to activation - Frequency of loop repetition per user ### Step 4: Calculate loop coefficient **Estimate growth velocity and the loop coefficient.** Calculate: - Invites/shares per user per cycle - Conversion rate of invites to new users - Net new users per cycle - Time per cycle iteration ### Step 5: Build the loop **Implement the highest-leverage loop first.** Start with the most natural loop for your product. Optimize messaging and friction, measure loop metrics and conversion rates, and compound results over time. ## Input format **Pass the product and growth context through $ARGUMENTS.** Include: - Product description and primary user action - Target user demographics and behavior - Existing sharing/collaboration features - Current growth channels and metrics - Constraints or opportunities ## Output **Produce a ranked growth-loop analysis and implementation plan.** Include: - Ranked evaluation of all 5 loop types for your product - Recommended primary growth loop with implementation plan - Secondary loops to layer over time - Key metrics and measurement framework - 30-60-90 day implementation roadmap - Potential loop coefficient and growth projections ## Framework Based on growth loops research by Ognjen Bošković. The focus is compounding user acquisition through built-in, product-native sharing and collaboration mechanisms. ## Tips - **Start with one loop and master it before adding complexity.** - **Viral loops compound fastest but take time to build.** - **Collaboration loops create the strongest retention and LTV.** - **Measure loop health weekly during the optimization phase.** - **Combine loops for multiplicative effect once operating at scale.** ## How you can tell it worked Each loop names who acts, what their action produces and how that brings the next user. The step most likely to break is marked as the one to test.