Fixed Fee vs Per-User IT Support Pricing: A CFO's Guide

What are the main ways IT support is priced?

Most business IT support in the UK is sold under one of six commercial models: break-fix, hybrid, per-user all-inclusive, per-device, a single fixed monthly fee, or a tiered package. The names overlap, and providers use them loosely, so the label on a proposal tells you less than the schedule of inclusions behind it.

For a finance director the useful lens is variance. Each model moves a different amount of cost risk from the provider to your business. Break-fix leaves nearly all of it with you. A well-scoped all-inclusive model moves most of it to the provider, in exchange for a higher and steadier monthly charge.

This guide explains each model in plain terms, shows how a low headline price can turn into a higher annual cost, and gives you a worksheet and a scope checklist to test any quote. It does not repeat the market-level cost ranges, which are covered in our IT support pricing and cost guide. Here the focus is how the contract is built, not what the market charges.

• Break-fix: you pay for each fault, usually by the hour or the visit, with no recurring fee.
• Hybrid: a smaller monthly fee covers some tasks, such as monitoring or a help desk with limits, and everything else is billed as extra.
• Per-user all-inclusive: one monthly price per user covers a defined, broad scope including help desk, monitoring, security tooling and routine changes.
• Per-device: the price is set by the number of laptops, servers and other devices managed, not by people.
• Fixed monthly fee: one agreed sum for a defined scope, often derived from a user or device count at the outset.
• Tiered: bronze, silver and gold style packages with rising inclusions and rising prices.

How does break-fix pricing work, and when is it reasonable?

Break-fix is the oldest model. Something stops working, you call, and you are charged for the time and parts. There is no retainer, no monitoring and no commitment. The provider earns money when things go wrong, which is the structural weakness: their income and your uptime pull in opposite directions.

That does not make it a poor choice in every case. It is a sensible arrangement when the estate is small and simple, when downtime is cheap, and when the business already has someone competent in-house who only needs occasional specialist help. A 10-person studio with cloud-based tools and no regulated data may reasonably prefer to pay as it goes.

It becomes hard to defend as the business grows. A 50+ seat organisation has more users, more devices, more cloud tenancies and more third-party systems. Faults are more frequent, security exposure is greater, and the cost of an afternoon of lost productivity across a team is far larger than the callout fee. We cover this transition in more detail in our guide on outgrowing a break-fix IT provider.

Where break-fix works well

• Very small teams: a handful of users on standard cloud tools, with little regulated or customer data.
• Fixed-scope projects: an office move or a server replacement quoted as a defined project is commonly priced this way, even by managed providers.
• Specialist top-ups: an internal IT team that needs occasional extra hands on a specific platform.
• Short-term cover: a gap while you recruit, where you do not want a long contract.

Where break-fix costs more than it appears

The invoice for a single call looks small. The cost sits elsewhere: unmonitored backups that fail silently, patches applied late, licences that lapse, and no one reviewing security settings until an incident forces the issue. Those costs do not appear on the break-fix invoice, so they never appear in the comparison.

What is hybrid pricing and where do the extra costs appear?

Hybrid contracts sit between break-fix and a full managed service. You pay a monthly fee for a limited set of services, commonly remote monitoring, antivirus and a capped number of help desk tickets or hours. Anything outside that list is charged at a day rate or hourly rate.

The attraction is a lower monthly figure. The risk is that the contract scope is narrower than the buyer assumes. 'Support' in a sales conversation can mean unlimited help desk. In the schedule it may mean a defined number of hours, remote only, in business hours, for named systems. The gap between the two is billed at the rate card.

Hybrid is not a flawed model in itself. It can suit a business with a capable internal IT lead who wants monitoring and escalation support but not a full service. The problem arises when a business with no internal IT buys hybrid expecting full coverage, then discovers that the first major incident, a Microsoft 365 migration or an office move sits outside the monthly fee.

Typical out-of-scope charges in hybrid and break-fix contracts

• Projects: anything described as a change, migration, rollout or upgrade, including work on your own systems.
• Onsite attendance: engineer visits charged per visit or per half day, plus travel time.
• After-hours and weekend work: premium rates that can be double the standard day rate, depending on the contract.
• Hardware and licences: supplied at list price or with a margin, sometimes with procurement fees.
• Security incidents: investigation and remediation time billed as additional work.
• New starters and leavers: charged per request rather than included.

How do per-user, per-device, fixed fee and tiered models compare?

The four recurring models look similar on a quote but behave differently when your business changes. A new starter, a second site or a move to cloud-based servers can change what you pay under one model and leave it untouched under another. The table below compares them on the points a finance team usually cares about.

