Skip to main content
Intempt
Coming soon

Discovery call qualification fields

Generates an AI summary for Discovery calls from meeting data using the qualification framework in the summary recipe.

Authored by Sid Chaudhary

Founder & CEO at Intempt

Agentic workflow

Coming soon

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

  1. 1

    Check the Discovery meeting type

    Coming soon

    Blu builds a step

  2. 2

    Set what discovery captures

    Coming soon

    Blu builds a step

  3. 3

    Check discovery quality by rep

    Coming soon

    Blu builds a step

About this recipe

When to use it

A discovery call summary that doesn't map to your qualification framework is just notes, not signal. This extracts champion, pain, current solution, decision criteria, timeline, and budget explicitly, so the summary feeds directly into deal qualification scoring.

What it delivers

Customizes how the AI summarizes discovery calls to explicitly extract the qualification framework (champion, pain, current solution, decision criteria, timeline, budget), feeding directly into deal-qualification scoring.

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

“Generates an AI summary for Discovery calls from meeting data using the qualification framework in the summary recipe.”

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. 01Check the Discovery meeting typeRetrieve the Discovery meeting type from the project's meeting taxonomy. Confirm it exists and has notetaker autojoin enabled, both are prerequisites for the custom summary recipe to fire on real meetings. If the type doesn't exist, halt and prompt the user to run /meeting-types-taxonomy first.
    2. 02Set what discovery capturesConfigure the AI summary recipe for the Discovery meeting type. Extract structured fields: (1) Champion (name, title, level of buy-in (high/medium/low/none), explicit quotes showing commitment; (2) Pain) pain statement in prospect's own words, severity (must-solve/should-solve/nice-to-have), business impact discussed (revenue, cost, time, risk); (3) Current Solution (what they use today (vendor name + version), what works, what doesn't; (4) Decision Criteria) explicit criteria mentioned (price, features, integration, security, etc.), priority ranking if discussed; (5) Timeline (target go-live, urgency drivers; (6) Budget) explicit number, range, or signal (no budget signal = flag); (7) Next Step: what was agreed, with owner and due date. If a field is not discussed, return 'not_discussed' rather than guessing. Use the result of "Check the Discovery meeting type".
    3. 03Check discovery quality by repCompose a Discovery call quality dashboard reading from the structured summaries: % of discovery calls with all 7 fields captured (target: 70%+); breakdown of most-frequently-missed fields (signals coaching opportunities); discoveries with 'no budget signal' flagged for follow-up; champion strength distribution across recent discoveries; pain severity distribution. Group by rep so managers can spot reps consistently missing qualification fields. Use the result of "Check the Discovery meeting type", "Set what discovery captures".

    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 /discovery-call-summary-recipe 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

    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 Sid ChaudharyTalking head from a portraitTurns a portrait still into a 5 second talking-head loop with subtle lip movement and eye contact.View recipe

    More recipes by Sid Chaudhary

    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 Return rate by categoryShows which product categories get returned most, and which ones have got worse since last quarter.View recipe Talking head from a portraitTurns a portrait still into a 5 second talking-head loop with subtle lip movement and eye contact.View recipe

    Got a play worth sharing?

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

    Submit a recipe