Generating Speaker Notes#

Slide decks don’t speak for themselves. The notes are where the actual talk lives: the transitions, the context behind the visual, the thing you want the audience to remember from this slide. Writing them well takes time, and the blank notes pane is its own kind of blank page problem.

This playbook uses AI to generate a first pass of speaker notes from your slides or outline, calibrated to your tone, your audience, and how you actually talk. The output is a starting point, not a finished script. You edit it into something that sounds like you.

The key distinction from written content: speaker notes are for being heard, not read. The rhythm matters. Sentences can be shorter. Repetition is a feature, not a bug. The AI’s default is to write for the page, and you need to push it toward the room.

When to Use#

You have a presentation coming up and the slides are done but the notes are empty.
You know what each slide is about but haven’t articulated the transition or the “so what” for each one.
You want to be prepared to talk at length without reading verbatim from the slides.
You’re handing a presentation to someone else who needs to be able to deliver it.
Your notes are too dense and you want help simplifying them to the key beats.

The Play#

Give the AI what it needs to calibrate#

Don’t just paste the slides and ask for notes. Give it context:

The audience — who they are, what they already know, what they care about
The setting — keynote to 500 people, client readout, team all-hands, recorded webinar
The length — total talk time and how much time per slide (rough is fine)
Your style — direct and punchy, conversational, story-driven, formal?
Previous speaker notes — if you have notes from a past talk that landed well, paste them in as a style reference. This is one of the most useful inputs you can provide. The AI can match your phrasing patterns, level of detail, and tone far more effectively with a concrete example of how you actually talk than with a description of how you’d like to sound.
The goal — what do you want the audience to do, feel, or believe when you’re done?

The more the AI understands the context, the less you’ll have to rewrite afterward.

Work slide by slide, not all at once#

If the deck is longer than five or six slides, work in sections rather than generating everything at once. This keeps each set of notes coherent and gives you a chance to course-correct if the style or depth is off before you get too far.

For each slide (or group of slides), provide:

The slide title and key visual or bullet points
Any specific points you know you want to make
Any transitions you want to land (especially slide-to-slide)
Time allocation if you have one

Ask for notes in the format you’ll actually use: some people want a loose paragraph, others want three bullet points, others want their talk scripted out fully. Be explicit.

Calibrate the depth#

There’s a real difference between notes that help you remember what to say and notes that script every word. Neither is universally right. Try both and see what works for you.

Light notes (beats only): If you’re a confident speaker who doesn’t want to feel tethered to the text, ask for the core point per slide and one transition. You fill in the rest.
Medium notes (paragraph per slide): If you want more to lean on but still want room to be natural. Good default for most presentations.
Full script: If you need to hit exact timing, you’re presenting in a second language, or the content is high-stakes and precise wording matters.

Specify this upfront. If the notes come back too dense or too sparse, tell the AI what to adjust and ask it to redo the section.

Read them aloud#

This is the most important step and the one most people skip. What reads well doesn’t always speak well. Read each slide’s notes out loud and mark:

Sentences that don’t land naturally when spoken
Places where the pacing feels off
Transitions that are awkward to say
Anything that sounds like text, not talk (“it is worth noting that,” “in conclusion”)

Feed these back as targeted edits rather than a wholesale rewrite. “This transition sounds stiff — make it more conversational” or “This point is too dense for a single beat — break it into two.”

Run a secondary pass for AI-isms#

Speaker notes generated by AI tend toward formal language, clean symmetry, and filler phrases, all of which sound noticeably artificial when spoken aloud. Before you finalize, run the notes through a secondary AI review in a fresh session focused on spoken delivery patterns.

Ask specifically for: sentences that wouldn’t be said naturally, overly balanced structures, hedging language, and any phrases that read better than they sound.

Build a rubric if you present repeatedly#

If you give similar presentations regularly (client updates, investor pitches, team standups), invest time in a rubric for what good speaker notes look like for your specific context. A rubric for a sales demo looks different from one for a keynote, but within each type, you’re evaluating against the same dimensions: conversational tone, appropriate depth per slide, strong transitions, clear “so what” on each point.

The rubric pays for itself across the third or fourth use.

Rubric Driven Assessment — Score your notes against a rubric for spoken delivery: conversational tone, pacing, transitions, audience awareness.
AI Driven Writing — If you’re building the slides and the notes at the same time, the writing pipeline helps you structure the narrative before you build the visuals.
Audience Translation — Delivering the same content to different audiences? Use audience translation to adapt the notes, not just the slides.
Secondary AI Review — Speaker notes that sound like AI are especially noticeable when spoken. Worth a review pass before you practice.

Prompts#

Speaker notes from slides#

I'm preparing speaker notes for a presentation. Here's the context:

- Audience: [who they are and what they know]
- Setting: [keynote / client meeting / all-hands / etc.]
- Total time: [X minutes], roughly [Y minutes] per slide
- Tone: [conversational / formal / story-driven / etc.]
- Goal: [what you want the audience to do, feel, or believe]

Here are speaker notes from a previous talk I gave that landed well — use these
as a style reference for tone, phrasing, and level of detail:
[paste previous notes, or remove this section if you don't have any]

Here are the slides:
[paste slide titles and bullet points]

For each slide, write speaker notes in [light beats / a paragraph / full script format].
The notes should sound like something I'd actually say, not something I'd read.
Flag any places where you're uncertain about what I'd want to emphasize.

Transition-focused pass#

Use this once you have a first draft and want to focus on flow between slides.

Here are my speaker notes. I want to focus on the transitions between slides —
the moments where I move from one topic to the next.

Review each slide-to-slide transition and rewrite any that are abrupt, formulaic,
or that don't make the connection clear. The transitions should feel natural to say
and should give the audience a sense of where we're going.

Notes:
[paste notes]