Managed IT Still Works Like It’s 2005

Before the industry replaces every engineer with an AI copilot, it might be worth fixing the fact that many organisations still onboard users through ticket queues operating at roughly the speed of the postal service.

There is a strange contradiction in modern IT.

Almost every SaaS platform on the planet has figured out self-service.

Need to add a user?
You do it yourself.

Need to assign a license?
A couple of clicks.

Need visibility of what you are paying for and who is consuming it?
That is normally built in.

Yet in managed IT, especially in MSP environments, many organisations still operate through ticket queues, privileged admins, and opaque operational processes that have barely evolved in years.

New starter? Raise a ticket.
Access change? Raise a ticket.
Remove a leaver? Raise a ticket.
Need it urgently? Good luck.

And while this sounds mildly inconvenient on paper, in high-change organisations it becomes a genuine operational problem.

The Organisations That Feel This Most

Some environments barely change.

Others never stop changing.

Hospitals.
Retail.
Aged care.
Staffing agencies.
Distribution companies.
Large legal projects.
Hospitality.

These businesses constantly onboard, move, and offboard users.

People change sites.
Temporary staff arrive.
Seasonal workers start.
Departments shift.
Projects ramp up and down quickly.

In these environments, onboarding delays are not “minor IT issues”. They directly affect operations.

One provider we worked with supported a large aged care organisation where onboarding new staff could take up to a week. Not because the IT team was incompetent — they were overloaded, operating through tickets, approvals, and manual provisioning processes.

The result was predictable:

users waiting for accounts
incorrect access
repeated support tickets
frustration from payroll and operations teams
security concerns around leavers

Eventually they implemented controlled operational workflows that allowed payroll to safely manage onboarding and offboarding directly, without needing privileged IT access or service desk involvement.

Users were added and removed at the correct time.
Provisioning became consistent.
Security improved.
And onboarding went from days to minutes.

Most importantly: Nobody needed to wait for a privileged infrastructure engineer to become available before a nurse could start work.

Which, surprisingly, turns out to be quite useful in healthcare.

The Hidden Cost Of Ticket-Driven Operations

Many MSPs have normalised ticket-driven onboarding simply because that is how managed IT has always worked.

A request arrives:

“Please create a new user called Fred and make him like Bob.”

That request then:

sits in a queue
gets triaged
eventually reaches someone with admin rights
gets manually processed
sometimes incorrectly

Meanwhile Fred is sitting there waiting to work while Bob explains that yes, Fred definitely started yesterday.

The customer becomes frustrated.
The service desk becomes overloaded.
The admin engineer becomes bored.
And eventually someone types the surname incorrectly, assigns the wrong group membership, or forgets a mailbox permission — generating another round of tickets.

The truly impressive environments manage to achieve multiple mistakes while still technically closing the original request successfully.

This is not rare.
This is normal.

And that is the problem.

Why MSPs Haven’t Solved This Already

To be fair to MSPs: this problem is genuinely difficult.

Technology vendors often present a world of perfectly standardised cloud environments where every customer:

uses the same architecture
follows the same operational processes
migrated successfully years ago
and apparently lives inside a Microsoft PowerPoint diagram

Reality is rather less fluffy.

Real customers have:

old applications
inherited systems
hybrid identity
strange line-of-business software
business-critical servers nobody wants to touch
operational exceptions
historical compromises
regulatory constraints
acquisitions
weird integrations
and at least one system held together by hope and a scheduled task

Every MSP knows this.

Even the best providers struggle to fully standardise customer environments over time because every customer deal introduces compromise.

Greenfield architecture is easy.
Existing customer reality is not.

And once an MSP reaches meaningful scale, the idea of implementing a new operational model often appears:

expensive
disruptive
operationally risky
and initially just “another cost”

Especially when existing ticket processes technically still function

Mostly.

The Dangerous Shortcut

To improve responsiveness, many organisations eventually delegate admin access to frontline staff.

This solves one problem while creating several others.

Now the service desk can move quickly — but also has access to systems and tools they probably should not.

