The buyer replies to your meeting reminder: “Can we focus on reporting?” Your solution engineer has spent the morning preparing an approval-workflow demo. Both people did their jobs. The preparation process let them down.
A useful pre-demo email confirms the meeting's purpose, offers one optional product preview, and asks one easy question about the buyer's priorities. Use the reply and any demo engagement to propose a better agenda, not to make watching a condition of attending. The call should still work if the buyer arrives without opening the email.
I wouldn't judge this email by how many people click. I'd judge it by whether the presenter knows what to show, what to skip, and what still needs a conversation.
What should a pre-demo email include?
Include the problem you expect to discuss, one relevant preview, and a question the buyer can answer without watching. Explicitly say that the preview is optional.
A pre-demo email is a message sent before a scheduled product demonstration to establish context and help shape the agenda. It supports discovery; it doesn't replace it.
The most useful sentence is often the one explaining what the preview shows. “This shows how work gets reassigned when the usual approver is unavailable” is a concrete promise. “Get familiar with our platform” gives the buyer a task without a reason.
Build the message in this order:
- Restate the context. Use the buyer's language from the booking conversation.
- Offer one preview. Explain the workflow it demonstrates before presenting the link.
- Ask for direction. Invite a priority, correction, or constraint.
- Remove the obligation. Confirm that you can cover the essentials together.
Leave out the deck, the discovery questionnaire, and the collection of customer resources. Those may become useful later. Right now, they compete with the one decision you need: where should the conversation start?
What does a good pre-demo email look like?
A good email sounds like a rep preparing for a specific conversation, not a sequence announcing the next step. Keep the question useful even if the recipient ignores the link.
Here's an illustrative example for a buyer who mentioned approval delays:
Subject: Approval routing or reporting for our call?
Hi [first name],
You mentioned that approvals stall when work moves between departments. For our call, I suggest we start with how requests reach the right approver and what happens when someone is unavailable.
Here's an optional preview of that workflow: [focused demo link]. It shows the standard process so we can spend our conversation on where yours differs.
Which is the bigger issue today: getting work to the right person, or seeing where it's stuck?
No need to watch beforehand. We can cover the essentials together.
[Rep name]
The question gives the buyer permission to redirect the meeting. A reply such as “Actually, we need reporting across departments” is not a failure of personalization. It's exactly the correction you wanted before the solution engineer started preparing.
If all you have is a website booking, don't manufacture familiarity. Try: “Is there a workflow you want us to focus on? You can also use the optional preview to choose the topics most relevant to you.”
And don't promise a viewing time unless you've checked it. A preview that runs longer than advertised starts the meeting with a small but unnecessary breach of trust.
Which product preview should you send?
Send the smallest demonstration that makes the buyer's problem concrete. When you don't know their priorities, let them choose rather than burying your guess inside a generic product tour.
Dale, the demo automation platform, uses reusable Pages for individual topics and Walkthroughs for screenshot-based, step-by-step exploration. A Linear Demo built around buyer priorities lets viewers rate topics Important / Somewhat Important / Not Important, then assembles the experience around those choices.
That distinction matters when “show us approvals” could mean routing, delegation, audit history, or reporting. A name-personalized introduction won't resolve that ambiguity. A meaningful topic choice can.
| What you know | What to send | What still needs discussion |
|---|---|---|
| One specific workflow matters | A Basic Demo (Single Experience Demo), or a custom link to selected topics | How the buyer's process differs |
| Several problems are in scope | A Linear Demo with relevant topic choices | Which priority should lead the call |
| Different roles need different context | A Branched Demo using preset choices | Where stakeholder requirements overlap or conflict |
| A custom requirement needs validation | A clearly labeled standard workflow example | Whether the requirement can actually be supported |
Keep that last distinction explicit. Showing a standard permissions workflow does not prove compatibility with a buyer's custom access model. Write “This illustrates the standard process; we'll validate your exception together.”
For known contacts, personalized demo links associate activity with the invited contact without another details prompt. Custom links can also take prospects straight to selected content. Treat the activity as useful context, not proof that every stakeholder has evaluated the workflow.
When should you send a pre-demo email?
Send it while the meeting context is fresh and the buyer still has time to respond. There is no useful universal rule that outweighs how the appointment was booked.
As an illustrative starting point, try the business day before the call. For a same-day booking, include the optional preview in a short confirmation rather than sending a separate preparation sequence. If the meeting is further away, capture priorities early enough for pre-sales to act on them.
The account executive or SDR managing the appointment should own this message. The solution engineer can help select the content, but shouldn't have to send a second introduction explaining the first.
Keep calendar reminders separate from content nudges. A reminder helps someone attend. A “you haven't watched yet” email turns a courtesy into homework. Unless the buyer asked you to follow up on the resource, leave it alone.
How should demo engagement change the agenda?
Use engagement to propose an agenda, then ask the buyer to confirm it. Topic selections are clues about priorities, not an approved requirements document.
Before the call, review the buyer's reply alongside topic ratings, relevant Walkthroughs, and document downloads. A direct statement about a deadline or blocker should carry more weight than your interpretation of a replay.
Here's how I'd translate observations into questions:
- Approval routing rated Important: “Should we start with how approvals get assigned today?”
- A permissions section replayed: “Are there access rules we should test against the standard workflow?”
- Reporting marked Not Important: “I'll keep reporting brief unless there's a dependency we need to cover.”
- A technical document downloaded: “Would it help to bring the implementation questions into this discussion?”
Notice what's missing: “I saw you replay that section.” You can use the information without narrating the tracking.
Rewatching deserves particular caution. It might mean interest. It might mean the explanation was confusing. Interpret Buying Intent Signals from demo activity together, and turn uncertain interpretations into questions rather than confident CRM notes.
Give the presenter a compact brief with separate labels for buyer stated, observed, and needs confirmation. For example: the buyer stated that approvals stall; they selected delegation; whether absence coverage is the main cause still needs confirmation. That separation makes a pre-sales preparation process more useful than a pasted activity log.
What if the buyer doesn't watch the preview?
Run the meeting as planned. No visible viewing activity is missing information, not evidence that the buyer is unqualified.
Open with a choice: “Would a quick look at the standard workflow help, or should we start with your current process?” Don't ask whether they “did the demo.” You said it was optional.
This fallback is where demo automation either saves work or creates it. If reps prepare two full presentations, one for viewers and one for non-viewers, you've added a branching production process to every meeting.
Instead, keep one reusable introduction to the relevant workflow, followed by discovery. Skip the introduction when it isn't needed. The warm-up should remove repetition when possible, not make the meeting dependent on content consumption.
Can you automate follow-up without sending the wrong message?
Yes, but behavior-based follow-up needs an owner and a check against the conversation already underway. Someone with a meeting booked doesn't need an automated invitation to book another one.
Dale supports Segments based on behaviors such as topic selection, link clicks, and attachment downloads. Campaigns can send once or trigger when a new contact joins a segment, with messages sent through the rep's Gmail, Outlook, or company SMTP.
For an illustrative workflow, a reporting-topic selection and related document download could prompt a reporting-focused resource. Before a scheduled call, though, the useful next step may simply be updating the presenter's agenda. Not every signal needs an email.
Set outreach ownership and meeting-status checks in your CRM or operating process before configuring Segments and Campaigns for behavior-based follow-up. Don't assume behavior triggers supply calendar reminders or every suppression rule your team needs.
Check Dale pricing for the demo types and automation capabilities your pilot requires. Evaluate interactive demo software against this actual workflow, not a feature list you may never use.
How do you tell whether pre-demo emails are helping?
Measure preparation effort and the usefulness of the call, not just preview clicks. An email that gets fewer views but surfaces the buyer's real question can still be doing its job.
For an illustrative pilot, choose one common workflow and comparable opportunities. Record preparation time, whether the opening agenda needed correction, and whether the meeting produced a buyer-confirmed next step. Note booking source and sales stage so you aren't comparing unrelated audiences.
Use this short launch checklist:
- The preview delivers the specific promise in the email.
- The buyer can answer the question without watching.
- One rep owns pre-meeting communication.
- The presenter has a no-preview opening ready.
- Sales and pre-sales review effort as well as engagement.
Pick an upcoming meeting and write its warm-up using the buyer's last actual question. If you need to inspect the delivery experience first, try the Dale interactive demo, then build one focused preview before expanding the process.