Product-led sales (PLS) is a sales motion that runs on top of a self-serve product: people sign up and use the product on their own, and salespeople contact only the accounts whose usage shows they're ready for a bigger deal. The product data decides who gets a call, when, and what the call is about.

Most users of a free plan or trial never need to speak to anyone. They try the product, upgrade with a card or drift away. A few of them, though, are a team at a large company that has outgrown the free tier without telling anyone, and a self-serve checkout won't turn that into an enterprise contract. Product-led sales exists to find those few and put a person in front of them at the right moment.

It tends to break in one of two ways. Either every signup gets routed to a rep, which annoys users and turns the motion into ordinary cold calling with a free plan attached. Or the usage data that should guide the reps sits in an analytics tool nobody in sales opens, so the reps go back to working lists.

TL;DR

• Product-led sales is the sales layer on a product-led funnel. The product handles signup, onboarding and small upgrades, and reps step in only where usage points to an account worth a larger contract.

• Public filings show the pattern. Zoom's 2019 IPO prospectus says 55% of its 344 customers paying over $100,000 a year started with at least one free host, and Figma's 2025 prospectus says about 70% of new Organization and Enterprise customers already had a Professional plan user inside.

• The signals that justify a call include several users from one company domain, a team stuck at a plan limit, trials of paid features, and admin activity like opening SSO or permission settings. A happy single user on the free plan should be left alone.

• Usage picks the moment and fit picks the account. Heavy use at a company too small to grow into a large contract belongs in self-serve, however busy the user is.

• The plumbing decides whether any of it happens: product events rolled up to the account, synced into the CRM through reverse ETL or HubSpot custom events, and an alert that tells the rep what the account actually did.

• The rep's job changes from pitching to helping an account that already uses the product, and the pay plan should reward the expansion reps cause, not the self-serve upgrades that would have happened anyway.

Who gets a call from this week's signups?

Take a made-up Ghent company, Routa, that sells job-planning software to installation and maintenance crews. The free plan covers up to five users, and the paid plan costs €12 per user per month. Out of a few hundred new and active accounts this week, three stand out.

The first is a facilities group in Antwerp with about 2,000 employees and some 400 field technicians. Fourteen users from its email domain are spread across three depots, two of their workspaces have hit the five-user cap, and an admin has opened the single sign-on settings page twice. If every technician ended up on the paid plan, that's 400 × €12 × 12, or €57,600 a year.

The second is a 60-person heating and cooling installer with about 25 technicians. Four users have been trying route optimization, a paid feature. Fully rolled out, the account is worth 25 × €12 × 12, or €3,600 a year.

The third is a freelance electrician who uses Routa every day, alone, and is among the most active users on the free plan. Upgrading would bring in €144 a year.

Only the facilities group gets a rep today. Spreading across depots, hitting the cap and looking at SSO are the moves of a company deciding whether to standardize on a tool, and that decision will involve IT, procurement and a budget holder who has never logged in. The installer gets an in-app offer and a short email about route optimization, and a rep only if an admin starts comparing plans. The electrician gets nothing except a good product. By activity alone he'd rank first.

What product-led sales adds to a self-serve product

Product-led growth is the engine underneath: the free plan or trial, the onboarding, the upgrade path that most customers follow without help. Product-led sales doesn't replace any of that. It adds three things on top: a rule for which accounts deserve a person, a pipe that gets product data to the people who act on it, and reps who know how to sell to someone already using the product.

The order of events is what separates it from sales-led growth. In a sales-led motion, the seller starts with a list of accounts and the first conversation comes before anyone has touched the product. In product-led sales, the user acts first and the rep responds to what they did. The first call starts from facts, such as "your team in Mechelen added six people this week", rather than from a guess about whether the product fits.

The unit that gets qualified is usually the product qualified lead, a user or account that has done what paying customers tend to do before they pay. Setting that threshold from your own conversion data has its own entry. What follows here is everything around it: which accounts rise above the threshold for a person, how the data travels and what the rep does next.

Zoom and Figma: what the prospectuses show

Companies rarely publish how their biggest customers first arrived. IPO filings are the exception, and two of them describe product-led sales almost exactly.

Zoom's 2019 registration statement says its sales model lets it turn a single non-paying user into a full enterprise deployment. In the fiscal year ended January 31, 2019, 55% of its 344 customers that contributed more than $100,000 of revenue had started with at least one free host. Those 344 customers brought in 30% of revenue. Zoom routed that demand to a direct sales force of field and inside reps organized by customer size and industry, with an online channel for small self-service buyers.

Figma's 2025 registration statement tells a similar story six years later. Figma hired its first sales rep in 2018, the year it launched its Organization plan for larger companies. In 2024 and the first quarter of 2025, about 70% of new Organization and Enterprise customers included at least one user who had previously been on a Professional plan. The filing puts it plainly: bottoms-up adoption drives growth, and the direct sales motion helps serve larger customers.

The same Figma filing also shows how much room is left after the first foothold. In March 2025, 78% of the Forbes Global 2000 used Figma, but only 24% spent more than $100,000 a year on it. That gap is the sales team's work: turning teams that already use the product into company-wide contracts, which is land and expand with the product doing the landing.

