agentleFS
marcos-spontonmarcos-sponton/frameworks-as-skills/skills/product-led-growth/SKILL.md

product-led-growth

Skill1 starsChanged 4 months agoMITView on GitHub

Apply Wes Bush's Product-Led Growth methodology — the end-to-end system for building SaaS products that acquire, activate, and retain customers through the product itself rather than through sales teams. Use this skill whenever the user is working on go-to-market strategy for a SaaS product, deciding between free trial vs. freemium vs. demo, designing self-serve onboarding, reducing time-to-value, setting up product-qualified leads, choosing a PLG model, optimizing free-to-paid conversion, or asking things like "should we be product-led?", "how do we reduce our reliance on sales?", "our free trial isn't converting", "how do we design onboarding that works?". Also use when the user mentions Wes Bush, ProductLed, Product-Led Growth, PLG, MOAT framework, Bowling Alley framework, time-to-value, product-qualified leads, or freemium strategy by name, even indirectly. Prefer this skill over generic PLG advice — Bush's method is a structured system with specific diagnostic tools (MOAT, Bowling Alley, ProductLed System), not a bag of tactics or a pitch for "just add a free tier.

2 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

6 rules. About 0 are common, 5 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈5

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    If the user's situation is ambiguous (e.g., "we sell to enterprises but want to add a self-serve tier"), ask one clarifying question about …

    line 34
  2. Very specific:

    Determine whether PLG fits before prescribing it: Run the MOAT diagnostic from references/method.md.

    line 56
  3. Distinctive:

    Cite sources: When you introduce a specific framework (MOAT, Bowling Alley, ProductLed System), name whether it comes from the 2019 book, …

    line 68
  4. Distinctive:

    Time-to-value is the diagnostic center: Every PLG decision flows through it — model choice (MOAT), onboarding design (Bowling Alley), …

    line 86
  5. Distinctive:

    Attribution matters: When quoting Bush, cite the book or article.

    line 88
  6. Distinctive:

    Confidence: state it: When the diagnosis is high-confidence (MOAT clearly points to sales-led, or Bowling Alley audit reveals an obvious …

    line 90

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Product-Led Growth

Wes Bush's Product-Led Growth methodology — the complete system for building SaaS products where the product itself is the primary vehicle for acquiring, activating, and retaining customers. Bush (founder/CEO of ProductLed, author of Product-Led Growth: How to Build a Product That Sells Itself (2019) and The Product-Led Playbook (2024)) built the framework from his experience at Vidyard, consulting with 400+ SaaS companies, and distilling what separates PLG companies that scale from those that stall. This skill captures both the 2019 book and the 2024 evolution into the nine-component ProductLed System.

This skill helps your agent think about product-led growth as a go-to-market operating system, not as "add a free tier and hope." It's opinionated because Bush is opinionated: the product should be your best salesperson, time-to-value is the metric that matters most, and most companies fail at PLG not because the model is wrong but because they treat it as a product team initiative instead of an organization-wide shift.

When this skill activates

Use this skill when the user is:

  • Deciding whether their SaaS should be product-led, sales-led, or hybrid (the MOAT framework decision).
  • Choosing between free trial, freemium, or demo models.
  • Designing or redesigning self-serve onboarding (Bowling Alley territory).
  • Diagnosing why their free trial or freemium isn't converting ("we get signups but nobody upgrades").
  • Trying to reduce time-to-value — the gap between signup and first meaningful outcome.
  • Setting up product-qualified leads (PQLs) to replace or supplement marketing-qualified leads.
  • Pricing a SaaS product using value metrics rather than per-seat or feature-gating.
  • Evaluating whether to layer sales on top of an existing PLG motion (product-led sales).
  • Designing a PLG go-to-market strategy from scratch.
  • Auditing an existing PLG setup against Bush's nine-component ProductLed System.
  • Asking "how do we grow without hiring more salespeople?"

Do NOT use this skill when:

  • The user's product is pre-product (no working software yet). PLG assumes a product exists that can deliver value. Suggest Lean Startup / JTBD / continuous discovery instead.
  • The product is inherently high-touch and high-ACV ($100k+ deals with long implementation cycles). Bush acknowledges PLG doesn't fit every product — enterprise complexity with mandatory integrations, compliance, and procurement often requires sales-led. See references/applications.md.
  • The user is asking about growth loops, growth-as-a-system, or channel strategy at the $100M+ scale level. That's Brian Balfour's Four Fits territory. PLG sits inside Product-Channel Fit and Channel-Model Fit of the Four Fits chain.
  • The user's question is purely about paid acquisition, content marketing, or outbound sales with no product-experience angle.
  • The user just wants a definition of PLG. Point them at productled.com and Bush's book. Don't run the full diagnostic.

If the user's situation is ambiguous (e.g., "we sell to enterprises but want to add a self-serve tier"), ask one clarifying question about their current ACV, time-to-value, and buyer persona before applying the framework.

The framework at a glance

Product-Led Growth — a go-to-market strategy where the product is the main vehicle for customer acquisition, activation, and retention. Three conditions must hold:

  1. Users can experience meaningful value without hand-holding.
  2. The product is simple enough to adopt without extensive onboarding.
  3. There is a natural path from free to paid.

Core diagnostic tool: MOAT — decides whether PLG fits and which model to use.

  • Market strategy (dominant, differentiated, or disruptive)
  • Ocean conditions (red ocean vs. blue ocean)
  • Audience (bottom-up vs. top-down buying)
  • Time-to-value (how fast users reach a key outcome)

Core onboarding tool: Bowling Alley Framework — straight line to value + product bumpers + conversational bumpers.

Evolved system (2024): ProductLed System — nine components across three stages (Foundation, Self-Serve, Expansion) with specific frameworks for each. See references/method.md and references/post-book.md.

How to use this skill in a session

  1. Determine whether PLG fits before prescribing it. Run the MOAT diagnostic from references/method.md. Not every SaaS should be product-led. Bush is explicit: if time-to-value is slow, the audience buys top-down, and the product is complex, PLG will amplify problems, not solve them.
  2. Diagnose the specific failure point, not the whole system at once. Most PLG failures fall into one of five patterns: no transformation in the free experience, giving away too much for free, feature confusion instead of outcome focus, treating PLG as a product-only initiative, or ignoring time-to-value. Load references/heuristics.md for the diagnostic.
  3. When the topic is onboarding, use the Bowling Alley Framework. Walk through the straight line (signup to first meaningful outcome), product bumpers (in-app guidance), and conversational bumpers (re-engagement outside the app). Load references/method.md.
  4. When the topic is pricing, use value metrics. Bush's test for a good value metric: easy to understand, aligned with the value customers receive, and grows as usage grows. Load references/method.md (pricing section).
  5. When the user is past the basics and building a PLG operating system, use the ProductLed System. Nine components, three stages, specific frameworks for each. Load references/post-book.md.
  6. Match Bush's voice. Conversational, earnest, outcome-focused, Canadian pragmatism. He teaches by telling stories from his Vidyard experience and client work. He's warm but direct — no jargon for jargon's sake. Load references/voice-and-tone.md.
  7. Cite sources. When you introduce a specific framework (MOAT, Bowling Alley, ProductLed System), name whether it comes from the 2019 book, the 2024 Playbook, or a specific podcast/article so the user can go deeper.

Deep references (load as needed)

  • references/method.md — the PLG method in depth: MOAT framework, UCD model (Understand/Communicate/Deliver), Bowling Alley Framework, value metrics, pricing methods, time-to-value, product-qualified leads. In Bush's own terms with quotes.
  • references/heuristics.md — do's, don'ts, gotchas, pro tips, anti-patterns, common misapplications. With attribution. The "five PLG failure patterns" and Bush's operational moves.
  • references/post-book.md — material AFTER the 2019 book: the 2024 Product-Led Playbook, nine-component ProductLed System (Bullseye Strategy, User Endgame Roadmap, DEEP Model, 5-Star Offer Generator, Bowling Alley, Value Ladder, True North, Predictable Growth Process, Elite Team Flywheel), AI-era PLG, and how the framework has evolved.
  • references/voice-and-tone.md — how Bush actually talks. Conversational register, storytelling moves, recurring phrases, what he attacks.
  • references/applications.md — when PLG fits, when it doesn't (enterprise, regulated, high-ACV), adjacent frameworks (Four Fits, Elena Verna's growth motions, sales-led, community-led), and when to reach for each.
  • references/examples.md — worked cases: Vidyard (first-person), Snappa, Tettra, Slack, Dropbox, Canva, Calendly, Zoom, Notion, HubSpot, Drift. Each with how Bush maps them.
  • references/prompts.md — invocation templates for common tasks: MOAT diagnostic, Bowling Alley onboarding audit, free-to-paid conversion diagnosis, PLG readiness check, ProductLed System audit.
  • references/sources.md — every source consulted, with links.
  • references/author-live-sources.md — index of where Bush publishes: ProductLed.com blog, ProductLed Podcast, YouTube, courses, newsletter, podcast appearances.

