Stop hiring engineers to fix problems you could have prevented

For many Managed Service Providers (MSPs), growth follows a familiar pattern. The business wins more customers, the number of managed endpoints increases, support ticket volumes rise and eventually another engineer is recruited to help the service desk manage the workload.

It's a model that has supported the growth of the managed services industry for decades, but it creates a fundamental challenge for profitability. Under a fixed-fee managed services agreement, customers generally pay the same monthly amount regardless of how many support tickets they generate. Every recurring incident, unnecessary alert and preventable technical issue consumes engineering time without necessarily generating additional revenue.

As a result, an MSP can increase its monthly recurring revenue while making little progress on profitability, because service delivery costs keep growing alongside customer numbers.

The traditional response is to make the service desk more efficient: better ticket management, faster response times, more capable engineers or AI to accelerate ticket resolution. All of these can help, but they overlook a bigger opportunity.

What if your MSP could prevent a substantial proportion of those tickets from being created in the first place?

That's the role of a Centralised Services team. Rather than waiting for customers to experience problems, Centralised Services focuses on proactive IT maintenance: keeping customer environments healthy, standardising technology, automating routine activities and proactively eliminating the underlying causes of support requests.

For MSPs serious about improving margins, operational maturity and scalability, building a dedicated Centralised Services capability can be one of the most valuable investments they make. This guide covers what the team does, how to structure it, the skills and tools it needs, and how to measure its financial impact.

What is a Centralised Services team in an MSP?

A Centralised Services team is responsible for the proactive management, maintenance, standardisation and automation of technology across an MSP's managed customer environments.

Unlike a traditional service desk, which mainly responds to incidents and service requests, Centralised Services focuses on keeping systems healthy and reducing the number of issues that need reactive support. Its responsibilities typically include:

• RMM administration
• Proactive endpoint and infrastructure maintenance
• Patch management and compliance
• Automated remediation and scripting
• Monitoring policy and alert optimisation
• Backup monitoring and exceptions
• Technology standardisation
• Configuration compliance
• Asset health and lifecycle monitoring
• Eliminating recurring incidents
• Proactive procedures and documentation
• Automation workflow development

The objective is a consistent, repeatable approach to maintaining customer environments, regardless of which engineer originally onboarded the customer or how the environment was configured. Take a device that keeps running low on disk space:

Similarly, instead of manually reviewing hundreds of patching exceptions every month, the team can set up automated reporting, remediation workflows and escalation procedures that focus engineering attention on the devices that actually need intervention.

Centralised Services changes the focus from resolving individual incidents to improving the overall health and efficiency of the managed environment.

Centralised Services vs Service Desk vs NOC: what's the difference?

A common misconception is that Centralised Services is just another name for a Network Operations Centre (NOC), or a team that monitors alerts. These functions can overlap, but their responsibilities and objectives are different.

A NOC typically detects and responds to operational events, while Centralised Services takes a broader role in stopping those events from becoming recurring problems. Here's the same alert through each lens:

These responsibilities can be combined, particularly in smaller MSPs. What matters is that proactive improvement has clearly defined ownership, rather than being something engineers attempt when the service desk is quiet.

Why every growing MSP needs a Centralised Services strategy

One of the biggest challenges facing MSPs is that reactive service delivery becomes increasingly expensive as the customer base grows.

Consider an MSP supporting 2,000 managed endpoints and generating 1,200 support tickets a month. If each ticket takes an average of 30 minutes of engineering time, the business needs 600 hours of engineering effort a month just to resolve them. Now imagine it eliminates 20% of that reactive workload through better maintenance, standardisation and automation:

That released capacity doesn't automatically become cash. But the MSP can use it to support more customers, reduce overtime, avoid future recruitment or move engineers onto higher-value work. (To see what each ticket costs you today, use our MSP cost per ticket guide.)

There's also a benefit that's frequently overlooked: customer experience. Customers don't necessarily care how quickly their IT provider resolves a recurring problem if the same problem keeps disrupting their business every week.

Preventing an issue altogether is a better outcome than repeatedly resolving it within SLA.

How to structure an MSP Centralised Services team

There's no universal structure that works for every MSP. The right approach depends on the number of managed endpoints, the complexity of customer environments, existing automation capability and the maturity of service delivery processes. But there are three practical models:

Model 1: one dedicated engineer

The important word is dedicated. If the engineer is regularly pulled back onto the service desk to resolve urgent tickets, proactive maintenance quickly becomes a secondary responsibility, and the MSP never develops the capability to reduce reactive workload.

