Sales Demo Checklist: Before, During and After the Demo, Plus a Scorecard
A sales demo checklist is a short list of things a rep must do before, during and after a B2B product demo so the demo answers the buyer's actual problem and ends with a committed next step. Before: confirm discovery, attendees and agenda. During: show the two or three workflows that matter to this buyer, check in often and handle questions directly. After: send a recap tied to what the buyer said, within a day, with the next meeting already booked.
This page is the checklist itself, written for sales leaders and SaaS and B2B sales teams. Use it to prepare demos, to review recorded ones, or to coach reps. At the bottom is the scorecard a mystery shopper uses when they sit through your demo as a realistic buyer, so you can see how demo best practices look from the buyer's side.
Before the demo checklist
Most demos are won or lost before they start. If discovery was thin, the demo turns into a feature tour.
Discovery and qualification
- Discovery call completed, or at least the core questions answered: problem, impact, decision process, budget, timeline.
- The buyer's top two or three problems written down in their own words.
- Success criteria known: what the buyer needs to see to move forward.
- Competitors or alternatives in the deal identified, including "do nothing."
- If discovery is missing, the first ten minutes of the demo are set aside to do it. See our list of sales discovery questions.
People and logistics
- Attendee list confirmed, with each person's role and what they care about.
- Decision maker or budget owner invited, or a plan to brief them.
- Calendar invite includes the agenda, the meeting link and a dial-in.
- Confirmation sent 24 hours before, with a one-line reminder of the goal.
- Sales engineer or specialist briefed on the buyer, if one is joining.
Demo environment
- Demo environment loaded with data that looks like the buyer's industry, not "Test Company 1."
- The two or three workflows the buyer cares about rehearsed end to end.
- Notifications off, unrelated tabs closed, screen-share tested.
- Backup plan ready (recorded clip or screenshots) in case the environment fails.
- Pricing approach decided: what you will say if asked, and who can say it.
During the demo checklist
Open (first five minutes)
- Introductions, with a quick round of what each attendee wants from the session.
- Recap of what you heard in discovery, and a check: "Is that still accurate? Anything changed?"
- Agenda and time confirmed, including time reserved at the end for questions and next steps.
Show (the middle)
- Lead with the buyer's biggest problem, not the login screen or company history.
- Tie each workflow back to something the buyer said ("you mentioned approvals take three days, here is how that works").
- Show outcomes, not menus. Fewer screens, more "here is the result."
- Pause and check in every few minutes: "How does that compare with how you do it today?"
- Answer questions directly. If you do not know, say so and commit to a date for the answer.
- Skip features the buyer does not need, even good ones.
- Keep the rep's talk time in check. A demo is still a conversation.
Close (last ten minutes)
- Ask what resonated and what did not.
- Ask about concerns or gaps directly: "What would stop you from moving forward?"
- Confirm the decision process and timeline again, now that more people have seen the product.
- Book the next step on the calendar before the call ends, with attendees and purpose agreed.
- If pricing is raised, give a clear answer or a clear date when it will be provided.
After the demo checklist
- Recap email sent the same day or next business day.
- Recap lists the buyer's problems, what was shown for each, open questions and the agreed next step.
- Any promised material (security docs, case studies, pricing) sent by the date promised.
- Answers to open questions delivered, not left for the buyer to chase.
- CRM updated with attendees, concerns, decision process and next step.
- Internal debrief if a sales engineer or manager joined: what to fix for the next session.
- Follow-up cadence set if the buyer goes quiet. Our guide to following up on sales leads covers timing.
The single best predictor of a good demo, from the buyer seat, is whether the rep remembers what the buyer said in discovery and builds the demo around it.
SaaS demo best practices that buyers actually notice
When an evaluator sits through a SaaS demo as a buyer, the things that stand out are rarely the product. They are the habits around it.
- Starting on time, with the right people. Late starts and "let me just get my screen working" set a tone.
- Not repeating discovery. If the buyer already explained their process to an SDR, they should not have to explain it again from scratch.
- Realistic data. A demo built on the buyer's type of business is easier to picture.
- Straight answers on integrations, security and pricing. Dodging these questions reads as a red flag.
- A clear ending. The buyer should leave knowing what happens next and when.
For more on SaaS sales specifically, see SaaS sales mystery shopping.
Sales demo scorecard: how a mystery shopper scores it
In a sales demo evaluation, a trained evaluator poses as a realistic buyer, requests a demo through your normal channels and scores the experience against criteria agreed with you before the shop. The scorecard below is a version you can copy. Score each criterion 1 to 5 and add notes with specific examples.
| Criterion | What good looks like | 1 | 3 | 5 |
|---|---|---|---|---|
| Scheduling and confirmation | Demo booked quickly, invite has agenda, confirmation sent | Slow or confused booking, no agenda | Booked, basic invite | Fast booking, agenda, reminder, right attendees |
| Preparation | Rep knows the buyer's company, role and problem | Asks what the company does | Knows basics | References specifics from discovery |
| Opening and agenda | Recaps discovery, confirms goals and time | Jumps straight into slides | States agenda | Recaps, checks for changes, agrees agenda |
| Relevance | Shows the workflows tied to the buyer's problems | Generic feature tour | Some tailoring | Every section tied to a stated need |
| Engagement | Regular check-ins, buyer talks a meaningful share | Monologue | Occasional questions | Two-way conversation throughout |
| Handling questions | Direct answers, honest about gaps | Dodges or bluffs | Answers most | Clear answers, follows up on unknowns by a date |
| Pricing | Clear answer or clear plan when asked | Refuses or deflects repeatedly | Vague range | Clear range or committed date for a quote |
| Decision process | Confirms who decides and how | Not addressed | Asked briefly | Mapped and next steps planned around it |
| Next step | Meeting booked before the call ends | "I'll send some info" | Next step suggested | Booked with purpose and attendees |
| Follow-up | Recap within a day, promises kept | No recap or very late | Generic recap | Specific recap, materials sent on time |
Example only: a demo that scores 5 on relevance and 1 on next step still leaves the deal at risk. Read the scorecard as a pattern. For a deeper explanation of each criterion, see what a mystery shopper scores on a sales demo.
Virtual demo checklist additions
Most B2B demos now happen over video. A few extra checks prevent the problems buyers mention most on remote demos.
- Join early and test audio, camera and screen-share in the actual meeting tool the buyer is using.
- Share a single window, not the whole desktop, so private messages and other customers' data stay hidden.
- Increase font and zoom so the screen is readable on a laptop, not only on a large monitor.
- Use names when checking in. "Does that match how your team handles approvals?" gets more response on video than "any questions?"
- Watch for quiet attendees. If someone has said nothing for ten minutes, ask them directly what they want to see.
- If recording, ask permission at the start and follow the consent rules where each attendee is located.
Demo mistakes the checklist is designed to catch
Each line on the checklist exists because of a mistake that shows up repeatedly when an evaluator sits through demos as a buyer.
Starting with the company story
Ten minutes on founding history, office locations and customer logos before the buyer sees anything relevant. Buyers can read that on the website. The fix is to open with the recap of discovery and go straight to the first problem.
Showing everything
Reps who know the product well often want to show all of it. The buyer leaves overwhelmed and cannot remember the part that mattered. Two or three workflows, done well, beat twelve done quickly.
Treating pricing as off limits
When a buyer asks about price and the rep answers "it depends, let's talk about that later" three times, the buyer starts to wonder what is being hidden. A clear range, or a firm date for a quote, keeps trust intact.
No next step
The demo ends with "thanks for your time, I'll follow up." Without a booked meeting, the deal now depends on the buyer replying to an email, and many do not.
How to use this sales demo checklist with your team
- Share the before-demo list as a required step for every scheduled demo. Put the key fields (problems, attendees, decision process) in the CRM.
- Have managers score a sample of recorded demos each month using the scorecard, and compare scores across reps.
- Pick the two lowest-scoring criteria across the team and coach on those, not on everything.
- Check the buyer's view. Recorded demos are the ones reps knew were being recorded. A mystery shop shows what a new buyer actually experiences, from the demo request form to the last follow-up email, and a re-shop after coaching shows whether it changed.