# PQL scoring and routing

> How to define a product qualified lead from real usage data, score it, and route it to sales without burning your self serve funnel or annoying free users.

Source: https://saas-marketing.net/guides/product-qualified-lead-scoring/
Topic: SaaS Lead Generation
Type: guide
Published: 2026-09-11
Last updated: 2026-09-11
Publisher: SaaS Marketing (saas-marketing.net)
License: CC BY 4.0. Quote or republish with attribution and a link to https://saas-marketing.net/guides/product-qualified-lead-scoring/

## Short answer

A product qualified lead score ranks accounts by usage behaviour that historically predicts paid conversion. Build it by comparing converted and non-converted cohorts to find the two or three events that separate them, set thresholds at the account level rather than the user level, apply a recency window of 7 to 14 days, then route by expected account value: self serve only, automated nudge, or human outreach. PQLs should be rarer than MQLs.

## Key takeaways

- Derive PQL criteria from cohort comparison, not from a workshop; intuition picks the wrong events roughly half the time.
- Score at the account level, because three users in one company is a signal and one user across three sessions is not.
- If your PQL volume matches your signup volume you have defined an active user, not a lead.
- Apply a recency window: behaviour from 40 days ago is history, not intent.
- Route by expected account value, since human outreach on a $600 ACV account loses money even when it converts.
- Track false positive cost in sales hours wasted, not just PQL to paid rate.

---

Most PQL models fail for the same reason. Somebody picks the events that feel important in a meeting, sales gets flooded with accounts that were never going to buy, and within a quarter the flag is ignored. The fix isn't a better tool. It's deriving the definition from conversion data and then being ruthless about how few accounts qualify.

This guide covers finding the predictive events, building the threshold, routing by value, and measuring the false positives that quietly destroy trust.

## Which usage events actually predict paid conversion

Find them by comparing cohorts, not by asking the product team. Export every account that converted to paid in the last two quarters and every account that signed up in the same window and didn't. Then count how often each cohort performed each tracked event in its first 30 days.

You're looking for lift, not volume. An event that 90 percent of both groups performed tells you nothing, even though it'll be the most common event in your dataset. Keep events where the converted group is three times or more likely to have done the thing.

| Event | Converted accounts | Non-converted | Lift | Keep? |
|---|---|---|---|---|
| Completed signup form | 100% | 100% | 1.0x | No |
| Viewed dashboard | 94% | 88% | 1.1x | No |
| Invited second seat | 71% | 14% | 5.1x | Yes |
| Connected an integration | 63% | 11% | 5.7x | Yes |
| Exported a report twice or more | 58% | 19% | 3.1x | Yes |
| Read the docs | 41% | 37% | 1.1x | No |
| Hit 70% of plan limit | 34% | 4% | 8.5x | Yes |

That table is illustrative structure, not measured data, but the shape is what you'll see. Three or four events survive. The rest are noise dressed up as engagement.

Logins. Login count feels like the purest signal of engagement and it's usually one of the weakest predictors, because free users with no intent log in out of curiosity and serious evaluators sometimes do all their work in two long sessions. Use it as a diagnostic, never as a scoring criterion.

## Four signal patterns that recur across B2B SaaS

The specific events differ by product, the patterns don't. Four show up again and again.

Multiple seats invited. One person exploring is evaluation. Three people in the same account is a project with internal momentum, which is why Slack, Figma and Notion all treat seat expansion as the central growth motion.

An integration or data source connected. This is the highest-effort action most users take, and effort is intent. Someone who has connected their CRM has made a small internal commitment and told a colleague about you.

A usage limit approached. Hitting 70 to 90 percent of a plan's cap is the cleanest commercial signal in the whole model, because the product itself is creating the buying conversation.

A high value action repeated across sessions. Once is a trial. Four times across three weeks is a workflow. Repetition separates evaluation from habit better than any single event.

**5x to 8x** Typical conversion lift on seat invite and limit-approach events versus baseline signups

## Building the definition: thresholds, account rollup, recency

Three design decisions turn events into a usable flag, and teams get the middle one wrong most often.

Threshold. Don't build a 100 point weighted score on your first attempt. Start with a rule: any two of the four qualifying events within the window. Weighted scores are harder to explain to sales, and a rule sales can recite is worth more than a model they can't audit.

Account rollup. Score the account, not the user. Two users each doing one qualifying action is a stronger signal than one user doing both, and a user-level score misses that entirely. Roll individual events up to the company domain and deduplicate free email domains carefully, because gmail.com will otherwise become your largest account.

Recency. Put a 7 to 14 day window on it. An integration connected 40 days ago with no activity since is not an intent signal, it's a historical fact. Without decay, your PQL list becomes a slowly growing pile of accounts that once looked interesting.

**Building the model in two weeks**

## Routing: who gets a human, who gets an email, who gets nothing

Route on expected account value, not on score. A perfect PQL at a 4-person company with a $600 expected annual value should never reach a salesperson, because a single 30 minute call plus follow-up costs more than the account is worth in year one.

The hold lane matters. Plenty of accounts use the product heavily and will never be worth a sales conversation: agencies, students, single-person consultancies. Flagging them and leaving them alone protects both the sales team's time and the user's experience.

Speed matters most in the top lane. A PQL is a moment, and the moment passes. Four hours is a reasonable service level; next-day follow-up on a limit-approach signal arrives after the person has either upgraded or moved on. Tooling for the routing itself is usually your CRM plus a workflow layer, and the mechanics are covered further in [lead scoring for B2B SaaS](/guides/lead-scoring-model-saas/).

