A product qualified lead is an account or user whose behaviour inside the product suggests they are ready to buy or expand. It only exists where people can use the thing before paying for it, which is why it arrived with free trials and free tiers rather than with any change in sales theory.
The idea is sound. Watching what somebody does beats asking what they intend. The implementations go wrong at a predictable point, which is the moment a usage event gets treated as a buying signal without anybody checking that the two are connected.
Where it sits against the other qualifications
| Type | Evidence it rests on | What it does not tell you |
|---|---|---|
| Marketing qualified | Engagement with your content: downloads, pages, form fills. | Whether they have the problem, or only an interest in it. |
| Sales qualified | A human judged them worth pursuing after a conversation. | Consistency. Two reps apply the bar differently and both are defensible. |
| Product qualified | Behaviour in the product, which is the strongest evidence of the four. | Authority and budget, which do not appear in usage data at all. |
The third row is the whole argument. Product usage is better evidence than the other two and it is evidence of a different thing. An engineer who has wired your API into a production system is demonstrating real value and may have no ability to sign anything.
The proxy problem
Most PQL thresholds are chosen in a room, by people reasoning about what a serious user would do. That produces milestones correlated with enthusiasm, which is not the same as correlated with revenue.
The two come apart most clearly in products with a technical user and a non-technical buyer. Heavy usage concentrates in the person who will never hold the budget, and the PQL queue fills with accounts that are genuinely engaged and structurally unable to convert. Sales works them, fails, and concludes the model does not work.
Finding the threshold instead of choosing it
The method is the same one that applies to any scoring model, and it fails for the same reason when the sample is small.
- Take the accounts that converted and look at what they did in the product before anybody spoke to them. Not what they did overall; what they did first.
- Take the accounts that used the product heavily and never converted. This is the half teams skip, and it is where the false signals are.
- Keep the behaviours that separate the two groups. Anything present in both is engagement rather than intent, however satisfying it is to measure.
- Check who performed the behaviour, not just that it happened. A milestone hit by an administrator means something different from the same milestone hit by an end user.
Under a few dozen conversions this exercise produces noise, and the honest move is to write a rule you can defend out loud and revisit it rather than fit a threshold to twelve data points.
The free tier changes the arithmetic
A free trial is a clock, so usage during it is compressed and reasonably comparable between accounts. A free tier has no clock, and somebody can sit on it productively for two years without ever intending to pay.
On a free tier the useful signal is almost never cumulative usage, because cumulative usage just measures tenure. It is a change in the rate, or contact with a limit: seats filling up, an export blocked, a second team appearing inside the same company. Those are moments where the product itself has raised the question of paying.
When not to build this
If nothing happens when an account crosses the line. A PQL that lands in a report rather than in somebody's queue is a metric. Routing has to read it or the definition is decorative.
If you cannot see individual behaviour reliably. PQLs depend on product analytics that attribute actions to accounts. Where that plumbing is broken the threshold is computed on partial data and is confidently wrong.
If the buyer is never the user. In products bought centrally and used by people with no say, product usage is a signal about adoption and a renewal risk indicator. It is not a buying signal, and dressing it as one sends sales to the wrong person.
Questions people ask
What is a product qualified lead?
An account or user whose behaviour inside the product suggests readiness to buy or expand. It only exists where people can use the product before paying.
How is a PQL different from an MQL?
An MQL rests on engagement with your marketing; a PQL rests on behaviour in the product. The product signal is stronger evidence, and it is still silent on budget and authority.
How do you set the PQL threshold?
Derive it by comparing accounts that converted against accounts that used the product heavily and did not. Thresholds chosen in a meeting track enthusiasm rather than revenue.
Why do our PQLs not convert?
The usual cause is that the threshold is being hit by someone who cannot authorise a purchase. Check who performed the behaviour, not only that it happened.
Do PQLs work with a free tier?
Yes, but cumulative usage mostly measures tenure there. Look for a change in rate or contact with a limit, where the product itself has raised the question of paying.
Or skip the search
Want the person who owns it after it ships?
If the work is a standing obligation rather than a bounded project, tell me which system you want built first. You get example profiles and a call with your pick before anything starts.
Placement runs through AYTalent. Engineers are employed and trained on the bench before they start with you.