What Is a PQL (Product-Qualified Lead)?

The definition of a PQL comes from data, not opinion. A team studies the accounts that eventually paid, finds the early actions they shared (connecting a data source, inviting colleagues, creating a third project, bumping into a plan limit), and turns that pattern into a rule. Most teams pair the behavior with fit data such as company size and the user’s role, so a student who loves the free tier does not outrank a buyer at a real company. Product analytics runs the rule and flags the lead in the CRM.

In practice a PQL changes the first sentence of the call. Instead of a generic check-in, the rep opens with what the account has already done: three teammates are active, the export limit was reached twice, the integration went live last week. That context is why PQLs tend to convert better than form fills, and why the concept does not transfer to a cold list, where no product behavior exists yet. Outbound meetings and PQL conversations are different motions with different baselines, so blending them in one report hides what is working.

Heavy usage is not always intent, because the power user may be a student, a competitor, or an employee of a company that already pays. Teams also set the threshold once and forget it while the product changes underneath, and they mix up a PQL, which describes one person, with a product-qualified account, which rolls usage up across everyone at a company. A PQL goes stale too: a burst of activity from a month ago is no longer a reason to call.