The vendor handoffs quietly eating your week

It is Thursday, and you are counting the threads. Your managed service provider opened a ticket about a laptop that will not enroll. Your managed security provider flagged a sign-in they want someone to confirm is legitimate. The cloud consultant you keep on retainer answered Tuesday's question with a question of his own. None of these is hard. None of them is yours. And all three are sitting in your inbox because you are the only person who can see all three at once.

So you do what you always do. You forward the security provider's alert to the managed service provider, because the account lives in the system they administer. You answer the consultant by relaying what the security provider told you last week. You set up a call to get two of the vendors talking, and it produces an action item that needs a fourth person who is out until Monday. By the time you close the laptop, you have done no technical work at all. You have moved information between people who could, in theory, talk to each other directly.

That feeling, that you are the router and not the operator, is worth naming. It is the cost nobody put on the invoice.

A common setup for a growing company looks sensible on paper. A managed service provider runs help desk and devices. A managed security provider, usually called an MSSP, watches for threats. A consultant or two covers the parts that need depth, the AWS account or a tricky Microsoft 365 migration. Each vendor is competent. Each owns a clear slice.

The trouble is not inside any slice. It is in the gaps between them, the seams. Identity is the classic one. Your managed service provider administers Microsoft Entra because they run M365. Your security provider monitors sign-ins to that same Entra tenant because watching for compromise is their job. When a Conditional Access policy needs to change, who owns it? The honest answer at most companies is whoever you forward the email to, which means you.

The seams collect work because no contract drew a line through them. The result is a steady tax that never appears as a line item:

• Relaying context between vendors who do not share a system or a thread, so the same facts get retyped three times.
• Deciding which vendor owns a problem before anyone can start on it, which is itself a judgment call that lands on you.
• Confirming that a handoff truly closed, because "we thought they had it" is the most expensive sentence in operations.

Here is the quiet shift that happens as a stitched stack grows. The vendors do not integrate with each other. You integrate them. Your attention becomes the connective tissue that holds the arrangement together, and that is a strange thing to discover you have been hired to be.

It shows up in the calendar first. The status calls, the forwarding, the "looping you in" replies, the follow-ups to make sure a thing got done. None of it is technical, so none of it feels like progress, and yet it fills the day. A study from Asana found that knowledge workers spend a large share of their week on coordination, the relaying and meeting and chasing it calls work about work, with skilled work squeezed into what is left (figures vary by role and year, so treat the specific percentage as unverified). For an operations director steering three or four vendors, that ratio gets worse, because every external party is one more boundary you personally have to span.

The work was never the laptop or the alert. The work was the relay, and the relay does not scale, because it lives entirely in your head and your inbox.

The deeper problem is accountability. When something falls through a seam, there is no one to ask, because the seam belongs to no one. The managed service provider points at the security provider, the security provider points at the consultant, and all three are correct, because the task genuinely sat in the space between their contracts. The only person who can be held to it is the one holding all the threads.

Fixing this is not about firing vendors or pretending one company can do everything. Some work genuinely needs a specialist, and a good operating model keeps that specialist available without making them your day to day. The fix is to stop being the integration layer yourself and to push the seams onto someone whose job is to own them.

Three changes do most of the work:

• Put every request into one tracked place with an owner and a status, not a scatter of inboxes and phone numbers. When a laptop will not enroll, it becomes one item someone is accountable for, the way our submit a request flow is built to handle, so it stops being an email you have to chase.
• Name the owner of each seam in advance. Decide on paper who holds identity, who holds the cloud account, who closes the loop on a security finding. The point of naming it is that the next ambiguous task already has a home before it reaches you.
• Demand that handoffs happen below your level. A finding from the security side should reach the person who acts on it directly, with you able to watch it close, not relay it. If a handoff still routes through your inbox, the seam is not owned yet.

This is what one partner across the layers buys you, and it is the part a price sheet cannot show. Integration is not the absence of specialists. It is the presence of someone accountable for the spaces between them, so those spaces stop being your second job.

Walk back to Thursday and the three threads. The laptop, the sign-in, the consultant's question were each small and each genuinely belonged to a capable vendor. What made them yours was the space between those vendors, the relay only you could run. That is the work eating your week, and it is invisible precisely because it never looks like work.

The number to find is not how many tickets you closed. It is how many hours you spent moving information between people who should have been moving it themselves. Count that for one week and you will see the size of the tax. So the question to sit with is this: of everything that reached your desk this week, how much was the actual job, and how much was being the connective tissue your vendors never had to build?