Managed IT Services: What Mid-Sized Businesses Really Get

Managed IT Services: What mid-sized businesses really gets

Short: Managed IT Services (MIS) are an operating model: Instead of building a separate IT department, an enterprise commissions an external service provider (MSP) with ongoing IT operation.

Managed IT Services (MIS) are an operating model: Instead of building a separate IT department, an enterprise commissions an external service provider (MSP) with ongoing IT operation.

The MSP assumes proactive responsibility for defined IT areas – against monthly flat fee instead of individual billing. Sounds simple, is more nuanced in practice.

This article explains what mid-sized businesses really need to get and look after.

What Managed IT Services typically include

Short: **Managed IT Services promise professional IT operations without their own IT department.

**Managed IT Services promise professional IT operations without their own IT department.

Core services (almost always included):

• Helpdesk and IT support (phone, remote, on-site)
• Endpoint Management: Patching, Updates, Configuration for PCs, Laptops, Mobiles
• Network Monitoring and Management (Router, Switches, Firewall)
• Backup management: setup, monitoring, recovery tests
• Antivirus and Endpoint Protection
• User and Rights Management (Active Directory, AAD)

Advanced services (often optional or as a package):

• Server administration (on-premise or cloud)
• Cloud Management (Azure, AWS, Microsoft 365)
• IT Security Monitoring (SIEM, MDR)
• Printer and peripheral management
• License management
• IT procurement and asset management
• Strategy and planning consulting

Mostly not included (case):

• Project work (introduce, migrate, implement)
• Hardware costs
• Software license costs
• On-site operations beyond the agreed quota

SLA: The heart of the contract

Short: A Service Level Agreement (SLA) defines the quality of the MSP and what happens if it does not comply.

A Service Level Agreement (SLA) defines the quality of the MSP and what happens if it does not comply. Main SLA parameters:

Reaction time: How fast does the MSP react to a request?

• Critical failure (P1): typical 1–4 hours
• Important fault (P2): 4–8 hours
• Normal request (P3): 1–2 working days

Solution time: Differences from reaction time! Reaction means "we take care of us". Solution means "the problem is fixed". Solution times vary greatly per complexity.

Service availability: 99 % vs. 99.9% availability – the difference is 8.7 hours vs. 52 minutes downtime per month.

Consequences of SLA violation: credits, termination rights. An SLA without consequences is a non-binding declaration of intent.

Price models and costs

Short: MSP price models vary, the most common approach:

MSP price models vary, the most common approach:

Per-Seat model: Fixed monthly fee per user or terminal. Advantage: Predictable costs, easy scaling.

Typical: €50–150 per user/month for basic MIS, €80–200 for more complete packages. .Module package model: Basic services + optional modules (security, cloud management, etc.). Flexible but more complex in billing.

Comparison of costs: A full-time IT employee costs the employer 60.000–90.000 € per year (full cost).

An MSP for 50 users costs 3,000–7,500 € per month (36,000–90,000 €/year) – but with a broader range of services, 24/7 options and without personal risks.

The comparison is not always in favor of the MSP – depends heavily on what is internally covered.

What medium-sized enterprises must pay attention to the contract

Short: **Description of performance: What is "Managed IT" exactly?

**Description of performance: What is "Managed IT" exactly? ** Each MSP has a different definition. What exactly is included? What costs extra? Project work, on-site deployments, hardware change – all clearly defined?

**Includes hours vs. billing after effort? ** Some MSPs offer "all inclusive", others have an hour contingent and expect to do so.

Those who do not know the quota are experiencing surprises in the monthly bill.

**Data storage location and GDPR. ** Where are monitoring data, backup data, support tickets stored? EU-DSGVO conformity and data processing agreement (DV contract) under Art. 28 GDPR are mandatory.

**Determination and Exit Strategy. ** 12 months notice period is usual in the industry, but capable of negotiation. More important: What happens when changing?

How do I get back documentation, access data, admin rights?

**Escalation path. ** What happens if support quality is systematically bad? Is an escalation contact defined? Is there a contact person who takes responsibility or is it always in the ticket system?

MSP and individual software development

