AI Stack for Campaign Operations

The gap between a campaign brief and a live campaign is where ops work happens — and where things get missed. Marketo program setup, UTM parameters, Salesforce campaign sync, scoring adjustments, form dependencies, alert triggers. Most teams rebuild this list from scratch for every launch, or rely on an ops person who holds the checklist in their head. This stack generates a complete ops checklist from your campaign brief and system requirements — covering every pre-launch, launch-day, and post-launch task, with dependencies flagged, so nothing gets missed before go-live.

The Stack

The Prompt

This stack is built around the Strategic Campaign Brief Prompt. Here's the abbreviated version — the full prompt with all variables and usage notes is on its own page.

You are a marketing operations manager converting a campaign brief into a
launch-ready operations checklist.

Using the campaign brief, Marketo requirements, and Salesforce field specs below,
generate a complete campaign operations checklist organized into:

PRE-LAUNCH (technical setup, asset creation, QA)
LAUNCH DAY (activation sequence, tracking verification, stakeholder notifications)
POST-LAUNCH (performance monitoring, lead routing verification, reporting setup)

For each task: specify the system owner, dependency (what must happen first),
and any common failure mode to watch for.

The Workflow

1. Start with a completed campaign brief

   The checklist is only as good as the brief it's built from. Confirm the campaign has a defined objective, channel mix, target segment, timeline, and success metrics before moving to ops setup.

2. Document your Marketo setup requirements for this campaign type

   List what Marketo needs: program template, scoring rule adjustments, UTM parameter structure, form and landing page dependencies, alert trigger conditions, and any nurture program connections that need updating.

3. Pull your Salesforce campaign field requirements

   Document the Salesforce side: campaign naming convention, influence model settings, lead source values, campaign member statuses, and sync rules between Marketo and SFDC — including what triggers a campaign member record.

4. Paste brief plus Marketo and Salesforce requirements into the prompt

   Give Claude the campaign brief and both system requirement documents together. Claude generates the full operations checklist: pre-launch setup, launch-day activation sequence, and post-launch monitoring tasks — with owners and dependencies flagged.

5. Move into Notion and assign owners

   Paste the checklist into Notion with your preferred task format. Assign owners to each task, set due dates against the launch timeline, and use it as the single source of truth across marketing, ops, and sales through go-live.

What This Replaces

• Manually rebuilding campaign checklists from scratch for every launch without a documented template
• Missed Marketo setup steps that cause UTM tracking failures or lead routing errors after launch
• Ops-to-marketing handoffs where neither team is sure what the other needs before the campaign goes live

Related Stacks

• AI Stack for Marketo Lead Scoring →
• AI Stack for Marketo Nurture Audit →
• AI Stack for Campaign Brief Creation →