Demo script framework
A demo script is not a word-for-word script, it is a structure that keeps every part of the demo tied to a buyer outcome.
Tell-show-tell is the backbone: context, proof, payoff, for each thing you show.
Short answer
A demo script framework uses a tell-show-tell structure for each capability: tell them the problem it solves, show it solving that problem with their use case, and tell them the outcome it produces. Repeat for the two or three capabilities that matter. The reusable outline is below, ready to adapt to any deal.
The framework
Fill this in per deal.
- Recap (2 min): "Last time you told me {pain 1} and {pain 2} were costing you {impact}. Today I will show how we handle exactly those."
- Capability 1 - Tell: "You said {pain 1}. Here is how we solve it."
- Capability 1 - Show: demonstrate it with the buyer's use case and data.
- Capability 1 - Tell: "So instead of {old way}, you get {outcome}. Does that address it?"
- Repeat tell-show-tell for capabilities 2 and 3.
- Summary: recap the outcomes shown and confirm they fit.
- Next step: agree a specific next action with a date.
Rules for the script
Discipline keeps it converting.
- Only include capabilities that solve a discovered pain.
- Confirm value after every capability, not just at the end.
- Use the buyer's language and data throughout.
Use this in Ardovo
You do not have to start from a blank page. Tell Rook, Ardovo's AI operator, what you need (for example, "demo script framework") and it drafts a version grounded in your real pipeline, personalizes it to the specific deal or contact, and saves it to the record in one step. Every framework lives in one shared library, so the whole team runs the same play.
Frequently asked questions
What is the tell-show-tell demo structure?
A pattern for each capability: tell the buyer the problem it solves, show it solving that problem with their use case, then tell them the outcome it produces. It keeps every feature anchored to a buyer need and confirms value continuously rather than only at the end.
Should a demo script be word for word?
No. It should be a structure, not a monologue, so you can stay conversational and adapt to the buyer's reactions. The framework keeps every part tied to an outcome while leaving room for the questions and check-ins that keep a demo two-way.
How do I adapt the framework to a specific deal?
Pull the two or three pains from your discovery notes, slot each into a tell-show-tell block, and configure the show step with the buyer's use case and data. The structure stays the same; the content changes per deal, which is what makes the demo feel tailored.