Presentation

A presentation is a slide deck the assistant builds for you from a brief and real research — the kind of thing you'd walk into a meeting with or send as a leave-behind. It's laid out and branded for you: your colours, your logo, and a slide design chosen to fit each point rather than the same bulleted list twelve times over. You review the actual slides in the app, and download it as a PowerPoint file when you're ready to present. Finished decks live in your Library under a Decks filter, alongside everything else the assistant has made for you.

How to create one

Start a session and describe the topic and who it's for. If the deck supports a specific campaign, that campaign's chat is a good place to start, since the assistant will already have the campaign brief and any attached documents as source material. Otherwise, Pulse is a good place to start.

A simple request is enough to get going — "build a presentation on [topic] for [audience]" — but the more you tell it up front (how many slides, whether you want deep research first, what the call to action should be), the fewer questions it needs to ask before starting.

See Using AI sessions for general tips on writing a good prompt.

The checkpoints

Building a deck isn't a single step — the assistant stops and checks in with you six times along the way, and won't move past a checkpoint until you say it's good:

1. The brief — topic, audience, and what you want the deck to accomplish.
2. The evidence — the sources it will back the argument with, whether from research or from the material you supplied. (See "Bringing your own research" below.) The research and sources found to back up the deck's claims.
3. The narrative and outline — the story the deck will tell and the order the slides will go in.
4. The draft slides — titles, bullets, and a sample of speaker notes, before any images are generated.
5. The deck with visuals — the same draft with images placed.
6. The finished deck — the quality review's findings (weak claims, missing citations, anything else it caught) shown together with the finished deck, ready to save to your Library. Approving here is what saves it; nothing reaches your Library before you do.

At each checkpoint you can approve and move on, or say what you'd like changed. Feedback doesn't restart the whole deck — the assistant redoes just that step with your feedback in mind and shows you the same checkpoint again.

If you'd rather not be asked, say so. Tell the assistant something like "build the whole deck without asking me questions" and it will run every step — brief, evidence, narrative, draft, visuals and the quality review — without stopping, then save the finished deck and summarize what it decided along the way, including anything the review flagged. It's the same pipeline; you're trading the checkpoints for speed, and you can still ask for changes to the finished deck afterwards. A deck built by an automation runs this way by default, since there's nobody there to ask.

You can ask for changes to specific slides. "Slide 4's title isn't landing", "cut the third bullet on the pricing slide", "make the numbers slide two stats instead of three" — the assistant edits exactly those slides and leaves the rest untouched, word for word. It does not rewrite the deck around your comment, so a change you asked for on one slide can't quietly alter another. If it can't make a change you asked for — the evidence doesn't support it, or it contradicts something you approved earlier — it tells you which slide and why rather than silently skipping it. After a few rounds without a clear approval, it will check whether you'd like to keep iterating, accept the current draft and move on, or take a different approach entirely.

If your feedback actually changes something decided earlier — for example, you're at the draft-slides checkpoint but you want to change the audience, which was settled back at the brief — the assistant will say so and offer to reopen that earlier checkpoint, rather than quietly building on top of a decision your feedback just changed.

Bringing your own research

Web research is optional. You'll be asked how much you want — quick, deep, or none — and if you've already done the work, choose none.

That's the right choice when you paste your own findings into the prompt, or point the assistant at a document or file you've already got: a report, a white paper, a campaign brief. It builds the deck from that material and cites it as the source, and it won't spend minutes searching the web for things you've already found.

One thing to know: your material becomes the whole evidence base. A claim it doesn't support gets dropped rather than quietly filled in from somewhere else — so if there's a number you want in the deck, make sure it's in what you give it.

Speaker notes

Every content slide gets speaker notes, not just a stack of bullet points (section dividers and the title slide don't need them). The notes carry the source for any statistic on that slide plus a short delivery cue — what to emphasize, where to pause, what to say when the slide comes up. The notes travel with the deck into the PowerPoint file, so they're there when you open it to present.

Evidence you can trust

Every statistic in the deck is cited, and you can see exactly where each one came from at the evidence checkpoint. If the assistant can't find a credible source for a claim, it drops the claim rather than inventing a number to fill the gap — it will tell you when that happens so you can decide whether to narrow the topic or move on without it. The deck's sources are listed on a Sources slide near the end, followed by a closing call-to-action slide.

Downloading

From your Library, open the session the deck was built in, then click the deck's tile to see its preview panel. From there you can download it as PowerPoint, Markdown, HTML, or Word, depending on what you need it for — PowerPoint if you're presenting it, Word or Markdown if you want to keep editing the text, HTML if you want to share it as a standalone page.

Example prompts

• "Build a presentation on [topic] for [audience], using the campaign brief and attached documents as the source. About 12 slides, with speaker notes."
• "Create a presentation on [topic] for [audience]. Do deep web research first and cite every statistic. Show me the outline before you build any slides."
• "Build a deck from [file name] — skip the web research, everything you need is in there. 10 slides for [audience]."
• "Turn the white paper [file name] into a 10-slide presentation for [audience]. Keep the argument, drop the detail."
• "I need to present [topic] to [audience]. Propose two or three narrative angles before you write anything."
• "Build a webinar deck on [topic]. Around 15 slides, with speaker notes detailed enough to present from."

FAQ

Q: Can I skip the checkpoints and just get a finished deck? A: No — the checkpoints are how the assistant makes sure it's building the right thing before it invests in the next step, especially the narrative and outline, which everything after it depends on. You can move through each one quickly by approving as you go if you're happy with what you see.

Q: What happens if I give feedback at the same checkpoint more than once? A: The assistant keeps revising and re-presenting that checkpoint. After a few rounds without a clear approval, it will check whether you'd like to keep iterating, accept the current draft and move on, or take a different approach entirely.

Q: Will the assistant make up a statistic if it can't find a source? A: No. It only cites what it can actually find, and it will tell you when a claim had to be dropped for lack of a credible source, rather than inventing a number.

Q: Where do I find a deck after it's built? A: In your Library, under the Decks filter — both the main Library and a campaign's own Library tab if the deck was built for that campaign.

Q: What formats can I download a deck in? A: PowerPoint, Markdown, HTML, or Word, from the artifact panel's download options.