Managed IT services means outsourcing responsibility for your technology to a provider who takes ownership of it, for a predictable recurring fee, rather than being paid to fix things after they break.
That distinction — ownership versus repair — is the whole idea. Everything else is detail.
This guide covers what is actually included, how the model works commercially, where it fits and where it does not, and what to expect if you engage a provider.
The core idea
Under a traditional arrangement, IT is a cost you incur when something goes wrong. You call someone, they fix it, you pay for the time. Your provider's revenue rises when your systems fail.
Under a managed arrangement, you pay a fixed monthly fee and the provider becomes responsible for the environment working. Their profitability now depends on your systems being stable, because every hour spent on a preventable failure is an hour they are not paid extra for.
This alignment is the reason managed services exist, and it is why the model includes work that no hourly arrangement can accommodate — monitoring, patching, documentation, lifecycle planning, security posture. None of that produces a billable event, and all of it prevents ones that would.
What is typically included
Monitoring and alerting
Agents on every device and server reporting health continuously: disk space, failed services, hardware warnings, offline devices, security events. The value is in triage rather than collection — alerts nobody reviews are worse than none, because they create an appearance of coverage.
Helpdesk
Day-to-day support for staff. Usually tiered — a first line handling common issues, escalating to engineers for anything complex. Coverage hours vary significantly between providers and are worth checking carefully.
Patch management
Operating system and application updates, tested and deployed on a schedule, with reporting on what applied and what failed. This is unglamorous and is one of the highest-value things a provider does.
Backup and recovery
Backups configured, monitored, and — critically — periodically restored to verify they work. A backup that has never been restored is an assumption.
Security
Depth varies enormously here. At minimum, endpoint protection, email filtering and MFA enforcement. Better arrangements include endpoint detection and response, monitored by someone. Ask specifically what is included, because "security" covers a wide range of products.
Documentation and asset management
A maintained record of what you have, where it is, how it is configured, and when it needs replacing. This is what turns reactive support into planning.
Vendor management
Dealing with your internet provider, software vendors and hardware suppliers on your behalf — a genuine time saving that is rarely the reason anyone buys, and frequently the thing they most appreciate later.
Strategic review
A recurring conversation that is not about a ticket: what is ageing, what should be budgeted, what risk is accumulating. Typically quarterly. If this is absent, you have a support contract rather than a managed relationship.
What is usually not included
Assume these are separate unless the agreement says otherwise:
- Hardware and software purchases
- Software licensing, particularly Microsoft 365 and Google Workspace seats
- Project work — migrations, office moves, major upgrades
- Support for specialised line-of-business applications, or support limited to best-effort
- Cabling and physical infrastructure
- Remediation of pre-existing problems discovered during onboarding
None of these exclusions are unreasonable. The problem is comparing a quote that includes licensing against one that does not and concluding the second is cheaper.
The variants
- Fully managed — the provider owns the environment end to end. The default for businesses without internal IT.
- Co-managed — you keep internal staff and the provider fills specific gaps: after-hours cover, specialist depth, project capacity, holiday cover. Frequently the right answer for businesses with one overloaded internal person.
- Helpdesk only — support for users, no responsibility for the underlying environment. Cheapest, and appropriate only when someone else owns strategy.
- Managed security — security-specific services, sometimes alongside a separate general IT provider.
How it is priced
Almost always per user per month, or per device per month. Per-user is more common and generally favours the client in device-heavy environments, since one person with four devices costs the same as one with one.
For fully managed service, typical ranges run roughly $100 to $250 per user per month, moving within that band based on user count, compliance obligations, security depth, coverage hours, and how much on-premise infrastructure remains.
Expect an onboarding or remediation cost at the start, separate from the monthly fee. Any provider quoting a firm monthly figure without examining your environment is guessing.
Is it right for your business?
Managed IT tends to fit when several of these are true:
- More than roughly 10 employees
- Downtime costs real money rather than being an inconvenience
- You have compliance obligations, or clients who send security questionnaires
- Nobody internally owns IT, or one person owns it alongside another job
- You are growing, and onboarding new staff is already awkward
- You carry cyber insurance, or intend to
It fits less well for very small businesses with simple cloud-only environments, for organisations that genuinely need someone physically present most days, and — past roughly 150 to 250 seats — for businesses where an internal team becomes more economical.
What the first months look like
Onboarding is where the work concentrates. A provider will document your environment independently, deploy their tooling, verify backups, take over vendor relationships, and produce a remediation list of what needs fixing.
That list is frequently uncomfortable — unsupported operating systems, failing hardware, backups that were never working, former employees with active accounts. This is not the provider creating problems. It is the first time anyone has looked properly.
Expect four to six weeks before things settle, and expect the environment to feel more scrutinised, not less, during that period. After that, the measure of whether it is working is straightforward: are you thinking about IT less than you were.