What is managed IT support?

UK SME pricing generally falls between about £30 and £90 per user per month. The spread reflects scope rather than quality alone: at the lower end, agreements typically cover remote helpdesk and basic monitoring, with projects, on-site work, security tooling and out-of-hours cover charged separately. At the higher end, agreements bundle endpoint protection, backup, device management and sometimes security monitoring. Comparing quotes requires normalising scope — a cheaper per-user rate that excludes patching, backup and security tooling is often more expensive once those are added back in.

Break-fix means paying for work as incidents occur, typically at an hourly rate with no ongoing fee. It can suit very small organisations with simple, stable environments. The structural weakness is incentive: the provider earns more when things break, and there is no commercial reason to invest in prevention such as patching, monitoring or documentation. Managed support charges a predictable recurring fee, which aligns the provider's interest with keeping systems stable. It also makes budgeting straightforward, since unpredictable incident costs are replaced by a known monthly figure.

Cloud services remove server maintenance but not administration. Someone still has to configure the tenant securely, manage licences, enrol and configure devices, apply Conditional Access and MFA policies, handle joiners and leavers, patch endpoints and third-party software, arrange backup of Microsoft 365 data, and support users when something fails. In very small organisations this often falls informally to whoever is most technical, which creates key-person risk and inconsistent configuration. The question is less whether the work exists and more who is accountable for it.

Yes, and it is a common arrangement. The IT provider continues to handle support, infrastructure and day-to-day operations, while a specialist handles security monitoring, certification, assessments and incident response. It works when responsibilities are documented explicitly — who patches, who owns firewall rules, who acts on an out-of-hours alert, who leads during an incident — and when both parties have direct communication rather than routing everything through the client. Ambiguity between two providers is a genuine risk, so a written responsibility matrix is worth the effort at the outset.

Look for defined response and resolution targets by severity, and whether they are contractual or aspirational. Confirm what falls outside support and is billed as project work, since that boundary is where unexpected costs arise. Check out-of-hours arrangements and whether they cost extra. Establish who owns licences, domains, backups and documentation, and how they transfer if the relationship ends. Clarify security responsibilities specifically: monitoring, patching cadence, incident response and reporting. Finally, check notice periods and whether the term renews automatically.