The SOPs and Playbooks Every MSP Marketing Team Needs

Ask an MSP owner how a lead gets qualified and handed to sales, and the answer is usually a story, not a process. Someone checks a few things. Someone follows up, eventually. It works, mostly, as long as that someone doesn’t get sick, take a vacation, or leave. That last part is the whole problem.

That’s the gap SOPs and playbooks close. Not paperwork for its own sake. The actual instructions for how marketing runs, written down somewhere other than one person’s memory. On paper. Or in a doc, at least, somewhere a second person can actually find it.

This is the playbook layer of what we call a marketing operating system, the connected platform, playbook, and execution layer that runs an MSP’s marketing as one system instead of a pile of disconnected tools nobody fully trusts. A platform without a playbook is just an expensive place to store contacts. SOPs are what make the playbook real instead of aspirational.

What Actually Counts as a Marketing SOP

The US Chamber of Commerce defines an SOP as detailed instructions and best practices for performing a specific business function. Applied to marketing, that means a written, repeatable set of steps for one task, specific enough that someone new could follow it without asking questions first.

A content calendar tells you what’s due. An SOP tells you how it actually gets made, reviewed, and published, the same way, every time. Same steps. Same order. Same checks before it goes live, whether the person running it has done it fifty times or once.

A playbook sits a level above that: the strategy and the sequence a set of SOPs exist to execute. An MSP needs both. Most have neither.

The confusion usually comes from how these get built in practice. A founder writes a rough process once, under deadline pressure, gets it mostly right, and never touches it again. Six months later a new hire follows it anyway, because it’s the only documentation that exists, even though half the steps describe tools the MSP stopped using in the meantime. Stale docs. Wasted hours. A new hire who thinks they’re the problem, when the doc is.

Why MSPs Feel the Gap Harder Than Most Small Businesses

This isn’t unique to marketing, or to MSPs specifically. SHRM’s research on institutional knowledge loss puts the cost of replacing a departing employee at 50% to 200% of their annual salary, depending on the role and how much of the job lived only in that person’s head rather than anywhere written down. The harder cost is the part that never shows up on an invoice. The context. The relationships. The process that walked out the door with them.

MSPs feel this harder than most small businesses do. The marketing function is usually one person. Sometimes one person doing it alongside three other jobs. When that person’s out, nobody’s running the playbook, because there’s no playbook written down to run. Nobody to hand it to, either.

This is part of why C4OS ships with a CMO-built playbook instead of just software. A platform with nothing telling you what to do with it just moves the same undocumented mess into a nicer interface. Same mess. Better login.

The Five SOPs Every MSP Marketing Function Needs

Five SOPs cover most of what actually breaks when marketing depends on one person’s memory.

• Content production. Who briefs it, who writes it, who reviews it, and what “done” actually means before it publishes. See our organic-first playbook for how the content motion itself should run, separate from the SOP that keeps it consistent.
• Lead handoff. What counts as qualified, who gets notified, how fast, and what context comes with it. Our appointment setting playbook covers how the handoff step specifically should run.
• Social and review response. Response time windows, tone guidelines, and when something gets escalated instead of answered from a template.
• Reporting. What gets measured, on what schedule, and in what format, tied to pipeline instead of vanity metrics.
• Campaign launch. The checklist before anything goes live. Tracking set up. Positioning checked. The right person signed off.

None of these are complicated to write. They’re just tedious to write honestly, which is exactly why most MSPs keep putting it off. A rough draft of all five, written badly, still beats the current default of having none.

Notice what’s missing from that list. Strategy isn’t an SOP. Strategy is the playbook’s job. SOPs are what execute the strategy the same way twice. That’s it. That’s the whole distinction, and it’s the one most MSPs blur until it costs them.

What Actually Happens Without One

The pattern is predictable once you’ve seen it a few times. A marketing hire leaves. The replacement spends the first six weeks reverse-engineering what the last person actually did, piecing it together from half-finished docs, old emails, and whatever the owner half-remembers being told once in a hallway conversation, because none of it was ever written down anywhere a second person could find. Campaigns that used to run every month quietly stop running. Nobody decided to stop them. Nobody was left who knew they were supposed to happen.

None of that shows up in a resignation letter. It shows up three months later. As a pipeline gap nobody can quite explain.

How This Fits the Rest of Your Marketing Operating System

SOPs are one of the four layers a marketing operating system needs: the platform, the playbook, an execution layer, and reporting tied to pipeline. Written SOPs are what turn the playbook layer from a slide deck into something a new hire, a fractional CMO, or an AI assistant can actually run.

That last part matters more every year. An AI assistant can execute a documented process. It can’t execute a process that exists only in someone’s head. Not yet. Maybe not ever. If an MSP wants any AI layer to actually help with marketing execution, whether that’s C4OS’s Claude skills or something else entirely, the SOPs have to exist first, because the AI is only ever as good as the process it’s been handed.

How to Start Writing Yours This Week

Don’t try to document everything at once. Start with whichever SOP would hurt the most if the person running it disappeared tomorrow. For most MSPs, that’s lead handoff or content production.

• Pick one process. Write down every step exactly as it happens today, not how it’s supposed to happen.
• Have someone who doesn’t normally do the task try to follow it. Every place they get stuck is a gap in the SOP, not a gap in them.
• Put it somewhere the whole team can actually find it. A shared doc nobody knows exists isn’t a system.
• Revisit it every quarter. An SOP nobody updates becomes a lie about how the work actually gets done.

One SOP, written this week and actually used, is worth more than five sitting half-finished in a folder nobody opens. Start small. Finish it.

Five SOPs, written honestly and kept current, do more for an MSP’s marketing consistency than almost any tool purchase. The tool matters less than most owners assume. The system around it is what actually holds up when someone’s out sick, on vacation, or gone for good.

If you’re not sure which SOP to write first, that’s worth a real conversation before you spend another afternoon guessing. Most owners guess wrong the first time anyway.

Book a Growth Strategy Call