How to Choose a Managed IT Provider

Compare providers on four things: how they deliver service (response time, resolution performance, who answers, onsite capability), how they handle security and recovery (what security is included, how often backups are restore-tested, whether a continuity plan exists), how they handle strategy and visibility (planning cadence, reporting, documentation ownership, co-managed capability), and their commercial terms (pricing model, exclusions, contract length, exit terms, and fit for your size and industry). Ask for evidence on each rather than accepting a description.

Ask when a backup was last restored and what the result was; what falls outside the agreement and gets billed separately; who leads technology planning and how often you will meet; what reporting you receive; whether documentation of your environment goes with you if you leave; and what the exit terms are. The answers to those six questions separate providers more reliably than a capability list.

Break/fix support bills for time after something has failed, so the provider only engages when there is a problem and has no commercial reason to prevent the next one. Managed IT is an ongoing engagement covering monitoring, maintenance, security, and support for a predictable fee, which aligns the provider with keeping the environment stable rather than with repairing it repeatedly.

Managed IT is usually priced per user or per device, per month, with the range driven by how many people you support, how much security and compliance work is included, and whether project work is inside or outside the agreement. Because exclusions vary widely between providers, two quotes are only comparable once you know what each one leaves out. ECS publishes its service plans so the scope of each tier is visible before a conversation.

Ask for the distribution, not an average — an average hides a slow week, and a stated "target" is a promise rather than a measurement. A median first response inside one hour is strong; the industry median is around four hours. For reference, ECS answers 66% of support requests within one minute and 90% within two hours, with the remaining 10% taking longer. Ask every provider on your list for those same three numbers.

The practical difference is onsite work and escalation. Network, server, cabling, and hardware problems eventually need someone physically present, and a local provider handles that directly rather than dispatching a subcontractor. A local team also tends to know the regional vendors, carriers, and compliance context you are operating in. The trade-off is that a national provider may offer broader after-hours coverage, so ask specifically how each handles both.

The common trigger is passing the point where technology problems reliably reach someone whose actual job is something else. For most organizations that happens somewhere between 15 and 150 employees, which is the range ECS is built around. Below that, a smaller support arrangement often still works; above it, the question usually becomes co-managed support alongside internal IT staff rather than whether to have a provider at all.

Yes. That arrangement is called co-managed IT: the provider covers the areas your internal team does not have capacity or specialization for — after-hours coverage, security tooling, escalation, project work — while your staff keep the institutional knowledge and the relationships. The essential detail is that responsibilities are divided in writing, because unwritten splits become gaps.

The timeline depends on the size and complexity of the environment, the quality of existing documentation, how quickly administrative access can be gathered, and how cooperative the outgoing provider is. Rather than quoting a fixed number, ECS builds an onboarding plan around the specific environment and reviews the transition at 30 days.