How to define product-qualified leads (PQLs) for your SaaS product

Most SaaS sales teams still rely on marketing-qualified leads (MQLs) -- people who downloaded a whitepaper, attended a webinar, or filled out a form. These signals tell you someone is interested in your category. They tell you almost nothing about whether that person will become a paying customer.

Product-qualified leads (PQLs) flip this model. Instead of measuring marketing engagement, PQLs measure product engagement. A product-qualified lead is a user who has experienced meaningful value in your product and exhibits behaviors that correlate with conversion.

The result: PQLs convert to paid customers at 5-6x the rate of MQLs. This guide walks through how to define PQL criteria for your specific product, build a scoring model, and route qualified leads to sales effectively.

PQL vs. MQL vs. SQL: understanding the differences

Before building your PQL model, it helps to understand how these lead types differ:

The key insight is that PQLs sit between MQLs and SQLs in the funnel. They have gone beyond showing interest -- they have actually used the product. But they have not yet been qualified by a human for budget, authority, and timeline.

PQLs apply when you have a free trial or self-serve signup where users interact with your product before talking to sales. They do not apply in pure enterprise sales where every deal starts with a demo, or very early-stage products without enough data to identify patterns.

Step 1: Identify your activation events

The foundation of any PQL model is understanding what activation looks like in your product. Activation is the moment a user first experiences the core value you deliver.

Start by listing every meaningful action a user can take in your product. Then filter down to the actions that represent value delivered, not just feature used.

Examples by product type:

• Project management tool: Created a project, added 3+ tasks, invited a team member
• Analytics platform: Connected a data source, created a dashboard, shared a report
• Developer tool: Installed the SDK, made a successful API call, deployed to production
• Collaboration tool: Created a shared workspace, sent 10+ messages, uploaded a file

The aha moment is the specific point where a user "gets it." For Dropbox, it was saving a file to the shared folder. For Facebook, it was connecting with 7 friends in 10 days. Your PQL model needs to capture the equivalent moment for your product.

How to find your activation events:

1. Pull a list of users who converted to paid in the last 6 months
2. Pull a list of users who signed up but churned or went inactive
3. Compare the product actions each group took in their first 7-14 days
4. Identify the actions that appear significantly more often in the converted group
5. Rank those actions by the difference in frequency between the two groups

The actions with the biggest gap between converters and churners are your activation events.

Step 2: Analyze what successful customers did before converting

Activation events tell you who is getting value. But PQLs need to predict who is ready to buy. These are related but not identical.

Pull conversion data and look at the 30 days before each conversion event. Track:

• Which features they used -- not just activation features, but the broader set
• How frequently they logged in -- daily users convert at much higher rates than weekly users
• Team behavior -- did they invite others? How many active users on the account?
• Depth of usage -- are they using advanced features or just the basics?
• Engagement trend -- is usage increasing, flat, or declining?

You are looking for the combination of signals that appears in accounts that convert but does not appear in accounts that stay free. This is your PQL signal set.

Step 3: Build scoring criteria

A PQL scoring model assigns points to different product usage signals and sums them into a total score. Here is a template you can adapt:

PQL scoring model template

Usage frequency (0-30 points):

• Logged in 1-2 days in last 7 days: 5 points
• Logged in 3-4 days in last 7 days: 15 points
• Logged in 5+ days in last 7 days: 30 points

Activation milestones (0-25 points):

• Completed onboarding flow: 5 points
• Reached primary activation event: 15 points
• Reached secondary activation event: 25 points

Team signals (0-20 points):

• Invited 1 team member: 5 points
• 2-4 active team members: 10 points
• 5+ active team members: 20 points

Feature depth (0-15 points):

• Used 1-2 features: 0 points
• Used 3-5 features: 8 points
• Used 6+ features or advanced features: 15 points

Intent signals (0-10 points):

• Visited pricing page: 3 points
• Viewed billing or upgrade page: 5 points
• Started checkout but did not complete: 10 points

Firmographic data (0-10 points, if available):

• Company size matches ICP: 5 points
• Industry matches ICP: 3 points
• Role matches buyer persona: 2 points

Total possible: 110 points

