Co-Managed IT: How MSPs and Internal IT Teams Share One Client Experience

Co-managed IT used to be the deal you took when a prospect wouldn't let go of their in-house team. That's not where things stand now. Coverage of the MSP market this year treats co-managed as a mainstream engagement model rather than a niche one (MSP Success), and mid-year trend roundups describe it as close to the default (Viirtue).

That's good news. It's also a new kind of problem. When two IT teams serve one client, the hard part usually isn't the technical work. It's making sure everyone can see who's doing what.

Here's how to set up a co-managed relationship so the work is shared, the credit is shared, and the client sees one coordinated team.

Why co-managed is a bigger opportunity than it looks

It's tempting to see a co-managed client as half a client. That gets it backwards.

• It's an easier way in. You're not asking a prospect to replace their IT staff and trust you on faith. You're offering to fill the gaps they already know they have.
• It tends to grow. Once the internal team gets used to working with you, scope often widens. Plenty of co-managed relationships start narrow and expand from there.
• You get the best of both teams. You bring patterns from across your client base. They bring deep knowledge of their own systems, people, and history. Together, the work gets done faster and better than either side would manage alone.

The catch? None of that happens on its own.

Where co-managed relationships break down

Most co-managed friction comes from the same few places.

There's no shared front door. Requests show up in your PSA, the internal team's inbox, a Teams message, and a hallway conversation. Nobody's sure which team owns what.

Your work is invisible. The internal IT lead can't easily see what you've delivered this month. At renewal, that's a problem.

Ownership gets murky. If end users start thanking the MSP for fixes the internal team asked for, resentment builds fast. Good co-managed setups make roles explicit.

Everyone's in different tools. Your techs live in the PSA. The internal team lives in theirs, or in email. Leadership lives in neither.

The fix for all four is the same: one shared place where both teams and the client's leadership can see the relationship. That's the job a client portal does.

Pillar 1: A shared service desk

Start with intake, because that's where confusion costs the most.

With the CloudRadial Unified Client Portal (UCP), you give the client one branded place to submit requests and report problems. Request forms support conditional logic, attachments, and single or multi-level approvals. Each form routes to the PSA board you choose, so a request lands structured and in the right queue for whichever team owns that kind of work.

Here's how that plays out in a co-managed account:

• Onboarding and offboarding forms that collect everything up front, with the client's internal IT lead approving before work starts.
• Separate paths for problems and requests, so a broken printer and a new-hire laptop don't land in the same pile.
• Ticket visibility for the client, who can see open, closed, and waiting tickets and reply on them without chasing anyone by email.

UCP integrates directly with ConnectWise Manage, Autotask, HaloPSA, Syncro, and Kaseya BMS. It doesn't replace your PSA. Your tickets stay there, and UCP reflects them back to the client.

If the client's people would rather ask for help in chat, CloudRadial ChatAI works in Teams, Slack, web, SMS, and the portal itself. Every conversation creates or updates a ticket in your PSA, so both teams work from the same record. ChatAI Enterprise adds support for co-managed client service desks.

Pillar 2: Shared visibility and planning

Co-managed clients often bring you in as an advisor, not just extra hands. That means the vCIO side of the relationship matters as much as the ticket queue.

UCP Professional gives you and the internal IT lead a shared view of where things stand:

• The Planner, a shared Kanban roadmap that anchors your QBR conversations: what's going right, what isn't, and what's next.
• On-demand QBR reports and inventory reports built from endpoint, license, and Microsoft 365 data, so prep doesn't mean days of screenshots.
• Compliance policies, a library of roughly 550 customizable checks across endpoint, license, and tenant data that show the client where they stand against the standard you define together.
• Assessments, including NIST and CIS question sets, for the judgment-based reviews that don't live in any RMM.

Here's what that does for a co-managed account. Both teams look at the same roadmap. When it's time to decide what to tackle next quarter, nobody's arguing from different spreadsheets. And the work your team delivered stays visible to the people who sign the renewal.

These capabilities are part of UCP Professional. UCP Starter covers the request and ticket experience. See pricing for the full tier breakdown.

Pillar 3: Shared content and clear roles