## The handoff: what the first message says and when it lands

The worst PQL outreach opens with "I noticed you've been using our product". It's creepy and it's generic at the same time, which is impressive. The good version references the specific thing the account did, and offers something that only makes sense given that action.

If the trigger was a seat invite, the message is about getting the rest of the team set up. If it was an integration connect, it's about the configuration step people usually get wrong. If it was a limit approach, it's about which plan fits their volume and whether annual billing saves them anything.

Sales does not need to know an account scored 78. They need to know that three people joined last Tuesday and the Salesforce integration went live on Thursday. Pass the evidence into the CRM record, not the number.

Timing follows the trigger too. Limit-approach signals are urgent. Seat invites are urgent within a day. Integration connects can wait until the user has actually used the integration once, because reaching out mid-setup interrupts the exact behaviour you want.

There's a full library of trigger-specific messages in the [product qualified lead email plays](/playbooks/product-qualified-lead-email-plays/), and a deeper model-building walkthrough in [building a PQL scoring model](/guides/pql-scoring-model/).

## Measurement: PQL to paid, and the cost of being wrong

Two numbers, and the second one is the one that saves the program.

PQL to paid conversion rate is the headline. Whatever it is, it must be meaningfully higher than your baseline signup-to-paid rate. If your signups convert at 4 percent and your PQLs convert at 6 percent, you have not built a lead score, you have built a slightly biased sample.

False positive cost is the number nobody tracks. Take the PQLs that went nowhere, multiply by the hours sales spent on each, and price it at loaded cost. A model producing 400 PQLs a month at 25 percent conversion is burning 300 accounts of sales attention. At 40 minutes each that's 200 hours a month, which is more than a full-time person.

| Metric | What good looks like | Where it breaks |
|---|---|---|
| PQL to opportunity | 20% to 40% | Below 15% means the threshold is too loose |
| PQL to paid | At least 3x your baseline signup-to-paid rate | Parity means the flag adds nothing |
| PQL volume as share of signups | 3% to 12% | Above 20% you have defined active users |
| Time from PQL to first touch | Under 4 hours in the top lane | Over 24 hours and the signal is stale |
| Sales hours per closed PQL deal | Falling quarter over quarter | Rising means false positives are growing |

Those bands are practitioner ranges, not measured benchmarks. Compare them against your own history before treating them as targets.

## The position worth defending: PQLs should be rare

If you take one thing from this page, take this. PQLs should be rarer than your MQLs, and considerably rarer than your signups. The instinct in every organisation runs the other way, because a bigger number looks like a better quarter and because marketing gets measured on volume.

Resist it. The moment sales works fifty PQLs and closes two, the flag loses credibility, and credibility is the only thing that makes the routing work. A tight definition that surfaces 30 excellent accounts a month beats a loose one that surfaces 400 mediocre ones, even though the loose one looks better on a slide.

The distinction between the two flags is worth being precise about, which is why it's covered separately in [MQL vs PQL in B2B SaaS](/comparisons/mql-vs-pql/) and in [MQL vs PQL generation](/comparisons/mql-vs-pql/). For definitions, see [product qualified lead](/glossary/product-qualified-lead/), the related [PQL metrics](/glossary/product-qualified-lead/) entry and [PQL generation](/glossary/product-qualified-lead/).

## What to do this week

Pull the cohort comparison. Don't design anything until you've seen the lift table, because the events that survive will not be the ones you'd have guessed and that surprise is the point of the exercise.

Then write the rule in one sentence, backtest it against last quarter, and check what share of signups qualify. If it's over 15 percent, tighten it before anyone in sales sees the output. The rest of the funnel context sits in the [SaaS lead generation hub](/saas-lead-generation/).

## Frequently asked questions

### What is a product qualified lead?

A product qualified lead is an account whose usage of your product has crossed a threshold that historically predicts conversion to paid or expansion. Unlike an MQL, which is scored on fit and content engagement, a PQL is scored on what the account has actually done inside the product, which makes it a far stronger predictor of revenue.

### How do you define PQL criteria?

Export two cohorts, accounts that converted to paid and accounts that signed up and did not, then compare event frequencies across their first 14 to 30 days. Keep events where the converted group is at least three times more likely to have performed the action. Two or three such events plus a firmographic filter is usually enough.

### How many PQLs should a SaaS company generate?

Far fewer than signups. A common healthy range is 3 to 12 percent of new accounts per month reaching PQL status. If 40 percent of your signups are PQLs, your threshold is measuring activity rather than buying intent, and sales will stop trusting the flag within a quarter.

### What is the difference between an MQL and a PQL?

An MQL is qualified on fit and marketing engagement: job title, company size, content downloaded, pages visited. A PQL is qualified on product behaviour: seats invited, integrations connected, usage volume, limits approached. PQLs typically convert to opportunity at several times the rate of MQLs, but arrive in much lower volume.

### Should every PQL get a sales call?

No. Route by expected account value. Below roughly $3K expected annual value the economics of human outreach rarely work, so send an automated nudge and keep the account self serve. Above $15K expected value a human should reach out within hours. The middle band is where testing pays off.

### What usage signals predict conversion best in B2B SaaS?

Four patterns recur across products: a second or third seat invited, an integration or data source connected, a usage limit approached at 70 to 90 percent, and a high value action repeated across multiple sessions. Repetition matters more than any single event, because it distinguishes evaluation from habit.