A go-to-market motion where the product is the primary mechanism for user acquisition, activation, and expansion, with conversion driven by the product experience and not a sales team.
How can we design the product so that using it creates the conditions for acquiring and converting the next customer?
Product-led growth is a go-to-market motion in which the product itself is the primary mechanism for acquiring, activating, and retaining customers. The company builds featuresFeatureProduct SpecificationA product capability or featureView reference → and flows that let a user experience genuine value before any sales conversation happens, and conversion follows from that experience.
The term "product-led growth" was popularised by OpenView Venture Partners around 2016 as a way to describe a pattern they were seeing across their portfolioPortfolioPortfolioA grouping of products by strategic axisView reference → companies. Atlassian, Slack, Dropbox, and Zoom had all grown primarily through product adoption, with little outbound sales. Blake Bartlett at OpenView codified the pattern and argued it represented a structural shift in how software companies should go to market. Wes Bush, founder of ProductLed, published Product-Led Growth: How to Build a Product That Sells Itself in 2019, which gave the approach a systematic treatment and introduced a vocabulary that has since been widely adopted. The underlying mechanics are older: freemium models and self-serve trials existed long before the term, but PLG named the strategy deliberately and gave teams a shared framework for designing around it.
A product-led growth motion has four mechanical stages that a user moves through.
Free entry. The product offers a meaningful free tier, a time-limited trial, or a freemium plan that lets a user accomplish something real. The goal is not a demo or a marketing page but a working product in the user's hands. A project management tool that lets up to five users manage unlimited projects for free is a free entry point. A 14-day trial of a design tool with no credit card required is another.
Aha moment. The product is designed to deliver a specific, tangible result quickly. Teams building PLG products map the shortest path from sign-up to the moment a user realises the product does something they care about. For a note-taking app, the aha moment might be the first time search surfaces a note the user had forgotten. For a data pipelineData PipelineData & AnalyticsAn automated pipeline for data transformationView reference → tool, it might be the first successful sync completing in under a minute.
Expansion motion. Usage naturally creates pressure to upgrade. A team outgrows the free tier's seat limit. An individual wants to share outputs with a client. A power user hits the API rate cap. The expansion trigger is baked into the product experience, surfaced at the moment the user feels the limit.
Monetisation trigger. Conversion happens when the user hits the natural ceiling or when the product surfaces the value of an upgrade at the right moment. PLG companies track product-qualified leads (PQLs): users who have completed the aha moment and show usage patterns that correlate with paid conversion.
A worked example. An analytics tool offers a free plan with three dashboardsDashboardData & AnalyticsAn analytics dashboardView reference → and 30 days of data retention. A data analyst at a mid-size company signs up without contacting sales, builds three dashboards, and shares one with their manager. The manager asks for a dashboard of their own. The team is at the seat limit. The analyst upgrades to a team plan. A month later the product surfaces a prompt to add historical data beyond 30 days. The team upgrades again. Sales has not been involved.
Product-led growth fits best when the product has a short time-to-value, when the buyer and the end user are the same person or in close contact, and when the core experience can be delivered at low marginal cost. SaaS tools for individual contributors, developer platforms, and collaboration software are natural fits.
It fits poorly when the product requires significant configuration or integration before delivering value, when the sale requires organisational sign-off from stakeholdersStakeholderTeam & OrganisationA person with influence over the productView reference → who will never touch the product, or when the cost to serve a free user is high. Enterprise infrastructure, regulated financial software, and complex services businesses typically needNeedUserA user need, pain, desire, or constraintView reference → a sales-led motion, at least at the initial sale, even if they can layer in PLG for expansion later.
The most common failure is building a free tier that is too restricted to demonstrate value. A freemium plan that withholds the core feature is not a PLG motion; it is a demo with friction. The second common failure is neglecting the expansion design: if the product does not naturally create pressure to upgrade, conversion requires a sales effort anyway.
The product-led growth framework is a flow pattern in the go-to-market category. The Unified Product Graph models the four stages as a connected sequence of entities:
gtm_strategygtm_strategysales_motiongtm_strategymetricModelling the PLG motion this way lets a team see the full funnelFunnelGrowthA conversion funnel tracking user progressionView reference → as a connected graph: each stage links to the next, metrics attach to the relevant stage, and the strategy decisions that shaped each stage are visible alongside the execution.