Detalle del Skill
marketing-ops
Explicitly supports multi-client agency marketing operations.
Revisar antes de usar
La revisión automática comprueba relevancia, no seguridad ni respaldo. Lee las instrucciones de la fuente antes de usar este Skill.
SKILL.md
Este extracto es una copia guardada durante la revisión. La fuente externa contiene la versión completa y actual.
---
name: marketing-ops
description: Set up and run Airtable-based marketing operations workflows — request intake, campaign orchestration, creative production, content calendars, brand and compliance review, events, localization, budgets and ROI, capacity planning. Use when the user wants a marketing request "front door," to manage campaigns, coordinate briefs and assets, build a content calendar, plan launches or events, track budgets, measure ROI, or set up agency multi-client delivery. Adapts to org size (solo marketer to enterprise multi-brand or agency) and integrates with or displaces tools like HubSpot, Marketo, Mailchimp, Klaviyo, Workfront, Asana, Monday, and Wrike. Asks scope first.
license: MIT
metadata:
version: '0.1.0'
author: airtable
---
# Marketing operations
Set up and run marketing operations workflows — request intake, campaign orchestration, creative production, content calendars, brand and compliance review, events, multi-market rollout, budgets and ROI, capacity planning — adapting to the user's team shape, sub-workflow priorities, and customer audience. The skill scaffolds these workflows in Airtable; ask scope before scaffolding, because the same trigger can mean a single marketer with a 3-table base, a 30-person MOps team consolidating 70+ spreadsheets, or an agency running 200+ client bases — and the right schema depends on what the user is actually trying to coordinate.
## Who this serves and what they're solving for
Marketing operations serves several recurring personas, each with distinct top priorities:
- **CMO / VP Marketing** — campaign performance visibility, brand consistency across channels and regions, agency oversight, budget pacing.
- **MOps director** — request intake throughput, taxonomy hygiene, team capacity visibility, single source of truth across the stack.
- **Creative ops / production lead** — designer queue, brief-to-asset cycle time, multi-round review and approvals.
- **Brand / compliance manager** (regulated industries) — legal review SLA, claims accuracy, version control on approved assets.
- **Demand-gen / content lead** — editorial cadence, channel attribution, lifecycle production.
- **Agency producer** — multi-client visibility, billable utilization, client-portal access.
The cross-cutting pain that drives this category into Airtable: _"swivel-chair work"_ across many single-purpose tools, no central source of truth for what's running where, capacity invisible until burnout, briefs lost in inboxes, budget vs. actuals reconciled manually each quarter.
## Before scaffolding: ask scope
Marketing operations cuts across CPG, apparel, financial services, healthcare, pharma, media, telecom, automotive, energy, hospitality, music labels, agencies, education, and nonprofit — even more broadly than product-ops. The "obvious" B2B-SaaS default fits less than a third of real-world cases. Lead with three scope questions, branch from there.
1. **Team and org shape.** Solo marketer / small (under 10) / mid (10-50) / large (50+) / enterprise (multi-brand or multi-region) / agency running multiple clients. Determines schema-shape default — an in-house team of 5 and an agency with 200 clients don't want the same scaffolding.
2. **Which sub-workflow first.** _"Marketing request intake, campaign orchestration, creative production, content calendar, brand and compliance review, event planning, budget and ROI, capacity planning, or something else?"_ Most users want one of these first, not all of them.
3. **Audience shape.** _"Are you marketing to named B2B accounts, broad consumer segments, both (B2B2C), or a multi-brand portfolio?"_ Determines whether the schema needs Accounts, Cohorts / Segments, both, or sub-brand tables.
Branch when relevant — but only when relevant:
- **Existing project / work-management tool?** (Workfront / Asana / Monday / Wrike / Smartsheet / ClickUp / Trello / Notion / Basecamp / MS Planner / none.) Many MOps setups have one. Airtable'Leer la fuente completa en GitHub (abre una página externa)