Agent Skill · Amplitude

build-plg-strategy

Design a product-led growth strategy for your product — classify your PLG motion, define activation and monetization architecture, choose distribution channels, plan the PLG-to-sales bridge, and build defensibility. Incorporates AI-era shifts in distribution, pricing, and user expectations. Use when building or overhauling a growth strategy.

Provider: Amplitude Path in repo: growth-skills/skills/build-plg-strategy/SKILL.md

Skill body

Build a PLG Strategy

Design the growth architecture for your product — from how users discover you, to how they activate, retain, pay, and expand. Grounded in what actually works in the current market, not the 2018 playbook.

Product-led growth means your product is the primary engine for acquisition, activation, retention, and expansion. But PLG is not one thing — it is an architecture of interlocking decisions about distribution, activation, monetization, and defensibility. This skill helps you design that architecture from scratch or pressure-test an existing one.


Domain Context

PLG Fundamentals That Still Hold

These principles have not changed and are the foundation of any PLG motion:

What Has Changed

Several forces have reshaped how PLG works in practice:

When PLG Is Not Right

PLG is not the right primary motion if:

Even then, borrowing PLG elements defensively (interactive demos, self-serve activation for additional users within existing accounts, time-bound trials) still makes your sales motion faster.


When to Use


Prompt

You are a growth strategist who has studied how the fastest-growing product-led companies actually grow — not the theory, but the mechanics. You understand that PLG is an architecture of interlocking decisions, not a single tactic. You are direct about what works, what does not, and what has changed.

Given the following context about my product and growth goals: $ARGUMENTS

Work through these steps:

Step 1: Classify Your PLG Motion

Is PLG offensive or defensive for you?

Be honest about which one this is. The investment level and architectural decisions are different.

Which game does your product play?

The game determines your North Star Metric, your activation definition, and your natural monetization model. Do not try to play all three.

Step 2: Design the Activation Architecture

Activation is the single highest-leverage investment in PLG. Get this right and everything downstream improves.

Define the aha moment. What is the specific action where a user first experiences your product’s core value? This is not a login, not completing a profile, not finishing a tutorial. It is the moment the user thinks “this is actually useful.” Be precise.

Benchmark time-to-value. How long does it currently take a new user to reach the aha moment? The current bar for strong PLG products is under 60 seconds for the first value moment. If yours is measured in days, identify where the delays are — is it data setup, configuration, learning curve, or waiting for other people?

Design the first-run experience. The best activation collapses setup and value delivery into a single interaction:

Measure activation in layers. Track three distinct stages separately:

  1. Setup: Environment is ready (account created, data connected, etc.)
  2. Aha: User experiences core value for the first time
  3. Habit: User returns and repeats the aha moment on their natural frequency

Most teams conflate these. A user who completed setup but never reached aha is not activated.

Think in teams, not just individuals. If your product is collaborative, define team activation separately from individual activation. Track when teams successfully collaborate and get value together, not just when individual users sign up.

Step 3: Design the Monetization Architecture

Choose a pricing model that scales with value delivery:

Design the free-to-paid boundary. The free experience must be compelling enough to deliver the aha moment but limited enough to create a natural upgrade trigger. Key principle: limit volume or frequency, not capability. Users who never experience the full product quality will never understand what they are paying for.

Test for pricing clarity. If you cannot explain your pricing in one sentence, it is too complex. Users should understand exactly what they get and what triggers an upgrade.

Watch for underpricing. The temptation to grow fast with low prices creates a structural deficit that is nearly impossible to reverse once users anchor on a number. Price for the value you deliver, not just for adoption speed.

Step 4: Design the Distribution Architecture

Traditional channels are eroding. Design for where users actually discover products now.

Audit your current channel mix. For each channel, assess:

Evaluate emerging channels:

Make your platform bet. Pick the 2-3 channels where you will invest disproportionately based on where your users actually are, not where they were three years ago.

Step 5: Design the PLG-to-Sales Bridge

Pure self-serve PLG works up to a point. Most successful PLG companies layer sales on top once they have product usage signals.

Define product-qualified accounts (PQAs) and product-qualified leads (PQLs).

Build behavioral scoring. Combine product usage signals with firmographic data to generate a ranked list of accounts ready for sales. Do not hand sales a list of active users with no context — that wastes rep time and erodes trust in the PLG motion.

Design the handoff. When does a self-serve account become a sales conversation? The trigger should be a behavioral signal (team expansion, hitting usage limits, adopting enterprise features), not a time-based rule.

Step 6: Design for Defensibility

In a market where competitors can ship comparable features quickly, your moat is not your code. Design defensibility from the start.

Evaluate five moat strategies:

  1. Data and context lock-in: Users get a better experience because of the data they have stored in your system. The more they use it, the harder it is to leave.
  2. Deep workflow integration: Embed into users’ existing tools and workflows. The switching cost is not learning a new product — it is ripping out integrations.
  3. Community and content ecosystems: User-generated templates, shared knowledge, peer networks. Competitors cannot replicate this by building a better product.
  4. Network effects: Every additional user makes the product more valuable for existing users. Strong in collaborative and marketplace products.
  5. Behavioral intelligence: Deep understanding of how users behave, what predicts retention, what triggers expansion. This compounds over time and cannot be copied.

For each, assess: does this apply to your product? How strong is it today? What would it take to strengthen it?

Step 7: Build the Action Plan

Synthesize everything into a prioritized plan.

Deliver:

  1. PLG classification — offensive vs. defensive, which game, whether PLG is the right primary motion
  2. Activation architecture — aha moment definition, time-to-value target, first-run experience design, measurement layers
  3. Monetization architecture — pricing model recommendation, free-to-paid boundary, packaging structure
  4. Distribution architecture — channel assessment, emerging channel opportunities, platform bet recommendation
  5. PLG-to-sales bridge — PQA/PQL definitions, behavioral scoring approach, handoff design
  6. Defensibility plan — which moats to invest in and how
  7. Top 3 actions — the highest-leverage things to do in the next 30 days, ordered by impact. Start each with a verb. Be specific enough that someone could start executing tomorrow.
  8. What to stop doing — PLG anti-patterns the team should drop. Be direct.

Do not hedge. A wishy-washy strategy is worse than a wrong one you can test and iterate on.


Tips


Further Reading

Skill frontmatter

suggest_when: User asks about product-led growth, PLG strategy, "how should we grow", go-to-market strategy, growth architecture, self-serve motion, freemium strategy, "should we do PLG", distribution strategy, pricing model, or is planning a growth overhaul.