Cost factors · Managed IT providers
How managed IT pricing models work and what to compare
Last updated 25 October 2026 · 2 sources listed · Reading time about 3 minutes
Short answer
Managed IT providers usually price per user, per device, as a tiered bundle or as a flat monthly fee, with projects and hardware often charged separately. Cost differences come from scope, service hours, security inclusions and how changes in headcount are handled. Compare by listing included services against your requirements and reviewing how out-of-scope work, onboarding and exit are charged.
Who this is for: A buyer reviewing proposals from several managed IT providers who sees per-user, per-device and flat-fee structures and needs a fair way to compare them.
What to evaluate
Pricing unit
Per-user, per-device and flat models respond differently as you hire, add shared machines or reduce staff.
How to check: Model a plausible growth and shrink scenario against each structure.
Included services
Identical headline figures can cover very different services, from basic helpdesk to patching, backup and security monitoring.
How to check: Build a grid of required services and mark whether each proposal includes, excludes or charges extra.
Service hours and response commitments
Extended hours and fast response require staffing that appears in the cost.
How to check: Ask for support hours, response targets and what happens outside them.
Project and onboarding charges
Setup, migrations and upgrades are frequently billed apart from the monthly fee.
How to check: Request itemised onboarding work and how future projects are estimated and approved.
Licence and hardware handling
Resold licences and hardware introduce margins and renewal dependencies.
How to check: Ask whether licences are held in your name and whether you can buy elsewhere.
Contract flexibility
Long terms and minimums reduce your ability to adjust when circumstances change.
How to check: Read minimum term, renewal and notice rules, and how reductions in scope are treated.
Comparison
| Structure | Scales with | Common catch |
|---|---|---|
| Per user | Headcount | Shared mailboxes, contractors and service accounts may be counted unexpectedly |
| Per device | Number of endpoints and servers | Staff with several devices increase cost and servers may be weighted differently |
| Tiered bundles | Level of service chosen | Needed security items often sit only in higher tiers |
| Flat monthly fee | Agreed scope, regardless of volume | Fair use limits and generous exclusions |
| Time and materials | Hours consumed | Unpredictable totals and weaker incentive to prevent issues |
Decision worksheet
Rate up to three options against this guide’s own criteria. It runs in your browser and saves only on this device. It is a thinking aid, not a recommendation.
1. Have you checked each criterion?
0 of 6 criteria checked.
2. Compare options (0 = fails or unknown, 3 = meets it well)
| Criterion | |||
|---|---|---|---|
| Pricing unit | |||
| Included services | |||
| Service hours and response commitments | |||
| Project and onboarding charges | |||
| Licence and hardware handling | |||
| Contract flexibility | |||
| Total (max 18) | 0 | 0 | 0 |
Questions to ask before you commit
- Which exact services are in the monthly fee and which are charged in addition?
- How is the user or device count measured and how often is it adjusted?
- What rate and approval process applies to work outside the agreement?
- Are licences purchased in our tenancy and under our administrative control?
- What are the charges for onboarding and for ending the agreement?
- How are price increases handled over the term?
- Does the quote include after-hours or emergency support, and on what terms?
Typical trade-offs
Fixed monthly fee versus pay-per-use
- Upside
- Fixed fees make budgets predictable and encourage proactive maintenance.
- Downside
- You may subsidise heavy users and face friction over what counts as in scope.
Bundled licences from the provider versus buying direct
- Upside
- Bundling simplifies invoicing and support.
- Downside
- Reduces transparency and can complicate moving to another provider.
Longer term for a lower unit rate versus flexibility
- Upside
- A longer commitment can improve unit economics.
- Downside
- Locks you in even if service quality drops.
Common mistakes
- Comparing monthly totals without normalising scope. Create one requirement list and price every proposal against it.
- Ignoring onboarding and exit charges until late. Request them upfront in writing.
- Overlooking how contractors, part-time staff and shared accounts are counted. Ask for the counting rules.
- Letting the provider purchase licences in their own account. Insist on ownership in your name.
- Choosing the cheapest tier then buying security add-ons piecemeal. Price the full set you need from the outset.
Related questions
Is per-user or per-device pricing better?
Neither is inherently better; fit depends on your working pattern. Per-user pricing suits staff who use several devices, while per-device pricing can suit organisations with many people sharing machines. Flat fees give predictability but need clear scope. Test each model against realistic changes such as hiring waves, seasonal staff and retiring servers. Check that any shared mailboxes, kiosks and service accounts are treated the way you expect.
Why do proposals for similar organisations differ so much?
Providers differ in how they bundle security, whether helpdesk hours are extended, the level of seniority assigned, tooling and how much project work is included. Some quote minimal scope to win business then bill extras. Others include proactive work in the base price. Compare services, not totals, and ask each provider to describe a typical month of activity for a client like you. The answers reveal what you are actually buying.
How should I budget for projects on top of a managed agreement?
Plan for upgrades, migrations, office moves and security improvements separately. Ask the provider for a rolling roadmap that lists likely work and rough effort, and agree how estimates are approved. Set aside a contingency for unplanned changes. A good provider helps you prioritise rather than pushing everything at once. Review the roadmap during regular service meetings so spending aligns with risk and business priorities.
What hidden costs appear when leaving a provider?
Common ones include fees for exporting documentation, charges for handover meetings, early termination penalties, repurchasing licences held in the provider's account and time spent rebuilding documentation that never existed. Avoid them by owning licences and credentials from the start, requiring documentation as a deliverable and reading exit clauses before signing. Ask the provider to describe their offboarding process and sample timeline in writing.
Sources and further reading
These pages were reachable when we last checked. They informed definitions and rules referred to above; they do not endorse this guide. Where rules differ by country, check the authority for your location.
- Supply chain security guidance — National Cyber Security Centre (UK), retrieved 27 October 2026
- Small Business Guide — National Cyber Security Centre (UK), retrieved 27 October 2026
Related guides
How to choose · Managed IT providers
How to choose a managed IT provider
Choose a managed IT provider by testing how they run service, not how they describe it. Look for a documented onboarding process, clear scope and exclusions, security practices applied to their own systems, named responsibilities for patching and backups, and references from clients similar to you. Contract terms on exit, data ownership and administrative access matter as much as response times.
Comparison · Managed IT providers
Managed IT vs in-house IT vs co-managed IT
In-house IT gives deep knowledge of your business and immediate presence but is limited by individual skills and cover. Managed IT offers breadth, process and cover at the price of dependence on a provider. Co-managed splits duties between an internal team and an external one. The right model follows from your size, specialist needs, risk and ability to hire and retain people.
Problems & fixes · Managed IT providers
When a managed IT provider is not working: diagnosing problems and exiting safely
First determine whether the problem is scope, communication, capacity or competence, using tickets and reports as evidence. Raise concerns formally against the agreement and give a chance to correct. If you leave, secure administrator credentials, documentation, licences and backups before announcing, and plan a staged handover so there is no service gap or unmonitored period.
Cost factors · Endpoint protection
What drives the cost of endpoint protection
Endpoint protection cost depends on device count, which capability tier you license, data retention, any managed monitoring, and the staff time required to run it. Quotes that look similar can hide different definitions of a device, different support levels and add-on modules. Compare total operating effort, not only the licence line.
Comparison · Business operations
Traditional bank versus fintech account for a business
Traditional banks usually offer broader services, direct deposit protection, cash handling and lending relationships, at the cost of slower onboarding and clunkier digital tools. Fintech providers offer speed, integrations and spending controls, but may rely on partner banks, have narrower product sets and different protection arrangements. Many businesses use both for different jobs.
Requirements · B2B software
SaaS contract terms to review and negotiate
Beyond price, the clauses that most affect outcomes are renewal and termination mechanics, data ownership and return, service levels and remedies, liability caps, security and breach commitments, and rules on price changes. Contract law varies by jurisdiction, so treat this as a checklist for conversation with counsel, not legal advice. Negotiate before signature, because leverage drops once data is in the system.
How to choose · Backup and recovery
How to choose a business backup solution
Choose backup by what you must restore and how fast, then test it. Look for protection of every data source including cloud applications, immutable or offline copies that attackers cannot erase, separate credentials from your main environment, encryption, and restore testing you can actually perform. A backup that has never been restored is an assumption, not a control.