Product qualified lead to SDR task
When a free user's behaviour says they are ready for a conversation, it creates an SDR task carrying everything needed for the first touch.
Authored by Sid Chaudhary
Founder & CEO at Intempt
Agentic workflow
Coming soon4 steps Blu runs end to end. It drafts a plan and nothing runs until you approve it.
- 1
Score free users on behaviour
Coming soonBlu builds a step
- 2
Find free users crossing 70
Coming soonBlu builds a step
- 3
Give the SDR the context
Coming soonBlu builds a step
- 4
Hold the 24 hour first touch
Coming soonBlu builds a step
About this recipe
When to use it
A rep working a PQL cold usually spends the first minutes just figuring out what the user actually did. This attaches the qualification context to the task itself, so first-touch is one click, not a research detour.
What it delivers
When a free-tier user crosses a PQL behavioral threshold - feature use, depth, repeated sessions - creates an enriched SDR task carrying the qualification context.
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
“When a free user's behaviour says they are ready for a conversation, it creates an SDR task carrying everything needed for the first touch.”
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.
- 01Score free users on behaviourCreate an AI-derived attribute 'pql_score' on the User object. Composite signal: (a) high-value feature usage (key activation events) weighted highest; (b) usage depth (sessions in last 14 days, features touched, time-in-product); (c) account-level density (other users from same domain active). Output: numeric score 0-100. Score >= 70 = PQL. Refreshed daily and on feature_used events.
- 02Find free users crossing 70Build a segment 'PQL: free users score >= 70' capturing free-tier users where pql_score crossed 70 in the last 7 days AND no active SDR task exists for this user AND no recent (last 30 days) outreach has occurred. Excludes paid users (different workflow) and users in opt-out list. Use the result of "Score free users on behaviour".
- 03Give the SDR the contextCreate a workflow firing when pql_score crosses 70. Step sequence: (1) enrich the user's account if not already enriched (firmographics, ICP fit); (2) compute outreach context: top features used, usage frequency, account size, ICP fit tier; (3) create a high-priority SDR task with the outreach context attached, assigned via territory rules (geo / industry / account size); (4) post a brief Slack notification to the assigned SDR's DM with the task link. If account is below ICP threshold, route to self-serve nurture journey instead of SDR queue. Use the result of "Score free users on behaviour", "Find free users crossing 70".
- 04Hold the 24 hour first touchCompose a PQL conversion dashboard: PQL volume (count of free users crossing threshold per week, trend), median time from threshold-cross to first SDR touch (SLA target: <24hr), PQL-to-meeting conversion rate, PQL-to-deal conversion rate by ICP tier, and rep leaderboard (SDRs converting PQLs at the highest rates). Flag any week where >20% of PQLs are untouched after 48 hours. Use the result of "Score free users on behaviour", "Find free users crossing 70", "Give the SDR the context".
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-signal-to-sdr-task 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.
