Platform

Builder

When an answer has structure (a comparison, a plan, a sequence, a score) chat is the wrong shape for it. Builder is the right shape. The agent renders the structured part as a canvas in the right panel while the chat reply stays short. You can read the canvas, edit it, copy from it, or send it as an attachment.

Updated today

Overview

At a glance

Where: Builder tab in the right panel
Created by: The agent when an answer has structure, or by direct request
Editable: Yes. Click any cell, header, or field
Persistence: Canvases save automatically and stay in the Builder tab for the session
Export: Copy as markdown, download as CSV, or generate a share link
Multiple at once: You can have several canvases per session; the tab lists them all

Builder is the difference between a long answer in chat and a working artifact in a tab. If you find yourself reading a wall of text and copying numbers out of it, the agent should have given you a canvas. Ask for one explicitly the next time and the agent will deliver.

What a canvas is

A canvas is a typed, editable artifact with a clear shape.

Every canvas has a kind. The kind controls the layout (table, ranked list, timeline) and the operations you can run on it (sort, filter, group, regenerate a row). The agent picks the kind that matches the work. Once a canvas exists you can keep iterating on it across turns: add columns, drop rows, ask for the same shape filled with different data.

Kinds of canvases

Four common shapes. Most work falls into one of them.

Kind	Use it when
Comparison table	You are evaluating multiple options against a shared set of dimensions
Score card	You want one option ranked against weighted criteria with a total
Sequence	The output is a series of steps over time (messages, plays, events)
Blueprint	The output is a plan, design, or doc with named sections and free-form content per section

Comparison tables

Rows are the options. Columns are the criteria.

The most common canvas. Use it for vendor comparisons, prospect lists, candidate evaluations, product feature matrices, anything where each row is an instance and each column is something you care about.

Things you can do

Action	How
Sort by a column	Click the column header
Add a column	Click the plus on the right edge of the header row
Ask the agent to fill in a new column	Add an empty column, then ask: fill in the column for each row
Drop a row	Click the row menu, then remove
Regenerate a row	Click the row menu, then refresh, optionally with a refined brief
Edit any cell	Click the cell and type

Tip

Comparison tables work best when the criteria are concrete. Vague criteria yield vague cells. Say what good looks like for each column so the agent can fill it in well.

Score cards

One subject, ranked against weighted criteria, with a total at the bottom.

Score cards are how you turn judgement into a number. They are useful when a stakeholder needs the answer to look defensible, or when you want to compare across many candidates the same way.

Common use cases

Score what	Against
A prospect	Fit, intent, account size, decision power
A vendor	Price, integration, support quality, roadmap
A candidate	Technical skill, communication, mission fit, growth potential
A landing page	Clarity, social proof, CTA strength, load time
A deal	Decision criteria, stakeholder alignment, timing, budget

Sequences

A series of steps with timing and dependencies.

Use a sequence for anything that unfolds over time. Email sequences, content calendars, sales plays, launch plans. The canvas shows each step in order with the timing and any dependencies between steps.

Common use cases

Sequence type	Example
Outbound email sequence	Five touches over three weeks with a clear hook per touch
Content calendar	Daily posts across channels for the next two weeks
Sales play	Discovery, demo, proposal, close, with what happens between
Launch plan	Pre-launch, launch day, post-launch with channels and owners per beat
Onboarding flow	Day-zero through day-thirty with check-ins and resources

Blueprints

Free-form structured docs. Named sections, prose per section.

Blueprints are for outputs that are mostly prose but have a clear shape: a product brief, a marketing positioning doc, a one-pager, a meeting prep doc. Each section is named (so you can navigate fast) and contains the free-form content the agent generated.

Common use cases

Blueprint type	Sections it usually has
Product positioning	Problem, audience, value, differentiation, message
Investor one-pager	Headline, problem, solution, traction, ask
Pre-call brief	Recap, open questions, ideal outcome, watch-outs
Project SOW	Scope, deliverables, timeline, payment, assumptions
Hiring spec	Role, must-haves, nice-to-haves, day-one outcomes, comp

Editing a canvas

You own it once it is in the tab.

01
Click anything to edit
Cells, headers, section names. The change saves on blur.
02
Ask the agent to edit
Type into chat: change column X to Y, drop the rows where Z, add a column called something. The agent applies the change to the active canvas.
03
Undo and redo
The canvas keeps a short history. The menu has undo and redo for in-session changes.
04
Rename the canvas
Click the title at the top of the canvas to rename. The new name shows in the Builder tab list.

Export and share

Get the canvas out of the platform.

Action	What you get
Copy as markdown	Markdown representation of the canvas. Pastes into any doc tool.
Download as CSV	Available for tables and score cards. Spreadsheet-ready.
Share link	Read-only URL that anyone with the link can view. Revocable.
Push to a note	Captures the current state into a note in Brain. Editable from there.
Send as attachment	Use as an attachment in a follow-up message to keep iterating with the agent.

Asking for a canvas

How to make the agent give you a canvas directly.

The agent decides automatically when structure helps. You can force it by asking. The phrases below all work.

Say	You get
Compare these five vendors as a table	A comparison table with one row per vendor
Score this prospect for me	A score card with sensible default criteria
Plan a five-touch outbound sequence	A sequence with timing and per-touch message
Write me a one-pager on this	A blueprint with named sections
Put the answer in the builder	Whatever shape best fits the answer

Note

If the canvas the agent gives you is not quite right, do not start over. Tell it what to change. Builder iteration is fast and the agent keeps context.