Chapter 2 of 3  ·  Build Your Brand OS
A Swim Club Series: From Experiments to System

Build the Foundation for Your AI-Ready Marketing Machine

How to build a Brand OS, run a team diagnostic, and turn your marketing function into something that actually scales — with or without more headcount.

April 2026 Edition
Build Your Brand OS ebook cover
What this covers

The gaps in your marketing system aren’t new. AI doesn’t create them. It just removes the hiding places. This guide shows you exactly where yours are and what to do about them.

This is the tactical companion to From AI Fantasy to Real Moats. Where that ebook makes the strategic case for Brand OS, this one shows you how to build it. It uses Swim Club as the demo throughout — every section walks you through real examples, then gives you a blank template to build your own.

  • Find your complexity type and understand what Brand OS work looks like from your starting point
  • Run the AI Readiness Quiz to get a solo read on where your team stands
  • Run the full team diagnostic — IC survey, leadership alignment, signal flow mapping — to find where the gaps actually are
  • Build a Life Story — the foundational document that makes everything else in the OS feel inevitable
  • Walk through all seven Brand OS files with Swim Club’s real content as the example
  • Understand the workflow ladder and choose your first automation
  • Know exactly what to do in your first six weeks and how to measure whether it’s working
Coming soon
Get notified about the free video series launching in May 2026
Enter your email and you’ll be the first to know when it drops.
About me
Anne-Marie Goulet

Anne-Marie Goulet

CMO, GTM Leader, and Founder @ Swim Club

I left the CMO seat to get back to the craft. Not to manage people doing the work, but to do it myself — building, testing, getting first-hand experience with AI in a way most people at my level have moved away from. Back in the water.

Fifteen years across Salesforce, Shopify, WordPress Enterprise, and Tulip Retail. In every environment — growth stage, turnaround, enterprise — the challenge was almost always the same underneath. Not the wrong people. Not the wrong tools. A system that wasn’t coherent, held together by human glue that doesn’t scale. I don’t come in with a playbook. I come in with questions, because the answer is usually already in the room.

The reason behind Swim Club: I’ve accumulated more lessons than I can carry alone, and I’d rather share them than watch someone else learn the hard way unnecessarily. That’s what Swim Club is.

— AMG

00 / The Problem

Agents can’t be the human glue.

Here’s what most marketing leaders miss about AI: it surfaces all the gaps you used to paper over. Gaps in brand clarity, customer signal, process, and governance that were tolerable when humans were the connective tissue become showstoppers the moment you try to automate.

Historically, the human glue was you. You knew which ICP to reference for which deal. You knew which tone to use for which audience. You knew that the “official” messaging deck was six months out of date and where the real version lived. You held the hidden context and it held the system together.

AI doesn’t know any of that. It will confidently use the wrong ICP, produce off-brand copy, and reproduce the six-month-old narrative — unless you give it a system it can actually use. That system is Brand OS.

Every wave of new technology tempted marketers to optimise the channel and forget the human. AI is the same temptation at higher stakes.

This isn’t a tools problem. The CMO accountability list keeps growing — growth, brand, pipeline, product narrative, customer insight, and now an “AI strategy” on top. Tools everywhere. Misalignment everywhere. Growth that feels like an accident rather than a capability.

The fix isn’t another tool. It’s a coherent system. And that starts with documenting what’s currently in your head — before it has to live in an agent instead.

Step 0 — Where You Are Now
Brand knowledge lives in people’s heads
ICP undocumented. Voice inconsistent. Four versions of the pitch. You are the connective tissue.
Step 1 — Brand OS Built
Seven files. One source of truth.
Life Story, ICP, Voice, Positioning, Manifesto, Design — documented, maintained, version-controlled.
Step 2 — Workflows on Top
AI that knows the brand
Assistants and workflows load the Brand OS. Output is coherent. You stop rewriting everything.
Step 3 — The Marketing Machine
Scale without adding headcount
Custom agents handle high-frequency, brand-dependent work. The system runs. You lead.
01 / Know the Game Board

Your complexity type shapes every move that follows.

Before you build anything — before you pick a workflow, run a survey, or open a Brand OS template — you need to know what you’re working with. The tactics that work for a founder running solo marketing look nothing like what works for a CMO managing a distributed team across multiple products and markets. Complexity isn’t just about team size. It’s three axes. And your position on each one changes not just what you build, but which problem to solve first.

