ChatGPT Prompts for Presentations: Slides, Speeches, Pitches

Published: July 2026 | 8 min read

A great presentation is not just slides on a screen — it is a structured argument, a visual story, and a performance. AI can help you build all three: the slide structure, the narrative script, and the delivery notes. These prompts cover the full presentation workflow from idea to standing ovation.

Slide Deck Creation

1. Slide Deck Outline Generator

Role: Presentation structure specialist
Task: Create a slide deck outline for [presentation topic].
Audience: [Who they are, what they know, what they expect]
Duration: [Minutes — this determines slide count]
Purpose: [Inform, persuade, train, pitch, update, keynote]
Key message: [The ONE thing they should remember]
Outline structure:
1. Title slide (title, subtitle, presenter, date)
2. Hook (2-3 minutes: story, question, statistic, or bold claim)
3. Agenda (what we will cover — 3-5 items max)
4. Section 1: [Problem/Context] (2-3 slides)
5. Section 2: [Key Insight/Analysis] (3-5 slides)
6. Section 3: [Solution/Recommendation] (2-3 slides)
7. Evidence (data, case study, demo — 2-3 slides)
8. Implementation/Next Steps (1-2 slides)
9. Q&A prompt slide
10. Closing slide (key takeaway + contact)
For each slide:
1. Slide number
2. Title (short, declarative — not "Overview" but "Why 40% of Projects Fail")
3. Content type (text, chart, image, demo, video, interactive)
4. Key points (2-3 bullets max)
5. Speaker notes (what to say that is NOT on the slide)
6. Transition (how to move to the next slide)
Rules:
- One idea per slide
- Slides support the speaker, not replace them
- 1 slide per 1-2 minutes of speaking
- No more than 6 bullets per slide, 6 words per bullet (6x6 rule for text slides)
Output: Complete slide deck outline ready for production.

2. Slide Content Writer

Role: Slide content writer
Task: Write the content for [slide description].
Slide purpose: [What this slide should accomplish in the presentation]
Content type: [Text, comparison, data, quote, image-led]
Format:
1. Slide title (5-7 words max, action-oriented or insight-driven)
2. Body content:
   - If text slide: 3-5 bullet points, each under 10 words
   - If comparison: 2-column table (before/after, us/them, problem/solution)
   - If data slide: chart description (what chart, what data, what insight to highlight)
   - If quote slide: the quote, attribution, context
3. Visual suggestion (what image/graphic would support this slide?)
4. Speaker notes (the full narrative for this slide — 3-5 sentences)
5. Transition to next slide (one sentence linking this to the next point)
Rules:
- Slides should make sense without the speaker (if handed out)
- BUT slides should not contain everything the speaker says
- Bold key terms for visual scanning
- No complete sentences in bullets (unless quoting someone)
- Numbers are better than words ("73%" not "a large majority")
Output: Slide content ready for PowerPoint/Keynote/Google Slides.

3. Visual Design Specification

Role: Presentation design consultant
Task: Create a visual design specification for [presentation].
Brand: [Company colors, fonts, logo guidelines if applicable]
Audience: [Who will see this — internal team, external clients, conference?]
Design specification:
1. Color Palette:
   - Primary (background or key elements): [hex]
   - Secondary (accents, highlights): [hex]
   - Text colors (primary text, secondary text): [hex]
   - Semantic colors (positive/green, negative/red, neutral/gray): [hex]
2. Typography:
   - Title font: [family, weight, size for title slides, section slides]
   - Body font: [family, weight, size for bullets, labels]
   - Data font: [family for numbers/charts — tabular figures]
   - Minimum font size: 18pt (anything smaller is unreadable)
3. Layout Grid:
   - Slide size (16:9 standard)
   - Margins (safe zone for content)
   - Title position (top, with consistent spacing)
   - Content area (where body goes)
   - Footer/page number position
4. Slide Types:
   - Title slide (centered, minimal, brand-forward)
   - Section divider (bold section name, number, brand color)
   - Content slide (title + bullets or visual)
   - Data slide (title + large chart + insight callout)
   - Quote slide (large quote text, attribution, brand background)
   - Closing slide (key takeaway, contact, brand)
