Guide IT Management

Costing and choosing an MSP: proposals, cost scenarios and evaluation

Two MSP proposals with the same per-user price can cover very different services. This page shows what to check in a proposal, compares three cost scenarios with the same scope and sets out how to evaluate an MSP before you sign.

16 November 2026
7 min read
Key takeaways
  • Two MSP proposals at the same per-user price can cover very different services: check users and devices, hours, inclusions, limits, on-site visits, tools and project work
  • Ask for a priced example of a typical year, including expected projects and visits, so that extra charges are visible before you sign
  • In the illustrative scenarios, changing one assumption, such as on-site days or salary band, can change the ranking, so compare the scope you need rather than the price per user
  • Agree ownership, access and exit terms before signing: your tenants, domains and licences stay in your name, and the MSP uses individual, revocable, least-privilege access

This page covers what an MSP costs, three cost scenarios with the same scope and how to evaluate a provider. For the real cost of in-house IT, the five points to compare, the four support models and when each one fits, see our in-house IT vs MSP comparison.

What an MSP actually costs

MSPs usually price per user, per device or as a fixed monthly fee. Per-user pricing is common, and the fee depends heavily on what is included. Two quotes with the same price per user can cover very different services.

Before you compare a quote with an internal cost, check:

  • Users and devices covered, including servers, network equipment and mobile devices.
  • Coverage hours: business hours only, extended hours or 24/7, and which hours apply to each priority.
  • Included activities: service desk, patching, monitoring, backup checks, Microsoft 365 administration, starters and leavers.
  • Ticket or hour limits, and the rate charged above them.
  • On-site support: how many visits are included and what extra visits cost.
  • Tools and licences: which are in the fee and which you pay for separately.
  • Projects: migrations, office moves and upgrades are often quoted separately.
  • Specialist services: security monitoring, compliance support or architecture advice may be extra or delivered by a partner.

The monthly fee alone can hide additional charges. Ask for a priced example of a typical year, including expected projects and visits. Our IT budget guide explains how to set a realistic annual figure.

Three scenarios with the same scope

The figures below are illustrative Cyvra estimates, not market quotes. Each scenario describes the same business: a 50-person professional services firm with one office, Microsoft 365, laptops and a few cloud applications. The required scope is identical in all three: a service desk during business hours, device and patch management, endpoint protection, backup monitoring, Microsoft 365 administration, starters and leavers, some on-site help and a modest project budget.

Scenario A: MSP only

  • Managed service: 50 users at £60 per user per month = £36,000 a year, including tools, remote service desk and monitoring during business hours.
  • Extra on-site visits: 12 days at £500 = £6,000.
  • Projects and specialist work: £5,000.

Estimated total: £47,000 a year. Not included: internal time to manage the provider and approve changes. Main trade-off: limited on-site presence, and support is bounded by the contract's scope.

Scenario B: Internal analyst plus tools

  • Gross salary: £38,000.
  • Employer National Insurance: 15% of (£38,000 minus £5,000) = £4,950.
  • Employer pension (assumed 5% of salary): £1,900.
  • Benefits, training and equipment: £1,500 + £2,000 + £1,500 = £5,000.
  • Tools (ticketing, RMM, endpoint protection, backup): £8,000.
  • Cover for holidays and absence through a pay-as-you-go support arrangement: £3,000.
  • Projects and specialist work: £5,000.

Estimated total: £65,850 a year, excluding one-off recruitment costs. Main trade-off: daily on-site presence and business knowledge, but dependency on one person and cover during business hours only.

Scenario C: Hybrid, internal analyst plus co-managed MSP

  • Internal analyst (salary, National Insurance, pension, benefits, training and equipment as in scenario B): £49,850.
  • Co-managed MSP service: 50 users at £25 per user per month = £15,000, including tools, monitoring, second-line escalation and holiday cover.
  • Projects and specialist work: £5,000.

Estimated total: £69,850 a year. Main trade-off: the highest cost of the three, in exchange for on-site presence, backup cover and access to a wider set of skills.

£47K
Scenario A: MSP only, 50 users (Cyvra estimate)
£66K
Scenario B: internal analyst plus tools (Cyvra estimate)
£70K
Scenario C: hybrid, analyst plus co-managed MSP (Cyvra estimate)

Change one assumption, such as the number of on-site days or the pay level, and the order can change. That is why the comparison has to start from the scope you need, not from a price per user.

How to evaluate an MSP

Price matters, but it is rarely the deciding factor on its own. These questions show whether a provider fits your needs.

References from similar businesses. Ask for two or three references from businesses of comparable size and sector. Call them and ask how the MSP communicated during incidents, not just whether it resolved them.

