Build a Sales Demo Script Ordered by the Prospect's Stated Pains
Turns your discovery notes into a timed demo script with one 3-minute segment per ranked pain, a talk track, and a check-in question after each segment.
You getPain ranking table, opening and segments
Prompt
You are a senior solutions engineer who runs product demos for B2B software deals.
I will paste my discovery notes after this prompt, plus a short description of my product. Build a demo script ordered by the pains the prospect actually stated.
Rules:
1. Rank pains by how strongly the prospect expressed them (cost, urgency, who raised it) and open with the top pain, not a product overview.
2. Write one segment per pain, each capped at 3 minutes, with a talk track the presenter can read aloud.
3. Start every segment by restating the pain in the prospect's own words from the notes, then show only the features that solve it.
4. End every segment with one open check-in question that confirms fit or surfaces a gap.
5. If a pain has no matching feature, say so plainly and suggest an honest way to handle it instead of skipping it.
Output format:
- Pain ranking table: Pain | Evidence from notes | Priority
- Opening (60 seconds): agenda tied to their pains
- Segments: Title, Time, Pain restated, What to show (click path), Talk track, Check-in question
- Close (2 minutes): recap and proposed next step
Finally, list any pains, stakeholders or details missing from the notes that I should confirm before the call.Example output
Tips and common edits
Why this works
- Ranking pains by evidence from the notes puts the prospect's biggest problem first instead of a generic product tour.
- The 3-minute cap per segment keeps the demo tight and stops feature dumping.
- A check-in question after each segment turns the demo into a conversation and surfaces objections early.
Use before a scheduled demo once discovery is done. Paste your raw discovery notes and a few lines on your product into ChatGPT, Claude or Gemini. Messier notes are fine; quotes help most.
Common edits
- Change the segment cap to 5 minutes for complex technical buyers.
- Ask for a 15-minute version covering only the top two pains.
Prompt details
- By
- Prompts-GPT editors
- Published
Did this prompt work?
Keep exploring
More like this
Build a Give-Get Concession Ladder Before Your Contract Negotiation
You get a ranked table of every concession you could offer, scored by cost to you and value to the buyer, each paired with a specific item to ask for in return.
Build an Ideal Customer Profile and Buyer Persona from Your Best Customers
Get an evidence-backed ICP table that splits firmographic fit, pain triggers and disqualifiers, plus a buyer persona sheet and first-call qualifying questions.
Turn Product Features into Value Propositions for Each Buyer Role
Get a feature-benefit-proof table that ties every feature to a measurable outcome for each buyer role, plus one-line value props and a list of claims that still need proof.
Proposal Executive Summary and Mutual Action Plan Builder
Converts discovery notes into a one-page proposal executive summary and a dated mutual action plan. It helps a rep decide whether the deal is ready to propose and what is still missing.
Spot Negotiation Tactics in a Message and Draft a Calm Counter
Get a table naming each tactic in your counterpart's message with the quote that shows it and its aim, plus a calm reply that protects your walk-away point.
Pricing Pushback Response Playbook with Value Reframe and Concession Rules
Diagnoses what a price objection really means and builds response scripts, trade-based concession rules, and escalation criteria. It helps a rep decide whether to hold price, trade scope, or walk away.