Architecture Reference // 2026

Product Led
Growth

The activation, conversion, virality, and organizational mechanics behind products that sell themselves.
8 domains  ·  27 rules.

ACQ
→
ACT
→
EXP
→
GRW

ACQUIRE  ·  ACTIVATE  ·  EXPAND  ·  GROW

01 // Foundation

What is PLG, and why does adding a free tier not constitute a strategy?

Product Led Growth is a go-to-market strategy where the product itself is the primary mechanism for acquisition, conversion, and expansion — not a pricing change, not a free tier bolted onto a sales-led product, and not a marketing tactic. It requires the product to do the work that salespeople and demand-generation teams do in a sales-led motion. PLG fails when the product was designed for demos and the go-to-market was redesigned for self-serve without redesigning the product.

PLG is a distribution strategy — the product must be redesigned to execute it
Adding a free tier to a product that was designed for demos and assisted evaluation is not PLG — it is free-tier theater. PLG requires that the product can acquire, activate, and convert users without human intervention. This means surfacing value immediately, providing an in-product upgrade path, and generating behavioral signals that feed the growth loop. If any step in the acquisition-to-conversion journey requires a sales rep, you have a hybrid motion. Name it accurately.
PLG works only when the product can be evaluated without customization or setup assistance
PLG fails for products that require significant configuration, data migration, or integration before value is visible. If a user cannot reach the core experience within 30 minutes of signing up — alone, without a CSM — PLG is not the right primary motion. The activation path must be self-completable. Every dependency on human intervention is a structural leak in the acquisition funnel that no amount of onboarding email optimization will fix.
In B2B SaaS, PLG and sales-assisted growth are complementary — not competing motions
The most effective B2B SaaS companies run PLG for self-serve discovery and a sales-assisted motion for enterprise accounts. PLG generates product-qualified leads; sales closes large contracts. Treating them as competing strategies leaves revenue on the table — either by failing to capture self-serve demand or by not pursuing enterprise accounts that require a human relationship. The handoff from PLG to sales is the PQL, not the territory line.
02 // Activation & Time to Value

What is the single metric that determines whether your PLG motion is working?

Activation is the moment a user first experiences the core value the product delivers. Before activation, users are evaluating. After activation, users are retained — even if they haven't paid yet. The most important lever in PLG is compressing the path from signup to that moment: fewer steps, less configuration, less ambiguity about what to do next. Activation rate is the leading indicator of conversion, retention, and NRR — everything else in the PLG funnel is downstream of it.

01
Define activation as a behavioral event correlated with retention — not a milestone you invented
"User completes profile" is not activation. Activation is the first behavioral event that predicts long-term retention — identified empirically by correlating early actions with 90-day retention, not by product intuition. For a project management tool it might be "created a task and assigned it to a teammate." For a data pipeline tool: "ran a successful sync." Define it from data. Redefine it when the data changes.
02
The empty state is where PLG motions most commonly fail — fix it before the onboarding flow
New users arrive to a blank product and leave. The empty state — the first screen after signup — is where most PLG funnels leak. A blank canvas is not welcoming; it is a barrier. Empty states should pre-populate with example data, guide the user to their first action, and make the product look like it is already working. Teams that A/B test downstream onboarding flows without touching the empty state are optimizing below the biggest drop-off point in the funnel.
03
Time to activation is the metric — not activation rate in isolation
A product with 40% activation and a 3-day median time-to-activation will underperform one with 30% activation and a 20-minute median. Every hour between signup and the aha moment is a window for the user to disengage, get distracted, or choose a competitor. Compress time to value relentlessly. Remove every step that is not strictly necessary to reach the core experience — including mandatory profile setup, optional integrations, and forced tutorial flows.
04
Instrument the activation funnel by step — "signup to paid" is not a funnel, it is two points
"5% of signups convert to paid" is not actionable. "We lose 60% of users between signup and their first project, and 40% of those drop at the integration step" is actionable. Instrument every step between signup and the activation event with distinct events. The funnel data reveals which step has the worst drop-off — which is the highest-leverage place to invest engineering time. Without step-level instrumentation, optimization is guesswork.
03 // Onboarding

