15 Claude Prompts for Professional Presentations

Most presentations fail before the first slide is built. The structure is unclear, the narrative has no spine, and the audience leaves without knowing what they were supposed to do next. The problem is rarely the design — it is the thinking behind the deck. The right Claude prompts for presentations give you a thinking partner for that part, before you open PowerPoint or Canva.

Below are 15 prompts grouped into structure, slide writing, anticipating the room, and delivery — each ready to copy and paste. Run them in Claude, or in Chat Smith, an AI assistant that keeps Claude, GPT and Gemini in one place so you can compare how each structures the same argument.

A great presentation is a great argument. Every slide should earn its place by moving the audience one step closer to understanding, agreeing or acting. That needs a clear structure, a narrative spine, and slide copy tight enough to read in three seconds — and Claude can help with all of it, but only when the prompt names your audience, your goal, and the decision you want to drive.

A long-context model such as Claude Sonnet 5 can hold your full outline, your data and your speaker notes in one conversation, which is what lets the later prompts here critique work the earlier ones produced. Every prompt below assumes you supply three things: who is in the room, what you want them to do, and what they already believe.

Four prompts to run before you open any design tool. This is where decks are won or lost — and for board or client work, an AI proposal generator can carry the written document once the argument itself is settled.

1. The presentation structure generator

Create a slide-by-slide outline for a [type of presentation] for [audience]. The goal is to [one sentence]. Total slides: [number]. For each slide give a title, a one-sentence summary of what it communicates, and the key point the audience should take away. Then flag any slide that does not move them toward the goal.

2. The narrative arc builder

Build the narrative arc for a presentation about [topic]. Audience: [who they are and what they care about]. The tension I want them to feel: [one sentence]. The insight I want to land: [one sentence]. The action I want at the end: [one sentence]. Structure it as situation, complication, resolution, with how many slides each section takes and what the audience should be feeling at each stage.

3. The audience pre-read

I am presenting [topic] to [the audience: their roles, what they already know, what they have already decided]. Before I build anything, tell me what this audience already believes about the topic, what they will resist and why, what they need to hear in the first 60 seconds to keep listening, and the one question they will be silently asking throughout. Then tell me what my opening slide has to do.

4. The slide audit

Here is my current outline: [paste slide titles and one-line summaries]. My slot is [X minutes] and my single goal is [one sentence]. Identify which slides do not move the audience toward that goal, which two could merge, which slide is doing the most work, and what this deck would look like at half the length. Be ruthless — name specific cuts rather than giving general advice.

Five prompts for the slides themselves. The discipline throughout is subtraction: fewer words, one point per slide, and a visual wherever it beats prose — the same thinking behind a good AI storyboard generator brief. For condensing source material before it reaches a slide, an AI summarizer does the first pass.

5. The slide headline writer

Here are the current headlines from my slides: [paste the list]. Rewrite each as an assertion — a complete sentence stating what the audience should believe after that slide, not a label for its contents. Under 10 words each. Audience: [describe]. Overall goal: [one sentence]. Then tell me whether the headlines alone tell a coherent story in order.

6. The body copy sharpener

Here is the content I want on a slide: [paste your draft]. The headline is: [headline]. Audience: [describe]. Rewrite it as slide copy that supports the headline directly, uses no more than three bullets or 40 words, removes anything the audience does not need in order to believe the headline, and avoids jargon. If any content belongs on a different slide, say which.

7. The executive summary slide

Here is my outline: [paste slide titles and one-line summaries]. Create a single executive summary slide covering the core problem in one sentence, the recommendation in one sentence, the strongest supporting evidence, and the decision required from the audience. Under 80 words total. Write it so a busy executive could understand the entire deck from this slide alone.

8. The data slide translator

Here is the data I want to show: [describe the chart or paste the figures]. The takeaway I want the audience to reach: [one sentence]. Write an assertion headline stating that takeaway, one sentence of context explaining why it matters, and a callout highlighting the most important number or trend. Audience: [describe]. Do not use the word "shows", and tell me if the data does not actually support my takeaway.

