Companion Briefs · v1 For James May 11, 2026

Two briefs.

Companion to the v4 memo. Answers the two questions you asked: how the Encoder sees patterns, and how the Vault bridges to every AI app feels seamless.

BRIEF 01

How the Encoder sees patterns.

Your note: "Want to understand how the encoder sees patterns. That sounds awesome and if we can crack that it would be worth paying for." Agreed. Here is what I actually mean.

Pattern recognition is a staircase. Three kinds of patterns, each available at a different stage of the company. Tier 1 ships immediately. Tier 2 builds with the portfolio. Tier 3 is the long game and the reason the company is worth a lot in five years.

Tier 1 · Ships day one
Vocabulary patterns.

Words and phrases that are universally vague and never survive scoring. The blocklist looks something like this: innovation, authentic, premium, trusted, passion, purpose-driven, best-in-class, world-class, reimagined, disruptive, agile, customer-obsessed, mission-driven, values-led.

Almost every founder uses three of these words in their first answer about voice. The Encoder catches each one and runs a structured pushback prompt. The point is not to ban the word — it is to force the founder to define what they actually mean. Half the time, the answer reveals the real distinctive thing the brand stands for. The other half, the founder realizes they have been hiding behind the platitude.

Example · the actual flow Q: How would you describe the voice of your brand?
A: Professional yet authentic, with a touch of warmth.

Pushback: "Professional yet authentic" is true of almost every B2B brand on earth. So is "warmth." Help me get to the version of this that only describes your company. If a competitor read your support replies and a competitor read your CEO's tweets, what would tell them apart in the first sentence?

A: We sound impatient with received wisdom but never impatient with the customer. We make concessions to clarity but never to brevity.

Pushback: Now we are getting somewhere. Show me three examples in the wild.

That second answer is the kind of operational specificity the Vault needs. The first answer is what a chatbot would say. Tier 1 patterns close the gap.

What it requires: a vocabulary list and a small library of pushback prompts mapped to it. No machine learning. No corpus of past clients. Ships with v0 of the Encoder.

Tier 2 · Builds after ~20 engagements
Failure shapes.

Statistical patterns in how brands fail the 25-point rubric. Real observations across encoded brands, not opinions. Examples of the shape:

  • Brands that describe their voice as "professional yet approachable" score below 12 of 25 on specificity, 84% of the time
  • Brands that list more than five values average 8 of 25 on enforceability
  • B2B brands that fail to define a voice difference between sales and onboarding generate three times the drift signal in the Monitor
  • Consumer brands with a "founder origin story" in their About page have stronger voice scores than those without, but only when the founder is still active

These are not strategic moves. They are diagnostic. They let the Encoder warn the customer mid-session: "Brands that answer this the way you just did tend to fail the next phase. Want to try again?"

What it requires: at least 20 completed encodings across at least three categories. Statistical signal kicks in around that point. Until then, Tier 2 is empty and the Encoder runs on Tier 1 alone. That is fine — Tier 1 is already differentiated.

Tier 3 · The long game (50+ engagements)
Strategic moves.

Patterns in how successful brands solve specific problems. The Encoder suggests moves, not just flags failures. Examples of the shape:

  • "Fintech brands facing regulator scrutiny tend to over-index on trust signals, which weakens distinctiveness. The brands that maintained voice did one of two things: X or Y."
  • "CPG brands launching a premium tier without a category history tend to fail the claims rigor test. The pattern that worked was Z."
  • "B2B SaaS brands that grew through PLG had a measurable voice difference between developer-facing and buyer-facing content. Brands that did not enforce this distinction had higher churn signal in the Monitor."

This is what no solo strategist has access to, even with decades of experience. One person can have seen 30 fintech rebrandings, maximum. The Encoded Brain has seen all of them, in structured form, with outcomes attached.

What it requires: 50+ completed engagements minimum. Real category diversity. Honest scoring (the rubric does most of this for us). A pattern only enters Tier 3 after observation across at least three engagements with distinct categories, per the bright-line rule.

Why this beats a solo strategist.

A great strategist makes a great brief once. The Brain makes one for every brand we have ever touched, every day. After 200 sessions, the Encoder pushes back on patterns we have seen fail before, suggests strategic moves we have seen succeed, and warns about voice modulation gaps we have measured in the Monitor. No human strategist alive has that pattern library. They cannot. It is not a competence question, it is a context-window question.

