SECTION OVERVIEW
Where you would rather not build the capability in-house
Some organisations want the capability in-house. Others would rather it simply worked, and would like one number to call when it doesn’t. Managed services is for the second kind.
We carry the infrastructure and the security around it against a scope agreed in writing: what is covered, what is monitored, how quickly we respond, and what is explicitly out of scope. There is no ambiguity about who owns a problem at two in the morning.
In security, that most often means continuous testing rather than an annual snapshot. Every feature, integration and third-party library you ship is a new path in, and a point-in-time review goes stale the moment the next deploy lands. A retainer tests the same scope continuously, so the gap between shipping and knowing closes from a year to a cycle.
On the infrastructure side it means the unglamorous work that decides whether a system is still running in three years: patching, backups that are actually restorable, certificate and domain renewals, log rotation, capacity, and the runbooks that let the right thing happen when the person who knows is on leave.
Everything is built on open systems and documented as we go. That is deliberate. It means the arrangement is reversible — if you later bring the work in-house, you receive the configuration and the documentation needed to run it yourselves, rather than a dependency you have to buy your way out of.
A named engineer is accountable for your environment. Reporting cadence is set at the outset, and you can read what we did and why.
CASE STUDY
Eleven schools, one managed estate.
A school network run as one environment
In July 2021 we signed a five-year contract with the PAREF school network. Eleven campuses, each with its own staff, its own timetable and its own expectations from parents — and, before the engagement, largely its own way of doing things.
Managed services here covers both halves of the problem: the infrastructure the schools actually run on, and the security around it. Treating eleven campuses as one estate rather than eleven separate problems is what makes that affordable. A fix is designed once and applied across the network; a standard is set once and holds everywhere; a change is tested somewhere safe before it reaches a campus on a Monday morning.
The managed scope is the layer everything else depends on: the servers the schools run on, their cloud infrastructure, and the security of those servers and the networks connecting them. Not the applications a teacher opens — the platform underneath them, kept patched, monitored, backed up and defended.
The measure of this kind of work is that there is nothing to report. Five years in, the schools are running, the standards are consistent across all eleven, and no campus is dependent on whoever happened to set it up.
Described at service level. Operational detail is not published.