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

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

At a glanceDemo script flow for Harbor FreightlinesOne segment per ranked pain, each ending with a check-in question
  1. Opening60 secondsRestate the three pains and the order
  2. Faster Month-End Close3 minutesClose takes 9 days; show unposted invoices and ERP sync
  3. Stopping Duplicate Payments3 minutes2 duplicates, about $14,000; show duplicate flag
  4. Approvals Out of Email3 minutesMobile approval and auto-reminder after 48 hours
  5. Close2 minutesRecap and propose 30-minute session with ERP admin

Example for: an AP automation tool demo to Harbor Freightlines, a 300-person logistics firm, with the controller and AP lead attending.

Pain Ranking

PainEvidence from notesPriority
Month-end close takes 9 daysController: "We're always the last department to close."1
Duplicate invoice paymentsAP lead found 2 duplicates last quarter, about $14,0002
Approvals stuck in email"Invoices sit in managers' inboxes for a week."3

Opening (60 seconds)

"Thanks for the time. You told us close takes nine days, duplicates cost you around $14,000 last quarter, and approvals stall in email. We'll take those in that order, about three minutes each, and stop after each one to check it fits."

Segment 1: Faster Month-End Close

  • Time: 3 minutes
  • Pain restated: "We're always the last department to close."
  • What to show: Dashboard > Close Status > Unposted Invoices filter > Bulk sync to ERP
  • Talk track: "Here's every invoice not yet posted, by age. One click syncs approved items to your ERP, so the final week of chasing becomes a filtered list."
  • Check-in question: "Which part of those nine days would this remove, and which part would still be manual?"

Segment 2: Stopping Duplicate Payments

  • Time: 3 minutes
  • Pain restated: Two duplicates slipped through last quarter.
  • What to show: Upload two invoices with the same vendor and amount > Duplicate flag > Hold reason
  • Talk track: "Matching checks vendor, amount, date and invoice number before anything reaches a payment run."
  • Check-in question: "How were last quarter's duplicates caught, and would this check have stopped them?"

Segment 3: Approvals Out of Email

  • Time: 3 minutes
  • Pain restated: "Invoices sit in managers' inboxes for a week."
  • What to show: Approval rules > Mobile approval > Auto-reminder after 48 hours
  • Talk track: "Managers approve from their phone, and reminders go out automatically, so nobody on your team chases them."
  • Check-in question: "Who are the slowest approvers today, and would mobile approval change how they work?"

Gap note: The notes mention multi-currency invoices from Canada. Confirm whether that is in scope; if your product handles it only partially, say so in Segment 1 rather than waiting for them to ask.

Close (2 minutes)

Recap the three pains and what each segment showed. Propose a 30-minute session with their ERP admin next week to confirm the sync.

Confirm Before the Call

  • Which ERP and version they run
  • Who signs off on budget besides the controller
  • Monthly invoice volume
Written by AI from this prompt. Your results will vary.

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 in Sales