The Demo That Answers a Question Nobody Asked

There is a particular experience of standing next to someone who has just bought a new phone.

They are not showing you the phone. They are showing you a settings menu. Three levels deep, there is a toggle that does something they find delightful, and they have been waiting all day to show somebody, and you are the somebody.

You didn't ask. You were never going to ask. And yet you're now four minutes into a tour of a thing you will never touch.

They're not being rude. They're just deep inside something you're standing outside of, and from in there, every part is interesting.

Solution slides do this constantly.

You've just spent a slide establishing a real, expensive, specific problem. The room is with you — this is the moment they're most willing to believe. And then the next slide is a feature list, or a five-minute demo that starts at login and moves methodically through the navigation.

Somewhere in there is the thing that fixes the problem. It arrives at minute four, after three things that don't, and by then the room has drifted.

The rule is almost aggressively narrow: the solution slide answers the problem slide. Nothing else goes on it.

If the problem was that a dispatcher reconciles three systems by hand every Friday, the solution slide shows the reconciliation happening automatically. Not the reporting. Not the permissions model. Not the mobile app, however good the mobile app is. Those are real and they matter and they belong later, or in the appendix, or in the second meeting.

The same goes for the demo. Start at the moment of relief. Not at login — nobody was ever convinced by a login screen. Open on the exact thing that was painful, now not painful, and stop while they still want more. Wanting more is the outcome you're playing for.

The instinct to show everything comes from a good place. You built it, all of it is hard, and none of it was obvious. Showing one part can feel like underselling the work.

But the room isn't scoring completeness. They're deciding whether the problem you described gets solved.

Answer that. Then stop.

---

More on the solution slide and the demo in The Pitch Deck Book.

Composite characters, invented companies. The mistakes are real; the people aren't.