Skip to main content
Intempt
Coming soon

Account level signal to AE task

When several people from one company start using the product in the same fortnight, it briefs an AE and asks them to open a deal.

Authored by Intempt Technologies

Recipe curators

Agentic workflow

Coming soon

4 steps Blu runs end to end. It drafts a plan and nothing runs until you approve it.

  1. 1

    Score the whole account

    Coming soon

    Blu builds a step

  2. 2

    Find accounts crossing 70

    Coming soon

    Blu builds a step

  3. 3

    Brief an AE to open a deal

    Coming soon

    Blu builds a step

  4. 4

    Compare against cold outbound

    Coming soon

    Blu builds a step

About this recipe

When to use it

One engaged user might just be one engaged user. Several people from the same account engaging in a short window is a real buying signal. This catches that pattern and turns it into an AE task.

What it delivers

When multiple users from the same account engage with the product in a short window - a PQA signal - creates an AE deal-creation task with the account's full engagement picture.

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 several people from one company start using the product in the same fortnight, it briefs an AE and asks them to open a deal.”

recipe.md preview

Built from the published catalog. Blu Agent's full step prompts load in your workspace when you run it.

Sign up to read the full recipe.md and run it with Blu Agent.

Sign up to see the full recipe

Inputs & outputs

What the recipe needs before it runs, and what it leaves in your workspace.

Inputs

  1. 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.

    1. 01Score the whole accountCreate an AI-derived attribute 'pqa_score' on the Account object. Composite: (a) count of distinct users from the account active in last 14 days (3+ users = strong PQA signal); (b) total feature events across the account; (c) seniority of users (any decision-makers based on title/email pattern); (d) usage depth across the account team. Output: numeric score 0-100. Score >= 70 = PQA. Updated daily and on new user signups from the domain.
    2. 02Find accounts crossing 70Build a segment 'PQA: accounts score >= 70' capturing accounts where pqa_score crossed 70 in the last 14 days AND no open deal currently exists for the account AND no AE has been actively engaged in the last 60 days. Excludes existing paid customers (different motion: see seat-expansion workflow). Use the result of "Score the whole account".
    3. 03Brief an AE to open a dealCreate 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. Use the result of "Score the whole account", "Find accounts crossing 70".
    4. 04Compare against cold outboundCompose 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. Use the result of "Score the whole account", "Find accounts crossing 70", "Brief an AE to open a deal".

    Install Intempt and run it

    1. 1

      Sign up

      Create a free Intempt workspace.

    2. 2

      Connect your data

      Add the sources this recipe reads from.

    3. 3

      Ask Blu

      Type /pqa-account-engagement-to-ae-task in Blu once this recipe is live there.

    4. 4

      Review and approve

      Blu builds each step and waits for your OK before anything goes live.

    Related recipes

    Intempt TechnologiesDiscovery call qualification fieldsGenerates an AI summary for Discovery calls from meeting data using the qualification framework in the summary recipe.View recipe Intempt TechnologiesPost 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 Intempt TechnologiesReturn rate by categoryShows which product categories get returned most, and which ones have got worse since last quarter.View recipe

    More recipes by Intempt Technologies

    Discovery call qualification fieldsGenerates an AI summary for Discovery calls from meeting data using the qualification framework in the summary recipe.View recipe Post 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 Product swap in a sceneReplaces the product in a shot you already have with a different one, keeping the scene, lighting and shadow the same.View recipe

    Got a play worth sharing?

    Publish it to the Intempt Collective Marketplace and earn when other teams run it.

    Submit a recipe