A dedicated Centralised Services Engineer is someone whose primary job is to make the service desk progressively less busy.

Model 2: a small team

As the MSP grows, the function can expand into a small team with responsibilities divided across proactive maintenance and automation. An illustrative structure:

Model 3: a mature function

Larger MSPs may develop a specialised function covering endpoint management, infrastructure monitoring, patch and vulnerability remediation, automation, backup operations, technology standards and operational reporting.

Importantly, the team's growth should reflect actual workload and measurable outcomes rather than an arbitrary endpoint-to-engineer ratio. The most effective structure is the one that lets the MSP reduce the reactive engineering effort needed per managed user or endpoint over time.

Seven core responsibilities of an MSP Centralised Services team

Each responsibility removes reactive work from a different angle: owning the platform, preventing failures, cutting noise, automating fixes and measuring the result.

1. RMM platform ownership and optimisation Standardise
2. Proactive patch management Prevent
3. Monitoring and alert optimisation Reduce noise
4. Automated remediation Automate
5. Technology standardisation Standardise
6. Root cause analysis and problem management Prevent
7. Operational reporting and continuous improvement Measure

What skills does a Centralised Services Engineer need?

The ideal Centralised Services Engineer isn't necessarily the person who closes the most tickets. The role combines technical capability, analytical thinking, scripting knowledge and an interest in continuously improving operational processes, across multiple customer environments.

• RMM and endpoint management

  NinjaOne, Datto RMM, ConnectWise RMM, N-able and Microsoft Intune.

• Microsoft technologies

  Microsoft 365, Windows Server, Microsoft Entra ID, Active Directory and endpoint administration.

• Scripting and automation

  PowerShell first, with Python, API integration and automation platforms adding value.

• Networking and infrastructure

  DNS, DHCP, VPNs, network monitoring, server health and common dependencies.

• Security and patch management

  Endpoint security, patch deployment, vulnerability remediation and secure configuration standards.

• PSA and documentation

  HaloPSA, ConnectWise PSA, Autotask, IT Glue, Hudu or similar.

• Analysis and problem solving

  Spotting patterns, investigating root causes and building permanent fixes rather than repeatedly resolving individual incidents.

Perhaps most important of all is a continuous improvement mindset. The difference shows up in the question each engineer asks:

What tools does a Centralised Services team need?

A Centralised Services function doesn't necessarily need a new technology stack. In many cases, the opportunity is to make better use of the tools the MSP already owns.

Don't add platforms simply because they offer extra automation features. Understand what your current tools can do, identify the gaps, and invest in new technology only where there's a clear operational and financial benefit. (Choosing an automation platform? Compare Rewst vs Pia vs n8n.)

How to measure the success of your Centralised Services team

One of the biggest mistakes MSPs make is measuring Centralised Services with the same KPIs as the service desk: tickets resolved, response times and SLA performance. Centralised Services should be measured mainly on how well it improves the managed environment and reduces preventable engineering work.

• Tickets per managed user

  Reactive support demand relative to customer size

  Downward
• Repeat incident rate

  How often known technical problems recur

  Reduce
• Human-assisted ticket hours

  Engineering effort spent on reactive support

  Reduce
• Automated remediation success rate

  Share of eligible workflows completed successfully

  Improve
• Patch compliance

  Devices meeting approved patching standards

  Improve
• RMM policy compliance

  Endpoints aligned with monitoring and maintenance standards

  Improve
• Alert-to-ticket ratio

  Monitoring events that create engineer work

  Fewer tickets
• Cost per managed user

  Direct cost of delivering support per user

  Sustainably lower
• Service gross margin

  Profitability of managed service delivery

  Improve
• Customer satisfaction

  Quality of the customer support experience

  Maintain or improve

Assess these measures together. Removing unnecessary monitoring alerts may cut ticket volumes, but it only counts as success if critical issues are still identified and handled properly. Likewise, automating a task may reduce manual effort without eliminating the underlying incident. Both create value, but report them separately.

For benchmarks on the margin side, see what a good gross margin looks like for an MSP.

Calculating the ROI of a Centralised Services team

For MSP owners, the financial case should be built around the engineering effort the team eliminates and the capacity it creates. The calculator below is pre-filled with an MSP supporting 2,500 managed users and 1,500 tickets a month, where Centralised Services prevents 20% of support demand.

