Product Qualified Lead (PQL)
A Product Qualified Lead is a user who has experienced real value from a product, usually through a free trial or freemium plan, and shows usage signals indicating they are likely to convert to a paid plan.
Key takeaways
- PQL status comes from product telemetry, not from anything the user self-reports.
- The activation milestone should separate accounts that retained from accounts that drifted away.
- Workspace-level signals beat user-level ones, since one active user proves little.
- Pair the usage milestone with an account attribute that justifies a human touch.
- Renamed or dropped events after a release silently change who qualifies.
In depth
A PQL is defined entirely by events the product emits, not by anything the user says. The chain runs in three parts: instrument the actions that carry meaning, choose an activation milestone that historically separated accounts which stayed from accounts which drifted away, and set a threshold combining that milestone with the shape of the account. Because the signal comes from usage, the unit is normally the workspace rather than the person, since one enthusiastic user inside a dormant team is not a buying signal at all.
Choosing the milestone is the whole design decision. A milestone set too shallow, such as completing signup or logging in once, fires for everyone and carries no information. Set too deep, it fires after the user has already made up their mind and the outreach arrives late. The useful test is whether accounts that reached it retained at a visibly different rate from those that did not. Instrumentation quality is the second constraint, because renamed or duplicated events silently change who qualifies.
Working definitions pair a behavioural milestone with an account attribute that justifies human effort: seat count, a corporate email domain, or a plan limit being approached. The routing decision is not only whether to reach out but with what: an in-app upgrade prompt for small accounts, a person for large ones. A scorecard quiz placed before or during signup adds the intent context telemetry cannot see, such as the intended use case, so identical usage patterns can be read differently by segment.
Product signals report what happened, never why. Heavy trial usage can mean a serious evaluation running to a deadline, an agency testing on a client's behalf, or someone extracting one-off value they never intend to pay for. The model also fails where the free tier is genuinely sufficient, because those accounts activate, retain and still never convert. And any definition breaks the moment onboarding changes, since the events being counted move or disappear with the release.
Example in practice
How to measure it
The core comparison is conversion to paid for accounts that crossed the threshold against accounts that did not. The ratio between those two rates is the lift the model provides, and if it is close to one the milestone is not carrying information. Measure coverage as well: the share of new paying accounts that were flagged as PQLs beforehand, which reveals buyers the definition is missing entirely.
Then measure the operational half. Track the time between the threshold firing and the first outreach, since the value of a usage signal decays while the user is still in the product. Watch the share of flagged accounts that churn shortly after paying, because a milestone that predicts purchase but not retention will inflate short-term numbers and damage the next renewal cycle.
Common mistakes
The most common error is treating signup completion as activation. Alerts then fire for everyone who creates an account, sales works a queue of tyre-kickers, and within a quarter the notifications are ignored. Choose the milestone empirically instead: take past accounts, split them by whether they converted, and find the action that most sharply divides the two groups. Then confirm the milestone still divides them on a more recent cohort.
The second is sending an alert with no context. A rep receives a notification that an account crossed the threshold, has no idea which features were used or how many people were in the workspace, and opens with a generic upgrade pitch. Attach the event trail, the seat count and the limit being approached to every alert, so the first message references what the team was actually trying to do.
Frequently asked questions
How is a PQL different from an MQL?
An MQL is qualified by marketing engagement such as content downloads or webinar attendance, while a PQL is qualified by hands-on product usage. PQLs tend to convert faster because they have already experienced value rather than just expressed interest.
What signals define a PQL?
Typical signals include reaching an activation milestone, repeat usage of core features, inviting teammates, and account characteristics like seat count. The right mix depends on which behaviors historically predicted paid conversion in your product.
Can a quiz funnel help generate better PQLs?
Yes. A scorecard quiz placed before the trial can pre-qualify visitors by use case and team size, so the people who enter your product are more likely to activate. This raises the quality of the PQLs that emerge downstream.
How do you choose a PQL activation milestone?
Take your past accounts, split them by whether they became paying customers, and look for the action that divides the groups most sharply. Good candidates are actions that require real setup effort, such as inviting a colleague, connecting a data source, or completing a core workflow end to end. Validate the milestone against a recent cohort before wiring it to alerts.
Should PQLs be identified at the user or account level?
At the account or workspace level in almost every B2B case, because purchases are made by teams. A single power user in an otherwise empty workspace is a weak signal, whereas three colleagues using the product in the same week is strong. Keep user-level detail for deciding who to contact once the account itself qualifies.
What should happen when an account becomes a PQL?
Route it to the cheapest touch that fits its size. Small accounts get an in-product prompt or an automated email referencing what they built; larger accounts get a person, with the usage detail attached. Treating every PQL as a sales call wastes capacity on accounts whose lifetime value cannot fund the conversation.
Do PQLs work without a free trial or free plan?
Not in their usual form, since the model needs pre-purchase usage to observe. Products without free access can approximate it with sandbox environments, interactive demos or guided product tours that emit similar events. Otherwise the equivalent signals come from marketing behaviour and stated fit rather than from the product itself.
How does a generous free plan affect PQL quality?
It weakens the link between activation and revenue. When the free tier covers the whole job for a segment, those accounts activate deeply, retain well and never upgrade, so they clog the qualified queue. Add a constraint signal to the definition, such as approaching a usage limit or needing a feature the free plan excludes.
What usually breaks a PQL model?
Instrumentation drift. An onboarding redesign renames an event, a tracking call is dropped in a refactor, or a step is merged into another, and the milestone stops firing without anyone noticing. Monitor the daily count of qualifying events as a health metric, and review the definition whenever the signup or onboarding flow is changed.