Is the Demo the New Deck?

For years, we've told people in our presentation workshops: show, don't tell. Now AI is taking that advice to the max. A growing number of teams are walking into leadership meetings and, instead of "here's our proposal," it's "here's what we built, let me show you."

Andrew Bosworth, Meta's CTO, put it well in an April 2026 Wall Street Journal interview:

"Lately I often feel like I'm working at two different companies depending on who I'm talking to." Some teams still work the way most did in 2025, large groups, formal documents, careful reviews. A small but growing number work almost entirely differently: tiny, fast-moving, communicating through working demos instead of documents."

That's the shift we're seeing too, though it doesn't mean the deck is dead. A deck still frames a decision and lays out options before a room commits to anything. But a working prototype earns trust a deck can't: no mockup pretending to be real, no roadmap promising what's coming. You hand someone the thing and say try it.

That doesn't mean presentation skills matter less, if anything, a demo asks more of you. A deck is predictable. A live demo isn't: wifi drops, a button misbehaves, all in front of the exact audience you wanted to impress. Framing, connection, and composure stop being optional.

So, is the demo the new deck? Probably not entirely, but it's earned a seat at the table, and it's likely to earn a bigger one. Why look at financial numbers on a slide when you could pull up the live dashboard instead? The sooner you start thinking this way, the better positioned you'll be.

Here's how to make sure your demo builds trust instead of just showing off code:

Step 1: Open with the quick story, not the screen

Don't lead with the product. If the room doesn't know why this matters yet, they'll spend the whole demo confused instead of watching. Set the stage, just do it fast: one sentence on the problem, one example of who feels it. Then move. "So we built something to test that. Let's look."

Step 2: When you do open the screen, show the result first

Resist the urge to build the demo chronologically. Peter Cohan calls this "doing the last thing first" in Great Demo: skip the login screens and setup, open with your most compelling result. Show the strongest version of your solution in under two minutes. You want the room thinking, "wait, how did they do that?" Then rewind and walk through how you got there, quickly and confidently. If they want more detail, they'll ask for it. Curiosity is a better hook than completeness.

Once you're in the demo, here are some tips to carry you through the rest of it:

Consider a co-pilot

As the stakes or the audience size go up, it's worth splitting the job: one person narrates, one drives the demo. It lets each person focus on doing one thing well instead of juggling both, and it gives you a natural way to build in back-and-forth, one person can ask the other a question mid-demo the way an audience member might, which tends to feel more like a conversation than a performance.

A slide still has its place

The best demos sometimes include a slide or two, not to replace the demo, but to clarify it. An architecture diagram, a simplified workflow showing where the bottleneck was, these are things a live screen often can't show as clearly. If you can, run two screens: one for the live product, one for the occasional slide. Just keep the hierarchy straight. The demo is the main event. The slide is there for clarity, not to share the spotlight.

Pause for questions along the way

If you have your audience save their questions until the end, then you've asked people to hold ten minutes of thoughts in their head, most of which they'll let go.

Build in natural checkpoints instead. After the core function, pause and ask, "What's your first reaction to that?"

Pausing for questions is also a break for you. Demoing live takes real focus, all at once: clicking the right things, narrating clearly, watching the room. A pause gives you a second to breathe and reset before the next section.

When it breaks, stay steady

It will happen eventually. Wifi drops, a field doesn't load, the exact bug you fixed yesterday reappears. How you handle those thirty seconds matters more than almost anything else in the meeting, because it's the one moment people aren't watching your product, they're watching you.

If you're presenting solo, that's its own kind of credibility, but it also means there's no one to hand off to when something glitches. Stay ready for it. Even Elon Musk wasn't immune, the Cybertruck's "unbreakable" window famously cracked live on stage during the 2019 unveiling. Stuff happens. A little humor goes a long way toward keeping the room with you instead of watching you sweat. People forgive a glitch, but they remember how you handled it.

Plan your closing

A deck gives you a built-in ending: a closing slide, "we're done, here's the call to action." A demo doesn't hand you that, so build one in on purpose.

Open with the problem, then close by returning to it. Tying the last thing you say back makes a demo feel like a complete story instead of a walkthrough.

For example, when OpenAI demoed GPT-4o's voice mode live in 2024, letting it hold a real-time conversation and read tone of voice, that moment did more to convince people AI had crossed a threshold than any keynote slide could. People weren't reading a roadmap, they were watching something happen and reacting to it live. A demo can move someone from "I get it in theory" to "I just saw it work" faster than anything else you can put in front of them.

The takeaway

Whether it's a deck or a demo, the fundamentals don't change: frame the problem before you make your ask, stay connected to the room, know how to recover when something goes wrong. What's changed is that those skills now have to work live, with no slide to fall back on if something breaks.

Show, don't tell, was always good advice. The demo just makes it literal.