Engineering the funnel around product-qualified leads

# Engineering the funnelfunnelThe customer journey from awareness to purchase, typically Awareness, Interest, Consideration, Decision, Action, with prospects narrowing at each stage.View full definition → around product-qualified leads

A user signs up for your whiteboard tool on a Tuesday morning. By Thursday she has invited four teammates, created two boards and wired the workspace into Slack. No demo request, no whitepaper, no conversation with a rep. She is worth several times the lead who filled in your "Request a demo" form last week, and if your funnelfunnelThe customer journey from awareness to purchase, typically Awareness, Interest, Consideration, Decision, Action, with prospects narrowing at each stage.View full definition → only reads form fills she stays invisible until the day she leaves.

That is a product-qualified lead (PQL). This lesson is the plumbing: how you define one, score one and route one before Friday.

The vocabulary: MQLMQLA Marketing Qualified Lead (MQL) is a prospect whose engagement and fit signals indicate they are more likely to become a customer, justifying handoff toward sales.View full definition →, PQL, SQLSQLSales Qualified Lead: a prospect the sales team has validated as ready for direct outreach and a proposal, having passed clear qualification criteria.View full definition →

Three lead types, three different kinds of evidence.

MQL (marketing qualified lead): interest shown through marketing activity. An ebook download, a webinar, three visits to the pricing page. Interest, not usage.

PQL (product qualified lead): someone who has used the product, usually on a free trial or free tier, and hit behaviours that predict purchase.

SQL (sales qualified lead): a lead a rep has vetted and accepted as worth working. The handoff to a human closer.

The old B2B software playbook ran MQLMQLA Marketing Qualified Lead (MQL) is a prospect whose engagement and fit signals indicate they are more likely to become a customer, justifying handoff toward sales.View full definition → to SQLSQLSales Qualified Lead: a prospect the sales team has validated as ready for direct outreach and a proposal, having passed clear qualification criteria.View full definition →: capture an email, nurture with content, pass to sales. It works when buying happens before using. Where the product carries acquisition, the motion the sibling lesson weighs against sales-led, the order reverses, and the PQL is the only signal that reads what the user actually did.

Why PQLs convert better

Action beats clicks as evidence. Someone who invited five teammates and connected two integrations has put your product into her working week. Someone who downloaded a PDF has put in nothing.

Practitioners report PQLs converting at meaningfully higher rates than MQLs. The multiple varies by product and gets quoted loosely, so treat any specific number you see as an estimate. The direction holds.

The economics compound in a second way. Once the product is instrumented, a PQL costs close to nothing to produce: it is a query over events you already collect. An MQLMQLA Marketing Qualified Lead (MQL) is a prospect whose engagement and fit signals indicate they are more likely to become a customer, justifying handoff toward sales.View full definition → carries the media spend that created it, every single time. The two cost curves diverge as volume grows, which is why PQL programmes look unremarkable in month one and decisive in year two.

Building a PQL scoring model

A PQL score ranks trial and free-tier users by likelihood to buy. You build it from activation signals: in-product events that correlate with becoming a paying customer.

Step 1: Find your activation signals

Sit with product analytics and answer one question: what did users who converted do that users who churned did not?

• Breadth: features touched, integrations connected.
• Team: seats invited, invitations accepted, shared workspaces created.
• Depth: the moment the user first gets the core value. In a design tool like Figma that might be a file with a second editor in it. In an email tool, a first campaign sent.
• Frequency: days active in the first week.
• Fit: company size, email domain, job title from enrichment.

Fit signals are the ones most likely to mislead you. A gmail.com address on a design tool is often a contractor who will pull three studios onto the same file; a corporate domain can be one analyst nobody follows. Keep fit weighted lightly until you have enough converted accounts to test it.

Step 2: Weight the signals

Seats invited usually predicts more revenue than a login, because per-seat pricing means adoption spreads through teams and a single active user caps out fast.

Two rules save rework later. Score on a rolling window rather than lifetime totals: a user who touched nine features across eight months is not the user who touched nine in four days. And score changes, not only levels, especially on freemium where the buying moment is a step up in usage rather than a clock running out. Slack's free plan keeps 90 days of message history (it replaced the old 10,000-message cap in 2022), and a team pressing against a ceiling like that is a better buying signal than the same team's absolute volume.

A simplified model in plain pseudocode:

pql_score = 0
# all counters read the trailing 14 days, not lifetime

# Team expansion (strongest predictor for team products)
pql_score += min(seats_invited, 5) * 8

# Aha moment reached
if reached_aha_moment:
    pql_score += 25

# Breadth of use
pql_score += features_used * 3

# Engagement frequency
pql_score += days_active_first_week * 4

# Firmographic fit
if work_email and company_size > 50:
    pql_score += 15

# Threshold for handoff
is_pql = pql_score >= 60

The weights are not magic. You set them, validate against who actually converted, then adjust. A rough model that flags obvious buyers beats no model.

Step 3: Set a threshold

Pick a score that separates "sales should reachreachThe number of unique people exposed to your message in a given period. Unlike impressions, reach counts each person once, no matter how often they see it.View full definition → out" from "keep nurturing in-product". Too low and you drown reps in weak leads. Too high and you miss real buyers.