9. The visual brief

Here is a slide's headline and content: [paste them]. Instead of more text, tell me what this slide should show: the specific chart type, diagram, image or comparison that would make the point faster than words. Describe it precisely enough that a designer could build it, and say what text should remain alongside it. If the point genuinely needs no visual, say so.

Three prompts for the people in the room and what they are thinking. Objections and questions decide more pitches than slides do — AI interview practice is a useful way to rehearse answers out loud once you have them, and for pitch decks there is a fuller set of Claude prompts for sales.

10. The objection slide creator

I am presenting [describe your proposal] to [audience]. Based on this outline: [paste it], identify the three most likely objections. For each, write the objection as the audience would phrase it internally, a response that acknowledges the concern before answering it with evidence, and whether it deserves a dedicated slide or belongs in Q&A.

11. The pre-wire briefing

I am presenting [describe the proposal] to [the decision-making group] on [date]. I want to pre-wire these stakeholders first: [list them with roles and what they care about]. For each, draft a short message I could send in advance that gives them the context they specifically care about, asks for input rather than approval, and surfaces any objection before the meeting. Tell me which one I most need on side beforehand and why.

12. The Q&A simulator

I am presenting [describe the presentation and its key claims] to [audience]. Generate the eight hardest questions this audience is likely to ask. Phrase each as they would actually say it — direct, sometimes sceptical. For each, write a confident two to three sentence answer, and flag any question where the honest response is "I will follow up with the data" rather than answering on the spot.

Three prompts for the last mile: what you actually say, how the deck holds up under a critical eye, and what happens when your slot gets cut in half ten minutes before you walk in.

13. The speaker notes writer

Write speaker notes for these slides: [paste headlines and bullet points]. For each, give three to four sentences the presenter should say out loud — not a description of the slide, but the reasoning that fills the gap between the headline and the next slide. End each with a transition. Tone: [confident and conversational / formal and precise / energetic].

14. The deck reviewer

Act as a senior communications consultant who has reviewed hundreds of executive presentations. Review this deck outline for a [type of presentation] to [audience]: [paste slide titles and summaries]. Score it out of 10 on narrative clarity, audience relevance, strength of the ask, evidence quality and flow. Name the weakest point in each category, then the two slides most likely to lose the room and why. Be direct.

15. The timing and cut-down plan

Here is my deck: [paste slide titles and one-line summaries]. My slot is [X minutes] including Q&A. Estimate realistic spoken timing per slide, flag where I am likely to overrun, and give me a cut-down plan for three scenarios: losing five minutes, losing half my time, and being asked to summarise the whole thing in two minutes. For each, name exactly which slides survive.

Use them in order. The audience pre-read and structure generator come before you open any design tool; the headline and body copy prompts tighten each slide once the outline is agreed; the reviewer runs before you finalise, and the Q&A simulator and cut-down plan belong to the night before. Each step gives the next one better material to work with.

Match the model to the task. Headline batches and body copy variants are volume work that a light model such as Claude Haiku 4.5 handles quickly. Structure, the deck review and the objection work want the strongest reasoning you have. If you build a lot of documents beyond decks, the wider set of Claude prompts covers writing, analysis and business work in the same style.

A deck needs several prompt types working together — structure, narrative, headlines, body copy, speaker notes, Q&A prep — and rebuilding each one from memory before every board meeting is where the time goes. Chat Smith lets you save them as reusable templates, group them by deck type, and share the set with teammates building presentations in parallel.

It also runs several AI models in one place, so the same structure prompt can go to two models and be compared. That is genuinely useful here: two models given the same brief will often disagree about what the opening slide should do, and the disagreement usually reveals that you had not decided either.

Start with the audience pre-read on whatever deck is next in your calendar. If it turns out you had misjudged what the room already believes, you will have saved more time than every other prompt here combined.