Product qualified lead leaderboard
Scores free users with a custom formula and includes contact details, so sales can prioritize outreach.
Authored by Sid Chaudhary
Founder & CEO at Intempt
Agentic workflow
Coming soon1 step Blu runs end to end. It drafts a plan and nothing runs until you approve it.
- 1
Rank free users by buying signal
Coming soonBlu builds a step
About this recipe
When to use it
PLG sales teams waste time chasing free users who show zero buying signal. This surfaces exactly which free accounts have crossed your configured product-qualified-lead threshold, ranked and ready for handoff.
What it delivers
Builds a sortable leaderboard of free users who've crossed configurable PQL thresholds, the standard report PLG sales teams use to prioritize outreach.
How you prompt this
Describe the outcome in your own words and Blu Agent maps it to this recipe, or run it by name. It drafts a plan first and nothing runs until you approve it.
Tell Blu Agent what you want
“Scores free users with a custom formula and includes contact details, so sales can prioritize outreach.”
recipe.md preview
Built from the published catalog. Blu Agent's full step prompts load in your workspace when you run it.
Inputs & outputs
What the recipe needs before it runs, and what it leaves in your workspace.
Inputs
- Nothing declared beyond an Intempt workspace. Blu asks for anything else it needs as it goes.
Outputs
How the recipe runs
Blu follows the steps in order and shows you each one before anything goes live.
- 01Rank free users by buying signalCreate an Insights report called "PQL Leaderboard". This recipe surfaces the highest-intent free users for sales follow-up: the Product Qualified Lead (PQL) leaderboard. PQL definition (configurable; default thresholds): A user qualifies as a PQL if ALL of the following are true within a 14-day rolling window: 1. User is currently on a free or trial plan (Subscription started with trial_end populated, OR no active Subscription started) 2. User has emitted ≥3 distinct sessions (≥3 Session start events on different days) 3. User has emitted ≥1 Completed a journey goal for the activation journey 4. User has emitted ≥10 Click on events on core feature targets (configurable target_id pattern) Optional ICP filter: user's Users.UTM source matches a high-fit channel (configurable) For each PQL, surface: - User identity (name, email, the account the user belongs to from Users object) - PQL score = a 0-100 number computed from a weighted blend of: session count × 5 + goal completions × 15 + core-feature clicks × 1 + days_since_first_seen as a recency multiplier (capped at the threshold) - Days as PQL (how long they've been over the threshold: long-tenured PQLs need urgent sales attention) - Most recent activity timestamp (Users.Last seen) - The specific behavior that crossed them over the threshold (which condition flipped most recently) Series A: Count of users in PQL state, weekly, label: "Active PQLs" Series B: Trailing-7-day PQL to Subscription started (paid, non-trial) conversion rate, label: "PQL Conversion Rate" Time range: Current snapshot + last 12 weeks for the trend Breakdown: By Users.the account the user belongs to (account-level aggregation (for B2B-leaning SaaS, multiple PQLs at the same account is the strongest signal; this is a "PQA") Product Qualified Account) Chart type: Sortable table (the leaderboard) plus a secondary trend chart showing weekly PQL volume Annotations: - Add benchmarks: PQL-to-paid conversion rates of 15-30% are healthy; below 10% suggests threshold is too lenient (qualifying too early). Above 35% means the bar may be too high: you might be missing users who'd convert with sales touch. - Flag PQLs who have been over-threshold for 7+ days without sales contact (lost-opportunity signal: every hour of delay reduces conversion). - Highlight accounts (the account the user belongs to) with 3+ users currently in PQL state: these are PQAs and warrant priority sales outreach. - Surface the dominant "qualifying behavior" pattern (which threshold was hit most recently): this informs the right opening message for sales. Use case: the single most-cited PLG report across the entire research base (Custify, Correlated, OpenView, ProductLed, Klipfolio, Userpilot all describe it as foundational). Routes high-intent free users to sales when the intent is hottest. Taxonomy notes: - All thresholds use canonical events: Session start, Click on, Completed a journey goal, Subscription started. - Users.the account the user belongs to enables account-level PQA aggregation. - Users.UTM source enables ICP filtering. - PQL scoring is computed by Lovable from these inputs: the recipe defines the formula.
Install Intempt and run it
- 1
Sign up
Create a free Intempt workspace.
- 2
Connect your data
Add the sources this recipe reads from.
- 3
Ask Blu
Type /pql-leaderboard in Blu once this recipe is live there.
- 4
Review and approve
Blu builds each step and waits for your OK before anything goes live.
Related recipes
Sid ChaudharyDiscovery call qualification fieldsGenerates an AI summary for Discovery calls from meeting data using the qualification framework in the summary recipe.View recipe Sid ChaudharyPost demo nurtureKeeps a demo warm for 90 days with a playbook, a case study, an ROI calculator and a customer story, and pulls the AE in early if they bite.View recipe Sid ChaudharyReturn rate by categoryShows which product categories get returned most, and which ones have got worse since last quarter.View recipe 