A practical start: take the last 90 days of conversions, find the score most of them crossed, set the threshold just below it.

Then check the arithmetic against capacity, because the threshold is a valve, not a truth. A rep working PQLs properly (reading the account, writing something personal, following up twice) handles somewhere between 60 and 100 accounts a month. Four reps gives you a ceiling around 300 to 400. If the model flags 900, you raise the threshold, push the surplus into an automated track, or hire. Teams that skip this produce the worst outcome available: 900 leads touched badly, and reps who stop trusting the score inside a quarter.

For a deeper walk through activation metrics, Amplitude's Product Analytics Playbook is a solid free resource on defining aha moments and activation events.

Mapping the handoffs

A score is useless if nobody acts on it. The hard part of PQL programmes is organisational: three teams have to hand off cleanly.

Marketing owns the top

Marketing drives sign-ups and free-tier activation, so its job shifts from generating demo requests to generating trials that activate. A marketer buying Google traffic now needs to know whether that cohort reaches the aha moment, not only whether it starts a trial. Channels reorder once you measure this: the source with the cheapest sign-up is frequently the most expensive PQL.

Product owns the middle

Product surfaces the signals and drives activation inside the app: the aha event, the in-app nudge ("invite your team to unlock shared boards"), the upgrade prompt at the plan ceiling. This is the collaboration that breaks most often, because marketing and product historically never shared a dashboard. One shared definition of activation, one owner of that definition.

Sales owns the qualified handoff

When an account crosses the threshold, a signal fires with context: this workspace invited six people, connected Salesforce, still on free. The rep opens with relevance rather than a cold script, usually to move a team from free to paid or to widen an existing footprint.

The handoff mechanics

The plumbing matters. A typical stack:

1. Product analytics tool (for example Amplitude or Mixpanel, both vendors in this space) tracks events.

2. Events feed a customer data platformcustomer data platformA Customer Data Platform unifies customer data from all sources into persistent, actionable profiles that other systems can use.View full definition → or reverse ETLETLETL (Extract, Transform, Load) is a data integration process that pulls data from sources, reshapes it into a consistent format, and writes it into a target system.View full definition → tool.

3. The score lands in your CRMCRMCustomer Relationship Management: software and strategy to manage and analyse customer interactions throughout their lifecycle.View full definition → (Salesforce, HubSpot) as a field on the account.

4. A workflow alerts the assigned rep and creates a task.

Speed counts. A PQL is hottest during the activation spike itself. ReachReachThe number of unique people exposed to your message in a given period. Unlike impressions, reach counts each person once, no matter how often they see it.View full definition → out four days later and you are talking to someone who has already moved on to another tab.

Common failure modes

Scoring on vanity signals. Logins alone are weak. Someone can log in daily and get nothing. Weight what ties to core value.

Ignoring account-level signals. The buyer is a team. Roll individual signals up to the domain. Notion's free tier is full of people using it as a personal notebook: score them individually and your PQL queue fills with accounts that will never have a second seat.

Talking to the wrong person in the right account. The heaviest user in a Figma or Miro workspace is often a designer with no budget line. The score identifies the account; routing still has to find whoever signs, and the champion is the introduction, not the buyer.

Silent model drift. Ship a new onboarding flow that touches four features on the user's behalf and every score jumps overnight without a single extra buyer. Version the model, and re-baseline the threshold after any release that changes the activation path.

No feedback loop. Sales has to tell marketing and product which PQLs were good. Set a monthly review where reps grade a sample.

Firing sales at self-serve buyers. Some users want to pay with a card and never speak to anyone. Interrupt that and you add friction to a purchase that was already happening.

A quick worked example

Take a Miro-style whiteboard tool with a free tier. The numbers are illustrative; the shape is not.

One month brings 1,000 sign-ups from a content campaign. 300 reachreachThe number of unique people exposed to your message in a given period. Unlike impressions, reach counts each person once, no matter how often they see it.View full definition → the aha moment, a board with a second person editing it inside the first week. Of those, 90 invite two or more teammates, connect the workspace to Slack, and start bumping into the free plan's limits.

Those 90 cross the threshold. Sales works 90 warm accounts with context instead of dialling 1,000 strangers. The other 710 stay in lifecycle nurture and in-app prompts, and a good share convert themselves later or re-enter the queue when a second team lands on the domain.

The part that decides whether the programme survives comes next. Of the 90, sales grades perhaps 20 as genuinely bad. If those 20 share a pattern (all one department, all under 20 employees), you have a weight to change rather than a complaint to file.

Key takeaways

• PQLs are leads defined by product usage, not marketing engagement. Action predicts intent better than clicks, and the marginal cost of finding one falls as you scale.
• Build the score from validated activation signals on a rolling window, count changes as well as levels, and keep firmographic fit lightly weighted until data earns it more.
• Set the threshold against rep capacity, not only against past conversions. A model that produces triple the leads your team can work destroys its own credibility.
• Roll signals up to the account, then route to whoever can sign, which is rarely the heaviest user.
• Re-baseline after product releases and have sales grade a sample monthly. A rough model that ships beats a perfect model that never launches.