Signal Library

The product qualified lead signal

The warmest signal you own, because it lives in your own product. Real usage, not a form fill.

A single sign-up is not a PQL. Value plus spread is.

By Kshitij · Updated June 2026 · 7 min read

Book a Fit Check

Signal Snapshot

Warm signal

Indicates

A user is getting real value and spreading

Strength

Strong · first-party behavior

Window

Days, act on the spike while it is hot

Detect with

PostHog, Amplitude, Mixpanel, Pocus, Endgame

Skip it when

A lone low-value sign-up with no path to expand

Family: product and behavior Stacks with website intent

A product qualified lead signal fires when a free or trial user's behavior shows real value and spread, not just a sign-up. It is the warmest signal you own, because the proof lives in your own product data.

The three angles

One PQL, three ways it shows up

Most teams watch one number and miss the rest. A real PQL is a pattern, and it surfaces in three distinct shapes.

1 Expand

Usage expansion

One account hits plan limits, repeats the core action that delivers value, and active days climb. The user is outgrowing the free tier and needs more room.

2 Spread

Internal spread

A new colleague gets invited, or a second and third person sign up from the same company domain. The tool is moving through the org, time to multithread.

3 Activate

Trial milestone

A user reaches the activation moment, the action that reliably predicts they stick around. A clean sales-assist moment to help them finish setting up and upgrade.

Angles 1 and 2 say "this account is buying more soon." Angle 3 says "this person just got value, help them get more." All three are warm because the behavior is real, and all three pair with website intent when the same account starts reading your pricing page.

How do you detect a PQL?

The signal lives in your own event data first. Define the qualifying behavior, watch it in product analytics, then route it to where sales will see it.

Layer	What it does	Tools
Product analytics	Where the behavior lives. Track the core action, active days, limit usage, and the activation moment per account.	PostHog, Amplitude, Mixpanel
Reverse-ETL to CRM	Push the qualifying behavior from the warehouse into the CRM so sales sees the PQL on the record, not in a separate tab.	Census, Hightouch
PLG signal tools	Purpose-built to score product usage, roll it up to the account, and route the PQL to a rep with the context attached.	Pocus, Endgame, Correlated, HeadsUp
By hand at first	At seed stage, a weekly query for accounts hitting limits or adding seats. Cheap, and it forces you to define the behavior.	SQL, a spreadsheet, your own dashboard

Tool-agnostic

We work across most product-analytics and PLG signal tools and adapt to your stack. For the full comparison, see our guide to signal and intent tools. The detector matters less than the behavior you choose to watch, which is why we start with signal mapping before any tool goes in.

Not sure which product behaviors actually predict a buyer?

Book a Fit Check

The window: trigger on behavior, not a timer

A usage spike is perishable. The right moment is days after the qualifying pattern, while the value is fresh in their head, and the two failure modes are too early and too late.

Too early

The interruption

Reaching out the second an account is created interrupts someone still exploring. It reads as a cold pitch and adds friction to the value they were about to find.

The spike, then days

The opening

They hit a limit, ran the core action again, or pulled in a colleague. The value is proven and fresh. Reach out now, referencing exactly what they did.

Too late

Already gone

Weeks later they have self-served the cheapest plan, churned, or forgotten the tool. The spike has passed and the conversation has nothing fresh to anchor to.

The play: how we work a PQL

Product-led signals are warm, so this is inbound-led outbound, not a cold sequence. A short, sales-assist conversation built on what they already did inside the tool.

1

Confirm value and fit

Is this a real pattern of usage, or one curious sign-up? Does the company fit the paid tier? If the behavior is thin or the fit is wrong, it is not this play.
2

Open on what they did, not who they are

Reference the specific limit they hit or the workflow they ran. The message is help, not a pitch: you noticed they were getting somewhere and want to make it easier.
3

Multithread when the account spreads

When a second or third colleague joins from the same domain, the account is bigger than one user. Reach the admin or most senior user with the team's usage in hand.
4

Offer the upgrade as the obvious next step

By now the value is established. The ask is small: the paid tier removes the limit they already hit. No demo gymnastics, just the next step they were heading toward anyway.

This is the signal-specific version. The full repeatable motion for working warm, product-led accounts lives in the inbound-led outbound play.

The angle

The native angle, and the generic one

You have data nobody else has: what they actually did in the product. Use it, or you waste the warmest signal you own.

The generic move

"Thanks for signing up! I'd love to show you everything our platform can do. Are you free for a 30-minute demo this week?"

✕Treats a sign-up as a buying intent it is not
✕Ignores everything they actually did in the tool
✕Asks for a demo before they have hit a wall

The signal-native move

"Saw your team ran the import flow about forty times this week and just hit the free row cap. Three of you are in there now. Happy to lift the limit and show your admin the team view, no demo needed. Want me to set it up?"

