Start with the work your team needs help covering
A co-managed engagement can help when internal staff need escalation support, Microsoft 365 administration, security operations or additional capacity for a migration. It should name who owns each queue, approves changes and communicates with employees. Headcount alone does not determine the right service model.
| Area | Internal team decision | External scope to agree |
|---|---|---|
| Help desk | Which requests remain with your team? | Escalation levels, supported hours and ticket handover |
| Administration | Who approves access and configuration changes? | Microsoft 365, identity, endpoint and system tasks |
| Security | Who can authorize containment and business interruption? | Monitoring, investigation and incident escalation responsibilities |
| Projects | Who sets priorities and accepts completion? | Migration tasks, dependencies and acceptance evidence |
| Documentation | Which records and credentials must the business retain? | Shared documentation, reporting and exit handover |
A service agreement should make shared ownership clear
Document the responsibilities your team retains before requesting a price. Tool access, licenses, change approvals, support hours and project work can materially change the scope. Co-managed pricing is quoted for the agreed work; do not assume it is a fixed percentage of a fully managed plan. Published managed IT plans provide context, while a tailored proposal defines this engagement.
Review published plans and pricing and record missing proposal details in the free MSP comparison worksheet.
How to plan the engagement
- List recurring support tasks, escalation gaps and projects that lack capacity.
- Map each responsibility to an internal owner, CloudTechForce or another supplier.
- Agree access, ticket handover, change controls and escalation contacts.
- Review service evidence and adjust the scope when your team's responsibilities change.
Questions buyers ask
Does co-managed IT replace our IT employees?
The engagement is designed to support your existing team. Your business decides which responsibilities stay internal and which are included in the external service.
Is co-managed IT the same as staff augmentation?
Staff augmentation supplies people for defined work. Co-managed IT defines an ongoing service and division of responsibilities. A project may need either model, depending on how you want to manage the work.
Can we request a limited scope first?
Yes. Describe the specific support or project gap so we can assess a limited scope. Coverage, access and escalation requirements still need to be agreed in writing.
How is co-managed IT priced?
Pricing depends on the responsibilities, supported systems, tools and coverage assigned to CloudTechForce. Request a tailored proposal; there is no universal discount against a fully managed plan.
Related services and decision guides
Page updated 2026-09-28. CloudTechForce is based in Columbus, Ohio; other listed locations are service areas. Company details and team information are available for your review. Service coverage and commitments are defined in the written agreement.
Scope co-managed IT support
Your IT team's responsibilities, user/site counts, existing tools, support hours needing coverage, project backlog and renewal dates.
Tell us which published plan you are considering, or describe the project you need quoted. We will use your requirements to discuss the appropriate scope.