Marketing Foundation: master the message and voice everything inherits

Your team already has the messaging-framework and brand-voice playbooks — the worked recipes for building each document, step by step. This module is the layer above the recipe. It’s where you master the two files every other piece of marketing inherits, build them for your own brand, and prove — against a real rubric — that you can.

It’s Module 1 of the certifiable Marketing track, and it’s the one we leave open. Read it, do the assignment, and you’ll know exactly what the depth is worth before you put a team through the rest.

Everything your marketing produces — every campaign, landing page, deck, nurture, and rep talk track — is a withdrawal from two accounts: what you say and how you say it. Most teams never fund those accounts, so every withdrawal is a guess. The foundation is the hour where you fund them once, and it’s the highest-leverage hour in the whole track.

Why the foundation is the highest-leverage hour you’ll spend

Enterprise marketing fragments at the message. Sales pitches one thing, the website says another, the deck a third, and a single buyer hears three different companies. The same thing happens with voice — every writer brings their own, so the brand sounds like five people because it is.

Two documents fix both. A messaging-framework.md decides what you say — positioning, value pillars with proof, per-persona angles, objection answers. A brand-voice.md decides how you say it — tone, rhythm, the words you use and avoid. Build them once and every later task inherits them: you feed both into a content job and the draft comes back on-message and on-voice instead of off in a new direction.

That’s why this is Module 1. Skip it and Claude just helps you produce off-message, off-voice work faster — which is worse, not better. Fund the two accounts first and everything downstream gets sharper for free.

Mastering the message — the judgment the recipe can’t teach

The playbook gives you the steps. Mastery is the judgment inside the steps — the four calls that separate a framework that holds from one that sounds fine and means nothing.

• Proof, or it isn’t a pillar. A value pillar with no evidence behind it is a wish, and a wish is a liability the moment a rep repeats it to a skeptical buyer. For every pillar, name the single hardest proof point you can stand behind — a metric, a named outcome, a certification — and flag the ones where the proof is thin. The flagged ones are the work; fix them or cut them here, not in front of a prospect.
• Differentiation has to survive one search. “We’re the easy, powerful, trusted option” differentiates you from nobody. A real differentiator is one a buyer can’t immediately disprove and a competitor can’t equally claim. If it doesn’t survive thirty seconds of a prospect Googling, it’s a tagline, not a position.
• Keep what and how apart. The single most common mistake is collapsing message into voice — one mushy “brand doc” that does neither job. Message governs substance; voice governs tone. Keep two files so each does one thing well, and so you can feed both into a task without one drowning the other.
• One owner, or it drifts. The whole value of the framework is that it’s a single source of truth. If everyone can edit it, it splinters back into three companies’ worth of messages within a quarter. Name one owner — usually product marketing — and treat changes as reviewed updates with a version bump.

Mastering the voice — a document Claude can actually use

Here’s the test most brand-voice docs fail: hand it to Claude with a flat draft and ask for a rewrite “in our voice.” If what comes back is recognizably yours, the doc works. If it comes back generic, your doc is a list of adjectives — and “professional yet approachable, bold but trustworthy” tells Claude (and a new writer) exactly nothing.

A voice document Claude can use is specific and exampled, not adjectival:

• Do/don’t pairs, not descriptors — “use plain verbs, not ‘leverage’ and ‘utilize’”; “contractions yes, exclamation marks no.”
• Real before/after examples — the same sentence written off-voice and on-voice, so the rule has a shape.
• Words we use / words we avoid — a short, opinionated lexicon. This single line does more work than a page of tone description.

Build it from copy you’re genuinely proud of, not from how you wish you sounded. The brand-voice playbook walks the extraction; mastery is knowing that the examples are the document and the adjectives are filler.

The Arabic foundation — the part nobody else teaches

For a MENA team this is not a translation step bolted on at the end. It’s a parallel foundation, and getting it right is the difference between a brand that reads native and one that reads like a translated brochure. The rule is adapt, don’t translate — and it has four edges most teams miss:

• Two voice docs, authored — not one translated. Arabic carries its own register, rhythm, and formality. Build a brand-voice-ar.md from Arabic copy you’re proud of, deciding deliberately where you sit between Modern Standard Arabic and a lighter Gulf register for your audience. Translating the English rules and hoping produces copy that’s technically correct and emotionally foreign.
• Localize the proof, not just the words. The customer references, the objections, and even which value pillar leads can differ in the Gulf market — procurement norms, who actually decides, and what earns trust are not the same. Re-point the angles; don’t just swap the language.
• One message, two expressions. The messaging house can be shared — the same positioning and pillars — but the per-persona angles and objection answers often need a Gulf-native version, not a mirror of the English.
• Same gate, both languages. Arabic copy clears the same brand and legal review — and regional compliance — as the English. The failure mode is letting the second language skip sign-off because nobody on the approval chain reads it. Find someone who does.

Done this way, Arabic is a first-class peer of English in your foundation. In this region that isn’t a nicety — it’s the credibility line.

