The launch: orchestrate one moment where everything fires at once

Your team already has the launch-campaign and pr-and-comms playbooks — the worked recipes for running a launch and a comms moment, step by step. This module is the layer above the recipe. It’s where you learn to orchestrate a launch: not to write one, but to run one — a single cross-channel moment where everything you’ve built fires at once, on a clock, in public, and nothing slips.

It’s Module 4 of the certifiable Marketing track, and it’s the module that pulls the others together. By now you’ve built the parts. The foundation (Module 1) decided what you say and how you say it. The content engine (Module 2) made that message repeatable on a calendar. The campaigns (Module 3) turned it into journeys and stories that earn the next step. The launch is where all three go live together, in two languages, on one day — and where the discipline that keeps a launch from slipping turns out to be a different skill from writing any single piece of it.

A launch is the one day every other module gets tested in public — the foundation, the engine, and the campaigns all fire at once, in front of an audience, on a clock. And the thing that slips it is almost never the copy. It’s an unsecured sign-off, a regional gate nobody owned, an Arabic line that went out as a translation. Orchestration is the discipline that fixes that: a runbook with a name and a date on every line, so launch day is execution, not an 11pm act of heroism.

The runbook is the product

The instinct on a launch is to treat the copy as the deliverable and the schedule as an afterthought — a calendar invite, a Slack thread, somebody’s memory. That’s backwards. On a launch, the runbook is the product. It’s the one artifact that holds the whole moment: every asset, the human who owns it, the date and time it goes live, the channel it lands on, and the gate it has to clear first. The blog post, the email, the thread — those are inputs to the runbook, not the thing itself.

• Claude builds the first runbook from the goal. You don’t start from a blank grid. Give Claude the launch goal, the date, and the assets you already have (the campaign suite from Modules 2 and 3), and ask it to lay out the runbook: every asset as a row, with columns for owner, go-live time, channel, and gate. In minutes you have a complete structure to react to instead of a blank page to fill — which is the difference between catching a gap a week out and discovering it live.
• A person owns each line — Claude doesn’t. The runbook’s whole job is to make ownership undeniable. Every row names a human, not a team and not “TBD.” Tell Claude to leave the owner column for you to assign: a launch where Claude invents the owners is a launch nobody actually owns. The blank owner cell is the single most useful thing a runbook surfaces — it’s the task that becomes the 11pm scramble, made visible a week early.
• One moment, not a scatter. The runbook aims everything at a single planned go-live — a deliberate sequence around one moment, not a drift of whenever-it’s-ready posts spread across a week. The sequence is a decision (tease, then the announcement, then the amplification), and the runbook is where you make that decision once instead of improvising it live.

The approval gate is a named step, not a vibe

Here’s what every launch veteran knows and every rookie learns the hard way: at enterprise scale, what slips a launch is almost never the copy. It’s an unsecured sign-off. The legal review that “was happening.” The regional gate nobody owned. The exec who never saw the message. The copy was done days ago; the launch slipped because an approval lived in someone’s head instead of on the runbook.

• Every gate is a row, with an owner and a deadline. Brand, legal, and regional compliance aren’t a vibe you’ll “loop in” later — they’re named steps on the runbook, each with a human and a date that falls before the asset it gates. The deadline is the entire point: a sign-off without a date is a sign-off that happens after the thing it was supposed to approve.
• Competitive and regulated claims clear legal — specifically. A launch makes its boldest claims, and the bold ones are exactly the ones a competitor or a regulator will test. Any claim that names a rival, cites a number, or touches a regulated area (for Mizan, anything about the FTA or tax filing) gets a legal gate of its own, traceable to the proof in your messaging-framework.md. Confident-and-wrong is expensive on a normal day; on launch day it’s public and permanent.
• The bilingual sign-off is a person who actually reads the Arabic. The most common gate failure in this region is the second language skipping review because nobody on the approval chain reads it — the Arabic ships because the English cleared. Put an Arabic sign-off on the runbook, owned by someone who genuinely reads and judges Arabic copy, not someone approving a shape they can’t read.

The operating guide is where the org-level version of these gates lives — the standing data, sign-off, and rollout rules that sit underneath every launch, so each one inherits the policy instead of re-litigating it.

Comms without the 11pm scramble

