Signs Your Agency Needs SOPs

If you searched for signs your agency needs SOPs, you likely already suspect the answer and want either permission to act on it or permission to wait. I have spent twelve years running delivery operations for marketing agencies, and procedure work is now part of what I sell, so read everything below with that declared. What most pieces on this topic skip is the second half: which signs are real, and when the honest answer is that you are not there yet.

What are the signs an agency needs SOPs?

Four of them come up more than any others, in agencies from five people to fifty. Each one looks like a people problem on the surface and turns out to be a documentation gap underneath.

1. The same question gets answered from scratch, every time it is asked

Someone messages you, or your ops lead, or whoever is closest, and asks how to handle something the agency has handled a dozen times before: what to do when a client wants a scope change mid-sprint, how to word a late-payment follow-up, what the escalation path is when a deliverable is going to miss its date. The answer gets typed out fresh, in a DM, and then it disappears into scroll history the moment the conversation moves on.

This looks like a training problem. It is not. Training assumes the answer only needs to be given once and will stick. It will not stick, because the person asking is not going to remember a Slack message from March when the same situation comes up again in September, and neither will the next person who joins the team and has never seen it at all. The question keeps costing someone’s time because the answer was never moved anywhere durable.

2. The same task, done by two different people, produces two different results

Put the same deliverable type in front of two capable people on your team and you get two different structures, two different levels of detail, two different definitions of finished. Clients notice this even when they cannot name it. They just experience your agency as inconsistent depending on who they happen to be working with that month.

The instinct is to blame the weaker of the two people. That is usually wrong. Two competent people producing different output on the same task is what happens when there was never a shared definition of what the task actually requires, so each of them built their own, reasonably, from their own judgment. The gap is not a skill gap. It is the absence of a shared answer to write once instead of two people each getting to a good-enough answer separately, every time.

3. A new hire needs most of a quarter before you trust them alone

Three months is a long runway for someone to become independent on work your team has been doing for years. Ask what is actually happening during that quarter and it is rarely formal training. It is the new hire shadowing people, asking questions as they hit them, and slowly assembling a private, incomplete version of how the agency works, one conversation at a time.

That ramp time is not really about the person. It is a measure of how much of your delivery process exists only as something someone has to be told, rather than something someone can be shown. Every week that a new hire spends reconstructing the process by trial and interruption is a week the people training them are not doing their own work either.

4. One person leaving would take a working procedure with them

You can usually name the person. Maybe it is whoever runs client intake from memory, in an order that only makes sense inside their head, or whoever has quietly become the only one who knows every exception to how your invoicing actually works. None of it exists on paper, because they never needed it written down for themselves.

The risk here is not that they will leave tomorrow. Most of the time they will not. The risk is that the agency has no way of finding out how much would break until it happens, and by then there is nobody left who remembers what the process was supposed to be. The fix is not asking that person to write everything they know in one sitting before they go. It is capturing the recurring parts of what they do while they are still doing it, inside the tools the work already lives in. I do this work inside ClickUp, Asana, Monday.com, Airtable and Notion, connected with n8n where a step should run itself rather than be written down as an instruction, and the platform is almost never the reason the knowledge stayed in one head instead of a shared document.

When is it too early for your agency to bother with this?

Two situations make SOPs the wrong move right now, and both are more common than the sales copy around this topic likes to admit.

The first is a process that changes every week. If how you deliver a service is still being figured out, in genuine flux rather than settled and merely undocumented, writing it down produces a document that is wrong before anyone reads it twice. Documentation records a decision. It cannot make one. Let the process hold still for a stretch first, then write down what it settled into.

The second is size. Below a certain headcount, usually somewhere under five or six people, everyone is close enough to the work that the overhead of building and maintaining procedures can cost more than the inconsistency it would fix. If the same three or four people are doing nearly everything, the knowledge is already shared by proximity. A procedure library at that size is often something built to feel organized rather than something the team actually needed yet.

If neither of those describes you and at least two of the four signs above have been true for a while, not just during a busy stretch, that is the difference between a rough month and something structural.

None of this is the full symptom picture either. SOPs are one piece of a wider operational picture, and if what is bothering you does not quite match any of the four above, the broader set of signs is worth reading: signs your agency needs operations help.

So does your agency actually need SOPs right now?

My verdict, bias declared again: if two or more of the four signs above have been true for a full quarter and your team is past five or six people, yes, and waiting mostly costs you the compounding version of the problem rather than the current-size version. The same question keeps getting answered from scratch, the quality gap keeps showing up in client-facing work, ramp time keeps eating a quarter of every new hire, and the risk sitting in one person’s head keeps growing with every month it stays there. Twelve years running this work across 92 completed engagements is the basis for that read, and it is exactly the kind of record worth asking anyone making this argument to show you.

If the four signs describe your agency but you would rather understand how to actually build a procedure library that survives past its launch week, I have written the how-to version separately: how to build agency SOPs. This piece was only meant to answer whether you need to.

Where to start

You do not have to work out which of the four signs matters most on your own, or guess at what order to fix them in. If you would rather this were diagnosed and built rather than self-assessed from an article, that is what SOP consulting is for. Either way, the first step I recommend is the Agency Ops Audit: a $1,500 fixed-fee review, two weeks, a written 90-day roadmap and a 60-minute readout call, that tells you which of this actually applies to your agency and what to fix first. It is recommended, not required: a retainer can also begin after a scoping call. If the honest answer is that you are not there yet, that is what the audit will tell you, and it will have cost you very little to find out.