Your assignment

Build the two foundation documents for one brand — your own (recommended: the output is a real asset your team keeps) or the sample brand Mizan, a GCC small-business bookkeeping tool used throughout this track. Open the folder with your raw inputs in Claude Desktop, approve each read in the “Ask permissions” prompt, and work in the chat — no terminal needed.

Module 1 deliverable — the foundation

1. messaging-framework.md  (one page)
   - a positioning statement in the standard shape
   - one core promise, one plain sentence
   - 3–4 value pillars, each with its single hardest proof point
   - per-persona angles for 2–3 real personas
   - an objection-handling table: the 6 hardest pushbacks, honest answers
   - a one-line "words we use / words we avoid"

2. brand-voice.md  (one page)
   - 4–6 tone rules as do/don't pairs
   - 2–3 real before/after rewrites
   - a words-we-use / words-we-avoid lexicon
   - an Arabic voice note: where you sit on the MSA↔Gulf register, and why

Bilingual teams: add brand-voice-ar.md, authored — not translated.

The Foundation toolkit gives you a fill-in template for each of these and the prompts that build them, so you’re filling in structure, not staring at a blank page.

How it’s graded — the rubric

This is the part the free playbook doesn’t have, and the part that makes the credential mean something. Your two files are scored against five criteria. Each is meets / nearly / not yet — and “nearly” on any one is a revise, not a pass.

Foundation rubric

1. Positioning is sharp        The promise is one specific sentence a stranger
                               could repeat. Not a category, not a vibe.
2. Every pillar has proof      No pillar rests on an adjective. Each names a
                               real metric, outcome, or certification — or it
                               was cut. Thin proof is flagged, not buried.
3. The voice doc is usable     Specific enough that Claude rewrites a draft
                               recognizably into your voice. Examples present,
                               not just descriptors.
4. Arabic register is right    The Arabic voice is authored, not translated;
                               the register fits the audience; the proof is
                               localized, not just the words. (Bilingual teams.)
5. It fits on a page           Each document is one to two pages. A framework
                               nobody can hold in their head doesn't get used.

The discipline is deliberately what a senior marketer would demand: a foundation that’s vague, unproven, or unusable fails quietly in every downstream task, so it has to be caught here.

The bar, shown — a worked model answer (Mizan)

You don’t have to guess what “meets” looks like. Here’s a passing excerpt for the sample brand — your own doesn’t need to look like this, it needs to clear the same bar.

messaging-framework.md — Mizan (excerpt)

Positioning
  For GCC small-business owners who dread the books, Mizan is the
  bookkeeping tool that closes your month in an afternoon — unlike
  generic accounting suites built for accountants, Mizan is built for
  the owner who isn't one.

Core promise
  Your books, done and trustworthy, without hiring an accountant.

Pillar 2 — "Trustworthy, not just fast"
  Benefit: numbers you can hand to a bank or auditor without a redo.
  Capability: every figure traces to its source document.
  Proof: 9,000+ GCC businesses; VAT-return-ready exports accepted by
         the FTA without amendment in our 2025 cohort.   ← real, checkable

Persona angle — the non-financial founder
  Lead with relief, not features: "you'll understand your own numbers."
  Top objection: "I already have an accountant." →
  "Keep them — Mizan does the daily books so you only pay them for advice,
   not data entry."

Words we use: books, close the month, owner, trustworthy.
Words we avoid: GL, reconciliation, ledger, leverage, solution.

brand-voice.md — Mizan (excerpt)

Tone rules
  - Plain over clever. "Close your month," never "streamline your
    financial close workflow."
  - Calm, not hype. No exclamation marks; the product is the relief.
  - You/your, always. We talk to one owner, not a market.

Before / after
  ✗ "Mizan empowers SMBs to leverage automated reconciliation."
  ✓ "Mizan matches your payments to your invoices, so you don't."

Arabic voice note
  Register: lightly formal MSA with Gulf-natural phrasing — not the
  stiff fus'ha of a bank letter, not slang. Address the owner with
  respectful directness (حضرتك tone without the word). Numbers Western,
  currency in context. Authored from Arabic copy we're proud of, not
  translated from the English above.

What you’ve proven — and what’s next

Clear the rubric and you’ve done something the free path can’t certify: you’ve built a real, professional-grade foundation and demonstrated the judgment behind it. That’s the Foundation stage of “Certified Marketing with Claude.”

From here the track turns the foundation into a working operation, each module assessed the same way:

• Module 2 — the content engine: the repeatable pipeline that turns these two files into briefed, on-brand content on a calendar.
• Module 3 — lifecycle & stories, Module 4 — the launch, Module 5 — measure & iterate, then the capstone — a complete campaign for one brand, end to end, graded into the certificate.

First, make what you built reusable. Grab the Foundation toolkit — the marketing CLAUDE.md and the two templates that turn the documents you just wrote into files your whole team installs and inherits. And if you’re rolling this across a team, the operating guide is the safety and sign-off layer that goes underneath all of it.