Lead qualification funnel
Shows how leads move through MQL, SQL, demo and closed won, where they stall, and how long the whole cycle takes.
Authored by Intempt Technologies
Recipe curators
Agentic workflow
Coming soon1 step Blu runs end to end. It drafts a plan and nothing runs until you approve it.
- 1
Track leads through qualification
Coming soonBlu builds a step
About this recipe
When to use it
MQL-to-SQL conversion rate alone doesn't tell you if leads move fast or rot in the queue. This tracks the real qualification funnel with velocity at every stage, so a slow SQL handoff shows up even if the eventual conversion rate looks fine.
What it delivers
Builds a lead-to-MQL-to-SQL qualification funnel from real lead_stage_changed transitions, with time-in-stage velocity measured at each step.
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
“Shows how leads move through MQL, SQL, demo and closed won, where they stall, and how long the whole cycle takes.”
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.
- 01Track leads through qualificationCreate a Funnel report called "Lead Qualification Funnel". Steps: 1. Event "User created" where Users.UTM source is not empty: "Lead Created" 2. Event "Lead stage changed" where new_stage indicates MQL (lead_stage relation matches MQL stage in the project's lead-stage configuration), aggregation: Count Unique Users per lead: "Reached MQL" 3. Event "Deal created" linked to the user (via primary_user_id or user_ids): "SQL Created" 4. Event "Meeting scheduled" where canceled_at is null AND end_time < now: "Demo Completed" 5. Event "Deal won": "Closed Won" Conversion window: 90 days Breakdown: By Users.UTM source (top 6 sources) Compare: Previous period (prior 90 days) For each step, also surface: - Median time-to-convert from previous step - Per-source conversion rate at each stage - Stage velocity from Step 1 to Step 5 (full sales-cycle length) Annotations: - Flag the largest stage drop-off. - Flag any source where MQL-to-SQL conversion is below 20% (MQL definition issue for that source). - Flag any source where SQL-to-Closed-Won is below 15% (deal-execution issue). - Highlight sources with high volume AND end-to-end conversion >5%. Surface the median sales-cycle length and whether it's increasing or decreasing. Taxonomy notes: - "lead_score" as a property is not canonical. Lead progression is tracked via Lead stage changed events (which include score, intent_trend, stage_changed_by properties). The lead_stage relation on the User points to a configured lead-stage record. - The MQL/SQL boundary is project-specific; the recipe uses the Lead stage changed.new_stage relation against the project's stage configuration.
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 /lead-to-mql-to-sql-funnel 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.
