Demos that win
A demo is not a feature tour. It is a story about the customer's problem, told with working software, that ends in a decision. FDEs run many kinds of demos — discovery demos, POC readouts, executive reviews — and the same principles apply to all of them.
Know which demo you're giving
| Demo | Audience | Goal |
|---|---|---|
| Discovery demo | Users and process owners | Spark ideas, learn what resonates |
| POC readout | Sponsor and technical leads | Show the approach works against the agreed criteria |
| Pilot / executive review | Executives and budget holders | Show business value and secure the next decision |
Structure: problem, before, after, impact, next step
- The problem — in their words, from discovery. "Today, finding the right policy clause takes agents about six minutes."
- Before — briefly show the current workflow, or describe it vividly.
- After — the same task in your solution, on their data.
- Impact — the measured result against the baseline, with the quality metric.
- Next step — the specific decision you need, and when.
Keep the live portion short. Executives remember one moment and one number.
Use their data
Nothing persuades like seeing a customer's own document, ticket or record handled correctly. Generic sample data invites "but our data is different." Prepare carefully: pick representative examples (not only the best ones), and get permission to show any sensitive data to the audience in the room.
Include one honest edge case — something the system handles imperfectly — and explain how it is managed. It makes everything else you show more credible.
Rehearse and de-risk
- Run the full demo end to end the day before, on the same network and accounts you'll use.
- Have a recorded backup of the key flow in case of a network or service outage.
- For LLM features, use stable settings and inputs you have tested repeatedly; outputs vary between runs.
- Close everything else on your screen. Turn off notifications.
When something goes wrong live
Stay calm and narrate: "This is a good example of why we have a fallback — let me show you the recorded run while I check this." Then follow up in writing with the fix. Handling a failure gracefully often builds more trust than a flawless demo.
After the demo
Send a short written follow-up the same day: what you showed, the results, questions raised, and the agreed next step with owners and dates. The decision is made in that email more often than in the room.
Ask the champion to present part of the demo — ideally the "before" story. Hearing the problem from a colleague lands far better than hearing it from a vendor.
Some FDE loops include a presentation or mock customer demo. Use the five-part structure, keep the live part tight, and leave time for questions — how you handle pushback is part of the assessment.
Senior Full-Stack Engineer · AI & AWS. I turn ambiguous customer problems into production systems — cloud, data and AI.