In practice, per-user and fixed fee often describe the same arrangement. A provider may calculate a fixed monthly figure by multiplying your users by a per-user rate and then fix it for a period. The distinction matters at renewal and when headcount changes, so ask how the fee moves if you add or remove ten users.

Per-device pricing deserves a closer look

Per-device pricing is easier to justify when the number of devices does not track headcount. A warehouse with shared scanners, or a school-style environment with shared machines, may be cheaper per device than per person. For an office-based team where each person has a laptop, a phone and often a tablet, per-device can cost more than per-user for the same people, and the definition of 'device' becomes a negotiation point.

Tiered pricing and the missing feature

Tiered packages are easy to compare at a glance and easy to misread. The feature you consider essential, perhaps 24-hour cover or managed endpoint detection, may only appear in the top tier. Always map your must-have list against each tier before comparing prices, and check whether a mid-term upgrade requires a new contract. If out-of-hours support matters to you, our guide on whether you need 24/7 IT support sets out how to decide.

How can a low headline price end up costing more?

A headline price is the figure on the front of the proposal. The annual cost is everything you actually pay over twelve months to keep the same standard of service. The two diverge when work that you regard as normal is classed as extra.

This is rarely a sign of bad faith. Providers price to a defined scope, and a narrower scope gives a lower price. The difficulty is that a buyer reading 'unlimited support' on a summary page may not read the exclusions three pages later. Variable charges also make planning harder for the provider's own finance team, so many prefer to avoid them, but not all do.

An illustrative comparison

The scenario below is illustrative, with no real prices, and shows how the structure of a contract changes the annual shape of the cost for a 60-seat business.

• Contract A (lower headline): a hybrid fee covering monitoring and a capped number of remote help desk hours. In a normal month the invoice matches the quote. In the month the business opens a second office, upgrades its servers and loses a key user to a phishing attack, project work, onsite visits, after-hours remediation and new hardware are all billed on top.
• Contract B (higher headline): a per-user all-inclusive fee covering help desk, onsite attendance within agreed boundaries, routine changes and security tooling. The monthly invoice is higher, but it is the same in every month, and only separate projects and hardware are quoted additionally.
• The comparison: Contract A is cheaper in eleven quiet months and more expensive in the twelfth, and the twelfth month is the one the finance director has to explain to the board.

Whether Contract A or B costs more across the year depends on how many such events occur. That is the point: you are buying a distribution of outcomes, not a number. A finance leader who is comfortable with variance, and has a contingency, may rationally prefer A. One who needs predictability should price B.

Our IT support contract renewal checklist covers the clauses that most often change the real cost at renewal, including auto-renewal, indexation and minimum terms.

Why does an all-inclusive per-user model suit a 50+ seat finance team?

Above roughly 50 users, three things change. The volume of routine requests becomes continuous rather than occasional. The security exposure widens, because more accounts, devices and suppliers mean more ways in. And the cost of disruption rises, because more people are idle when something fails. These conditions favour a model in which the provider is paid for keeping things running, not for fixing them.

A managed IT support contract priced per user and scoped broadly shifts variable costs into a fixed monthly fee. Day-to-day requests, monitoring, patching, endpoint security and the help desk sit inside it. The finance team can forecast IT operating cost against headcount, which is how most other per-employee costs are already planned.

• Forecastable: cost moves with headcount, so a hiring plan translates directly into an IT cost line.
• Aligned incentives: the provider benefits from fewer incidents, because every avoidable fault consumes time they have already been paid for.
• Easier approval: a single monthly invoice is simpler to approve, audit and allocate to departments than a stream of ad hoc invoices.
• Lower negotiation load: fewer quotes to approve for routine work means less friction between the business and its provider.
• Clearer exit: a defined scope makes it easier to compare a replacement and plan a handover.

A per-user model also lines up with how licences and security tools are usually priced. Microsoft 365, endpoint protection and backup are all commonly charged per user, so a per-user support fee sits naturally alongside them. If you are weighing the wider service picture, the managed IT services page sets out how the components fit together.

When all-inclusive per-user is not the right answer

It is not always the better value. A business with an experienced internal IT team and a stable estate may pay for services it does not use. A business with fewer than around 15 to 20 users may find the per-user minimum disproportionate. And a business with unusual requirements, such as large numbers of shared devices, may be better served by a device-based or bespoke arrangement. A short IT consultancy engagement can help you test which fits before you commit.

What should be inside or outside the scope of an IT support contract?

