Account executives, Sales reps, Sales engineers, Founders, Sales managers
Prepare the Required Inputs listed in the Workflow Prompt. Use as much detail as necessary.
1. Copy the Workflow Prompt.
2. Paste it into your AI tool.
3. Replace the "Required Inputs"
4. Run the prompt.
Get access to this workflow and 1000+ others designed to save hours and get better results with AI.
You are a sales demo strategist. Your task is to create a tailored product demo script that shows only the most relevant parts of the offer and connects each section to the buyer's stated problems, goals, and decision needs.
### Required Input
- Offer: [Product, service, or solution being demonstrated, e.g. onboarding software for customer success teams]
- Target Buyer: [Role, seniority, company type, and likely priorities]
- Buyer Situation: [What is happening now, e.g. manual onboarding causes delays and inconsistent handoffs]
- Confirmed Pain Points: [Specific pains from discovery, e.g. low visibility, rework, missed launch dates]
- Desired Outcomes: [What the buyer wants to improve, e.g. faster time-to-value and fewer support escalations]
- Demo Length: [Available time, e.g. 20, 30, or 45 minutes]
- Features or Capabilities to Show: [Only list relevant capabilities]
- Known Objections or Concerns: [Budget, adoption, security, complexity, migration, stakeholder buy-in]
- Next Step Goal: [What should happen after the demo, e.g. technical review, pilot, proposal]
### Input Validation
Review all inputs before creating the script. If the buyer situation, pain points, offer, demo length, or next step goal is missing or too vague, ask specific clarification questions. Pause and wait for clarification before generating the final output.
### Instructions
Create a demo script that is consultative and buyer-specific. Do not produce a generic feature walkthrough. Every demo section should answer why this matters to this buyer now.
Start with a short opening that confirms the buyer's priorities and sets the agenda. The opening should make it easy for the buyer to correct the focus before the demo begins.
Sequence the demo around the buyer's workflow or business problem, not the product menu. For each demo moment, include what to show, what to say, what pain or outcome it connects to, and what confirmation question to ask.
Include transitions that connect one section to the next. Avoid dumping features. If a feature is not clearly tied to a buyer priority, mark it as optional or remove it.
Prepare objection-handling prompts for known concerns without sounding defensive. Include points where the seller should pause, check relevance, and invite questions.
End with a close that summarises the buyer's priorities, confirms whether the demo addressed them, and asks for the next step aligned with the sales stage.
### Output
Provide the demo script in this format:
1. Demo Strategy Summary
2. Opening Agenda Script
3. Buyer Priorities to Confirm
4. Demo Flow by Section: What to Show, What to Say, Why It Matters, Confirmation Question
5. Features to Emphasise
6. Features to Skip or Keep Optional
7. Objection Handling Prompts
8. Buyer Engagement Questions
9. Closing Script
10. Recommended Next Step
Create a shorter version for a 15-minute demo with only the highest-impact sections.
Offer: Customer onboarding workflow platform for SaaS teams
Target Buyer: Head of Customer Success at a 180-person SaaS company
Buyer Situation: Onboarding is managed through spreadsheets, Slack, and manual follow-ups, causing delays and lack of visibility across teams
Confirmed Pain Points: Missed onboarding milestones, lack of ownership clarity, reactive escalations, inconsistent customer experience
Desired Outcomes: Faster onboarding completion, clear ownership, proactive risk detection, consistent onboarding experience
Demo Length: 30 minutes
Next Step Goal: Secure multi-stakeholder demo with CS Ops and Product
Strategy: Run the demo through a single onboarding journey to show how visibility, ownership, and proactive alerts replace manual coordination.
"Based on what you shared, onboarding delays and lack of visibility are creating risk as you scale. I’ll walk through one onboarding journey to show how teams move from manual coordination to structured workflows. Stop me if something doesn’t match your process."
Section 1: Onboarding Workflow Setup
What to Show: Pre-built onboarding template
What to Say: "This replaces spreadsheets with a defined workflow tied to each customer"
Why It Matters: Eliminates inconsistency and manual coordination
Question: "How close is this to how your onboarding is structured today?"
Section 2: Task Ownership and Handoffs
Show: Task assignments and ownership tracking
Say: "Each task has a clear owner, removing ambiguity"
Why: Solves ownership confusion
Question: "Where do handoffs typically break today?"
Section 3: Progress Visibility Dashboard
Show: Customer onboarding dashboard
Why: Real-time visibility replaces manual reporting
Question: "How do you currently get this level of visibility?"
Section 4: Risk Alerts
Show: Missed milestone alert
Why: Moves from reactive to proactive management
Question: "Would this have helped in recent escalations?"
"We already use spreadsheets" ? "This keeps your process but removes manual tracking and delays"
"We focused on visibility, ownership, and proactive alerts. Does this align with what you need to improve onboarding?"
Schedule deeper demo with CS Ops and Product stakeholders
Get access to all workflows, across every sector, with structured systems built for better results.