How do you design an onboarding that reaches the aha moment without a CSM in the room?

Most onboarding is designed around the product's architecture — "here are your settings, here is your dashboard, here is the help menu" — rather than around the user's intent. This produces tours of empty interfaces that show users where features live but never demonstrate why they matter. Good onboarding takes the user to value by the shortest possible path. Intent-first onboarding routes users toward the experience they came to have — not toward a tour of the experience they might someday need.

01
Design onboarding around the user's first job — not around the product's feature set
The user signed up with a specific intent. Onboarding should identify that intent — through a brief qualification question, a use-case selector, or a template library — and immediately route them toward the experience that matches it. Feature-first onboarding shows users where things live. Intent-first onboarding shows users how to accomplish the thing they came to do. The difference is whether you start with your product's taxonomy or with the user's goal.
02
Checklist onboarding works only when activation genuinely requires multiple distinct steps
An onboarding checklist creates visible progress and reduces ambiguity — but only when activation requires multiple actions and each checklist item moves the user meaningfully closer to value. For a single-action activation path, adding a checklist creates friction instead of removing it. The test: is completion of the checklist tightly correlated with long-term retention? If yes, the checklist is load-bearing. If no, it is ceremony that delays value delivery.
03
Send behavioral emails — not scheduled drip sequences
Day-1, day-3, day-7 drip treats all users identically regardless of what they did in the product. Behavioral emails — triggered by what the user did or did not do — dramatically outperform scheduled sequences. "You created a project but haven't invited anyone yet" converts better than "Day 3: Did you know you can invite teammates?" Triggered emails require instrumented events as a prerequisite. Scheduled sequences require a content calendar. The infrastructure investment is the same; the conversion difference is not.
04 // Virality & Acquisition

How does a PLG product acquire its next user from its current user?

Viral acquisition in PLG is not about referral bonuses or shareable content — it is about designing the product so that using it creates a surface that exposes new users to its value. Collaboration, sharing, and publishing are the natural mechanics. The strongest viral loops are structural: the product delivers its full value only when the user involves someone else. If your product delivers its full value to a single user in isolation, your acquisition loop is paid or content-driven — not product-driven.

Structural virality — inviting colleagues is required for full value, not optional
Slack requires teammates for messaging. Figma multiplies in value with each additional collaborator. Notion pages are more useful when shared. In each case, reaching the full product experience requires bringing someone else in. This is structural virality — not a referral program, not a growth hack. If your product delivers its full value to a single user in isolation, you must either redesign the core collaborative loop or accept that your acquisition motion is not product-driven.
Published artifacts expand the acquisition surface without acquisition spend
A user who publishes a report, dashboard, form, or document creates a publicly accessible artifact that carries your brand to a new audience. Every view of that artifact is a passive acquisition impression. Every viewer who creates an account is a viral acquisition with zero marginal CAC. Invest in making shared content look polished, load instantly, and carry a visible "built with" signal. The quality of published content determines whether the brand impression drives conversion or indifference.
Measure virality with the viral coefficient by cohort — not with "invites sent"
The viral coefficient is the number of new activated users each existing user generates. A coefficient above 1.0 means the product grows without external acquisition spend. Most B2B SaaS products operate between 0.1 and 0.4 — enough to meaningfully reduce CAC but not enough to sustain growth alone. Track it by cohort to distinguish whether virality is improving, decaying, or stable over time. "Invites sent" is an activity metric; the viral coefficient is a growth rate.
05 // Free-to-Paid Conversion

How does a PLG product convert a free user to a paying customer without a sales conversation?

Free-to-paid conversion in PLG is an in-product motion. There is no sales call to lean on, no demo to schedule, no CSM to walk the user through pricing. The product itself must make the value case, surface the upgrade moment, and complete the transaction. The failure mode is designing the free tier and paid tier without designing the transition — leaving users who have hit peak free-tier value with no clear path forward. The conversion trigger should be the moment of maximum value awareness — not an arbitrary time limit or paywalled feature they may never encounter.

