The capacity your five-person team is already sitting on

You run a five-person company, and four of those people do the actual work that customers pay for. The fifth person is you, some weeks. The other weeks you are the head of sales, the office manager, and the person who answers the help desk vendor when they email asking which laptop belongs to the contractor who left in March.

Here is the thing nobody puts on the org chart. You are not short on people. You have a managed service provider running your help desk. You have a tool watching your cloud. You have a compliance platform collecting evidence. You have a consultant on call for the hard questions. On paper, you have a security and operations function that a company three times your size would recognize.

So why does it still feel like the whole thing rests on you? Where did the capacity go? It did not vanish. It is sitting there, fully paid for, in the gaps between the vendors you already hired. This is about finding it.

Count where a typical week goes. Not the work itself, the work about the work.

• The email thread where you tell the help desk vendor what the cloud consultant already told you, because the two of them do not share a system.
• The meeting where you reconcile what your compliance platform says is true against what your environment is doing.
• The follow-up where someone asks who owns the identity provider, and the honest answer is that nobody does, so it falls to you.

None of that is on a price sheet. It does not show up as a line item, which is exactly why it is so easy to miss. The coordination tax is real work; it gets paid in your evenings, not your budget. A small team does not lose capacity to laziness or bad tools. It loses capacity to seams.

When you buy your information technology from one vendor, your security monitoring from a second, and your audit evidence from a third, you have not bought a team. You have bought three contracts and the job of stitching them into something that behaves like a team. That stitching job has an owner, and the owner is you.

This is the difference between a stack that is integrated and one that is merely assembled. Integrated means the request you file, the change that gets made, and the proof it happened are the same thread. Assembled means they are three threads, and you are the only person holding all three.

The capacity is not missing. It is spent translating between vendors who were never set up to talk to each other.

Research on context switching is consistent on the cost of this kind of fragmented attention. One widely cited study from the University of California, Irvine found that after an interruption it took workers an average of 23 minutes to return to the original task (Gloria Mark's interruption research, UC Irvine). A five-person company cannot spare many of those.

The fix is not more tools, and it is not a bigger team you cannot yet justify. It is removing the seams by putting the layers under one operator who is accountable for all of them.

When identity, devices, and M365 are run by the same people watching for threats, and that same operation is the one collecting your audit evidence, the translation work disappears. You stop being the integration layer. The hour you used to spend forwarding context becomes an hour you spend on the company.

A few concrete shifts a founder notices first:

• The "who owns this" question stops landing on you, because one partner owns the whole environment, including the parts that used to fall between vendors.
• Audit evidence stops being a fire drill, because it falls out of running the environment properly and is ready before the auditor asks.
• The help desk request, the security change, and the record of both live in one place, so following up takes a glance, not an investigation.

We should be honest about where this does not apply. If you are a 10-person company with two laptops and a single cloud account, you do not need an integrated operation; a good point tool and a capable friend will carry you for a while. The math changes as the seams multiply, usually somewhere around the time a customer sends you a security questionnaire with a deadline.

Walk back to that Tuesday where you were the help desk, the head of sales, and the office manager inside the same afternoon. The work that drained you was almost none of it the real work. It was the coordinating, the translating, the holding of three systems in your head because no one else was positioned to.

A small team gets powerful not by hiring its way out of that, and not by buying a fourth tool to watch the other three. It gets powerful when the layers it already pays for stop needing a human router in the middle. The capacity was never the problem. The seams were.

So the question worth sitting with this week is a simple one: of the hours your team spent, how many went to the work itself, and how many went to keeping the vendors in sync?