Running a client demo
Tell a story the client cares about, and stay cool when something breaks live.
Case study: The demo that started with the login page
Pooja's team in Pune had built a slick claims app for a Chicago insurer. Her demo started with the login page, then the settings screen, then the database schema. Ten minutes in, the client's VP asked, "So what does an adjuster actually do with this?" Then the upload button threw an error, and Pooja froze for a long, silent minute. For the second demo she opened with, "Meet Dana, an adjuster with forty claims a day," showed Dana closing a claim in two minutes, and when a page loaded slowly, she said, "That's the test server. Let me show you the recording while it loads."
Takeaway: Demo the user's story, not your features. When something breaks, name it, stay calm and move on.
We sometimes show every feature to prove hard work, and treat a live bug as a disaster. Global clients want to see their problem solved, and they respect a calm, honest recovery.
Running the demo
Goal: Show how the product solves the client's real problem, handle surprises calmly, and leave with clear feedback and next steps.
Step by step
- Set the scene. Recap the problem and what they'll see in the next twenty minutes.
- Tell a user story. Walk through one real user's day, not a feature list.
- Handle bugs calmly. Name it, have a backup, keep going.
- Invite feedback. Ask specific questions, not 'any doubts?'.
- Agree next steps. Who does what by when.
Say this, not that
| Today I'll show you how an adjuster closes a claim in two minutes instead of fifteen. | First I will show the login page. | Open with the outcome they care about. |
| Let's follow Dana, an adjuster handling forty claims a day. | ||
| Looks like the test server is slow. Let me show you the recording while it catches up. | Sorry, sorry, it was working yesterday. | Calm recovery builds more trust than a perfect demo. |
| What would your adjusters find confusing here? | Any doubts? | Specific questions get honest, useful feedback. |
| So next steps: we fix the upload issue by Tuesday and you share it with two adjusters. |
Model conversation
- You
- Thanks for joining, Jennifer. Today I'll show you how an adjuster closes a claim in two minutes instead of fifteen.
- Jennifer
- That's the number I care about. Go ahead.
- You
- Let's follow Dana. She opens her queue and sees the most urgent claims first.
- Jennifer
- Nice. Can she upload photos from the site?
- You
- Yes, let me show you. Ah, that upload's failing on the test server. I'll log it, and here's a thirty second recording from this morning instead.
- Jennifer
- Okay, that looks smooth. I'd want it working before we pilot, though.
- You
- Absolutely. What would your adjusters find confusing on this screen?
- Jennifer
- Probably the status labels. Let me get two adjusters to try it next week.
Giving demo feedback
Goal: Give honest, specific feedback that helps the team build the right thing, without demotivating them.
Step by step
- Start with what works. Be specific about what you liked.
- Name the gaps. Say what's missing or wrong, tied to your users.
- Prioritize. Separate must-fix from nice-to-have.
- Agree next steps. When will you see the changes?
Say this, not that
| The search is really fast. My team will love that. | Good, good, nice work. | Specific praise tells them what to keep. |
| My concern is that the approval flow has too many clicks for our managers. | ||
| That isn't what we need yet, but here's the problem behind it. | This is all wrong. | Explaining the problem helps them fix it. Judging just hurts. |
| The must-fix is the approval flow. The colors are nice-to-have. | Priorities stop teams from fixing the wrong things. | |
| When could we see the updated version? |
Model conversation
- Meera
- That's the end of the demo. We'd love your honest feedback.
- You
- Thanks, Meera. First, the search is really fast. My team will love that.
- Meera
- Great to hear. What else?
- You
- My main concern is approvals. Our managers approve fifty requests a day, and this takes six clicks each.
- Meera
- That's useful. We assumed approvals were occasional.
- You
- That's the must-fix for us. The color changes we mentioned are nice-to-have, so don't worry about those yet.
- Meera
- Got it. We could add bulk approval in the next sprint.
- You
- Perfect. When could we see the updated version?
Practice it out loud
Reading is half of it. Fluent listens to you say it and scores your clarity, free, in your browser.