Built, Not Generated

The video at the top of this page is the one on our home page. It's called How Bryn Works and it runs 1:16. The storyboard was filed on October 7. The cut was live by October 13. Storyboard to live, inside a week.

I'd expect most people to assume the fast part was a prompt: somebody described the video to a model, picked the least strange result, and went to lunch. That isn't what made it fast. What made it fast is that every number in it traces to a place you can open. Each number on screen is one the demo workspace, a sample account inside the product, actually holds. The voice is synthetic. The words it reads aren't: every line of the voiceover started as a row in the storyboard. The colors came from a brand system that was already written down. The week went on assembly, because the parts were already there.

The video follows one signal: something a buyer just did, like coming back to your pricing page. A company opens pricing for the third time this week. Bryn, the agent we built at Civic to spot buyers on your site and run the follow-up you approved, works out who it is. Then a rule fires, the team hears about it in Slack, and the run leaves a receipt. This piece is about how it got made, and about the bigger version of the same idea.

Where the number came from

There are two ways to make a marketing asset now, and from across the room they look the same.

Generated means a prompt goes in and an asset comes out. It can be beautiful. What it doesn't have is a source behind any frame. The chart in the corner is chart-shaped. The quote is quote-shaped. The number on the dashboard is whichever number looked right.

Built means parts go in and an assembly comes out. The parts already exist and already have owners: the product's own screens, the values in a demo workspace, the brand's colors and type, the copy rules, a storyboard somebody signed off. Assembly is the work. Every frame in the result can point at the part it came from.

The tell is one question. Ask where a number came from. In a generated asset the answer is "the model," which is another way of saying nowhere. In a built one, the answer is a place you can open. The "3rd visit this week" in the first frame of our video came from the demo workspace. The storyboard's rule was that the words "Demo workspace" appear on screen once, so every number in the cut is visibly the workspace's own, and nobody watching has to take it on faith.

Fortune wrote last Thursday about Apple stitching its old rainbow logo by hand and releasing a video of the hands at work, and the line I kept was that the people behind the work can become part of the pitch. I'd put it one notch more plainly. Care shows when every part has a source.

Here's the cut taken apart, beat by beat.

Where the agents earn it

None of this is new. Good teams have always built from parts. What's changed is what the parts cost to fetch. Pulling the real screen, finding the real value, checking a line against the rules, checking the caption again for the punctuation you banned: each one is a small errand, and a video is a long list of small errands. That's why generating was tempting. It skips the errands.

Agents don't make building fast by writing faster. They make it fast by running the errands. Fetch the part. Check it against the rule. Assemble. Check the assembly against the rule again, because the second pass is where the small mistakes turn up. The rules stay human. Somebody decided that every motion on screen would be a change of state, that the voice would read a script written line by line, and that the video would carry no metric the workspace doesn't hold. Those rules are the craft. Agents just stop them being the bottleneck.

I've made the other kind. A couple of years ago I made a slide background from a prompt. It took about a minute and it looked good. It had a little chart in the corner, rising, because the prompt said growth. In the meeting someone asked what the chart showed. It showed nothing. It was chart-shaped. I'd saved a minute and spent the next ten explaining a line that didn't measure anything. That's the trade generating offers: the time comes back later, in front of the person you least want to explain it to.

So the week was simple to describe. The storyboard came first, with its rules and its checks written down before production. The parts came from places that already existed. Then the checks, then the home page.

The two dates on the ends are on the record. What's between them is what the week was for.

The materials that move a deal

A video for the home page is the easy case. It's one-to-many: you build it once, everyone sees the same thing, and if a part is wrong you fix it once.

The materials that move a deal are one-to-one. A page about the company that just came back. The pack you read before the call. The image you attach to a note. The follow-up itself. Each has a bill of materials too, and the parts aren't screens and brand colors. The parts are records: what the account just did, what the CRM already holds, what was already sent, what already ran.

That's where a system of action comes in: software that reads what all your other tools know, acts on it by rules you wrote, and keeps a record of every move. I made the longer case for one in A System of Action. The short version, for this piece, is that the record a system of action keeps is the best parts bin a marketer has ever had.

The Brief. Name a company and Bryn hands back a page about it, in that company's own colors, inside a minute. It ends on its own receipt: the clock of each step. I wrote up what's in one in Let me be Brief..., and How a Brief Is Built walks the receipt line by line. Every section traces to the step that produced it. A tile with no step behind it isn't shown.

The meeting pack. Before an external call we put together a cheat sheet and a demo deck shaped to the account. The parts are the CRM history and Bryn's read of the account: what they looked at, who's been in touch, what was said last time. Agents assemble it. The record is what makes it right.

The attached image. Every Field Note here ships with images for its social posts, and they're cropped from the essay's own figures and rendered on the server from its own markup. The poster this video sits behind was drawn the same way, as markup, and every label on it is a line someone wrote.

The follow-up draft. A rule you set once: when this happens, do that. Bryn calls that a Play. When one fires, the draft arrives with its evidence attached: the visits, the account, the rule that matched. A draft that writes to a customer can wait in Approve mode: Bryn drafts the step and waits for your yes. The draft is built from the run, so the yes is a yes to something you can read.

Pick what an account just did, and see what each one is built from.

The speed comes from the record

I've spent the last few weeks writing about running growth as a team of one. The Work That Runs Without You handed the small, triggered work to rules. The last part, The Stack You Hand Over, lands on Thursday. This piece sits beside the series, because the person who owns the number usually owns the materials too, and there's no second person to make them.

Here's what I've found. When the record is good, building is fast, because the parts are sitting there: the visit, the history, the run, the figure. You fetch, check and assemble, and the result can cite every line. When the record is thin, building is slow, because every part is an errand to go and find, and generating starts to look reasonable. That isn't a character flaw. It's a supply problem.

So the order of work changes. Fix the record first. Then let agents build from it. The materials get faster as a side effect, and they get the one thing generation can't give them, which is an answer when someone asks where a number came from.

Where Bryn fits

Bryn is the system of action the Brief, the meeting pack and the follow-up draft all draw from at Civic. It watches the site and the product for signals, runs the Plays we approved, and keeps the record those materials cite. We ran it on ourselves first, which I wrote up in We Are Customer Zero, and we still do. Every run is logged, so the people who sign off can read it. Bryn is not another dashboard to watch. It is the governed execution layer that runs Plays through your stack. In plain terms: it runs the follow-up you approved, inside the tools you already use, and leaves a record that anything you build afterward can point to.

The gift

Before you ship any asset this week, write its bill of materials. One line per frame or claim. Name the part, and where it lives.

A number on a slide: which report, pulled on which date. A screenshot: which screen, in which workspace. A quote: who said it, and where it's written down. A line of copy: which rule it was checked against.

Anything you can't fill in is the part that was generated. Replace it with a part that has a source, or cut it. You'll ship a little less, and what you ship will hold up when someone asks.

Stop watching signals. Start running them.