How is managed IT support pricing structured?

Managed IT support pricing is best understood as a combination of the charging unit, the services included in the agreement and the rules for work that falls outside the standard service. Comparing the monthly figure alone can be misleading if two providers define their support boundaries differently.

The main pricing models

• Per-user pricing: a charge is based on the people supported, often covering the computers, access permissions and standard applications associated with each user. This can be straightforward for office-based organisations with consistent requirements.
• Per-device pricing: charges are linked to managed laptops, desktops, servers, network equipment or other defined assets. This may suit organisations where users work across shared devices or where infrastructure management is the main requirement.
• Hybrid pricing: a provider may combine a user charge with separate treatment for servers, network equipment, specialist systems or other assets. This allows the agreement to reflect a more complex technical environment.
• Tiered or service-based pricing: different packages may provide progressively broader management, security oversight, strategic advice and technical administration. The important point is to compare the actual inclusions rather than the package name.

What the monthly service should define

A clear proposal should describe which activities are included in the recurring service. This may cover service desk assistance, monitoring, maintenance, account administration, backup oversight, security management, Microsoft 365 administration, network management or technology planning, depending on the agreement. It should also state whether support applies to all systems or only to approved and documented equipment.

Definitions matter. For example, “managed security” could mean that security tools are installed and monitored, while a broader service may also include policy advice, incident coordination and remediation support. Similarly, cloud management may include administration of accounts and configurations without including the underlying software subscription. Each element should be identified separately so that the business can establish its real operating cost.

Factors that commonly change the price

• the complexity and age of the existing technology environment;
• the number of operating systems, applications and specialist platforms that must be supported;
• the level of administration required for user accounts, permissions and joiners or leavers;
• the extent of security monitoring, protection and compliance support required;
• the number and type of servers, network components and cloud environments;
• the need to support remote workers, shared devices or multiple sites;
• the amount of strategic consultancy and technology planning included;
• the quality of existing documentation, configurations and asset records; and
• any requirement to support legacy systems or third-party applications.

These factors do not necessarily appear as separate line items. A provider may incorporate them into a per-user or per-device charge, while another may price them as fixed components. The proposal should make clear which approach is being used.

Included work and additional charges

Agreements commonly distinguish between operational support and project work. Operational support maintains and administers the agreed environment. Project work changes it, such as a migration, office move, major network redesign, new system deployment or substantial hardware replacement. Some providers include a limited amount of consultancy or change activity, whereas others quote it separately.

Other potential additional charges can include new equipment, software subscriptions, third-party licences, specialist consultancy, travel, disposal of hardware and work caused by systems that were not disclosed during the assessment. These are not automatically unreasonable, but they should be identified before the agreement is signed. A useful contract explains the approval process, applicable rates or quotation method and whether the business can decline optional work.

Onboarding and initial remediation

The transition into managed support may have its own cost. Initial work can include auditing assets, documenting systems, applying updates, improving account controls, configuring monitoring tools, reviewing backups and correcting known issues. This effort is different from the ongoing management fee because it establishes the information and controls needed to operate the service properly.

Ask whether onboarding is included, charged as a fixed project or calculated from the work identified during an assessment. If remediation is required before the provider will take responsibility for a system, the proposal should separate essential corrective work from optional improvements.

Contract terms and price reviews

The agreement should explain its initial term, renewal arrangements, notice requirements and the method used to adjust charges when the environment changes. In particular, it should state how new users, removed users, replacement devices, acquired businesses and additional locations affect the fee.

It should also clarify whether unused allowances expire, whether there is a minimum monthly charge and how billing is handled when staff numbers fluctuate. A transparent change process prevents disagreements when the business grows or its technology estate is reorganised.

How to compare proposals

1. List the users, devices, servers, cloud platforms and locations that each provider has priced.
2. Map each quoted service to a specific business requirement.
3. Separate recurring management from licences, equipment, projects and consultancy.
4. Check exclusions, fair-use limits, third-party dependencies and chargeable activities.
5. Review how security, backup, documentation and reporting responsibilities are allocated.
6. Calculate the likely cost of expected changes, not just the starting fee.

A suitable pricing structure should be understandable, scalable and aligned with the organisation’s risk and operational needs. S2 Technology Group can use an assessment of the existing environment to distinguish the ongoing managed service from onboarding, improvement projects and third-party costs, giving businesses a clearer basis for evaluating support options.