✓Names the exact behavior, the limit, and the spread
✓Leads with help, removing the wall they already hit
✓Routes to the admin because the account is spreading

Where it is strong, and where it is weak

An honest read, because the tools selling you PQL scoring will only show you the upside.

Strengths

✓First-party data, you own it and nobody else has it
✓Warm by default, they have already used the product
✓Carries intent, fit, and timing in one pattern
✓Converts well, because the context is real and specific

Watch-outs

!Fires too early if the bar is set at sign-up
!Needs clean event tracking, which seed teams often lack
!One active user is not an account, watch the spread
!Only exists if you have a free or trial motion at all

When a PQL is just noise

The fastest way to break a product-led motion is to call every active user a PQL. The signal works when you hold the bar. Skip it when:

✕It is a lone sign-up. One account, no repeat action, no spread. That is curiosity, not value. Let them keep exploring and watch for the pattern.
✕There is no path to a paid tier. A hobbyist or student maxing the free plan is a happy user, not a deal. Behavior without fit is a false positive.
✕The behavior is shallow. Logins and page views are vanity signals. If they are not doing the action that actually delivers value, the number is noise.
✕You are scoring it as binary. A PQL is a spectrum, sorted by recency, velocity, and fit. Treating a faint signal like a hot one floods sales with junk.

Want your product signals worked into real meetings?

Book a Fit Check

Stack it with

A PQL is strong alone and stronger combined. When a second signal lands on the same account, the case to reach out goes from likely to obvious.

+ Website intent

The same account is reading your pricing page. Usage plus a pricing visit is a buyer raising their hand twice.

+ Funding

A power user at a company that just raised. The budget to expand the seat count is now confirmed.

+ New hire

A new leader joins an account already using you free. A champion with a mandate to make the tool official.

Combining signals on one account is its own motion. We map and score the combinations through signal mapping, then work them with signal stacking.

How we would run it

An example, start to finish

An illustrative walkthrough of the method, not a specific client result. We report real numbers only when they are real.

1

Day 0 · Detected

The pattern fires

A free account runs the core action well past the average, hits the row cap, and a second colleague from the same domain signs up. Routed to a rep with the usage attached.
2

Days 1 to 2 · Reach out

Open on the behavior

A short note naming the limit they hit and offering to lift it. Help first, no demo. Sent while the workflow is still fresh in their head.
3

Day 4 · Multithread

Reach the admin

Because the account is spreading, loop in the most senior user with the team's usage, framing the paid tier as the team view they are clearly ready for.
4

Day 7 · The ask

Offer the next step

A short call to set up the paid plan, framed as removing the wall they already hit. The deal follows the value, not a pitch.

Signals like this fed pipeline we've built inside these companies

Palm.ai

Alcméon

Mindflow

CEF.AI

Boolee

CoachHub

Inrō

Buster.AI

Palm.ai

Alcméon

Mindflow

CEF.AI

Boolee

CoachHub

Inrō

Buster.AI

FAQ

Questions founders ask

What is a product qualified lead signal?

A product qualified lead signal fires when a free or trial user's behavior shows real value and spread, not just a sign-up. The pattern is someone hitting plan limits, repeating the core action that delivers value, raising their active days, or pulling in colleagues. One person creating an account is not a PQL. A pattern of usage plus internal spread is.

How do you detect a PQL?

Start with your own product analytics, PostHog, Amplitude, or Mixpanel, because the signal lives in your event data first. Pipe the qualifying behavior into the CRM with reverse-ETL through Census or Hightouch so sales sees it, or use a product-led signal tool like Pocus, Endgame, Correlated, or HeadsUp to score and route it. The detector matters less than the definition of the behavior you choose to watch.

When should you reach out to a PQL?

Reach out within days of the qualifying pattern, while the usage spike is still hot, not on a fixed timer and not the second an account is created. Reaching out too early interrupts a user who is still exploring and reads as a cold pitch. Waiting weeks means they have already self-served the cheapest plan or forgotten about you. Trigger on the behavior, then move fast.

Why is a single sign-up not a PQL?

A sign-up is a vanity signal. One person making an account proves curiosity, not value or intent to buy, and scoring it as a PQL floods sales with noise. The real signal is value plus spread: the core action repeated, limits approached, active days rising, or a second and third colleague from the same company joining. Layer behavior with fit before you call it qualified.

What is the right motion for working a PQL?

Product-led signals are warm because the person has already used the product, so the natural motion is inbound-led outbound, not a cold sequence. Open on what they did inside the tool, the limit they hit or the workflow they ran, and offer to help them get more out of it. It is a sales-assist conversation, not a demo booking, and it lands because the context is real.

Keep going