Portfolio Depth

  • Single product or service
  • Multi-product or solution set
  • Platform or ecosystem

Market Breadth

  • One segment or geography
  • Multiple ICPs or regions
  • Global, multiple buying committees

Org Structure

  • Centralised function
  • Embedded or distributed
  • Matrix

The combination of these three axes produces your complexity type and determines your starting moves. These aren’t stages you graduate from. A late-stage company can land in the Solo Operator profile if the CMO is brand-new. A Series A startup can be a Complex Org if they’re already selling in four markets with two products.

The Solo Operator
Single product · One market · Flat structure

Everything lives in one person’s head.

The story, the ICP, the “what good looks like” — it all lives in one person’s head. Nothing is documented. Every time someone new joins, you have to re-explain everything from scratch. Nothing survives the founder’s absence. And nothing scales — human or AI — without a written system.

“I know this stuff cold. I just haven’t written it down yet.”
Brand OS goal: Get it documented for the first time. Start with Life Story + ICP. That’s enough to unlock everything else.
The Growing Pains
Growing team · Multiple voices · No governing source

The story existed once. Now it’s five versions.

The team has grown. Multiple people now touch brand decisions — sales, marketing, product, leadership. Nobody agreed on a single version of the pitch, the ICP, or what “on-brand” means. You don’t have a brand problem. You have a coordination problem.

“Sales tells the product story their way. Product tells it theirs. I spend half my time reconciling both.”
Brand OS goal: One system of record. Not a rebrand — a consolidation. Build the Brand OS folder and make it the thing everyone points to.
The Complex Org
Multiple products · Multiple markets · Matrix structure

The knowledge exists. It just doesn’t flow.

You have all the information somewhere — it’s just not connected. Individual contributors run their own context because there’s no shared one. Customer signal lives in four tools and never reaches marketing. Human glue has been holding the system together. This is an infrastructure problem, not just a documentation problem.

“Our Canadian team runs a different pitch than our US team. We ran a brand workshop two years ago. Nobody’s opened the output since.”
Brand OS goal: Map the signal flow. Build the canonical source in a governed, maintained folder. Pick the first 1–2 workflows to run on top of it.

These categories are directional and illustrative — not rigid buckets. Most teams sit across two of them depending on the team, the channel, and the moment.

Know your type before you start. The work is different for each archetype and the most common mistake is treating documentation as the answer when you actually have a governance problem, or building more on top of a system nobody uses.

02 / The AI Readiness Assessment

Run this with your team before you build anything.

Every failed AI implementation has the same root cause: teams skipped the diagnostic. They chose the tool before they understood the problem. They automated a broken process instead of fixing it first.

This condensed quiz gives you a quick read on your team’s readiness across six dimensions. It takes about three minutes. The individual signals matter less than the aggregate, and the gaps between IC and leadership perceptions are where the real work lives.

Rate your agreement on a scale of 1–5, where 1 = strongly disagree and 5 = strongly agree. Submit to get your readiness breakdown.

Connectivity
I could describe the journey a typical piece of content takes — from brief to live to measured and expect my team to describe the same process.
Strongly disagree Strongly agree
Connectivity
If my highest-performing team member left next month, the team could still operate without a major reset. The process lives in the system, not in that person.
Strongly disagree Strongly agree
Clarity
I could ask five people on my team — including someone in sales — “who is our priority customer?” and get the same answer from all of them.
Strongly disagree Strongly agree
Clarity
When content comes to me for approval, my feedback is mostly about strategy or substance — not about whether it sounds like us or matches the brand.
Strongly disagree Strongly agree
Signal Flow
Customer signal from calls, support, and NPS is regularly reaching the people writing content and building campaigns — without me being the one to route it.
Strongly disagree Strongly agree
Technical Readiness
If I asked for a report on how our content is performing against our ICP — broken down by segment — I’d get a reliable answer within 24 hours.
Strongly disagree Strongly agree
Capability
My team is using AI for real, repeatable work — not just demos and experiments. I can point to at least one workflow that runs on AI today and actually produces output we ship.
Strongly disagree Strongly agree
05 / Run the Diagnostic

