Marketing Campaigns: build lifecycle sequences that move, and stories that earn trust

Your team already has the lifecycle-nurture and customer-story playbooks — the worked recipes for designing a sequence and turning a customer interview into an approved case study, step by step. This module is the layer above the recipe. It’s where you master the two moves that turn finished content into a campaign that actually moves someone — a lifecycle sequence and the proof that earns trust — build them for your own brand, and prove, against a real rubric, that you can.

It’s Module 3 of the certifiable Marketing track. It inherits the message and voice you built in Module 1 and runs on what the Module 2 content engine produces — because a nurture is only as good as the message it carries and the assets it can reach for. Module 2 fills the library; this module builds the route a buyer walks through it.

Content informs; a campaign moves someone — and the difference is sequence and proof. A nurture isn’t a stack of emails; it’s a path where each step earns the next click. A customer story isn’t a testimonial; it’s borrowed trust, cleared for use. Master those two and your content stops being a library nobody walks through and starts being a route a buyer actually follows.

Every email has one job — or the sequence has none

The default failure is batch-and-blast: the same message to the whole list, treating a day-one signup like a sales-ready lead, and torching both. A real nurture is designed — and the design discipline is one rule applied without mercy: every step has exactly one job, and earns the next.

• Name the job before you write a word. Before any copy, each email gets a single job, a single angle, and one CTA. The moment an email tries to welcome and upsell and re-engage, it does none of them. Write the job first; the copy is downstream of it.
• The asks escalate — no step assumes a yes the last one didn’t earn. The classic break is email two writing as if the reader already said yes to email one. A sequence is an arc: deliver a first win, then ask for a little more, then a little more. Each click is permission for the next ask, not a given.
• A sequence is for a segment, not a list. Who entered, where from, and what they already know decides which track they’re on — trial-to-activation is not lead-nurture is not win-back. Segmentation is the difference between a message that fits and a blast that annoys. Define entry criteria, the branches (click, convert, go cold), and the suppression rules so you never email someone who already did the thing.
• Claude designs and drafts; you own the send. This is a hard line. Claude maps the journey, writes the arc, and drafts every email — but consent (only people who opted in), instant unsubscribes, an approved sending tool, and PDPL / GDPR / CAN-SPAM are yours. The playbook makes the emails; it does not make you compliant.

A customer story is consent and claims, not just craft

A customer story is the strongest proof you own and the single most likely thing to blow up in your face. The craft — find the arc, draft it in your voice, the customer as the hero — is the easy 60%. The 40% that gets teams burned is the part most courses never mention: consent and claims. Three gates, and all three close before anything publishes.

• Consent is the whole game, and it’s in writing. Name, logo, each specific figure, each direct quote — the customer approves what’s public, explicitly and on the record, before it ships. A quote or a number that goes out ahead of sign-off is a relationship problem and a legal problem at the same time. When consent is still pending, you don’t wait — you ship the anonymous version (a GCC trading business, no name, no logo) and the proof still lands.
• Every claim is fact-checked to the source. Quotes are verbatim or they’re fabricated — never let a quote get “tidied up” into something cleaner the person never said. Numbers are exact: the figure the customer agreed to is the figure. Claude will happily turn 31% into “over a third” and state it with total confidence — that’s the limit you design around. Every figure traces to a transcript line, or it gets marked [NEED] and confirmed, never invented.
• Mind the legal and PII gate. A public case study can quietly carry third-party data, an unapproved competitor mention, or a figure under embargo. Route it past legal or PR, strip anything personal that wasn’t cleared, and put a named human on the published claim. Claude builds the apparatus — the sourced quote-and-number list, the who-signs-off list, the approval email — but it doesn’t clear you. A person does.

The discipline here isn’t bureaucracy; it’s what lets your best proof actually ship instead of dying in a transcript because nobody wanted to own the risk.

Map the journey to the message — your framework in motion

Here’s the connection that turns a competent sequence into a sharp one: each lifecycle stage leans on a different pillar or objection from the messaging framework you built in Module 1. The sequence isn’t separate from your message — it’s your message framework set in motion, one beat at a time.

