पाठशाला Pathshala · उत्पाद Utpād, The product · Lesson 21 · Scale

Product-led growth: the mechanics behind the buzzword

Product-led growth is three pieces of engineering, not a slogan: a self-serve path to value, a loop through which users bring users, and upgrade triggers tied to usage. Build and measure each one.

Pathshala, The Founder Library · 11 October 2026 · 6 min read

A row of wooden water wheels on a shallow river below misty green hills.
Photograph: Quang Nguyen Vinh · Pexels

Product-led growth has become a word founders put on a slide when they mean that they have a free plan. A free plan is not a growth strategy. Product-led growth is a set of mechanics built into the product, each of which can be measured, and a company either has them working or does not.

This lesson takes the term apart. It gives a working definition, the three mechanics underneath, how to measure a loop and why its cycle time matters, how to design the moment that asks for money, a worked example for an Indian software company, the cases where the model does not fit, and the monthly review that keeps the mechanics honest.

What the term actually means

Wes Bush of ProductLed defines product-led growth as a strategy that relies on the product as the main vehicle to acquire, activate and retain customers. In practice that means the prospect evaluates the product before paying, through a free plan or a free trial, and that a meaningful outcome inside the product makes the upgrade an easy decision. He defines time to value as the time it takes a new user to reach their activation moment, and it is the first number to watch.

The test of whether a company is product-led is simple. Can a stranger who has never spoken to anyone at the company sign up, get the job done and pay, in one sitting or over a few days, without a demo? If the answer is no, the company may have a free plan but its growth still runs through sales. That is not a failure; it is a [different motion](/library/sales-motions-self-serve-inside-field), and the mechanics below are the work required to change it.

The three mechanics

The self-serve path. Sign-up, setup and the first result without human help. Its numbers are time to value and the activation rate, the share of new sign-ups who reach the moment that predicts they will stay. The [activation lesson](/library/activation-first-session-that-decides) covers how to find that moment. Every step a new user needs a person for is a step the product is not yet doing.

The loop. Using the product creates something that brings the next user: an invitation to a collaborator, a shared document or link that a non-user opens, a public page that search engines index, a payment request that the recipient must act on. Without a loop the product converts traffic that marketing buys; with one, each user is also a channel.

The upgrade trigger. The point at which the product asks for money should be the point at which usage shows the product is worth it: a limit on usage, on seats, on history, or on features a team needs once it depends on the product, such as admin controls, permissions and audit logs. The [freemium lesson](/library/freemium-free-trial-or-neither) covers where to draw the line between free and paid. Product-led companies also hand the warmest self-serve accounts to sales once usage crosses a threshold, often called product-qualified leads.

The loop, measured

Reforge’s Growth Loops are the New Funnels, by Brian Balfour, Casey Winters, Kevin Kwok and Andrew Chen, describes a loop as a closed system in which the output of one cycle is reinvested as the input of the next, and contrasts it with a funnel, which runs one way and needs constant new input at the top. Their Pinterest example: users save and repin content, Pinterest sends that content to search engines, searchers find it and sign up or return, and the cycle repeats.

Wooden norias beside a citrus grove in Hama, lifting river water for irrigation.
A noria lifts water that grows the grove beside it. A product loop should do the same with its users: each turn brings the next. Photograph: Noor Aldin Alwan · Pexels

An invite loop reduces to two numbers. The coefficient: invites sent per activated user, times the share accepted, times the share of invited users who activate in turn. The cycle time: the days from a new user signing up to their invitations being sent. A coefficient of 0.3 means every hundred activated users bring thirty more, who bring nine, who bring three: the loop multiplies the inflow by about 1.4 and then stops. A coefficient above one compounds. Cycle time decides how fast either happens, which is why a loop where users invite in the first session is worth more than one where they invite in the second month.

At the defaults, three invites, a quarter accepted and 40 per cent activation give a coefficient of 0.3, and the loop brings a little over a quarter of the year’s sign-ups. Raise activation to 60 per cent and the coefficient rises to 0.45: activation improves the loop twice, because more users activate and more of the invited ones do. Halve the cycle time and the year’s total barely changes below a coefficient of one, but above one it changes everything. The work that moves the loop is usually the same as the work on activation, plus putting the invite where the user already needs a collaborator.

A free plan is a price. Product-led growth is a path to value, a loop that brings the next user and a trigger that asks for money when the value is visible.

A worked example: a reconciliation tool for CA firms

A Hyderabad company builds a GST reconciliation tool for chartered accountancy firms. Sales has run through demos to firm partners; it closes about forty firms a quarter. The founders want the product to do more of the work. They build the three mechanics in order.

Self-serve first. A new firm can sign up, upload one client’s purchase register and see mismatches against GSTR-2B in under ten minutes, without a call. Activation, defined as a firm completing a reconciliation for two clients in its first week, starts at 22 per cent and reaches 41 per cent after three months of fixing the upload step. Then the loop. The natural collaborator is the client: a firm sends each client a link to upload missing invoices. Each invite shows the product to a business owner, and some of those businesses use other accountants, who are told by their client which tool to use. Firms send a median of six links a month; the coefficient on new firms is small but the cycle is a week. Then the trigger. The free plan covers five clients. The upgrade prompt appears when a firm adds its sixth client, the moment it has shown it depends on the tool, priced per client. Firms that cross twenty clients go to a sales call for the multi-partner plan.

A year in, self-serve brings more paying firms than the demo pipeline did, and sales works only the accounts that usage has already qualified. The company is product-led in the sense that matters: most customers met the product before they met a person.

The pattern of product first and person later is common among developer tools, and one of the largest was built from India. Postman, the API platform, was founded in Bengaluru and says 500,000 companies use it.

When product-led growth does not fit

Three situations defeat it. The buyer never touches the product: a procurement system bought by a CFO and used by clerks cannot rely on the clerks to sell it upward. Setup needs integration or data the user cannot provide alone: an ERP connection, a security review, a migration of years of records. The value appears only at scale, after months or across a whole organisation, so no single user sees it in a session. In each case a free plan adds cost without adding customers. The honest move is a sales-led motion with a trial that a salesperson sets up, and the product mechanics above used to shorten that sale rather than replace it.

The monthly mechanics review

Once a month, one page, three sections. Self-serve: median time to value for the month’s sign-ups, activation rate, and the step where most new users stall; pick one step to remove. The loop: invites sent per activated user, acceptance rate, activation of invited users, the resulting coefficient and the median cycle time in days; pick one change that either raises the coefficient or shortens the cycle. The trigger: free-to-paid conversion by cohort, the usage level at which accounts upgrade, and the share of revenue from accounts that never spoke to sales.

Compare each number with last month and with three months ago. A product-led company should see the share of revenue from self-serve accounts rise quarter by quarter. If it does not, the mechanics are not working yet, whatever the slide says.


The figure is a simplified model and the Hyderabad company is illustrative. Postman’s figure is as stated on its site, checked 10 October 2026.

Sources

  1. Wes Bush, Product-Led Growth (PLG): what it means, examples, and why it’s taking off, ProductLed, August 2023
  2. Brian Balfour, Casey Winters, Kevin Kwok and Andrew Chen, Growth Loops are the New Funnels, Reforge, July 2018
  3. Postman, About Postman (checked 10 October 2026) — Founded in Bengaluru; 500,000 companies use Postman.