5. Visual Elements:
   - Icon style (line, filled, duotone — pick one and stick with it)
   - Chart style (minimal gridlines, direct labels, brand colors)
   - Image style (photographic, illustrative, or abstract — pick one)
   - Consistent spacing and alignment throughout
Output: Design spec ready for designer or template creation.

Speech & Script Writing

4. Full Speech Script Generator

Role: Professional speechwriter
Task: Write a speech script for [presentation].
Topic: [What the speech covers]
Audience: [Who is listening, what they know, what they feel about the topic]
Duration: [Minutes — determines word count, roughly 130 words per minute]
Tone: [Professional / inspirational / conversational / formal / persuasive]
Key messages: [2-3 things they must remember]
Script format:
1. Opening (30-60 seconds):
   - Hook (story, question, statistic, or bold statement)
   - Why this matters to THIS audience (make it relevant to them)
   - Roadmap (what we will cover)
2. Body (divided into 2-3 sections):
   For each section:
   - Section transition (signpost: "Now let us look at...")
   - Main point (the argument or insight)
   - Evidence (data, example, story, analogy)
   - Application (what it means for the audience)
   - Transition to next section
3. Closing (1-2 minutes):
   - Summary (not a repeat — a synthesis: "What this all adds up to is...")
   - Call to action (what they should do, think, or feel)
   - Memorable close (callback to opening, powerful quote, or forward-looking statement)
Formatting:
- [PAUSE] for dramatic pauses
- [EMPHASIZE] for words to stress
- [SLOW DOWN] for important points
- [Slide: X] for slide change cues
- [Transition] for movement or body language cues
Word count target: [duration in minutes] x 130 words
Output: Complete speech script with delivery cues.

5. Speaker Notes from Slide Deck

Role: Presentation coach
Task: Write speaker notes for each slide in this deck.
Deck: [List of slides with titles and content]
Presentation context: [Purpose, audience, duration]
For each slide:
1. What to say (2-4 sentences that expand on the slide content — NOT reading the slide)
2. Key emphasis (which word or point to stress)
3. Timing (how long to spend on this slide)
4. Transition (how to move to the next slide — one sentence)
5. Body language cue (gesture, eye contact, movement suggestion)
6. Q anticipation (what question might this slide trigger? prepare an answer)
Rules:
- Never read the slide — the audience can read
- Add value: context, example, story, or insight not on the slide
- Keep notes short (they are reminders, not a script — unless requested)
- First slide and last slide get more notes (open and close matter most)
Output: Speaker notes document for each slide, ready for presenter view.

6. Q&A Preparation Guide

Role: Presentation prep coach
Task: Prepare a Q&A guide for [presentation topic].
Presentation: [Topic, key arguments, audience]
Anticipated questions (10-15):
Category 1 — Clarification (they did not understand something):
1. "Can you explain [concept] more?" 
   Answer: [clear, concise explanation with example]
2. "What did you mean by [phrase]?"
   Answer: [rephrase in simpler terms]
Category 2 — Challenge (they disagree):
1. "How do you respond to [counterargument]?"
   Answer: [acknowledge, then present your evidence]
2. "Is not [alternative approach] better?"
   Answer: [fair comparison, acknowledge merits, explain why your approach is better for THIS context]
Category 3 — Application (how do I use this):
1. "How would this work in [specific situation]?"
   Answer: [walk through the application step by step]
2. "What would you do if [edge case]?"
   Answer: [practical guidance, or honest "that is a great question, here is what I would consider"]
Category 4 — Extension (where can I learn more):
1. "Where can I read more about [topic]?"
   Answer: [specific resources — books, papers, links]
2. "What is next for [this initiative/technology]?"
   Answer: [forward-looking perspective]
For each answer:
1. The answer (2-4 sentences, conversational)
2. Key data point or example to support (if applicable)
3. Bridge back to key message (if the question took you off track)
Also include:
- "I do not know" responses (how to handle questions you cannot answer gracefully)
- Hostile question handling (stay calm, acknowledge, pivot to what you DO know)
Output: Q&A preparation guide for the presenter.

Pitch Decks & Business Presentations

7. Investor Pitch Deck Builder

