Michael Bannach
The IT director is on a beach for the first time in three years. On the second morning, the network switch at the satellite office fails, which takes down the phones, the printers and the connection back to headquarters for thirty-one people. The office manager there does what she has always done: she texts the IT director. He answers from the beach, because he is the only person who knows where the spare switch is, what the configuration on it should be, and which cable goes where. He spends the morning on the phone walking a salesperson through a wiring closet. Nobody at the beach house is pleased, and neither is the salesperson.
Nobody in that story did anything wrong. The company has a capable IT director, a reasonable budget and offices that mostly run fine. What it does not have is a second person who understands the environment. Every system, every vendor relationship, every password to the firewall and every undocumented decision about how the satellite office is wired lives in one head, and that head is supposed to be on vacation.
An IT department that is one person deep is a single point of failure with a salary
Co-managed IT is built for companies of one hundred to five hundred people with an internal IT team of one to five, and the director of that team carries an impossible job description. Help desk for every user. Projects, from the new phone system to the office move. Security, which now means the cyber insurance application, the customer questionnaires and the thing the CFO read about in the news. Vendor management for the carrier, the copier company, the line-of-business software and whoever sold the firewall. And, in a multi-site company, physically being in several places at once.
The usual response is to hire. A second technician helps with the help desk and does nothing about the fact that the director is still the only person who understands the environment. A regional technician for each office is rarely affordable and still leaves every site without coverage at night, on weekends and during vacations. Meanwhile the director spends the week on password resets. The roadmap, the budget and the security program keep sliding to next quarter.
What co-managed IT changes, and what it leaves alone
Co-managed IT splits responsibility between two teams. You keep your IT director and everything that should be his: strategy, budgets, the key vendor relationships, the relationships with the people who use the systems. An outside team takes the parts that need coverage more than they need the director’s judgment: monitoring around the clock, patching, security operations, backup, after-hours coverage, and dispatch to the remote sites. The split is written down in a one-page matrix before anything starts, and it can be adjusted quarterly as the internal team grows or the business changes.
The part that gets underestimated is the tooling. A good co-managed arrangement gives your internal team access to the same remote monitoring and management platform the outside team uses, with shared dashboards and shared alerts, and a documentation and asset management platform both teams keep current. That is what turns the switch failure into a ticket somebody else owns. The site drops off the dashboard both teams watch. Someone triages it from the alert. A technician near the office is dispatched, and the documentation says where the spare is and what goes on it. The IT director reads about it the next morning, if he reads email on vacation at all.
A non-profit client with more than two hundred employees, five offices in the Northeast more than three hundred miles apart, had the same problem without the beach. Their IT director at headquarters oversaw everything, and the remote offices had nobody on site. A failed printer, a downed switch or a new hire at a remote office meant dispatching from headquarters or asking untrained staff to triage until help arrived. We put field technicians near each office, monitoring across every location around the clock, a shared ticketing system both teams work from, and standardized documentation for every site. The director kept strategy and vendor decisions. By our count the arrangement comes to more than a hundred thousand dollars a year in cost avoidance, and their IT director put it in one line: “Our IT Director now can lead strategy, not logistics.”
What it is not
Co-managed IT is the wrong answer for a few kinds of companies. If you have no internal IT and want technology fully handled, that is managed IT, a different arrangement. If you want contractors on call with no shared tools or process, this is not that. If your internal team is not willing to share visibility and documentation, the model does not work, because the whole point is that two teams can see the same environment. And if what you need is a single project with no ongoing relationship, buy a project.
What the first ninety days look like
You get a documented onboarding plan with dates before you sign anything. Within the first ninety days the shared platforms are in place. Onboarding, patching and escalation runbooks are standardized across every site. On-site dispatch and after-hours coverage run on an agreed service level that gets reported on. The written split of responsibilities is in force. The IT director’s calendar starts to have room in it for projects and strategy, and the quarterly roadmap review becomes the place those get decided rather than deferred.
Pricing is quoted in writing after a twenty-minute call and a short discovery. The arrangement typically costs less than one mid-level IT hire.
Three questions for your IT director
- If you were unreachable for two weeks, what would break first, and who would fix it?
- How many hours last month went to password resets and printer problems, and how many went to the roadmap?
- Which of our systems is documented well enough that someone who has never seen it could restore it?
A director with coverage answers all three with names and dates. A director without it already knows the answers and has not had the budget to change them.
How we handle it
Your director gets a bench. Senior engineers for escalations and the projects that never get started, vCIO guidance for the budget and roadmap conversations, and access to the same RMM and documentation platforms we use. Your company gets the coverage: 24/7 infrastructure monitoring, patch and policy management, centralized security management, backup monitoring with recovery readiness testing, and one escalation number with one accountable team behind it. Leadership gets an executive reporting cadence with a named owner and evidence that holds up with auditors, insurers and customers. If it ever ends, you get transition assistance with documentation and access handed over in writing. And the next time the office manager calls about a dead switch, the person who answers is not on a beach.
If you want a plain read on where the company stands before the next vacation, the three-minute IT and security scorecard turns your answers into a written roadmap, and the conversation after it is free.