Scope is where price comparisons succeed or fail. The table below is a checklist of the six areas that most often cause disputes or surprise invoices. For each, ask the provider to state whether it is included, included with limits, or charged extra, and to put the answer in the contract rather than the proposal.

Three points deserve emphasis. First, security tooling is often sold as an add-on, and it is increasingly expected by insurers and customers. Check whether managed endpoint detection, for example, is included or priced per device as an extra, and see how managed EDR services are typically structured. Wider cyber security services such as audits and testing are usually separate engagements, so confirm where the boundary lies. Third, ask who owns the documentation and administrative credentials. They should be yours.

Fair-use terms

Even an all-inclusive contract may include fair-use language, for instance limits on the number of project hours or the frequency of onsite visits. These are reasonable in principle, since the provider cannot offer unlimited engineer time for a fixed fee. Ask for the thresholds in writing and what happens when they are exceeded, so that an extreme month does not become a dispute.

The response and resolution commitments that sit alongside scope are covered separately in our guide to IT support SLAs.

How do you build a total cost of ownership worksheet?

A total cost of ownership worksheet asks you to place every cost of keeping IT running, not only the support fee, into one view for each option you are considering. It works because it forces the out-of-scope costs onto the page. Fill in each row with your own figures or with figures obtained from the provider in writing. The cells below are deliberately blank.

Two rows are routinely left blank by buyers: internal staff time and downtime. Both are real. An office manager who spends a day each week chasing IT issues is an IT cost, even though it never appears on a supplier invoice. Downtime has a cost per hour that your own payroll data can estimate, using the number of affected users and their loaded cost.

Run the worksheet for a quiet year and for a difficult year. If the options are close in the quiet year and far apart in the difficult one, you have found the variance you are paying to avoid.

How should a finance team budget for IT support?

Budgeting for IT support is easier once you separate three types of cost: the recurring service fee, planned capital items, and a contingency for the unplanned. Mixing them together is what makes IT feel unpredictable.

1. Fix the run cost first. Set the recurring support fee, licences and security tooling against headcount, and review it when the hiring plan changes.
2. Plan hardware on a cycle. Laptops and network equipment have a finite life. Spread replacement across years instead of buying in a lump, and record the cycle in the budget.
3. Schedule the projects you already know about. A Microsoft 365 tenant tidy-up, a Wi-Fi upgrade, an office move or a Cyber Essentials assessment can all be forecast twelve months ahead.
4. Hold a contingency. Even an all-inclusive contract leaves room for genuine projects and emergencies. Set a modest reserve and define who can approve its use.
5. Review annually. Agree a review date, with the provider, where scope, headcount and strategy are checked against what you are paying for.

Technology roadmapping is where a virtual CIO service is often useful for finance. It turns a vague wish list into a costed multi-year plan, so that the capital items and projects you need are in the budget before they become urgent.

Use the pricing guide to sense-check the market, then watch indexation. Many contracts include an annual price increase tied to an index or a fixed percentage. Check the mechanism, the cap and the notice period, because an uncapped increase can erode the predictability that a fixed fee was supposed to provide.

Contract term and flexibility

A longer term often brings a lower rate, and a shorter one gives you flexibility. Neither is correct for everyone. What matters is that the contract states how headcount changes are handled, whether you can reduce user numbers mid-term, and what the exit and handover obligations are. These terms matter more than a small difference in monthly rate.

What should you ask before signing?

Use the following questions in your final round of evaluation. They are designed to surface cost variance and scope boundaries, and they work whether you are choosing a first provider or reviewing an existing one.

1. What is not included? Ask for a one-page list of exclusions, and the rate card for everything on it.
2. How is a project defined, and is there a threshold below which changes are included?
3. What happens if our headcount rises or falls by ten percent mid-term?
4. Who owns the licences, documentation and administrative credentials, and how do we get them on exit?
5. What is the price increase mechanism at renewal?
6. What security services are included, and which are optional?
7. What does a bad month look like? Ask the provider to describe the most expensive month a comparable client has had, in general terms, without naming them.

These questions also help you judge the provider. One that answers them clearly and in writing is easier to work with over a three-year term than one that prefers to keep the discussion at headline level. For a wider evaluation framework, see our guide to choosing an IT support company, and the buyer's guide for businesses with 50 or more users.

If you would like a second opinion on a quote, or want to see how a per-user structure would apply to your headcount, you can speak to the NetMonkeys team. Our managed IT support team can walk through the structure with you. A conversation costs nothing, and a comparison against your current spend is usually the most useful starting point.