What Happens to Your Marketing Systems When I'm Busy

There’s a fair question I don’t always get asked directly: what happens to the marketing infrastructure I build if I get busy for a few weeks?

It’s a reasonable thing to wonder about anyone who runs a side business alongside a full-time role, and I’d rather answer it before someone has to work up to asking. It has also shaped how I build, more than almost any other consideration.

How the question changed the way I build

I don’t design systems that need me checking a dashboard every day to keep working. Reports run on a schedule. Alerts fire on their own when something looks off, so a problem reaches the owner without waiting for me to notice it. And the documentation is written so someone else could open it and understand what’s happening without me walking them through it.

That last piece is the one people tend to underweight. Documentation is the thing that separates a system the client owns from a system the client rents access to. If the only explanation of how it works lives in my head, then it doesn’t matter how well the reports run, because the business is still dependent on me being reachable.

A dependency in infrastructure’s clothes

This is less about redundancy for its own sake and more about a definition. A marketing system a business can’t operate without its builder isn’t really infrastructure. It’s a dependency wearing infrastructure’s clothes.

The measure of a good system isn’t how impressive it looks in a demo. It’s whether it still makes sense to the business three months later, without me standing next to it explaining things.

Alerts are a good example of why. An alert that fires when a form stops submitting or a campaign’s spend jumps is only useful if it reaches the owner directly and says in plain words what to look at. One that sends me an email and waits for me to translate is just a slower way to find out.

I find that test uncomfortable, and useful. It rules out clever things that only I would understand, and it favors dull, legible ones. A report that arrives on the same day in the same layout beats a fancier one that needs me to interpret it, because the first keeps working when I’m unavailable and the second doesn’t.

What I’d ask anyone I was evaluating

If I were hiring someone to build my marketing systems, solo operator or agency, I’d ask what happens when they’re not immediately available. Not because I’d expect a perfect answer, but because the shape of the answer tells you a lot. Do reports run without them? Would someone else be able to pick up the documentation? Is there anything the business can only do by calling the builder?

An agency has more people to cover a gap, and a solo operator has to have done the work up front to make a gap survivable. Either way, the question is worth asking before you sign anything. And if you’d like to see what the handoff documentation for one of my builds looks like, I’m happy to show you.