Sales Demo Script Examples You Can Adapt in an Afternoon

• 0:00 -- Name the problem back to them. "You said month-end close takes four days and most of it is chasing approvals." One sentence, using their words. No agenda slide.
• 0:30 -- Show the end state first. The finished, approved, closed month. Start at the outcome so everything after has a destination.
• 2:00 -- Walk the path to it. Three steps maximum. Narrate decisions, not clicks -- "I approve this one and reject that one", never "now I click the green button".
• 8:00 -- Break something on purpose. Show a rejection, a missing field, an error. Credibility comes from the unhappy path.
• 10:00 -- Stop and ask. "Where does this differ from how you do it now?" The answer is your next demo, and often the real objection.

Use this when you genuinely do not know their situation yet. The first eight minutes are questions, and the demo is assembled live from the answers -- which only works if you have a library of short flows to pull from.

The structural rule is that you do not open the product until you can name the specific outcome you are about to show. If you cannot, keep asking. A demo that begins before that point becomes a tour by default.

• 0:00 -- Three questions. What does this process look like today, what does it cost you, what have you already tried.
• 8:00 -- Say what you are about to show and why. "Based on that, the part worth seeing is X."
• 9:00 -- One flow, completely. Resist adding a second.
• 16:00 -- Their data, or the closest thing to it. Even a renamed record moves this from generic to plausible.
• 18:00 -- Agree the next step out loud. Not "I will send something over".

This is the self-serve version, for a homepage or an email. There is no discovery and no adaptation, so it has to pick the single most common problem and address only that.

Written as captions rather than narration, because most viewers have sound off. Each caption is one short line, in the imperative, describing what is happening -- not what the feature is called.

• Step 1. The problem visible on screen. A cluttered inbox, an overdue list, a blank report.
• Steps 2-4. The three actions that fix it. One caption each.
• Step 5. The result, with a number on it if you have one.
• End. One next step. A trial link, not "learn more".

• "Stop me when this stops matching how you work." Converts a monologue into a conversation and surfaces objections early.
• "That is the whole flow." Signals completeness. Buyers routinely assume there is more and worse to come.
• "This part is genuinely manual today." Volunteering a limitation buys more credibility than it costs, and it will come out anyway.

Cut the company history, the logo slide, the org chart, and the sentence beginning "as you can see". Cut any feature nobody asked about. Cut the settings page unless configuration is the objection.

A useful test: read the script and mark every line that would still matter if the buyer had five minutes total. What is left is usually the real demo, and it is usually about a third of what was written.

• How to Run a Sales Demo That Closes (Checklist + Structure)
• Your Sales Demo Is Too Long: How to Cut It Down
• How to Give a Product Demonstration That Does Not Drift
• How to Write Demo Captions That People Actually Read