IT manager and managed service partner shaking hands in a modern office

For Capital Region IT directors and managers who have the skills, just not the hours, the bench or the backup.

Co-managed IT starts to make sense when your IT people are good, and there just aren't enough of them. Quick gut check: who handles nights? Vacations? Security? Same one or two names four times? Bring in a partner to take a piece of that, and your business gets safer while those two people get to breathe.

Most IT managers we meet at mid-sized Albany organizations aren't short on skill. They're short on pretty much everything else. Hours. Backup. Somebody to call at 11 p.m. when the firewall starts acting funny.

You know the week. Monday is password resets and a printer that's decided to retire. Tuesday a cyber insurance questionnaire shows up with 60 questions and a Friday deadline. Wednesday the CEO pops in to ask about the Microsoft 365 project you've been pushing back since April. And somewhere in there you were supposed to take a vacation.

That's not a performance problem. It's just the job growing, but the headcount didn't.

When does co-managed IT make sense?

Usually when one of three holes keeps popping up. Nobody's watching after hours (coverage). Security, network or compliance questions keep landing that your team's never dealt with (depth). Or nobody has a spare minute to think about where IT should be a year from now (planning).

People use the term loosely, so here's ours. Co-managed IT is an outside provider splitting the workload with your in-house staff. Your folks keep the steering wheel. We, or whoever you pick, take the chunks you decide to hand off.

Some signs it might be time:

  • Most of what anyone knows about your IT lives in one or two heads, so a resignation or a bad flu turns into a business problem
  • Anything that breaks Friday night waits until Monday
  • Tickets eat the day, and the security projects keep sliding into next quarter
  • The cloud move or network refresh has been "almost started" for months
  • Cyber insurance forms, client security reviews or the NY SHIELD Act are asking for proof your team can't easily pull together
  • The company keeps adding people and locations, and IT is still the same two folks

Nodding along at two or more of those? Then it's not a question of whether your team is good enough. It's whether any team that size could cover all of it. Check it here

Is your IT team short on skill, or short on hours?

Hours, almost every time. Here's the math nobody puts in a budget meeting. A week has 168 hours. Your IT person works about 40 of them, give or take meetings, vacation and the odd sick day. So, for the other 128, your systems are humming along with nobody looking.

Talent doesn't fix that. The sharpest IT manager in the Capital Region still needs to sleep, still heads up to Lake George in August, still catches whatever's going around. Coverage fixes it. Eyes on the servers, laptops and security alerts all night, and a help desk that actually answers when someone in billing calls at 7 on a Thursday.

That's usually where co-managed relationships start, because it's the easiest piece to hand off and the hardest to staff yourself:

  1. After-hours and holiday help desk for the people who don't keep 9 to 5 hours
  2. Overflow support for the weeks when tickets pile up or someone's out
  3. 24/7 monitoring and patching so updates and alerts don't depend on anybody's calendar

Where does a small IT team run out of depth?

Security, networking and compliance, mostly. Stuff that changes every few months, needs pricey tools, and comes up about once a year. You don't get great at anything you do once a year.

By depth we mean somebody who's already fixed this exact mess fifty times. On a normal Tuesday your generalist is fine. Then comes the week the VPN keeps dropping and nobody can say why, or the ransomware alert at 4 a.m., or the 200-question security review your largest client wants back by month end. That's when a small shop either guesses or loses three days to Reddit threads and vendor PDFs.

With a co-managed partner, your people finally have somebody to tag in. Escalations, threat hunting, the firewall nobody wants to touch, the big migration project, all of that can go to the bench. Your team keeps the relationships with your users. They just stop being the last line of defense on every hard question.

Who owns the long-range IT plan?

Honestly? At most mid-sized Albany shops, nobody does. On paper it's the IT manager. In real life the day to day eats every hour that could've gone into a budget, a roadmap or a security plan the board would fund.

This is the gap the corner office notices. Surprise invoices. Projects nobody can justify. The CEO asking "so what's the plan?" and the honest answer being "I haven't had a minute."

In a co-managed setup you get a vCIO, which is just a fancy name for a part-time CIO you share with other companies. They sit with your IT lead and help build the budget and a 1, 3 and 5-year roadmap. Your IT lead's name goes on it, and they're the one presenting it upstairs. The vCIO brings the frameworks, the benchmarks and the hours. Done right, this is the piece that does the most for your IT lead's standing with the leadership team.

What does a co-managed IT split look like in practice?

Most of the time your crew keeps user support, the business apps and IT strategy. The partner grabs nights and holidays, monitoring, patching, security alerts and backups. Network stuff usually lands somewhere in the middle. However you slice it, write the split down before anybody logs into anything.

One common co-managed IT responsibility split (TAG Solutions model)

Responsibility Your IT team Co-managed partner
First-line and onsite user support Leads Backs up overflow and after-hours
Escalations and complex issues Escalates Owns
After-hours and holiday coverage Informed Owns
Patching and monitoring Informed Owns
Security monitoring and response Informed Owns
Backups and recovery testing Informed Owns
Network and firewall Shared Shared
Business applications and vendor relationships Leads Supports
IT strategy and budget Leads Supports (vCIO)

