Every AI Tool And Every Employee, Running On The Same Decided Truth

No — and this is the most common misread. A brand guide describes your voice in words like "confident" and "approachable," which a human can interpret and an AI can't. The Foundation Five is written as decided, bounded rules an AI tool can actually apply: which claims are safe to ship, which need sign-off, which sentence patterns are yours, which are banned. It's built to be used by machines and people at once, not read once and filed.

Most positioning work produces a document, not a decision. If the room can't agree, the report just records the disagreement more elegantly. The two-day workshop in week three is built to force a ruling on every open question — not summarize the debate, but resolve it. And the last two weeks are dedicated to rollout: your team trained on it, an SOP for connecting their tools to it. Nothing ships to a drawer.

Tools will get better at storing and retrieving what you give them. They can't decide who you refuse to serve, what you'd never say, or how your products relate to each other — that's judgment, not infrastructure. The Foundation Five is deliberately tool-agnostic: it works in Claude, Copilot, or whatever comes next, because it's not built on any platform. If your company later invests in a knowledge system or RAG stack, the Foundation Five is exactly what feeds it.

Partially, and we'll tell you exactly where the line is. The sprint forces every decision that has a decider. If your business genuinely lacks a category, or your leadership is split in ways deeper than messaging, we won't manufacture consensus that doesn't exist. What you'll get instead is a precise diagnosis of what's unresolved and what it's costing you — which is usually the more valuable outcome anyway.

Faster versions exist, and they're the reason most positioning work doesn't hold. Two weeks is enough to gather material and run the workshop. It is not enough to codify the rulings into working assets, install them in your tools, and get your team actually using them — the step almost everyone skips. Eight weeks is the minimum to end with something adopted, not just documented.

Agencies typically produce creative output — a new logo, a new tagline, a new deck. This produces decisions: the underlying rulings that every creative output and every AI workflow should already agree on. You could hire an agency after this and get sharper creative work, because the hard questions would already be settled. Most companies do it in the wrong order.

The person with actual authority to make the call — founder, CEO, or whoever holds final say — for both days. This is a firm condition, not a preference. Workshops without the decider present produce the same unresolved debates you already have; the whole value of the sprint is a room that can commit.

Every asset ships with a named owner and an update protocol, so someone is accountable for keeping it current as your pricing, positioning, or team changes. Companies that skip this step watch the asset go stale within a quarter. It's built into the deliverable, not an upsell afterward.

It shortens weeks one and two. Existing material gets audited against the thirty questions in the extract phase, so you're not paying to redocument what's already solid. But most companies find their existing documents disagree with each other in ways nobody had noticed — which is exactly what the workshop resolves.

The clearest signal is qualitative before it's quantitative: your team stops asking you what the company's stance is on X, and AI output across sales, marketing, and support starts sounding like one company instead of three. We also set up the Foundation Five to be checked against — new hires, new AI workflows, new content all get measured against whether they match it, which is not possible without a decided version to measure against.

Yes. Everything extracted in interviews and the workshop is used solely to build your Foundation Five. If a documented, anonymized version of your engagement is used as a case study, that's a separate written agreement — never assumed, and never without your sign-off on exactly what's shared.

No — in fact, some of the clearest wins come from companies just starting. If your team already uses AI without a foundation, this fixes an inconsistency you can already see. If you're about to start, this means you never build the inconsistency in the first place, which is the cheaper path.