Using AI Agents for PPT and Slides

Using AI on slides is not “make it pretty.” It is splitting outline and wording into jobs. Ask an agent for a deck map, one message per slide, and speaker notes first. A person still closes template, logo, and number accuracy. This article does not list prices for paid PPT tools.

Replace “make a nice deck” in the search box with the S04 skeleton: goal, scope, done-check — applied to a presentation.

How do you get the outline?

One-line answer: Write audience, time, and the decision you want in one line, then take a slide count and one sentence per slide before any design.

Inputs a person fills before the agent runs:

  • Audience: weekly internal share versus a customer decision.
  • Time: 7 minutes or 25. Slide count is bound to time.
  • One ask: what the room should do (approve, schedule, wait).
  • Material: notes and tables you already have; unpublished numbers to ban.

Sample instruction: “12 minutes, non-engineering managers, decision is ‘approve the beta date’. Eight slides or fewer. Each slide gets one message sentence and a source filename. No design suggestions.”

A useful outline artifact:

  1. Opening: the problem in one line.
  2. Context: why now.
  3. Body, three or four slides: one claim each.
  4. One slide for risks and alternatives.
  5. One slide for the ask and next week.

If the agent grows the deck, put the time box back in. “Make it richer” is a search sentence; in a talk it mixes messages on one slide. Take the outline read-only; move to copy only after you agree.

A coding agent that writes the outline as Markdown is easy to review. Generating a slide file waits until the map is locked.

What about script and bullets?

One-line answer: Bullets are short claims that stay on the slide. The script is spoken sentences. Do not mix them in one prompt.

A paragraph on the slide makes the room read instead of listen. Split roles:

  • Bullet session: one message + at most three bullets per slide. Claims with verbs, not noun piles. Numbers carry a source filename in parentheses.
  • Script session: 40–70 seconds of spoken language per slide. Transitions and caveats that are not on the slide go in speaker notes.
  • Cut session: ask “one sentence for this slide?” again and merge duplicates.

Sample done-check: “Eight slides, ≤3 bullets each, full sentences only in notes. Table figures match the attached CSV row count. Guessed numbers marked [needs check].”

Search-shaped asks (“make it punchy”) add adjectives. Job-shaped asks lock length, banned phrases, and sources. Brand slogans and legal lines are pasted by a person; tell the agent not to invent them.

If you run agents in parallel — outline versus bullets — they must read the same outline file. If each grows its own slide list, you cannot merge one deck.

Where does design have to stop?

One-line answer: Allow layout, color, and image ideas only inside a locked template. A person still gates logo, contrast, data labels, and rights.

Limits the human keeps, even when a generator paints slides:

  • Brand: logo clear-space, banned colors, official template. Reject “trendier fonts.”
  • Data: axis units, period, sample. A pretty chart hides a wrong axis.
  • Readability: body contrast, characters per slide, margins that survive a zoom share.
  • Rights: source of generated images and icons. A person checks customer-facing use.
  • Meaning: an icon must not change the claim. Decoration that beats the message fails.

Plan prices for dedicated PPT products move on vendor pages, so they are not frozen here. Confirm before you publish a number. When you pick a tool, prefer outline review in text and a lockable template over a sticker price.

Minimum path: (1) agree a Markdown outline, (2) generate bullets and notes in separate passes, (3) a person moves copy into the official template — or into a tool with the template locked, (4) re-read numbers and logo. If the agent emits a deck file, do not skip 3–4.

Slides behave like code. The outline is the diff; design is the skin. Delegating skin first keeps the search-only habit.

Sources

  • S03 role split and S04 job-shaped instructions applied to a presentation artifact.
  • Paid PPT AI pricing: vendor pages (not pinned in this article).