All articles
Brand Issue #18 05 · 2026 6 min read

The brand book is dead.

The 80-page PDF brand book is the most produced and least used artifact in modern brand work. The companies still shipping them are paying for a document nobody opens, instead of the system everyone needs.

Open your last brand book. The PDF, the Figma file, the wiki page, whichever form it took. Count how many people on your team have it open right now. If you are honest, the number is zero.

The brand book is the most produced and least used artifact in modern brand work. Every meaningful agency engagement ships one. Every meaningful client filed it somewhere two weeks after launch. The reasons are not mysterious. The document was built for a different production pipeline, one in which a designer opens it, reads it, applies it manually, and asks for permission to deviate. None of those things happen now.

What replaced the brand book without anyone announcing it

The brand is being applied to most of your surfaces by software, not by humans. The website is built on a component library that imports tokens. The product UI is themed from a design system. The internal documents are templated. The social motion is rendered through After Effects or Figma plugins that pull from the same tokens the website uses. The brand book sits in a folder, unread, because the system has already absorbed everything that mattered.

This is good. This is the right direction. The error is continuing to invoice for a PDF that documents the system, instead of building the system itself.

The shape of what replaces it

A modern brand identity ships as four artifacts, none of which is a PDF.

  1. A tokens repository. Colors, type, spacing, motion, sound, voice, expressed as machine-readable values in a shared format like Style Dictionary or Tokens Studio. Every other tool downstream consumes from here. Update the token, every surface updates automatically the next time it is built.
  2. A live component library. Both Figma and code. Buttons, cards, headings, layouts. Versioned. Documented inline. The components are the brand. The brand cannot drift from the components because the components are what gets used.
  3. A short voice document. Twelve pages, fifteen examples. Not 80. Designed to be read once and internalized. Lives on a public URL so it can be linked into Slack threads when someone asks "how do we say X".
  4. A small MCP server. Or its equivalent. A piece of infrastructure your team's LLM tools can call, so that when someone asks Claude or Cursor to draft a homepage section, the model has the tokens, the voice and the components at its disposal. The brand is now a runtime concern, not just a design-time one.

The total page count of all four put together is less than the average brand book. The total utility is roughly ten times higher.

Why this is hard, and not for the obvious reasons

The hard part is not building the tokens repository. That part is well understood. The hard part is governance. Who can change a token. Who reviews a new component. What happens when product engineering wants to introduce a color that doesn't exist in the system.

A brand book is a wall. A design system is a kitchen. Both control the food, but only one of them lets you cook.

Most companies do not have an answer to governance because the old brand book hid the question. With a PDF, the answer was always "ask the agency". With a system, the answer is "follow this process, in this repo, with these reviewers". The process has to be designed and staffed. Most companies underbudget for this and end up with a system that drifts within a year.

What this means for procurement

If you are buying brand work this year, change the brief. The deliverable is not a book. The deliverables are a tokens repo, a Figma library, a voice document and a runtime configuration that your team's tools can consume. The agency that quotes for the book is quoting for the wrong job.

If you are an agency, the change is harder. The book was easy to sell. It was tangible, it photographed well in case studies, and it sat on a desk where the CEO could see it. The system is invisible. The way to make the system tangible is to ship it as a small live website, owned by the client, that documents itself. We have moved every Studio Nine engagement onto this format over the last 18 months. Nobody has asked us for the PDF since.

The brand was always meant to be the air everyone in the company breathes. The book was a fossil of that intention. The system is the breath itself.