A product-qualified lead is a user who has already experienced value in the product and is likely to convert to a paying customer.
Product-qualified leads (PQLs) are the PLG equivalent of MQLs and SQLs — free-tier users who have hit specific in-product milestones that predict conversion likelihood. The idea is elegant: instead of guessing which prospects will buy based on demographic fit, watch which ones are actually using the product and route them to sales at the moment they've experienced value. Executed well, PQLs deliver conversion rates 3-5x higher than cold outbound and cost a fraction of paid acquisition. Executed poorly, they become a firehose of low-quality leads that overwhelm sales without producing revenue.
A PQL isn't just any user who signed up — it's a user who has experienced enough value that a sales conversation is likely productive. Definition varies by product but usually combines: (1) usage depth (used 3+ core features, or hit 5+ sessions in 14 days), (2) team behavior (invited 2+ collaborators, or created shared assets), (3) integration completeness (connected 1+ data source), and (4) contextual fit (company size, role, industry from enriched signup data). Wrong definition (too loose): every free signup is a PQL — floods sales with no better than random conversion. Wrong definition (too tight): only 0.5% of signups qualify — starves sales of leads. Aim for 5-15% of signups qualifying, with 15-30% conversion of PQLs to paid.
Two schools of thought. Binary: user either meets the PQL criteria or doesn't; sales works only the yes column. Simple, easy to explain, easy to trigger. Scoring: users accumulate points across dozens of behaviors; PQLs are the top 10-20% by score. More nuanced, harder to maintain, prone to score drift. Binary works better for most companies below Series B. Scoring becomes worth the complexity when volume is high enough (500+ signups/month) that finer differentiation actually matters.
When a user hits PQL threshold, the handoff must be fast (within hours, not days) and contextual (the sales rep sees exactly what the user has done in-product). Typical stack: product event fires when threshold hit → data pipeline routes to CRM → SDR or AE gets an alert with the user's usage summary → outreach references the specific actions ('saw you connected Salesforce and built 3 dashboards — how's it going?'). Generic 'noticed you signed up' outreach kills conversion; contextual outreach doubles or triples it.
(1) Sales works PQLs like traditional outbound leads, ignoring product context — same generic pitch, same low conversion. (2) PQL definition set once and never revisited — over time the definition drifts from actual conversion behavior. (3) No feedback loop from sales back to product on which PQLs actually closed — the definition never improves. (4) Marketing and sales fight over ownership — was this deal marketing-sourced or product-sourced? Resolve with clear attribution rules upfront. (5) PQLs bypass the free-tier product journey that would naturally convert users — over-aggressive PQL contact reduces conversion vs. letting the product do the work.
Track: (1) PQL rate — % of signups that become PQLs. (2) PQL-to-opportunity rate — % of PQLs that become qualified opportunities. (3) PQL-to-close rate — % of PQLs that become customers. (4) PQL velocity — median time from signup to PQL to close. (5) PQL segment performance — which signup sources produce the highest-converting PQLs? Compare PQL cohorts against non-PQL free users who converted organically to isolate the PQL program's actual lift.
Investor directory · Fundraising library · Articles A–Z · Company funding database