The comms kit is the launch’s insurance policy, and the whole trick is that it’s written before the moment, while you’re calm — not live, under a deadline, with a reporter or a customer waiting. The launch-day version of writing the announcement is writing it at 11pm the night before. The orchestrated version is having it drafted, gated, and scheduled days earlier, so the day itself is execution.

• The announcement, drafted and gated early. The actual news in the first sentence, the proof behind the claim, one approved quote — written from your locked message, cleared by brand and legal, sitting ready on the runbook with a go-live time. Not a teaser. The news.
• The FAQ includes the questions you hope nobody asks. The easy questions answer themselves. The valuable part of a launch FAQ is the uncomfortable one — the price, the data, the is this actually safe and accurate — answered honestly in advance, with a clean we-don’t-comment-on-this line where that’s the right call. Claude is good at generating the hostile questions you’d rather not think about; that is precisely why you ask it to.
• The holding lines exist before the thing they hold. Draft the calm, honest line for each way the launch can go sideways — a critical reaction, a factual challenge, a channel that fails on the day — now, with an approver named on each. Under pressure you will reach for the line you already wrote; the orchestration is making sure that line exists and is pre-cleared, so “respond” is a send, not a scramble.

One moment, two languages, coordinated

For a MENA launch, “bilingual” is not a translation step bolted to the end of the runbook. It’s two launches that land the same instant, each native to its language, on one shared schedule. The failure you’re designing against is the English going live at 9am and the Arabic trailing a day later as an obvious translation — which tells your Arabic-first audience, precisely, that they were the afterthought.

• Both languages, one go-live. The Arabic and English assets sit on the same runbook, aimed at the same moment. Neither is the original; neither is the echo. The runbook is what makes simultaneity a plan instead of a hope — the Arabic post has its own row and its own time, right next to its English twin.
• Authored, not translated — inheriting the Arabic foundation. The Arabic launch is built from your Arabic voice and message docs (the brand-voice-ar.md you wrote in Module 1), adapted for the Gulf market — the proof, the objections, even which pillar leads can differ. Run the English announcement through translation and you get copy that’s technically correct and emotionally foreign; author it and you get a launch that reads native.
• The same gate, in both languages. Both languages clear brand, legal, and regional — and the Arabic clears an Arabic reader. One moment, two native expressions, both signed off. In this market that isn’t a nicety; it’s the credibility line.

Your assignment

Build a complete launch plan for one brand — your own (recommended: the output is a real launch your team keeps) or the sample brand Mizan, the GCC small-business bookkeeping tool used throughout this track. Open the folder with your launch brief, your foundation docs, and your campaign assets in Claude Desktop, approve each read in the Ask permissions prompt, and work in the chat — no terminal needed. The runbook and the comms kit are files you create and edit in the file pane.

Module 4 deliverable — the launch

Pick one real launch moment. (Sample: "Mizan launches VAT-season auto-filing"
— a deadline-driven moment with a regulated claim and a bilingual audience,
which is exactly where orchestration earns its keep.)

Inherit everything upstream. The launch does NOT re-invent the message — it
schedules it:
  - messaging-framework.md + brand-voice.md (+ brand-voice-ar.md) from M1
  - the campaign assets + the calendar from M2 / M3

1. launch-runbook.md   (one table that owns the whole moment)
   - every asset × its owner × its go-live date/time × its channel
   - every approval gate as its OWN row — brand, legal, regional compliance —
     each with an owner and a deadline BEFORE the asset it gates
   - the hard dependencies marked (legal clears the claim before the blog;
     the Arabic sign-off before the Arabic post)

2. comms-kit.md        (drafted before the day, not during it)
   - the announcement: the actual news, first sentence, one approved quote
   - a public FAQ — including the questions you hope nobody asks
   - holding lines for 3 ways it goes sideways, each with an approver named

3. The approval gates, made explicit — not a vibe
   - who signs brand, who signs legal, who signs the region
   - who reads and signs the ARABIC (someone who actually reads it)

Bilingual teams: the Arabic launch is authored — not translated — and lands the
SAME moment as the English. Both languages, one runbook, one go-live.

