Skip to main content

Presentation Decks

A presentation deck is one of the two kinds of deliverable an ORQO workflow can produce. Where a document artifact is a paginated report, brief, or memo, a deck is a set of 16:9 slides -- the kind of presentation a founder would actually stand up and present.

Decks are produced by the same artifact-capable agents that produce documents. An agent with the Can Create Artifacts capability decides, based on its task, whether the deliverable should be a document or a deck -- you simply ask for "a presentation" or "a slide deck" in the task directive.

tip

Decks are a rich, strong-model capability. Composing a polished, on-brand presentation end-to-end works best with a high-capability model on the deck-producing assignment. See Model Picker.

What the agent composes

You give the agent a topic -- or let it work from the workflow's own findings -- and it composes the whole presentation end-to-end. A finished deck can combine any of these slide ideas:

Slide ideaWhat it looks like
Full-bleed image coverAn edge-to-edge image with the title set over it -- the opening or section-break slide
Golden-ratio splitA major focal area beside a narrower supporting column, balanced on the golden ratio
Comparison / competitor matrixA dense comparison table with checkmarks running down your column -- "us vs. them" at a glance
Data chartA bar, line, or area chart rendered crisply on the slide
Hero numberA single large statistic that carries the slide
Bullet listA focused set of points, one idea at a time
Pull quoteA highlighted quotation -- testimonial, vision statement, or key takeaway
Headline + intro framingA large headline (with one word accented in your brand color) and a single framing sentence above the slide's content

The agent chooses the layout and content for each slide. You describe the goal and the key points; it decides how to lay them out.

One idea per slide -- by design

By default, decks follow one-idea-per-slide discipline: each slide makes a single point cleanly. The agent deliberately uses a dense slide -- a full comparison matrix or a data chart -- only when the content genuinely calls for it. The result reads like a deck built by a designer, not a wall of text.

On-brand color schemes

Every deck renders in a selectable color scheme that carries your corporate identity:

SchemeFeel
MidnightDark, high-contrast -- bold and modern
IvoryLight, editorial -- clean and approachable
NoirMonochrome -- understated and premium

The same slides render in any scheme, so you can switch the look of an entire deck without rebuilding it. The agent selects a scheme that fits your brand; you can request a specific one in the task directive.

Your brand colors

The schemes carry your organization's identity because you define the brand palette once, in Settings → Branding (organization admins only). You set four brand colors -- Background, Title, Body, and Accent -- for dark decks and, separately, for light decks, using a dark/light toggle with a color picker for each. ORQO derives the rest of each palette (surfaces, muted text, borders) automatically so every deck stays coherent and on-brand. Your heading and body fonts are set in the same place.

When a deck renders in a dark scheme it draws from your dark brand colors; in a light scheme, your light ones. This is what lets a single deck switch schemes and still look like it belongs to you.

You can also set a type scale in the same place -- a Title and a Body percentage that make headlines and body text larger or smaller. This is font-only: it changes how loud or how tight the type reads without altering the layout, so you can move a deck from a bold, pitch-style look toward a more compact, business-report feel. It applies to every deck the organization produces, in any format.

Any workflow can override the organization palette with its own brand colors -- and its own type scale: open the workflow's settings and expand the Branding Override section. This is useful when one workflow produces decks for a different brand or client. Individual artifacts can also be fine-tuned live in the artifact's Theme editor.

The agent verifies its own work

Just like document artifacts, a deck-producing agent can visually preview its work before finishing. It renders the deck, looks at it, and fixes problems -- a misaligned chart, an awkward split, a slide that's too crowded -- before completing the stage. The agent can also zoom in on a single slide to check it at full detail.

This self-review is what makes decks presentation-grade rather than rough drafts. You can encourage it in your task directive:

"After building the deck, preview it slide by slide and fix any slide where the layout looks crowded or a chart doesn't render cleanly."

Viewing and sharing a deck

A finished deck appears on the workflow run page under the Artifacts tab, and you can work with it in several ways:

ActionWhat happens
View as a lightbox of slidesThe whole deck is laid out as a grid of slide thumbnails -- you can take in the entire presentation at a glance
Click a slide to enlargeClicking a thumbnail opens that slide large over a dimmed backdrop; step through with the arrow keys, close with Escape
Download PDFExport the deck as a 16:9 PDF, one slide per page -- ready to present or send
Publish a share linkGenerate a public link anyone can open in a browser, no account required; unpublish to revoke it instantly

Published decks render with full formatting -- images, charts, matrices, and your color scheme intact -- on a clean standalone page with no platform chrome.

Decks vs. documents

DocumentPresentation deck
ShapePaginated pages16:9 slides
Best forReports, briefs, memos, dashboardsPitches, summaries, comparison decks, board updates
Built byAn artifact-capable agentThe same artifact-capable agent
How you request it"Write a report / brief...""Build a presentation / slide deck..."
ViewInteractive HTML pageLightbox grid of slides
DownloadPaginated PDF16:9 slide PDF
Share linkYesYes
On-brandCorporate identity colors & fontsSelectable color scheme carrying your identity

Both are produced by the same capability and share the same publish, download, and save-to-library options. See Artifacts for the document side and the shared lifecycle (publishing, PDF export, saving to your document library).