Product Demo AI Prompt Templates
Six AI prompt templates for product demos: build persona demo scripts, tailor to discovery calls, write talk tracks, follow up, and prep objections. Use the variants as they are, fill in the placeholders, or download the editable Word file.
Made by Anatolii Ulitovskyi 
Fact-checked by RH Fardin Updated 1. Build a demo script for a persona
When to useBuild it once per persona you sell to, then reuse it as the backbone every rep tailors before a call.
Prompt
You are a role at company, a product description. Write a demo script for persona. This persona struggles with persona pain. The capabilities worth showing are features -- do not show anything else, even if it seems impressive. The demo slot is duration. Structure the script as timed sections. Open by naming persona pain in their language and stating what the next duration will cover. For each capability, write the setup sentence, what to click, and the one line that connects it back to persona pain. Build toward outcome and script the exact words for that ask. Write it in a tone tone. Flag any point where a rep should stop and ask a question instead of continuing to talk.
How to adapt it
- Write persona pain as what their boss asks them about, not as a product gap.
- Cut features to three; a fourth almost always steals the time the closing ask needs.
- Set outcome to something concrete like a scoped pilot, so the script has somewhere to land.
Why it works
It forbids the feature tour by capping what can be shown, then forces every section to connect back to what the persona is measured on. Timed sections and scripted stop-and-ask points fix the two ways demos fail: running long, and the rep talking through the moment the buyer wanted to speak.
2. Tailor the demo to a discovery call
When to useUse it the day before the demo, once you have notes or a transcript and know who is joining the call.
Prompt
You are a role at company, a product description. Here is our standard demo script: base script. Here are the notes from the discovery call: discovery notes. These people are joining: attendees. The slot is duration and this constraint applies: constraint. Rewrite the script for this specific call. Reorder the sections so the prospect's most urgent stated problem comes first, and cut any section they gave no signal about, even if we usually show it. Quote their own words back in the setup lines where they said something usable. For each attendee, mark the one moment in the demo aimed specifically at them. List what you cut and why, so I can put a section back if I disagree.
How to adapt it
- Paste discovery notes in full; the throwaway line is often the one worth opening on.
- Fill attendees with what each person is accountable for, so nobody sits through 30 minutes aimed at someone else.
- State constraint honestly so the script does not depend on a data set you will not have.
Why it works
Reordering around the prospect's most urgent problem is what tailoring actually means, and requiring cuts forces the demo to fit the slot. Asking the AI to explain what it removed keeps you in control, and quoting the prospect's own language makes the demo feel built for them because it was.
3. Write a demo talk-track for one feature
When to useWrite one whenever a feature is being demoed inconsistently, or when a new capability ships and nobody has words for it yet.
Prompt
You are a role at company, a product description. Write a demo talk-track for feature, aimed at audience. Today they do this work like this: before state. On screen I will do these steps: clicks. The segment gets time budget. Write it in four beats. First, describe before state in one sentence so the audience recognises their own workflow. Second, narrate clicks in terms of what is happening for the user, never in terms of buttons and menus. Third, state the change in plain terms and support it with proof. Fourth, ask one question that gets audience talking about their own version of this. Mark where to pause. Do not use the words simply, just, or easy.
How to adapt it
- Make before state specific enough that someone in the room winces -- recognition is the whole hook.
- Keep proof to one number; a second one starts an argument about methodology.
- Trim time budget to four minutes or less, since talk-tracks expand to fill whatever you give them.
Why it works
The four-beat structure puts the pain before the feature and the outcome before the proof, which is the order people actually buy in. Banning button narration and the word simply strips out the two habits that make demos sound like a manual being read aloud.
4. Draft demo follow-up notes
When to useWrite it within a few hours of the demo, while you can still tell which objection was real and which was polite.
Prompt
You are a role at company, a product description. I just demoed to prospect. Here are my raw notes: raw notes. Here is what I showed and what landed: showed. Here is what I still owe them: open questions. We agreed on this next step: next step. Write a follow-up recap the prospect can forward to a colleague who was not on the call. Lead with the problems they described in their own words, not with what we showed. Then note how we addressed each one, briefly. List open questions as commitments with owners and dates. State next step plainly at the end. Keep it under word limit words. Separately, list anything in my notes that sounds like an unspoken objection I should chase.
How to adapt it
- Paste raw notes exactly as written; tidying them first strips the hesitation signals worth catching.
- Never leave open questions empty -- an unanswered question you name yourself builds more trust than a clean recap.
- Put a real date in next step, because a recap without one is a thank-you note.
Why it works
Leading with the prospect's own problems makes the recap forwardable, which matters because the person who decides usually was not on the call. Turning open questions into dated commitments creates a reason to reply, and the unspoken-objection list surfaces what politeness hid.
5. Turn a demo recording into next steps
When to useRun it right after the call, and again before your next conversation with the account, when the details have faded.
Prompt
You are a role at company, a product description. Below is the transcript of a demo with speaker labels: transcript. Deal context: deal context. Analyse the call against qualification framework. Return the answer as output format. For every finding, quote the exact line from the transcript that supports it -- if you cannot quote a line, do not make the claim. Identify buying signals we may have talked past, moments where a question was asked and not fully answered, and any point where the prospect changed tone or went quiet. Pay particular attention to risk focus. Finish with three concrete next actions ranked by what most reduces the risk of this deal stalling. Be blunt about weak spots.
How to adapt it
- Use a transcript with speaker labels; without them the AI cannot tell your claims from theirs.
- Set risk focus to whatever kills your deals most often, so the analysis serves your pipeline and not a template.
- Requiring a quote per finding is the load-bearing instruction -- drop it and you get plausible fiction.
Why it works
Presenting and listening compete for attention, so the signals you miss are the ones that matter. Forcing every finding to carry a verbatim quote makes the analysis auditable, and ranking actions by stall risk turns a call review into something that changes what you do next.
6. Prepare answers to likely demo objections
When to useDo it the morning of any demo that matters, especially when a competitor is in the deal or you know a gap will come up.
Prompt
You are a role at company, a product description. I am demoing to prospect. We are up against competitor. Our real weaknesses are known gaps. I expect this pushback: objections. I can cite proof points. Prepare the count objections most likely to come up, including any I did not list that follow from known gaps or competitor. For each one, write what the buyer is actually worried about underneath the question, a spoken answer of no more than four sentences, and the proof points to reach for. Where known gaps make us genuinely weaker, write an honest answer that concedes the point and reframes -- do not spin. Rank them by how likely they are to end the deal.
How to adapt it
- Be truthful in known gaps; a prompt fed marketing copy prepares you for a demo that will not happen.
- Write objections in buyer language, since that is how they will actually arrive.
- Ask for the worry underneath each question -- the stated objection is rarely the real one.
Why it works
It rehearses the objections you would rather avoid by deriving them from your real gaps and the competitor's strongest claim. Naming the worry beneath the question produces answers that address the concern rather than the wording, and ranking by deal risk tells you which two to actually memorise.
For small sales and support teams
Capture every lead and follow up on time.
The CRMsoftware.pro AI agent qualifies website visitors 24/7 and sends each inquiry to your leads inbox. Turn a lead into a deal in one click and track every follow-up as a task.
- Leads inbox and 1 pipeline on the free plan
- Tasks with an assignee and a deadline for each follow-up
- WhatsApp, Telegram and human handover from Launch, $19 a month billed yearly
Free plan: 3 users, no credit card.
How to use
How to use this template
- 1
Pick the closest variant. Choose by the situation, not only by the channel.
- 2
Replace every placeholder in brackets. If you cannot fill one, ask the customer one short question first.
- 3
Save the final wording where your team works: your CRM, your help desk, or saved replies and the knowledge base in CRMsoftware.pro.
- 4
Review the results every week. Drop the variants that confuse people and improve the ones that work.
FAQ
Frequently asked questions
Can I use these templates commercially?
Yes. Copy, edit, and use them in your business, client work, CRM, help desk, or CRMsoftware.pro workspace.
What is a product demo AI prompt template?
It is a reusable instruction for an AI assistant that turns demo work into a first draft -- a persona script, a tailored running order, a talk-track, a follow-up recap, or an objection prep sheet. You supply the bracketed details from your own product and pipeline, and the AI produces something you edit rather than write from scratch.
How do I stop the AI writing a feature tour?
Cap what it can show. Name three or four capabilities and tell it explicitly not to include anything else, then require every section to connect back to a pain the persona is measured on. Feature tours appear when the prompt asks for a walkthrough of the product instead of a demo aimed at one buyer's problem.
Can I use a demo transcript with an AI assistant?
Yes, and a transcript with speaker labels is the single most useful input you can give one -- it surfaces the signals you missed while presenting. Follow your own policy and any recording consent rules for sharing call data with third-party tools, and require the AI to quote the transcript for every claim so nothing gets invented.
How long should an AI-drafted demo script be?
Set the slot length in the prompt and ask for timed sections, because scripts expand to fill whatever space you give them. A 25 or 30 minute demo usually supports three capabilities plus a closing ask. If the draft comes back with four, cut one -- the fourth almost always steals the time the ask needs.
Put this template to work in CRMsoftware.pro
Start free with 3 users and an AI agent that answers on your website 24/7. Paid plans start at $19 a month, billed yearly.