The What you keep section below gives you a fill-in template for the runbook and the comms kit, plus the prompts that build them — so you start from structure, not a blank grid.

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 launch plan is scored against five criteria. Each is meets / nearly / not yet — and a “nearly” on any one is a revise, not a pass.

Launch rubric — five criteria, each meets / nearly / not yet.
A "nearly" on any one is a revise, not a pass.

1. Every line is owned      Every asset, gate, and channel names a
                            human and a go-live time. A blank in the
                            owner or date column is the gap that
                            becomes the 11pm scramble — caught a week
                            early here, not live.
2. The gates are explicit   Brand, legal, and regional compliance are
                            their own rows with deadlines, before the
                            assets they gate. Competitive and regulated
                            claims show a named legal sign-off, not an
                            assumed one.
3. One coordinated moment   Channels fire to a single planned go-live in
                            a deliberate sequence — not a scatter of
                            whenever-it's-ready posts across a week.
4. The message is inherited Every claim traces to messaging-framework.md
                            and its proof. The launch schedules the
                            message; it doesn't invent a louder one for
                            the occasion.
5. Bilingual + simultaneous The Arabic launch is authored (not
                            translated), lands the same moment as the
                            English, and is signed off by someone who
                            actually reads it. (Bilingual teams.)

The discipline is deliberately what a launch lead would demand: a launch fails loudly and in public, so the gaps that a normal campaign can absorb quietly — an unowned line, an unsecured sign-off, an Arabic asset a day late — have to be caught here, on the runbook, before the day.

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 — a launch of VAT-season auto-filing. Your own doesn’t need to look like this; it needs to clear the same bar.

launch-runbook.md — Mizan: "VAT-season auto-filing" (excerpt)

Asset / step                Owner               Go-live          Gate
Legal: clear the VAT claim  R. Haddad (Legal)   Feb 18           ← this IS the gate
Regional sign-off (UAE)     A. Saleh (Compl.)   Feb 20           ← gates AR + email
Announcement blog — EN      You                 Feb 24, 09:00    brand · legal ✓
Announcement blog — AR      L. Mansour          Feb 24, 09:00    brand · legal · AR-read ✓
Launch email — EN + AR      You                 Feb 24, 10:00    brand ✓
Social — EN (LinkedIn, X)   You                 Feb 24, 11:00    brand ✓
Social — AR (LinkedIn, IG)  L. Mansour          Feb 24, 11:00    brand · AR-read ✓

Dependency: legal clears the FTA claim (Feb 18) BEFORE either blog publishes.
Dependency: regional + AR sign-off (Feb 20) BEFORE the Arabic post and email.

Every line has a named human and a time; the gates (legal, regional, Arabic-read) are their own rows with deadlines that fall before the assets they clear; and the Arabic post sits on the same 09:00 moment as its English twin — not a day behind. Now the announcement it’s all scheduled around:

announcement.md — Mizan (excerpt)

Mizan now files your VAT return for you.

Until today, Mizan got your books closed and your VAT return ready — you still
pressed submit. Starting today, Mizan files it straight to the FTA. The same
returns 9,000+ GCC businesses already trust, accepted without amendment in our
2025 cohort — now sent on time, without the last-week scramble.

"Owners don't dread VAT," says [spokesperson], [title] at Mizan. "They dread
the week it's due. We took the week back."

holding line — if the FTA filing channel has downtime on launch day

Some returns are queued while we confirm delivery with the FTA. Nothing is
lost: every return is saved and filed the moment the channel clears, and we
will confirm each one to you directly.

[Must clear R. Haddad (Legal) before this goes out.]

Notice what the announcement does and doesn’t do: it makes one plain claim, backs it with the proof from the foundation (9,000+ businesses; accepted without amendment), stays calm with no exclamation marks, and talks to one owner. The holding line is honest, buys time without overcommitting, and names its approver — written now, while calm, not at 11pm during the outage.

What you keep — toolkit additions

These extend the Foundation toolkit you already installed. Save them in the folder your team works in; every launch from now on starts from structure, not a blank grid. Replace the Mizan placeholders with your own.

The launch-runbook.md template

# launch-runbook.md — [Brand]: [launch moment]

Goal:        [the one outcome this launch is for — one sentence]
Go-live:     [date + time + timezone — the single moment everything aims at]
Languages:   [EN / AR — both land the same moment]

