Is outsourced IT support priced per user, per device, or by service scope?
Outsourced IT support can be priced per user, per device, by service scope, or through a combination of these models. The appropriate structure depends on the systems covered, the level of support required and how the provider defines the services included in the agreement.
The pricing basis for outsourced IT support is the unit used to calculate the recurring service: a supported user, a supported device, a defined service scope, or a combination of these. The most suitable model depends on how an organisation works, how many endpoints and systems it operates, and whether its support requirements are broadly predictable.
Per-user pricing assigns a charge to each person covered by the agreement. It commonly includes support for the standard devices and access services that person uses, although the exact definition varies between providers. This can be straightforward for office-based businesses where each employee has a consistent set of equipment and applications.
A per-user model requires the agreement to define what counts as a user. For example, it should clarify how temporary workers, contractors, shared accounts, leavers, new starters and people who use several devices are treated. A person with a laptop, desktop computer and mobile device may still be one supported user, but that is only clear if the proposal says so. Shared workstations, warehouse terminals and meeting-room equipment may need separate treatment.
Per-device pricing bases the charge on the equipment being supported. Devices might include desktop computers, laptops, servers, network appliances or other endpoints, with different categories attracting different charges. This approach can suit organisations where equipment numbers are easier to measure than user numbers, or where many devices are shared by different people.
Per-device pricing also needs careful definitions. A quote should identify which device types are included, whether servers and network infrastructure are priced separately, and how replacement equipment, spare devices, personal devices and unsupported operating systems are handled. A business with a relatively small workforce but a large number of operational devices may find that a device-based model produces a different result from a user-based model.
Service-scope pricing charges for an agreed package of responsibilities rather than applying a simple rate to every person or endpoint. The scope may describe the systems managed, the support channels covered, security administration, cloud environment management, backup oversight, network management or strategic IT guidance. The price is then linked to the complexity and boundaries of that responsibility.
This model can be useful where the technology estate is unusual, where support requirements are shared across several sites, or where a business wants one defined operational responsibility rather than a separate calculation for every asset. It is not necessarily unlimited support. The contract should state which activities are included, which are treated as projects or additional work, and what assumptions were used when the scope was priced.
Hybrid pricing is common. A provider may combine a per-user charge for everyday support with separate charges for servers, network infrastructure or specialist systems. Another arrangement might use a service-scope fee for management of the core environment, with user or device charges used to account for changes in scale. Hybrid structures can reflect a business more accurately, but they make the schedule of included items particularly important.
When comparing quotations, look beyond the headline unit price and check the following points:
- What is counted? Confirm the definitions of a user, device, site, server, shared account and supported system.
- What is covered by the unit? Establish whether the charge includes support, monitoring, administration, security management and routine maintenance, or only a particular element.
- How are changes measured? Ask when new users or devices are added, how removals are recorded and whether changes are reconciled immediately or at an agreed review point.
- Are there minimums or thresholds? Some agreements use minimum quantities or define a baseline environment, so reducing one category may not reduce the charge in the same proportion.
- Which work follows a different charging method? Implementation work, major upgrades and other planned projects may sit outside the recurring support calculation and should be identified separately.
- Does the scope match the operating model? A business with remote workers, shared equipment, multiple locations or specialist operational technology needs a pricing definition that reflects how its systems are actually used.
The best comparison is therefore not simply “per user versus per device”. It is a comparison of the total supported environment and the responsibilities attached to the price. Two proposals using the same charging model can still differ substantially if one covers more systems, more administration or a broader support scope.
Before accepting a quotation, ask the provider to map the proposed charges to an asset and user list, then record the assumptions in the agreement. This makes it easier to understand the starting price, identify what would change it and assess whether the model remains appropriate as the organisation grows. S2 Technology Group can use this type of assessment when discussing managed IT support, cyber security, cloud solutions and business connectivity for small to medium-sized organisations.
A useful way to assess an outsourced IT support price is to test how it responds to different types of change. Model user growth and device growth separately, because the same operational change can affect each pricing structure differently.
For example, adding an employee may increase a per-user charge even if they use an existing workstation. Replacing one laptop with another may leave a per-device charge unchanged, while adding a shared warehouse terminal could increase it without adding another supported user. A service-scope fee may remain unchanged in either situation unless the change expands the provider’s responsibilities.
Ask for these scenarios to be reflected in the quotation or pricing schedule. This shows whether the proposed model follows the organisation’s actual cost drivers and makes future changes easier to budget. It also helps identify whether a low starting price could increase sharply as the ratio between users, devices and managed systems changes.