Short: Many MSPs focus on IT operations – hardware, software license management, infrastructure.

Many MSPs focus on IT operations – hardware, software license management, infrastructure. What they often do not afford: development and support for individual software solutions. Here it needs a second partner for software maintenance and care of its own applications.

The cooperation between MSP (infrastructure) and software development partner (applications) must be clearly regulated: who has what access rights, who is responsible for production problems, how is knowledge transferred?

Conclusion

Short: Managed IT Services can bring significant benefits to medium-sized companies without strong internal IT department: planned costs, broad expertise, proactive operation.

Managed IT Services can bring significant benefits to medium-sized companies without strong internal IT department: planned costs, broad expertise, proactive operation. Quality varies greatly between providers. A durable SLA, clear performance description and a well-thought-out exit strategy are not small things, but decisive for long-term success. .Our team at Groenewold IT Solutions not only supports the development of software, but also the operation of individual applications and the strategic IT planning – as a reliable partner for German mid-sized businesses.

Frequently Asked Questions (FAQ)

What is the difference between MSP and classic IT support?

Classic IT support responds to problems (break-fix). MSP acts proactively: monitoring, patching, prevention. MSP is an operating contract, not individual invoices.

Can I combine MSP and own IT staff?

Yes, very often. Typically: A separate IT generalist for internal responsibility and specific corporate knowledge, MSP for the broader operating tasks (monitoring, helpdesk, security). Clear roll separation is decisive.

How do I change from one MSP to another?

Knowledge transfer is critical: documentation, admin access data, asset lists, configurations.

If you conclude a contract, make written notice that these documents belong to you and will be handed over completely upon termination.

What happens if the MSP fails or becomes insolvent?

Dependence on the MSP is a real risk.

Reduction: Keep all access data and documentation locally (not only at the MSP), regularly test whether your own access is still working, and in an emergency plan clarify how to bridge.

What do I know if the scope is too big?

If more than three independent target groups or delivery items are same time “Must-have”, most of the time prioritization is missing.

For Managed IT Services: What mid-sized businesses really gets helps a clear pilot with a measurable result.

How do I avoid technical dead ends?

Short: With ** early architecture reviews**, prototype critical uncertainties and repeatable deployments.

With ** early architecture reviews**, prototype critical uncertainties and repeatable deployments. At medium level, a clean interface strategy pays off.

What role does maintenance play after the launch?

Short: A sustainable solution needs Patch cycles , monitoring and ownership.

A sustainable solution needs Patch cycles, monitoring and ownership. Plan budget for further development – not only for the first release.

Additional notes

Specialization: Requirements and Stakeholders

Projects around managed rarely fail due to missing features – more often on unclear decision paths and changing priorities.

Document assumptions explicitly (what we know, what we guess) and link them to review appointments.

gets

and ** services** should not only be addressed “sometimes”: specify measurable intermediate results that show whether the chosen direction is wearing.

This increases internal acceptance and makes external communication more credible – for example towards management, supervisory board or public bodies.

Frequent questions (FAQ)

Conclusion and next steps

Short: Managed IT Services: What mid-sized businesses really gets can be successfully implemented when technology, organization and measurability match – instead of isolated tool rollouts without process reference.

Managed IT Services: What mid-sized businesses really gets can be successfully implemented when technology, organization and measurability match – instead of isolated tool rollouts without process reference.

Use the overview in this article as a basis for discussion on priorities, risks and the first loadable pilot.

Intensify matching topics in category overview Blog category and check operational support via software development, IT consulting. Groenewold IT accompanies analysis, implementation and operation – from the first classification to scalable releases.

Technical sources and further links

Short: The following independent references complement the classification on the topics of this Article:

The following independent references complement the classification on the topics of this Article:

• Bitkom – Digital Economy Association
• BSI – Federal Office for Information Security
• European Commission – Digital Strategy
• MDN Web Docs (Mozilla)
• W3C – World Wide Web Consortium

"Mobile apps need not only UX but also clear offline and security concepts; otherwise, trust and acceptance in the area suffers."

— *Björn Groenewold, Managing Director, Groenewold IT Solutions *