Meeting prep brief
Sends the host a brief 24 hours before a meeting: who is coming, how the account is doing, every prior touch, and what to talk about.
Authored by Sid Chaudhary
Founder & CEO at Intempt
Agentic workflow
Coming soon5 steps Blu runs end to end. It drafts a plan and nothing runs until you approve it.
- 1
Assemble the brief
Coming soonBlu builds a step
- 2
Lay it out to be skimmed
Coming soonBlu builds a step
- 3
Send it a day before
Coming soonBlu builds a step
- 4
Deliver it to the host
Coming soonBlu builds a step
- 5
Check every meeting got one
Coming soonBlu builds a step
About this recipe
When to use it
Manually pulling together a stakeholder map and prior touches before every call doesn't scale past a handful of meetings a week. This generates the brief automatically, 24 hours out. Try the standalone version free with the AI Meeting Prep Generator.
What it delivers
When a meeting is scheduled, auto-generates an AE prep brief 24 hours before it - stakeholder map, prior touches, account health, suggested talking points - delivered to the host via email or Slack.
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
“Sends the host a brief 24 hours before a meeting: who is coming, how the account is doing, every prior touch, and what to talk about.”
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.
- 01Assemble the briefCreate an AI-derived attribute on the Meeting object called 'prep_brief'. Computed at Meeting scheduled time. Output: a structured brief with sections: (a) attendees: name, title, role on deal, recent activity; (b) account snapshot: ARR, plan, health score, open opportunities; (c) prior touch history: last 5 interactions across email/meetings/support; (d) suggested talking points: AI-derived from deal stage, recent product usage, and any open support tickets; (e) competitive intel: if any flag exists. Refreshes if a new attendee is added within 1 hour of meeting time.
- 02Lay it out to be skimmedGenerate an HTML email template that renders the prep_brief attribute in a clean, scannable layout. Sections: meeting summary at top (date, time, duration, attendees), then collapsible sections for account, prior touches, talking points, competitive intel. Include a CTA button to view the brief in the app. Tone: utilitarian, not marketing. Use the result of "Assemble the brief".
- 03Send it a day beforeCreate a workflow firing on Meeting scheduled. Schedule a delayed step to fire 24 hours before the meeting (or immediately if the meeting is within 24 hours). On firing: re-compute the prep_brief attribute (catches any last-minute updates), then trigger the brief journey to deliver to the host. If the meeting is rescheduled, cancel the pending delivery and re-schedule. If cancelled, suppress delivery. Use the result of "Assemble the brief", "Lay it out to be skimmed".
- 04Deliver it to the hostBuild a 1-touch journey that sends the prep-brief email to the meeting host when triggered by the prep delivery workflow. Audience: the meeting host (not the attendees). Channel: email by default; if a Slack integration is connected and the host has a Slack ID, prefer Slack DM with a link to the brief. Use the result of "Assemble the brief", "Lay it out to be skimmed", "Send it a day before".
- 05Check every meeting got oneCompose a dashboard tracking prep-brief coverage: % of meetings where a brief was delivered, median time before meeting the brief was sent, and host open rate on brief emails. Break down by meeting type (demo, discovery, expansion, renewal). Flag any meetings where prep_brief computation failed (missing data, attribute compute error). Use the result of "Assemble the brief", "Lay it out to be skimmed", "Send it a day before", "Deliver it to the host".
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 /meeting-prep-brief 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.
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 