Board presentation: fifteen minutes with people who read the pack
A board presentation is not the pack read aloud. How to structure the verbal part, what to leave in the appendix, and how to handle the question you cannot answer.
A sales presentation is not a pitch deck and not a product tour. How to structure one so it works when the buyer stops you on slide three, which they will.
A sales presentation has a different job from a deck you send investors and from a product walkthrough. Its job is to get a specific buyer to a specific next step, in a room where somebody will interrupt you — and the deck that survives that interruption is the one built so any slide can be the first one you actually get to talk about.
The buyer stopping you on slide three is the best thing that can happen, because it tells you what they actually care about. A deck built as a linear argument collapses at that point; one built as a set of self-contained sections lets you jump to the relevant part and come back. Practically: one idea per slide, a headline that states the point rather than labelling the topic, and an appendix holding the detail you would otherwise have crammed into the main flow. If your deck only makes sense in order, you have written a document and are reading it aloud.
Put the number of slides you will actually use at around ten and keep the rest in the appendix. The most common failure is not a bad deck, it is a forty-slide deck in a thirty-minute meeting where the last third — which contains the next step — is never reached.
Send a short written summary the same day: what you heard, what you proposed, what happens next and by when. This is not a formality — it is the artefact that circulates internally to the people who were not in the room, and it will be read more carefully than your deck. If what you send is just the slides, the people deciding will form their view from a document designed to be narrated.
Ettex Slides handles the delivery side with present mode and speaker notes for the argument you make out loud, while the written follow-up belongs in a document rather than in a slide. Where the deck depends on figures that change, keeping them in a sheet and the narrative in the deck avoids the version where three slides disagree.
A pitch deck asks an investor to fund a company; a sales presentation asks a buyer to take a next step. The audience, the proof required and the ending are all different.
Around ten in the main flow, with everything else in an appendix. The constraint that matters is reaching the next step before the meeting ends.
Send a short summary rather than the full deck. A deck built to be narrated reads badly alone, and sending it removes the reason for the meeting.
A board presentation is not the pack read aloud. How to structure the verbal part, what to leave in the appendix, and how to handle the question you cannot answer.
A webinar checklist covering the week before, the half-hour before and the follow-up. What breaks in practice, and the two numbers worth measuring afterwards.
A demo script keeps a product demonstration pointed at the buyer's problem instead of your feature list. How to structure one, and what to do when they ask about something you cannot show.