Discovery That Sets Up the Demo: What You Must Know Before You Present

Includes: The pre-demo discovery summary: know this before you present checklist
The short answer

A demo only works if your discovery made it possible. Before you present, you should know the buyer's real problem and the outcomes they care about, which stakeholders are watching, the decision process and timeline, and the landmines like an incumbent or a fixed budget. Discovery that sets up the demo means you demo around their outcomes — not your feature list.

A demo doesn't sell your product — it proves your discovery was right. The difference between a feature tour and a demo that lands is entirely what you learned before you presented. If you've done the work in this module — the real pain, the budget, the committee, the process — then the demo becomes a tight, tailored proof of exactly what the buyer needs. Skip the discovery, and you're showing slides to a stranger.

Why discovery must set up the demo

The buyer doesn't care how many features you have; they care whether you solve their problem. The champion in the room is watching for proof their internal push was right. The evaluator is checking you against their criteria. The decision-maker is watching for risk. Discovery gives you each person's lens so the demo speaks to all three at once.

The pre-demo summary (checklist)

Before you present, be able to answer these — ideally in one written page you share with your champion:

  • The problem and the outcomes. What are we fixing, and what would "better" look like to them in their numbers?
  • Who's in the room. Every stakeholder, and the one outcome each is there to see.
  • The process and constraints. Where this sits in their decision process, the timeline, and any budget or compliance boundaries you can't cross.
  • The landmines. The incumbent they're comparing you to, the objections that will come up, and the gap you need to prove.

Demo around outcomes, not features

With that summary, the demo practically writes itself. Open by restating their problem and the outcomes you'll prove. Walk the product only as it maps to those outcomes. For every feature you'd love to show, ask "does this prove a value they named?" — if not, leave it out. End by tying what they saw back to their timeline and the next step in their process, so the demo moves the deal instead of ending it.

Start here

That closes this module's work — you've gone from a qualified meeting to a demo-ready diagnosis of a real deal. The next module turns that diagnosis into the sellable deal, starting with how to run a sales demo that proves outcomes. Everything you learned in discovery is the raw material the rest of the deal is built from.

Practice this

Pass this challenge (score 3+ of 4) to mark the lesson complete in your progress.