MSP value model
Why IT companies are moving
to Managed Services?

What is an MSP?

A Managed Service Provider is an IT company that manages a client's infrastructure for a fixed monthly fee (subscription) rather than per project or per billable hour. This is a fundamental shift in the business contract: instead of being a solution vendor, the MSP becomes the client's IT partner.

Key differences between models

The difference in margin is not accidental. The break-fix model comes with high workload variability and time spent on unplanned incidents. MSP smooths that variability with 24/7 monitoring and proactivity.

Anatomy of a profitable MSP

A profitable MSP does not sell "IT". It sells three service tiers, each with clearly defined value for the client and margin for the MSP.

Tier 1: Foundation

• 24/7 monitoring (Remote Monitoring & Management, RMM)
• Patch management (Windows + 3rd party applications)
• Backup (monitoring): verifying that backups actually run, not the storage itself
• Help desk Level 1 (tickets answered within 15 minutes)
• Monthly report (uptime, incidents, threat trends)

Client value: system stability, no unexpected outages, fast threat detection.

MSP margin: relatively high - tool costs (RMM) are fixed, and monitoring is largely automated.

Tier 2: Standard

• Everything in Tier 1
• Active Directory management (user provisioning, password policies, security groups)
• Security (central antivirus, security-event monitoring, alerts on suspicious activity)
• Help desk Level 1 + Level 2 (tiering, most tickets resolved within SLA)
• Virtual CIO (one strategic meeting per month, infrastructure review)
• SLA: 4h response on a P1 incident (with penalty for breach)

Client value: compliance (GDPR, NIS2), identity management, proactive security, access to an expert.

MSP margin: high - security and AD require a specialist but are low-ticket (more annual review, fewer ongoing fixes).

Tier 3: Premium

• Everything in Tier 2
• Digital transformation project management (IT roadmap, migration planning, change management)
• Compliance management (NIS2, ISO 27001, GDPR audits, board reporting)
• Dedicated engineer (one person responsible for the client)
• SLA: 2h response, 24/7 on-call
• Quarterly business reviews (board report, IT KPIs, recommendations)

Client value: investment in digital transformation, risk reduction, access to a person who understands the client's business context.

MSP margin: high - a dedicated engineer works more efficiently than ad-hoc consultants, and compliance leans on repeatable processes.

Why do clients pay for an MSP?

Five reasons why a client chooses an MSP instead of hiring an in-house IT person:

1. Predictable IT cost

Instead of "a sudden 50k PLN for a server outage", a steady budget. CFOs like predictability. With an MSP, no more shock invoices.

2. Proactive instead of reactive

An MSP fixes things before they break: alerts, patches, monitoring. Break-fix waits until the system goes down. For the client this means saving employee time and avoiding downtime.

3. Expertise without headcount

Three specialists (network, security, cloud) for the cost of one full-time hire. IT companies are short of staff. The MSP is talent outsourcing.

4. Compliance "by default"

The MSP "watches over" NIS2, GDPR and security policies. For the financial sector, manufacturing or retail this is not a luxury - it is a sine qua non.

5. Scalability without growing pains

A new branch in another city? The MSP scales infrastructure in days, not months. An in-house IT hire means budget, HR, onboarding.

How to build an MSP offering? Mistakes and lessons

Mistakes that repeat at every integrator moving from projects to subscription. Lessons from practice.

Mistake #1: Too broad an offering at the start

"Let's do everything for everyone" → team burnout, low margin, churn. When an MSP serves both startups and manufacturing, both Tier 1 and Tier 3, quality drops overnight.

Lesson: pick one segment (e.g. manufacturing companies with 50-200 employees) and a Tier 1+2 offering. Stay a specialist in that segment. Tier 3 will appear naturally once you understand the industry's needs.

Mistake #2: Pricing set too low

"We will be cheaper than the competition" → a price set below real cost. Outcome: the client values proactivity less, and the MSP runs out of budget for a proper help desk.

Lesson: price from your own costs (tools + L1/L2 help desk cost), not from "what the client will pay". As ticket volumes rise, service costs rise too - especially Level 2 - so price must reflect that.

Mistake #3: No tooling for scale

You can handle a dozen clients with simple ticketing and Excel. Beyond that it breaks down - tickets reviewed ad hoc, monthly reports built on the weekend, SLA tracked from memory.

