Skip to main content

Create a Presentation Deck

Have a workflow produce a polished 16:9 presentation deck -- full-bleed image covers, comparison matrices, data charts, hero numbers, and pull quotes -- rendered in an on-brand color scheme and ready to present, download, or share.

A deck is one of two deliverables an ORQO workflow can produce. The other is a document artifact (a paginated report, brief, or memo). Both are built by the same artifact-capable agent -- the difference is what you ask for.

Prerequisites​

What is a deck?​

A deck is a presentation: a sequence of 16:9 slides instead of paginated pages. The agent composes the whole thing end-to-end from a topic you give it -- or from the workflow's own findings -- choosing a layout for each slide:

  • Full-bleed image covers for the opening and section breaks
  • Golden-ratio split layouts that balance a focal area against a supporting column
  • Comparison / competitor matrices -- a table with checkmarks running down your column
  • Data charts -- bar, line, or area
  • Hero numbers -- a single large statistic per slide
  • Bullet lists and pull quotes
  • Headline + intro framing to say what each slide is about

By default the agent keeps to one idea per slide, reaching for a dense slide (a full matrix, a chart) only when the content calls for it. The whole deck renders in a selectable color scheme that carries your corporate identity.

Steps​

1. Enable artifacts on a stage assignment​

Open your workflow in the Workflow Builder and click the assignment node for the agent that should produce the deck. In the assignment drawer, enable the Can Create Artifacts toggle.

This is the same capability that produces document artifacts -- a deck is just a different shape of deliverable. The agent decides whether to produce a document or a deck based on your task directive.

Use a strong model

Composing a presentation-grade deck end-to-end is a rich capability. Assign a high-capability model to the deck-producing assignment for the best results. See LLM Assignment.

2. Ask for a deck in the task directive​

In the assignment's Task Directive field, make it clear you want a presentation, and describe the story you want it to tell:

  • The topic, or "build this from your findings in the previous stage"
  • The key points or sections (e.g., the problem, your solution, a competitor comparison, the numbers, the ask)
  • The audience -- a board, an investor, a customer
  • Optionally, a color scheme (midnight, ivory, or noir)
tip

Describe the narrative, not every slide. For example: "Build an investor pitch deck: a cover, the market problem, our solution, a competitor comparison matrix showing where we win, a chart of projected growth, a hero number for our current traction, and a closing ask slide. Use the midnight scheme." The agent decides how to lay out each slide.

3. Provide source material with seed documents (optional)​

If the deck should be built from existing material -- research, a data file, an earlier report -- attach it as a seed document so the agent has it as context.

  1. Click the assignment node in the Workflow Builder.
  2. In the assignment drawer, go to the Documents section.
  3. Select one or more documents from your project's document library.

The agent receives these alongside the task directive and any upstream stage results, and can turn them directly into slides.

4. Let the agent verify the deck visually​

When Can Create Artifacts is enabled, the agent can take a visual screenshot of the deck and review it -- whole-deck or one slide at a time -- before completing the stage. This is what keeps decks presentation-grade. Encourage it in the directive:

"After building the deck, preview it slide by slide. Fix any slide that looks crowded, any chart that doesn't render cleanly, or any split that looks unbalanced."

5. Run the workflow​

Start the workflow as usual (see Run a Workflow). The agent works through its directive, composes the slides, and the deck appears in the run results when the stage completes.

6. View the deck​

Open the run detail page and click the Artifacts tab. The deck appears as a grid of slides -- you can take in the whole presentation at a glance. Click any slide to open it full-screen, sized to fit the whole page; page through with the on-screen arrows or the arrow keys, and close with Escape (or a click on the backdrop).

7. Download as a 16:9 PDF​

Click Download PDF on the deck card to export the presentation as a 16:9 PDF, one slide per page -- ready to present or send.

Click Publish on the deck card to generate a public share link. Anyone with the link can open the deck in their browser -- images, charts, matrices, and your color scheme intact -- without a platform account. Click Unpublish to revoke the link immediately.

tip

Published decks are ideal for recurring updates. Run a monthly board-update workflow, publish the deck, and share the same link each cycle.

9. Save to your document library​

How decks are saved to your project's document library follows the same rules as document artifacts, based on your project's Long-Term Memory configuration. See Use Artifacts for the details.

Tips​

Iterate with re-runs

If a deck isn't quite right, refine the task directive and re-run from that stage instead of re-running the whole workflow.

Turn findings into a deck

Pair a research or analysis stage with a deck stage: the first stage gathers and structures the findings, and a deck-producing agent in a later stage presents them. The agent builds the slides directly from the upstream results -- no need to restate the content.

What's next​