The gaps between IC and leadership are where the work lives.

The in-browser quiz above gives you a solo read. The real diagnostic runs across your whole team and the signal you’re looking for isn’t just the low scores. It’s the divergence between what ICs experience and what leadership believes to be true.

Run this before you propose any tooling changes. The results tell you exactly where to start and more importantly, where not to start.

1

The IC Survey

5 sections, 24 questions, ~15–20 minutes. Distributed anonymously to all marketing ICs. Covers: role context, how work gets done, brand clarity and customer signal, tools and AI usage, and appetite for change.

This is the full version of the readiness quiz above — with open text questions that reveal what the Likert scale can’t. Run it before any kickoff conversation about workflows or AI tooling.

Output

AI Readiness Radar across six dimensions. Bottleneck map. Friction inventory.

2

The Leadership Survey

A shorter companion survey for the CMO, CRO, and other senior stakeholders. Covers conviction and sponsorship, definition of success, timeline and budget reality, and their own perception of the six readiness dimensions.

The point isn’t to validate leadership — it’s to surface where their perception diverges from what ICs reported. Those gaps are your highest-priority intervention points.

Output

Leadership alignment score. Perception gap map. Readout agenda.

3

Signal Flow Mapping

The signal inventory: source, owner, quality, access, API availability. For each customer signal source in your org — Gong calls, support tickets, NPS, deal lost analysis, community — map whether it actually reaches the people making creative and messaging decisions.

Most teams discover they have more signal than they thought. The problem is routing. Signal that lives in one tool and never reaches marketing is the same as having no signal at all.

Output

Signal map. Routing gaps. Ritual gaps (what you have vs. what you need).

The full IC Survey is available as a Google Form (make a copy) — duplicate it and run it with your team.

03 / Life Story

The story that makes your brand make sense.

Most companies have an About Us. Few have a Life Story. The difference is that an About Us is written for external audiences — polished, on-message, optimised for first impressions. A Life Story is written for the company itself. It answers the question: why does this company exist, in the actual language of the people who built it?

Personal or company — which one do you build?

Founder or solo practitioner: your personal story often IS the company story. Your credibility, your point of view, and your reason for existing are inseparable. Build the personal Life Story first — it will feed directly into ICP and voice.

CMO or marketing leader at an established company: you’re likely building the company’s Life Story, not your own. Even if you’re new to the role, the founding moment exists — you’re just excavating it. Interview the founder. Look for the original problem the business was created to solve. The story is there; it usually just hasn’t been written down yet.

Fractional CMO or consultant: you may need both — your own Life Story (why you do this work) for your personal brand, and the ability to build your clients’ Life Stories as part of your practice.

This sits early in your Brand OS — not because it’s the most tactical, but because it’s what makes ICP, voice, and positioning hang together instead of feeling assembled from parts. When your ICP is right and your messaging still feels hollow, the answer is almost always a missing or underdeveloped Life Story.

The Life Story is what separates a positioning statement from a category claim.
Individual-to-company translation
Individual Life Story Company Life Story
The formative experienceThe founding moment — what the founder saw or felt that others didn’t
The thing you couldn’t un-seeThe unsolvable problem — what made this company necessary
The belief that formedThe core conviction — the one true thing the company is built on
The mission that followsThe reason you exist — not what you do, but what you’re compelled to build
The four questions to answer
  • 1
    What was the founding moment?

    Not the company story you put on your website — the real moment. The thing that was seen or felt that started this. Be specific. Date, place, feeling if possible.

  • 2
    What was the problem you couldn’t un-see?

    The gap in the world that made this company necessary. The thing that, once you saw it, you couldn’t look away from.

  • 3
    What belief formed from that?

    The one conviction that drives every decision. The thing the company believes to be true about how the world should work.

  • 4
    What does that compel you to build?

    Not just a product. A reason for existing. The mission that follows from the belief — not a tagline, but a real answer.

Swim Club brand-os-story.md Life Story — plain language, not website copy
Founding Moment

After years at Salesforce, Shopify, and WordPress Enterprise, I hit a wall. Travelling two weeks a month. Working around the clock in a turnaround environment. My 14-month-old stopped wanting me to put him to sleep. I also kept being the unofficial Dear Abby for marketers in my network — people who couldn’t ask their boss, couldn’t post it on LinkedIn, and were increasingly tired of the LinkedIn varnish. At some point those two things collided and I couldn’t un-see either of them.