With $50,000 a year invested in dedicated Centralised Services capacity (employment or service costs plus the operating expenses attributable to it), the potential first-year net capacity value is $90,000 − $50,000 = $40,000, an illustrative capacity-value return of 80%.

The business case should also account for implementation effort, automation maintenance and any extra software or operating costs. Even so, the example shows why proactive engineering can create a measurable return that goes well beyond reducing the cost of individual tickets.

A 90-day plan to build your MSP Centralised Services team

You don't need a large department to start building proactive service delivery. A structured 90-day plan is a practical starting point.

The first 90 days aren't about automating everything or eliminating every reactive incident. They're about establishing a repeatable operating model that steadily reduces unnecessary work and improves the health of customer environments.

Five common mistakes MSPs make when building Centralised Services

1. Treating Centralised Services as overflow for the service desk

   When the service desk gets busy, it's tempting to pull the Centralised Services Engineer into reactive support. Occasional help may be necessary, but making it the norm defeats the purpose of the role and keeps the MSP stuck responding to problems instead of preventing them.

   Protect their proactive time
2. Measuring success by tickets closed

   An engineer who resolves 100 monitoring tickets may look productive, but one who permanently removes the causes of those 100 tickets may deliver far more value.

   Measure prevention, health and hours released
3. Automating poorly designed processes

   Automation should follow standardisation. If environments and procedures are inconsistent, automating them can add complexity and risk.

   Set standards before large-scale workflows
4. Failing to establish ownership

   RMM policies, scripts, monitoring configurations and automation workflows all need ongoing maintenance. Without a clear owner, they drift out of date as environments and platforms change.

   Name an owner for every policy and workflow
5. Ignoring the financial outcomes

   Not every activity has to produce an immediate saving. Better patch compliance, less security exposure and a stronger customer experience all matter. But leadership should be able to see how the investment supports a more efficient, scalable business.

   Report hours released and margin impact

When should an MSP hire its first Centralised Services Engineer?

There's no magic number of endpoints or employees. For some MSPs the opportunity becomes obvious when recurring incidents start consuming a meaningful share of service desk capacity. For others it becomes a priority when:

• RMM policies have become inconsistent across customers
• Automation isn't progressing because nobody has time to own it
• The business keeps adding engineers to handle growth
• The same incidents keep coming back to the service desk

A useful starting point is to calculate how many engineering hours preventable problems consume each month. If the capacity that proactive maintenance and automation could release is worth more than the cost of the function, there may be a compelling business case. The ROI calculator above shows the break-even reduction for your numbers.

The calculation should include more than immediate labour savings, though. Better reliability, stronger security, happier customers and the ability to support future growth can make proactive engineering worthwhile before direct savings appear.

For smaller MSPs, a single dedicated Centralised Services Engineer may be the right start. Larger businesses may need a team with specialist skills across endpoint management, automation and proactive infrastructure operations. Either way, establish accountability and protect the time needed to make meaningful improvements.

How Dijital Team helps MSPs build Centralised Services capability

At Dijital Team, we believe improving MSP profitability takes more than hiring additional engineers at a lower cost. The greatest opportunity often comes from changing how services are delivered, so the business gets more efficient as it grows.

Through our dedicated offshore staffing model, we help MSPs establish Centralised Services and automation capability without the full cost and complexity of recruiting more onshore technical staff.

Through our Better Business Pathway, we work with MSPs to improve operational maturity, strengthen margins and build more scalable businesses. Centralised Services is an important part of that journey, because it moves the business away from adding people to manage more work and towards removing unnecessary work in the first place. Read more about how a Centralised Services Engineer unlocks MSP growth.

Our objective isn't just to help MSPs employ more engineers. It's to help them build a better operating model.

The bottom line: build a team that makes your service desk less busy

For MSPs, growth shouldn't automatically mean hiring more service desk engineers. You'll always need more technical people as you grow, but the most scalable MSPs keep reducing the engineering effort it takes to support each customer.

A Centralised Services team creates that capability. Through proactive maintenance, standardisation, monitoring optimisation, root cause analysis and automation, MSPs can reduce recurring incidents, improve customer experience and release valuable engineering capacity.

The financial benefits can be substantial, but the real opportunity is broader: turning service delivery from a reactive function whose cost grows with revenue into a proactive operation that becomes more efficient as the business matures.

The best Centralised Services team isn't the one that closes the most tickets. It's the one that stops the most unnecessary work reaching the service desk.

Frequently asked questions