It also explains the economics. Because most users convert themselves or never convert at all, sales effort only goes to accounts with evidence behind them, which keeps customer acquisition cost low for the long tail while the large accounts still get a person.

Usage signals that should put a rep on the account

Not every burst of activity deserves a call. The signals worth routing to sales usually show an account outgrowing self-serve, not just a user enjoying the product:

• Several people from one company domain. One user is an experiment. Ten users across departments or offices is a company deciding whether to rely on you.

• A team stuck at a limit. Seat caps, project limits or usage ceilings, especially when the team keeps working around them instead of upgrading.

• Paid features in use. Trials of features on a higher tier tell you which plan the conversation should be about.

• Admin and security behavior. Opening SSO, permissions or audit log settings, or asking about data processing terms. These are the steps a company takes before a wider rollout, and they usually come with a procurement process attached.

• A sudden change in activity. A spike after months of steady use often means a new project, a new leader or a new team.

Acting on these is signal-based selling with your own product as the source, and it works best alongside outside buying signals like fresh investment or a newly hired head of operations at the same account.

Knowing when not to call matters just as much. A single user getting value on the free plan, with no colleagues joining and no limits in sight, should be left to the product. Calling them early spends a rep's time on an account that can't buy much, and teaches users that signing up means getting chased.

Heavy usage at the wrong company

The most common product-led sales mistake is ranking accounts by usage alone. The electrician in the Routa example would top any activity leaderboard, and the account is worth €144 a year.

So every product signal needs a fit check next to it. Company size, industry, region and the number of potential users decide whether an active account could ever become a large contract. Teams that keep who the account is and what it's doing as two separate scores can route on both: strong usage at a company that matches your profile of high-value customers goes to a rep the same day, strong usage at a poor fit stays self-serve, and a good-fit company with light usage gets nurture from the product until it picks up.

For this to work, users have to roll up to companies. Free signups often use personal email addresses or several subsidiary domains, so lead-to-account matching is what lets you see that fourteen separate users are really one facilities group.

Plumbing that puts product data in front of reps

Most companies already collect the events product-led sales needs. The problem is where those events live. Product analytics sits in one tool, billing in another, and sales works out of the CRM. Until the three agree on which account did what, reps are guessing.

A setup that works usually has four parts:

1. Named events. The product records the actions that matter, such as invites, limits reached, paid features tried and admin settings opened, with the user and company attached.

2. An account view. Events are joined to company records, usually in a data warehouse, so usage can be counted per account, not just per user.

3. A sync into the CRM. Segment describes reverse ETL as extracting data from a warehouse with a query you write and syncing it to tools like HubSpot. Tools such as Hightouch do the same job. Without a warehouse, HubSpot can take custom events sent through its API on Professional and Enterprise plans and use them in workflows.

4. An alert with context. Lead routing assigns the account, and the rep gets a message that says what happened, not just that a score changed.

That last step is where product data becomes part of the revenue engine. A signal that fires on Monday and reaches a rep on Thursday has lost most of its value, because the team has either upgraded on its own or moved on.

How the rep's job and pay change in product-led sales

A rep in a product-led sales motion rarely explains what the product does. The user already knows. The job is to help an account get more out of something it already relies on: plan the rollout to other teams, sort out security and procurement, and build the internal case for a company-wide contract. That's closer to consulting than to pitching, and it suits reps who ask good questions more than reps who enjoy cold calls.

The first message should prove the rep has looked. "Your Antwerp and Ghent depots are both at the five-user limit, and someone opened the SSO settings. Want help setting up a single account for all three sites?" will get an answer. "Just checking in on your trial" won't.

Pay needs the most care. If reps earn full commission on every upgrade in their territory, they'll claim self-serve conversions that would have happened anyway, and the company pays twice for the same revenue. A cleaner sales compensation plan defines what counts as sales-assisted, such as a contract above a set size or an account the rep worked before it upgraded, and pays on expansion within those accounts.

Product and sales also need shared rules of engagement: which accounts reps may contact, how often, and which in-app prompts pause while a rep is talking to an account. Without them, the same admin gets an upgrade banner, a lifecycle email and a sales call in one afternoon.

In short

Product-led sales puts people where the product can't finish the job. Most users never need a rep, and treating them as if they did wastes sellers and irritates the very people the product won over. A small share of accounts, the ones spreading across a large company and running into limits, need someone to turn team usage into a company contract.

Zoom and Figma both built their large accounts this way, from free or individual users first and a sales team second. The hard parts are less glamorous: deciding which signals justify a person, checking fit before acting, and getting the data to reps fast enough to matter.

Done well, it's one of the cleanest routes to prospecting that starts from what accounts actually did, and it fits into a GTM system where product, CRM and outreach share one view of each account.

Nebor builds that layer for clients: the event tracking, the account roll-up, the CRM sync and the alerts reps act on, set up in the stack they already have and handed to the team with every scoring and routing rule documented, so the rules can change when the product does.

Frequently asked questions