• Entry leans on the lead pillar — relief, not the feature tour. The first email delivers the core promise as a feeling. For Mizan, that’s “you’ll understand your own numbers,” not a tour of the dashboard.
• The middle answers the differentiator that survives a search. This is where the pillar with real proof does its work — Mizan’s “Trustworthy, not just fast,” carried by a figure that traces to its source.
• The decision step answers the hardest objection, with proof. Don’t route around the thing that stalls deals — meet it. Mizan gives “I already have an accountant” its own email: “Keep them — Mizan does the daily books so you only pay them for advice, not data entry.”
• Activation delivers the promise, then earns the ask. The proof pillar shows up here too — 9,000+ GCC businesses; VAT-return-ready exports the FTA accepted without amendment — and only then does the sequence ask for the upgrade.

The test is simple: if a step can’t name the pillar or objection it carries, it’s filler, and filler is where unsubscribes come from. A nurture that maps cleanly to your framework reads like one confident argument; one that doesn’t reads like seven strangers taking turns.

Bilingual journeys — adapt the sequence, don’t translate it

For a Gulf audience the Arabic nurture is a parallel campaign, not a translation pass bolted on after the English ships. The rule is the same adapt, don’t translate you learned in the foundation — and a sequence has its own edges most teams miss.

• The cadence localizes, not just the words. Send timing is part of the message. A sequence that lands on a Friday in the Gulf, or schedules around the GCC work week and Ramadan as if it were a Western calendar, reads as foreign before a word is parsed. Re-time the arc; don’t just re-language it.
• The proof and the lead objection can differ. Who decides, what earns trust, and which pushback comes first are not the same across markets. The local proof (the FTA acceptance, the GCC business count) carries weight here that a generic global stat doesn’t — re-point the angles to what lands for this buyer.
• Register, authored from copy you’re proud of. Lightly formal Modern Standard Arabic with Gulf-natural phrasing — not the stiff fus’ha of a bank letter, not slang — drawn from your brand-voice-ar.md, with numbers kept Western. The Arabic subject line is written, not converted.
• Same gate, both languages. The Arabic sequence and any Arabic-language story clear the same consent and legal review 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 — that’s the credibility line in this region, not a nicety.

Your assignment

Build a working campaign for one brand — your own (recommended: the output is real work your team ships) or the sample brand Mizan, the GCC small-business bookkeeping tool used throughout this track. Open the folder with your context in Claude Desktop, approve each read in the “Ask permissions” prompt, drop your interview transcript into the file pane, and work in the chat — no terminal needed.

Module 3 deliverable — a campaign that moves

1. lifecycle-nurture.md  (a trial → activation sequence, 4–5 steps)
   - the goal of the whole sequence, in one sentence
   - per step: its single job, the ONE CTA, the send delay, and the
     M1 pillar or objection it leans on
   - the segment it's for + the branch and suppression rules
   - a per-email metric and one sequence-level number to judge it on
   - an Arabic version — authored, not translated (cadence re-timed,
     proof and objections localized)

2. customer-story.md  (one approved case study)
   - the before / change / after arc, drafted in your voice
   - every quote verbatim, every number sourced to a transcript line
   - a consent + claims checklist, applied — not just attached
   - [NEED] on any gap, never filled with invention; if consent is
     pending, ship the anonymous variation

Inherit the foundation: feed in messaging-framework.md, brand-voice.md, and
brand-voice-ar.md so the whole campaign stays on message and on voice, and
the sequence reads like one conversation instead of seven.

The toolkit blocks below give you a fill-in template for each, 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.

Campaigns rubric

1. Every step has a job + CTA   Each email names one job and drives one CTA.
                                No email does three things; none assumes a yes
                                the previous step didn't earn.
2. Segmented, not one-size      The sequence targets a defined segment, with
                                entry criteria, branches, and suppression — not
                                a batch-and-blast to the whole list.
3. On-voice & on-message        Reads in your brand voice, and every step maps
                                to a named pillar or objection from M1. No step
                                is filler that can't say what it carries.