The Problem I Couldn’t Un-See

Marketers who were stuck, burned out, or in over their heads and nowhere honest to turn. Leaders who looked the other way. The gap between what was safe to say publicly and what was actually happening. “Where are all the leaders at?” was a question I kept asking. I still don’t have a good answer, but I decided to stop waiting for one.


The Belief That Formed

You can’t phone it in on people leadership. What you permit, you promote. The teams that win aren’t the ones who move fastest — they’re the ones whose leaders did the unsexy upstream work first. And the tools for doing that work better have never been more available — if you’re honest about what they can actually do.


What It Compels Me to Build

Swim Club. A place where marketers get the honest, operator-grade help they can’t get from their boss, their HR team, or LinkedIn. And where founders and marketing leaders can fix what’s actually broken — not just build on top of the dysfunction.

This is brand-os-story.md. It lives in the Brand OS folder alongside ICP, voice, and positioning. Every agent and workflow that touches brand content loads this file.
Now write yours.

Plain language, past tense, written the way you’d tell it in a room. Not on a website. If your team runs on Notion, start a new page and call it brand-os-story.md. If you’re a Google Workspace shop, open a Google Doc. The format doesn’t matter. Getting it out of your head does.

brand-os-story.md — your template. Fill this in first, before you touch anything else in the Brand OS.
Founding Moment
What happened? Be specific — date, place, feeling if possible. What did you see or feel that others around you didn’t?
The Problem You Couldn’t Un-See
What gap in the world made this company necessary? The injustice, absence, or broken thing that stuck and that you couldn’t stop thinking about.
The Belief That Formed
One or two sentences. The thing your company believes to be true about how the world should work. Not a mission statement — a conviction.
What It Compels You to Build
Not a product description. The mission. Why this, why now, why you.
04 / Build Your Brand OS

Seven files. Everything an AI needs to be coherent.

Brand OS is a folder.

Seven markdown files, each with a specific job. Together they contain everything an AI model — or a new team member — needs to produce work that sounds, looks, and argues like your brand.

The files aren’t templates to fill in once and forget. They’re working documents. They get updated when the business changes, when you learn something new about customers, when the competitive landscape shifts. They’re governed, maintained, and loaded into every workflow that touches brand.

Who You’re For

  • brand-os-story.md — Life Story
  • brand-os-icp.md — ICP

How You Sound

  • brand-os-voice.md — Voice
  • brand-os-positioning.md — Positioning
  • brand-os-manifesto.md — Manifesto

How You Look

  • brand-os-design.md — Design System
System Instructions
One file that gives your AI its context before you type a single word.

Every AI tool has a way to load standing instructions — rules, context, and brand knowledge that apply to every session. In Claude it’s called CLAUDE.md. In ChatGPT, Custom Instructions. In Gemini, Project Instructions. Same idea, different name. Write it once. That’s what makes Tier 1 actually reliable at scale.

Swim Club Brand OS Live example — 7 files, one folder
CLAUDE.md — Session Loading File
Auto-load rules
Writing or content → read brand-os-voice.md. HTML or visual assets → read brand-os-design.md. Positioning or website copy → read brand-os-positioning.md.
Memory — who I am
Anne-Marie Goulet. Founder of Swim Club. CMO & GTM leader, 15 years. Salesforce, Shopify, WordPress, Tulip. Left the CMO seat to get back to the craft. I’m a talent capitalist. We’re in this together.
Source of truth — three layers
CLAUDE.md → voice, brand, frameworks, philosophy. Notion HQ → live priorities, content pipeline. Website → published positioning. Canonical when in doubt.
Preferences
Thought partner, not a yes-machine. Analogies when learning. Brevity and directness. British/Canadian spelling. Content reviewed against VoU principles: problem-first, specific, plain language.
CLAUDE.md is the orchestrator. It doesn’t replace the Brand OS files — it tells Claude which ones to load, when, and in what order. The brand knowledge lives in the six files. CLAUDE.md is what makes it load automatically.
brand-os-icp.md — Three Segments
Segment 1: The Founder
Early-stage, building their marketing function. Wants to do it right from the start. Frustrated by generic advice that doesn’t apply to their stage or sector.
Segment 2: The Marketing Leader
VP or CMO at an established org. Inherited a team and a system — not necessarily the one they’d build. Under pressure to modernise and show AI ROI.
The third segment is the Blog Reader — informed, not yet a buyer. The ICP doc keeps all three distinct so content, campaigns, and outreach can be targeted correctly.
brand-os-voice.md — How I Sound

