designing-growth-loops
Help users design and optimize growth loops. Use when someone is building viral mechanics, designing referral programs, creating product-led acquisition, or figuring out how to make their product grow itself.
What this skill does
# 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. Over the years of building all these apps, I've accrued all these growth hacks that still nobody knows about." 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. If you're using Waze every day, then every day you have an opportunity to tell someone else." Sustainable word-of-mouth is tied to how often users engage with the product. ### Map the loops qualitatively and quantitatively Ben Williams: "Being able to identify the various micro and macro loops, how they're all connected, being able to document them in a qualitative model provides a shared understanding and guides intentional investment." ### 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 - Pricing Strategy - Retention & Engagement - Marketplace Liquidity Management
Related in Ads & Marketing
ads
IncludedMulti-platform paid advertising audit and optimization skill. Analyzes Google, Meta, YouTube, LinkedIn, TikTok, Microsoft, and Apple Ads. 250+ checks with scoring, parallel agents, industry templates, and AI creative generation.
banana
IncludedAI image generation Creative Director powered by Google Gemini Nano Banana models. Use this skill for ANY request involving image creation, editing, visual asset production, or creative direction. Triggers on: generate an image, create a photo, edit this picture, design a logo, make a banner, visual for my anything, and all /banana commands. Handles text-to-image, image editing, multi-turn creative sessions, batch workflows, and brand presets.
rpg-migration-analyzer
IncludedAnalyzes legacy RPG (Report Program Generator) programs from AS/400 and IBM i systems for migration to modern Java applications. Extracts business logic from RPG III/IV/ILE source code, identifies data structures (D-specs), file operations (F-specs), program dependencies (CALLB/CALLP), and converts RPG constructs to Java equivalents. Generates migration reports, complexity estimates, and Java implementation strategies with POJO classes, JPA entities, and service methods. Use when modernizing AS/400 or IBM i legacy systems, analyzing RPG source files (.rpg, .rpgle, .RPGLE), converting RPG to Java, mapping data specifications to Java classes, planning legacy system migration, or when user mentions RPG analysis, Report Program Generator, RPG III/IV/ILE, AS/400 modernization, IBM i migration, packed decimal conversion, or mainframe application rewrite.
brand-library-architect
IncludedBuild a complete brand library for a product — visual asset render pipeline, brand documentation set (BRAND, COPY, MANIFESTO, BIOS, FAQ, GLOSSARY, TONE, PRICING), open-source convention files (README, CONTRIBUTING, SECURITY, CODE_OF_CONDUCT), and a self-contained press kit. This skill should be used when the user asks to "build a brand library / brand kit / press kit / brand assets" for a product, "set up a brand library workflow," "create a positioning manifesto plus visual identity," or any combination of brand documentation + visual asset pipeline. Apply phase-by-phase or run end-to-end. Templates are product-agnostic and use {{TOKEN}} placeholders the skill prompts the user to fill.
writing-tech-post
IncludedAuthors engineering blog posts end-to-end: launch deep-dives, incident postmortems, architecture migrations, performance case studies, tutorials, AI/agent system writeups, security disclosures, and research-to-product translations. Picks the correct archetype, plans the abstraction ladder, enforces an evidence cadence (diagrams, benchmarks, profiles, traces, code, ablations), tunes voice against publisher house styles (Datadog, Vercel, GitHub, AWS, Meta, Cloudflare, Jane Street), and runs a pre-publish gate for narrative momentum and disclosure ethics. Use when drafting a new engineering post, restructuring a draft that feels flat, deciding which evidence form belongs where, validating that depth and product context are balanced, or preparing a postmortem, migration, or performance narrative for external publication. Do not use for API reference documentation, README authoring, marketing copy, release notes, generic SEO content, ghost-written executive thought leadership, or non-engineering long-form essays.
blog-google
IncludedGoogle API integration for blog performance: PageSpeed Insights, CrUX Core Web Vitals with 25-week history, Search Console performance, URL Inspection, Indexing API, GA4 organic traffic, NLP entity analysis for E-E-A-T, YouTube video search for embedding, and Google Ads Keyword Planner. Progressive feature availability based on credential tier (API key, OAuth/service account, GA4, Ads). Shares config with claude-seo at ~/.config/claude-seo/google-api.json. Use when user says "google data", "page speed", "core web vitals", "search console", "indexation", "GA4", "keyword research", "nlp entities", "blog performance", "youtube search", "google api setup".