Product-Led Growth in Practice

Moving from theory to execution: the metrics, org structures, and product decisions that make PLG work.

A company told me they were going product-led. I asked what would change on Monday. The answer was that marketing would stop gating the demo and the product team would add a self-serve signup. That was the whole plan. Six months later the signup flow worked beautifully and nothing else had moved, because product-led growth is not a signup flow. It is a decision about where the growth loop lives, and that decision has consequences for metrics, staffing, and roadmap that most companies do not actually want to accept.

I have built growth systems at AliExpress US, Indiegogo, and Next2Market. The pattern across all three is the same: PLG works when the product itself creates the next user, and it fails when a company adopts PLG vocabulary while keeping a sales-led operating model. The gap between those two states is almost entirely execution, not strategy.

Find the Loop Before You Find the Metrics

Before touching a dashboard, a team needs a written, falsifiable statement of its growth loop. Not a funnel. A loop, meaning the output feeds back into the input without someone spending money to restart it.

The affiliate engine I built at AliExpress is a clean example. A partner joins, earns from traffic they send, earns enough to justify producing more content, and that content both drives more GMV and demonstrates to other potential partners that the program pays. Each turn of the loop made the next partner cheaper to acquire. That system reached 10,000-plus partners across 40-plus countries and drove roughly 30% revenue lift, and the reason it scaled is that the loop was real. Partner earnings were the fuel, and partner earnings came out of the product working, not out of a marketing budget.

Contrast that with the common failure: a company runs paid acquisition into a self-serve product, users convert at some rate, and the company calls it PLG. There is no loop there. It is a funnel with a cheaper sales motion. That can be a perfectly good business, but it does not compound, and it will not behave the way PLG case studies promise.

The test I use is simple: if we cut paid spend to zero for a quarter, does user growth go to zero, or does it keep turning at a lower rate? If it goes to zero, there is no loop yet, and the first job is building one rather than instrumenting one that does not exist.

The Metrics Most Teams Get Wrong

Once a loop exists, measurement determines whether you can improve it. Most PLG metric stacks are copied from a blog post and measure the wrong things at the wrong altitude.

One warning from experience. Whatever you make the headline activation metric will be gamed, not maliciously but structurally, because teams optimize what is measured. At AliExpress, when we built the AI recommendation system that lifted GMV 40%, the tempting metric was click-through on recommended products. Optimizing click-through would have made the system worse: sensational thumbnails and clickbait pricing lift clicks and depress purchase satisfaction. We held the line on downstream GMV per session and return rate as the real scoreboard, which made the work slower to show wins and much better when it did.

Org Structure Is the Actual Constraint

Here is where I disagree with most PLG writing. The standard advice is to hire a growth team. In my experience, hiring a growth team into a company that has not changed its ownership model is the most reliable way to get PLG theater.

The problem is jurisdiction. A growth team that does not own the core product experience can only touch the edges: landing pages, emails, onboarding tooltips, pricing page copy. Those are real levers, but they are the smallest ones. The biggest PLG levers live inside the core product, which belongs to product teams who are measured on feature delivery and have no incentive to prioritize a growth experiment.

So the growth team runs experiments in the territory it controls, reports single-digit percentage wins, and the company concludes PLG is overhyped. The actual finding is narrower: growth work confined to the perimeter produces perimeter-sized results.

What works better, in the teams I have seen succeed, is giving the growth function real ownership of a surface that matters, with the engineering capacity to change it. At Next2Market, growth owned the entire path from first touch to post-purchase, including product page architecture and checkout. That ownership is why an 18% conversion rate improvement was achievable at all. It required changing things that would have been off-limits to a perimeter growth team.

A growth team without product ownership is a marketing team with better analytics. That can be valuable, but it will not produce product-led growth.

Product Decisions That Determine Whether PLG Works

Some product choices quietly decide the ceiling of a PLG motion long before any growth work begins. These are the ones I look at first.

The free tier has to be genuinely useful and structurally incomplete. Most companies get one of the two. A free tier that is crippled produces signups who never reach value and therefore never refer anyone. A free tier that is complete produces happy users who never pay. The right shape is a product that fully solves one real problem and creates an obvious next problem that the paid tier solves. That is a design question, and it is usually decided badly by committee between sales and product.

Single-player value must come before multiplayer value. Products that require a team or a network before delivering anything have a brutal cold-start problem and will not grow product-led regardless of how good the growth team is. If your product only works once three colleagues join, you have a sales-led product with a self-serve signup page.

The sharing mechanism has to be a byproduct of normal use, not a separate altruistic act. Invite flows that ask a user to stop what they are doing and recruit someone perform terribly. Mechanisms where sharing is how the user gets their own job done perform well. The distinction sounds small and it is the difference between a loop coefficient of 0.1 and 0.8.

And pricing must scale with realized value, not with seats or arbitrary tiers. When the price a customer pays tracks the value they get, expansion happens without a conversation. When it does not, every expansion requires a negotiation, which reintroduces the sales motion you were trying to avoid.

The First 90 Days

If I were brought in to make PLG real at a company, the first quarter would look deliberately unimpressive. No new experiments for the first three weeks. Instead: write down the growth loop in one paragraph and test whether it survives the cut-paid-spend thought experiment. Define activation empirically from cohort data rather than from opinion. Instrument time-to-value and the loop coefficient, and get both onto a dashboard that the whole company sees.

Then pick the single worst step in the path to activation, the one where the largest cohort drops with the clearest reason, and fix it properly rather than running five small tests around it. Expect one meaningful win, not a portfolio of them.

Somewhere in that quarter you will also hit the org question, because the fix that matters will require changing something the growth function does not own. How leadership responds to that request is the real signal about whether the company is product-led or just using the phrase. Every PLG program I have watched succeed cleared that hurdle early. Every one I have watched stall ran into it and quietly routed around it.