Per user, per device or hourly: which IT pricing model suits you?

How each model actually works

Under per-user pricing you pay a fixed amount for every person supported, and that person can use a laptop, a phone and a tablet without the price changing. Per-device pricing counts endpoints instead, often with different rates for a workstation, a server and network equipment. Hourly billing has no standing fee at all: you log a problem, a technician works on it, and the time appears on your next invoice.

There are hybrids too. Some providers sell prepaid blocks of hours at a discount that expire after a set period. Others charge a small per-device monitoring fee and then bill hourly for any fix. Knowing which version you are being offered matters, because a block of hours that lapses unused can cost more than plain hourly support, and monitoring without included fixes can generate a steady stream of small invoices.

The incentives behind the price

Every pricing model rewards the provider for something. Under a flat monthly fee, the provider earns the same whether you have one problem or fifty, so it pays them to prevent issues: patch on time, replace failing hardware early and set up security properly. Under hourly billing, the provider earns more when things break, which does not make hourly technicians dishonest, but it does mean prevention is something you have to ask and pay for separately.

Per-device pricing sits between the two. It rewards keeping each machine healthy, but it can make providers slower to recommend consolidating or retiring old equipment, because fewer devices means less revenue. None of this is a reason to distrust anyone. It is simply worth knowing which way the economics lean so you can ask the right follow-up questions.

Which model fits which office

A three-person consultancy working entirely in Microsoft 365 on laptops, with no server and few problems, may be well served by hourly support plus a sensible security baseline they set up once. A twelve-person accountancy where everyone has a laptop, a desktop at the office and a mobile with company email fits per-user pricing, because counting devices would triple the bill for no extra work.

A small manufacturer or warehouse with shared PCs on the floor, used by several shift workers who do not each have email, is a natural fit for per-device pricing. Likewise a medical practice with consulting room computers shared between clinicians. The test is simple: count people, count devices, and see which number better reflects the actual work involved in looking after your setup.

Questions that expose hidden costs

Ask how part-time staff, contractors and shared mailboxes are counted under a per-user plan. Ask whether a per-device plan charges for printers, phones and network gear, or only computers. Ask what the minimum billing increment is on hourly work and whether travel time is charged. Ask whether a monthly plan includes setting up a new starter's laptop or treats it as billable project work.

Also ask what happens when your headcount changes. A good per-user arrangement lets you add and remove people month to month with a simple adjustment. Some contracts set a minimum number of seats for the full term, so if you shrink you keep paying for people who have left. Make sure the contract explains how and when numbers are updated.

Switching models as you grow

Many businesses start hourly and move to a monthly plan as they grow. The usual trigger is not cost but disruption: invoices become unpredictable, staff start fixing things themselves to avoid calling, and nobody is watching updates or backups between incidents. When that happens, the cheaper model is quietly costing you in lost time and growing risk.

Going the other way is also reasonable. If you have downsized, moved fully to cloud apps and have a capable staff member who handles basics, a lighter arrangement with occasional paid help may be enough. Review the fit every year or two rather than staying on whatever model you signed up to when the business looked different.

A worked example

Picture a fifteen-person architecture practice. Each designer has a powerful desktop at the office, a laptop for site visits and a phone with company email, so there are roughly forty-five devices but only fifteen people. Priced per device, the bill reflects forty-five endpoints even though most help requests come from people, not machines. Priced per user, the practice pays for fifteen seats and every device is covered.

Now picture a joinery workshop with the same fifteen staff, where only four office staff have email and the floor shares three PCs for job sheets. Here per-device pricing covers seven machines and a server, which may come in well under fifteen user seats. Same headcount, opposite answer. That is why it pays to ask for your own setup to be priced rather than relying on a provider's sample figures.