This model combines product usage (the primary signal), intent behavior (the directional signal), and firmographic fit (the contextual signal). The weighting should reflect your actual conversion data -- if team size is the strongest predictor, weight it more heavily.

Step 4: Set thresholds

Thresholds determine when a lead becomes "product-qualified." Setting them correctly is critical -- too low and you flood sales with unqualified leads, too high and you miss opportunities.

How to set initial thresholds:

1. Score your last 100 converted customers retroactively using your model
2. Score your last 100 churned or inactive accounts
3. Find the score range where converters are concentrated but churners are not
4. Set your PQL threshold at the lower end of that range

Typical threshold structure:

• Below threshold (e.g., under 40 points): Not product-qualified. Continue nurturing with in-app guidance and email sequences.
• PQL threshold (e.g., 40-70 points): Product-qualified. Route to sales for outreach.
• High-intent PQL (e.g., 70+ points): Hot lead. Prioritize immediate outreach.

Important: Revisit thresholds quarterly. As your product changes and your customer base evolves, the signals that predict conversion will shift. A threshold that worked six months ago may be too loose or too tight today.

Step 5: Build routing rules

A PQL without a clear routing path is wasted signal. Define exactly what happens when a lead crosses each threshold:

Self-serve path (below PQL threshold but activated):

• Show in-app upgrade prompts at contextual moments
• Send targeted email with relevant use cases
• Display feature comparison highlighting premium capabilities

Standard PQL (crossed threshold):

• Alert assigned sales rep or round-robin to available rep
• Include PQL score, key actions taken, account context, and recommended talking points
• Set SLA for first outreach (e.g., within 4 hours during business hours)

High-intent PQL:

• Immediate notification to sales (Slack alert, SMS, or CRM task)
• Include full usage history and specific features they engaged with
• SLA: outreach within 1 hour

Enterprise PQL (high score + large company):

• Route to enterprise AE or account team
• Include firmographic context and potential deal size
• Coordinate with CSM if the account already has a relationship

The handoff matters

The worst thing you can do with a PQL is hand it to a rep who then sends a generic "just checking in" email. Use the product context you have:

Bad: "Hi, I noticed you signed up for our product. Would you like to schedule a demo?"

Good: "Hi, I saw your team has created 12 dashboards and connected 3 data sources this week. Teams at your stage often get value from our automated alerting feature -- would it help if I walked you through how [similar company] set it up?"

PQL examples by product type

• Project management: PQL criteria include 3+ active team members, 20+ tasks created, 2+ integrations connected, weekly active usage
• Analytics platform: 3+ dashboards created, data refreshed daily, shared a report externally, visited pricing page
• Developer tool: 100+ API calls, production deployment, multiple team members using SDK
• Collaboration tool: Daily active usage, 5+ team members, 3+ channels created, external guests invited

Common mistakes in PQL programs

• Too many criteria: If your PQL definition has 15 criteria, it is too complex. Start with 5-6 signals covering usage frequency, activation depth, and team adoption.
• Not updating criteria: PQL criteria that worked at launch will not work at scale. Review conversion data quarterly.
• Ignoring firmographic data: A solo developer using your tool heavily is a different opportunity than a VP of Engineering at a 500-person company. Include company size and role as secondary signals.
• Treating all PQLs the same: A user who crossed threshold yesterday differs from one above threshold for three weeks. Recency matters.
• No feedback loop with sales: Build a mechanism for reps to mark PQLs as "good lead" or "not ready" and use that data to refine criteria.

Getting started

1. Export your user data. Pull product usage data for your last 200 signups, including which ones converted.
2. Find patterns manually. Use a spreadsheet to compare behaviors between converters and non-converters.
3. Define 3-5 criteria. Pick the signals with the clearest separation between the groups.
4. Set a threshold. Start conservative so sales is not overwhelmed.
5. Route leads manually. Before building automation, have someone review PQLs daily and assign them.
6. Measure and iterate. Track PQL-to-paid conversion rate weekly. Adjust criteria monthly.

Tools like Skene can accelerate this by surfacing usage patterns that predict conversion. But the framework above works with any analytics setup, even a spreadsheet. The companies that win with product-led growth treat product usage data as their most valuable sales signal.