Brand
Strategy.

Why most "brand strategy" docs are moodboards

If your current brand-strategy document is mostly typography references, colour palettes, and "we are bold yet approachable", it is not a strategy — it is a visual brief masquerading as one. A strategy resolves future questions before they get asked. A moodboard captures vibes you already had.

The test for whether something is a strategy: it should be able to answer a future question the team has not asked yet. "Should our new pricing page sound like our launch copy or like our support docs?" "Is this competitor announcement worth a response?" "Does this partnership fit who we are?" If the document does not resolve those, it is decoration.

Five pillars, written down, owned by humans, and refreshed once a year is what produces a strategy that actually does work. The rest of this page is how to build it — in five days, by people who already have day jobs.

The five pillars

1. Audience — who is this for, and in their words

Three customers, three prospects who said no. One page each capturing what they were trying to do when they found you, the alternative they considered, and the words they used when they described the problem. The framework anchors to those words. Teams that anchor to internal vocabulary end up with positioning that customers cannot recognise as theirs.

2. Positioning — one sentence, hostile-reviewer-proof

One sentence: "[product] is the [category] for [audience] who [trigger condition], because [insight a competitor cannot copy]." The hostile-reviewer test: read the sentence to a smart outsider who does not work in your category. If they shrug, your positioning is genre-default and the rest of the framework will rest on sand. If they push back with specifics, you have something to defend.

3. Voice — how the brand sounds, with examples

Voice is not adjectives. "Confident, warm, professional" is the voice of every B2B SaaS that ever shipped. Voice is documented with examples — three sample sentences for the marketing surface, three for product UI, three for support, three for error states. Plus a vocabulary list: words to use, words to avoid, and the reasoning for both.

4. Visual system — direction first, system later

The framework's job is to lock the direction the visual system runs in, not to ship the system itself. A two-direction brief — each with a wordmark, palette, type pairing, and one application surface — is enough to lock the strategic decision. The full system expansion happens in a separate engagement after the framework signs off.

5. Behaviour — how the brand acts when no one is watching

The pillar most teams skip and the one that produces the highest leverage when written. How does the brand handle a critical bug? A competitor launching a feature you do not have? A customer asking for a refund? An internal disagreement about a campaign? Behaviour rules answer these in 10 minutes the next time, and they prevent the brand from quietly drifting into the founder's mood-of-the-day.

Running the framework in five days

One day per pillar, in this order — because each pillar depends on the previous one. Re-ordering produces frameworks that look complete but contradict themselves.

1. 01 Day 1 — Audience. Interview three customers and three prospects who churned or said no. Build a one-page audience definition: who they are, what they were trying to do when they found you, and the words they use when they describe their problem. The framework anchors to those words, not the team's preferred vocabulary.
2. 02 Day 2 — Positioning. Workshop with the founder + marketing lead. Output: a one-sentence positioning statement that survives being read by a hostile outsider. Format: '[product] is the [category] for [audience] who [trigger condition], because [insight that the competitor cannot copy]'. If the sentence does not survive, the framework stops here until it does.
3. 03 Day 3 — Voice. Capture how the brand sounds in product copy, marketing, support, and error states. Document with examples, not adjectives. Output: a one-pager with the vocabulary list (use / do not use), three sample sentences per surface, and the test phrase that distinguishes the brand voice from the founder's personal voice.
4. 04 Day 4 — Visual system. Two-direction visual brief. Each direction has a wordmark, palette, type pairing, and one application surface. The team picks one in week two, then the chosen direction expands into the full system in a separate engagement. The framework day delivers direction, not a finished system.
5. 05 Day 5 — Behaviour. Write the behaviour rules: how the brand shows up in customer support, how it handles error states, how it announces product launches, how it apologises, how it celebrates wins. These are the rules that keep the brand consistent when no one is watching. Output: a one-page behaviour playbook the team can read in 10 minutes.

If running this internally feels like overhead, the Brand Identity for SaaS engagement bundles all five days with the studio in the room. The Brand for SaaS pillar covers how the framework feeds into the broader engagement.

A 30-minute self-check

Five questions. Honest answers. If you cannot answer at least three of them without consulting a slide deck, the framework is not in your team's head — it is in a Notion document no one reads.

1. Who is your audience, in their words? If you answer in your words instead of theirs, the audience pillar is unfinished.
2. What is your one-sentence positioning? If you cannot recite it, neither can the team.
3. What three words does your brand never use? If you cannot name them, the voice pillar is decoration.
4. What does the brand look like in a context you have not yet shipped — say, a billboard, or an in-product onboarding step? If you cannot picture it, the visual system has not been internalised.
5. How would the brand respond to a customer asking for a refund? If you have to make it up on the spot, behaviour rules are missing.

A free Loom audit on your current brand against this checklist is at /free-audit/. Send a URL, get a 15-min walkthrough, no follow-up sequence.

Common mistakes

• Running visual before positioning. The studio shows a moodboard, the team falls in love with a palette, positioning gets contorted to fit. The framework is now upside-down and every future surface fights it.
• Treating voice as adjectives. "We are bold yet approachable" survives no committee meeting. Voice has to be example-driven or it does not exist.
• Skipping behaviour because "we are too small for it". Small teams are exactly when behaviour rules pay off — they prevent the brand from being whatever the founder felt this week.
• Treating the framework as a one-time exercise. Strategy decays. Yearly refresh on the audience and positioning pillars, every-two-years refresh on voice and behaviour.
• Hiring a strategy agency for the deck and the founder for the decisions. If the founder makes the decisions, the agency's "strategy" output is documentation, not strategy — and you paid agency rates for documentation.

Doing it yourself vs hiring it out

Three options, in increasing order of cost and likelihood of actually finishing:

• Solo founder runs it. Cheapest, hardest. Bias risk on positioning. Works if the founder has run brand work before, or has an outside reader for the positioning sentence.
• Founder + marketing lead run it together. Most common. Works if those two can sit in a room for five days and not have other fires to fight. Failure mode: the sprint becomes a side-project that drags across six weeks.
• Outside studio facilitates the five days. Most likely to finish. Studio brings the framework, the founder + team supply the input. Engagement length: 5 in-room days plus 1 week of writing-up. Funky Rabbit pricing for this is bundled with the Identity Sprint or Brand Suite — not sold standalone.