Presentations are one of the highest-leverage things professionals create — and one of the most painful to build well. A single deck can determine whether a deal closes, a project gets funded, an idea catches on inside a company, or a conference audience stays engaged for forty minutes instead of checking their phones. The problem is that building a great presentation is a multi-disciplinary task: you need narrative structure, visual design, audience psychology, public speaking technique, and domain expertise, all working together.

AI tools are remarkably good at this — when prompted correctly. The key insight is that "make me a presentation about X" produces terrible output because a presentation is not a document. It is a performance supported by visuals. Structured prompts that separate the narrative outline, the slide content, the speaker notes, and the visual direction — and that specify audience, length, and purpose — produce dramatically better results.

This guide gives you a complete set of reusable prompt templates for presentations of every kind: internal status updates, investor pitch decks, conference talks, training sessions, sales presentations, and academic lectures. Every prompt follows the five-part framework — Role, Task, Context, Constraints, Output Format — with bracketed [PLACEHOLDERS] you adapt to your situation.

Why Presentations Need a Different Prompting Approach

Presentations fail when you treat them as documents. A slide is not a page of a report; it is a visual anchor for a moment of speech. Here is why structured prompts matter so much:

The audience cannot re-read a slide. Content that works in a report fails on a screen because the audience has about six seconds to absorb a slide before the speaker becomes the focus again.
Less is more, but less is harder. The temptation with AI is massive — generate twelve bullet points when three will do. Constraints in your prompt must force compression.
Speaker notes are not the slides. The worst slides are the ones where the presenter reads the slide aloud. Good prompts separate what the speaker says from what the audience sees.
Visual direction is separate from content. AI text models should not specify pixel-level design, but they should give a creative brief that a tool — or a human designer — can execute.
Narrative shape matters. A status update, a pitch, and a conference talk have fundamentally different structures. Telling the AI "this is a board update that takes 12 minutes" is more useful than listing topics.

The prompts in this guide treat presentations as the multi-layered artifacts they are.

Presentation Architecture Prompts

1. The Narrative Outline Before Any Slides

Role: You are a presentation strategist who has coached hundreds of talks for TED, corporate keynotes, and investor pitches. You believe the narrative structure should be locked before a single slide is designed.

Task: Create a narrative outline for a [LENGTH — e.g., 15-minute, 40-minute, 5-minute lightning] presentation about [TOPIC] for [AUDIENCE — e.g., a board of directors, a room of 200 developers, a sales team weekly, a university lecture hall].

Context: The purpose of this presentation is [PURPOSE — e.g., secure a Series A, train a team on a new process, persuade leadership to adopt a new tool, present research findings]. The audience's current knowledge level is [EXPERTISE]. The audience's starting attitude toward the topic is [ATTITUDE — skeptical, neutral, enthusiastic, hostile]. The single most important thing the audience should do or believe after this talk is [THE ONE THING]. Supporting points that matter are: [LIST 3-5 KEY POINTS]. Stories or examples that are available: [ANY SPECIFIC STORIES, DATA, OR CASE STUDIES YOU HAVE].

Constraints: Structure the outline around a narrative shape — not "Introduction, Body, Conclusion." Use one of: a journey, a problem-solution arc, a myth-busting structure, a "what is, what could be, how we get there" pattern, or a debate structure. Give each section a working title and a one-sentence summary of what the speaker will accomplish in that section. Specify the approximate time for each section that totals to the target length. Include exactly one "the turn" — the moment where the presentation shifts from what the audience expects to what you want them to see. End with a single, specific call to action — not "let's continue the conversation" but a concrete next step.

Output Format: Markdown with H2 for each section. Time allocation in brackets after the section title. No slides yet — just the narrative skeleton.

2. The 10-Slide Pitch Deck Skeleton

Role: You are a startup accelerator pitch coach who has reviewed over 1,000 decks and knows what investors actually look for — and what makes them stop paying attention.

Task: Create the slide-by-slide skeleton for a [STAGE — pre-seed, seed, Series A, Series B] investor pitch deck for [COMPANY DESCRIPTION — one sentence about what the company does].

