When a business considers managed IT services, the first question is often “How much per user?” A better first question is “What will this provider take responsibility for?” Price has little meaning until coverage and ownership are clear.
Start with the service boundary
A managed service agreement should identify which users, devices, networks, servers, cloud services, and third-party systems are covered. It should explain what is routine support, what becomes a project, and what requires a separate vendor.
Five questions that reveal the real service
- What is monitored and maintained? Ask which systems are in scope, how issues are detected, and who responds.
- How is support requested? Clarify business hours, escalation paths, after-hours arrangements, and emergency procedures.
- Who owns backups and recovery? Identify who performs checks, how restore tests work, and which recovery assumptions remain untested.
- What documentation will exist? Expect asset inventory, access procedures, vendor contacts, and operational runbooks that remain available to the business.
- How is improvement planned? Look for reviews that distinguish recurring issues from one-off tickets and turn them into a prioritized roadmap.
Co-managed IT can be the right answer
An internal IT lead may already know the environment better than anyone else. A co-managed provider should make that person more effective by sharing defined responsibilities, project capacity, or operational coverage—not creating competing authority.
Make the handoff explicit
Before signing, ask for a responsibility matrix that shows who handles identity administration, endpoint security, vendor support, cloud changes, purchasing, and incidents. Agreement on ownership is often more valuable than a long feature list.