4. Consented + fact-checked     The story has written consent (or ships
                                anonymous); every quote is verbatim and every
                                number traces to a source line. Gaps are [NEED],
                                not invented. Legal/PII gate cleared.
5. Arabic is adapted            The Arabic sequence is authored, not translated:
                                cadence re-timed, proof and objections localized,
                                register right, same sign-off gate. (Bilingual.)

The discipline is deliberately what a senior marketer would demand: a sequence that blasts, a story that misquotes, or an Arabic version that reads translated fails in public — so it has to be caught here, against the rubric, not in front of a customer or a regulator.

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

You don’t have to guess what “meets” looks like. Here are passing excerpts for the sample brand — yours doesn’t need to match these, it needs to clear the same bar. Mizan’s English brand copy stays English by design.

nurture-sequence.md — Mizan (trial → activation, excerpt)

Goal: turn a free-trial signup into an owner who has closed one month.
Segment: GCC small-business owners on a self-serve trial, no accountant on staff.

Step 1 · Day 0 · Welcome
  Job: deliver the first win, not a feature tour.
  Carries: the core promise — "your books, done and trustworthy, without
           hiring an accountant" (relief).
  CTA: connect one bank account.   (the single first action)

Step 2 · Day 2 · The first close
  Job: make "close the month" feel real by closing one week.
  Carries: Pillar — "Trustworthy, not just fast": every figure traces to
           its source.
  CTA: see your first week matched to your invoices.   (voice: "matched")

Step 3 · Day 5 · Handle the big objection
  Job: defuse "I already have an accountant" before it stalls the upgrade.
  Carries: objection answer — "Keep them. Mizan does the daily books so you
           only pay them for advice, not data entry."
  CTA: open your month-to-date in one screen.

Step 4 · Day 9 · Proof, then the ask
  Job: earn the upgrade with proof, not a discount.
  Carries: proof — 9,000+ GCC businesses; FTA-accepted VAT exports.
  CTA: keep your books — upgrade before the trial ends.

Branch: clicked step 3, didn't upgrade → add one accountant-comparison email.
        Converted at any step → exit the sequence immediately.
        Went cold by step 4 → one "still here when you need us" note, then stop.
Suppress: never email anyone who already upgraded or unsubscribed.
Measure: per email = open · click · the action; sequence number = trials that
         close one full month (not opens — opens feel good and prove nothing).

Arabic version (authored, not translated):
  Cadence re-timed to land Sun–Thu, never Friday.
  Step 1 subject, authored: «أغلق شهرك الأول مع Mizan»
  Proof stays local (FTA, the GCC count); "I already have an accountant" is
  still the lead objection, phrased Gulf-natural. Numbers Western. Register:
  lightly formal MSA with Gulf-natural phrasing.

customer-story.md — Mizan (excerpt)

Headline (states the outcome)
  Al Hosn Trading closed twelve months in one afternoon — and handed the bank
  a clean set of books without a redo.

Arc
  Before: the owner dreaded the books; year-end was a week of catch-up.
  Change: moved the daily books to Mizan; the accountant moved to advice only.
  After: monthly close in an afternoon; a VAT return the FTA accepted as filed.

Quotes (verbatim, sourced)
  "I finally understand my own numbers."        ← transcript line 41
  "I stopped paying my accountant to type."     ← transcript line 58

Numbers (exact, sourced)
  Close time: three days → one afternoon.       ← line 22  (NOT "75% faster")
  VAT return accepted by the FTA, no amendment. ← line 64

Consent + claims note
  [ ] Name "Al Hosn Trading" + logo — written sign-off PENDING → mark [NEED]
  [x] Both quotes verbatim, each sourced to a transcript line
  [x] Every figure exact — "an afternoon" is what was said, never "75% faster"
  [ ] Legal/PR review — not yet on file → do NOT publish until it is
  While the boxes are open, ship the anonymous variation: "a GCC trading
  business," no name, no logo. The proof still lands.

What you keep — toolkit additions

