MARKETING OPS
Two-Function Marketing Operating System
Split marketing into Demand Gen vs. Enablement, then enforced SLAs and output minimums.
Project Details
Outcome
7-day brief-to-ship SLA; 200+/yr content output floor.
Scope
Org design → intake-to-archive workflow → deck governance → GA4 audience segregation.
Stack
Beautiful.ai • GA4 • SharePoint/Teams • Marketing Hub
Governance
7-day SLA • published minimum outputs • version control • cadence reviews
What I Shipped
- Outcome — 7-day brief-to-ship SLA enforced across content + sales assets (no ‘rush’ queue jumping).
- Outcome — output minimums published and tracked: 200+/yr floor incl. 26 press releases/yr.
- System — two accountable lanes: Demand Gen (pipeline) + Enablement/Design (asset factory).
- Governance — centralized intake-to-archive + Beautiful.ai version control (no rogue decks).
- Governance — GA4 audience segregation: B2B reporting isolated from consumer/debtor noise.
- Artifacts — SLA doc, output cadence dashboard, GA4 tracking requirements, hub structure map.
Interview Line
I rebuilt marketing into two functions with a 7-day brief-to-ship SLA and published output minimums—marketing now runs like a product team.
Longform Draft
Longform draft available (markdown).
Deep Dive
In a live walkthrough I can share redacted artifacts (process maps, KPI dictionaries, example reporting packs, and automation logs).
DEEP DIVE
HOVER TO REVEAL
Example artifacts: routing decision tree; KPI dictionary excerpt; QA checklist; a "what changed?" weekly narrative page.