Prepare for a demo from the last call

Demo preparation is the work that gets skipped when the calendar is full. Properly done it means re-listening to two calls, reading the opportunity history, checking whether anything has changed at the company, and rebuilding a deck around what this particular buyer said. Realistically it means opening the standard deck ten minutes before, changing the logo, and hoping the notes from six weeks ago are still in someone's head.

The material is all recorded. The calls are transcribed, the deal history is in the CRM, and what changed at the company since is public. What is missing is the twenty minutes to join them, which is the part that does not need a person.

What goes into the demo prep brief

The run opens from the next demo on Google Calendar, timed so the brief and the deck are ready before it starts. It gathers three kinds of material:

• Every recorded call with the company, from Granola, searched by attendee email and separately by company domain, because the person you are meeting may sit on a colleague's call rather than their own. Four things come out of each call: the problems they described, in their words; any objection, and whether it was resolved; commitments, with who owes what; and the names and roles of everyone who spoke.
• The opportunity, from HubSpot: stage, value, close date, owner and the history of stage changes. A deal that has slipped its close date twice is a different meeting from one that just opened, and the brief says which one this is.
• What changed since the last call. Public news about the company, found with Serper: a funding round, a leadership change, a product launch, a reorganisation. Role changes come from the attendees' own LinkedIn profiles. Anything worth mentioning keeps its source URL. A demo that opens on something that happened last week is a demo where they know you were paying attention.

What makes AI demo prep hold up

Quote them, do not summarise them. A buyer who said "we lose two days a month reconciling the two systems by hand" has handed over the exact sentence to repeat back. Compressed into "integration challenges" it becomes indistinguishable from every other account, and the deck reverts to the standard one with a logo swapped in.

The stakeholder who has never spoken is the highest-value line in the brief and the easiest to miss by hand. The CRM knows there is a head of operations on the account; the call transcripts show only the two people who attend everything. That gap is usually where the deal gets decided, and spotting it means comparing two systems nobody compares.

Leaving placeholders instead of numbers keeps the draft usable. A model asked to build a deck will happily produce "reduces reconciliation time by 60%", which is a figure nobody can source, said out loud in a room where someone may ask. A visible bracket is a prompt to the presenter; an invented number is a liability that looks finished.

A demo deck built from what the buyer said

The draft deck follows the problems from the calls, in the order the buyer raised them. Its sections exist because they said those things:

• One slide per problem they actually named. If they named three problems, the deck has three problem slides.
• One slide for every objection left unresolved on the calls. Skipping it means it gets raised in the room instead, with less preparation.
• A bracketed placeholder wherever a claim needs a number.

The brief goes to Slack first and the deck link second. The brief is what someone reads on the way into the room; the deck is what they open once they are there. It leads with the single most important thing, which is usually either an unresolved objection or a stakeholder who has never spoken.