Pitch Deck Delivery and Client Presentations

There is a critical difference between presenting and presenting a deck. Presenting a deck means you're narrating slides — the deck leads and you follow. Presenting means you're having a conversation and the deck is visual support for your points. The former loses audiences; the latter wins them. Before any client presentation, ask yourself: what do I want the client to feel, think, and do at the end of this meeting? If you can't answer that in one sentence for each question, you're not ready to present. The answers shape how you open, where you spend time, and what you ask for at the end. The opening of a presentation determines whether you have the room. The two worst openings: starting with a company overview (who cares about you yet?) and starting with an apology ('I know we're a bit over time' or 'This is a rough version of the deck'). The best openings start with the audience: a question that makes them think, a statement of what they're about to learn, or a story that puts them in the world of someone like them who had the problem you're about to discuss. Pace and pacing: most founders present too fast when nervous, which is almost always. The instinct is to get through the material quickly and reduce the risk of questions. This is the opposite of what works. Slow down. Pause after key points to let them land. Ask a question every 5–7 minutes to check understanding and keep the audience engaged. Silence feels longer to you than to your audience — they experience it as emphasis.

In a client presentation, questions are the most important thing that happens. Not because the client is trying to trip you up, but because questions reveal where their attention is, what concerns them, and what they need to hear to move forward. Founders who present defensively (treating questions as interruptions or challenges) lose the room. Founders who welcome questions and engage with them genuinely build trust in real time. The PREP framework for answering questions under pressure: Point (state your answer directly, in one sentence), Reason (explain why, with brief supporting logic), Example (give a specific example or data point), Point (restate your answer). This structure prevents rambling, which is the presentation killer for technical founders who are comfortable with complexity. For questions you don't know the answer to: never bluff. 'That's a good question — I don't have that data to hand, but I'll get you a specific answer within 24 hours' is a better answer than a five-minute detour into uncertain territory that ends with a qualified 'I think' statement. Honesty builds more credibility than comprehensive answers. For hostile or challenging questions: don't defend, explore. 'Help me understand the concern behind that question — is it about [X] or more about [Y]?' This defuses the emotional charge and often surfaces a solvable objection underneath what seemed like an attack. The close of every client presentation: never end with 'Any other questions?' End with a specific proposed next step. 'Based on what we've discussed today, I'd like to propose we schedule a scoping call with your technical lead next week and I'll send you an updated proposal by Friday. Does that work?' Specificity removes ambiguity and moves deals forward.