Demo What Matters
Demo what matters.
A demo is not a product tour. First understand the visitor, then show the workflow that answers their need.
DISCOVER → DEMO OR DISCUSS
Start with the Visitor
Use the conversation to decide what to show.
- Understand who they are.
- Understand their use case or problem.
- Choose the relevant workflow.
- Show the value.
- Ask if it answers their question.
- Continue deeper only where useful.
Example
“You mentioned migration from Exchange. Let me show the part that matters for that.”
Do Not Describe the Demo
Trap
The Empty Demo
A weak demo sounds like this:
- “Normally there would be some messages here.”
- “Imagine we had some files.”
- “This would show a recording.”
- “Normally this dashboard would contain data.”
Rule
Don’t describe the demo. Prepare the demo.
The environment should look credible the moment the visitor sees the screen.
Show Only What Works
Rule
Use a working demo path.
If a workflow is not ready, unstable, or unclear, do not make it the main demo. Show the prepared environment and only add extra items when they can support a clear use case.
Make the Environment Feel Alive
Mission
Prepare a credible demo environment
A technically working tenant is not enough. The environment should feel active, realistic, and ready before the booth opens.
Prepare these areas before the event:
- Email populated
- Calendar filled
- Contacts ready
- TeamChat active
- Files available
- Conference ready
- Recording available where useful
- Notes populated
- Dashboard usable
Prepare Email for the Screen
Email should look real, not empty.
Prepare:
- realistic conversations;
- enough inbox content;
- at least one visually rich email;
- useful images where appropriate;
- examples linked to expected discussions.
Pro Tip
Keep one visually strong email ready to open. A screen full of plain text is harder to read from a booth distance.
Prepare Calendar and Contacts
The calendar should support the story you want to show.
Prepare:
- realistic meetings;
- events;
- useful calendar content.
Contacts should also look credible.
Prepare:
- people;
- organisations;
- contact information.
Prepare TeamChat
TeamChat should explain collaboration quickly.
Prepare:
- active rooms;
- realistic conversations;
- shared files;
- content that makes the use case clear.
Do not rely on live improvisation to make the room interesting.
Prepare Files and Documents
Rule
Do not leave empty folders.
Prepare documents that:
- look realistic;
- can be opened;
- support the demo story.
Useful files may include:
- presentations;
- Word documents;
- Excel documents;
- PDFs;
- comparisons;
- case studies;
- battlecards.
Use only what fits the conversation.
Prepare Conferences and Recordings
Have a conference or room ready to show.
Where relevant, prepare a recording before the booth opens. Do not rely on creating everything live while a visitor is waiting.
Prepare Notes and Dashboard
Populate Notes and Dashboard enough that they can be shown naturally.
The visitor should see useful content immediately, not an empty feature waiting for explanation.
Prepare Event-Relevant Examples
Some topics depend on the event and expected visitors.
Prepare examples where relevant for:
- tracking;
- signatures;
- security;
- MFA or 2FA;
- mobile access;
- collaboration;
- deployment scenarios;
- migration;
- competitive positioning.
Remember
Prepare examples because you expect the question, not because every feature must appear in every demo.
Set Up All Agreed Demo Stations
Where the booth uses several demo stations, prepare them before opening.
All agreed stations should be:
- powered on;
- logged in where needed;
- connected;
- visually clean;
- ready to use without setup;
- opened to the expected applications or pages.
The visitor should never wait while you build the demo environment.
Use the Stations With Purpose
| Station | Main use | Must be ready for |
|---|---|---|
| Station 1 | Primary guided demo | Main prepared environment |
| Station 2 | Parallel demo | Second conversation or overflow |
| Station 3 | Visitor or flexible use | Self-exploration, activity, or extra overflow |
This model is useful when the booth has three stations. If the booth has fewer, keep the same principle: every available station must have a clear purpose.
Station 1 — Primary Demo
Use the primary station for the main guided demonstration.
It should have:
- the prepared demo environment;
- a clean starting state;
- expected applications or pages ready.
This is the station you use when a visitor has a clear need and you want to guide the conversation.
Station 2 — Parallel Demo
Use the second station when another team member needs to show something at the same time.
It should be ready for:
- a second conversation;
- a handover from Sales;
- a short parallel demo;
- overflow during busy periods.
It should not require setup before use.
Station 3 — Visitor or Flexible Station
Use the third station where appropriate for:
- visitor self-exploration;
- another parallel demonstration;
- an event challenge or activity;
- overflow.
Do not assume the third station is always free for self-exploration. Use it according to the event setup.
Reset After Every Demo
Rule
Reset the station before the next visitor.
After a demo:
- close sensitive or confusing conversation states;
- return to a clean starting screen;
- reopen the prepared demo view;
- make the station look ready again.
Do not make the next visitor inherit the previous visitor’s conversation.
Use the Booth Equipment
Use the proper booth display for guided demos when it is available.
A small personal laptop makes the demo harder to see and weaker for groups. Keep the main demo on the prepared booth station unless the event setup requires another approach.
Rush Mode
Keep the Demo Moving
When the booth gets busy, shorten the demo and protect the flow.
QUALIFY → CHOOSE / ROUTE → DEMO OR DISCUSS → RESET
Use the second and third stations to support parallel conversations. Keep every station ready so the team can react quickly.
Quality still matters. Rush Mode means shorter, not careless.