designing-growth-loops▌
refoundai/lenny-skills · updated Apr 8, 2026
MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.
$22
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:
- Identify the loop type - Determine if they need viral, paid, content, or product-led acquisition loops
- Assess prerequisites - Check if they have the LTV, network effects, or product stickiness to support the loop
- Find the natural sharing moment - Help them identify where users would naturally want to bring others in
- 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
How to use designing-growth-loops on Cursor
AI-first code editor with Composer
Prerequisites
Before installing skills in Cursor, ensure your development environment meets these requirements:
- ›Cursor installed and configured on your development machine
- ›Node.js version 16.0+ with npm package manager (verify with
node --version) - ›Active project directory or workspace where you want to add designing-growth-loops
Execute installation command
Execute the skills CLI command in your project's root directory to begin installation:
The skills CLI fetches designing-growth-loops from GitHub repository refoundai/lenny-skills and configures it for Cursor.
Select Cursor when prompted
The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:
Verify installation
Confirm successful installation by checking the skill directory location:
Reload or restart Cursor to activate designing-growth-loops. Access the skill through slash commands (e.g., /designing-growth-loops) or your agent's skill management interface.
Security & Verification Notice
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your development environment. Always verify the publisher's identity, review recent commits, and test in isolated environments before production deployment.
List & Monetize Your Skill
Submit your Claude Code skill and start earning
Use Cases▌
Task Automation & Efficiency
Automate repetitive workflows and reduce manual effort
Example
Generate reports, summarize documents, draft communications
Save 3-5 hours per week on routine tasks
Knowledge Enhancement
Learn new skills, understand complex topics, get expert guidance
Example
Explain concepts, provide examples, suggest learning resources
Accelerate learning and skill development by 2x
Quality Improvement
Enhance output quality through reviews, suggestions, and refinements
Example
Review drafts, suggest improvements, catch errors
Improve work quality by 30-40% with less effort
Implementation Guide▌
Prerequisites
- ›Claude Desktop or compatible AI client with skill support
- ›Clear understanding of task or problem to solve
- ›Willingness to iterate and refine outputs
Time Estimate
15-45 minutes depending on use case complexity
Installation Steps
- 1.Install skill using provided installation command
- 2.Test with simple use case relevant to your work
- 3.Evaluate output quality and relevance
- 4.Iterate on prompts to improve results
- 5.Integrate into regular workflow if valuable
Common Pitfalls
- ⚠Expecting perfect results without iteration
- ⚠Not providing enough context in prompts
- ⚠Using skill for tasks outside its intended scope
- ⚠Accepting outputs without review and validation
Best Practices▌
✓ Do
- +Start with clear, specific prompts
- +Provide relevant context and constraints
- +Review and refine all outputs before using
- +Iterate to improve output quality
- +Document successful prompt patterns
✗ Don't
- −Don't use without understanding skill limitations
- −Don't skip validation of outputs
- −Don't share sensitive information in prompts
- −Don't expect skill to replace human judgment
💡 Pro Tips
- ★Be specific about desired format and style
- ★Ask for multiple options to choose from
- ★Request explanations to understand reasoning
- ★Combine AI efficiency with human expertise
When to Use This▌
✓ Use When
Use when skill capabilities match your task, clear ROI on time saved, and you can validate outputs. Best for repetitive tasks, learning, and quality improvement.
✗ Avoid When
Avoid when task requires deep expertise you can't validate, involves sensitive decisions, or when learning process is more valuable than speed of completion.
Learning Path▌
- 1Familiarize yourself with skill capabilities and limitations
- 2Start with low-risk, non-critical tasks
- 3Progress to more complex and valuable use cases
- 4Build expertise through regular use and experimentation
Discussion
Product Hunt–style comments (not star reviews)- No comments yet — start the thread.
Ratings
4.6★★★★★41 reviews- ★★★★★Ishan Agarwal· Dec 28, 2024
designing-growth-loops reduced setup friction for our internal harness; good balance of opinion and flexibility.
- ★★★★★Aditi Rahman· Dec 20, 2024
We added designing-growth-loops from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
- ★★★★★Aanya Rahman· Dec 12, 2024
designing-growth-loops is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
- ★★★★★Ganesh Mohane· Dec 4, 2024
Keeps context tight: designing-growth-loops is the kind of skill you can hand to a new teammate without a long onboarding doc.
- ★★★★★Sakshi Patil· Nov 23, 2024
designing-growth-loops has been reliable in day-to-day use. Documentation quality is above average for community skills.
- ★★★★★Sakura Iyer· Nov 19, 2024
I recommend designing-growth-loops for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
- ★★★★★Liam Farah· Nov 3, 2024
Solid pick for teams standardizing on skills: designing-growth-loops is focused, and the summary matches what you get after install.
- ★★★★★Olivia Gill· Oct 22, 2024
designing-growth-loops has been reliable in day-to-day use. Documentation quality is above average for community skills.
- ★★★★★Chaitanya Patil· Oct 14, 2024
Solid pick for teams standardizing on skills: designing-growth-loops is focused, and the summary matches what you get after install.
- ★★★★★Nia Liu· Oct 10, 2024
Useful defaults in designing-growth-loops — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
showing 1-10 of 41