Which pricing model best suits your organisation’s managed IT requirements?

The best managed IT pricing model is the one that matches how your organisation uses technology and how predictable you need your technology costs to be. A suitable model should make the relationship between your users, devices, support requirements and monthly charge easy to understand, while remaining practical when your organisation changes.

There is no universally correct structure. A small professional services firm with standard laptops and cloud applications may suit a per-user model, while a manufacturer with shared terminals, specialist equipment and varied support needs may require per-device or hybrid pricing. The right choice comes from comparing the charging basis with the resources your IT environment actually consumes.

Per-user pricing

A per-user model applies a recurring charge to each person covered by the agreement. It is often straightforward for organisations where each employee has a broadly similar set of requirements, such as a computer, email, cloud applications and routine technical support.

This structure can be useful when employees use several devices, because the price is linked to the person rather than every laptop, desktop or mobile device they access. It also makes budgeting easier when the number of employees is relatively stable. However, the agreement should explain how it treats part-time staff, contractors, shared accounts, leavers and employees who need additional technical support.

Per-user pricing may be less suitable where many people share equipment or where a small number of users operate a large and varied estate of devices. In those cases, charging solely by user may not reflect the work involved in managing the environment.

Per-device pricing

A per-device model charges according to the equipment being managed. Devices may include workstations, laptops, servers, network equipment or other systems, depending on the scope of the agreement.

This approach can provide a closer connection between the charge and the technical assets requiring maintenance. It may suit organisations with shared computers, production-floor terminals, dedicated servers or a workforce that uses a limited number of devices across multiple shifts. It can also be easier to assess when the device estate is well documented.

The main consideration is that a growing device count can increase the monthly cost even if the number of employees does not change. The contract should therefore state which device types are included, whether inactive or spare equipment is chargeable, and how new devices are added or retired.

Tiered pricing

Tiered pricing groups users or devices into service bands. Each band may include a defined level of support, management or security, with a different charge for each tier. For example, standard users may receive the core service, while users with more demanding operational or security requirements are assigned a higher tier.

This can be appropriate where requirements differ significantly within the same organisation. It avoids treating a basic office user and a technically demanding role as identical, provided the boundaries between tiers are clearly defined.

Tiered arrangements require particular care when reviewing what is included. Terms such as “standard support”, “enhanced security” or “priority service” should be described in operational terms. The agreement should identify the services, devices, users and support routes associated with each tier rather than relying on labels alone.

Hybrid pricing

A hybrid model combines two or more charging methods. An organisation might pay a base fee for the core IT service, a per-user charge for employee support, and a separate device-based charge for servers or specialist equipment. This can reflect a complex environment more accurately than a single charging basis.

Hybrid pricing is often useful for multi-site businesses, organisations with a mixture of standard and specialist technology, or companies that retain some internal IT capability while obtaining external support for defined areas. Its disadvantage is that it can be harder to audit. A clear schedule of chargeable users, devices, projects and optional services is essential.

How to compare the available models

Rather than comparing only the headline monthly figure, assess each model against the following questions:

• What is being counted? Establish whether the unit is a user, device, site, server, service or combination of these.
• What is included? Check whether monitoring, maintenance, cyber security management, backup oversight, cloud administration and strategic advice form part of the recurring service or are treated separately.
• What is excluded? Identify project work, major upgrades, hardware, software licences, onboarding, third-party charges and specialist tasks that may attract additional fees.
• How are changes handled? Confirm how new starters, leavers, acquisitions, office moves, new sites and device replacements affect the charge.
• How is usage reviewed? Find out whether billing is based on the number recorded at a particular date, an average, a minimum commitment or another agreed method.
• Can the service be adjusted? Check whether users or devices can move between service levels as their responsibilities change.

Match the model to the organisation

Organisations with a consistent user profile and a relatively standard technology estate will often find per-user pricing easier to administer. Businesses with shared equipment or a high concentration of technical assets may gain a more representative view from device-based pricing. Where needs vary between departments, locations or types of equipment, tiered or hybrid structures may provide better alignment.

Growth plans also matter. A business opening additional sites may need a model that can add locations and network equipment without requiring the entire agreement to be renegotiated. An organisation reducing its office footprint may instead prioritise a structure that allows redundant devices and services to be removed cleanly.

For businesses with an internal IT contact or small technology team, a hybrid arrangement can define which responsibilities remain in-house and which are managed externally. The pricing should reflect the agreed division of work, so that routine tasks are not duplicated and ownership is clear when an issue crosses organisational boundaries.

Use a representative inventory before choosing

A pricing comparison is more reliable when based on an accurate inventory rather than an estimate of employee numbers alone. Record users, endpoints, servers, sites, network equipment, cloud services and any specialist systems that require consideration. Note which assets are shared, which are critical to operations and which are approaching replacement.

Then test each model against likely changes. Consider what happens if the organisation adds employees, replaces laptops, introduces a new site, adopts another cloud service or retires legacy equipment. A model that appears inexpensive for the current environment may become difficult to control if every change creates an unclear or disproportionate charge.

S2 Technology Group can discuss managed IT structures for small and medium-sized organisations around Stourbridge, Kinver, Wordsley, Kingswinford, Kidderminster, Halesowen, Dudley and neighbouring areas. The important outcome is not choosing the most familiar pricing label, but agreeing a transparent basis that reflects the technology being managed and the support the organisation genuinely requires.