playbook step_05

Product-Led Growth: Letting the Product Do More of the Selling

TryValueHabitUpgradeShare

Product-led growth (PLG) is a go-to-market approach in which the product itself is the main vehicle for acquiring, activating and expanding customers. Instead of requiring a sales conversation before anyone can try the software, PLG companies let users experience value first, then pay as they get more out of it. It is not a fit for every product, but its principles improve almost any self-serve experience.

Designer sketching a user interface wireframe on an office whiteboard
Figure: In product-led growth, the onboarding flow is part of the marketing.

Is PLG right for your product?

PLG tends to work well when users can reach value on their own in a short time, when the person who uses the product can also influence the buying decision, and when the product benefits from more people using it. It is harder when setup requires heavy integration work, when buyers and users are completely separate, or when each deal requires significant customization.

Many companies use a hybrid: self-serve for individuals and small teams, with sales assistance for larger accounts. The playbook below applies to the self-serve part either way.

Step 1: Choose an entry model

  • Free trial: full or near-full access for a limited period. Encourages focused evaluation but adds time pressure.
  • Freemium: a permanently free plan with limits on usage, features or seats. Builds a large user base; requires careful limits so that growing teams naturally need to upgrade.
  • Reverse trial: users start with premium features for a limited time, then move to a free plan unless they upgrade. Shows the full value while keeping a free path.
  • Usage-based entry: users pay as they consume, often with a free allowance. Common for infrastructure and API products.

Choose based on how long it takes to experience value, the cost of serving free users and how your value grows with use.

Step 2: Shrink time to value

The single most important lever in PLG is how quickly a new user experiences the product's core benefit. Map the steps from signup to that moment and challenge each one.

  1. Remove fields and steps that are not needed before first value.
  2. Offer templates, sample data or a guided setup so users see a working result immediately.
  3. Defer configuration, such as team settings and integrations, until after the first win, unless it is required for value.
  4. Detect the user's goal early with one question and route them to the relevant starting point.

Define this moment as your activation metric. Our article on activation metrics explains how to choose and validate it.

Step 3: In-product guidance

Good guidance helps users progress without getting in the way.

Checklists

A short list of the steps that lead to activation, with progress visible. Keep it to a handful of items and let users dismiss it.

Empty states

Screens with no data yet are prime real estate. Explain what will appear there and offer a one-click way to create the first item or load an example.

Contextual tips

Short hints triggered when a user reaches a relevant screen, rather than a long tour at the start that people skip.

Lifecycle messages

Email and in-app messages work together. Use the lifecycle email flows playbook to reach users who leave before finishing setup.

Step 4: Design the upgrade path

In PLG, the upgrade should feel like a natural next step rather than a wall. Good upgrade moments occur when users hit a limit that reflects real growth, such as more projects, more teammates or more usage, or when they try a feature that clearly adds value for larger teams.

  • Explain what the limit is and why it exists before users hit it.
  • When showing an upgrade prompt, explain what they get and what it costs in plain terms.
  • Let admins upgrade without contacting sales, and let non-admins request an upgrade from their admin easily.

Step 5: Product-qualified leads

A product-qualified lead (PQL) is a user or account whose product behavior suggests they are likely to benefit from a paid plan or a conversation with sales. Signals might include multiple active teammates, usage approaching limits, use of features associated with larger teams, or a company domain that matches your ideal customer profile.

pql-rule.txt
account is PQL when:
  active_users_7d   >= 3
  AND core_actions_14d >= threshold
  AND (usage > 80% of free limit OR team_feature_used)
route → in-app upgrade prompt
      → if company fits ICP: notify sales to offer help

Sales outreach to PQLs should focus on helping, such as answering questions about security reviews, billing or rollout, rather than pushing a generic demo.

Step 6: Build growth loops

PLG products often grow through usage itself: inviting teammates, sharing outputs with clients, or publishing templates. Make these actions easy and valuable. See referral loops for loop design and measurement.

Step 7: Align the team

PLG blurs the lines between marketing, product, sales and support. Shared metrics, such as activation rate, free-to-paid conversion and net revenue retention, help everyone pull in the same direction. A small cross-functional growth group that owns the self-serve journey end to end can move faster than separate teams handing off at each stage.

Common pitfalls

  • A free plan so generous that few users ever need to upgrade.
  • Limits so tight that users never experience real value.
  • Treating every signup as a sales lead, overwhelming both sales and users.
  • Neglecting onboarding after launch as features pile up.

Start with time to value. It improves conversion under any model and makes every other PLG investment more effective.

Playbook checklist

  • Entry model chosen based on time to value and cost to serve
  • Signup-to-value steps mapped and trimmed
  • Templates or sample data available on first login
  • Empty states explain what will appear and offer a first action
  • Upgrade prompts explain the limit, the benefit and the price
  • Product-qualified lead rule written down and reviewed

Related reading