## The runbook (every line has an owner and a date)
Asset / step          Owner          Go-live          Channel        Gate
[announcement — EN]    [name]         [date, time]     [blog]         brand / legal
[announcement — AR]    [name]         [date, time]     [blog]         brand / legal / AR-read
[email — EN + AR]      [name]         [date, time]     [list]         brand
[social — EN]          [name]         [date, time]     [LinkedIn, X]  brand
[social — AR]          [name]         [date, time]     [LinkedIn, IG] brand / AR-read

## Approval gates (each is its own row above, repeated here with a deadline)
- Brand sign-off:        [owner] — by [date, BEFORE the assets ship]
- Legal sign-off:        [owner] — by [date]; covers [the regulated/competitive claims]
- Regional / compliance: [owner] — by [date]; covers [market-specific rules]
- Arabic sign-off:       [owner who actually reads Arabic] — by [date]

## Dependencies (what blocks what)
- [legal clears the claim] BEFORE [the blog publishes]
- [regional + Arabic sign-off] BEFORE [the Arabic post + email]

The comms-kit.md template

# comms-kit.md — [Brand]: [launch moment]

## Announcement (drafted and gated before the day)
Headline:       [the news, plainly — not a teaser]
First sentence: [the actual news: what changed, for whom]
Body:           [context + the proof behind the claim]
Quote:          "[spokesperson, on-message, calm]" — [name, title]

## Public FAQ (including the questions you hope nobody asks)
Q: [the obvious one]
A: [honest, proof-backed]
Q: [the uncomfortable one — price, data, is-this-safe/accurate]
A: [honest; a clean we-don't-comment-on-this line where that's the right answer]

## Holding lines (written calm, before the moment that needs them)
If [a critical reaction]: [short, calm, honest, buys time] — approver: [name]
If [a factual challenge]: [acknowledge, commit to verify, no overclaim] — approver: [name]
If [a channel/delivery failure]: [the contingency line] — approver: [name]

Saved prompts (Launch)

Build the runbook from the goal
  "We're launching [moment] on [date, time, timezone], in [EN and AR]. Read
   messaging-framework.md and the campaign assets in this folder. Build a
   launch-runbook table: every asset and step, its owner, its go-live time, its
   channel, and which approval gate it must clear first. Add brand, legal, and
   regional sign-off as their OWN rows, with deadlines BEFORE the assets they
   gate. List the hard dependencies. Leave the owner column for me to fill —
   don't invent names."

Draft the holding lines
  "For this launch, list the 3–4 most likely ways it goes sideways — a critical
   reaction, a factual challenge, a channel/delivery failure, silence. For each,
   draft a short holding line in our voice (brand-voice.md): calm, honest, buys
   time without committing to anything unverified. Mark who must approve each
   before it goes out. Don't write anything I couldn't stand behind."

Red-team the runbook
  "Read launch-runbook.md as a skeptical launch manager. Find every line with a
   blank owner or date, every claim that ships before its legal gate clears, and
   every place the Arabic trails the English instead of landing the same moment.
   List the gaps in priority order — the ones that become an 11pm scramble first."

On the Terminal & Automation track these prompts become one-keystroke slash commands; on Desktop you paste them in the chat with the right files open, and they do the rest.

What you’ve proven — and what’s next

Clear this rubric and you’ve proven the part of marketing that never shows up in any single asset: not writing a launch, but running one. A moment where the foundation, the engine, and the campaigns fire at once, in two languages, with every brand, legal, and regional sign-off secured before the day instead of chased during it. That’s the Launch stage of “Certified Marketing with Claude” — the module that proves you can hold the whole thing at scale, which is exactly the skill a team buys the certificate to vouch for.

One module remains before the capstone, and it’s the one that makes the next launch better than this one:

• Module 5 — measure & iterate: close the loop. Read what the launch actually did, separate signal from noise, and feed the lesson back into the foundation — so Module 1 gets sharper every cycle instead of going stale.

Then the capstone runs all five modules end to end for a single brand — foundation, engine, campaigns, launch, and measurement as one integrated campaign system — graded into the credential. The launch you just planned is one of its five pieces, and you’ve now built the hardest one to coordinate.

Next: Module 5 — measure & iterate, then the capstone.