Candid. Direct. Warm. Practical. Swim Club’s voice reads like a senior peer in the room — not a consultant who needs you to need them. The test: read it aloud. Does it sound like a real person?

I say
“Here’s what I’d actually do.” / “This is the part nobody talks about.” / “That’s a real problem — here’s why it happens and how to fix it.”
I don’t say
“Revolutionise your marketing stack.” / “Unlock your potential.” / “In today’s fast-paced landscape…” Jargon. Hedging. Corporate distance.
brand-os-positioning.md — How I Compete

One-liner: Swim Club is where marketing leaders get the honest, operator-grade support they can’t get from their boss, their consultants, or LinkedIn. Four differentiation pillars, each with proof.

Operator, not advisor
15 years in the seat. Salesforce, Shopify, WordPress. I know what it costs to get this wrong.
Fundamentals-first, AI-practical
Brand OS is built on fundamentals. Then I make them machine-readable. In that order, always.
brand-os-manifesto.md — What I Believe

The philosophical layer. The beliefs the Life Story gave birth to — the principles that govern how Swim Club operates.

  • A. You can’t phone it in on people leadership. What you permit, you promote.
  • B. The teams that win aren’t the ones who move fastest — they’re the ones whose leaders did the unsexy upstream work first.
  • C. Candour over comfort. A hard truth delivered with care beats a comfortable answer that costs you six months.
  • D. Fundamentals before tools. Every time. Without exception.
brand-os-design.md — The Visual System

The design file isn’t aesthetic — it’s infrastructure. When an AI generates a visual asset, it loads this file.

Colour Tokens
--coral: #fe486c / --pblue: #9eb5f5 / --blue: #2c59fe / --navy: #000e4b / --light: #fbecfa / --fuchsia: #eb6df0
Typography
EightiesComeback for display/hero/quotes. Tommy Black (900) for H1–H4. Tommy 400 for body. Tommy Bold uppercase for labels.
Design tokens in markdown means any AI with file access can produce on-brand HTML, Figma prompts, or design specs without a brand guide document. The token names are the specification.
06 / The Workflow Ladder

Start generic. Go custom when the job is clear.

Most teams get this backwards. They try to build custom agents before they’ve proven the job is repeatable. The result is a brittle automation that breaks every time something changes and a team that trusts AI less, not more.

The ladder has three rungs. Climb them in order.

Where your peers actually stand
81%
of martech leaders are already piloting AI agents. But 45% say they don’t deliver. The most common reasons: the underlying data isn’t clean, the job wasn’t defined clearly enough, and expectations were set by vendors — not by people who’d done the work.
7%
of enterprises say their data is completely ready for AI. Jumping to Tier 3 before fixing this is the single most common reason AI investments stall and the least discussed.
65%
of CMOs expect AI to dramatically change their role. Only 32% think significant skill changes are needed. Gartner calls this the “AI blind spot.” The odds are good you’re in it.
Sources: Gartner Martech Leader Survey (2025) · Cloudera / Harvard Business Review Analytic Services (2026) · Gartner CMO Survey (2026)
Tier 1 — Assistants
You’re at the keyboard. AI is the co-pilot.

Prompt + Brand OS context → better output

You direct every task. The AI has your Brand OS loaded and produces on-brand, on-voice output. This is where everyone should start. Most teams stop here and that’s fine. Generic assistants with good context handle 80% of marketing AI use cases.

When to move up: when you’re doing the same task 3+ times a week and the prompt is stable.
Tier 2 — Workflows
The process is defined. AI runs it.

Trigger → steps → output, without you in the middle

A defined process with a clear input, stable steps, and a measurable output. Examples: new Gong call → summarise key signals → update ICP doc. New campaign brief → draft 3 subject lines → send for review.

When to move up: when the workflow is stable, high-value, and you want something more brand-aware than a generic tool.
Tier 3 — Agents
The job is strategic. The agent knows the brand.

