A product qualified lead (PQL) is a prospect who has engaged meaningfully with your product — typically through a free trial or freemium plan — and crossed activation thresholds that predict conversion. Unlike MQLs (who showed interest in content), PQLs have demonstrated actual value from the product. They convert at 25-30% compared to 2-5% for MQLs, according to OpenView Partners research.
In product-led growth (PLG) models, the product does the selling before sales does. A PQL is the signal that the product has done its job — the prospect is ready for a conversation.
What is a Product Qualified Lead (PQL)?
A PQL is a free trial or freemium user who has hit a set of in-product behaviors that your data shows correlate strongly with conversion to paid. The definition is company-specific — what counts as a PQL at a CRM tool differs from what counts at a design platform — but the logic is always the same: certain actions inside the product predict that a user is getting value and is therefore ready to buy.
Three components define every PQL framework:
- Activation threshold — the specific in-product actions a user must complete (e.g., imported 50+ contacts, invited 3 teammates, run a report)
- Time window — within how many days of signup those actions must occur (commonly 7-14 days)
- Frequency signal — how many times a core feature was used (prevents one-time curiosity from qualifying)
PQLs convert at 5-10x the rate of MQLs. Companies that route PQL signals to sales within 24 hours see meaningfully higher close rates than those with delayed follow-up. The aha moment has an expiration date.
Why PQLs matter for product-led businesses
Traditional lead qualification asks "is this person interested?" PQL qualification asks "has this person already gotten value?" The distinction changes everything about sales efficiency:
- Higher conversion rates. PQLs have already completed a proof of concept inside your product. The sales conversation skips straight to pricing and expansion — not whether the product works.
- Shorter sales cycles. No discovery call needed to understand the use case. The product data already tells the sales rep what the prospect built, which features they used, and where they got stuck.
- Lower acquisition cost. You're not spending sales bandwidth on unqualified curiosity. Every PQL handoff has a data-backed reason to believe the deal will close.
- Better retention. Users who qualify as PQLs before converting are already habituated to the product. They churn at lower rates because they chose to buy based on value experienced, not a salesperson's pitch.
- Feedback loop for product. Tracking what actions create PQLs tells your product team exactly which features drive revenue — and which onboarding steps to optimize first.
How PQL scoring works
Building a PQL model is a four-step process. Skip step one and the rest falls apart.
- Identify activation behaviors from historical data. Pull your conversion data for the last 12 months. Look at users who converted to paid — what did they do in their first 7-14 days that non-converters didn't? Common signals: invited teammates, connected an integration, created a first project, ran a first export. These are your candidate activation events.
- Build a scoring model. Assign point values to each activation event weighted by how strongly each correlates with conversion. A user who completes your three highest-value actions scores higher than one who completes ten low-signal actions. Set a threshold score that defines PQL status.
- Route to sales with context. When a user crosses the PQL threshold, the alert sent to the sales rep should include: which activation events fired, what features they've used, how many times they logged in, and any firmographic data (company size, role). Don't just say "PQL triggered" — give the rep a call script.
- Refine quarterly. PQL definitions drift. Product changes, onboarding flows change, buyer personas change. Review your model every quarter against actual conversion data and adjust thresholds accordingly.
PQL vs MQL vs SQL — comparison
| Lead Type | Qualification signal | Conversion rate | Sales cycle |
|---|---|---|---|
| PQL | In-product activation (feature use, invites, imports) | 25-30% | Short — already proven value |
| MQL | Marketing engagement (content, email, ads) | 2-5% | Long — needs full sales motion |
| SQL | Sales-confirmed fit (budget, authority, need, timeline) | 40-60% | Short — sales-qualified before outreach |
Real PQL examples
Here is how two product-led companies define and act on PQLs in practice.
Example 1 — CRM free trial
A CRM tool defines its PQL threshold as: imported 50+ contacts AND created at least one pipeline AND logged in on 3+ separate days within 14 days of signup. Users who hit all three criteria convert at 28% — four times the baseline. When the threshold fires, the sales rep gets an alert with the user's contact data, their company size (from Clearbit enrichment), and which CRM features they used. The first outreach email mentions the specific pipeline they built.
Example 2 — Freemium design platform
A design tool tracks collaboration as its primary PQL signal. Any free user who shares a design with an external collaborator AND receives at least one comment back hits PQL status. The logic: collaboration requires a real use case, a real team, and real work product. That combination signals organizational need for a paid seat. This single signal achieves a 22% conversion rate on outreach.
PQL vs activation rate — which metric to optimize first
Optimize activation rate first when
- Few users are reaching your PQL threshold
- Trial-to-PQL conversion is under 15%
- Onboarding is incomplete or confusing
- Users are churning before hitting activation events
- Product has too many steps before first value moment
Optimize PQL-to-paid conversion when
- Activation rate is healthy (15%+)
- PQLs exist but sales isn't following up fast enough
- Sales team lacks context about what the PQL did in-product
- PQL definition is too broad (many qualify, few convert)
- You need to tighten the threshold with more specific signals
6 best practices for PQL programs
- Start with conversion data, not intuition. The most common mistake is defining PQL thresholds based on what feels like meaningful product use rather than what actually predicts conversion. Run the analysis first.
- Use 2-3 activation signals, not 10. Complex scoring models are harder to maintain and harder for sales to explain on calls. A tight set of high-signal events outperforms a sprawling rubric.
- Follow up within 24 hours. PQL intent has a half-life. A user who hit their aha moment on Tuesday is 60-70% less likely to respond positively to outreach by Friday.
- Give sales the product context, not just the alert. "User X hit PQL threshold" is less actionable than "User X built a 4-stage pipeline, imported 82 contacts, and logged in 5 days in a row." Write the data into the CRM automatically.
- Never route PQLs to a mass email sequence. PQLs deserve a personalized, product-specific touch. Reference what they built. Generic nurture sequences signal that you didn't look at their account.
- Review your PQL definition quarterly. Product changes create new activation events. Old signals may lose predictive power. Treat PQL definition as a living model, not a one-time configuration.
A user who opens your product 20 times in their first week is not necessarily a PQL. Power exploration is not the same as activation. Track completion of specific valuable actions — like connecting an integration, inviting a colleague, or completing a core workflow — rather than raw session count.
Common PQL mistakes to avoid
- Defining PQL thresholds without data — results in a model that qualifies the wrong people and wastes sales time.
- Too many criteria — a 10-point activation checklist lets great buyers fall through because they took a different path to value.
- Slow follow-up — PQL intent peaks at the moment of activation, not three days later.
- Not passing product context to sales — reps who can't reference specific in-product actions sound generic and lose the personalization advantage PQLs offer.
- Never updating the model — a PQL definition from two years ago reflects a different product and a different buyer. Refresh it.
- Confusing PQL with free trial signup — every trial signup is not a PQL. Most aren't. The threshold exists to separate genuine activation from casual browsing.
Frequently asked questions
An MQL qualifies based on content engagement — downloading a whitepaper, attending a webinar, clicking an email. A PQL qualifies based on actual product usage. PQLs show they get value from the product; MQLs show interest in the topic. PQLs convert at 25-30% vs 2-5% for MQLs.
Start with 2-3 key behaviors that correlate with conversion in your historical data. Too many criteria create false negatives (real buyers don't qualify); too few create false positives (sales wastes time on unready prospects).
No. PQLs require product usage data, which means the prospect must have access to the product through a free trial, freemium plan, or pilot. Without usage data, you have an MQL at best.
Within 24 hours. PQLs contacted within the same day they hit activation thresholds convert significantly higher than those contacted days later. Momentum from the aha moment fades fast.
Product analytics platforms like Mixpanel, Amplitude, or Heap track in-app behavior. CRMs like HubSpot or Salesforce can receive these signals via webhooks or native integrations to trigger sales alerts when a user hits PQL thresholds.
Related glossary terms
Sources
