Sales demo tracker — requests, Q&A, follow-ups

Ten demos a week, four tabs each

A demo request comes in. You run the call, field a handful of pointed questions, promise to send a recap and book a follow-up. Then the next demo starts, and the one you just finished begins to fade — the questions you meant to answer in writing, the pricing point that came up, the date you floated for round two.

The pieces all exist. The thread is in Outlook, the slot is open on the calendar, the answers are fresh in your head. They just never end up next to the prospect they belong to, so the recap gets written from memory and the next call gets booked a day later than you said it would.

One deal, every demo touchpoint

The workspace is a CRM built around your deals — a Pipeline page that lays out every active opportunity as a board by stage, Contact and Company pages for the people behind them, and a Deal Detail page that gathers everything tied to one prospect. The activity timeline on each deal is where the email thread and the scheduled call all land, next to the running call and note log.

You work the demo from that surface. Instead of digging through Outlook for the right thread or scrolling the calendar for the next opening, you ask the assistant, and it pulls the pieces onto the deal you have open.

From demo call to booked follow-up

1. Open the deal for the prospect. The Pipeline is the landing surface — every active demo as a card, grouped by stage. Open the one you just ran to see its contact, linked email threads, and meetings in a single timeline.
2. Capture the Q&A from the call. Give the assistant a quick debrief — the questions asked, the pricing point that came up, what you promised — and it writes a short, structured summary onto the deal’s timeline so the recap comes from what actually happened, not from memory a day later.
3. Book the next call. When the prospect wants a follow-up, the assistant creates the Outlook Calendar event with the attendees and links it back to the deal as an activity. The invite goes out to everyone on it.
4. Send the follow-up. The assistant drafts the recap email — grounded in the Q&A it just logged — and sends it from your Outlook account. The sent email lands on the deal timeline too, so the next person to open the deal sees exactly what was promised.
5. Pull a thread in when you need it. If an earlier email exchange with the prospect lives in your inbox, ask the assistant to find it and link it to the deal — the back catalogue and the new follow-up sit in the same place.

Pipeline shape, calendar, and segments

• Pipeline stages — the default shape fits most founder-led demos. Rename or add stages to match how you actually move a prospect from first demo to close.
• Calendar to schedule on — follow-ups land on your primary Outlook calendar by default. If you keep prospect meetings on a separate calendar, point at that one instead.
• Customer segments — group prospects by segment (say, design agencies versus mid-market SaaS) so the assistant’s recap and outreach drafts stay scoped to the kind of buyer you’re talking to.
• Follow-up templates — per-segment message shapes the assistant starts from when drafting a recap. Each carries effectiveness stats from past sends, so the angle that actually gets replies floats to the top.

One timeline per deal, the stages you choose

A demo tracker earns its keep when nothing about a prospect goes missing between calls — the questions, the commitments, the next meeting all attached to the deal rather than spread across your inbox and calendar. Wiring the debrief, the scheduled call, and the sent email to the deal itself is what lets the assistant recap from what actually happened instead of asking you to remember it.

The workspace description is what you change when the demo motion changes — when you reshape the pipeline stages, move prospect meetings to a different Outlook calendar, or open a new customer segment that needs its own follow-up shape. The demo loop stays the same; the parts you’d tune for your own team are the parts you describe.