MSP vs On-Demand IT Support: What Should Your Business Own?
Managed IT and on-demand support assign work differently. A managed service agreement defines recurring responsibilities. On-demand help addresses the issue or task you engage someone to handle. The right arrangement depends on what needs doing between incidents and who is responsible for it.
Employee count alone does not decide the answer. A ten-person business can have substantial operational dependencies, while another team of the same size can have a simpler setup and a capable internal owner.
Make recurring responsibilities visible
For each responsibility below, record a named owner, completion evidence and escalation contact before comparing proposals:
Employee access and departures: approved checklist.
Device inventory and updates: current record/status.
Backups and recovery testing: agreed checks and test results.
Internet and phone coordination: provider/service record.
Employee help requests: documented support process.
Renewals and administration: calendar and owner.
A blank row is a responsibility gap. Buying software does not assign an operator. An occasional support session does not automatically create ongoing monitoring or backup administration.
Compare the operating models
How does work start? A managed agreement defines recurring duties and requests. On-demand support begins with a specific accepted request or engagement.
What covers routine checks? In managed IT, the provider owns them where expressly included. With on-demand help, your internal owner handles them unless separately engaged.
How are larger changes handled? Check what the managed contract includes or excludes. On-demand changes usually need a separate scoped project.
What response is promised? Read written support targets and exclusions, or the accepted scope and stated availability.
How are costs structured? Compare recurring fees plus exclusions/projects with hourly, incident or project scope as agreed.
These are common structures, not universal rules. Read the actual proposal. A response target is different from a guarantee that every problem will be resolved within that time.
Do I need an MSP for ten employees?
Consider a hypothetical remote team with consistent devices and an operations lead handling administration. It may need occasional specialist help and planned deployments. Another ten-person business may depend on several shared systems, have frequent employee issues and lack anyone checking recurring tasks. Ongoing support deserves a closer look in that situation.
The question is how much work needs owning, how often it occurs and what interruptions the business can tolerate. Headcount is one input.
Compare the full scope and cost
For each proposal, separate recurring charges, incident work, projects, equipment and subscriptions. Add internal coordination time as your own estimate, not a vendor fact.
Ask four questions:
What work do you own, and what remains ours?
What are the support hours and escalation process?
Which costs or changes need separate approval?
Who retains account ownership, documentation and the ability to transition providers?
A hybrid can work when responsibilities are explicit. It becomes risky when each party assumes the other is checking an important dependency.
Where FMA fits
FMA offers remote help and scoped technology projects. A project request begins requirements and scope discussion; it does not purchase work or authorize changes. Hardware, subscriptions and reseller charges are separate from consulting scope.
If you need ongoing monitoring, emergency response or a recurring management agreement, make that requirement explicit when evaluating a provider. Do not infer it from an hourly support offering.
Can we use both models? Yes, provided the agreement states who handles each recurring and incident responsibility.
Where should we start? Review the existing employee onboarding checklist and identify any tasks without an owner. Then bring those gaps to the support discussion.
Sources: FMA’s current Services Overview and Project Request define FMA’s scope. The comparison and hypothetical examples are editorial guidance, not claims about all MSP contracts or FMA customer outcomes.