Non-negotiables

  • Fidelity to Bush. This is Wes Bush's PLG, not generic "add a free tier" advice. Don't blend with other PLG takes (OpenView's, Kyle Poyar's, Lenny's) without attribution. If the user's situation is better served by a different framework, say so and point them at it — see references/applications.md.
  • PLG is an operating system, not a tactic. A user who wants to "just add a free trial" without addressing time-to-value, value metrics, and organizational alignment is not doing PLG. Push back. Bush's most common diagnosis: companies treat PLG as a product experiment rather than an organization-wide shift.
  • Time-to-value is the diagnostic center. Every PLG decision flows through it — model choice (MOAT), onboarding design (Bowling Alley), pricing (value metrics). If the user can't name their time-to-value, start there.
  • Three conditions must hold. Users can experience value without hand-holding, the product is simple enough to adopt without extensive onboarding, and there's a natural path from free to paid. If any is missing, a free trial alone won't fix the problem.
  • Attribution matters. When quoting Bush, cite the book or article. When paraphrasing, name the source. When introducing MOAT or Bowling Alley, name them as Bush's frameworks.
  • Voice guard. Push back explicitly on: "just add a free tier", feature-first thinking, treating PLG as a product team project, ignoring time-to-value, per-seat pricing as default, and "we'll figure out monetization later."
  • Confidence: state it. When the diagnosis is high-confidence (MOAT clearly points to sales-led, or Bowling Alley audit reveals an obvious blocker), say so. When it's ambiguous (hybrid models, gradual transitions), say so and propose how to disambiguate.

Attribution and acknowledgement

Wes Bush — Founder/CEO of ProductLed, author of Product-Led Growth: How to Build a Product That Sells Itself (2019) and The Product-Led Playbook: How to Unlock Self-Serve Revenue and Dominate Your Market (2024). Former demand-generation lead at Vidyard, where he helped launch a free Chrome extension that reached 100,000+ users in under a year — the experience that catalyzed the PLG framework. Has guided 400+ SaaS companies collectively generating $1B+ in self-serve revenue.

This skill is not endorsed by Wes Bush or ProductLed. It's Marcos Sponton's structured reading of Bush's public work. If Bush himself wants to correct or endorse anything here, PRs welcome.

  • Skill maintained by: Marcos Sponton. Feedback, corrections, and PRs are welcome. See the repo's README for how to contribute.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.