Marketing Operations: The Operating Cadence Nobody Documents
Written by Martin J.
A campaign crosses five handoffs, and usually only one of them has a written rule. The rest run on memory until someone asks who approved what, and then the quarter is already gone. Which of your handoffs would survive a week without you?
Your launch slipped a quarter, and the meeting that agreed the new date could not name who was approving what. Thirteen weeks went somewhere, and the post-mortem will blame craft, capacity or the agency. What actually went missing was smaller and duller: a rule nobody wrote down for the five handoffs your campaign crossed on the way out. Every team believes it has a marketing operations process. The test is whether any of it survives the week the person carrying a handoff is on leave.
The date moved three times before anyone called it a slip. A week first, which nobody minded. Then a month, which got a new name and a phase two. Then a quarter, by which point the deck had been rebuilt around the new date. What stayed constant was the room: eleven people, one decision, no record of who took it.
The rules between those handoffs, written down and dated, are the whole subject. Marketing operations is the policy that sits between the handoffs: who accepts a request, when the clock starts, what complete means, and who signs off. A small body of writing rather than a department. In practice it comes down to four artifacts: an intake record, a clock on each request, a calendar of decisions and a register of tool owners. Your project tool will not show you the gap, because it records what someone typed into it, and nobody types the handoff.
The Handoff SLA: Five Transfers and When the Clock Starts
A campaign does not move through stages. It changes hands five times: someone writes the brief, builds the asset, approves it, launches it, and reports on what happened. A team usually has a written rule for exactly one of the five, and it is approval, because approval is where disagreements become visible in a meeting.
The failure is always in the same place. Briefs fail when the outcome was never a number. Builds fail when the audience was never defined. Approvals fail when the approver is on leave and no delegate was named. Launches fail when nobody re-booked the send time. Reports fail because nobody agreed, before launch, which number would count.
The gap shows up in research. In LeanData's 2026 B2B State of Martech and Revenue Operations report, 190 enterprise leaders across seven countries rated process and operations lowest of five maturity pillars at 3.66 out of 5, against 3.82 for people and teams, with the least improvement over three years. If that holds where staff are dedicated, it holds harder for your six-person team.
The clock-start rule is the detail almost nobody writes down. The default is to start counting when the request lands, so the email that arrives Monday begins its meter on Monday. That is the wrong start, because a request with missing information is not work yet. It is an idea with a due date.
Start the clock at triage instead. Triage means a named person has read the request, confirmed it is complete, and accepted it. Until that happens it sits returned, and it does not count against your capacity for the week.
After triage the work splits into four phases with a boundary each: intake, build, approval, data and launch prep. The Pedowitz Group publishes targets of 4 to 8 business hours for intake, 1 to 2 business days for a simple build, 4 hours for a low-risk single approver, and 4 to 8 business hours for launch prep on a segment that already exists. Read those as one consultancy's practice norm, not an industry median, and replace them with yours after a quarter of your own data.
Two notes before you build this. These are decision handoffs, and automating one before it has a written rule is how a team automates an argument. If you head that way, marketing workflow automation covers the machinery.
The Intake Form Is the Whole System
An intake form is a decision about what your team refuses to guess. Keep it short and the guessing moves into the build, where it costs a rewrite. Make it long and people route around it, which costs you the record. Etumos, a consultancy that publishes its intake playbook, names both failure modes: a form so long people avoid it, and a form with no triage that becomes a wishlist nobody works from.
The six fields that stop a rewrite
- The outcome in one sentence. Write "40 qualified demo requests from this segment by the end of the quarter", not "an ebook". Without it you will build the wrong asset well.
- The audience as it exists in your CRM. The exact list name, not a description of who you imagine. Without it someone rebuilds the segment during the build.
- The offer, including the price when there is one. A missing price is a rewrite waiting for the final week.
- The real date and its reason. An event date is a date. A preference for "sometime in March" is not, and it will be treated as one anyway.
- The approver's name, plus their delegate for the week they are away. Without the delegate, every approval waits on one calendar.
- The assets that already exist, and who owns each. Copy, images, legal-approved claims. Without this list the build starts from zero and duplicates work you already paid for.
Six is the number that holds up. Four and the form stops being a gate. Ten and people send you a message instead.
What to do with the request that arrives as a chat message
It will arrive as a chat message, and refusing it does not work. You need a reply you can send in ten seconds that keeps the record. This is the one I use.
"Thanks. Three things are missing before this can go into the build: the segment name as it exists in the CRM, the approver for the final copy, and the event date this has to be ready for. I have moved the slot from Tuesday the 14th to Thursday the 16th so the two review days survive. The ticket is set to Blocked until those arrive, so you can see where it sits."
That reply does four things at once: it names what is missing, it moves the date, it sets a visible status, and it puts the request into the same queue as everything else. What it does not do is accept the work on the sender's terms. The informal channel is where your SLA dies.
The Marketing Operations Calendar: Twelve Weeks of Decisions
A calendar of activities tells you what your team is doing. A calendar of decisions tells you when something is allowed to stop. The second one fits on a wall, and it does more for a quarter than any dashboard.
Twelve weeks, one decision per block. Week 13 is deliberately empty, and you should treat it as slack rather than capacity you forgot to fill.
Week | Block | The decision it forces |
|---|---|---|
1 | Intake reset | Which three open requests get re-dated this week, and who tells each requester |
2 | Capacity plan | How many build slots the quarter holds, and which request types get none |
3 | Brief review | Which briefs are approved as written and which go back before a build starts |
4 | Build lock | The last date an asset can enter the quarter, after which the answer is no |
5 | Approval tiering | Who is the single approver for low-risk work and who is the second for the rest |
6 | Launch window | Which campaigns launch now and which wait for a full window instead of a half one |
7 | Midpoint read | Kill or fund the two campaigns that missed their leading indicator |
8 | Register review | Which tool loses its owner this quarter and which renewal gets canceled before its notice date |
9 | Second build block | Which queued requests are refused outright because the capacity is already spent |
10 | Report refresh | Which numbers leave the report, and which owner presents each one that stays |
11 | Pre-close audit | What carries into next quarter, written down with the reason it slipped |
12 | Retro and rebuild | Which of the five handoffs failed most, and the single rule change that follows |
Two rows in that table need a warning attached.
Week 10 is about the meeting and the artifacts on the table, not which numbers deserve to be there. Metric selection is its own discipline and our guide to marketing KPIs does it properly.
Week 8 carries the one capability question this page does not answer: whether a recurring piece of work should stay a written rule or become something an agent runs. That comparison has its own answer in RPA vs agentic AI.
The week 7 midpoint is the block that earns the calendar its reputation, so run it in thirty minutes on one question: kill or fund each of the two campaigns that missed their leading indicator, and write the answer down with an owner.
The Stack Register: One Owner per Tool
Every tool in your stack needs one named person accountable for its configuration, its users, its integration health and whether anyone still uses it. That person does not have to be an administrator, and often should not be. The accountability has to be attached to a name, or it belongs to nobody.
The register is one sheet with five columns per tool: the tool, its named owner, its renewal date and notice window, the integration that would break first, and the team that depends on it. The notice window is the column that pays for the sheet, because that is where the money actually gets decided, and it is always earlier than the renewal.
Review the whole register once a quarter, in a session of 2 to 4 hours, and check four things: utilization, integration health, whether current usage still matches the case that justified the purchase, and which two tools now do the same job. That cadence is vendor-published advice, not independent research. It earns the time for one reason: a register with names on it stops being a list you rebuild from memory after someone leaves.
This section is deliberately not a build order and not a cost exercise. What to keep, what to merge and in what order to buy all belong to a different article, and martech stack is the one that does it. marketing automation tools covers the evaluation.
One line deserves its own rule: what happens the day an owner hands in notice. The new name gets written within the notice period, not after the account is orphaned. If nobody can be named for a tool, that is your first deletion candidate, and a better signal than any usage report.
The Two-Person Version: Six Calendar Blocks Instead of Twelve
You are probably reading this with two people and no specialist. The system still holds at that size, if you drop things on purpose instead of by accident.
What survives: the six-field intake, run twice a week in twenty minutes; the clock-start rule; a calendar of six blocks instead of twelve; and the register, reviewed once a quarter.
What gets dropped deliberately, said out loud so nobody expects it later: the weekly reporting cadence, which becomes monthly; the approval tiers, because two approvers is not a tier system; the capacity plan, replaced by a fixed number of builds nobody renegotiates in week 6; and the retro, folded into the monthly review.
What must never be dropped: the re-dated request and the Blocked status. Protect the calendar too. It is the only artifact your colleague cannot reconstruct from memory on the day it matters.
Frequently Asked Questions
What does marketing operations actually own?
The written rules between the handoffs, and the artifacts that hold them: the intake record, the clock on each request, the quarterly calendar, the stack register and the reporting cadence. It owns the decision about what counts as complete. It does not own the campaign.
What is a marketing operations SLA?
A published agreement about time, with a rule for when the clock starts. It names the phases, at minimum intake, build, approval and launch prep, gives a window to each, and states when a request counts as submitted. The clock starts at triage, not at submission. Without that rule you have a set of hopes with business days attached.
How is marketing operations different from project management?
A project tool records the status of tasks. The cadence decides what those statuses mean: what complete means, when the meter starts, who approves, and what happens when capacity runs out. You can run it on a board, in a sheet or in a tool built for it. Replacing the tool has never fixed a missing rule.
Install the Calendar This Month
Marketing operations earns its keep first as a calendar: twelve rows and a decision on each, the cheapest thing here to install and the fastest to prove. Allable keeps the brief, the calendar row, the asset and the publish date in one project, which makes the week 7 read possible without a chase. Start with week 1 this month. Add the clock-start rule to the next request that lands.