Context: The company is [COMPANY NAME] and [ONE-PARAGRAPH DESCRIPTION]. Target check size: [DOLLAR AMOUNT]. Key metrics: [LIST 3-5 METRICS]. Founded [DATE], team size [N], located in [LOCATION]. Investors so far: [EXISTING INVESTORS]. The biggest objection investors raise is [OBJECTION]. The "why now" is [MARKET SHIFT].

Constraints: No more than 10 slides. For each slide, provide: (1) Slide number and title. (2) The ONE key message — the single sentence the investor should leave with. (3) What should be ON the slide visually — chart, diagram, screenshot, quote, etc. (4) What the speaker should SAY while the slide is up — the 30-45 second spoken version. (5) The likely investor question this slide will provoke and a one-sentence answer.

Cover these slides: Problem, Solution, Market Size, Product, Traction, Business Model, Competition, Team, Financial Projections, The Ask. You may reorder or combine these, but the deck must tell a coherent story — not just dump information. Do NOT include a "thank you" slide — use the final slide as a visual CTA.

Output Format: Markdown. H2 for each slide.

3. The Board Update Structure

Role: You are a chief of staff who has written hundreds of board updates and knows that board members want signal, not noise — and that the wrong update can derail a meeting into tactical rabbit holes.

Task: Create the structure for a 20-minute board update deck about [TOPIC — e.g., Q3 progress, a strategic pivot, a funding decision, a hiring plan].

Context: The board is [COMPOSITION — e.g., three investors and two independent directors]. Current company situation: [BRIEF STATE]. Key wins since last update: [LIST]. Key concerns: [LIST]. The decision you need from the board: [DECISION]. The bad news you might need to surface is [BAD NEWS or "none"].

Constraints: Maximum 8 slides. Structure as: (1) Headline message — one slide, one sentence. (2) Progress against last quarter's commitments — with traffic light colors. (3) Current metrics with trend lines. (4) The one decision you need from the board today. (5) The risks and how you plan to mitigate them. (6) What you need from the board going forward — intros, advice, cover. Every slide must pass the "busy board member who read this on the way to the meeting" test — each should be fully comprehensible without the spoken narrative.

Output Format: Markdown with H2 for each slide, the key message in bold, and a "spoken version" in italics.

Slide Content Prompts

4. The Bullet-Reducer

Role: You are a presentation designer who believes that every bullet point on a slide is a failure of imagination — but you understand that sometimes bullets are necessary, and when they are, they should be razor-sharp.

Task: Take the following slide content and reduce it to the minimum number of bullet points that still communicates the full message. Each bullet must be under 12 words.

