The problem with MQLs in a PLG company is that they measure interest, not intent. A user who downloaded your whitepaper last month is interesting. A user who logged in 12 times this week, invited three teammates, and just hit your paywall twice is ready to talk. The Product Qualified Lead (PQL) is the mechanism that captures the second user and gets them to sales before the moment passes. This article explains how to define a PQL, score one, and act on the signals that matter.
PQL vs. MQL vs. SQL: what makes PQLs different
A Marketing Qualified Lead (MQL) is qualified by marketing behavior: content downloads, webinar attendance, email engagement, website visits. An MQL tells you that someone has shown interest in your category. It does not tell you whether they have experienced your product's value or whether they have a genuine commercial intent.
A Sales Qualified Lead (SQL) is qualified by a sales rep after a discovery conversation: they have confirmed budget, authority, need, and timeline. SQLs are expensive to generate because they require a human conversation. In a PLG motion, they represent the end of a qualification process that should have started much earlier.
A Product Qualified Lead (PQL) is qualified by product behavior. It is a free user who has reached a specific combination of in-product actions that historically predict conversion to paid. PQLs are cheaper than SQLs to generate (the product does the qualification work) and more reliable than MQLs (behavior is a stronger signal than content engagement). They represent the ideal entry point for sales in a PLG company.
The three pillars of a PQL definition
A robust PQL definition is built on three pillars. All three must be present for a user to qualify as a PQL — meeting only one or two of them produces low-conversion sales conversations.
Pillar 1: Activation milestone
The user has completed the core activation sequence. They have reached the aha moment — the point where they understand why the product is genuinely useful — and demonstrated this by completing the specific actions that define activation in your product.
Activation is product-specific, but the pattern is consistent: activation is not signup, it is not profile completion, and it is not a generic "first meaningful action." It is the completion of the specific sequence that turns a visitor into someone who understands and has used the product's core value proposition.
For a project management tool, activation might be: created a project, created at least 3 tasks, and assigned a task to another user. For a document collaboration tool: created a document, shared it with at least one person, and received a comment. For a data analytics tool: connected a data source and created a report that contains actual data.
Pillar 2: Usage intensity
Activation alone is not sufficient. A user who activated two months ago and has not logged in since is not a PQL. A PQL is a user who has activated and who is actively using the product at a frequency that demonstrates ongoing value delivery.
Usage intensity metrics:
- Sessions in the past 14 days: 3+ is a standard minimum threshold for considering a user active
- Days active in the past 30 days: Distributes usage over a broader time window to catch users who are consistent but not daily
- Core actions per session: Depth of engagement within each session — high depth users are more likely to convert than surface-level browsers
Pillar 3: Firmographic fit
Not every activated, engaged user is a commercially interesting PQL. A freelancer who genuinely loves your product but will never pay more than €15/month is a happy customer, not an enterprise PQL. Firmographic fit determines whether the user's organization has the commercial potential to justify a sales conversation.
Firmographic filters for PQL scoring:
- Company size: 50+ employees typically correlates with a budget holder who can approve €3,000+ annual contracts
- Industry: Match against your ICP industry list
- Funding signals: Recent funding rounds often correlate with budget availability and growth intent
- Job title: A decision-maker or manager role has more commercial relevance than an individual contributor role for enterprise deals
A practical PQL scoring model
The following scoring model is a starting framework. Calibrate the weights based on your own historical conversion data — the goal is to predict which users actually converted, then reverse-engineer the score thresholds that would have identified them.
Activation layer (up to 30 points):
- Activation milestone completed: +20 points
- Activation within 7 days of signup: +10 bonus points
Usage intensity layer (up to 30 points):
- 3-6 sessions in past 14 days: +10 points
- 7+ sessions in past 14 days: +20 points
- Used core feature 5+ times in past 30 days: +10 points
Firmographic layer (up to 25 points):
- Company 50-200 employees: +10 points
- Company 200+ employees: +20 points
- ICP industry match: +5 points
Commercial intent layer (up to 30 points):
- Paywall hit at least once: +15 points
- Enterprise feature accessed (SSO, admin settings): +15 points
- Invited 2+ teammates: +10 points
PQL threshold: 50+ points from the combined score triggers a PQL designation and sales workflow. Hot PQL threshold: 70+ points or any single trigger from the hot trigger list below.
Hot PQL triggers: when to act immediately
Some signals are strong enough to bypass the cumulative scoring model and trigger immediate sales action. These are events that represent a concentrated, time-sensitive buying intent signal that should not wait for the daily batch scoring job.
Paywall hit: A user hits a usage limit or tries to access a paid feature and is blocked. This is explicit commercial intent. The user wants to do something and cannot without paying. Response window: within 4 hours.
Enterprise feature access attempt: A user navigates to SSO configuration, tries to set up SCIM provisioning, or accesses the audit log page — features that are enterprise-gated. This signals that the user is evaluating the product for organizational deployment. Response window: within 24 hours.
Team invitation above threshold: A user sends 5 or more invitations in a single week. This signals active organizational expansion — the product is being deployed beyond individual use. Response window: within 24 hours.
Domain-level adoption spike: Multiple users from the same company domain activate within a short time window (3+ activations from the same domain in 14 days). This signals grassroots adoption that is now approaching critical mass. Response window: 48 hours — identify the senior-most user from the domain and initiate an account-level conversation.
The sales conversation with a PQL
The PQL changes the nature of the sales conversation. A rep calling a PQL is not starting from zero — they are starting from a position of proven value delivery.
The opening frame: "I can see you and your team have been using [Product] to [specific use case based on feature data]. I wanted to reach out because some of what you are doing is typically where teams find it useful to talk about how [enterprise-level capability] would fit — specifically [relevant detail from product data]."
The key principle: reference specific product behavior, not generic interest. The user can tell the difference between a rep who has done their homework and one who is making a canned outreach. Product context is what makes the difference.
For the full PQL pipeline setup in HubSpot — including workflow configurations and reporting — see the article on product data in HubSpot.