Technical Demo Run of Show Template
Published October 21, 2026 · By Kate Steinmeyer · Templates & Scripts

A technical demo run of show keeps the buyer's question, the live path, and the backup evidence in one place. Use this template for a 30-minute session and change the timing to match the buyer's agenda.
Copy the session plan
| Time | Lead | Action | Buyer question answered | Backup |
|---|---|---|---|---|
| 0–3 min | AE | Confirm goal and decision criteria | What do we need to evaluate? | Written agenda |
| 3–5 min | SE | State environment and sample data limits | What is real in this demo? | Setup slide |
| 5–15 min | SE | Show one core workflow | Can our team do the task? | Approved recording |
| 15–22 min | SE | Show the requested technical proof | Does it fit our constraints? | Architecture or test evidence |
| 22–27 min | Buyer + SE | Questions and bounded exploration | What remains uncertain? | Follow-up log |
| 27–30 min | AE | Summarize evidence and next step | What happens next? | Recap email |
Fill in the actual workflow, role, account, record, and success state before the meeting. Mark every claim that needs verification.
Add a recovery note
Write the fallback next to each live step: “If [step] fails, show [approved asset], explain [limit], and name [follow-up owner and date].” Test the fallback link from the presenting machine. A backup recording can preserve the meeting, but it should be labeled as recorded evidence.
Rehearse the handoff
The AE owns the opening, decision context, and close. The SE owns the technical demonstration and its limits. Agree on who answers implementation, security, and roadmap questions, and who records open items. In the recap, distinguish what the buyer saw live from recorded evidence and questions still awaiting verification.
For choosing the technical depth, see the technical demo guide.
Fill the plan with one buyer task
For a fictional buyer evaluating data imports, the session goal might be: “Determine whether a sample file can be mapped, imported, and checked for rejected rows.” At minute five, the SE should state that the account contains synthetic data. At minute 15, the buyer should have seen the import summary and error review. At minute 22, any integration or scale question that was not tested goes into the follow-up log.
Before the session, send the agenda to the AE and SE and verify the backup asset opens. Afterward, compare the planned proof with what the buyer actually saw. If the live step failed and only a recording was shown, say so in the recap. That makes the run of show useful as an evidence record, not merely a timing script.