# Managed, co-managed, or internal IT: which fits your team? Start with who should own daily support and who has the capacity to do the work. An outside provider, an internal IT team, or a combination can support the same business in different ways. This guide helps Puget Sound businesses define responsibilities before choosing an arrangement. Updated: October 5, 2026 ## Managed IT: an outside provider owns the agreed support path Managed IT can give employees a primary place to request help while a provider takes on agreed administration, monitoring, maintenance, vendor coordination, and improvement work. The business still approves spending, access, and priorities. The agreement should identify the covered systems and work, rather than assuming every technology issue is included. - Consider this model when there is no dedicated internal IT owner or employee support regularly interrupts other roles. - Define who handles accounts, devices, Microsoft 365, networks, maintenance, alerts, backups, and vendor escalation. - Identify the business contact who approves access, planned changes, budgets, and priorities. - Confirm what stays with software vendors and which projects or tools are separately scoped. [Review ArcTechOne's managed IT service scope](https://arctechone.com/managed-it-services) ## Co-managed IT: add capacity while retaining internal ownership Co-managed support works alongside an internal IT owner. The provider might handle escalations, Microsoft 365 work, infrastructure projects, documentation, security tasks, or overflow. Employees need clear routing so a request is not passed between two teams without an owner. Decide which work starts internally and which work goes directly to the provider. - Consider this model when internal IT knows the business but needs technical depth, project capacity, or additional coverage. - Agree on the systems and tasks assigned to each team and the escalation process between them. - Keep business priorities, access approvals, and architectural decisions with the agreed decision owner. - Plan documentation and access so both teams can work within their approved responsibilities. ## Internal IT: build day-to-day capacity inside the business An internal team can carry company context, maintain direct relationships with employees, and own daily priorities. It still needs a clear workload, access to the right tools, and a plan for specialized work, projects, and absences. Internal ownership and outside assistance can coexist; choosing internal IT does not require handling every task without a provider. - Consider internal capacity when the work requires ongoing business context, direct coordination, and enough demand to support the role. - Account for compensation, benefits, recruitment, training, tools, and coverage when comparing costs. - Identify the projects or systems that need expertise beyond the team's available skills or time. - Avoid assigning security, backups, and every employee request to one person without checking available capacity. ## Use the same responsibility checklist for every model The label matters less than whether each recurring task has an owner, an approval path, and enough capacity. Review a normal support week and an upcoming project with the people involved. If two teams share a responsibility, specify who leads and when the other team becomes involved. - Employee requests: who receives, prioritizes, resolves, and communicates them? - Accounts and devices: who administers them, and who approves access changes? - Security and recovery: who follows alerts, maintenance, backup failures, and recovery testing? - Vendors and projects: who coordinates dependencies, testing, documentation, and the final handoff? - Coverage and changes: how are absences, urgent impact, new locations, and changing workloads handled? [Use these questions when choosing an outside IT provider](https://arctechone.com/resources/choosing-managed-it-provider) ## Separate a defined project from the ongoing support model A company can use an outside specialist for a hardware or network project while keeping its existing daily support arrangement. ArcTechOne's 30+ property computer and monitor refresh included data transfer, installation, OneDrive, Microsoft Entra ID, and Intune management. The project scope and the ongoing administration of the resulting environment are separate decisions. - Define the project's objective, users, locations, equipment, licensing, dependencies, and testing requirements. - Identify who supports employees during the change and who maintains the environment afterward. - Compare internal capacity and outside labor against the actual work rather than an assumed universal package. [Plan labor, recurring technology, and project costs](https://arctechone.com/resources/managed-it-services-pricing) ## Frequently asked questions ### Does managed IT replace our internal IT employee? It does not have to. A co-managed arrangement can add outside capacity while your internal IT owner retains business context and decision authority. Define which support, administration, escalation, and project tasks each team handles. ### Which model costs less? There is no universal answer. Compare the same responsibilities, workload, coverage, tools, and project needs. Internal costs include employment and coverage; provider costs depend on the agreed scope, labor, and separate technology costs. ### Can we start with a project instead of an ongoing engagement? Yes. ArcTechOne can scope project work or hourly support around a defined need. Agree on access, dependencies, testing, and who takes over ongoing support after the work. ### Who should approve employee access in a co-managed arrangement? Your organization should identify the people authorized to approve business access. Internal IT and the provider can carry out approved changes within their assigned responsibilities and document the handoff. ## Related ArcTechOne services - [managed IT services and engineering capacity](https://arctechone.com/managed-it-services) - [managed IT provider selection guide](https://arctechone.com/resources/choosing-managed-it-provider) ## Managed IT support by service area Discuss the support model that fits your staff, locations, systems, and internal capacity. - [Managed IT services in Seattle](https://arctechone.com/managed-it-services-seattle) - [Managed IT services in Bellevue](https://arctechone.com/managed-it-services-bellevue) - [Managed IT services in Tacoma](https://arctechone.com/managed-it-services-tacoma)