Skip to main content
SEs walk into demos blind more often than they’d admit — they know the prospect’s name and the deal size, not their tech stack, integration patterns, or what their team has been Googling. A demo-prep Agent builds the brief the SE wishes they had, every time.

​
When this pays off

Back-to-back demos

SEs run 4+ demos a day and prep blurs into the prior one.

Technical context is shallow

The CRM has firmographics; the SE needs tech stack, scale, and likely integration patterns.

Demos feel generic

SEs use the same demo flow for every prospect because there’s no time to tailor.

Tribal knowledge in handoffs

AE-to-SE deal handoffs lose detail. The SE rediscovers what the AE already learned.

​
The shape of this use case

A demo-prep Agent takes a calendar event + opportunity and returns a structured technical brief.

Inputs

Calendar event, opportunity record, attendees, deal stage, prior conversation notes.

Sources

CRM, prior call notes, public tech stack signals, past similar deals, your demo playbook.

Output

A one-page brief — account context, likely tech stack, integration angles, suggested demo flow, anticipated objections.

Delivery

Emailed to the SE before the call, attached to the calendar event, posted in Slack to the deal channel.

​
Where to start

Two ways in, depending on whether you want something running today or built to your exact spec.

Clone a pre-built Agent

Open the Pre-Meeting Prepper. More in the Marketplace.

Build your own

Start from scratch in the builder, or by describing it in Claude Code or Cursor with Programmatic GTM.
Either way, these are prompts your SEs can use on day one:
  • “Demo with Acme tomorrow — what’s their tech stack, what integration angles should I lean on, and what objections has the AE flagged?”
  • “Globex is on my calendar next Tuesday. Walk me through how to position our enterprise SSO story for their auth setup.”
  • “What’s the right demo flow for a mid-market manufacturing prospect comparing us against Competitor X?”

​
Where to take it

Once it’s running, deepen it in three moves:

Give it a playbook

Shape it with a prompt and your demo playbook, battle cards, and objection docs in Knowledge.

Automate it on signals

Wrap it in a workflow that fires on a trigger.

Let it improve

Feed back which brief sections SEs use into the Agent’s evals so briefs sharpen over time.

​
Common pitfalls

A five-page brief doesn’t get read in the five minutes before a call. Cap the length and force the prompt to prioritize.
Without segment-specific Knowledge, the brief recommends the same demo flow for every prospect. Branch on segment and use real exemplars.
The CRM hasn’t been updated since the discovery call but the brief reads as if it were live. Have the Agent disclose when the freshest signal is and flag stale data.
The brief ignores what the AE already learned because notes live in another tool. Pull AE notes into the source set explicitly.