Skip to main content
Intempt
Coming soon

Demo call summary fields

Built in Demo call summary recipe: one of nine fixed recipes that summarizes demo meetings.

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 Demo meeting type

    Coming soon

    Blu builds a step

  2. 2

    Set what the demo summary captures

    Coming soon

    Blu builds a step

  3. 3

    Track what demos reveal

    Coming soon

    Blu builds a step

About this recipe

When to use it

A demo call generates product feedback, sales coaching material, and deal-progression signal, but only if someone actually extracts it. This customizes the AI summary to pull features shown, questions asked, objections raised, and technical concerns flagged, feeding all three uses at once.

What it delivers

Customizes how the AI summarizes demo calls to extract features shown, questions asked, objections raised, technical concerns, and the proposed follow-up, feeding product feedback, sales coaching, and deal-stage progression in parallel.

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

“Built in Demo call summary recipe: one of nine fixed recipes that summarizes demo meetings.”

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 Demo meeting typeRetrieve the Demo meeting type from the meeting taxonomy. Confirm it exists with notetaker autojoin enabled. If absent, halt and direct the user to /meeting-types-taxonomy.
    2. 02Set what the demo summary capturesConfigure the AI summary recipe for the Demo meeting type. Extract structured fields: (1) Features Demoed: list of product features shown, with engagement signal per feature (attendee asked questions / silent / pushed back); (2) Questions Asked (list of attendee questions with category (capability, integration, pricing, security, onboarding, other); (3) Objections) list of objections raised verbatim, with category (price/timing/competition/feature-gap/authority/trust) and resolution status (handled/parked/unresolved); (4) Technical Concerns: specific technical questions or blockers (integrations needed, data residency, SSO, compliance); (5) Decision-Maker Signal (was a decision-maker on the call, were they engaged; (6) Follow-up Requested) what attendee asked for (case study, trial, technical demo, custom proposal, references); (7) Next Step: what was agreed. Use 'not_discussed' for missing fields rather than guessing. Use the result of "Check the Demo meeting type".
    3. 03Track what demos revealCompose a demo insights dashboard reading from structured summaries: top 10 features by demo frequency (which features sell themselves vs. need more pitch); top 10 objections by frequency (objection-handling content priorities); decision-maker attendance rate (low % = multi-threading problem); follow-up-requested distribution (what does the market actually want); and most-asked technical concern categories (product / engineering input). Group by rep and time period. Use the result of "Check the Demo meeting type", "Set what the demo summary 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 /demo-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 ChaudharyDiscovery call qualification fieldsGenerates an AI summary for Discovery calls from meeting data using the qualification framework in the summary recipe.View recipe 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

    More recipes by Sid Chaudhary

    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 Return rate by categoryShows which product categories get returned most, and which ones have got worse since last quarter.View recipe

    Got a play worth sharing?

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

    Submit a recipe