Context: This slide supports [SPEAKER'S POINT]. The audience is [AUDIENCE]. The slide will be on screen for approximately [SECONDS].

Constraints: Maximum 4 bullets. Prefer 3. Each bullet is a phrase that works as a visual scan — not a complete sentence. No bullet should be a sub-point of another bullet; if they overlap, combine them. Use parallel grammatical structure across all bullets. No buzzwords or generic phrases ("leverage synergies," "drive innovation"). If any content should move to the speaker notes instead of the slide, say so explicitly.

Output Format: "SLIDE:" then the bullets. "SPEAKER NOTES:" then anything that moved off-slide.

[INSERT OVERSTUFFED SLIDE CONTENT]

5. The Data Story Slide

Role: You are a data storyteller in the tradition of Edward Tufte and Cole Knaflic — you believe a chart should make one point, unmistakably, and that most charts fail because they try to show everything.

Task: Design one slide that presents the data below as a story — not just a chart. Tell me what chart type to use, what to exclude, what to annotate, and what the speaker should say.

Context: The data is [INSERT DATA OR DESCRIBE THE DATASET]. The one insight the audience must walk away with is [THE KEY INSIGHT]. The audience's data literacy is [LEVEL]. The speaker has [SECONDS] on this slide.

Constraints: Do NOT include every data point — include only what supports the key insight. Specify: (1) Chart type and why. (2) What to leave out — data that would distract. (3) The one annotation that makes the insight unmissable — a callout, a comparison line, a color highlight. (4) The title of the slide — not a description of the data but the conclusion the data supports. (5) The "so what" — a sentence the speaker says after the audience has absorbed the visual.

Output Format: Markdown with labeled sections. The slide title in bold at the top.

[INSERT DATA]

6. The Visual Concept Brief

Role: You are an art director who briefs slide designers. You do not design slides — you describe what they should feel like, and let designers execute.

Task: For each slide concept below, write a one-paragraph visual brief that a designer can execute. Describe the mood, the focal metaphor, the key visual element, and the do-not-do list.

Context: The presentation's overall visual identity is [MOOD — e.g., minimal and editorial, bold and geometric, warm and human, technical and precise]. The brand colors are [COLORS]. The visual constraint is [CONSTRAINT — e.g., no stock photos, only original illustrations; no text-heavy slides; one concept per slide].

Constraints: Each brief should be specific enough to act on but open enough to allow creative interpretation. Do NOT say "make it modern" or "clean layout" — those words mean nothing to a designer. Instead say things like "a single oversized number that fills 60% of the slide, with the supporting context as small caption text in the bottom corner." Address: focal point, color treatment, typography hierarchy, the one thing that should NOT happen.

Output Format: For each slide: "Slide [N]: [Title]" then the visual brief.

[INSERT SLIDE CONCEPTS]

Speaker Notes and Delivery Prompts

7. The Speaker Notes Generator

Role: You are a speechwriter who writes speaker notes that are actually useful — not transcripts, not vague cues, but prompts that help a presenter deliver naturally.

Task: Write speaker notes for the following slide-by-slide outline. The notes should be what the presenter says, not what is on the slides.

Context: The presenter's speaking style is [STYLE — e.g., energetic and informal, calm and authoritative, storytelling-heavy, data-driven]. The total talk length is [MINUTES]. The presenter's comfort with the material is [LEVEL — expert, familiar, new]. The presenter has [REHEARSAL TIME] to prepare.

Constraints: Notes for each slide should match the time allocated — about 130 words per minute of talking. Write in the way people actually speak — contractions, shorter sentences, natural pauses marked with [PAUSE]. Include delivery cues: [SLOW DOWN], [EMPHASIZE THIS], [GESTURE], [LOOK AT AUDIENCE]. Where the speaker should reference the slide visually, indicate with [POINT TO CHART] or [LET IT LAND — 3 seconds]. Do NOT write a script word-for-word — write notes that guide, not trap. Where appropriate, include an improvised moment — a bracketed instruction like "[ask the audience: how many of you have experienced this?]" that the presenter can use or skip. End each slide's notes with a transition cue to the next slide.

Output Format: For each slide: "Slide [N] — [Title] ([SECONDS]):" then the speaker notes in plain text.

[INSERT OUTLINE]

8. The Q and A Preparation Brief

Role: You are a media trainer who prepares executives for the toughest questions and knows that the Q and A is where most presentations are won or lost.

Task: Anticipate the questions the audience will ask after this presentation and prepare brief, strong answers.

Context: The presentation is about [TOPIC]. The audience is [AUDIENCE]. The most controversial or weakest part of the presentation is [WEAK SPOT]. The one thing the presenter hopes no one asks about is [SCARY TOPIC]. The factual claims that could be challenged are [CLAIMS].

Constraints: Generate two categories of questions:

Expected questions — 5 questions the audience will almost certainly ask, with 2-3 sentence answers that are direct, confident, and avoid filler.
Hostile or difficult questions — 3 questions designed to put the presenter on the defensive, with answers that acknowledge the validity of the question, provide the counterpoint, and pivot to a stronger frame. Use the structure: Acknowledge, Answer, Redirect.
For each hostile question, include a "trap to avoid" — the way NOT to answer that would create a problem.

Output Format: Markdown with H3 headings for each question. Answer in plain text. "Trap" in italics for difficult questions.

9. The Opening That Grabs the Room

Role: You are a keynote speechwriter who knows that the first 30 seconds determine whether an audience gives you their attention for the next 30 minutes.

Task: Write three different opening options for a [LENGTH] presentation about [TOPIC] for [AUDIENCE].

Context: The tone of the talk is [TONE — e.g., urgent, inspirational, provocative, reassuring]. The "so what" of the entire talk is [THE SO WHAT]. The presenter is comfortable with [STYLE — e.g., storytelling, provocation, humor, data-driven authority] and should avoid [WHAT THEY DISLIKE].

Constraints: Each opening should be under 90 seconds when spoken — about 180 words. Each must be fundamentally different in approach:

Option A — The story: Open with a specific, real story — not a hypothetical, not a joke. The story must connect to the core message within the first 30 seconds.
Option B — The provocation: Open with a statement that challenges the audience's current belief. Must be genuinely uncomfortable, not a soft "you might think X but actually Y."
Option C — The question: Open with a question that the audience cannot answer and will spend the rest of the talk answering. The question must be specific, not rhetorical.

No "thank you for having me" preambles. No "I'm here to talk about [obvious thing]." Start in the middle of something.

Output Format: Three sections labeled "Option A," "Option B," "Option C."

Specialized Presentation Prompts

10. The Sales Demo Presentation

Role: You are a sales engineer who has run thousands of product demos and knows that demos fail when they show features instead of telling a story about outcomes.

Task: Structure a 20-minute product demo presentation for [PRODUCT] to [BUYER PERSONA] at a [COMPANY TYPE].

Context: [PRODUCT] is [ONE-SENTENCE DESCRIPTION]. The buyer's primary pain is [PAIN]. The buyer's current solution is [STATUS QUO]. The competitive alternatives are [COMPETITORS]. The outcome the product delivers is [OUTCOME]. The one feature that is most convincing in a demo is [KILLER FEATURE]. The feature that is impressive but NOT worth showing because it distracts is [DISTRACTING FEATURE].

Constraints: Structure the demo as: (1) The current state — 2 minutes framing the pain without bashing the competitor or current solution. (2) The "aha" moment — 5 minutes of the single most compelling demo flow that resolves the pain. (3) The "and there's more" — 5 minutes of 2-3 supporting capabilities that build on the aha moment. (4) The outcome — 3 minutes of the results other customers have seen, ideally with specifics. (5) The close — 5 minutes of next steps and questions.

For each section, specify what the presenter should do in the product — the actual clicks and screens — and what to say. Do NOT show every feature. If the presenter feels the urge to show a feature, put it in the "reserve for Q and A" list.

Output Format: Markdown with H2 for each section. Click-by-click instructions in a sub-bullet.

11. The Training Deck Structure

Role: You are an instructional designer who knows that training succeeds when participants DO the thing, not when they LISTEN about the thing.

Task: Structure a [LENGTH — e.g., 90-minute, half-day, 2-hour] training session on [TOPIC] for [AUDIENCE — their role and experience level].

Context: By the end, participants should be able to [LIST 3-5 LEARNING OBJECTIVES — concrete, observable skills]. Participants currently can [CURRENT ABILITY]. The biggest misconception they hold is [MISCONCEPTION]. The practice materials available are [WHAT YOU HAVE — exercises, case studies, datasets].

Constraints: Apply adult learning principles: no more than 15 minutes of talking before a change of pace — an exercise, a discussion, a quiz. Every section must have one thing the participants DO, not just hear or see. Structure as: Hook — why this matters to them, 3 minutes. Concept — the framework, 12 minutes. Practice — apply it, 15 minutes. Discussion — debrief what happened, 5 minutes. Repeat for each concept module. Estimate time for each segment that totals the session length. Include a knowledge check that is applied, not a pop quiz — a scenario they must solve using the concepts.

Output Format: Markdown table with columns: Segment, Time, Type, Activity, Materials Needed, Facilitator Notes.

12. The Conference Talk Structure

Role: You are a conference speaker coach who has coached talks for major industry conferences. You know that conference audiences are distracted, skeptical, and have seen a thousand talks — your talk has to earn attention, not assume it.

Task: Structure a [LENGTH — e.g., 30-minute, 45-minute, 15-minute] conference talk about [TOPIC] for [AUDIENCE — e.g., 500 software engineers, 200 product managers, a general tech audience].

Context: The talk's core argument is [ARGUMENT]. The talk's unique angle — what makes this different from other talks on the same topic — is [ANGLE]. Stories or examples available: [LIST]. Visual materials: [WHAT YOU HAVE — slides, live demo, code walkthrough, video]. The talk's title is [TITLE].

Constraints: Conference talks need a different shape than corporate presentations. Structure as: (1) Cold open — start with something that hooks in the first 60 seconds, no setup. (2) The promise — what the audience will learn, in one sentence, delivered at the 90-second mark. (3) Three acts — not three bullet points but three movements that build on each other. Each act should have a moment of tension, a reveal, and a resolution. (4) The callback — reference the opening story or image at the end to give the talk structural closure. (5) The takeaway — one and only one thing the audience should leave with, stated explicitly.

No "agenda slide." No "about me" slide. No "let me tell you about my company" preamble. The talk is about the audience's problem, not the speaker's credentials.

Output Format: Markdown with H2 for each act, bullet points for the beats within each act, and speaker time estimates.

The Full Workflow: From Brief to Delivered Presentation

Great presentations are built in stages, not in one shot. Here is the recommended workflow using the prompts above:

Start with the narrative — use prompt #1 to lock the story shape before touching slides.
Build the skeleton — translate the narrative into slides with prompts #2 or #3 depending on the context.
Write tight slide content — use prompt #4 to compress every slide's bullets.
Design data slides thoughtfully — use prompt #5 for any slide that shows data.
Brief your visual designer — use prompt #6 if you are working with a designer or using an AI design tool.
Write speaker notes — use prompt #7 to create notes that actually help you present instead of scripts that trap you.
Prepare for Q and A — use prompt #8 so you are never caught flat-footed.
Craft the opening — use prompt #9 to win the first 30 seconds.

Using AI at each stage means you move faster, but more importantly, each stage forces you to make explicit decisions about audience, purpose, and narrative — the decisions most presenters skip and most presentations suffer for skipping.

What to Avoid: Presentation Anti-Patterns

Watch for these common failures that bad prompts produce:

The wall of text slide. If your prompt does not constrain word count, the AI fills every slide. Always specify "maximum [N] bullets, 12 words each."
The read-along. If your speaker notes are identical to the slide content, the presenter will read the slides. Always separate them in your prompt.
The feature dump. In demo presentations, unconstrained AI will list every feature. Constrain to the one killer feature plus two supporting ones.
The template voice. Without specific tone instructions, AI writes presentations in a bland corporate voice. Specify the emotional texture: "urgent but not alarmist," "confident but humble," "provocative but substantiated."
The missing call to action. Presentations without a clear next step waste the audience's attention. Always include in your constraints: "End with one specific action the audience should take."

Build Your Presentation Prompt Library

The prompts in this guide are starting points. As you use them, you will find adjustments that fit your particular domain, your visual brand, and your speaking style. Save those refined prompts as templates.

With a tool like PromptWright, you can build these prompts as reusable templates with labeled variables — so instead of pasting in a wall of text each time, you fill in fields like "audience," "length," and "key insight" and generate a fresh outline, slide skeleton, or speaker note set in seconds. You can also test the same prompt across different models — GPT-4o, Claude, DeepSeek, Gemini — to find which produces the strongest narrative structure or the tightest slide content for each presentation type you build.

Treat your presentation prompts as a living library, not a fixed set. After each presentation, note what worked and what didn't, and refine the prompts. Over a few cycles, you will have a personal presentation engine that turns rough ideas into structured, persuasive talks in minutes — giving you back the hours you used to spend wrestling with slide formatting and bullet points.

→ Build Your Presentation Prompt Library at PromptWright

AI Prompts for Presentations: Slides, Pitches, and Talks