Reads approved brief · spawns Claude Code strategists in parallel · coordinates Copy + Asset phases · routes outputs to Notion campaign page
Google
Agent
Google Ads Strategist
Default: Performance Max. Full surface: PMax · Search/RSA · Display · Shopping · YouTube · Demand Gen
Meta
Agent
Paid Social Strategist
Angle · Reels hooks · Carousel
LinkedIn
Agent
Paid Social Strategist
Sponsored · Intro · CTA
TikTok
Agent
Paid Social Strategist
3-sec hook variants · Native format
Phase 3 — Copy Generation
Agent
Ad Creative Strategist
Per-platform copy variants · Google asset groups (PMax) + RSA · Meta sets · LinkedIn · TikTok scripts
Output
Copy in workspace + Notion campaign page
Direction Check (lightweight)
Creative Direction Review
Justin reviews creative direction + copy alignment first · escalates to Taq if creative concern · prevents wasting asset-gen cycles on off-brand directions
Two gates only · partner-divided. Brief approval (Justin + Taq) and asset approval (Taq owns creative, Justin owns business). Strategy + copy + asset generation runs continuously between them.
Re-brief, not resize. Each platform gets its own emotional entry point. Never repurpose one ad across surfaces.
Ships paused, always. APIs create the structure; humans flip active. Third checkpoint by design.
One tool per tier per campaign. No stacking within a campaign — pick one static tool (Canva default) and one video tool (HyperFrames / Runway / Descript chosen per campaign). Stack across campaigns is fine.
One Ads Campaign project per client per campaign. Notion is the single review surface. Workspace .md is the source. Drive is the client mirror.
Kai orchestrates Phases 2–4. Brief approval gates the trigger; Kai then dispatches the platform strategists, copy strategist, and asset generators in sequence. No bare sub-agent invocations.
Mid-pipeline direction check before assets. Justin reviews creative direction + copy after Phase 3, escalates to Taq if creative concern. Asset generation only fires once direction is sound — saves Canva + video render cycles.
Every n8n step has a Kuma watcher. Bundle Builder + Publish Bridge both ship with push monitors. Silent failure is not allowed.