Product-Led Sales: Letting Usage Create the Opportunity

For a few years the pitch for product-led growth was that you wouldn't need a sales team. Users would sign up, try the product, like it, and put in a credit card. Then the product-led companies that actually got big (Slack, Atlassian, Dropbox, Figma, Notion, Datadog) all went and built large sales organizations, mostly without saying much about it. The product didn't replace sales. It changed what sales was for.

Product-led sales is the methodology for that second act. The idea is that product usage, rather than marketing engagement or cold outreach, creates and qualifies the opportunity. The rep's job is to find the accounts where usage points to an expansion, get to the right people, and turn individual or team adoption into a contract with the organization.

Where it came from

Blake Bartlett of OpenView Venture Partners coined the term product-led growth (PLG) in 2016, to describe companies whose acquisition, conversion, and expansion are driven by the product itself. Wes Bush's 2019 book Product-Led Growth popularized the concept and the practices around free trials and freemium. Behind both sat earlier bottom-up adoption stories, most famously Atlassian's decision to grow without a traditional sales force, and the broader consumerization of enterprise software.

Product-led sales split off as its own discipline somewhere around 2020 to 2022. PLG companies had run into a specific problem. The free tier and self-serve plans were pulling in enormous numbers of users, but most of the revenue came from converting those users' organizations to enterprise agreements, and that conversion needed people. Tools such as Pocus, Endgame, and others built "product-led sales" platforms to surface product-qualified leads to reps, and practitioners started writing the motion down. By the mid-2020s PLS was a standard layer in most PLG go-to-market plans.

Where it fits best

You can't run product-led sales without a product-led foundation underneath it. It works when there's a free trial, freemium tier, or self-serve plan producing a steady flow of users, and when the usage data from those users is rich enough, and accessible enough, that someone can actually analyze it. The product also has to deliver value to individuals or small teams before the whole organization buys. And there needs to be a real gap between self-serve pricing and enterprise contract value, or sales has nothing to convert.

It doesn't fit products that can't be tried without an implementation, businesses that never instrumented usage, or markets where the buyer never touches the product before they buy. For those, solution selling or account-based selling make more sense.

How the methodology works

PLS sits on top of a self-serve funnel and adds people where the data says people are worth it.

1. Instrument the product

Nothing else works if you can't see usage. The company tracks sign-ups, activation events, feature adoption, collaboration (invites, shares, seats added), frequency, and account-level aggregates. Usage gets tied to accounts as well as individuals, so a rep can see that 40 people at one company have opened free accounts even though not one of them has talked to sales.

2. Define the PQL and the PQA

A product-qualified lead (PQL) is a user whose behavior says they're ready to buy or upgrade: they've hit a usage limit, adopted a premium feature, invited teammates. A product-qualified account (PQA) is an account whose aggregate usage says there's an organizational opportunity: lots of users, multiple teams, activity in several departments, or a pattern that looks like a rollout. Setting these thresholds is analytical work. You look at which behaviors historically came before conversion and expansion, and score accounts on those.

3. Route and prioritize

Not every PQA gets a rep. Most product-led companies segment. Small accounts stay self-serve with automated nudges, mid-sized accounts get a light sales assist, and large accounts with strong signals get the full enterprise motion. Fit data (company size, industry) gets combined with usage data to make the call.

4. Engage with product context

The PLS rep's outreach starts from what the account is already doing. "I noticed your engineering and design teams are both in the workspace and you've hit the collaborator limit twice" is a different opener from a cold email in every way that matters. The conversation is about how the organization gets more from a tool it already uses, not whether to adopt it. The usual paths: land-to-expand, where a department's self-serve usage becomes a team or enterprise plan; consolidation, where several separate self-serve accounts at one company become one contract; and governance, where growing usage triggers IT and security requirements that only the enterprise tier covers.

5. Find the buyer

The people using the product are rarely the people who sign enterprise contracts. A PLS rep works from the enthusiastic user, who becomes the champion, up to the budget holder, and usually has to bring in IT, security, and procurement people who have never opened the product. This is where PLS borrows from enterprise selling. Usage data gets the rep in the door, but the deal still needs an economic buyer and a decision process, and frameworks like MEDDIC apply just as they would anywhere else.

6. Feed learning back to the product

PLS teams work closely with product and growth. Which features drive expansion? Which limits trigger upgrades? Where do self-serve users stall? What sales learns shapes packaging and the roadmap, and product changes reshape the sales motion in turn.

A worked example

A collaborative design tool sees 60 free users at a large retailer, spread across three brand teams. Usage is up 40 percent month over month, two users have hit the file limit, and one has tried to turn on single sign-on, which is enterprise-only.

The account scores as a PQA. The rep reaches out to the user who tried SSO, who turns out to be a design lead tired of managing separate accounts. That lead becomes the champion. Over the next month the rep gets introduced to the VP of Brand, who owns budget, and to the IT security team, who won't approve any org-wide tool without SSO and audit logging. The enterprise deal closes for 300 seats. Nobody at the retailer ever filled out a "contact sales" form.

Strengths and limitations

PLS is efficient, because reps only spend time where usage justifies it. The conversations are warm. And it compounds as the user base grows. The downsides: it depends entirely on data infrastructure, reps can annoy perfectly happy self-serve users, and usage doesn't always map to budget. The most enthusiastic users sometimes sit in a team with no purchasing power at all. It also needs product, growth, marketing, and sales to coordinate tightly, which in our experience is the part most organizations struggle to keep up.

Key takeaways

• In product-led sales, usage creates and qualifies the opportunity. The product is the top of the funnel.
• PLS took shape around 2020 to 2022, once PLG companies admitted they still needed sales for enterprise conversion.
• PQLs and PQAs turn usage into sales priorities, and setting the thresholds is analytical work rather than guesswork.
• Users are not buyers. The rep still has to get from champion to economic buyer, and enterprise qualification still applies.
• Product and sales have to share what they learn, or the motion stops compounding.

Product-led sales is the clearest case of a sales motion that runs on signals and nothing else. Whether those signals reach the rep in time, with enough context to act on, is the whole question. That's the problem orchestrating land-and-expand is meant to solve, and it usually decides whether a PQA converts or quietly drifts to a competitor's free tier.