Five steps to starting your product-led growth motion, part 2

Part two of a PLG guide by Hila Qu covers the fourth and fifth steps of launching a product-led growth motion: setting up infrastructure and tooling, then building the team. The core argument is that PLG is fundamentally data-led, so companies must first invest in product analytics, a unified customer data layer, an experimentation platform, and lifecycle messaging before adding specialized tools. The article then lays out how a PLG team typically evolves from a small pilot through a formal org to a scaled, multi-squad structure, noting that no universal setup exists. It matters because it gives B2B product and growth leaders a practical sequence for building and staffing a self-serve funnel without over-investing early.

01Key takeaways

• Treat data infrastructure as non-negotiable, since PLG without product analytics means flying blind on how free users behave.
• Connect product usage, marketing, sales, and firmographic data into one central database so teams can act on it.
• Buy an experimentation platform rather than building one, unless you have the data science and engineering capacity to maintain it.
• Use lifecycle tools to trigger in-app, email, and SMS messages based on actual product usage.
• Start with a small dedicated growth team or cross-functional tiger team, and expand headcount only after PLG proves a good fit.
• Decide the head of growth's reporting line deliberately, weighing product leadership against revenue leadership based on how aligned incentives are with sales.

02Key sections

PLG infrastructure

Describes three must-have foundations: product analytics with proper instrumentation, a customer 360 database with two-way data flows to sales and marketing tools, and an experimentation platform. It warns against building experimentation tooling in-house when buying is more practical.

Lifecycle marketing and the PLG tool stack

Explains that PLG lifecycle messaging uses in-app, push, and SMS channels to drive usage rather than just nurture leads. It then frames the optional tool stack as category-level solutions to add once core infrastructure is in place.

Beginning phase team setup

Presents two starting options, a dedicated growth team or a cross-functional tiger team, depending on whether the initiative is focused or spans many functions. The goal at this stage is to prove PLG fits the business.

Growing and scaling phases

Shows how the team formalizes into a product growth team aligned with sales and marketing, with the head of growth reporting either to a CPO or a CRO/GTM leader. As it scales, subteams organize around funnel stages and infrastructure, each with a PM, analyst, engineer, and designer.

Reporting structure tradeoffs

Compares placing growth under product versus under revenue leadership, noting that the revenue-side model reduces conflict over quotas and commissions. The choice depends on how established the sales organization is.

03From the post

“If you’re just joining us, make sure to read part one of this series, where I cover the first three steps of starting your PLG motion: - Step 1: Map your funnel - Step 2: Pick a starting point - Step 3: Anticipate the most common pitfalls Now let’s continue with step 4. You can find on LinkedIn, Twitter, and Substack. Make sure to check out the Reforge courses she teaches, Advanced Growth Strategy and Experimentation & Testing, and sign up here to get updates on Reforge’s new PLG program, which launches in fall 2023. Step 4. Set up the infrastructure PLG tooling is a fast-evolving space. At a high level, there are two categories to consider: 1. PLG infrastructure 2. PLG tool stack The infrastructure tools are must-haves for running a PLG motion, while the tool stack includes other optional solutions that make PLG easier. 1. PLG infrastructure All PLG companies need three important pieces of infrastructure to enable the motion: a. Data infrastructure In a way, product-led growth is data-led growth. You give away your free product in…”

04Frameworks mentioned

Summary and takeaways written by PM Atlas; quotes are short excerpts. © the original author.