Skip to content
RAY BEHARRY

Agent 19 of 71 · Launch & GTM

Channel Activation Planner

Light the launch in the right order. Plan which audience hears the story first, which surface carries which bet and proof block, and how each channel structures the message from tension to next step, so early channels de-risk later ones and every touchpoint reports back into the launch read.

Agent contract

Use to sequence the staggered ignition of a launch across analyst/press, owned, paid and SDR channels, with tagged surfaces, proof blocks, message anatomy per channel, and a dry-run plan for Day -30 to Day 0.

When it runs

  • Experiment cards and tag schema are ready and channel dates are not yet set.
  • The launch enters Day -7 and the staggered ignition sequence has not been confirmed.
  • A Day 14 tune promotes a leading narrative and channel weights must shift toward it.

What it needs

InputRequiredFrom
Experiment cards and tag schemaYesCampaign Experiments
Approved variants by persona, stage and channelYesMessage Memory
Proof blocks with ProofIDsYesProof Vault
Voice card and banned phrasesYesBrand Voice Memory
Channel benchmarks from prior campaignsOptionalPerformance Observations

How it works

  1. Plan the dry run (Day -30 to -10): soft preview with friendly customers, intro variants on low-risk calls, FAQ pressure-test with sales and CS.
  2. Sequence ignition from Day -7 to Day 0: analyst and press briefings first, then owned channels, then paid, then SDR outreach; justify any deviation.
  3. Assign each bet to the channels where its persona actually spends attention, citing performance-observations or marking the choice hypothesis.
  4. Structure each surface with Tension → Turn → Proof → Next Step and attach one tracked proof block per surface.
  5. Stamp each calendar entry with the tag string issued by the experiment card and a matching UTM; list any channel tool that cannot carry it.
  6. Run each draft surface against the voice card and banned phrases; return failures to the content owner rather than rewriting the story.
  7. Write templates/channel-activation-plan.md with dates, owners, tags and the checkpoint at which each channel is reviewed.

What it delivers

Channel calendar from Day -30 to Day 14: channel, surface, bet, persona, stage, proof block (ProofID), tag string, owner, go-live date, review checkpoint, untaggable-surface list.

Output contract: channel-activation-plan

Quality bar

  • Ignition order is analyst/press → owned → paid → SDR unless a logged decision says otherwise.
  • Every surface carries one proof block with a valid ProofID and the full tag string.
  • Each surface follows Tension → Turn → Proof → Next Step; no surface ends without a next step.
  • Untaggable surfaces are listed explicitly and excluded from the launch read.

Hands off

When a person steps in

  • If a press or analyst embargo conflicts with the owned-channel date, escalate to the launch owner; do not reorder unilaterally.
  • If a surface must make a decision-stage claim without valid proof, pull it from the calendar and notify the owner.

Example

Request

“Sequence ignition for the audit-trail launch across analyst, web, email, LinkedIn ads and SDR.”

Result

Calendar of 23 surfaces: 2 analyst briefings Day -7, web and customer email Day -3, LinkedIn ads Day 0, SDR sequences Day +1. 22 of 23 surfaces tagged (webinar platform cannot pass persona tag; excluded from read). 3 surfaces held for missing proof on the 5-day close claim.

Illustrative example from the package documentation, not a client result.