These extend the Foundation toolkit — copy them into the same folder your team works in, replace the Mizan placeholders with your own, and every campaign starts from structure instead of a blank page.

The nurture-sequence template — the goal-per-step discipline, made fill-in-the-blank.

# nurture-sequence.md — [Brand]

Goal (one sentence): [the single action the whole sequence drives]
Segment: [who's in it · where they entered · what they already know]

| # | Send  | The step's ONE job        | Pillar / objection it carries | The ONE CTA |
|---|-------|---------------------------|-------------------------------|-------------|
| 1 | Day 0 | [first win, not a tour]   | [core promise / relief]       | [action]    |
| 2 | Day _ | ...                       | [pillar + its proof]          | ...         |
| 3 | Day _ | [answer the objection]    | [the objection, named]        | ...         |
| 4 | Day _ | [proof, then the ask]     | [proof pillar]                | ...         |

Branches:  click → [...]   convert → exit   cold → [one note, then stop]
Suppress:  never email anyone who already did the action or unsubscribed
Measure:   per email = open · click · action   |   sequence = [the one number]
Arabic:    authored, not translated — cadence re-timed, proof + objections
           localized, register per brand-voice-ar.md (see the prompt below)

The customer-story template + the consent/claims checklist — the part that turns a draft into something publishable.

# customer-story.md — [Brand]

Arc:     before (the pain) → change (what they did) → after (the outcome)
Quotes:  [verbatim only — each with its transcript line]
Numbers: [exact only — each figure with its transcript line]
Draft:   ~500 words in brand-voice.md — customer is the hero, you the enabler
Gaps:    [NEED] on anything you'd have to supply — never invented

Consent + claims checklist (every box before it ships):
[ ] Customer approved name + logo, in writing
[ ] Customer approved each quoted figure, in writing
[ ] Every quote is verbatim — nothing "tidied up"
[ ] Every number traces to a transcript line — nothing rounded up
[ ] No PII or un-cleared third-party data in the public version
[ ] Legal / PR sign-off on file
[ ] A named human owns the published claim
→ Any box unchecked? Ship the anonymous variation, or don't ship.

The saved prompts — paste them in the chat with the right files open. (On the optional Power Track these become slash commands; you need none of that to use them today.)

Draft a sequence with a job per step
  "Read messaging-framework.md and brand-voice.md. Design a [N]-step
   trial→activation nurture for [segment]. For each step give me: its single
   job, the ONE CTA, the send delay, and which pillar or objection from the
   framework it carries. Make the asks escalate — no step assumes a yes the
   one before it didn't earn. Don't write final copy yet."

Extract a story, every claim flagged for fact-check
  "Read interview.txt. Give me the before/change/after arc, the 5 most
   quotable lines word-for-word, and every number mentioned — each marked
   with the transcript line it came from. Flag with [NEED] anything you can't
   source. Don't smooth a quote and don't round a number."

Adapt the sequence for the Gulf — don't translate it
  "Read brand-voice-ar.md and messaging-framework.md. Adapt this nurture into
   Arabic for a Gulf audience: match the Arabic voice register, re-time the
   cadence for the GCC work week, swap in proof and objections that land here,
   and flag anything that shouldn't carry over. This is an adaptation, not a
   translation."

What you’ve proven — and what’s next

Clear the rubric and you’ve proven something the free playbooks can’t certify: you can take finished content and make it move someone — a sequence that earns each step, and proof that’s cleared to use. That’s the Campaigns stage of “Certified Marketing with Claude.”

From here the track turns a campaign into a moment, each module assessed the same way:

• Module 4 — the launch: orchestrating a full go-to-market moment end to end — the launch plan and comms kit — without the 11pm scramble.
• Module 5 — measure & iterate, then the capstone — a complete campaign for one brand, foundation through measurement, graded into the certificate.

Because this module lives or dies on consent and sign-off, pair it with the operating guide — the data, approval, and rollout layer that belongs underneath every story you publish and every list you send. It’s the safety net that makes “Claude drafts; a person decides” a process, not a hope.