Most managed IT providers charge in one of a handful of ways: per user, per device, in tiers, as a flat monthly fee, à la carte, or by the hour when something breaks. The right model is the one where your bill stays predictable while the provider stays responsible for outcomes, not just for hours worked. This guide explains how each model works, where each one leaks money, and how to compare quotes that look nothing alike.
TL;DR
- Common structures include per-device, per-user and all-inclusive pricing, according to TechTarget's coverage of managed IT services. Tiered, à la carte and hourly break-fix variants sit around them.
- Per-user and per-device quotes are easy to compare, but they say little about what the provider is accountable for. SLA-based and flat-rate agreements tie the fee to the service you actually receive.
- The monthly fee is rarely the whole cost. Ask about onboarding, projects, security tooling, compliance work and after-hours support before you sign.
- Compare quotes on one yardstick: the total annual cost for your headcount, devices and risk profile, with the scope written out line by line.
- Hourly break-fix is cheapest only in quiet months. It has no built-in monitoring or prevention.
Table of Contents
- The six managed IT pricing models at a glance
- Per-user pricing
- Per-device pricing
- Tiered pricing
- Flat-rate and all-inclusive pricing
- SLA-based and value-based pricing
- À la carte pricing
- Break-fix and time-and-materials billing
- What the monthly fee usually leaves out
- What shapes the price you are quoted
- How to compare quotes fairly
- How to tell whether you are getting value
- Our perspective
- Putting it together with Nexus
- FAQ
- Sources
The six managed IT pricing models at a glance
Providers mix and rename these, but nearly every proposal you receive is built on one of the following.
| Model | You pay | Best for | Main risk |
|---|---|---|---|
| Per user | A fixed fee per employee per month | Teams where staff use several devices each | Cost grows with every hire, including part-timers and contractors |
| Per device | A fixed fee per endpoint or server per month | Shared workstations, shops, clinics with many shared terminals | Phones, tablets and new equipment can inflate the bill |
| Tiered | One of 3 to 4 bundled packages | Buyers who want a clear menu | The feature you need sits one tier above the one you can afford |
| Flat rate / all-inclusive | One fixed monthly fee for a defined scope | Owners who want a stable budget | Vague scope leads to disputes over what "all" covers |
| À la carte | Individual services, each priced separately | Companies with a capable internal IT lead | Gaps between services and a bill that creeps upward |
| Break-fix / time and materials | An hourly rate when something fails | Very small, low-risk setups | No prevention, and an unpredictable bill in a bad month |
The sections below take each in turn.
Per-user pricing
You pay a set amount for every person on your team each month. That fee typically covers help desk support, device management and a baseline of security for everything that person uses: laptop, phone, cloud accounts.
Why buyers like it. Budgeting is simple. Twenty-five employees at a given rate is a line you can forecast, and you do not have to count devices.
Where to look closely.
- Does the price cover every device each person uses, or only one?
- How are shared mailboxes, service accounts, contractors and seasonal staff counted?
- Is there a minimum user count, and what happens to the fee when you shrink?
A worked example with made-up numbers: if a quote were $150 per user per month and you had 40 employees, the monthly fee would be $6,000, or $72,000 a year. Add five contractors who each need accounts and the annual figure rises by $9,000. Counting rules matter as much as the rate.
Per-device pricing
Here the fee follows the hardware: workstations, laptops, servers, sometimes network gear. It suits environments where several people share machines, such as a clinic front desk or a warehouse, because headcount tells you little about the number of endpoints.
The weakness is that your IT footprint rarely stays still. Every tablet, point-of-sale terminal or new server nudges the bill up, and it is easy to leave unmanaged devices outside the contract, which is exactly where attackers look. Ask for a written device inventory at signing and a rule for how additions are priced.
TechTarget's coverage of managed services pricing points out that per-device and per-user models are easy to quote, yet offer less protection than SLA-based pricing, which reflects the risk and value actually delivered to the client. That is the central tension in this whole topic: simple to price is not the same as simple to hold accountable.
Tiered pricing
Tiered plans offer three or four packages. A typical ladder looks like this:
- Basic: remote monitoring and management, patching, antivirus and a basic help desk.
- Standard: adds backup, vendor management and stronger security controls.
- Premium: adds strategic planning (often called a virtual CIO), compliance support, advanced security and on-site help.
Tiers make a proposal easy to read, and they give you a path to grow. The trap is a feature that matters to your business, such as multi-factor authentication enforcement, immutable backups or audit evidence, sitting in a tier above the one the salesperson quotes first. Read the feature list, not the tier name.
Flat-rate and all-inclusive pricing
A flat rate is one fixed monthly fee for a defined scope of work. Done well, it is the most predictable model for an owner: the invoice does not change because a server failed or a laptop was lost. It also aligns incentives. If the provider is paid the same whether or not you have outages, it is motivated to prevent them.
The quality of a flat-rate deal comes down to the scope document. Before you sign, make sure it states:
- Which services, systems and locations are covered.
- Response and resolution targets, in writing, with a remedy if they are missed.
- What counts as a project and is billed separately, such as an office move or a cloud migration.
- How the fee is adjusted when your headcount or footprint changes.
If you want to see how a single-vendor, fixed-fee arrangement fits into a wider IT strategy, our guide to managed IT services walks through scope and expectations in more depth.
SLA-based and value-based pricing
This is a close cousin of flat-rate pricing. The fee is set by the service levels promised and the business risk covered, such as how fast a critical incident is acknowledged, how much downtime is tolerable and what recovery targets apply to key systems. A hospital billing system and a marketing-agency file share do not carry the same risk, so they should not be priced the same way.
As managed service providers mature, industry commentators describe a move toward pricing that matches a client's security and redundancy needs rather than counting seats. For buyers this is good news, provided the SLA has teeth: measurable targets, reporting you can see and a consequence for misses.
À la carte pricing
You pick individual services, such as monitoring, backup or help desk, and each has its own price. It can work if you already have a strong in-house IT person and only need to fill specific gaps. The danger is the seams. When three services come from three line items, nobody owns the problem that falls between them, and the total often ends up above a bundled price. If you are filling gaps around an existing team, a co-managed arrangement is worth comparing with buying separate pieces.
Break-fix and time-and-materials billing
Break-fix means you call when something is broken and pay an hourly rate for the repair. There is no ongoing monitoring, patching or planning in that price, because nobody is paid to look for problems before they happen.
It can be a reasonable fit in a few narrow situations:
- A very small office with few devices and no regulated data.
- A one-off project, such as a network cabling job, where the work is defined and finite.
- A short bridge period while you evaluate a longer-term provider.
For any business holding customer records, payment data or patient information, a reactive model leaves the preventive work undone. The cost shows up later, in a single large incident invoice.
What the monthly fee usually leaves out
Two quotes with the same monthly number can differ by thousands over a year. Ask about each of these line by line.
- Onboarding and setup. Some providers charge a one-time fee to inventory systems, deploy agents and document the environment. Others fold it into the first months.
- Projects. Migrations, office moves, hardware refreshes and major upgrades are frequently billed apart from the monthly service.
- Security tooling and services. Find out whether endpoint detection, email filtering, 24/7 monitoring and incident response are inside the fee, or sold as add-ons.
- Compliance work. Assessments and audit support for frameworks such as HIPAA, SOC 2 or PCI DSS are often scoped separately from day-to-day support.
- After-hours and on-site support. Check whether evenings, weekends and site visits carry a surcharge.
- Hardware, licences and cloud consumption. These may be pass-through costs at the vendor's price or marked up.
- Contract terms. Look at term length, auto-renewal, price escalators and the notice you must give to leave.
- Exit. Confirm you keep ownership of your documentation, credentials and data, and how a handover would work.
What shapes the price you are quoted
Several factors move any model up or down, whichever you choose:
- Headcount and device count. The base for both per-user and per-device pricing.
- Security depth. Basic antivirus is a different product from managed detection and response with round-the-clock analysts. For organizations holding sensitive customer or patient data, one buyer's guide argues that this deeper coverage is now a baseline expectation rather than a premium extra.
- Compliance obligations. Healthcare, payments and public-company suppliers need evidence trails, which means more documentation and review.
- Cloud footprint. Workloads in AWS, Azure or Google Cloud add configuration, cost and access management work.
- Support hours. Eight-to-five coverage costs less than 24/7.
- Environment quality. A messy network with unsupported systems takes more effort to stabilize.
How to compare quotes fairly
Because providers choose different models, convert every proposal to the same measure.
- Write down your own inputs: employees, contractors, devices, servers, locations, cloud platforms and compliance frameworks.
- Ask every provider to quote against that same list, and to state what is excluded.
- Calculate the first-year total: twelve monthly fees, plus onboarding, plus the projects you already know you need.
- Divide by headcount to get a per-user figure you can compare across per-user, per-device and flat-rate bids.
- Score accountability: response targets, reporting, named contacts and what happens when targets are missed.
- Check the exit terms before the price.
A cheaper bid that excludes security monitoring is not cheaper. It is a smaller product.
How to tell whether you are getting value
A managed IT contract earns its fee when you can point to fewer disruptions, faster resolution and risks you can name and see being reduced. Ask for monthly reporting on ticket volume and resolution times, patch compliance, backup test results and open security findings. Review the contract yearly against your growth: a plan sized for 20 people is a poor fit at 45. Pair that review with a look at your downtime and incident history over the same period.
Our perspective
Fragmented IT is the most expensive kind. When one company handles help desk, another does security, and a third looks after the cloud, each invoice looks reasonable and the total is hard to explain. Worse, when something goes wrong, each party can point to the next.
That is why we favor a single, flat monthly fee for a clearly written scope, with security, cloud, network and compliance work under one agreement and one SLA. You get one point of accountability and a bill that does not change with the month's ticket count. Our approach is built around senior practitioners in each domain, so the person answering your hard question is not a generalist reading a script.
Whatever model you choose, insist on three things: a scope you can read in plain language, service levels with consequences, and no surprise invoices. A price that is easy to quote but leaves the provider unaccountable for outcomes is a poor bargain.
Nick - Sr. Executive
Putting it together with Nexus
If you want one provider for managed IT, cybersecurity, cloud, network, compliance and data protection, with fixed monthly pricing and a single SLA, take a look at the Nexus services. We scope each engagement to your environment, so pricing follows what you actually need.
For a closer look at how bundled services reduce vendor sprawl, read about the business benefits of integrated IT providers. When you are ready to talk numbers, start from our main site and bring your headcount and device list.
FAQ
Which managed IT pricing model is most common?
Per-device, per-user and all-inclusive structures are the ones most often described in coverage of the managed IT market. Many providers layer tiers on top of a per-user rate. The most common is not automatically the best fit, so test it against your own headcount and risks.
Is flat-rate managed IT pricing better than per-user pricing?
It depends on what you value. Flat-rate pricing gives a steadier budget and ties the fee to a written scope, while per-user pricing is simpler to scale with headcount. Many buyers get both by choosing a fixed monthly fee that is calculated from a user count and has clear rules for changes.
When does break-fix make sense?
Break-fix suits very small offices with few devices and no sensitive data, or a one-off project with a defined end. It includes no proactive monitoring or maintenance, so it is a poor fit once you handle customer, payment or patient information.
What should I budget for beyond the monthly fee?
Ask about onboarding, projects such as migrations, security add-ons, compliance assessments, after-hours support and licences. Request a first-year total in writing so you can compare proposals on the same basis.
How do I compare an hourly quote with a monthly one?
Estimate how many hours you used last year, including emergencies, and price them at the hourly rate. Then compare that to twelve months of the recurring fee, remembering the monthly plan includes monitoring and prevention that the hourly plan does not.
Sources
- Managed IT service coverage, TechTarget
- Managed services pricing models: per-device vs. SLA-based approach, TechTarget
- Managed security services provider buyer's guide, EK Frazo