The context
Organisations across the Kingdom are outsourcing IT operations at an accelerating rate, and the reason is consistent: the specialist roles required to run a modern environment cannot be filled fast enough, and the ones that are filled concentrate too much knowledge in too few people. The decision to move to a managed model is usually framed as cost. It is more often about risk.
A professional services firm of around six hundred staff had an internal IT team of five. Four spent almost all their time on end-user support and routine maintenance. The fifth was the only person with infrastructure knowledge, and had been for eleven years.
Leadership described the problem as capacity. It was concentration. Every non-routine decision, every escalation and every project depended on one individual, whose annual leave functioned as an organisational risk event.
The approach
ITBuilders scoped the engagement by separating the work rather than the people. Routine, high-volume and after-hours operations moved to a managed model: monitoring, patch cycles, backup verification, first and second-line support, and standard change execution against defined templates. Anything requiring knowledge of the firm's business — application ownership, vendor relationships, internal project priorities — stayed internal, because that knowledge is not transferable and should not be.
Transition ran over a defined period with deliberate overlap. Documentation was produced during handover rather than requested beforehand, since environments of this age are documented by the people running them and by nobody else. Runbooks were written by working through actual incidents alongside the internal team, then validated by having someone unfamiliar with the environment execute them.
Service levels were defined against business impact rather than ticket category, which changed prioritisation in practice. A partner unable to access a matter file before a filing deadline and a partner with a slow laptop had previously carried the same priority. They no longer do.
Backup verification moved from a reported status to a tested restore on a fixed schedule. The first cycle found two systems whose backups had been completing successfully and were not recoverable. Both had reported green for over a year.
What changed
The internal team now runs the firm's IT strategy, application roadmap and vendor management. Routine operations run to a defined standard with documented coverage outside business hours. The eleven-year dependency remains a valued employee and is no longer a single point of failure.
Continuity of operation
The arrangement is delivered by ITBuilders engineers in the Kingdom, in the firm's own working hours, with named accountability for each service line. What makes a managed model work over years rather than months is that the provider retains the people who learned the environment during transition. An outsourcing relationship that rotates unfamiliar engineers through a client estate recreates the knowledge problem it was bought to solve.
