IT support contract pricing is rarely a single number. What looks like a monthly rate is usually a formula: a unit of measurement, a scope of coverage, and a set of assumptions about how often you will need help. Change any one of those and the effective cost moves, even if the printed rate does not.
Two quotes covering the same office can therefore differ dramatically and both be correct. The model you choose determines what happens when your needs shift, and shifting needs are the only reliable feature of a growing business.
This article explains four common structures, the situations each suits, and the risks that hide inside an apparently straightforward offer.
Why the Model Matters More Than the Rate
Providers price support by measuring something, and users, devices, hours and retained capacity are the usual units. Each unit creates a different incentive: some reward stabilising your environment, others reward volume of work.
Understanding which unit drives your invoice lets you predict how the cost behaves when you hire, relocate, replace hardware or take on a seasonal contract. It also tells you what to monitor in the agreement to avoid surprises at renewal.
Per-User Pricing
A fixed amount is charged for each named person who needs support. The fee covers the devices that person uses, their account, and their share of helpdesk demand.
When it fits
Per-user pricing suits organisations where people and computers move together: professional services firms, agencies and administrative teams. It is simple to forecast, simple to audit, and scales in a way finance teams find easy to explain.
The risks to watch
Watch the definition of a user. Shared accounts, contractors and people who work mainly on one shared terminal can inflate the count. Also check whether a heavy user who generates most of the tickets costs the same as everyone else, and whether mid-month additions are charged in full.
Per-Device Pricing
Here the unit is the machine rather than the person: workstations, laptops, servers, network equipment, and sometimes specialised hardware on a production floor.
When it fits
Device-based pricing suits environments where equipment outnumbers people or devices are shared: warehouses, clinics, workshops, and sites with scanners, controllers or kiosks that need maintenance but have no permanent owner.
The risks to watch
Server and network equipment usually carries a higher weight than an end-user machine, so ask how tiers are assigned. Device sprawl is the other hazard: equipment bought by departments can sit outside the contract and generate charges when it fails. A current asset register protects both sides.
Hour Blocks and Prepaid Time
You buy a quantity of support hours in advance, at a rate below the emergency price, and draw them down as work is done.
When it fits
Blocks suit small teams with limited infrastructure, seasonal businesses, and organisations wanting a predictable relationship without a full subscription. They also work well for defined projects quoted up front.
The risks to watch
The two questions that matter are burn rate and expiry. If you consume the block faster than expected, the effective cost is higher than the quoted rate. If unused hours expire, you have paid for capacity that never existed. Ask how consumption is reported, whether time is billed in minimum increments, and whether unused hours roll over.
A further consideration is prioritisation. Clients on blocks are often served after those on recurring agreements, which is reasonable commercially but uncomfortable during a bad week.
Retainers and Capacity Commitments
A retainer reserves expertise or engineering time each month, whether or not it is used, which makes it a commitment to availability rather than to tasks.
When it fits
Retainers make sense where the value lies in access to scarce skills: security work, infrastructure engineering, or environments where change is continuous and interruptions are costly. Mid-size organisations with an internal team but recurring specialist needs often find this the most practical model.
The risks to watch
Under-consumption is the obvious one: paying for capacity you never draw on. Check whether unused time rolls over, how long it accumulates, and the notice period for adjusting the commitment. Also confirm the retained hours come from people with the skills you need, not general administrative work.
Mixed Models Are Common and Often Sensible
Many agreements combine structures. A per-user subscription covers routine support and monitoring; server and network equipment are counted separately; projects are quoted in blocks; and a small retainer reserves planning time each month.
Hybrid pricing is not automatically worse, but it must be legible: each component should show its unit, its rate, and what triggers a change in quantity.
Five Things to Check in Any Pricing Schedule
- The unit is defined precisely — what counts as a user, a device, or an hour of work.
- Inclusions and exclusions are listed for each component rather than described in narrative.
- Change mechanics are stated: how additions, removals and mid-term adjustments are handled.
- Renewal escalation is limited to a stated mechanism rather than left open.
- Reporting exists so you can compare consumption against the forecast at least quarterly.
Frequently Asked Questions
Which model is cheapest?
There is no universal answer: the cheapest model depends on your ratio of users to devices and how predictable your support demand is. The practical test is which structure produces the smallest variation between quoted and final cost over a year.
Should we buy hours instead of a subscription to save money?
It can work for genuinely light needs. The difficulty is that hour-block clients often lack monitoring and preventative work, so problems are found later and cost more time to resolve. The saving is real until something significant fails.
How often should pricing be reviewed?
At minimum annually, and after any material change: a new site, a major hire, an acquisition or a significant technology replacement. A schedule that no longer matches your environment produces disputes regardless of how fair the rate was.
What if the provider refuses to itemise the schedule?
Treat it as a warning. A single blended figure hides what drives cost, making it hard to budget for growth or compare proposals on equal terms.
Match the Model to the Way You Change
The right structure is the one that behaves sensibly when your organisation does something unexpected. Pick a unit that tracks your reality, insist on clear change mechanics, and review the numbers against actual consumption rather than hope.
This article is general information about commercial structures for technology support and is not professional, financial or legal advice. Consult qualified advisers before signing or renegotiating a contract.