The third piece is the one that makes co-management feel like a partnership instead of an arrangement.

Roles you control, per client. UCP is configurable per client and per user role. Your internal IT counterpart can see reporting and handle approvals, while their staff see the forms and knowledge base they need. UCP Starter supports two user roles per client. Professional supports up to ten.

Standards you set once. Knowledge base content, request forms, dashboard layouts, and planner items are authored once in UCP and pushed to clients through content packages. For compliance, partner-managed policies stay in sync from your template packs, and the client can still add checks that only matter to them.

Training you deliver together. UCP connects to Bigger Brains courses, so you can assign Microsoft 365 training and track completion alongside the client's own initiatives.

Required tasks with the right authority behind them. Policy sign-offs, mandatory training, and announcements work best when the client's own leadership assigns them. In a co-managed account, that's often the internal IT lead. You provide the content. They drive completion with the authority they already have over their staff.

Access where people already work. The portal runs in a browser, as a branded desktop tray app, or embedded in Microsoft Teams.

How to set up a co-managed account in CloudRadial

A client-ready portal takes real configuration, and most partners work through it in Jumpstart sessions with a dedicated onboarding manager. Here's a sensible order for a co-managed client:

1. Write down who owns what. Which request types go to you, which go to the internal team, and which need approval. This becomes your form and routing design.
2. Set up roles. Decide what the internal IT lead sees versus their end users.
3. Build the forms. Start with the requests that cause the most back-and-forth: onboarding, offboarding, hardware, and access.
4. Assign your standard content. Push your knowledge base, forms, and policy packs, then let the client add what's specific to them.
5. Set the planning rhythm. Put the first quarter's work on the shared Planner and agree on when you'll review it together.

From selling a portal to delivering a partnership

Here's the shift that makes co-managed work. If you pitch a portal as a product, you're asking for a yes or a no. If you introduce it as the way your two teams will work together, it's part of how you deliver. That's a much easier conversation.

Some co-managed clients only need a shared service desk. Some mostly want the planning and reporting. Some want both, plus training and content. UCP lets you configure each client differently, so every account gets what fits.

See it in a co-managed setup

Want to see how a shared service desk, the Planner, and role-based views come together for a client with its own IT team? Book a demo and we'll walk through it with your co-managed accounts in mind.

Frequently Asked Questions

What are the best tools for co-managed IT between an MSP and an internal IT team?

The best co-managed IT setups use a small stack both teams can share: a PSA as the single system of record for tickets, an RMM both teams can access with permissions scoped to what each one manages, a documentation platform both sides can read and update, a collaboration tool such as Microsoft Teams or Slack, and a client portal that ties it all together for the client. The portal is the piece that's easiest to skip, and it's the one that gives the client's internal IT lead a single view of requests, tickets, reporting, and the shared roadmap.

CloudRadial fills that portal role. The Unified Client Portal integrates with ConnectWise Manage, Autotask, HaloPSA, Syncro, and Kaseya BMS, routes structured requests to the right PSA board, and gives each client role its own view. ChatAI adds chat intake across Teams, Slack, web, and SMS, with co-managed service desk support on the Enterprise tier.

What is co-managed IT?

Co-managed IT is a support model where a business's internal IT team and an MSP share responsibility for its technology. The internal team usually keeps day-to-day operations and business knowledge, while the MSP covers specialized work, extra capacity, or strategy.

Who should own the end-user relationship in co-managed IT?

Usually the internal IT team. They're the ones end users see every day, and the partnership works best when the MSP makes them look good rather than competing for credit. Clear routing and clear roles help. In CloudRadial, the portal carries your branding, and you decide per client and per role who sees and approves what.

Does a co-managed client need access to our PSA?

Not always. Giving client staff direct PSA access isn't the only option. A client portal can show the internal team their tickets and let them submit and approve requests, while the tickets themselves stay in your PSA.

Which CloudRadial tier do I need for co-managed IT?

UCP Starter covers branded request intake, ticket visibility, the knowledge base, and two user roles per client. UCP Professional adds the Planner, on-demand QBRs, compliance policies, assessments, and up to ten user roles per client. For chat, ChatAI Enterprise adds co-managed client service desk support.

Updated October 19, 2026