What it does
Use when a user mentions "PQA detection", "product-qualified account", "multi-user account engagement", or asks for related help. When multiple users from the same account engage with the product in a short window — PQA signal — create an AE deal-creation task with the account's full engagement picture, because account-level signals are stronger than single-user signals.
You get
Attribute
AI-Derived Attribute produced by this recipe.
Segment
Segment produced by this recipe.
Workflow
Workflow produced by this recipe.
Dashboard
Dashboard produced by this recipe.
How it works
Compute Account Engagement Score
create_ai_attributeCreate an AI-derived attribute
Identify PQA Accounts
Create SegmentBuild a segment
Build PQA Detection Workflow
Create WorkflowCreate a workflow firing when pqa_score crosses 70. Step sequence: (1) refresh account enrichment (firmographics, technographics, decision-maker contacts via Apollo/ZoomInfo if connected); (2) compute account context summary: active user count, key features used per user, decision-makers identified, employee count, ICP fit; (3) create a high-priority AE task to create a deal record and start outreach, with the full account context pre-attached; (4) notify AE manager and assigned AE via Slack with a one-paragraph summary and link to the account record. Only fire for ICP-matched accounts.
Build PQA Conversion Dashboard
Build DashboardCompose a PQA dashboard tracking: PQA detection volume (accounts crossing threshold per month), AE response time (median time from PQA-flag to deal_created), PQA-to-deal conversion rate, PQA-to-meeting rate, ARR-weighted PQA value (deals from PQAs vs. non-PQA outbound). Compare PQA-sourced deals vs. cold-outbound-sourced deals on win-rate and cycle time — usually PQAs win 2-3x more reliably.
Ready to run this recipe?
Tell Blu what you need. It builds the segment, content, journey, and dashboard in minutes.
Sign up free