What is Product-Led Growth?

Origin of the term

Blake Bartlett, a partner at OpenView Venture Partners, popularized "product-led growth" around 2016 to describe a pattern he and his colleagues had been watching in the wild: Dropbox, Slack, Atlassian, Twilio, Calendly, Zoom, and Figma had all grown into very large businesses with proportionally tiny outbound sales teams. The product was doing the selling. The phrase put a name to something that had been quietly emerging for a decade, and it has become the dominant framing for early-stage SaaS go-to-market.

What it requires structurally

PLG only works if four things are simultaneously true. The product is reachable — a prospect can find it, sign up, and start using it inside a single sitting, with no demo request, no procurement cycle, no provisioning email. The product delivers real value in the first session — not after a thirty-day setup, not after configuring twelve fields, but inside the first ten or fifteen minutes. The product creates natural expansion pressure — usage grows, more teammates get pulled in, and the upgrade is obvious. And every step of that flow is instrumented well enough that the team can see where users drop off and fix it before the cohort cools.

Take away any one of those and the motion breaks. A great free tier with terrible onboarding is just a leaky bucket. A self-serve trial that ends in "request a quote" is sales-led with PLG cosplay. The discipline is in shipping each piece honestly.

PLG vs sales-led growth

The honest framing is that they are points on a spectrum, not opposites. Even very PLG companies eventually have account executives, because once a team of five users becomes a team of five hundred, the buying decision moves to a procurement department that wants a contract, not a credit card. Conversely, very sales-led companies often add PLG motions on top of their existing pipeline — Salesforce launched an entirely self-serve product line in part to feed its enterprise pipeline with already-warm logos. The right mix depends on average contract value, complexity of the use case, and whether the product can credibly deliver value before a buyer's IT team is involved.

Where founders get it wrong

Two common failure modes. The first is treating PLG as a marketing term — slapping "free trial" on a sales-led product without rebuilding the onboarding to actually deliver value during that trial. The second is overestimating the product's ability to sell to the buyer — engineers love a self-serve tool, but the person writing the check is often three layers above them, and that person still wants a security review, a quote, and a conversation. Companies that nail PLG usually do both motions in parallel rather than betting the company on one.

At QUANT LAB

When we build a SaaS platform, we design the signup, onboarding, and self-serve billing as first-class features rather than something to bolt on after launch. That usually means a Stripe implementation that supports trials, metered upgrades, and team plans on day one; an in-product event stream that feeds an analytics tool so the team can see drop-off in real time; and an admin panel for the founders to look at any account's funnel without writing SQL.

Read our guide on building multi-tenant SaaS with Postgres RLS for the data-layer pattern that makes self-serve onboarding feasible, or our Next.js + Stripe guide for the billing flow. If you want a 30-minute review of whether your product is structurally ready for a PLG motion, book a call.