Skene
PLG term

Product-qualified lead (PQL)

A product-qualified lead (PQL) is a lead whose in-product behavior indicates high buying intent, such as reaching a usage threshold or completing a key workflow. Unlike marketing-qualified leads (MQLs) based on content engagement or sales-qualified leads (SQLs) based on sales conversations, PQLs are identified by what users actually do in your product. In a PLG motion, PQLs are the primary handoff point from product-led acquisition to sales-assisted conversion, making them a critical bridge between self-serve growth and human-assisted expansion.

Funnels
Also called: PQL, Product qualified lead, Usage-qualified lead
About this term

This page is part of the Skene PLG glossary. Use it as a reference when writing specs, dashboards, or playbooks that rely on this concept.

Canonical glossary index: /resources/glossary

Definition

A product-qualified lead (PQL) is a lead whose in-product behavior indicates high buying intent, such as reaching a usage threshold or completing a key workflow.

PQLs represent users or accounts that have demonstrated value realization through their actions, not just interest through form fills or content downloads.

PQL vs MQL vs SQL

MQLs (marketing-qualified leads) are based on marketing engagement: downloading whitepapers, attending webinars, or visiting pricing pages.

SQLs (sales-qualified leads) are based on sales judgment after discovery calls or demos.

PQLs are based on actual product usage data, making them the most reliable indicator of intent in a PLG model.

Examples of PQL signals

Examples include: inviting multiple teammates, hitting plan limits, or consistently returning to core value-driving features.

For a collaboration tool: adding 5+ team members. For an analytics product: creating multiple dashboards. For a developer tool: making production API calls.

Negative signals matter too—accounts that reach PQL thresholds but then go dormant may need nurturing rather than sales outreach.

Building a PQL model

A useful PQL model combines quantitative usage thresholds (such as number of projects, events, or seats) with qualitative fit data such as role or company size.

Over time you can refine your PQL model by comparing which behaviors show up most often in accounts that convert or expand.

Start simple—a single behavior threshold—and add complexity only when you have data to justify it.

Operationalizing PQLs

Route PQL alerts to sales in real-time so they can reach out while the user is actively engaged.

Provide sales with context: what the user has done, what plan limits they are approaching, and what their company profile looks like.

Track PQL-to-opportunity and PQL-to-close rates to validate and refine your PQL definition.

Implementation notes

  • Define PQL criteria based on historical conversion data—look at what converted accounts did before buying.
  • Avoid setting PQL thresholds too low (creating noise) or too high (missing opportunities).
  • Combine usage signals with firmographic data (company size, industry) for better lead scoring.