Mid-Sized MSP
Can combine personal service with resilient teams, broader skills and mature processes. Often a strong fit for organisations with 50 to 500 users.

Don't compare IT providers by what they promise. Compare what they can prove.
Most proposals sound similar. The differences often appear in what happens after an alert, who actually answers the phone, what security is included, how risks are reported, how much your organisation matters to the provider and what happens when something goes wrong.
Every IT proposal seems to promise responsive support, proactive monitoring, cybersecurity, strategic advice, dedicated account management, 24x7 capability and expert engineers. The same words can describe very different services.
The difference between IT providers is often hidden in what happens after the promise.
This guide helps you compare business IT support providers across the areas that materially affect employee experience, risk, security, business continuity, cost, governance and future capability. It is designed for organisations comparing several providers, reviewing current service quality, replacing an MSP or preparing an IT support tender.
Before you compare managed IT support providers, agree the operational responsibility you want them to take. You cannot compare proposals fairly until every provider is pricing the same responsibility.
Provider takes agreed operational ownership.
External specialists strengthen an internal IT team.
Several providers require clear coordination and ownership.
You cannot compare proposals fairly until every provider is pricing the same responsibility.
Fully managed and co-managed delivery describe how work is divided with your team. Your wider sourcing model determines how technology suppliers are coordinated and who owns dependencies between them. Read more about choosing an IT outsourcing model or how co-managed IT supports internal teams before asking providers to price the same brief.
The right provider is not necessarily the biggest or the cheapest. Provider size affects personal attention, skills, process maturity and adaptability. For organisations with approximately 50 to 500 users, the right-sized MSP can be almost as important as the services themselves.
You need enough scale for resilience and specialist skills, but not so much scale that your organisation becomes just another account.
Small, mid-sized and larger MSPs can all be excellent in the right circumstances. These ranges are indicative rather than industry-standard definitions. Use the profiles to understand practical trade-offs, not as a ranking.
Can combine personal service with resilient teams, broader skills and mature processes. Often a strong fit for organisations with 50 to 500 users.
Can provide the specialist teams, security and resilience a growing organisation needs, while retaining direct relationships, flexibility and senior access. For organisations with 50 to 500 users, this can offer a compelling balance of capability and cost.
Typical characteristics, not guarantees. Individual providers vary considerably.
A provider may have impressive capabilities, but those capabilities only matter if your organisation receives meaningful access to them.
The question is not simply how big the provider is. It is how much of that organisation will genuinely be available to you.
Every provider can make a promise. Use this framework to ask what happens in practice, request evidence and identify answers that still need investigation.
What to compare
Who actually begins troubleshooting, the technical capability at first contact and the routes available to employees.
Ask this
When an employee calls or starts a chat, do they reach an engineer who can begin helping, or someone who simply logs and passes on the request?
Good evidence might include
Be cautious if
The provider discusses response times but cannot explain who begins technical troubleshooting.
What to compare
Who answers outside office hours, what they can resolve and which users and events are covered by the agreed fee.
Ask this
At 10pm, who answers, what can they resolve, and which users and incidents are included in our fee?
Good evidence might include
Be cautious if
The phrase 24x7 is used without explaining whether it is staffed support, monitoring or an on-call arrangement.
What to compare
Whether device health, events and trends become owned corrective work before users report disruption.
Ask this
Show us a recent issue you identified and corrected before a user reported it. What triggered the intervention?
Good evidence might include
Be cautious if
The provider says it monitors everything 24x7 but cannot show how monitoring becomes action.
What to compare
Asset ownership, dependencies, support status, firmware, capacity and action on meaningful infrastructure alerts.
Ask this
If a backup internet connection fails while employees can still work, who notices, who acts and how do you verify resilience has been restored?
Good evidence might include
Be cautious if
The provider can list monitoring tools but cannot identify ownership of the underlying estate.
What to compare
The workflow linking approvals, device readiness, provisioning, access removal, exceptions and proof of completion.
Ask this
Show us how you would prepare a new starter and prove that a leaver's access has been removed across the agreed systems.
Good evidence might include
Be cautious if
The process relies on email requests with no reliable record of whether every action was completed.
What to compare
Which protections and remediation activities are included, what needs deployment and what enhanced services cost extra.
Ask this
Which security protections and remediation activities are included as standard, what needs deployment, and what costs extra?
Good evidence might include
Be cautious if
Security is described through product names alone, without an accountable operational process.
What to compare
Privileged access, customer separation, management systems, controlled integrations and the practical blast radius of an incident.
Ask this
If one of the systems you use to manage us were compromised, what would prevent the attacker reaching our users or servers?
Good evidence might include
Be cautious if
The provider can discuss customer security but has no clear answer about security of its own privileged tooling.
What to compare
Current certification, the scope it covers and how controls translate into the service your organisation will receive.
Ask this
Can we inspect your current certifications and their scope, and understand how those controls apply to our service?
Good evidence might include
Be cautious if
A logo is presented as proof without current certificates, scope or operational context.
What to compare
Whether service views make risks, recurring problems, security, actions and commercial responsibilities visible.
Ask this
Show us the service view we would receive. How would we identify unresolved risks, recurring problems and overdue actions?
Good evidence might include
Be cautious if
Reporting consists only of ticket counts or selectively chosen percentages without context.
What to compare
Named relationship ownership, regular governance, escalation, risk registers, roadmaps and coordination across suppliers.
Ask this
When an issue involves several suppliers, who coordinates resolution and keeps us informed?
Good evidence might include
Be cautious if
Responsibility falls between suppliers, with no one accountable for keeping the business informed.
What to compare
What turns support work into a project, how scope is discovered and what can change an agreed fixed price.
Ask this
What turns a service request into a chargeable project, and what could change an agreed fixed price?
Good evidence might include
Be cautious if
The provider offers a fixed price without explaining scope, dependencies or change-control assumptions.
What to compare
Who develops the technology roadmap, how business priorities shape recommendations and access to relevant specialist skills.
Ask this
Who develops our technology roadmap, and can you demonstrate how a client's business priorities changed your recommendations?
Good evidence might include
Be cautious if
Strategy is limited to an annual sales review or generic product presentation.
What to compare
Restore testing, recovery objectives, supplier dependencies, communication arrangements and actual learning after a test.
Ask this
Show us a recent recovery test. What worked, what failed and what changed afterwards?
Good evidence might include
Be cautious if
A successful backup job is treated as evidence that the business can recover.
What to compare
The realistic annual cost, including recurring fees, onboarding, starter devices, visits, projects, licences, renewals and exit.
Ask this
Price a realistic year against our requirements. Which events could still generate additional invoices?
Good evidence might include
Be cautious if
The lowest monthly rate is compared without checking the costs that sit outside it.
What to compare
Takeover discovery, documentation, readiness, supplier coordination, administrative account transfer, data ownership and comparable references.
Ask this
What must be verified before takeover, and what happens to our accounts, configurations, documentation and data if the relationship ends?
Good evidence might include
Be cautious if
Onboarding is described as a project plan but the provider cannot explain transition readiness or exit arrangements.
These questions do not reward polished claims. They reveal evidence, ownership and the operating model beneath the proposal.
This reveals whether proactive means more than monitoring dashboards.
If important risks exist, they should be visible, owned and tracked.
This reveals how seriously the MSP treats privileged access and supply-chain risk.
Support, monitoring, security, backup and strategy can appear in almost every proposal. The important difference is what each service actually does.
Provider A might mean
Endpoint antivirus licence, Microsoft defaults and basic patching.
Provider B might include
Managed endpoint protection, SOC, vulnerability management, identity monitoring, incident response and critical remediation process.
Comparing feature names is easy. Comparing what the service actually does is harder and much more important.
For a closer view of prevention in practice, read what happens to your IT while nobody is watching and the warning signs your IT provider can see.
Score up to three providers against the same evidence standard. The names and scores stay only in this browser while you are viewing this page. This is a decision aid, not an independent certification.
No personal data is required. Provider names are editable locally and are not sent to analytics. Both comparison modes use the same provider names, but keep their evidence scores separate.
Brief Comparison - 5 categories
Unanswered categories remain unanswered. An explicit Unclear score records missing or unavailable evidence.
Assess effective technical help, engineer accessibility, available contact channels, ownership and resolution capability.
Current Provider
Provider 2
Provider 3
Assess prevention of recurring problems, infrastructure management, device health, reliability and practical improvement.
Current Provider
Provider 2
Provider 3
Assess cybersecurity, vulnerability management, protection of the provider's own systems, security response and recovery capability.
Current Provider
Provider 2
Provider 3
Assess service reporting, performance evidence, risk visibility, accountability and clear responsibilities.
Current Provider
Provider 2
Provider 3
Assess dedicated consulting, roadmaps, technical expertise, project delivery, change capability and organisational fit.
Current Provider
Provider 2
Provider 3
Brief Comparison - 5 categories
These scores are a record of evidence, not a definitive ranking. Compare only within this mode because the Brief and Detailed assessments use different category counts.
0 of 5 categories assessed
Strongest demonstrated areas
No areas demonstrated with evidence yet.
Areas requiring further evidence
No categories have been explicitly marked unclear.
Still unanswered
IT Support & Responsiveness, Proactive IT Management, Security & Resilience, Transparency & Governance and 1 more
0 of 5 categories assessed
Strongest demonstrated areas
No areas demonstrated with evidence yet.
Areas requiring further evidence
No categories have been explicitly marked unclear.
Still unanswered
IT Support & Responsiveness, Proactive IT Management, Security & Resilience, Transparency & Governance and 1 more
0 of 5 categories assessed
Strongest demonstrated areas
No areas demonstrated with evidence yet.
Areas requiring further evidence
No categories have been explicitly marked unclear.
Still unanswered
IT Support & Responsiveness, Proactive IT Management, Security & Resilience, Transparency & Governance and 1 more
We welcome the same questions and evidence standards. Our team can show you how our approach works in practice.
Compare WavexUncertainty is useful. It tells you what to investigate before signing.
Show us our current critical vulnerabilities and their remediation status.
When was the last successful restore test and what was actually restored?
Show us current patch compliance and any exceptions.
Show us examples of issues corrected before users reported them.
Who covers our key technical areas when the usual engineer is unavailable?
People can get effective help quickly.
The provider identifies deterioration and risk before users experience the consequences.
Core controls are embedded, vulnerabilities are managed and security incidents have defined response processes.
Customers can see service quality, risks, actions and performance.
The provider helps the organisation evolve rather than simply maintaining the status quo.
Use these related resources at the point they are useful, rather than treating a provider comparison as a one-off exercise.
Turn the questions in this guide into clear requirements, evidence and evaluation criteria.
Decide which responsibilities should stay in-house and which should be owned externally.
Examine privileged access, operational tooling and the security controls behind a managed service.
See the evidence that makes service performance, action and customer experience visible.
Move from backup completion to credible recovery and continuity evidence.
Understand how an external partner can extend an internal IT team's capability.
Before evaluating proposals, agree the essential requirements, desirable capabilities, evidence required and commercial assumptions. For each provider, classify answers as demonstrated, documented, verbal only or unclear.
Retain the evidence, proposal clarifications, pricing assumptions, scope statements and exclusions. An impressive demonstration still needs to match the service description and commercial terms you eventually sign.
If you are running a formal tender, use our guide to creating an IT tender document to turn these questions into requirements, responsibilities and an evaluation framework.
We will show you how our support, security, governance, transparency, proactive management and technical consultancy work in practice. At around 60 people, Wavex is large enough to provide specialist teams, operational resilience and 24x7 capability, while remaining small enough for clients to have meaningful access to senior technical and company leadership.