The upgrade prompt must appear at the moment of maximum value awareness — not at account creation
Placing upgrade prompts at signup ("choose a plan") or after an arbitrary time delay ("your trial ends in 3 days") misses the conversion window. The highest-converting moment is when the user has just experienced value and is trying to do more of it — and hits a natural limit. "You've used 9 of your 10 free projects" at the moment the user is creating project #10 is the correct placement. Interruption-based paywalls convert at a fraction of the rate of friction-based paywalls at the point of expansion intent.
Make the upgrade path self-serve to the end — "contact sales for pricing" is a conversion dead end
An upgrade flow that terminates with "contact sales for pricing" has a conversion rate an order of magnitude lower than one that ends with a credit card field. Every step that requires a human introduces latency and drop-off. For ACV under $50k, the full upgrade including billing should be self-completable in under 3 minutes. For enterprise ACV, a self-serve path should still exist so users who prefer to proceed without waiting for a sales cycle can do so.
Present the annual plan as the default at first conversion — not as an upsell after monthly commitment
A user who has just decided to pay is more likely to commit annually than a monthly subscriber being upsold at renewal. Present the annual plan first, with the monthly price visible as the alternative. The anchoring effect of "save 20% annually" at the moment of first commitment outperforms any attempt to convert monthly customers to annual mid-contract — because the decision fatigue of a second conversion is always higher than the decision fatigue of the first.
Track conversion rate by signup cohort — not by calendar date
"Our conversion rate is 3%" is a snapshot, not a trend. "The February signup cohort converted at 3.8% within 30 days; January converted at 3.2%" reveals that a change made between January and February improved conversion. PLG conversion rates are cohort metrics — analyzed against when users signed up, not against when the conversion event occurred. Without cohort tracking, the effect of product changes on conversion is invisible in the aggregate number.
06 // Product Qualified Leads

How does a PLG motion feed a sales team without routing every signup to a sales rep?

A Product Qualified Lead is an account that has demonstrated, through product behavior, that it is ready for a sales conversation. PQLs are the structural handoff between self-serve PLG and sales-assisted growth — they are accounts that have activated, used the product meaningfully, and are now either hitting enterprise feature ceilings or showing organizational signals that indicate enterprise intent. PQLs are not leads that marketing scored — they are leads that the product earned.

MQL

Marketing Qualified Lead — intent signal, no product evidence

A user who downloaded a whitepaper, attended a webinar, or scored above a threshold on demographic criteria. No evidence of product activation. Routing MQLs directly to sales produces a high-volume, low-conversion SDR queue. In a PLG company, MQLs should be routed back into the product — not to a sales rep — until they demonstrate activation.

PQL

Product Qualified Lead — activated, engaged, hitting a ceiling the product cannot sell past alone

A PQL definition built from product behavior: account has 3+ active users, created 10+ projects in 30 days, and has hit the collaboration limit at least once. Sales conversion from PQLs is 5–10× higher than from cold signups because the product has already done the discovery work. PQL definitions that lack usage behavior in their criteria produce false positives: sales calls customers who signed up and never activated. Route PQLs to sales. Route everyone else to the product.

EQL

Expansion Qualified Lead — self-serve ceiling reached, organizational footprint growing

An EQL is a paying account showing signals that it has outgrown its current plan: accelerating usage, users joining from new domains, feature requests for enterprise capabilities. EQLs reveal where the self-serve ceiling sits. If many EQLs never convert through sales, the self-serve ceiling may be too low — closing the gap with product investment is more durable than adding a CSM motion to each account.

07 // Expansion Mechanics

How does a PLG product grow revenue from within its existing user base without a CSM for every account?

Expansion in PLG is the product counterpart to account management in a sales-led motion. The product surfaces expansion moments — usage limits reached, team features unavailable, collaboration requests blocked — and routes users to the upgrade path without human intervention. At PLG scale, the CSM-per-account model does not survive. Expansion must be automated, product-driven, and triggered at the exact moment of expansion intent — not on a quarterly review cadence.