Role: Pitch deck consultant
Task: Create an investor pitch deck for [company/startup].
Company: [What you do, stage, traction, ask]
Deck structure (12-14 slides):
1. Title (company name, tagline, logo, presenter)
2. Problem (the pain — make it visceral, not abstract)
3. Solution (your product in one sentence, with a visual)
4. Market (TAM/SAM/SOM — bottom-up, not "trillion dollar market")
5. Product (how it works — 3 screenshots or a demo flow)
6. Traction (metrics that matter: revenue, growth, retention, logos)
7. Business Model (how you make money — pricing, unit economics, CAC/LTV)
8. Go-to-Market (how you sell — channel, sales process, growth strategy)
9. Competition (2x2 matrix or comparison table — show you know the landscape)
10. Team (why THIS team — relevant experience, not just impressive titles)
11. Financials (3-year projection: revenue, gross margin, burn, runway)
12. The Ask (how much, what for, milestones it will fund)
13. Use of Funds (breakdown: product, sales, hiring, marketing)
14. Contact + Appendix (backup slides for detailed questions)
For each slide:
1. Slide title
2. Content (what goes on the slide — concise)
3. What the presenter says (what is NOT on the slide but should be spoken)
4. Design note (what visual element supports this slide)
Rules:
- 10-15 slides total (investors see hundreds — respect their time)
- Every slide should be understandable in 30 seconds
- Numbers, not adjectives ("3x growth" not "rapid growth")
- The problem slide should make the investor feel the pain
Output: Complete pitch deck outline with speaker notes.

8. Sales Pitch Deck

Role: Sales enablement specialist
Task: Create a sales pitch deck for [product/service].
Product: [What you sell, who buys it, what problem it solves]
Buyer: [Who is in the room — role, industry, company size]
Deck structure (8-12 slides):
1. Title (your company, their company, meeting purpose)
2. Agenda (what we will cover — sets expectations)
3. Their Situation (show you understand their world — current state, challenges)
4. The Cost of Inaction (what happens if they do nothing — make the pain concrete)
5. Our Solution (how we solve it — in their language, not feature-speak)
6. How It Works (simple flow diagram — implementation, timeline, effort)
7. Proof (case study or testimonial from a similar company — with results)
8. ROI (investment vs return — payback period, total savings, risk reduction)
9. Comparison (why us vs alternatives — including doing nothing)
10. Next Steps (clear, simple path forward — pilot, demo, proposal)
11. Summary (1 slide: the problem, the solution, the ROI)
12. Appendix (detailed feature slides, security, integrations, FAQs)
For each slide:
1. Content (what is on the slide)
2. Talk track (what the salesperson says)
3. Discovery questions (what to ask the prospect on this slide)
4. Objection handling (what objection might come up, how to respond)
Output: Sales deck with talk tracks and discovery questions per slide.

9. Conference Talk Proposal

Role: Conference speaker proposal writer
Task: Write a conference talk proposal for [topic].
Conference: [Name, audience, typical talk length, themes]
Proposal sections:
1. Title (compelling, specific, not generic — "How We Cut Deploy Time by 90%" not "DevOps Best Practices")
2. Subtitle (1 sentence expanding on the title)
3. Abstract (150-250 words for the program):
   - Hook (1-2 sentences: why this matters to the audience)
   - What they will learn (3-4 bullet points)
   - Approach (stories, data, case study, live demo?)
   - Takeaway (what they will be able to do after)
4. Outline (5-7 bullet points: the flow of the talk)
5. Key takeaways (3 bullet points: what the audience leaves with)
6. Why this talk? (why are YOU the right person to give this talk?)
7. Why now? (why is this relevant at this conference, this year?)
8. Audience level (beginner, intermediate, advanced)
9. Format (talk, workshop, panel, ignite)
10. Prerequisites (what should attendees know before?)
11. Past talks (links to recordings or slides from previous talks)
12. Speaker bio (100 words: who you are, why you are credible)
Rules:
- Titles with numbers or specific results get accepted more often
- "We" is more credible than "I" (shows real experience, not theory)
- Be specific about outcomes (not "learn about X" but "be able to do Y")
- Reviewers read hundreds — make the abstract skimmable
Output: Complete conference talk proposal ready for submission.

Data Visualization & Delivery

10. Chart-to-Slide Adapter

