How do I get product usage data into my CRM without an engineering sprint?

Start with Segment or RudderStack if you already have an event pipeline. Tools like Pocus and Correlated are specifically designed to bridge this gap — they connect to your data warehouse or product analytics platform and push PQL scores into Salesforce or HubSpot without custom engineering work. If you have no event infrastructure at all, begin with a simple daily CSV export of key metrics and automate from there.

What is the difference between a PQL and a hot MQL?

An MQL is defined by marketing engagement: page views, content downloads, form fills. A PQL is defined by product behaviour: feature usage, team expansion, billing thresholds. The distinction matters because product engagement demonstrates actual need, not just interest. A prospect who downloads your whitepaper might be doing competitive research. A team that created three projects and invited five colleagues is building a workflow around your product.

Should I reach out to free-tier users, or wait for them to hit a paywall?

Both approaches have merit, but the highest-conversion motion is to reach out when the user has demonstrated value (aha moment reached) and is approaching a natural expansion point (approaching limits, adding team members). Reaching out too early — before the user has experienced value — can feel premature and pushy. Let the product do the selling first, then add the human touch when the data says they are ready. ---

How to Surface Product-Qualified Leads (PQLs)

Overview

Marketing-qualified leads are based on content engagement: someone downloaded a whitepaper or attended a webinar. Product-qualified leads are based on actual product behaviour: someone is using your product in a way that predicts they will pay for it (or pay more). The difference in conversion rates is not subtle — PQLs convert 5-6x better than MQLs.

The challenge is that most sales teams do not have visibility into product data. Usage metrics live in analytics platforms, billing data sits in Stripe, and the sales team works out of the CRM. This playbook bridges that gap by defining the nine most reliable PQL signals, showing you how to surface them, and providing outreach frameworks that respect the user's product experience.

If you are running a product-led growth motion — or even a hybrid PLG + sales-assisted model — this is the playbook that turns free users into paying customers and paying customers into enterprise contracts. For the complete taxonomy of buying signals, see our signal-based prospecting guide.

The Signals This Playbook Uses

Signal	Propensity	Volume	Strength
Surge in product usage	8/10	6/10	High
Multiple workspaces created	7/10	4/10	High
Paid ceiling threshold approached	9/10	5/10	High
Multiplayer product activity	7/10	5/10	High
Surge in product log-ins	6/10	7/10	Medium
Product link share	5/10	6/10	Medium
New account sign-up (ICP match)	5/10	8/10	Medium
Feature adoption (Aha! moment)	8/10	5/10	High
Product reactivation	7/10	4/10	Medium

Surge in product usage and paid ceiling threshold are the two highest-conversion signals. A team that suddenly triples their API calls or bumps against their free-plan limits is demonstrating real need — they are not browsing, they are building.

Multiple workspaces and multiplayer activity indicate organic expansion within an organisation. When one user invites five colleagues, the account just qualified itself.

Product reactivation — a user returning after a stagnant period — often correlates with a renewed initiative or a new stakeholder who discovered the product.

Step 1: Detection Setup

Required tools:

Pocus or Correlated — Purpose-built PQL platforms that connect to your product database and surface accounts based on usage patterns. Define PQL criteria and get real-time alerts in Slack or your CRM.

Amplitude or Mixpanel — Product analytics platforms for defining and tracking key events. Create cohorts based on usage milestones (e.g., "created 3+ projects in 7 days").

Segment or RudderStack — Event pipeline to route product data to your CRM, PQL platform, and analytics tools.

CRM (Salesforce/HubSpot) — Destination for enriched PQL signals. Create custom fields for product usage metrics and automate lead scoring.

Alert configuration:

Real-time alerts for paid ceiling threshold approached (highest urgency — the user is hitting limits now)

Daily digest for usage surges, workspace creation, and multiplayer activity

Weekly batch for new sign-ups matching ICP, feature adoption milestones, and reactivation

Route alerts to the assigned CSM (existing accounts) or SDR (new accounts)

Key events to instrument:

Workspace created / team member invited

Plan limit approached (API calls, storage, seats, etc.)