01
Team expansion is the highest-leverage PLG motion in B2B — design the invitation flow accordingly
A single activated user has expansion potential that compounds with every teammate they invite. A 5-person team costs 5× a single user; a 50-person team costs 50×. The team invitation flow is the highest-leverage surface in any B2B PLG product. Every friction point in that flow — confusing permission models, unclear cost implications, invitation email delivery failures — compounds across every account at organizational scale. Treat the invitation flow as a revenue surface, not a utility feature.
02
Expansion is triggered by value delivered — not by a calendar or a CSM's follow-up schedule
A quarterly business review is a sales-led expansion motion. In PLG, expansion is triggered when the product signals that the user has outgrown their current plan — a usage threshold, a collaboration limit reached, a request for an enterprise feature. The product must expose these signals visibly to the user (not only to the sales team) and provide an immediate upgrade path. If the expansion trigger requires a human to notice and act, the expansion motion does not scale.
03
Instrument expansion signals separately from conversion signals — they have different leading indicators
Expansion revenue from existing accounts has different behavioral precursors than free-to-paid conversion. A user creating additional workspaces, inviting users from new domains, or consuming usage at an accelerating rate are expansion signals — not conversion signals. Building a separate expansion signal model lets you route the right intervention — an in-product upgrade prompt, a PQL alert to sales, or an EQL flag — to the right account at the right time, rather than treating all usage growth identically.
08 // Culture & Measurement

How do you build an organization that sustains a PLG motion without reverting to sales-led instincts?

PLG requires a different operating model than sales-led growth. The product team owns the revenue funnel. Engineering velocity directly impacts ARR. The success metric for a PM in a PLG company is not features shipped — it is activation rate, conversion rate, and expansion revenue attributable to product changes. The organizational tension in PLG is that sales instincts — call the customer, close the deal — are the opposite of the motion the product is designed to run.

The North Star metric is activated users — not signups, not pageviews, not MQLs

Signups are a vanity metric in PLG. An unactivated signup has the same revenue value as no signup. The North Star should be the number of users who have reached the behavioral activation event in a given time window — because activation is the leading indicator of conversion, retention, and NRR. Teams that optimize for signups build top-of-funnel machines. Teams that optimize for activated users build products that convert and retain.

Product managers in PLG own conversion rate — not features

In a sales-led company, PMs own the feature roadmap. In a PLG company, PMs own the funnel. A PM responsible for the activation flow is accountable for activation rate, time-to-activation, and conversion rate from activated user to paid. This requires PMs to be deeply instrumented — not just aware of what features launched, but aware of whether those features moved the conversion curve. A feature launch that doesn't improve the funnel is not a win in a PLG org.

Sales and PLG incentives must be structurally aligned — misalignment produces active friction

In companies running PLG and sales in parallel, sales reps will resist the self-serve motion if self-serve conversions don't count toward quota. Reps who watch self-serve deals close without credit will intercept self-serve users, add friction, and slow the PLG motion. Structure compensation so that sales receives credit for self-serve conversions within their territory. Misaligned incentives produce organizational behavior that actively undermines the product-led motion — regardless of what the strategy deck says.

The bottleneck is activation, not acquisition — optimize in that order

In most early PLG companies, activation rate is the binding constraint, not traffic volume. More signups into a broken activation funnel produces more wasted CAC, not more revenue. Fix activation before investing in acquisition. Once the activation funnel is working — activation rate stable, time-to-value compressed, conversion rates healthy — acquisition investment has a predictable return. Before that, acquisition spend is speculation dressed as growth.

The mental model

PLG is not a free tier. It is a product designed to sell itself.
Activation rate is the leading indicator. Conversion follows. Expansion compounds.
The empty state is where PLG motions most commonly fail.
Route PQLs to sales. Route everyone else back to the product.
The bottleneck is activation, not acquisition — until it isn't.

Daniel Brasileiro