What this is worth paying for.

Tier 1 patterns alone justify $99-$499 self-serve. Most founders do not know they have been hiding behind "authentic" until something pushes back. That experience converts.

Tier 2 patterns justify the enterprise gap. At $25K-$100K, the strategist in the room is supported by failure-shape diagnostics no other practice has. The diagnostics are the leverage.

Tier 3 patterns are the long-term moat. They are also the reason an acquirer pays a multiple of revenue. Notion's database. Bloomberg's terminal. Encoded Brands' Brain. The corpus is the company.

What I want to discuss with you.

BRIEF 02

How the Vault bridges to every AI app.

Your note: "The Vault is a great idea to keep people engaged and drive passive revenue. How do we make the bridge from vault to all the AI apps feel easy/seamless?" Right question. Here is the full picture.

The Vault is only useful if integrating it to the customer's actual agent stack is genuinely easy. For most surfaces, it already is. For the harder ones, we ship documentation and the enterprise tier includes hands-on integration support. The customer-facing promise: configure once. Every agent stays on-brand forever.

Figure 01 · How agents reach the vault the Vault hosted MCP · authenticated vault.encodedbrands.com/[brand-id] MCP-native tools Claude, ChatGPT, Cursor Custom GPTs & Claude Projects system prompt Marketing tools Canva, Adobe, ad-tech partners CX & sales agents Intercom, Decagon, Sierra, Salesforce Custom internal your engineers build ↑ five integration paths ↑
Figure 01. Five paths from agent to vault. Green paths are easy (configure in minutes). Amber paths are medium (an afternoon of engineering on the customer side, or we help). Coral path is enterprise (we partner with their dev team).

The five paths, ranked by effort.

Surface
How it works
Effort
MCP-native toolsClaude, ChatGPT Enterprise, Cursor
Customer goes to Settings, adds an MCP server, pastes the vault URL. The agent now consults brand context on every relevant query. As easy as adding a Slack integration. We provide the URL and one paragraph of instructions.
5 min
Custom GPTsand Claude Projects
Customer puts the vault URL in the system prompt of their custom GPT or Claude Project. Three lines of text we provide. Their internal prompt now includes "consult brand context at vault.encodedbrands.com/[brand-id] before generating."
10 min
Marketing toolsCanva, Adobe, ad-tech partners
These tools are building agentic infrastructure that reads brand identity from public endpoints. Where they expect a brand.json, we publish one. Where they want depth, the vault serves it through the same pointer. The integration is automatic for anything reading the ad-tech protocols. This is where Skin meets Soul.
automatic
CX & sales agentsIntercom Fin, Decagon, Sierra, Salesforce
These platforms do not have MCP support yet. Customer's CX or RevOps team adds vault content to the agent's system prompt or knowledge base. We ship a configuration guide and snippet library. Two-to-four-hour task on customer side. At enterprise tier, we configure it with their team.
2-4 hrs
Custom internal agentsenterprise dev teams
Internal tools built by the customer's engineering team. They write the integration themselves. We provide developer docs, a reference implementation, and the MCP endpoint specification. This is the longest tail and where the largest enterprise customers actually live.
enterprise

What the customer experience actually looks like.

At self-serve tier ($49-$199/month Vault), the customer receives a welcome email with their vault URL and a one-page integration playbook covering the top five surfaces. Most customers will integrate Claude, ChatGPT, and their custom GPT in under 30 minutes. They do not need an account manager. They do not need a call.

At enterprise tier ($2K-$5K/month Vault), the customer gets an onboarding call where we map their actual agent stack. We write the integration prompts for their specific tools. We test with their agents. We certify the integrations and document them for their team. The Monitor watches actual output afterward and confirms the configuration held.

The architectural decision that makes this seamless.

The Vault is a single MCP endpoint per brand. Every integration path above points at the same URL. The agent authenticates, the vault returns the right depth of context for that agent's permission level, the agent uses it.

This is the unlock. The customer does not maintain N different brand context files for N different surfaces. They maintain one vault. We host it. We version it. When the customer updates their brand context (new voice rules, new claims, new audience), every agent reads the update on the next call. No re-deployment. No re-distribution. No emails to ten team leads asking them to update their prompts.

Configure once. Every agent stays on-brand forever.

What I want to discuss with you.