What Four Years Inside a $3 Million Marketing Agency Taught Me
Why your business still runs through you
You told yourself you were closing the laptop at four, and here you are at twenty to five, standing at the kitchen counter with it still open next to the fruit bowl, answering a question you know you have answered before.
It is not a big thing, which is exactly why it keeps happening. Somebody on your team wants to know how to handle a client request, and you could type out the answer in about four minutes, so you type out the answer in about four minutes. That is faster than fixing the reason she had to ask you in the first place, and you will tell yourself the same thing tomorrow when the next one comes in.
Nobody would call this a crisis. Your clients are happy, the money came in this month, your team is good people who are trying. From the outside your business looks like the thing you always said you wanted to build, and most days it feels like that too, right up until about half past four in the afternoon.
What you are actually looking for is not a quicker way to answer that question. You are looking for a business where the question does not come to you at all.
Key takeaways on why growing businesses stay chaotic
A business can grow for years with every important method sitting in one person's head, and nobody notices, because the work keeps getting done.
The riskiest systems in your business are usually the private ones your people built quietly to survive their own workload.
You cannot improve a process you have never written down, which is why capture always comes before change.
Standard beats clever, because one decent method everybody follows will always outperform five brilliant methods nobody shares.
Documentation without a review rhythm goes stale in about ninety days, and that is why most SOP projects fail on the second read rather than the first.
What operational architecture covers, and what it does not
I use the phrase operational architecture a lot, so let me be plain about what I mean by it before we go any further.
What sits inside it
How work moves. The path a piece of work travels from the moment it is requested to the moment it is delivered, and whose hands it passes through along the way.
Where the method lives. The place your team looks to find the right way to do something, close enough to the work that finding it takes seconds instead of a hunt.
Who owns which outcome. Not who does which tasks, who owns the result. The difference shows up in who gets asked when it goes wrong.
How your tools are set up. Your software configured to carry the process, rather than five apps each holding a piece of it and you holding the rest.
How it stays true. The rhythm that catches drift and updates the method before your clients are the ones who notice.
What sits outside it
Marketing strategy. What you sell and who you sell it to is your call, and always will be. My side of the line is making sure it gets delivered the same way every single time.
Sales coaching. Nobody needs to teach you how to close. You closed your way to where you are standing.
Mindset work. Real and valuable, and a different job than this one.
Buying more software. New tools laid over a broken process will only get you a faster broken process and another subscription.
Hiring your way out. A new person inherits whatever chaos is already there and adds herself to it.
Here is a test you can run on your own business this week. Take the thing your business does most often, then ask yourself whether two different people on your team would do it the same way without checking with you first. If the answer is no, then what you have is a method problem, and no amount of hiring will fix it.
Five signs your business processes live in someone's head
I spent about four years inside a marketing agency doing around three million a year, and I came in the door as an assistant. Operations found me there. I did not go looking for it.
What happened was that the CEO started coming to me. Not for admin, for opinions. What did I think about this move, how should we handle this client, what was I seeing that she was not. I ended up in the strategy calls, in client retention, in client experience, implementing the marketing systems and untangling how the team spent its time. None of that was written in my job description. It landed on me because I was the person who understood how the work actually moved through the place.
These are the five things I watched from that seat, and I have seen every one of them since in businesses far bigger than that one.
1. You are still the answer key
The same questions keep finding their way back to you, and they are not new questions. You answer them quickly because answering is genuinely faster than fixing, and every time you answer quickly you teach your team one more time that you are where the answers live. It is a kindness that costs you your afternoons.
2. Everybody has a way, and everybody's way works
Ask three people on your team how they onboard a client and you will get three sincere, slightly different answers. Nothing looks broken from where you are sitting, so nobody raises it with you. Then one client gets a noticeably different experience from the last one, and you cannot put your finger on why.
3. Your client finds the problem before you do
There is no checkpoint sitting between the work being finished and the work reaching the client, which means your quality control is your reputation and your reputation is finding out last. This is the sign that usually costs you a client before it costs you a change.
4. One person is the only person
Somewhere in your business there is a thing only one person can do. The reporting, maybe, or the offboarding, or a whole platform that only she knows how to log into properly. Everybody knows who she is. Nobody has ever sat down and worked out what happens if she gets sick, or hands in her notice, or simply takes the two weeks she is owed.
5. The business grew and nobody wrote a thing down
This is the one I lived, so let me break it down.
At that agency I built my own little systems just to survive my own workload. A ready to repurpose content system, because I was making the same thing over and over in slightly different shapes. A process for optimising Google Business profiles, because we did a lot of them and I was tired of thinking it through from scratch every time. They worked and they saved me so many hours.
Nobody asked me to build them and nobody asked me to write them down, so they lived in my head and in my own files, and the day I left they walked out of the building with me. The agency did not lose a system that afternoon. It lost something it never knew it had in the first place.
If you want to see what this is costing you in real dollars before you read on, run the Cost of Chaos Calculator. It takes a few minutes and it hands you a number instead of a feeling, which is a much harder thing to ignore.
How to document your business processes in five steps
The order here matters more than any single step, and most people start at three or four, which is exactly why their documentation projects stall out around week three. You cannot standardise what you have not captured, and you cannot maintain what nobody owns.
1. Capture what is already happening
Before you change a single thing, write down how the work is being done right now, including the parts you are not particularly proud of. Sit with each person and have her walk you through her real process rather than the tidy version she thinks you want to hear. You are after the truth here, not the ideal. Expect this to take a week or two, and understand that it is the one step you cannot skip.
2. Pick one way and make it the way
Now look at the three versions you just captured, and either choose the strongest one or build a better one out of the best pieces of each. Then say plainly, out loud and in writing, that this is how it is done from now on. Standard beats clever every time, because a decent method everybody follows will always beat a brilliant method only one person uses.
3. Put the method where the work happens
An SOP sitting in a folder nobody opens is a document, not a system. The method belongs inside the tool where the work actually gets done, as a task template, a checklist on the card, a field that has to be filled before the thing can move. If somebody has to go looking for the instructions, she will guess instead, and she will guess differently to the person beside her.
4. Give every recurring outcome an owner
Owning tasks sounds like "I sent the report." Owning an outcome sounds like "reporting is handled, and here is what it is telling us." One of those tells you something happened. The other means somebody is watching it for you. Write the owner's name beside each recurring outcome, tell her directly, and then let her do it without you checking over her shoulder.
5. Build the review before you build anything else
Set the rhythm while it is all still fresh, because monthly is enough for most of it. Somebody opens the process, checks it against how the work is genuinely being done that month, and updates whatever has drifted. Ninety days is roughly how long good documentation stays true without that, so put it in the calendar now. Don't rush de brush, but do put the brush back in the same place every time.
P.S. I'm from Barbados and Don't rush de brush is a saying we say here meaning, take your time but be diligent.
What I learned running operations inside a marketing agency
I want to be honest with you about whose story this is, because I think it matters.
That agency was not my client. I was on the inside, on payroll, and most of what I have just told you I learned by being the person all of those gaps landed on. When something fell between two people, it fell on me.
The moment it clicked was small and unremarkable. The CEO came by and asked what I thought we should do about something well outside anything I had been hired for, and I realised she was not asking because of my title. She was asking because I was the one who knew how the work moved, and it turns out that knowing how the work moves is the most valuable thing in a growing business, and the thing almost nobody is looking after.
The first thing I ever properly fixed there was not glamorous either. One repeatable process, written down, for work that had been getting done slightly differently every single time. That was it. No overhaul, no new platform, no big reveal at the end.
I tell you about the small first step because the big ones will not hold without it. Every business I have worked in since has started in that same unglamorous place, and not one of them expected to.
What poor business systems cost you in hours and money
Do this arithmetic yourself, because your own numbers will convince you far better than mine will.
The hours. Count up the questions that came back to you this week that you had already answered before. Give each one ten minutes, which is generous to you and probably still short. Twelve of those is two hours gone, and two hours a week is more than a hundred hours a year of you explaining things you already know to people who could have read them.
The money. Take whatever an hour of your time is worth to this business, and multiply it by those hours. That is the amount you are paying yourself to do work that nobody in their right mind would pay you to do.
The one that is neither. Trust is the third cost and it never shows up on a spreadsheet. When one person is the only person, you are carrying a risk you have never priced. When your client spots a slip before you do, you spend something you cannot bill for and cannot get back. And when your team keeps asking instead of deciding, they are not learning to own anything, which is a slow cost that turns up eighteen months later looking like turnover.
Pro tip. Most people document the hardest thing first, because the hardest thing is what worries them at night. Start with the most frequent thing instead, because frequency is where the money is hiding. A process you run four times a week pays back the effort inside a fortnight. That complicated annual one can wait until you have proven to your team that writing things down actually makes their week lighter.
Five questions to ask before you hire an operations manager
Ask these of anybody you are thinking of handing your operations to, and please ask them of me too. If somebody gets tetchy about being asked, you have learned what you needed to learn.
1. What is the first thing you would fix, and why that one?
You want a specific, small answer with a reason attached to it, something tied to how often the thing happens or how much it would hurt if it broke. If she wants to overhaul everything before she has looked at anything, she is selling you a package rather than solving your problem.
2. How will my team learn this without me sitting in the room?
Listen for training and recording, not just documents. Anybody can hand you a folder full of processes. The actual work is getting the method into your people's hands so it survives after the pretty documents are delivered.
3. What happens to all of this once you are gone?
A good answer includes a maintenance rhythm and a named owner on your side of the table. If everything she builds needs her forever to keep standing, then all you have done is swap one dependency for a more expensive one.
4. Which of my tools would you get rid of?
Somebody who only ever adds is looking at her own preferences rather than at your business. A good operator will happily take something away, and will be able to tell you exactly what it was costing you to keep it.
5. What do you need from me, and how many hours will it take?
You should get a real number, broken down by phase. If the answer is vague, the plan is still living in her head instead of on paper, which is the same problem you were hiring her to solve.
Where to start building systems in your business
Here is what I want you to take away from those four years of being the person who knew how the work moved.
Your business is not chaotic because you are disorganised, and I need you to hear that properly, because most women in your position have quietly decided it is a personal failing. And it is not. Your business is chaotic because it grew faster than anybody wrote anything down, and writing things down stays nobody's job until you make it somebody's job. Growth hides this beautifully. The work keeps getting done, the money keeps arriving, and the whole structure stays balanced on a handful of good people who happen to remember things.
That balance holds right up until the day it does not, and the day it does not is never a convenient one.
You built something extraordinary. And now it's time to optimise it so it runs without you holding it together.
If you want to know exactly where your business is leaning on you, start with a Sanity Session. It is a paid session, and you get a ninety minute diagnosis call plus your Sanity Map, a PDF naming your dependency points, your leaks, and the first three fixes in the order they should happen. I take four to eight of these a month, and one per business, ever.
Common questions about documenting business processes
How long does it take to document a process properly?
For one recurring process, expect a few hours of capture and a few hours of writing, spread across a week. The capture part always takes longer than people think it will, because you are recording how the work is genuinely done rather than how it is supposed to be done. A full set of core processes for a small team is usually a thirty day piece of work, which is why The Reset is built as a sprint of thirty days or less.
Do I need new software to do this?
Almost certainly not. Most businesses already own everything they need and are using about a third of it. Before you buy anything, look properly at what your current project tool can do with templates, checklists, and recurring tasks. New software laid over a broken process gives you a faster broken process and another line on the card.
What is the difference between an SOP and operational architecture?
An SOP is one document describing one process. Operational architecture is the whole structure around it: how work moves, where the methods live, who owns which outcome, how your tools are configured, and how all of it stays current as the business changes. SOPs are one part of it. Having a folder of SOPs and having operational architecture are two very different situations.
My team is only three people. Is it too early for this?
Three is the right time. The cost of documenting climbs with every person you add, because each new hire learns the undocumented version from the last one and adds her own flavour to it. Doing this at three people is a project. Doing it at ten is an excavation.
Why do you require a twelve month commitment for the retainer?
Because the change is sequenced. Capture, then standard, then getting it into the tools, then ownership, then maintenance. Each stage depends on the one before it, and habits take a great deal longer to set than documents take to write. A shorter term would let me build the structure and leave before it holds, and that is a promise I am not willing to make to you. Scale With Sanity is my monthly retainer, on a twelve month commitment, and I take three anchor clients at a time. You can apply here.
What if I have tried documenting things before and it did not stick?
Nearly everybody has, and it usually failed for one of two reasons. Either the documents lived somewhere nobody worked, or nobody owned keeping them true. Both are structural problems with straightforward fixes, and neither one is a failure of discipline on your part.
Can I start smaller than a retainer?
Yes, and most women do. They start with a Sanity Session to find out what is actually wrong, then take one Reset to fix the biggest leak in thirty days or less. The retainer is for when you want the whole structure built, held, and maintained rather than one piece of it repaired.