Core feature activated for first time (your product's "aha moment")

Shareable link generated or shared externally

Step 2: Signal Qualification

PQL signals need to be filtered through two lenses: account fit and engagement intensity.

Account fit scoring:

Company size matches ICP: +20 points

Industry matches ICP: +15 points

Sign-up with corporate email domain: +10 points

Multiple users from same domain: +15 points

Already on paid plan: +10 points

Engagement intensity scoring:

Usage surge (>2x baseline): +25 points

Approaching paid ceiling: +30 points

Multiple workspaces: +20 points

3+ team members active: +20 points

Aha moment reached: +15 points

Reactivation after 30+ day dormancy: +10 points

PQL threshold: Accounts scoring 50+ points get routed to sales. Accounts scoring 30-49 enter an automated nurture sequence. Below 30, continue monitoring.

Step 3: Outreach Execution

Timing: This varies by signal. Billing threshold signals require same-day outreach. Usage surges should be contacted within 2-3 days. Reactivation signals can tolerate a week.

Channel priority:

In-app message or prompt (lowest friction, highest context)

Email from a named account rep (not marketing automation)

LinkedIn (for economic buyers identified through enrichment)

Template 1: Paid Ceiling Approaching

Hi [Name], I noticed your team at [Company] is getting close to the [specific limit — e.g., "5-seat cap" or "10,000 API call threshold"] on your current plan.

Rather than hitting a wall, I wanted to connect and walk you through how teams at [similar company] have scaled beyond this point. There are a few options that could make sense depending on how you are using [product feature].

Do you have 15 minutes this week?

Template 2: Multiplayer Expansion

Hi [Name], it looks like the team at [Company] has been growing their usage of [Product] — [X team members] active this month, up from [Y] last month.

When we see that kind of organic adoption, there is usually a point where a centralised setup (shared workspace, admin controls, unified billing) saves everyone time. Would it be helpful to walk through how other teams your size have structured this?

Template 3: Product Reactivation

Hi [Name], welcome back — I noticed you and your team have been active in [Product] again over the past couple of weeks.

Since you were last in, we have shipped [relevant new feature]. A few teams in [their industry] have been using it to [specific outcome]. Would a quick update call be useful, or would you prefer I send over a summary of what has changed?

Step 4: Signal Stacking for Maximum Impact

The power combinations:

Usage surge + paid ceiling + multiple workspaces = Enterprise-ready account. This combination indicates an organisation that has adopted your product organically and is about to need an enterprise contract. Engage the economic buyer directly.

New account sign-up (ICP match) + aha moment reached within first week = Fast-converting PQL. These users adopted quickly and represent the highest-velocity conversion opportunity.

Multiplayer activity + product link shared externally = Viral expansion. The product is being used as a collaboration tool across teams or even external partners. This is your signal to introduce enterprise features (SSO, admin controls, audit logs).

When three or more PQL signals fire on the same account within a 14-day window, escalate to your highest-touch motion: schedule a personalised demo, offer a free pilot of the enterprise tier, or arrange a call between their team lead and your solutions engineer.

Measuring Success

Metric	Target	Benchmark
PQL-to-opportunity conversion	15-25%	vs 2-5% MQL-to-opportunity
Time from PQL to closed deal	21-30 days	vs 60-90 days MQL
Reply rate on PQL outreach	20-30%	vs 3-5% cold
Expansion revenue from PQL signals	20-30% of net new ARR	varies by model
Free-to-paid conversion rate	5-8%	PLG benchmark

Frequently Asked Questions

Related Signal Playbooks

This playbook is part of the Signal-Based Prospecting series. Related playbooks:

[Identifying & Tracking Economic Buyers](/blog/playbook-economic-buyers) — When a VP or C-level logs into your product, it is one of the highest-propensity PQL signals. Learn how to detect and engage economic buyers directly.

[Support Signal Alerts](/blog/playbook-support-signal-alerts) — Support tickets often reveal PQL signals in disguise. "How do I add more users?" is both a support question and a seat expansion signal.

[Signal-Heavy Accounts: How to Prioritise Multi-Signal Opportunities](/blog/playbook-signal-heavy-accounts) — PQL signals are the highest-weighted category in most signal stacking models. Learn how to combine them with website and job change data.