Custom AI that handles complex, brand-dependent work

A custom agent built for a specific, high-leverage job. Loads your Brand OS. Understands your business logic. Makes decisions, not just transformations. Most teams need one or two agents at most.

What to say no to: strategically ambiguous jobs, politically sensitive decisions, rare or bespoke requests that change every time.

The rule of thumb: start generic. A generic assistant loaded with your Brand OS will outperform a custom agent built on a weak foundation every time. Build the foundation first. Go custom when the job is clear, stable, and demonstrably worth the investment.

Brand OS is the prerequisite. Not the nice-to-have.
07 / Your First 6 Weeks

What you and your team will actually do, and in what order.

The biggest mistake teams make is trying to do everything at once. Brand OS, diagnostic, workflow selection — all in parallel, all urgent, none finished. The six-week structure below is the antidote. It sequences the work so that each phase builds on the last.

Weeks 1–2
Complexity + Readiness Assessment
Identify your complexity type. Distribute the IC Survey. Start mapping signal flow. Draft the Life Story — don’t polish it yet.
Week 2–3
Diagnostic Synthesis
Collate IC Survey results. Run the leadership survey. Build the Readiness Radar. Map the gaps. Identify the highest-priority intervention points.
Weeks 3–4
Brand OS Build
Build the six Brand OS files in order: Story → ICP → Voice → Positioning → Manifesto → Design. Don’t skip steps. Don’t outsource the writing — the thinking is the point.
Week 4–5
Workflow Selection
Apply the prioritisation filter to your workflow candidates. Select 1–2 to build. Load Brand OS into your generic assistant and test it before touching any custom tooling.
Week 5–6
First Workflow Running
Build and test the first workflow. Document what you observe. Measure it against the baseline you established in week one.
Week 6
Leadership Readout
Executive POV. Readiness Radar and perception gap map. Brand OS folder walkthrough. Workflow shortlist. 0–12 month roadmap. This is the deliverable the whole six weeks was building toward.

What you hand to your team at the end of week 6: the Brand OS folder, the Readiness Radar, the workflow shortlist, and the roadmap. That’s a real deliverable — something that exists, is owned, and can be handed to the next person who joins the team without a full knowledge transfer.

08 / Measuring What Changes

Know it’s working before pipeline moves.

Before you design your measurement, get clear on your why. The metrics worth tracking are different depending on what you’re actually trying to achieve.

Behaviour Shifts: Leading Indicators
Move first  ·  visible within weeks
Teams self-serving from Brand OS
82
Fewer brand escalations — people are referencing the files directly, not waiting for approval
First drafts cleared without major rework
78
Quality floor has risen — campaigns moving forward without a full reset
Cross-functional language alignment
70
Sales, marketing, and product using the same terms for the same things
System KPIs: Engine Health
Follow over months  ·  how well the machine is running
ICP alignment across functions
85
Sales, marketing, and product using the same ICP definition
Customer signal reaching marketing
70
Gong calls, support tickets, NPS actually flowing to the team
Brand OS actively referenced and kept current
90
Files are being opened, updated, and used — not abandoned after week one
Commercial Outcomes: Lagging Indicators
Take longest to move  ·  attribution is hardest here
Win rate trend
62
Improving as ICP clarity and message sharpness compounds
Content velocity per person
78
More output per person — Brand OS removing the decision-making overhead
Campaign quality sustained without burnout
72
Brand system handling consistency; team energy goes to strategy and judgment
Each bar shows the illustrative health score on a 0–100 scale. Your starting point will differ — the point is directional movement over time.
The goal isn’t a perfect Brand OS. The goal is a living one — owned, maintained, and actually used.
If you ran the readiness diagnostic at the start of this guide, come back to it in 90 days. The gap you measured then is the baseline. What you track now is the proof.
Anne-Marie Goulet

Ready to build the machine?

Swim Club is where marketing leaders get the honest, operator-grade support they can’t get from their boss, their consultants, or LinkedIn. If you want to build a Brand OS, run a diagnostic, or figure out where to start — come find me.

Whether you’re starting from scratch or inheriting a system that was built for a different company, the path forward is the same: clarity first, then consistency, then compounding. That’s what the Brand OS is for.

Contact me