product-led-growth
Use when asked about "product-led growth", "PLG strategy", "self-serve growth", "freemium model", "free trial design", "product-led sales", "PQL", or "bottoms-up growth". Helps design and optimize product-led growth motions where the product drives acquisition, activation, and monetization. Based on frameworks from Elena Verna and Hila Qu.
What this skill does
## Domain Context This skill implements a proven product management framework. The approach combines best practices from industry leaders and is designed for practical application in day-to-day PM work. ## Input Requirements - Context about your product, feature, or problem - Relevant data, research, or constraints (recommended but optional) - Clear articulation of what you're trying to achieve # Product-Led Growth (PLG) ## What It Is Product-Led Growth is a go-to-market strategy where the product itself drives acquisition, activation, retention, and monetization. Instead of relying on sales to close deals before users can try the product, PLG lets users experience value first and buy later. The core insight: **In PLG, the product does the selling.** Users sign up, experience value through self-serve, and either convert themselves or become qualified leads for sales. PLG is fundamentally **Data-Led Growth (DLG)**. When you give away a free product, you get two things in exchange: broader reach (lower barrier to entry) and usage data that tells you which features correlate with conversion and retention. Without this data foundation, you're giving away your product for nothing. ## When to Use It Use PLG frameworks when you need to: - **Design a freemium or free trial model** for a B2B SaaS product - **Add self-serve to a sales-led product** to expand reach - **Optimize conversion** from free to paid users - **Define product-qualified leads (PQLs)** for your sales team - **Reduce customer acquisition cost** through self-serve - **Build a hybrid PLG + sales motion** (product-led sales) - **Diagnose why free users aren't converting** to paid ## When Not to Use It - **Highly complex products requiring customization** - **Very small addressable market** - **No individual use case exists** - **You lack data infrastructure** - **You want instant revenue impact** — PLG takes 12+ months ## Resources **People to follow:** - Elena Verna (Substack, LinkedIn) — PLG, PLS, growth strategy - Hila Qu — PLG implementation, activation, growth teams **Tools mentioned:** - Product analytics: Amplitude, Mixpanel, PostHog - Experimentation: Optimizely, Amplitude Experiment, Eppo - PLS platforms: Pocus, Endgame, Correlated ## Further Reading - [Product Led Growth](https://www.productcompass.pm/p/product-led-growth)
Related in Ads & Marketing
ads
IncludedMulti-platform paid advertising audit and optimization skill. Analyzes Google, Meta, YouTube, LinkedIn, TikTok, Microsoft, and Apple Ads. 250+ checks with scoring, parallel agents, industry templates, and AI creative generation.
banana
IncludedAI image generation Creative Director powered by Google Gemini Nano Banana models. Use this skill for ANY request involving image creation, editing, visual asset production, or creative direction. Triggers on: generate an image, create a photo, edit this picture, design a logo, make a banner, visual for my anything, and all /banana commands. Handles text-to-image, image editing, multi-turn creative sessions, batch workflows, and brand presets.
rpg-migration-analyzer
IncludedAnalyzes legacy RPG (Report Program Generator) programs from AS/400 and IBM i systems for migration to modern Java applications. Extracts business logic from RPG III/IV/ILE source code, identifies data structures (D-specs), file operations (F-specs), program dependencies (CALLB/CALLP), and converts RPG constructs to Java equivalents. Generates migration reports, complexity estimates, and Java implementation strategies with POJO classes, JPA entities, and service methods. Use when modernizing AS/400 or IBM i legacy systems, analyzing RPG source files (.rpg, .rpgle, .RPGLE), converting RPG to Java, mapping data specifications to Java classes, planning legacy system migration, or when user mentions RPG analysis, Report Program Generator, RPG III/IV/ILE, AS/400 modernization, IBM i migration, packed decimal conversion, or mainframe application rewrite.
brand-library-architect
IncludedBuild a complete brand library for a product — visual asset render pipeline, brand documentation set (BRAND, COPY, MANIFESTO, BIOS, FAQ, GLOSSARY, TONE, PRICING), open-source convention files (README, CONTRIBUTING, SECURITY, CODE_OF_CONDUCT), and a self-contained press kit. This skill should be used when the user asks to "build a brand library / brand kit / press kit / brand assets" for a product, "set up a brand library workflow," "create a positioning manifesto plus visual identity," or any combination of brand documentation + visual asset pipeline. Apply phase-by-phase or run end-to-end. Templates are product-agnostic and use {{TOKEN}} placeholders the skill prompts the user to fill.
writing-tech-post
IncludedAuthors engineering blog posts end-to-end: launch deep-dives, incident postmortems, architecture migrations, performance case studies, tutorials, AI/agent system writeups, security disclosures, and research-to-product translations. Picks the correct archetype, plans the abstraction ladder, enforces an evidence cadence (diagrams, benchmarks, profiles, traces, code, ablations), tunes voice against publisher house styles (Datadog, Vercel, GitHub, AWS, Meta, Cloudflare, Jane Street), and runs a pre-publish gate for narrative momentum and disclosure ethics. Use when drafting a new engineering post, restructuring a draft that feels flat, deciding which evidence form belongs where, validating that depth and product context are balanced, or preparing a postmortem, migration, or performance narrative for external publication. Do not use for API reference documentation, README authoring, marketing copy, release notes, generic SEO content, ghost-written executive thought leadership, or non-engineering long-form essays.
blog-google
IncludedGoogle API integration for blog performance: PageSpeed Insights, CrUX Core Web Vitals with 25-week history, Search Console performance, URL Inspection, Indexing API, GA4 organic traffic, NLP entity analysis for E-E-A-T, YouTube video search for embedding, and Google Ads Keyword Planner. Progressive feature availability based on credential tier (API key, OAuth/service account, GA4, Ads). Shares config with claude-seo at ~/.config/claude-seo/google-api.json. Use when user says "google data", "page speed", "core web vitals", "search console", "indexation", "GA4", "keyword research", "nlp entities", "blog performance", "youtube search", "google api setup".