gtm-product-led-growth
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 complexity demands human touch. Includes the parallel test where sales-led won 10x on revenue.
Profile →npx skills add github/awesome-copilot --skill gtm-product-led-growth --agent copilot
Same command for any agent — swap --agent for claude-code, codex, cursor.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# 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 + bu
- When to Use
- Core Frameworks
- 1. The PLG Reality Check (Test Before You Commit)
- 2. The Growth Equation (Map Inputs to Outputs)
- 3. Channel Economics (Kill Losers, Double Down on Winners)
- 4. Time to First Value (The Only Activation Metric)
- 5. The $5K → $50K Inflection (When PLG Breaks)
- 6. Growth Forecasting (Plan for Uncertainty)
- 7. The Playbook Documentation Habit
- Decision Trees
- Should We Build PLG or Sales-Led?
- Keep, Scale, or Kill This Channel?
- Common Mistakes
- Quick Reference
What does the gtm-product-led-growth skill do?
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 complexity demands human touch. Includes the parallel test where sales-led won 10x on revenue.
How do I install it?
Run `npx skills add github/awesome-copilot --skill gtm-product-led-growth --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From github/awesome-copilot, a repository with 37,432 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.