Building a presentation from scratch is slow. You stare at a blank slide, rearrange bullet points, rewrite your opening three times, and spend an hour on a deck that should have taken twenty minutes.
The hardest part is not writing the content — it is structuring it. Deciding what goes on each slide, what order the ideas follow, and how to open and close. That is exactly what AI is good at when you give it the right context.
These five patterns cover the core presentation tasks: full outlines, slide-by-slide content, speaker notes, pitch decks, and Q&A preparation.
Pattern 1: The Structured Outline Builder
Before creating slides, you need a structure that tells a coherent story from opening to close. This pattern generates a presentation outline with clear logic and flow.
The Template
code
You are a presentation coach who helps professionals structure talks.
Create a presentation outline for the following:
Presentation context:
- Topic: [what the presentation is about]
- Audience: [who will be watching — their role, knowledge level, and what they care about]
- Goal: [what you want the audience to think, feel, or do after the presentation]
- Time limit: [how long the presentation should be]
- Setting: [all-hands meeting, client pitch, conference talk, team update, board meeting]
Outline structure:
1. Opening (1-2 slides): A hook that grabs attention — a surprising fact, a provocative question, or a concrete story. Not "today I will talk about..."
2. Context/Problem (2-3 slides): Establish why this topic matters to this audience right now
3. Core content (varies by time): The main points, organized in a logical sequence. For each point, provide:
- Slide title (clear and specific)
- Key message (one sentence — what this slide communicates)
- Supporting evidence or example (what makes this point credible)
4. Implications/Recommendations (2-3 slides): What the audience should do with this information
5. Close (1 slide): A memorable final statement that reinforces the core message — not "any questions?"
For the full outline, also provide:
- The narrative thread: One sentence describing the through-line that connects all sections
- Transitions: A one-line transition between each major section
- Time allocation: Approximate minutes per section given the total time limit
Constraints:
- Total slides: estimate based on 2 minutes per slide for the given time limit
- Every slide should pass the "so what?" test — if the audience would not care, cut it
- No more than one key message per slide
- Avoid sections that are only there for completeness — every section should earn its place
- Tone of the outline: [formal/conversational/energetic — match the setting]Why It Works
The "narrative thread" requirement is what separates good presentations from slide collections. It forces a through-line that connects every section. The "so what?" test instruction prevents filler slides that dilute the presentation. Time allocation ensures the outline fits the time limit rather than being an abstract wishlist.
Example Output
For a 20-minute all-hands presentation on why the company should invest in a customer education program:
Narrative thread: We are losing customers not because our product is bad, but because they never learn to use it well — and education is cheaper than churn.
>
Opening (2 minutes, 1 slide)
Slide: "What Our Churned Customers Have in Common"
Message: 68% of customers who churned in Q1 used fewer than 3 of our 12 core features.
Hook: Start with this number and let it sit for a beat. Then: "They did not leave because they did not like us. They left because they never got enough value to stay."
>
Context (4 minutes, 2 slides)
Slide 1: "The Usage Gap"
Message: There is a clear correlation between feature adoption depth and retention.
Evidence: Show a simple chart — customers using 5+ features retain at 92%; customers using 1-2 features retain at 41%.
Transition: "So the question is not how to keep customers. It is how to get them using the product deeply enough to stay."
>
Slide 2: "Why Onboarding Alone Is Not Enough"
Message: Current onboarding covers setup but not the workflows that drive ongoing value.
Evidence: Our onboarding completion rate is 78%, but feature adoption beyond the basics drops sharply after week two.
>
Core Content (8 minutes, 4 slides)
Slide 1: "What a Customer Education Program Looks Like"
Message: A structured library of courses, tutorials, and certification paths tied to specific outcomes.
Evidence: Overview of the proposed program — not the full plan, just enough to make it concrete.
Transition: "Here is why we think this works."
>
Slide 2: "The Business Case"
Message: Reducing churn by 5% through education would recover an estimated $X in annual revenue.
Evidence: Back-of-envelope calculation using our current churn rate and average contract value.
>
Slide 3: "What We Need to Build It"
Message: A small dedicated team for three months, with existing content as a foundation.
Evidence: Scope estimate — one content lead, one instructional designer, engineering support for the platform.
>
Slide 4: "Risks and What Could Go Wrong"
Message: The biggest risk is building courses nobody completes. Mitigation: start with the three highest-impact workflows and measure completion before scaling.
>
Recommendation (4 minutes, 2 slides)
Slide 1: "The Proposal"
Message: Start a pilot program in Q3 focused on the three features most correlated with retention.
Transition: "If this works, it becomes our most cost-effective retention lever."
>
Slide 2: "What I Am Asking For"
Message: Budget approval for one FTE and a Q3 pilot. Decision needed by end of month.
>
Close (2 minutes, 1 slide)
Slide: "The Cheapest Customer to Acquire Is the One You Already Have"
Final statement: "We have great customers who want to stay. We just need to show them how."
Pattern 2: The Slide Content Writer
Once you have an outline, each slide needs concise content that works visually. This pattern generates slide-ready text — headlines, bullet points, and supporting notes — that you can paste directly into your slide tool.
The Template
code
You are a presentation designer writing content for individual slides.
I have a presentation about [topic]. Here is my outline:
[paste your outline or list of slide topics]
For each slide, provide:
- Slide title: A clear, assertive headline (not a topic label — "Customer Churn Dropped 15%" not "Churn Data")
- Bullet points: 3-4 bullets maximum, each under 12 words
- Visual suggestion: One line describing what graphic, chart, or image would support this slide
- Slide notes: 2-3 sentences of additional context that the presenter can reference but that does not appear on the slide
Constraints:
- Slide titles should make the point — if someone only reads the titles, they should get the story
- Bullet points are memory aids, not sentences — trim aggressively
- No slide should have more than 40 words of visible text total (title + bullets)
- Avoid "agenda" slides unless the presentation exceeds 30 minutes
- Visual suggestions should be specific: "bar chart comparing Q1 vs Q2 retention by segment" not "relevant graphic"
- Tone: [match the presentation tone]Why It Works
The "40 words of visible text" constraint prevents the most common slide mistake: walls of text. The "assertive headline" instruction ensures titles communicate the point rather than just labeling the topic — a principle from presentation best practices that most people forget when writing slides quickly.
Example Output
For a quarterly marketing review:
Slide 3: Organic Traffic Hit an All-Time High
>
Bullets:
- 142K monthly sessions (+28% QoQ)
- Blog drove 60% of organic growth
- Top 3 posts generated 40% of traffic
>
Visual: Line chart showing monthly organic sessions over the past 4 quarters, with Q4 highlighted.
>
Notes: The growth is concentrated in 3 high-performing blog posts published in November. The rest of the blog performed consistently but did not drive incremental growth. This suggests we should double down on the content format that worked rather than publishing more broadly.
>
---
>
Slide 4: Paid Spend Is Up, But Efficiency Is Flat
>
Bullets:
- Ad spend increased 20% to $45K/month
- CAC held steady at $78 (no improvement)
- LinkedIn outperforming Google by 2x on CPL
>
Visual: Side-by-side bar chart — Google vs. LinkedIn cost per lead, with spend overlaid.
>
Notes: We increased budget expecting CAC to decrease with scale, but it held flat. LinkedIn is clearly the more efficient channel. Recommendation: shift 30% of Google budget to LinkedIn in Q1 and monitor for diminishing returns.
Pattern 3: The Speaker Notes Generator
Good speaker notes help you deliver confidently without reading from the slides. This pattern creates notes that guide your delivery — what to say, when to pause, and how to handle transitions.
The Template
code
You are a speech coach writing speaker notes for a presentation.
Presentation context:
- Topic: [topic]
- Audience: [who they are]
- Presenter's style: [formal, conversational, storytelling-heavy, data-driven]
- Presentation setting: [in-person, virtual, recorded]
I will provide my slide content. For each slide, write speaker notes that include:
1. Opening line: The first sentence to say when this slide appears — this sets the tone for the slide
2. Key talking points: 3-4 bullet points of what to cover, in the order to cover them (not word-for-word script — just the key beats)
3. Transition: One sentence that bridges to the next slide
4. Delivery cue (where helpful): A note about pacing, emphasis, or audience interaction (e.g., "pause after this number" or "ask the room before showing the next slide")
Slide content:
[paste your slides]
Constraints:
- Notes should guide delivery, not script it — provide the beats, not a verbatim speech
- Opening lines should feel natural to say out loud (read them aloud as a test)
- Include at least 2 moments in the full deck where the presenter should pause, ask a question, or invite reaction
- If a slide has data, include a note on what story the data tells — do not just restate the numbers
- Keep notes for each slide under 100 words
- Tone: match the presenter's style described aboveWhy It Works
The "opening line" for each slide solves the most awkward moment in presenting: the silence when a new slide appears while the presenter figures out what to say. Having that first sentence ready makes transitions smooth. The delivery cues prevent monotone delivery by building in natural pauses and interactions.
Example Output
For a product demo presentation, conversational style:
Slide 5: The Dashboard
>
Opening line: "This is what you see the moment you log in — and the whole point is that you should not have to click anywhere else."
>
Talking points:
- Walk through the three main sections: today's tasks, team activity, upcoming deadlines
- Point out the red indicators — these flag items that need attention without the user having to go looking
- Mention that everything on this screen is customizable
>
Transition: "Now let me show you what happens when you actually click into one of these tasks."
>
Delivery cue: Hover over each section as you mention it. Give the audience 3-4 seconds to absorb the layout before you start talking about details.
>
---
>
Slide 6: Task Detail View
>
Opening line: "Here is where the actual work gets done."
>
Talking points:
- Show the inline editing — you can change the status, assignee, and due date without leaving this view
- Highlight the activity log on the right — every change is tracked, so you always know who did what and when
- Mention integrations: this syncs with Slack and email so updates happen everywhere
>
Transition: "The question most people ask at this point is about collaboration — so let me show you how that works."
>
Delivery cue: This is a good slide to ask "has anyone here dealt with the problem of updates happening in multiple places?" before showing the integration feature. Let 2-3 people respond.
Pattern 4: The Pitch Deck Structure
Pitch decks — for investors, internal stakeholders, or clients — follow a specific logic: problem, solution, evidence, ask. This pattern creates that structure.
The Template
code
You are a pitch consultant who helps companies create compelling pitch decks.
Create a pitch deck structure for the following:
Pitch context:
- What we are pitching: [product, service, initiative, or idea]
- Audience: [investors, executives, clients, partners]
- What we are asking for: [funding amount, budget approval, partnership, contract]
- Our strongest asset: [the most compelling thing about our product/company — traction, team, technology, market timing]
- The key objection we expect: [what the audience is most likely to push back on]
Create a [number]-slide pitch deck with:
For each slide:
- Slide title (assertive, not descriptive)
- Key message (one sentence — what this slide should leave the audience thinking)
- Content notes (what data, examples, or visuals should be on this slide)
- What NOT to include on this slide (to prevent scope creep per slide)
Deck structure should follow this arc:
1. The hook — why this matters right now
2. The problem — specific and relatable to the audience
3. The solution — what you are building/proposing
4. Evidence — traction, data, or proof it works
5. The ask — what you need and what the audience gets in return
6. The close — a memorable final impression
Also provide:
- The single strongest sentence in the deck (the one line you want the audience to remember)
- Where to preemptively address the expected objection (which slide, and how)
Constraints:
- No more than [number] slides — every slide must earn its place
- Avoid jargon that the audience would not immediately understand
- Do not oversell — let the evidence speak
- If data or traction numbers are not provided, mark where they should go rather than inventing them
- Tone: [confident and grounded / urgent and compelling / calm and authoritative]Why It Works
Including "what NOT to include" per slide prevents the common pitch deck failure of cramming too much into each slide. Identifying the key objection upfront and addressing it within the deck shows strategic thinking and prevents the audience from fixating on an unaddressed concern.
Example Output
For a Series A investor pitch for a developer productivity tool:
Strongest sentence in the deck: "Every engineering team we have onboarded has recovered at least 5 hours per developer per week — and the median is 8."
>
Address the objection (expected: "this is a crowded market") on Slide 4 (Evidence) — show the retention and NPS data that demonstrates we are winning despite the competition. Let the data answer the objection instead of arguing against it directly.
>
Slide 1: "Engineering Teams Are Drowning in Context Switching"
Message: The problem is immediate, measurable, and getting worse.
Content: Open with a stat about how much time developers lose to context switching per week. Make it relatable — this audience has engineers on their portfolio companies.
Do not include: Your product yet. Build the tension first.
>
Slide 2: "The Current Solutions Do Not Work"
Message: Existing tools address symptoms (notifications, calendars) but not the root cause (fragmented workflows).
Content: Brief landscape of current approaches and why they fall short. Not a competitor teardown — a category critique.
Do not include: More than 2-3 competitor logos. This is about the problem category, not a feature comparison.
>
Slide 3: "We Built the Unified Developer Workspace"
Message: One tool that consolidates code review, communication, and task management into a single flow.
Content: Product screenshot or demo GIF. Keep it visual — show, do not describe. One sentence of how it works.
Do not include: Feature lists. Show the experience, not the spec sheet.
>
Slide 4: "The Numbers Speak"
Message: This is working — users stay, expand, and refer others.
Content: Key metrics — ARR, growth rate, NPS, net revenue retention, customer logos. This is where you address the crowded market concern through evidence: "Despite 20+ tools in the space, our NPS is [X] and net retention is [X]%."
Do not include: Vanity metrics (total signups, downloads) that do not indicate business health.
>
Slide 5: "$5M to Reach $10M ARR in 18 Months"
Message: Here is what we are raising, what we will do with it, and the milestones it unlocks.
Content: Funding amount, use of funds (60% engineering, 25% sales, 15% operations), and the ARR target with a timeline.
Do not include: Detailed financial projections — save those for the appendix or follow-up meeting.
>
Slide 6: "Join Us Before the Window Closes"
Message: The market timing is right, the traction proves the model, and this round will not stay open.
Content: One sentence on market timing, one sentence on what differentiates this opportunity.
Do not include: Desperation or artificial urgency. Let the opportunity speak for itself.
Pattern 5: The Q&A Preparation Sheet
The best presenters prepare for questions as carefully as they prepare the presentation itself. This pattern generates likely questions and structured answer frameworks.
The Template
code
You are a presentation coach preparing a speaker for a Q&A session.
Presentation context:
- Topic: [what the presentation covers]
- Audience: [who they are and what they care about]
- The most controversial or uncertain point: [what is most likely to draw questions]
- Decisions or asks in the presentation: [anything the audience needs to approve or act on]
Generate [number] likely audience questions in these categories:
- Clarification questions: Things that might not have been clear enough in the presentation
- Challenge questions: Pushback on your data, reasoning, or recommendations
- Practical questions: How to implement or act on what you presented
- Curveball questions: Unexpected but reasonable questions from someone thinking differently
For each question:
1. The question as the audience member would phrase it
2. Why they are asking (what underlying concern or interest drives this question)
3. A structured answer approach — not a script, but the key points to hit and the order to hit them
4. What to avoid in your answer (common traps for this type of question)
Constraints:
- Questions should be specific to this presentation, not generic Q&A
- Include at least one difficult question that you would rather not be asked — and prepare for it anyway
- Answer approaches should be honest — if the answer is "we do not know yet," say that
- Keep each answer approach to 3-5 bullet points
- Tone: pragmatic and groundedWhy It Works
The "why they are asking" insight helps you address the underlying concern rather than just the surface question. Including a question you would rather not be asked prevents being caught off guard by the one topic you hoped nobody would raise. The "what to avoid" section prevents common fumbles like getting defensive or over-explaining.
Example Output
For a Q&A after presenting a proposal to restructure the customer support team:
Question 3 (Challenge): "You showed that response times have improved in the pilot, but the pilot was only 4 weeks with a hand-picked team. How do you know this scales?"
>
Why they ask: They are skeptical that pilot results will hold under real-world conditions. This is a reasonable concern — many pilots succeed because of the Hawthorne effect (people perform better when they know they are being observed).
>
Answer approach:
- Acknowledge the limitation directly: "That is a fair concern. Pilots are inherently optimistic."
- Share what controls you built in: team selection criteria, workload that matched normal volumes, no additional resources beyond the restructured workflow
- Propose a phase 2: "What I am recommending is not a full rollout — it is expanding the pilot to two more teams for 8 weeks before making it permanent"
- If pressed: "If the next phase does not show similar results, we scrap it. This is designed to fail cheaply."
>
What to avoid: Do not get defensive about the pilot methodology. Do not claim the pilot is definitive. Lean into the uncertainty and show you have a plan for reducing it.
>
Question 5 (Difficult — the one you hope nobody asks): "Is this restructuring going to result in layoffs?"
>
Why they ask: Any restructuring raises anxiety about job security, even if that is not the intent. The audience may be concerned for their own teams or direct reports.
>
Answer approach:
- Answer directly: "No. This restructuring changes how the team is organized, not the size of it."
- If the honest answer is more nuanced, say so: "We expect the same headcount. There may be role changes, and I will be transparent about those as we finalize the plan."
- Acknowledge the anxiety: "I understand why that question comes up whenever someone says 'restructure.' It is a fair question."
>
What to avoid: Do not brush it off with "do not worry about that." Do not make promises you cannot keep if the restructuring plan is still in flux. Vague reassurance is worse than a direct answer.
Quick Tips for Presentation Prompts
- Specify the audience's decision-making power. A presentation to decision-makers needs a clear ask. A presentation to influencers needs talking points they can relay. The structure changes based on who acts on the information.
- Include your time limit. This is the single most important constraint for presentation structure. A 10-minute presentation has a completely different architecture than a 45-minute one.
- Describe the setting. A conference keynote, a team standup, and a board meeting have different norms for formality, interaction, and depth.
- Ask for the narrative thread first. Before generating slides, ask the AI for the one-sentence through-line. If that sentence is not compelling, the presentation will not be either.
- Test the opening out loud. Read the AI's suggested opening line aloud. If it feels awkward, ask for alternatives.
When to Use Templates vs. Freeform Prompts
Use these templates for structured presentations with a clear purpose — quarterly reviews, pitch decks, project proposals, or training sessions. The patterns ensure your deck has a logical flow and does not waste slides.
Go freeform when you are brainstorming the concept for a talk, exploring what angle to take, or working on a creative presentation where the format is part of the message. For those, use the CRAFT framework from our prompt writing guide to set up the context and let the AI help you find the structure.
For instant prompt generation without building templates manually, SurePrompts' AI Prompt Generator can structure your presentation requests automatically.