We sold you the PDF

Paul Jun, who runs brand at Ramp, published Brand as software this week. It's long. Read it anyway. The claim underneath holds up: a guideline can describe a brand, but it can't do the work. Paul is fixing that from inside a company. We're fixing it from the side that used to sell the guideline.

Every agency has shipped the same deliverable for forty years. Strategy deck, identity system, a guidelines PDF, a handshake. Then we left. The PDF went into a Drive folder. Six months later a sales deck showed up on LinkedIn with the wrong logo, an old tagline, a stock photo nobody approved. (We know because clients send them to us. Usually with an apology.)

Paul counted 375 design requests in his first six months at Ramp. That queue is the bill for the PDF. Every request is someone asking a human to re-apply a decision the company already paid for. The agency made the decision once, invoiced for it, then handed over a document that couldn't apply itself.

Guidelines fail at the handoff. The voice section says "warm but direct." The account manager writing a cold email at 11pm still has to guess what that means. So she guesses. Multiply by 400 people. Nobody broke a rule; 400 people interpreted one.

What changes

The brand can now sit inside the tools. Positioning, voice, visual system, product truths, the founder's point of view, the list of things it should never say. All of it loaded into agents that write, design, audit, and answer questions. Ask for a landing page. It knows who the page is for. Ask for a LinkedIn post. It writes in the voice, then scores its own draft against the guidelines before you see it.

We've been building this at Space since 2024. We call it Brand OS. Four jobs. It thinks (strategy work that draws on the brand's own documents). It writes (against the tone-of-voice guide). It designs (pick an asset type, an aspect ratio, one sentence, then edit from there). It audits (any asset, scored on-brand or off, with the fixes). The first client rollout was the stress test. Decks were the first thing anyone asked it for. They still are.

The brief for the interface was one line. Someone who has never opened an AI tool should be able to use it. The user is the account manager at 11pm.

What this does to agencies

The agency of the next few years is a software company delivered as a managed service. Engineers and marketers sit inside the client, build the system, load it, then maintain it. Palantir figured out the forward-deployed model for governments. Nobody has done it for brand.

The invoice changes with it. Guidelines were a one-time fee for a document. A brand system is a product. It needs an owner, a roadmap, evals, someone to fix it when the launch page comes out wrong. That's a retainer, for something that gets better every month. (Most agency retainers are for something that gets more expensive every month.)

What stays human

Paul draws the line where we do. Original work (a new identity, the sentence that makes somebody stop scrolling) can't be averaged out of what already exists. The system takes the 375 requests. People take the ten that matter.

Where we part with Paul: he assumes every company builds this in-house, an artist paired with a builder. Most won't. A fifty-person company has one designer, a Canva login, and a Slack channel called #design-requests. That company needs someone to build the system, load it, run it for a while, then hand it over once the team can carry it.

If you have a guidelines PDF and a queue, send us both.