What is a product qualified lead (PQL)?
In sales and marketing, PQL means product qualified lead. It's a person or a team whose use of your product shows they're ready for a sales conversation, most often during a free trial or on a free plan. An MQL is qualified by how someone engaged with your marketing. A PQL is qualified by what they did in the product.
How to measure PQLs
Two numbers tell you whether PQLs work. The PQL rate shows how many trials become one, and the PQL-to-customer rate how many of those buy. Time to purchase shows whether they also sign sooner. Compare the last two with the trials that never became PQLs.
PQL rate (%) = (new trials that became PQLs ÷ new trials) × 100
PQL-to-customer rate (%) = (PQLs who became paying customers ÷ PQLs) × 100
Time to purchase = days from trial start to payment, PQLs compared with other trials
Count by cohort rather than by calendar month. Take the trials that started in a given week, and count how many reached the signal within the trial. Otherwise someone who starts on the 30th and qualifies on the 5th lands in the wrong month, and the rate swings for no real reason.
Why add PQLs if every trial can already be an MQL?
A trial sign-up shows that someone wants to try the product, but nothing yet about what they'll do with it. A few days later, some are already using it for real work, some are stuck on setup, and some haven't logged in since. Handled as one list of MQLs, they all get the same follow-up at the same pace, and the rep calls each of them knowing just as little.
The PQL uses what the product already records to set the order. Other trials still get the usual follow-up, but sales calls first the people whose use shows they're moving toward a purchase, while it's happening. They've already seen the product work for them, so the conversation can start further along.
Define the signal from what paying customers did in their trial
Start from the outcome and work backward. Take the trials that turned into paying customers over the last few months, and the trials from the same months that didn't. Look at what each group did during the trial. You're looking for an action that shows up often among those who paid and rarely among the others. Unlike activation, which every new user should reach, a PQL signal is one that only part of the trials reach, mostly those who go on to buy.
The trial sets the limit. In 14 days, many trial users only come back on a handful of days, so the signal has to be reachable in that window. A threshold that takes a month of use never fires, and good leads buy or leave before sales hears about them. On a free plan there's no deadline, and the question moves to timing: the moment someone reaches a limit of the free plan is often the moment to talk.
You rarely find the right signal on the first attempt. Five are commonly used:
- Repeated use. Coming back on several days. Easy to measure, but someone can return often without touching what matters.
- Using the core feature. Repeating the action behind your activation event, past a threshold. Slack's 2,000-message mark is the best-known threshold of this kind: almost all the teams that passed it kept using the product.
- Reaching a limit. Hitting a cap on seats, projects or usage. It puts a decision in front of the user, if your plan has limits.
- Bringing others in. Inviting colleagues, or several people active on the same trial. A strong sign when buying is a group decision.
- Looking at plans in the product. Opening the plans or billing page inside the product. It's close to a decision, so it often comes late. The pricing page on your website counts for less, since many trial users pass through it on their way to sign up.
The stricter the signal, the shorter and later the list. If sales is flooded with leads who go nowhere, tighten it. If the list is almost empty, loosen it. Within a trial, a burst of key actions over two or three days is usually a better moment to call than the total since the trial began.
Whatever the signal, check the account first. A business email, a company in your target and real data connected instead of a sample file tell you the trial is a real evaluation. The job title weighs less than in an MQL score, because the person testing is often not the one who buys. A developer or an analyst asked to evaluate the tool is a good sign for the account, even if they never sign the contract. A student on a personal email, alone, with sample data, is curiosity, however active.
Getting sales to follow up on PQLs
That first conversation depends on sales picking up the PQL. Two objections come up again and again, and both are fair.
The first: "a PQL is just another lead." If the list is long and comes with no context, sales will treat it like a guide download, and they'll be right. Send fewer PQLs, only from accounts large enough for a call to matter, with what the team did in the product: a source connected, three colleagues invited, two visits to the plans page. The first call then starts from what they did. When the active user isn't the buyer, the PQL is a reason to reach the account and find who decides.
The second: "they'll buy online anyway." Sometimes that's true. Check it before arguing: for a few weeks, send half of comparable PQLs to sales and leave the other half to buy on their own, then compare conversion, plan and time to purchase. If a call changes nothing for small accounts, stop routing them, and keep sales for the accounts where a conversation changes the result. The self-serve customers your sales team can't see covers what that split looks like in the CRM.
Where PQLs go wrong
The bar sits in the wrong place. A rising PQL rate with a falling PQL-to-customer rate often means the bar is too low, and sales soon stops trusting the list. A very high conversion on a tiny list can mean the bar only catches people who were going to buy anyway.
A large account looks hotter than it is. Many people testing in the first week make a large company look ready to buy. Its signature still goes through procurement and a security review.
The definition changes without a date. Review it every quarter, and date each change, so a jump in the rate isn't mistaken for a change in your trials.
Following PQLs from trial to revenue
Funnelsight reads the PQL definition your team set, as an event in the product or as a field in your CRM, and follows it like any other stage of the funnel. You see the PQL rate by acquisition source, the path from PQL to opportunity to customer, and the time to purchase compared with other trials. Each change to the definition is dated. Scoring leads and routing them to reps stays with your CRM and your data stack.
See which sources bring the PQLs that become customers, and how fast they sign.
Start free trialWhat's the difference between a PQL and an MQL?
An MQL is qualified by who someone is and how they engaged with your marketing, such as downloading a guide or requesting a demo. A PQL is qualified by what they did in the product. The same person can be both. Count them once, and keep both origins on the record, so marketing and sales report the same total.
What's the difference between a PQL and an activated user?
Every new user should reach activation, the first time the product does its job for them. Only part of them become PQLs. A PQL adds what activation doesn't show, an account in your target and signs of buying intent, such as reaching a limit or inviting colleagues.
What's the difference between a PQL and an SQL?
A PQL is qualified by what someone did in the product, before anyone has spoken to them. An SQL has been qualified through a conversation, by a BDR or a sales rep depending on how your team is organized. A PQL can become an SQL once that conversation confirms there's a real opportunity. Stage names vary between companies, so follow the ones your CRM already uses.
Do you need a product analytics tool for PQL scoring?
Not to start. Product events usually already sit in your application database or your data warehouse, and a weekly export compared with the deals in your CRM is enough to test a definition. Once it holds, the PQL becomes a field in the CRM, often updated by the same sync as your MQL scores. Combine several signals into a score only when one already leads to real conversations.