6 min read
·
The brand guide nobody uses, and what to build instead
A brand guide is written for people to read, not for a model to apply the same way every time. A proper foundation is what produces documents on brand.
The brand guide nobody uses goes unused because it asks busy people to do the work, and a PDF can't produce a document. The fix isn't a better guide or more reminders. It's to turn the brand into a full set of foundational documents, built in a specific structure, and package that into a Claude skill.
Why the guide gets ignored
A brand guide is a reference, not a worker. It sits in a shared drive and describes what good looks like. To use it, someone has to open it, hold it in their head, and apply it while they're busy doing the real job. Most of the time they don't. They write the report, drop in whatever logo's on the desktop, pick a font that looks close enough, and move on. The guide isn't wrong. It's just passive, and the bigger it is, the more rules there are to skip.
The cost shows up as drift, not an invoice
You never get a bill for an unused brand guide. You get drift. Two people produce the same kind of report and they look like they came from two different companies. The proposal that wins the work and the one that loses it use different fonts. A new starter copies the last document they were sent, which was already off brand, so the error compounds. None of it's dramatic on any single day, and all of it adds up to a company that looks like it doesn't pay attention to the exact people you're trying to win.
Why uploading the guide to Claude doesn't fix it either
The popular advice, including from Anthropic, is to upload your brand guide and a few examples and let Claude match your brand. From real testing, that shallow setup looks right in a demo and drifts in real use. The reason is the same reason the PDF gets ignored on the shelf. A brand guide is written for humans to interpret, not structured for a model to apply the same way every time. It holds for a paragraph, then slides back to a generic register and a plain layout. The upload-and-go version feels like progress and quietly produces the same inconsistency you already had.
What it actually takes
Reliability needs a full set of foundational documents, built in a specific structure, that capture the brand properly rather than describing it for a reader. That's the difficult part, and it's exactly why do-it-yourself attempts drift. Once that foundation exists, it gets packaged into a Claude skill. A person gives a short instruction, turn this spreadsheet into a quarterly report, and what comes back is a finished document already on brand: the right logo, the right fonts, laid out the right way, with tables that look the same on a Monday as they do on a Friday. Nobody opened a PDF. Nobody checked anything against a standard. The standard produced the document.
What this feels like day to day
The clearest way to picture it is a team of on brand administrators on call. You give one a short instruction and it produces exactly what you asked for, on brand, every time. You're not managing them and you're not checking their formatting. You describe the document and it arrives finished. That's the experience the skill gives a small team, without the team. It also changes what a rebrand means. Updating a whole filing system to a new look becomes the kind of job that takes a day rather than weeks, because the tool that produced the documents can reproduce them.
Proof it holds
We built this for Pulse Technology Hub, a Perth technology firm, as part of a full rebrand. We ran the whole process, gave them the new brand, built the foundation, and installed the skill, so their documents now come out in one look whoever makes them. We've also built it for the apparel brand Golf Subculture, keeping the brand it already had. Whether you want a rebrand like Pulse or want to keep your current brand, the foundation is what makes the documents come back consistent.
Where to start
You don't need a rebrand to do this. If you've already got a brand, we capture it into the foundation, so you keep your look and gain the ability to produce documents from it. If you're rebranding anyway, the new brand goes into the foundation from the start, so the documents and the identity land together. Either way, the brand stops being a file people are meant to follow and becomes the thing that produces the work.
Brand Ortopylot builds your brand into a full foundation and packages it into a Claude skill, so every document comes out on brand from a short instruction. See how it works at ortopylot.com.
Common Questions
Why does nobody follow our brand guidelines?
Because a guide is passive. It describes what good looks like but can't produce anything, so using it means opening a PDF and applying it by hand while busy, and most people skip that step. The reliable fix is to build the brand into a full foundation that produces the documents, so following a guide isn't a manual task any more.
Why doesn't uploading our brand guide to Claude work?
Because a brand guide is written for humans to read, not structured for a model to apply the same way every time. From real testing, the upload-and-go setup looks right in a demo and then drifts in real use, holding for a paragraph before sliding back to generic. Reliability needs a full set of foundational documents built in a specific structure, which is the part most do-it-yourself attempts skip.
What should we build instead of a brand guide?
A full set of foundational documents, built in a specific structure, that capture the brand properly and get packaged into a Claude skill. The skill then produces finished documents on brand from a short instruction, rather than asking a person to match a standard. That foundation is the hard part, and it's what separates output that holds from output that drifts.
Why are our company documents inconsistent?
Because they're produced by different people, by hand, with no shared tool that knows the brand. Each person applies the guide from memory, or copies an earlier document that was already off brand, and the drift compounds. Small and medium companies feel this most, because they produce a lot of documents without an admin team to police them.
Can we keep our existing brand without a rebrand?
Yes. We capture the brand you already have into the foundation, so you keep your current look and gain the ability to produce documents from it automatically. A rebrand's only needed if you want a new identity, in which case the new brand goes into the foundation at the same time.
How long does it take to rebrand all our documents?
By hand it's usually weeks, and often it never finishes. With the brand built into a foundation and a skill, updating a whole filing system to a new look becomes the kind of job that takes about a day, because the tool that produced the documents can reproduce them in the new brand.
Is inconsistent branding really a problem?
Yes, because it shows. When two reports from the same company look like they came from two different ones, or the winning and losing proposals use different fonts, the inconsistency reads as a lack of care to the people you're trying to win. The cost isn't a line item, it's a brand that looks unreliable.
Read the post. Now see how the system works.
The two-minute version of how it all fits together. Form on the page if you want to talk.
See How It Works
© 2026 Ortopylot. Operating from Perth, Western Australia.