Introduction

The Factory is where braaand produces creatives, and where you come back to work on what it produced. That covers more ground than "make a hundred ads": a full campaign batch, a round of variations on your best-performing creative, a Score-and-refine loop that reworks the weak half of a batch, or one idea you're hand-developing. In the app it's the Workflows part of your brand: every campaign you launch becomes a workflow there, and opening one lands you on its node canvas. One surface wears three hats: a node editor where you wire up how creatives get made, a canvas where every creative in the run is visible and pickable, and a production line that executes the graph durably, surviving closed tabs and navigation.

That combination is the point. Most tools make you choose between automating a hundred creatives and hand-developing one idea, or between shipping a batch and optimizing it. Here it's all the same act: wiring a node onto something. Wire a Score onto a whole batch, onto the three cards you selected, or onto one single creative that doesn't even exist yet. Route the losers into a Rerun, drop a Vary node on the winner to spin off new angles, or wire nothing at all and just ship what you built. The pipeline doesn't care which grain, or which stage of the creative process, you're working at.

The mental model

Four nouns, each with one job:

• A workflow (a run) is a verb: one execution of a pipeline. It owns the build's progress, its cost, its log. Find them under Workflows in the brand nav.
• A board holds creatives for review: keep/discard, sections, comments, client sign-off. One board can collect results from many runs. See Boards.
• A collection organises the work: the campaign folder grouping the runs, the boards, and the creatives that belong together. See Collections.
• A share link exposes a board read-only to someone with no braaand account, the client review link. Minted per board, revocable any time.

So: workflows produce → boards hold → collections organise → sharing exposes. Every run files itself into a collection at launch and drops its results onto a board; you never have to tidy up after a run to find its output.

Three ways to work

Everything on the canvas can be wired at three grains, and they're not three features. They're three places to start a wire:

1. A whole batch: every lane of creatives has an outlet on its right edge meaning "everything this node produces". Wire it onward and the full batch flows.
2. A selection: check a few cards and a node's Run narrows to exactly those.
3. One creative: a single card (or a promise of one, see the node editor) wires out on its own, takes its own path, and genuinely leaves the batch. Whatever the batch feeds next works on the rest.

Runs are durable

Press Run pipeline and the run belongs to the server, not your tab. Navigate away, close the laptop, it keeps building, shows up as a live pill next to the command palette orb wherever you are, and pings you when it's done. Reopen its canvas any time to watch each creative move through its stages (writing copy, finding an image, fitting layout), or come back a week later and wire something new onto the finished batch.

A run's full accounting, what it built, what each stage cost in time and credits, what the judge said, is one click away: Copy run log in the canvas sidebar produces a shareable text log you can paste to a colleague or an AI.

Where to go next

• Campaigns: the quick path, hand braaand a brief, review the batch on a board.
• Workflow builder: promises, wiring, and how the canvas works.
• Nodes: every building block, one by one.
• Examples: worked pipelines to copy from.
• Boards and Collections: where results land, and how they're organised.
• Recipes: reusable pipelines you run by name.