Role: Data presentation specialist
Task: Adapt this chart/data for a presentation slide.
Data/chart: [Describe the data and what it shows]
Slide context: [What point is this slide making in the presentation?]
Transformation:
1. Simplify:
   - Remove gridlines (or make very light)
   - Remove chart border
   - Remove legend if < 4 series (direct-label instead)
   - Round numbers (73.2% -> 73% on slide, keep detail in appendix)
   - Keep only the data that makes the point (do not show all 20 categories, show top 5)
2. Highlight:
   - What is the key insight? Make that the title ("Revenue Grew 42% in Q3" not "Revenue by Quarter")
   - Use color to draw attention (brand color for the key bar/line, gray for the rest)
   - Add annotation (callout box with the key number or insight)
3. Format for slides:
   - Large enough to read from back of room (minimum 18pt labels)
   - High contrast (dark text on light background or vice versa)
   - No 3D effects, no gradients, no shadows (they distort data)
   - Horizontal bar chart if labels are long (easier to read than rotated labels)
4. Speaker notes:
   - What does the chart show? (1-2 sentences)
   - What is the insight? (1 sentence: the "so what")
   - What should the audience do? (1 sentence: the "now what")
Output: Chart specification (ready to build in PowerPoint/Keynote) + speaker notes.

11. Demo Presentation Script

Role: Demo presentation specialist
Task: Write a demo script for [product/feature].
Product: [What you are demoing, who the audience is, what they care about]
Demo structure:
1. Setup (30 seconds):
   - "Let me show you how [product] handles [scenario]"
   - What we are about to do (set expectations)
   - Why it matters to them (connect to their pain)
2. Demo flow (3-5 minutes):
   For each step:
   a. Action (what to click/type — exact steps)
   b. What to highlight (call attention to what matters — "notice here that...")
   c. What to say (the narration — not describing what they see, but why it matters)
   d. Wow moment (the thing that makes them say "I want that")
3. Pivot points (if audience asks a question, where to detour):
   - If they ask about X: go to [backup slide/feature]
   - If they ask about Y: show [related capability]
4. Common issues and recovery:
   - If demo is slow: have a talking point ready
   - If demo fails: have a screenshot/video backup
   - If audience is quiet: have a question to re-engage
5. Close (30 seconds):
   - Summary (1 sentence: what they just saw)
   - Next step (what to do: trial, follow-up meeting, proposal)
Rules:
- Never demo more than 3 features (the audience cannot absorb more)
- Show the outcome first, then how it works (not the other way around)
- Talk about the benefit, not the feature ("this saves 30 minutes per task" not "this is the automation panel")
- Practice the exact clicks (muscle memory = smooth demo)
Output: Complete demo script with exact steps, narration, and backup plans.

12. Presentation Review Checklist

Role: Presentation quality reviewer
Task: Create a presentation review checklist.
Review dimensions:
1. Structure:
   - Is there a clear opening (hook + agenda)?
   - Does each section build on the previous one?
   - Is there a clear close (summary + CTA)?
   - Would the deck make sense if read without the speaker?
2. Content:
   - Is the key message clear (can you state it in one sentence)?
   - Is every slide necessary (any that could be cut without loss)?
   - Are claims supported by data or examples?
   - Is the language appropriate for the audience?
3. Visual Design:
   - Consistent fonts, colors, alignment?
   - Text readable from the back of the room (18pt minimum)?
   - Slides not too dense (6x6 rule for text slides)?
   - Charts clear and properly labeled?
   - No clip art, stock photos that add nothing, or decorative elements?
4. Delivery:
   - Speaker notes present for each slide?
   - Timing allocated per slide/section?
   - Transitions planned between slides?
   - Q&A anticipated and prepared?
5. Audience Focus:
   - Does it address what the audience cares about?
   - Is the language about THEM, not about US?
   - Is there a clear ask or next step?
6. Technical:
   - File format correct (PDF backup of PPT)?
   - Embedded videos tested on the presentation machine?
   - Fonts embedded (if custom)?
   - Links tested (if any)?
Generate 25-35 review items.
Format: Presentation review checklist for self-review and peer review.

Best Practices

For more communication content, see our ChatGPT prompts for meeting notes and ChatGPT prompts for report writing.