Here's what the table can't show you. Does the partner go through your IT lead, or around them? The good ones hand credit to your team and wouldn't dream of strolling into the CEO's office with a tech issue your IT lead hasn't heard about. Ask them point blank.

Is co-managed IT cheaper than hiring another IT person?

Kind of depends what's missing. Short on coverage or specialist know-how? Co-managed usually wins, since a new hire buys you 40 more hours and one more brain. Just drowning in ordinary daytime tickets? Then yeah, maybe you need another person.

According to the U.S. Bureau of Labor Statistics, network and computer systems administrators earned a median of $99,130 a year as of May 2025. Benefits, tools and training come on top of that, plus however long it takes to find a good one in this market.

Second IT hire vs. co-managed IT: what each one covers

Question Second IT hire Co-managed IT
Nights and weekends? Only if you set up an on-call rotation Yes, 24/7
Specialist depth? Whatever that one person knows A whole team of specialists
Vacations and turnover? Partly, until they leave too Covered, and the partner already knows your setup
Long-range planning? Rarely vCIO support for your IT lead
How you pay Salary, benefits, tools, training Scoped monthly fee
Best when Daytime work is simply too much Coverage, depth or planning is the gap

Plenty of organizations end up doing both eventually. The trick is paying for the gap you actually have, not the one that's easiest to write a job posting for.

Who is co-managed IT not for?

Not everybody needs it. No IT staff at all? Fully managed is usually simpler. A big IT department with round-the-clock coverage and its own security people? You might only need help on projects.

It's also the wrong move when:

  • The real issue is daytime workload, and one more hire would solve it
  • Leadership quietly wants to replace the IT team and is calling it "co-managed" to dodge a hard conversation
  • Your team won't share documentation and admin access with a partner

Take that last one seriously. Co-managed only works when both sides can see everything. A partner who can't see your environment can't cover it at 2 a.m.

How TAG Solutions Approaches Co-Managed IT

TAG Solutions has worked with organizations around Albany and the Capital Region for more than 35 years. Since we sell both co-managed and fully managed, we don't care which box you check. We'd rather you land in the right one.

We start with your IT lead and a whiteboard, not an installer. Who owns what? Whose phone rings at 2 a.m.? Where does a problem go when it gets hairy? It all goes on paper. Then our engineers poke through your environment with 500-plus best-practice checks. Your IT lead gets the results as a starting line, not a grade. Your IT lead keeps making the calls, and you'll have one named Technical Alignment Manager on our side whenever a decision's needed.

There's a vCIO in the mix too, for the budget and the roadmap your leadership keeps poking about. And an IT Risk Score, so the CFO can see progress without a decoder ring.

We back everything with service guarantees.

Is your IT team covered, or just getting by?

This is a self-assessment, maybe 15 minutes. You'll see your score right away, how each area stacks up, and a list of gaps to bring into budget season.

If you want, you can schedule a 15-min call for free to review your results and evaluate your case.

What IT Leaders Ask Us About Co-Managed IT

How do I pitch co-managed IT to my CEO without sounding like I can't handle the job?

Talk about risk. Don't talk about workload. "We're slammed" earns you a sympathetic nod and nothing else. "Here are 128 hours a week where nobody is watching our systems" gets a meeting. Bring the insurance questionnaire you had to half-guess on, and the project that's slid three quarters in a row. Sketch what a partner would take while you keep running the show. Done that way, you're not the overwhelmed IT guy. You're the one who spotted a hole and brought a plan to plug it.

What should our internal IT team keep?

Whatever needs someone who knows the place. The people, the onsite stuff, the business apps, the vendor relationships, and the say on priorities and budget. That's the part an outsider can't easily replicate. The partner should get what needs eyes on it at 3 a.m. or tools you'd never buy for a team of two, like after-hours tickets, monitoring, patching, threat response and restore testing.

How many IT people do you need before co-managed IT makes sense?

One. Honestly, the one-person shop is where we see it help the most. If Mike in IT is the only one who knows the VPN setup, his honeymoon is a business risk. Two to five person teams use it a lot too, usually for nights, security depth and help with planning. With nobody in-house at all, you're really shopping for fully managed IT instead, where the provider owns support, security and planning top to bottom.

How long before co-managed IT actually helps?

First relief comes in a few weeks, when monitoring is running and after-hours calls stop going to your personal cell. The real payoff is more like a couple of months out. The partner has to get to know your setup, agree on the split on paper, and time changes around your team's calendar. Anyone itching to rearrange your network in week one? Red flag. The partnerships we've seen go well start small (listen, write things down, take the nights) and grow from there.

Isn't co-managed IT just a way for an MSP to get its foot in the door?

Some providers do use it that way. So put them on the spot. Ask if they sell fully managed too, and how they'd decide which one you need. Ask who'll be talking to your leadership team, them or your IT lead. Get the responsibility split on paper before any signature. A provider who's serious will handle all three questions in a couple of minutes, with your IT lead at the center of every answer. If they start hedging, that tells you plenty.

What happens to our documentation and tools?

Better than it was, if the partner's any good. You'll share one set of notes on passwords, configs and how-tos, which means either team can jump in when the other's out sick. The partner normally runs the monitoring and security software, and your people keep getting every alert and report. People skip this part all the time: spell out in the contract who owns those notes and where they go if you split up.