Vendors throw the term “Brand Vault” around as if it meant something specific. It does, but only if the vendor actually ships the artefacts. This is the inventory we expect when we evaluate AI visibility tools, and the questions to ask before signing a contract.
The five artefacts
A working Brand Vault is five files, not five marketing tabs.
1. Brand factsheet
The single source of truth for who you are: legal name, alternate spellings, HQ, year founded, founders, board, current funding stage, employee count, and the one-sentence positioning. Every other artefact references this one. If the factsheet is not under version control, it will drift, and AI engines will find the drift before you do.
2. Product matrix
Every product or SKU you sell, with: product name, category, price band, primary use case, three to five differentiating features, and the closest competitive alternative. The matrix is what the visibility tool feeds the engines; it is also the single most-edited artefact in a healthy vault.
3. Claim register
Every quantitative or comparative claim you make publicly: “fastest”, “cheapest”, “first to do X”, “trusted by 1,000+ teams”. Each claim has a source, a date, and an internal expiration. The register is the difference between an AI engine confidently citing you correctly and an AI engine confidently citing a 2022 stat you have since outgrown.
4. Citation reference set
The 50 to 200 third-party URLs that establish your authority: press coverage, analyst notes, customer case studies, podcasts you have appeared on, and meaningful reviews. The vault should know which references are still live and which have linkrotted, because engines absolutely do.
5. Persona and tone artefact
A short, written tone-of-voice document plus a “do-say / do-not-say” table. AI engines do not consume tone documents directly, but every piece of content you publish that goes into the vault should be checked against it, and that check is what protects your brand from drift.
What we expect the tool to do with the vault
A serious AI visibility tool should be doing three things with the vault, automatically:
- Detecting drift: telling you when the engines have started citing claims that the register marks as expired.
- Filling gaps: telling you which factsheet or matrix fields the engines are answering with stale or wrong data.
- Closing the loop: feeding fixes back through the channels (your owned content, your wiki page, your G2 listing) where engines actually retrieve.
If the tool only stores the vault and does not use it, you are paying for a wiki.
What we expect to own ourselves
The vault is yours. Some buyers ask: “If we churn, do we get the vault?” The answer should be yes, in a portable format (JSON or YAML), without negotiation. Vendors that lock the vault into their own UI are leveraging the wrong asset. Walk away.
Adjacent reading
- For how vendors compare on this dimension see vendor matrix.
- For procurement pitfalls see buyer’s guide.
- For the tooling shortlist see /rankings/ai-visibility-tools.
