MR
Mayur Rathi
@github
⭐ 34.1k GitHub stars

Gtm-Product-Led-Growth

Gtm-Product-Led-Growth是一款testing方向的AI技能,核心价值是Build self-serve acquisition and expansion motions,可用于解决开发者在testing领域的实际问题,帮助用户提升效率、自动化重复任务或优化工作流。

Build self-serve acquisition and expansion motions. Use when deciding PLG vs sales-led, optimizing activation, driving freemium conversion, building growth equations, or recognizing when product compl

Last verified on: 2026-05-30
mkdir -p ./skills/gtm-product-led-growth && curl -sfL https://raw.githubusercontent.com/github/awesome-copilot/main/skills/gtm-product-led-growth/SKILL.md -o ./skills/gtm-product-led-growth/SKILL.md

Run in terminal / PowerShell. Requires curl (Unix) or PowerShell 5+ (Windows).

Skill Content

# Product-Led Growth


Build self-serve acquisition and expansion motions. But first, figure out if PLG is even the right motion for your product.


When to Use


**Triggers:**

- "Should we build PLG or sales-led?"

- "How do we drive self-serve adoption?"

- "Freemium to paid conversion isn't working"

- "Developer-led adoption strategy"

- "Which growth channels should we invest in?"

- "How do I know if PLG will work?"


**Context:**

- Developer tools and platforms

- B2B SaaS with self-serve potential

- Products where value is obvious without demo

- Bottom-up adoption motions

- Growth channel prioritization


---


Core Frameworks


1. The PLG Reality Check (Test Before You Commit)


**What I Learned Running Both Motions in Parallel:**


Classic startup debate. PLG camp: "Developers want self-serve." Sales camp: "Enterprises need hand-holding." Instead of arguing, we tested both for 6 months. Same product, two GTM motions, tracked everything.


**The Results:**


PLG: High volume, low ACV (~$5K), fast time-to-revenue, higher churn. Sales-led: Lower volume, high ACV (~$50K), slower time-to-revenue, lower churn. **Sales won 10x on dollars despite 10x less volume.**


**Why:** Product complexity + buyer seniority = sales-led wins. The product required integration with existing infrastructure, change management across teams, and multi-stakeholder alignment. Developers loved self-serve. But they weren't the economic buyer.


**PLG works when:**

- Value is obvious in first 5 minutes

- Implementation is trivial

- Individual user gets value without team buy-in

- No procurement/legal hurdles

- Buyer = user


**Sales-led works when:**

- Product requires integration/setup

- Multiple stakeholders need alignment

- Buyer ≠ user

- Deal size justifies human touch

- Customer needs education to see value


**Before building PLG, test your motion. Don't assume PLG is better because it's trendy.** PLG is efficient at volume, but sales-led can be more profitable with complexity.


---


2. The Growth Equation (Map Inputs to Outputs)


**The Pattern:**


Growth compounds when you systematize the relationship between activities and user acquisition. Not "do more marketing" — map specific inputs to measurable outputs.


**How to Build Your Growth Equation:**


For each channel, define: Activity (input) → Traffic (output) → Conversions.


- **Organic Search:** 1 quality blog post → 400 users/month → 5% conversion = 20 new users

- **Paid Ads:** $1K spend at 8% conversion on 100K impressions = 8K clicks → conversions at X%

- **Community Events:** 1 event → 60 attendees → 35% conversion = 21 users

- **Referral:** 1 integration partner → N referred users → conversions at Y%


**Why This Matters:**


Once you validate the equation, scaling becomes math. "I need 200 more users next month" → "I need 10 more blog posts" or "I need $5K more ad spend." Without the equation, you're guessing.


**Testing the Equation:**


1. Start with hypothesis: "If I create X, it drives Y conversion"

2. Test with small sample: 1 blog post, measure actual conversion

3. Validate: Does reality match hypothesis?

4. Scale with confidence: If yes, increase input

5. Kill if not: 4 weeks of data is enough to decide


**Common Mistake:**


Guessing at conversion rates without testing. Assuming all users from the same channel are equal quality. Scaling before validating the equation.


---


3. Channel Economics (Kill Losers, Double Down on Winners)


**The Pattern:**


Every channel has economics. Without tracking them, you over-invest in losers and under-invest in winners.


**Track Per Channel:**

1. **CAC:** Total spend / new users

2. **Conversion rate:** Signups → paying

3. **Retention:** 30-day, 90-day by source

4. **LTV:** Revenue over customer lifetime, by channel

5. **Payback period:** How long to recoup CAC


**The Decision Framework:**


- CAC < (LTV × margin) → Scale aggressively

- CAC ≈ (LTV × margin) → Optimize, don't scale

- CAC > (LTV × margin) → Kill within 4 weeks


**Monthly channel revie

🎯 Best For

  • UI designers
  • Product designers
  • Claude users
  • GitHub Copilot users
  • AI users

💡 Use Cases

  • Generating component mockups
  • Creating design system tokens
  • Using Gtm-Product-Led-Growth in daily workflow
  • Automating repetitive testing tasks

📖 How to Use This Skill

  1. 1

    Install the Skill

    Copy the install command from the Terminal tab and run it. The SKILL.md file downloads to your local skills directory.

  2. 2

    Load into Your AI Assistant

    Open Claude or GitHub Copilot and reference the skill. Paste the SKILL.md content or use the system prompt tab.

  3. 3

    Apply Gtm-Product-Led-Growth to Your Work

    Provide context for your task — paste source material, describe your audience, or share existing work to guide the AI.

  4. 4

    Review and Refine

    Edit the AI output for accuracy, tone, and completeness. Add human insight where the AI lacks context.

❓ Frequently Asked Questions

Does this work with Figma?

Some design skills integrate with Figma plugins. Check the Works With section for supported tools.

How do I install Gtm-Product-Led-Growth?

Copy the install command from the Terminal tab and run it. The skill downloads to ./skills/gtm-product-led-growth/SKILL.md, ready to use.

Can I customize this skill for my team?

Absolutely. Edit the SKILL.md file to add team-specific instructions, examples, or workflows.

⚠️ Common Mistakes to Avoid

Skipping usability testing

AI-generated designs should be validated with real users before development.

Not reading the full skill

Skills contain important context and edge cases beyond the quick start.

🔗 Related Skills