growth-strategy▌
manojbajaj95/claude-gtm-plugin · updated Apr 8, 2026
MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.
Comprehensive growth strategy combining technical SEO/SMO/CRO implementation with strategic growth frameworks.
Growth Strategy
Comprehensive growth strategy combining technical SEO/SMO/CRO implementation with strategic growth frameworks.
Quick Reference
| Situation | Use This Skill For |
|---|---|
| SEO/SMO/CRO implementation | Technical Optimization |
| Building growth engines | Growth Loops Framework |
| Strategic growth planning | Strategy & Frameworks |
| Distribution strategy | Channel & Platform Strategy |
| Network effects | Product-Led Growth |
Part 1: Core Principles
Foundational Truths
- Growth follows product-market fit, never precedes it
- Retention is the foundation; acquisition without retention is a leaky bucket
- The best growth is product-driven, not marketing-driven
- Compound effects beat linear efforts
- Every growth channel eventually saturates
- Network effects are the ultimate moat
- Premature growth destroys companies
Growth Is Not Marketing
Growth is the systematic application of product, engineering, and data to create compounding user acquisition, activation, and retention. It's a mindset, not a department.
Part 2: Growth Loops Framework
Why Loops, Not Funnels
Funnels: Linear. Pour effort in, get results out, start over. Loops: Each cycle generates fuel for the next cycle.
The key shift: Move from "How do we get more users?" to "How does each user we acquire generate more users?"
Loop Types
| Loop Type | Description |
|---|---|
| Content Loops | Users create content → attracts more users → more content |
| Viral Loops | Users invite others → exponential spread |
| Sales Loops | Customers generate revenue → fund more acquisition |
Critical Patterns
| Pattern | Insight |
|---|---|
| Funnels vs Loops | Funnels are linear; loops compound |
| Paid ≠ Loop | Paid acquisition doesn't compound — it's buying users |
| Founder-Led First | Can't outsource finding growth model |
| Product Must Own Growth | Can't be marketing-only function |
| One Primary Loop | Others supplement but won't save you |
| Earned Over Paid | Invest 80%+ in earned/owned channels |
Platform Cycles
New platforms open, then close. Time your bets correctly:
- Early: High reach, low competition
- Mid: Reach peaks, competition grows
- Late: High competition, diminishing returns
Part 3: SEO × SMO × CRO Framework
SEO Checklist
Page-Level
-
<title>— unique, 50-60 chars, primary keyword -
<meta name="description">— 150-160 chars -
<link rel="canonical">— self-referencing - Single
<h1>with primary keyword - Primary keyword in first 100 words
- Descriptive
alttext on all images - Internal links to related pages
Site-Level
-
robots.txtnot blocking important resources -
sitemap.xmlup to date - HTTPS everywhere; mobile-friendly
- Core Web Vitals passing (LCP < 2.5s, CLS < 0.1, INP < 200ms)
OGP / Twitter Cards
<meta property="og:type" content="website">
<meta property="og:title" content="Page Title">
<meta property="og:description" content="Description">
<meta property="og:image" content="https://example.com/og-image.png">
<meta property="twitter:card" content="summary_large_image">
CRO Core
| Pillar | Goal | Key Metrics |
|---|---|---|
| SEO | Be found | Organic traffic, rankings |
| SMO | Be shared | Social CTR, shares |
| CRO | Convert | Signup rate, completion |
Part 4: Growth Models
The LTV Equation
LTV = (Average Revenue Per Customer × Average Customer Lifespan) - CAC
Unit Economics
- LTV:CAC ratio: 3:1 minimum for sustainable growth
- Payback period: < 12 months preferred
- CAC: Cost to acquire a customer
- ARPU: Average revenue per user
AARRR Framework
| Metric | Definition |
|---|---|
| Acquisition | Users come from |
| Activation | First meaningful use |
| Retention | Users come back |
| Referral | Users invite others |
| Revenue | Users pay |
Part 5: Network Effects
Types of Network Effects
| Type | Description |
|---|---|
| Direct | More users → more value (social networks) |
| Indirect | More users → more options → more value (marketplaces) |
| Two-sided | Supply and demand sides benefit (platforms) |
| Data | More data → better product → more users |
Building Network Effects
- Cross-side presence: Ensure both sides of marketplace exist
- Liquidity thresholds: Hit critical mass in each segment
- Switching costs: Users invest in platform
- Platform stickiness: Integration with workflows
Part 6: Product-Led Growth (PLG)
PLG Core Principles
- Product as the main driver of acquisition
- Free trials and freemium models
- In-product virality
- Self-serve onboarding
- Usage-based expansion
PLG Metrics
| Metric | Target |
|---|---|
| Activation rate | > 40% |
| Time to value | < 5 minutes |
| Weekly active ratio | > 20% |
| Expansion revenue | > 20% of total |
Part 7: Growth Experimentation
ICE Framework
| Factor | Score (1-10) |
|---|---|
| Impact | Could this double growth? |
| Confidence | How sure will this work? |
| Ease | How easy to implement? |
Test Execution
- Document hypothesis clearly
- Define primary and guardrail metrics
- Calculate required sample size
- Wait for statistical significance (95%)
- Run full business cycle (1-2 weeks minimum)
What NOT to Test
- Button colors before understanding objections
- Copying competitors blindly
- Optimizing without funnel context
Part 8: Growth Team & Timing
When to Hire Growth
| Stage | Growth Focus |
|---|---|
| Pre-PMF | Founder-led, iterate on product |
| Finding PMF | First 100 customers, understand channels |
| Validated PMF | First growth hire, build experiments |
| Scaling | Full growth team, channel expansion |
Growth Team Structure
- Individual Contributor: Run experiments
- Growth Manager: Prioritize and coordinate
- Growth Lead: Strategy and team management
Part 9: Key Frameworks Summary
Andrew Chen's Wisdom
- Marketplace dynamics
- Network effects as moat
- Platform distribution
- Cold start problem
Brian Balfour's Frameworks
- Growth loops methodology
- Platform cycles
- Paid ≠ loop insight
Casey Winters' Playbooks
- Kindle before fire (non-scalable → scalable)
- Product-led sales
- PQA > PQL
Common Mistakes
- Premature scaling — Growth before PMF burns cash
- Acquisition without retention — Leaky bucket
- Chasing channels — Without understanding loops
- Vanity metrics — Focus on leading indicators
- One-hit wonders — Not building compounding systems
Related Skills
- product-market-fit-analysis: For PMF assessment
- conversion-rate-optimization: For CRO implementation
- customer-success-and-retention: For retention strategy
- ab-test-setup: For growth experiments
How to use growth-strategy 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 growth-strategy
Execute installation command
Execute the skills CLI command in your project's root directory to begin installation:
The skills CLI fetches growth-strategy from GitHub repository manojbajaj95/claude-gtm-plugin 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 growth-strategy. Access the skill through slash commands (e.g., /growth-strategy) 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▌
User Story & Requirements Generation
Create detailed user stories, acceptance criteria, and feature specs
Example
Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios
Reduce spec writing time by 50%, ensure comprehensive coverage
Competitive Analysis
Research competitors, compare features, identify gaps
Example
Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities
Complete competitive research in 2 hours instead of 2 days
Roadmap Prioritization
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
Make data-driven prioritization decisions faster
Stakeholder Communication
Draft PRDs, status updates, and stakeholder presentations
Example
Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement
Save 3-5 hours/week on communication overhead
Implementation Guide▌
Prerequisites
- ›Claude Desktop or compatible AI client
- ›Access to product documentation and roadmap tools (Jira, Notion, etc.)
- ›Understanding of product management frameworks (RICE, Jobs-to-be-Done, etc.)
- ›Stakeholder contact information and communication channels
Time Estimate
30-60 minutes to see productivity improvements
Installation Steps
- 1.Install product management skill
- 2.Start with user story generation for known feature
- 3.Progress to competitive analysis: research 2-3 competitors
- 4.Use for roadmap prioritization: apply RICE/ICE scoring
- 5.Draft stakeholder communications and refine based on feedback
- 6.Build template library for recurring PM tasks
- 7.Share effective prompts with product team
Common Pitfalls
- ⚠Not validating competitive research—verify facts before sharing
- ⚠Accepting user stories without involving engineering team
- ⚠Over-relying on frameworks without qualitative judgment
- ⚠Not customizing outputs to company culture and communication style
- ⚠Skipping stakeholder validation of generated requirements
Best Practices▌
✓ Do
- +Validate research and competitive analysis with real data
- +Collaborate with engineering when generating technical requirements
- +Customize frameworks and templates to your company context
- +Use skill for first drafts, refine with stakeholder input
- +Document successful prompt patterns for PM tasks
- +Combine AI efficiency with human judgment and intuition
✗ Don't
- −Don't publish competitive analysis without fact-checking
- −Don't finalize user stories without engineering review
- −Don't make prioritization decisions solely on AI scoring
- −Don't skip customer validation of generated requirements
- −Don't ignore company-specific context and culture
💡 Pro Tips
- ★Provide context: company goals, constraints, customer feedback
- ★Ask for alternatives: 'Show 3 ways to prioritize this roadmap'
- ★Request stakeholder-specific formatting: 'Executive summary vs. engineering spec'
- ★Use skill for 70% generation + 30% customization to company needs
When to Use This▌
✓ Use When
Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.
✗ Avoid When
Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.
Learning Path▌
- 1Basic: user stories, feature specs, status updates
- 2Intermediate: competitive analysis, prioritization frameworks, PRDs
- 3Advanced: product strategy, go-to-market planning, OKR setting
- 4Expert: product vision, market positioning, business model innovation
Discussion
Product Hunt–style comments (not star reviews)- No comments yet — start the thread.
Ratings
4.6★★★★★30 reviews- ★★★★★Chaitanya Patil· Dec 24, 2024
growth-strategy has been reliable in day-to-day use. Documentation quality is above average for community skills.
- ★★★★★Kwame Gonzalez· Dec 20, 2024
Keeps context tight: growth-strategy is the kind of skill you can hand to a new teammate without a long onboarding doc.
- ★★★★★Mia Taylor· Dec 4, 2024
We added growth-strategy from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
- ★★★★★Naina Chawla· Nov 23, 2024
Useful defaults in growth-strategy — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
- ★★★★★Piyush G· Nov 15, 2024
Solid pick for teams standardizing on skills: growth-strategy is focused, and the summary matches what you get after install.
- ★★★★★Kaira Iyer· Nov 11, 2024
growth-strategy is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
- ★★★★★Charlotte Kim· Oct 14, 2024
growth-strategy has been reliable in day-to-day use. Documentation quality is above average for community skills.
- ★★★★★Shikha Mishra· Oct 6, 2024
We added growth-strategy from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
- ★★★★★William Iyer· Oct 2, 2024
growth-strategy fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
- ★★★★★Mia Robinson· Sep 21, 2024
Keeps context tight: growth-strategy is the kind of skill you can hand to a new teammate without a long onboarding doc.
showing 1-10 of 30