Revenue Enablement report
Demo Script Builder: your result
This answer uses a made up example company. Change the details above and press Run to see your own result.
Demo Script Builder
Create a demo script built around buyer outcomes
For account executives and solutions engineers. The decision: what do we show in this demo, and in what order?
Give it the demo type and your solution, and get a demo script with a time plan, preparation checklists, every part from opening to close and a checklist for after the demo.
What you get
This sample is a made up example, built from the inputs behind Fill in an example. It shows part of one section of the answer.
The plan
| Part | Time | What happens |
|---|---|---|
| Opening | 4 min | Asks for the main problem, states the outcome |
| Confirm | 4 min | Plays the problem back and asks 1 person |
| Demo | 16 min | 3 steps: the workflow the buyer described, end to end, with their own example, the controls, reports and audit trail the buyer's reviewers will ask for and where it sits among the systems the buyer already runs |
| Discussion | 4 min | Open questions |
Who sees what
| Person | Role | What they came for | Shown in |
|---|---|---|---|
| Head of Last-Mile Operations | operations leader | daily execution, service levels and cost per unit of work | Step 1 |
See the full example answer or run it with your own details.
Result
When a tool is not enough: if the decision needs more than one answer, talk it through in a call. Book 45 minutes with Shashwat.
What next? Work with Shashwat Try another tool See all 85 tools and skills
Example answer
Generated on 2 November 2026 from this branch, with the inputs behind Fill in an example. Your own inputs give a different result.
Revenue Enablement report
Example: Demo Script Builder
Show the full result
Demo Script: First look
Acceptance conditions to agree before the script
No must show features supplied. Name the buyer task and agree the observation, approver and pass condition before using this script.
No acceptance criterion is treated as agreed from a feature name alone. Keep the buyer's wording and evidence beside each condition.
Our product, first look, 30 minutes, for the Head of Last-Mile Operations (Third-party logistics). 3 steps, each built on a problem you named and tied to the people it matters to.
Sector: not clear from your inputs (name the industry for sector notes). Business model: not stated. Tell us how you charge and the plan will adjust.
The plan
| Part | Time | What happens |
|---|---|---|
| Opening | 4 min | Asks for the main problem, states the outcome |
| Confirm | 4 min | Plays the problem back and asks 1 person |
| Demo | 16 min | 3 steps: the workflow the buyer described, end to end, with their own example, the controls, reports and audit trail the buyer's reviewers will ask for and where it sits among the systems the buyer already runs |
| Discussion | 4 min | Open questions |
| Close | 2 min | Agrees the next step |
Who sees what
| Person | Role | What they came for | Shown in |
|---|---|---|---|
| Head of Last-Mile Operations | operations leader | daily execution, service levels and cost per unit of work | Step 1 |
Demo Script
Part 1: Opening (4 minutes, from 0:00)
Say: "Thanks for making the time. Over the next 30 minutes I will take you through our product, with the Head of Last-Mile Operations in the room, with Third-party logistics in mind."
Say: "What I would like by the end of this session is a clear next step that we both agree."
Say: "The plan: first I confirm that I have your problem right, then 16 minutes of demo in 3 steps (the workflow the buyer described, end to end, with their own example, the controls, reports and audit trail the buyer's reviewers will ask for and where it sits among the systems the buyer already runs), then your questions, then the next step."
Ask: "Before I share my screen: Head of Last-Mile Operations, what would make these 30 minutes worth it for you?"
Part 2: Confirm (4 minutes, from 4:00)
Say: "I have not been told your main problem, so before I show anything: what is the one thing you most want solved?"
Ask the Head of Last-Mile Operations: "Before I show the workflow the buyer described, end to end, with their own example: which part of the day goes wrong most often, and what does it cost?"
Ask: "What is the one thing you most want solved?"
Part 3: Demo (16 minutes, from 8:00)
Say: "Let me share my screen. I will keep to what you asked to see, one step at a time."
Step 1: The workflow the buyer described, end to end, with their own example (about 5 minutes)
Step 1 is for the Head of Last-Mile Operations, because the workflow the buyer described, end to end, with their own example is the part closest to their work.
On screen: our product on one real case of "The workflow the buyer described, end to end, with their own example", using an example from Third-party logistics. Take one real case through it from its start to the result the user sees.
Say: "This one is for the problems you named. I will take one real case through it from its start to the result the user sees."
Ask: "How does the Head of Last-Mile Operations work with the workflow the buyer described, end to end, with their own example today, and what would change for them in the first week?"
Step 2: The controls, reports and audit trail the buyer's reviewers will ask for (about 5 minutes)
On screen: our product on one real case of "The controls, reports and audit trail the buyer's reviewers will ask for". Pick one live example from your side and run it through from the beginning.
Say: "This one is for the problems you named. I will pick one live example from your side and run it through from the beginning."
Ask: "Which number tells you the controls, reports and audit trail the buyer's reviewers will ask for is working, and who looks at that number?"
Step 3: Where it sits among the systems the buyer already runs (about 5 minutes)
On screen: our product on one real case of "Where it sits among the systems the buyer already runs". Run a case you chose, not one I prepared, and stop at the first thing that looks wrong.
Say: "This one is for the problems you named. I will run a case you choose, not one I prepared."
Ask: "What would make where it sits among the systems the buyer already runs worth keeping after a month?"
Part 4: Discussion (4 minutes, from 24:00)
Say: "I will stop sharing here. What did that raise for you?"
Part 5: Close (2 minutes, from 28:00)
Say: "Which capabilities and pass conditions must the buyer agree before a pilot?"
Say: "Here is what we covered. You also saw the workflow the buyer described, end to end, with their own example, the controls, reports and audit trail the buyer's reviewers will ask for and where it sits among the systems the buyer already runs."
Say: "What would be the right next step from here, and who should be part of it?"
If yes. Say: "I will send a summary of what we covered and an invite for the next step. Who else should be on it?"
If hesitant. Say: "Which of the problems we played back is still not answered for you? I want you to have everything you need."
After The Demo
- Send the summary promised in the close, and brief your champion separately.
To sharpen this, give: attendees (it would add a row and a question for each person, and choose the parts they should see); key pain points (it would choose which parts are shown and what the playback says; now the steps follow the order of your description); competitor context (it would add a side by side line and sharpen the difference answers); must show features (it would fix the flows that are always shown; now the steps come from the usual demo list of this kind of seller); known objections (it would add a spoken answer to each; none is answered now); desired outcome (it would change the close; now it agrees the next step); your solution (list the parts of the product with a few words on what each does; it would make the steps the product's own parts).
Suggested timings, lengths and counts: adjust them to your own.
When a tool is not enough: if the decision needs more than one answer, talk it through in a call. Book 45 minutes with Shashwat.
How to read the answer
The builder creates a timed, five-part demo plan (Opening, Confirm, Demo in 3 steps, Discussion, and Close) scaled to your Demo duration (such as 30 minutes), along with a Who sees what table and spoken Say: and Ask: prompts. At the top, Acceptance conditions to agree before the script warns you that if no Must show features or Key pain points were supplied, the three demo steps use generic seller workflows (The workflow the buyer described, The controls, reports and audit trail, and Where it sits among the systems) and you must confirm the buyer's main problem in Part 2: Confirm before sharing your screen.
What to do next
- Founder: Before running the demo, fill in Key pain points, Must show features, and the specific parts of Your solution so the three demo steps show your actual product flows rather than generic placeholders.
- CEO: Make sure every demo ends with Part 5: Close by agreeing on the exact capabilities, pass conditions, and participants required for a pilot.
- CMO: Supply the industry example data and competitive side-by-side talking points so the solutions engineer can run a real case from the buyer's sector in Step 1.
- CRO: Train reps to follow Part 2: Confirm strictly: never share the screen until the primary audience member confirms the one problem they most want solved in these 30 minutes.
- Demand generation head: Use the After The Demo follow-up step to send prospects a recap template and a link to relevant technical or security documentation.
Why come back
Re-run the builder for each live deal once discovery is complete, adding the full list of Attendees, Key pain points, Must show features, and Known objections, or when switching from a First look to a Technical deep dive, Executive overview, or Proof of concept. The tool applies the same fixed rules every time. It does not call an AI model, and this site does not keep what you enter.
Who is the Demo Script Builder tool not ideal for?
- Anyone who cannot give the inputs listed above, because the answer is built only from them.
- Teams that want the tool to read their CRM, email or call notes: it works only from what you type.
- Anyone who wants to send the output straight to a buyer: every output is a draft for a person to review first.
How do I use the Demo Script Builder tool with an AI assistant?
Add Revenue Enablement once (see Use it in Claude, ChatGPT or Gemini), then ask in plain words. Here is a prompt built from the tested example:
My role is not stated. Ask me for my role first. Use Revenue Enablement's Demo Script Builder tool. demo type: First look; your solution: our product; demo duration: 30; primary audience: Head of Last-Mile Operations; customer industry: Third-party logistics. If this tool is unavailable, ask me to open its web page; do not invent its output. In Gemini CLI or Antigravity, use the Helix GTM Suite skills package for related guidance, without claiming to run this connector.
How does the Demo Script Builder tool work?
You do not need to sign in. A web browser is enough, and the answer comes back in a second or two.
- Fill in the form above, or press Fill in an example.
- Press Run Demo Script Builder.
- Read the result on this page, then copy it and edit it before you use it.
It applies fixed rules in the Revenue Enablement code to the inputs above and returns text. It does not call an AI model, does not look anything up, and does not store what you type. The web form and the AI assistant connector run the same tool code, so the same input gives the same answer in both.
Previous: Email Sequence GeneratorNext: Pricing Negotiation Guide
For developers
MCP tool name: demo_script_builder. REST: POST https://revenue-enablement.gtmhelix.com/api/tools/demo_script_builder with this JSON body (see How it works):
{
"input": {
"demo_type": "first_look",
"your_solution": "our product",
"demo_duration": 30,
"primary_audience": "Head of Last-Mile Operations",
"customer_industry": "Third-party logistics"
}
}
Choose your app
Run a Helix tool in your browser, then take the result to ChatGPT, Claude or Gemini. Connectors work with supported plans in Claude, ChatGPT, Cursor, VS Code and Windsurf. The Helix GTM Suite skills package supports Claude Code, Gemini CLI, Antigravity, Cursor and VS Code, and is available through skills.sh. Each plugin has its own installation steps, below or on its own page.
Connector setup guides · Skills package setup guide · Find the skills on skills.sh