Managed IT agreements vary in scope, exclusions, response commitments and transition responsibilities. A low monthly price may describe a different service from a broader proposal. This guide helps you compare the work each provider will actually perform and decide what your business needs to keep in-house.
What managed IT actually covers
Managed IT may include the services below. Mark each one as included, separately priced or excluded when comparing proposals.
Help desk and end-user support
Day-to-day support for your team: password resets, software issues, device problems, connectivity questions. Most managed IT agreements specify a response time (often categorized by severity — P1 for critical outages, P2 for significant disruption, P3 for minor issues) and a support channel (phone, email, portal). Compare the exact commitments: a fifteen-minute response to a P1 and a four-hour response are both “included help desk,” but they are not the same thing.
Remote monitoring and management
Monitoring tools can report device health, software inventory, patch status and selected performance signals. Ask which assets are covered, what triggers an alert, who responds and during which hours. Monitoring can reveal a problem early, but coverage and response are defined by the actual agreement.
Patch management
Keeping operating systems and applications patched is a security and stability function. In a managed IT arrangement, the MSP owns the patching cadence — testing patches in a staging environment where practical, deploying on a defined schedule, and handling exceptions for software that cannot be auto-patched. Ask how quickly critical security patches are deployed; the answer reveals their operational discipline.
Backup management
Most managed IT agreements include monitoring that backup jobs are completing and alerting on failures. What they may not include: actual restore testing, management of backup strategy changes, or recovery in the event of a major data loss incident (which may fall under a separate disaster recovery engagement). Clarify exactly what backup management means in the agreement you are reviewing.
Security tooling
Base plans often include endpoint protection (antivirus or EDR) and email filtering as part of the stack. Whether active monitoring of security alerts is included — or whether it requires a separate MDR engagement — depends on the provider. If your insurer or compliance posture requires active security monitoring, confirm explicitly what the MSP provides versus what they recommend you add separately.
What managed IT does not cover
Understanding exclusions is as important as understanding inclusions. Common items that are typically out-of-scope in a base managed IT agreement:
Major projects. Infrastructure upgrades, cloud migrations, new office deployments, and significant software implementations are typically project work billed separately from the managed service fee. Some MSPs include a defined number of project hours. If you have a major project on the horizon, clarify whether it is in scope before you sign.
Procurement. Managed IT arrangements vary in how hardware and software purchases are handled. Ask about purchasing authority, markups, warranties and ownership before assuming procurement is covered by the recurring fee.
On-site visits above a threshold. Remote support is included; extended on-site visits may have a defined allotment per month or be billed separately above a threshold. Confirm this for any site that requires regular physical presence.
Incident response for major events. A ransomware incident that requires forensic investigation, clean-up, and recovery from backup typically involves significant project hours beyond what is included in a monthly managed service fee. Some MSPs include an incident response retainer; others handle it as a separate engagement.
Co-managed IT vs. fully managed
In a fully managed arrangement, the MSP may own most day-to-day IT operations. Your team still needs a named owner for priorities, approvals and oversight.
Co-managed IT means you have internal IT staff — one person, a small team — and the MSP supplements them. The MSP might handle help desk volume that exceeds your internal capacity, provide specialist expertise (security, networking, cloud architecture) your internal team does not have, or take over specific functions like patch management and backup while your team handles everything else.
Co-managed works well when you have a capable IT person who is spread too thin, or when you have internal IT but need specialist depth you cannot justify hiring for. The key is defining clearly who owns what — ambiguity in a co-managed arrangement creates accountability gaps that surface during incidents.
How pricing actually works
Managed IT is typically priced in one of three ways.
Per-user pricing sets a recurring charge for each covered person. Confirm device limits, shared accounts, minimum seat counts and which services are included before comparing per-user rates.
Per-device pricing charges for covered endpoints such as laptops, servers and network devices. Count shared devices and confirm whether different asset classes have different rates or support terms.
All-in or flat-rate pricing sets a monthly price for a defined environment and scope. It does not mean every project or incident is included. Review usage assumptions, change triggers and exclusions in the agreement.
Contract red flags
Vague scope language
"All-inclusive IT support" and "comprehensive managed services" are not scope definitions — they are marketing. The contract should specify exactly what is monitored, what response times are committed to, what is included versus out-of-scope, and what the escalation path is. If the service agreement does not answer these questions, you will negotiate scope at the worst possible time: during an incident.
No documented onboarding process
Ask for a written onboarding plan that covers asset discovery, documentation, monitoring setup, access transfer and unresolved risks. A vague plan makes it harder to judge whether important parts of your environment will be covered at handover.
Locked-in RMM tooling without portability
Some MSPs deploy their monitoring and management tooling in ways that make it difficult to migrate to a new provider. Ask whether the documentation they create about your environment is yours to take when you leave, and whether there are any tools deployed that would need to be removed or replaced at transition. This is not a reason to avoid an MSP, but it is a negotiating point and a transition-planning input.
No defined escalation path for major incidents
Do not assume the MSP is the first responder for every security or infrastructure incident. Identify the owner for each scenario, the contact path, actions included and response times. Document where specialist incident response or a cloud provider takes over.
Pricing that assumes you will not use the service
A low base fee may exclude work your team uses frequently. Ask for ticket-volume assumptions, support-hour limits, overage rates and how service levels change as your environment grows. Compare the estimated total cost at your expected usage.
Transition planning
Switching MSPs is operationally disruptive if it is not planned well. The transition period — from outgoing provider to incoming provider — is when critical knowledge about your environment needs to transfer, and when operational gaps are most likely to appear. A structured transition plan reduces that risk.
- 01Document your current environment thoroughly before transition — asset lists, software licenses, credentials, network diagrams, warranty status.
- 02Negotiate a parallel overlap period with your outgoing provider if possible, so knowledge transfer can happen without a gap in coverage.
- 03Confirm that all documentation your current MSP holds about your environment is transferred to you before the relationship ends.
- 04Change all passwords and administrative credentials as part of the offboarding process from your previous provider.
- 05Confirm your new MSP has completed an onboarding assessment and has your environment documented before you go fully live.
- 06Test the help desk and support process before you are fully dependent on it — submit a non-urgent ticket and observe the response.
- 07Clarify what happens to any monitoring agents or tools deployed by the outgoing MSP that need to be replaced.
- 08Review the new agreement for auto-renewal clauses and confirm notice period requirements.
When to bring in a procurement desk
Managed IT proposals can be difficult to compare when service scope and pricing units differ. SwitchU can help map your requirements, request comparable supplier proposals and identify the terms that need clarification before you decide.
Keeping your current provider is a valid outcome if the scope and service still fit. If a structured review would help, the form below is the place to start.
For what we source and how the desk works, see our cloud and managed IT solution page.