The brand guidelines PDF is the most-produced and least-used document in the design industry. Every agency makes one. Almost nobody opens them after the first week of the new identity being live. Then the in-house marketing team starts producing work, the work drifts, and six months later your brand looks like fifteen people with no agreement and a shared canvas.
The fix is not "make the guidelines longer." The fix is to stop delivering guidelines and start delivering a component library.
The eight artefacts we deliver instead of a guidelines PDF.
- Figma component library. Every brand element as a Figma component with documented variants. Logos, buttons, type styles, colour tokens, motion specs, photography crops, illustration system.
- Token export. Design tokens exported to JSON and CSS — the same numbers in Figma and in code, single source of truth.
- Canva mirror library. When the in-house team uses Canva, we deliver a mirror of the Figma library inside Canva. Same constraints, same components, same drift-resistance.
- Template kit. Pre-built templates for the formats the team produces weekly — social, email, paid creative, slide decks. Editable, not lockable.
- Asset library. Photography, illustration, icons, textures — organised by usage context, not by date of creation.
- Voice doc. One page. Eight rules. With examples of in-voice and out-of-voice writing.
- Decision log. The reasons each major brand decision was made — so future designers know why before they overwrite it.
- 30-minute walkthrough video. A Loom for the in-house team showing how to find and use the library. The most-watched deliverable we ship.
Why the PDF dies.
Three reasons. First, it doesn't live where the work happens. The designer is in Figma; the marketer is in Canva; the PDF is in a Google Drive nobody's looked at since onboarding. Second, it can't be edited. The moment something changes — and something always changes — the PDF goes stale and nobody updates it. Third, it implies "rules to memorise." Memorisation is the worst implementation of a brand system; the system should be unavoidable, not memorable.
How we test for survivability.
Before sign-off, we run a stress test. We hand the library to the in-house marketer who didn't come on the design calls and ask them to produce a piece of work — a social post, an email, a slide. If they produce it on-brand without asking us anything, the system survives. If they can't, we go back and fix the gap before launch, not after.
The brand system you should ship is the one that survives the marketer who didn't come on any of your design calls.
The agencies that won't do this.
Most won't, for two reasons. A component-library deliverable removes the agency's structural justification for ongoing work — the marketing team can now produce on-brand work without calling the agency. And it requires the agency's designers to think in systems, which is a different skill from making beautiful one-offs. Both reasons are the agency's problem, not yours.
If your current brand system is "a 60-page PDF and a Drive folder," you have a system that will drift in twelve months. The above eight artefacts cost less than most rebrands and last five times as long.