product-led-growth

product-led-growth is a skill for Claude Code from beingsmit/technical-product-gtm. It costs 58 tokens per session (3,001 once invoked), scanned A, a copy of gtm-product-led-growth, MIT.

A product-growth planning framework for deciding whether users should discover and adopt a product themselves, known as product-led growth, or whether sales support is needed. It covers self-serve adoption, freemium conversion, activation, and expansion.

In plain words
What is it for?
Choosing a growth model, planning self-serve onboarding, improving activation, assessing freemium-to-paid conversion, and deciding when human sales help is needed.
Why use it?
It helps compare self-service growth with sales-led growth instead of assuming one approach fits every product. It also addresses cases where a product is too complex for users to adopt alone.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin. Also seen: positional $N argument.

Part of the technical-product-gtm plugin — 11 skills shipped together

Good fit Choosing a growth model, planning self-serve onboarding, improving activation, assessing freemium-to-paid conversion, and deciding when human sales help is needed.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/beingsmit/technical-product-gtm/product-led-growth
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add beingsmit/technical-product-gtm --skill product-led-growth
Clone the repo
git clone --depth 1 https://github.com/beingsmit/technical-product-gtm

Made for: Claude Code.

Or install technical-product-gtm, the plugin that ships this one along with the rest of its 11 skills.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for product-led-growth

README.md
[![agentmods](https://agentmods.dev/badge/skills/beingsmit/technical-product-gtm/product-led-growth/github.svg)](https://agentmods.dev/skills/beingsmit/technical-product-gtm/product-led-growth)
Your own site
<a href="https://agentmods.dev/skills/beingsmit/technical-product-gtm/product-led-growth"><img src="https://agentmods.dev/badge/skills/beingsmit/technical-product-gtm/product-led-growth/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for product-led-growth

Your own site · 80×15
<a href="https://agentmods.dev/skills/beingsmit/technical-product-gtm/product-led-growth"><img src="https://agentmods.dev/badge/skills/beingsmit/technical-product-gtm/product-led-growth.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 58 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 3,001 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin 95% copy Near-identical to another mod in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00058 $0.03001
Opus 5 $0.00029 $0.01501
Sonnet 5 $0.00012 $0.00600
Haiku 4.5 $0.00006 $0.00300

Measured 12d ago against content hash 634c44f3eb9f, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

product-led-growth scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 12d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

Origin

This is a copy

95% identical to gtm-product-led-growth — 5 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

skills/product-led-growth/SKILL.md · 341 lines

How it starts

The opening of the file, as written. The whole thing — 341 lines — stays where its author put it; the contents beside it link to each section on GitHub.

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)

Read the full file on GitHub · 341 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 12d ago First seen · 341 lines · 58 tokens per session scan A 634c44f3eb9f

Subscribe to this mod's changes

product-led-growth is a skill published in the GitHub repository beingsmit/technical-product-gtm (42 stars, last pushed 5mo ago), licensed MIT. It adds 58 tokens to every session and 3,001 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. It is 95% identical to gtm-product-led-growth, differing in 5 lines, and is treated as a copy.

Related

Other skills, from other repositories

chief-strategy-officer

Owns where the business plays and how it wins over a multi-year horizon — portfolio choices, corporate development, strategic partnerships, and planning under uncertainty. Use this for a decision about which markets or businesses to be in, whether to build, buy, or partner, how to allocate capital across business…

cbrock84/headcount · 93 tokens

seo-strategy

Audits and improves organic search performance — technical health, site architecture, internal linking, structured data, and the content decisions that determine what can rank. Use this to run an SEO audit, diagnose why pages are not ranking or were deindexed, plan a site's URL and navigation structure, add structured…

cbrock84/headcount · 74 tokens

financial-statement-analysis

Reads a set of financial statements and establishes what changed and why — fluctuation analysis against prior period and against budget, profitability, liquidity, solvency and efficiency ratios, benchmarking, and the non-GAAP measures presented alongside them. Use this to interpret results, review a counterparty's or…

cbrock84/headcount · 93 tokens

service-desk

Runs the IT service desk — intake, triage, prioritization, escalation, knowledge, and the metrics that improve service rather than distort it. Use this to set up or fix a service desk, design ticket priority and escalation, reduce repeat contacts, structure a knowledge base, or work out why a desk hitting its targets…

cbrock84/headcount · 73 tokens

youtube-producer

Plans, packages, and scripts long-form video for retention and channel growth — idea selection, titles and thumbnails, script structure, and diagnosing why a video or channel underperforms. Use this for video ideas, packaging, scripting, a retention teardown, or channel strategy — including when someone describes a…

cbrock84/headcount · 86 tokens

estimating-and-contingency

Produces a cost or effort estimate someone can defend — decomposing the work, choosing between analogous, parametric and bottom-up methods, documenting the basis and its assumptions, expressing confidence as a range, and sizing contingency and management reserve separately. Use this to build an estimate, challenge one…

cbrock84/headcount · 87 tokens