Internal IT team working alongside a managed services provider — RDI Solutions co-managed IT

Co-Managed IT

Keep Your IT Team. Hand Us the Rest.

Co-managed IT for NYC and Long Island businesses with their own IT staff. Take NOC device and network management, a managed help desk, or the security stack — and leave everything else where it is.

You already have an IT team. You do not need to replace them. You need the parts of the job that are stopping them from doing the work you actually hired them for.

RDI can be your fully outsourced IT department, and for a lot of businesses that is the right answer. But our managed IT plans are built from individual services, not sold as one block, which means we can take a defined piece of the workload and leave the rest with your team. That is co-managed IT: you decide where the line sits, and it is written down.

The two most common splits

Almost every co-managed conversation we have starts in one of two places. Which one sounds like your team tells us most of what we need to know.

You keep the help desk

RDI takes NOC device and network management

Your internal team is good with your users and knows your business. What you do not want them spending their week on is patch cycles, firmware, and watching monitoring dashboards. We take the infrastructure layer and leave the people layer with you.

RDI handles

  • Operating system and third-party patch management
  • Network monitoring and alerting
  • Proactive device maintenance and remediation
  • Server monitoring, patching and after-hours alerting
  • Escalation when something needs a human before your team notices

You keep the projects

RDI takes the managed help desk

Your team is working on migrations, applications and infrastructure, and every password reset pulls them off it. We become the help desk your office staff call, so the project work stops getting interrupted.

RDI handles

  • Remote support for your office staff, answered by our own team
  • Day-to-day troubleshooting, access issues and application questions
  • Ticket triage, with escalation to your team only when it belongs there
  • Weekday or round-the-clock coverage, depending on how you work
  • Ticket reporting so you can see what your users are actually asking for

Plenty of arrangements sit between the two, or combine them. Security services can be layered onto either split, and a lot of internal teams take the security stack from us precisely because it is the piece that is hardest to run well with limited headcount.

Build the plan from the pieces you need

Our managed IT services are quoted as separate line items. A fully managed client takes all of them. A co-managed client takes the ones that fill their gap and pays for nothing else.

ServiceWhat it coversOften taken when
NOC device managementProactive monitoring, patch management, remediation and escalation for every workstationInternal IT is user-facing and does not want to run patch cycles
NOC server managementThe same for physical and virtual servers, including after-hours alertingThere is on-premise infrastructure and nobody watching it overnight
Managed help deskLive remote support for your office staff, weekday or 24/7/365Internal IT is on projects and keeps getting pulled into tickets
Managed endpoint securityEndpoint detection and response, with monitoring, triage and response handled by the SOCNobody internally is watching security alerts at 2am
Email securityPremium-tier email threat protectionPhishing is the live risk and filtering is not enough
Cloud securitySecurity monitoring and policy enforcement across cloud services and identitiesMicrosoft 365 or Google Workspace is the core of the business

Because it is built this way, co-managed is not a discount version of managed IT. It is the same services, scoped to a different boundary. Our managed IT pricing guide explains how the per-user figure is built if you want to understand the economics before you call.

Your team sees everything we see

Co-managed arrangements fail when one side cannot see what the other is doing. Your internal team can request any of the following at any point in the agreement:

Environment documentation

The documentation we build on your environment as we work in it. Yours to request, which also means the business is not dependent on one person’s memory.

SLAs in writing

What we respond to, how fast, and what happens when we do not. Your team should be able to hold us to a number, not a promise.

Alert reports

What fired, what we did about it, and what is recurring. Patterns in the alerts are usually the argument for the next infrastructure decision.

Ticket reports

Volume, categories and resolution times. If forty tickets a month trace back to one application, that is worth knowing before the renewal.

When co-managed is right, and when it is not

Co-managed works when you have internal IT capability worth keeping. The deciding question is usually simple: do you have an internal IT person or team you trust and plan to keep? If the answer is yes, co-managed is worth a conversation. Signs it fits:

  • Your IT staff know the business and the applications, and that knowledge is worth protecting
  • They are overloaded in one specific direction — either buried in tickets, or buried in maintenance
  • Nobody is covering nights, weekends or vacations
  • Security needs to be measurably better and nobody has time to own it properly
  • A client questionnaire or an insurer has started asking what controls you have

Fully managed is usually the better answer if you have no internal IT, if the person wearing the IT hat is really your office manager, or if leadership wants one accountable party for everything including strategy and budgeting. We will say so if that is what we think. In that case, see Managed IT Services. If you are weighing this against adding headcount, our guide on hiring another IT person versus outsourcing works through the arithmetic.

The rule we work by

If you cannot point at a system and say who owns it, it is not co-managed. It is confusion with an invoice attached. Every split we agree to gets written down before it starts.

Local hands when remote is not enough

Remote support resolves most issues, but switches, cabling, access point placement, hardware failures and office moves still need somebody in the building. RDI works from offices in Midtown Manhattan and Ronkonkoma, our help desk answers in about 90 seconds, and our on-site average across NYC and Long Island is four hours. In a co-managed arrangement, that means your internal team is not the only pair of hands on site.

It also means one vendor can cover the copiers, the phones and the network. If your internal team is currently fielding scan-to-email problems and conference room issues alongside everything else, that is work that can move too.

Frequently asked questions

What is co-managed IT?

Co-managed IT is an arrangement where your internal IT team and an outside provider split the work, with each responsibility assigned to one owner in writing. At RDI it means taking specific services off your team — NOC device and network management, the help desk, the security stack, or a combination — while they keep everything else.

Can we get network and device management without the help desk?

Yes. That is one of the two most common co-managed splits. Your internal team keeps supporting your users, and RDI handles patch management, network monitoring, proactive device maintenance and escalation. The help desk line simply is not on your agreement.

Can RDI just be our help desk?

Yes. A managed help desk plan gives your office staff live remote support from our team, so your internal IT people can stay on critical projects instead of being interrupted by day-to-day requests. You choose weekday or round-the-clock coverage, and you get ticket reporting on what your users are actually asking for.

What visibility does our internal team get?

Your team can request the documentation we create on your environment, the SLAs covering what we respond to and how quickly, alert reports showing what fired and what we did, and ticket reports covering volume, categories and resolution times.

Is co-managed IT cheaper than fully managed?

It costs less than a full plan because you are buying fewer services, not a discounted version of the same thing. Our managed IT services are quoted as separate line items, so a co-managed agreement includes what you need and leaves out what your team already covers.

Can we start co-managed and move to fully managed later?

Yes, and it goes the other way too. Because the plan is assembled from individual services, adding or removing a piece is a change to the agreement rather than a migration. Businesses often add services when an IT person leaves, and remove them when they hire.

Tell Us What Is Holding Your IT Team Back

We will map what your team keeps and what we take, put it in writing, and quote only the services you need. If fully managed is the better fit, we will tell you that instead.