This increases:

operational risk
accidental damage
security exposure
inconsistency
audit concerns

Every MSP has stories about accidental clicks in admin consoles.

Usually the phrase:

“I only meant to…”

appears shortly before a very long afternoon/evening/night.

The problem is not delegation itself.

The problem is delegating raw infrastructure access because there is no controlled operational layer sitting above it.

SaaS Solved This Years Ago

The interesting thing is that most modern SaaS businesses already solved this operational model years ago.

Customers expect:

visibility
self-service
auditability
role-based access
delegated administration
operational responsiveness

Nobody raises a support ticket to add a user to Slack and waits three days for an infrastructure engineer.

Yet many managed IT environments still behave exactly this way.

Customers often buy managed services as a black box:

they cannot see what they consume
they cannot safely enact changes
they cannot easily onboard users
they do not know what licenses are assigned
and every operational request disappears into ticketing systems and escalation queues

That operational model increasingly feels outdated.

The MSP Opportunity

This is where differentiation starts to emerge.

Most MSPs sell similar technology stacks:

Microsoft 365
security tooling
cloud services
endpoint management
support contracts

But customers increasingly experience MSPs through:

onboarding responsiveness
operational visibility
speed of change
consistency
accuracy
ease of interaction

The MSPs solving this well create meaningful advantages:

onboarding in minutes instead of days
reduced support volume
fewer operational mistakes
safer delegation
lower attack surface
more accurate billing
improved customer trust

One MSP reduced support cases by around 20–25% simply by removing repetitive provisioning and access requests from the ticket queue.

Another organisation running large-scale legal research projects implemented operational workflows that allowed users to be onboarded and offboarded in bulk without manual ticket handling, while maintaining accurate Citrix access, auditability, and billing visibility throughout the project lifecycle.

Operational visibility matters here too.

When providers can accurately track:

assigned services
operational changes
user entitlements
licensing consumption
who approved changes
and who enacted them

they reduce:

revenue leakage
over-licensing
billing disputes
operational confusion

That is not just operational efficiency.

That is commercial advantage.

The Real Future Of Managed IT

The future is probably not fully automated, perfectly standardised cloud-only infrastructure.

At least not anytime soon.

Real businesses are messy.
Customer environments evolve slowly.
Legacy systems persist because many still work perfectly well for the business.

And honestly, replacing stable systems simply because a cloud vendor prefers a different architecture is not always rational.

The future is more likely:

controlled operational workflows
delegated administration
operational visibility
safer self-service
auditability
consistent execution across inconsistent environments

Not removing providers from the process.

But giving providers better operational systems for managing real-world customer environments at scale.

Because despite what the cloud diagrams suggest, the world is still held together by onboarding requests, inherited infrastructure, and someone urgently asking for Fred’s login before the morning shift starts.

Frequently Asked Questions

Why do MSP onboarding delays happen?

Many MSPs still rely on ticket-driven operational processes that require privileged administrators to manually provision users, assign access, and enact changes across customer environments. In high-change organisations this often creates delays, mistakes, and operational bottlenecks.

Why are hybrid customer environments difficult to standardise?

Real-world customer environments evolve over time and often contain inherited systems, legacy applications, customer-specific requirements, hybrid identity models, and operational exceptions. This makes complete standardisation difficult, even for highly capable MSPs.

What is controlled self-service in managed IT?

Controlled self-service allows approved operational teams or customer administrators to safely perform common tasks such as onboarding users, assigning services, or managing access without requiring direct administrative access to underlying infrastructure.

Why is delegated administration risky?

Many organisations improve responsiveness by giving broad administrative access to frontline staff. While this speeds up operations, it can increase security exposure, accidental changes, inconsistency, and audit concerns if not managed through controlled operational workflows.

How can MSPs reduce onboarding friction?

MSPs can reduce onboarding friction by implementing controlled operational workflows, improving operational visibility, reducing dependency on privileged administrators, and enabling safe delegated administration for common operational tasks.