Prompier
ApprovedSalespresentationscriptsales

Demo script outline built around the buyer's problems

PL by Prompier Library ☆☆☆☆☆ New Version 1 · updated Nov 10, 2026
Reviewed by moderator Prompier Library on Nov 10, 2026. Checked for personal data, secrets, risky instructions and a clear license.

About this prompt

Turns what you learned in discovery into a demo outline that shows only the features tied to the buyer's own problems, with questions to ask along the way. Use when you are preparing a product demo for a specific buyer.

Prompt text

You are an experienced sales engineer who builds demos around the buyer's problems, not around a feature tour. Your goal is a demo outline the seller can follow on the call. Inputs - What we learned in discovery (problems, goals, who is involved): {{discovery_notes}} - What we sell and the features that exist today: {{product_features}} - Who will attend and what they care about: {{attendees}} - Time available: {{demo_length}} Steps 1. List the buyer's problems in their own words, in priority order. If discovery notes are thin, say what is missing and ask at most 3 questions; otherwise proceed. 2. Match each problem to one feature or workflow that really exists in the product list. If nothing matches, say so and mark it as a gap to be honest about on the call. 3. Choose the 3 or 4 moments that matter most for the time available. Leave everything else out and say what you are leaving out. 4. For each moment write: the problem it answers, what to show, the line to say before it, the question to ask after it, and the sign that it landed. 5. Plan the opening (agree the goal and agenda) and the close (recap, agreed next step). Output format ## Opening (goal, agenda, timing) ## Problems in priority order ## Demo flow (one block per moment: problem, what to show, what to say, question to ask, sign it landed) ## Left out on purpose ## Gaps to be honest about ## Close and next step Quality bar - Use only the features and facts supplied; never promise a feature, result or price that is not in the inputs. - Write "Not stated" where the notes do not say. - Plain words, no jargon, and fit the time given.

Variables

4 variables
VariableWhat to enterExampleDefault
{{discovery_notes}}Paste your discovery notes: problems, goals and who is involvedClinic group with 6 sites; front desks lose time on phone bookings; no-shows hurt; manager wants one weekly view—
{{product_features}}List the features and workflows that exist todayOnline booking page, SMS reminders, shared calendar, no-show report, patient notes—
{{attendees}}Who will be on the call and what each cares aboutClinic manager (wants less admin), two receptionists (want fewer calls)—
{{demo_length}}How long the demo slot is30 minutes—

Try it

Live preview
Paste your discovery notes: problems, goals and who is involved
List the features and workflows that exist today
Who will be on the call and what each cares about
How long the demo slot is
Your finished prompt
You are an experienced sales engineer who builds demos around the buyer's problems, not around a feature tour. Your goal is a demo outline the seller can follow on the call. Inputs - What we learned in discovery (problems, goals, who is involved): {{discovery_notes}} - What we sell and the features that exist today: {{product_features}} - Who will attend and what they care about: {{attendees}} - Time available: {{demo_length}} Steps 1. List the buyer's problems in their own words, in priority order. If discovery notes are thin, say what is missing and ask at most 3 questions; otherwise proceed. 2. Match each problem to one feature or workflow that really exists in the product list. If nothing matches, say so and mark it as a gap to be honest about on the call. 3. Choose the 3 or 4 moments that matter most for the time available. Leave everything else out and say what you are leaving out. 4. For each moment write: the problem it answers, what to show, the line to say before it, the question to ask after it, and the sign that it landed. 5. Plan the opening (agree the goal and agenda) and the close (recap, agreed next step). Output format ## Opening (goal, agenda, timing) ## Problems in priority order ## Demo flow (one block per moment: problem, what to show, what to say, question to ask, sign it landed) ## Left out on purpose ## Gaps to be honest about ## Close and next step Quality bar - Use only the features and facts supplied; never promise a feature, result or price that is not in the inputs. - Write "Not stated" where the notes do not say. - Plain words, no jargon, and fit the time given.

Sample output

Opening (about 3 minutes) Goal: show how the clinics could cut phone bookings and see no-shows in one place. Agenda: three short moments, then questions and a next step. Ask the manager to say which one matters most. Problems in priority order 1. Front desks lose time on phone bookings. 2. No-shows hurt the clinics. 3. The manager wants one weekly view across 6 sites. Demo flow Moment 1 (about 8 minutes): phone bookings. Show: the online booking page and the shared calendar. Say: "You told us the phones take much of the day. Here is how a patient books without calling." Ask: "How many of your bookings could happen this way?" Landed if a receptionist names a task they would stop doing. Moment 2 (about 7 minutes): no-shows. Show: SMS reminders and the no-show report. Say: "Reminders go out on their own, and the report shows who still misses." Ask: "How do you track missed visits today?" Landed if the manager asks how reminder timing is set. Moment 3 (about 6 minutes): the weekly view. Show: the shared calendar across sites and the no-show report by site. Say: "This is the one weekly view you asked for." Ask: "What would you check first on a Monday?" Landed if the manager describes their own routine. Left out on purpose Patient notes: nobody raised it, and it would use time the three moments need. Gaps to be honest about Not stated: whether any result figures from other clinics can be shared. Do not quote any numbers on the call. Close and next step (about 5 minutes) Recap the three problems and what was shown for each. Ask the manager to agree one next step, such as a short trial with two sites, and who else should join.

An example the author shared. Your result will differ.

Reviews

No written reviews yet. If you have used this prompt, tell others how it went.