Demo Plan Template: How to Plan a Software Demo That Wins the Technical Win
November 11, 2026 · Casey O'Brien
A demo plan is a one-page document a presales engineer writes before a software demo. It names the audience, the buyer’s pains in their own words, the story the demo will tell, the three to five moments that prove the product solves those pains, and the decision the demo should move forward.
Teams that plan demos this way avoid the most common failure in presales: the harbor tour, where the engineer shows every feature in menu order and the buyer remembers none of them.
Why plan a demo at all
Every unplanned demo drifts toward the same shape: login screen, navigation, settings, then features in the order they appear. It feels thorough to the presenter. To the buyer it is a tour of someone else’s product.
A plan forces three decisions before the call:
- Which problems this demo solves. Taken from discovery, in the buyer’s words.
- Which moments prove it. Three to five, each tied to one pain.
- What happens next. A demo that does not move the deal to a defined next step is a presentation.
The demo plan template
Copy these eight sections into a doc for every demo.
1. Deal and audience
- Account, opportunity, stage and date
- Who will attend, their role, and what each person cares about most
- Who is the technical decision-maker, and who could block
2. What we heard in discovery
- The top three pains, quoted as the buyer said them
- The number attached to each, if the buyer gave one
- Their current tools and workarounds
3. The story
- One sentence: “Today, [persona] at [company] has to [painful workflow]. After this demo, they will see how they can [outcome].”
- The persona the story follows, with a realistic name and role
4. Proof moments (three to five) For each moment: the pain it answers, what you will show, and the one sentence you want the buyer to repeat to their boss.
5. What we will not show Features this audience does not need. Writing them down is what stops the tour.
6. Data and environment
- Demo data that matches the buyer’s world: their industry, their terms, believable numbers
- Integrations to have connected, and a backup if one fails
7. Questions to ask during the demo Two or three checks such as “Is that how your team would handle it?” that turn the demo into a conversation.
8. The ask and next step
- The decision this demo should produce: a POC, a second demo for a wider team, a security review
- Who owns the next step on each side, and by when
A worked example
Here is a condensed plan for a fictional buyer.
| Section | Example |
|---|---|
| Deal | Northwind Logistics, expansion opportunity, technical evaluation stage |
| Audience | VP of Operations (economic), integration lead (technical decision-maker), two analysts |
| Pain 1 | “We rebuild the weekly carrier report by hand every Monday.” About 6 hours a week |
| Pain 2 | “Exceptions sit in email until a customer complains.” |
| Pain 3 | “Our TMS and our warehouse system don’t agree on inventory.” |
| Story | Today, Priya, an operations analyst, spends Monday morning rebuilding the carrier report. After this demo, the report builds itself and exceptions reach her before the customer notices. |
| Proof moment 1 | The carrier report generated from live data. Line: “Monday morning is back.” |
| Proof moment 2 | An exception alert routed to the right owner. Line: “We hear about it first.” |
| Proof moment 3 | TMS and warehouse sync with a conflict flagged. Line: “One number for inventory.” |
| Will not show | Admin settings, billing, the mobile app |
| Ask | A two-week POC against three written success criteria, kicked off by the integration lead |
Use tell-show-tell for every proof moment
Each proof moment follows the same three beats:
- Tell. Restate the pain in the buyer’s words and say what you are about to show.
- Show. Demonstrate only that workflow, using their kind of data.
- Tell. Say what they just saw and what it means for them, then ask if it matches how they work.
The structure keeps the buyer oriented and gives them the sentence to repeat internally. It also gives you a natural place to stop and ask a question before moving on.
Open with a short recap of discovery
Spend the first two or three minutes playing back what you heard in discovery: their pains, their numbers and what they said success looks like. Ask whether anything has changed. Then show the first proof moment.
The recap does three things. It proves you listened, it lets the buyer correct you before you build on a wrong assumption, and it frames everything that follows as an answer to their problem.
Common demo planning mistakes
- Planning from the product instead of the buyer. If the plan’s headings are module names, it is a tour.
- Generic demo data. “Acme Corp” and round numbers tell the buyer this demo was not built for them.
- Too many proof moments. Past five, the buyer stops remembering any of them.
- No defined ask. Ending with “any questions?” hands control of the next step to the buyer.
- Planning in a personal doc. If the AE and the manager cannot see the plan, they cannot help shape it or reuse it.
Connect the demo plan to the POC
The demo plan’s proof moments are the first draft of the POC’s success criteria. If the buyer agrees the demo showed the outcome, the POC proves it in their environment, against criteria they sign. The free POC success criteria template has 70 criteria to start from, and the mutual action plan template lays out the steps from demo to decision.
Where PresalesIQ fits
PresalesIQ is purpose-built presales management software with demo planning built in. Each demo plan captures the objective, the audience and the value hypothesis, and AI drafts the must-show scenarios from the deal’s discovery for your team to review. The plan stays attached to the opportunity from Salesforce or HubSpot, so the AE and the manager see it before the call. You can share demo plans and POCs with the buyer in the Technical Deal Room, where they agree to success criteria and sign off each stage on the record.
See a demo plan built from real discovery.
Frequently asked questions
What should a demo plan include? The audience and their priorities, the top pains from discovery in the buyer’s words, the story the demo will tell, three to five proof moments, what you will not show, the demo data and environment, questions to ask and the next step you want.
How long should a demo plan be? One page. If it runs longer, the demo is trying to cover too much.
What is a harbor tour demo? A demo that walks through product features in menu order instead of solving the buyer’s specific problems. It feels complete to the presenter and is forgettable for the buyer.
What is the tell-show-tell demo method? A structure for each demo moment: tell the buyer what you are about to show and why it matters to them, show only that workflow, then tell them what they saw and what it means for their team.
Who should write the demo plan? The presales engineer running the demo, with input from the AE on the audience and the deal. The manager should be able to see and review it before the call.
How is a demo plan different from a demo script? A script is the words and clicks. A plan is the strategy: which problems, which proof, for which audience, leading to which decision. Write the plan first and the script follows from it.
Keep reading
- Product Gap Tracking: How Presales Ties Feature Requests to RevenueHow presales teams track product gaps so they reach product with revenue attached: what to capture, how to size revenue at risk and how to report it.
- Why presales management still relies on manual loggingPresales teams still log their work by hand because CRMs weren't built for them. What that lag costs, and how AI-native capture removes it.
- Build vs Buy in 2026: Why Presales Teams Keep Building Their Own Tools32% of companies skipped a software purchase to build it with AI. Four presales leaders told me they did exactly that. Here is where each build stopped.