Registered office
20 Wenlock Road
London N1 7GU
Registered office
20 Wenlock Road
London N1 7GU

Compare on-demand IT support with managed IT, including scope, costs, monitoring, response targets, the best fit for your UK SME and a buyer checklist.
On-demand IT support fixes a defined problem when you ask; managed IT provides an ongoing support, monitoring and maintenance relationship. On-demand is usually better for occasional, contained work. Managed IT is usually better when several users or critical systems need dependable ownership and prevention.
Reviewed: 18 August 2026
| Area | On-demand IT | Managed IT |
|---|---|---|
| Relationship | Per incident or project | Ongoing service |
| Cost model | Hourly, fixed task or project | Usually per user, device or month |
| Main purpose | Resolve a specific need | Support, maintain and reduce risk |
| Monitoring | Normally not continuous | Included where specified |
| Response | Subject to current availability | Contracted priorities and targets |
| Documentation | Focused on the task | Maintained across the environment |
| Best fit | Small or infrequent needs | Teams that depend on IT every day |

On-demand support is called when there is a known problem or piece of work: email delivery, a broken WordPress site, a server fault, DNS changes, a device issue or a small migration. The provider inspects risk, agrees scope and price, then resolves or advances that issue.
It does not normally include continuous monitoring, routine patching, account reviews, backup checks or guaranteed availability between requests. A good provider will still protect production, confirm access and backups, explain assumptions and document the outcome.
Managed IT combines a helpdesk with agreed proactive work. Depending on the plan, it can cover user onboarding and offboarding, Microsoft 365 or Google Workspace administration, device maintenance, endpoint security, backups, monitoring, patching, supplier coordination, reporting and roadmap reviews.
The provider learns the environment and maintains tools, access and documentation so each ticket does not start from zero. The contract defines covered users and systems, support hours, priority levels, response targets and exclusions.
On-demand is not inherently lower quality. It is a different commitment: capability for a task without reserving ongoing capacity or taking ownership of the environment.
For on-demand support, include diagnosis time, urgent availability, repeated discovery, internal coordination and the risk that routine maintenance is missed. A low hourly rate does not help if every incident begins with rebuilding context.
For managed support, check setup fees, minimum users, included tools, onsite charges, project rates and contract term. Do not pay for monitoring or software already supplied elsewhere unless the overlap is intentional.
Compare outcomes on the same basis: hours covered, first response, supported users and devices, backup responsibility, security tools, onsite provision and planned work. ACA publishes managed IT plans from £39 per user per month; exact cost varies with users, servers and scope. See the current managed IT support plans.
Yes. Common combinations include:
The key is one responsibility map. Duplicate providers should not both assume the other owns backups, security incidents or supplier escalation.
The NCSC’s guidance for choosing an MSP is useful when reviewing service boundaries, security, incident handling, resilience and exit arrangements.
Start with an inventory and short health check. If the environment is stable and internal ownership is clear, retain on-demand support with a written emergency route. If important routines have no owner, build a managed scope around the gaps rather than buying an oversized package.
ACA Tech Solutions provides both on-demand technical support for defined issues and managed IT support for ongoing response, prevention and ownership.
Not automatically. Managed IT is usually more predictable and includes proactive work; on-demand can cost less when needs are rare. Compare like-for-like coverage and operational risk.
Yes. Discovery from previous work can make onboarding easier, but the provider should still document assets, access, backups, risks and responsibilities formally.
Usually not. Major migrations, new sites, large hardware deployments and application development are commonly scoped separately.