Lesson: ManageEngine SDP multi-tenant from day one - built-in ticketing, SLA, reporting and integrations. Details on architecture and scaling are in our scenario-based piece ITSM for MSPs: multi-tenant help desk.

Mistake #4: No SLA in the contract

"We fix it as soon as we can" → the client is always unhappy. They think "3 hours", you think "within 24h". No contract, no truth.

Lesson: SLAs with contractual penalties (e.g. a monthly discount for breaching the agreed response time). It changes the whole team's behavior: instead of "today, on Slack", tickets go into a queue and are resolved in order. SLA monitoring in SDP gives hard data on how well you actually meet commitments - a sales argument in itself.

Mistake #5: Forgetting about churn rate

An MSP is built on recurring revenue. If 20% of clients leave per year, the model does not scale - you do not recover acquisition cost. Churn is driven either by poor service (no SLA) or by trying to expand without understanding client needs.

Lesson: Quarterly business reviews (even 30-minute ones) are the minimum required cost of retaining a client. They show value: "A year ago you had 12h of outage per year, now 0.3h. Value: 6 x annual revenue from your business." That is the argument that takes the conversation off price.

Tooling for a profitable MSP

No MSP gets built without the right stack. Below is the minimum required for an MSP serving 20-200 clients:

Tool cost is usually billed per endpoint and requires a quote from the vendor - most do not publish a full, public price list.

How to price the service for the client

An MSP service price should start from your own costs: tool cost per endpoint plus help desk labor cost (L1, plus L2 at higher tiers). Add overhead (HR, office, insurance) and your target profit. The client price has to cover all of that with margin - so calculate it for your own cost structure rather than using off-the-shelf rates. If you are evaluating ManageEngine SDP for a smaller company, also see ManageEngine for a 10-100 person company, with TCO calculation and edition comparison.

MSP metrics: what to measure?

You cannot manage what you do not measure. Below are the KPIs of a profitable MSP:

1. MRR (Monthly Recurring Revenue)

The foundation of the MSP business. Growing MRR means growing company value (at stable margins). Track MRR monthly and annually (12-month rolling MRR).

2. Churn rate

What percentage of clients leave per year? Target: < 5%. Above 10% means something is seriously wrong with the service or communication.

3. NPS (Net Promoter Score)

"Would you recommend us to a friend?" Profitable MSPs have NPS 50+. Below 30 means a retention problem.

4. MTTR (Mean Time To Resolve)

Average incident resolution time. Targets: P1 < 2h, P2 < 8h, P3 < 24h. This directly drives SLA compliance.

5. Revenue per endpoint

How much do you earn per device per month? For Tier 2, roughly 100 PLN. It shows the profitability of your client mix (large clients get bigger discounts).

6. Ticket volume per endpoint

Tickets per endpoint per year. For a diversified MSP that is about 2-4 tickets/endpoint/year. If it is 10+, you have either misconfigurations at the client or a chronic infrastructure issue.

The future of MSPs in Poland 2026-2030

Where is the MSP industry heading?

Market dynamics

• The managed services market is growing - it is one of the more dynamic segments of the IT market. Exact growth rates depend on methodology and data source.
• Main growth drivers: regulation (incl. NIS2) and the shortage of IT specialists on the labor market. Many companies, especially in smaller towns, cannot afford an in-house IT specialist, so they reach for an MSP.

Opportunities 2026-2027

• Manufacturing companies and SMEs (50-500 employees), most without an internal IT team. This is the main target. Niche segments (paint shops, factories, logistics) have very specific needs that only local integrators understand.
• MSP + specialization = high margin. "MSP for healthcare" or "MSP for retail" lets you set higher prices (because you understand the regulations).
• Expansion revenue: earn not only on Tier 1, but on extending services (digital transformation, security, compliance). Expanding scope at an existing client can meaningfully increase revenue from them, especially in Tier 3.

Risks 2027-2030

• Commoditization (price wars). Large MSPs (Softserve, DXC) will start to compete aggressively on price. Response: specialization and expansion revenue.
• The IT generation is ageing. IT specialists are retiring → fewer people on the market → higher wages in MSPs. Margins will drop unless we raise client prices.
• AI is changing IT support. Chatbots and automation take over part of the repetitive tickets - the L1 help desk role is shifting toward managing and supervising AI solutions. This process is already under way.