Claude Prompts for PowerPoint Presentations

Most guides to claude prompts for presentations are wrong about the first step. They tell you to ask Claude to "write slide content" — and that's backwards. The problem with most bad presentations isn't the words on the slides. It's the structure underneath them, and that's the part worth fixing first.

Before: The Weak Prompt

Write slides for a presentation about our Q3 results.

Why It Fails

This prompt asks for content before structure exists. Claude will generate a reasonable-sounding set of slide titles and bullets, but with no argument to hang them on — no sense of what the audience should believe by the end that they didn't believe at the start. You end up with a data dump, not a presentation.

⚠️ Common mistake: Treating "slides about X" as the goal instead of "convince this specific audience of Y using X." A presentation without a point to prove drifts into a list of facts nobody remembers by Friday.

After: The Improved Prompt

I'm presenting Q3 results to [audience — e.g. the exec team / the
board / my direct team]. The one thing I need them to walk away
believing is: [your specific point, e.g. "we should shift budget
from paid acquisition to retention next quarter"].

Here's the raw data: [paste key numbers]

First, propose a 6-slide structure (title only, no content yet)
that builds toward this conclusion logically. Each slide title
should represent one step in the argument, not just a topic.

What this does: Asking for structure first, separate from content, lets you sanity-check the argument's logic before you're emotionally invested in slide copy you'll be reluctant to cut. It also forces Claude to organize around your specific conclusion rather than a generic "results overview" template.

⚡ Pro tip: Once you approve the 6-slide skeleton, generate content for each slide in a separate follow-up prompt, one slide at a time. Content generated slide-by-slide against an approved structure is noticeably tighter than content generated all at once against a vague brief.

Breaking Down Each Element

The named audience changes everything downstream — a board presentation and a team presentation about the same Q3 numbers should barely resemble each other in tone or level of detail, and Claude can only make that distinction if you state it.

The single conclusion sentence is the most important line in the whole prompt. It's what turns "slides about Q3" into an actual argument with a beginning, middle, and end. If you can't state your one-sentence conclusion, that's worth sitting with before you open Claude at all — no prompt fixes a presentation that doesn't know its own point yet.

The "title only, no content yet" instruction is a small thing that saves a lot of rework. Reviewing six slide titles takes thirty seconds; reviewing six full slides of content and realizing the third one is redundant takes much longer.

Variations for Different Contexts

For a sales presentation to a specific prospect:

Propose a 5-slide structure to convince [prospect company, one
sentence on their known pain point] to move forward with [your
product]. Slide 3 must address their most likely objection: [objection].

For an internal training deck:

Propose a slide structure teaching [skill] to [audience seniority
level]. Structure should move from "why this matters to your job"
to "how to do it" to "common mistakes to avoid" — not the reverse.

Scenario: Sales director prepping a renewal pitch A sales director used the objection-handling variation to restructure a renewal pitch after losing a similar deal the previous quarter — putting the objection-response slide third instead of buried at the end, where it had previously come too late to change the client's mind.

Scenario: Engineering manager presenting a technical migration to non-technical execs An engineering manager used the structure-first prompt to translate a database migration plan into a 6-slide argument for executive budget approval, deliberately excluding technical jargon from the slide titles themselves and saving detail for the appendix.

Scenario: Nonprofit program director building a funder update A program director at a nonprofit used this structure to build a funder update deck, working backward from the one sentence she needed funders to believe ("this program is ready to scale") rather than starting from a list of the quarter's activities.

Save and Reuse This

The real fix in claude prompts for presentations is separating structure from content, and grounding the structure in a single sentence you need your audience to believe. Once you've built this two-step prompt pattern — structure first, content slide-by-slide after — save it in PromptABCD, because the next deck you build starts from a proven argument shape instead of a blank Q3-results template.