Contracted competences. Check which skills are in the contract, not only in the sales presentation. Operational support experience does not show capability for security programmes, architecture, audits or compliance. If you need those, ask who delivers them, on what terms and at what cost.

SLA detail. Read the SLA in full. Which targets apply to response, restoration and resolution? How are priorities defined? What service credits or other remedies apply if targets are missed, and what is excluded?

After-hours incident handling. Ask how they handle a major incident at 2am on a Sunday, and who is actually on call. The answer, and how confidently they give it, tells you a lot.

Security certifications and controls

ISO/IEC 27001 certification is useful evidence that a provider runs an information security management system. Check that the certificate is authentic and valid (the IAF CertSearch database or the certification body can confirm this), and above all check the certified scope: it may cover a different part of the business from the services you are buying. Certification does not replace your own assessment of the contracted services, how the provider controls access to your systems, how it handles incidents and what the contract makes it responsible for.

Ownership, access and exit

Changing MSP can be complex, so agree the exit arrangements before you sign.

  • Ownership. Your business remains the owner of its tenants, domains, licences, cloud accounts and other digital assets, registered in its own name.
  • Access. The MSP uses individual, delegated and revocable accounts with least privilege and phishing-resistant MFA, not shared administrator accounts. For Microsoft 365, partners can use granular delegated admin privileges (GDAP), which give role-based, time-bound access that you approve; check what your provider uses.
  • Exit. The contract covers documentation, knowledge transfer, revocation of access, return or deletion of data and support during the transition. There is no universal transition period; agree one that fits the size and complexity of your environment.

Data protection

An MSP that can access personal data may act as a processor for some activities and as an independent controller for others, such as its own billing and account management. Under the UK GDPR, processing on your behalf needs a written contract with the processor (Article 28). Document the roles, who authorises access, the security obligations, the use of subprocessors and how incidents are escalated to you.

A simple supplier scorecard

Score each shortlisted provider, and your internal option, on the same criteria:

  • Total annual cost for the same scope
  • Coverage: hours, locations and on-site support
  • Technical competence in the areas you need
  • Security controls and evidence
  • Transition terms, including onboarding
  • Ownership of accounts, data and documentation
  • Exit arrangements and notice period

The question is not whether an MSP is better than in-house IT. It is whether your business needs an IT team or an IT function.

Frequently asked questions

Can an MSP support the specialist software our business uses?

Most MSPs support standard business software: Microsoft 365, common CRM and accounting platforms, and mainstream ERP systems. For highly specialist or custom applications, ask the MSP directly whether they have experience with that software and who supports it when something goes wrong. Where your business depends on specialist software, test the MSP's knowledge of it during the evaluation process before signing.

What happens if our MSP closes or is acquired?

Your protection comes from ownership and access arrangements agreed in advance. Keep tenants, domains, licences and cloud accounts in your company's name, make sure the MSP works through individual, revocable accounts, and require up-to-date documentation throughout the contract. Agree knowledge transfer, access revocation, data return or deletion and transition support. If the MSP is acquired, the acquirer usually takes over existing contracts, but service quality can change, so review the agreement when ownership changes.

Is using an MSP a security risk given they have access to our systems?

Any third party with privileged access is a risk to manage. Assess the provider's security maturity in proportion to the risk and the access you grant: named individual accounts, least privilege, phishing-resistant MFA, logs you can review and a clear incident process. ISO/IEC 27001 certification with a relevant scope is useful evidence, and requiring it can be reasonable where the access and risk justify it. An under-resourced internal function can also leave security gaps.

How long does the transition to an MSP take?

There is no standard duration. It depends on how well your environment is documented, whether you have an accurate inventory of devices and accounts, how access is organised and how complex your systems are. A typical sequence is discovery and documentation, deployment of monitoring and management tools, then knowledge transfer. Keep your existing support in place and complete the handover only after you have verified that the new provider can handle incidents independently.

Ryland Deakin
About the author
Lead Consultant, Cyvra · CISM · CompTIA Security+ · MCP

Ryland has delivered cybersecurity, compliance, and IT management programmes for regulated organisations across the UK and the Netherlands for over 20 years. View full profile

Talk to Cyvra

Find out what IT model fits your business

We are an independent consultancy and do not sell support contracts. We assess your current setup and help UK businesses decide what mix of in-house and managed support makes sense.

Disclaimer: This article is for general informational purposes only and does not constitute legal, regulatory, or professional advice. Cyvra makes no warranty as to the accuracy or completeness of this content, which may not reflect the most current regulatory developments. Readers should seek independent legal and regulatory advice appropriate to their specific circumstances. Cyvra accepts no liability for any loss arising from reliance on this content.