Managed Infrastructure
A maintained dependency map, patching with evidence it ran, capacity against an evidenced peak, and a backup that has actually been restored.
| How it is bought | Monthly recurring |
| Duration | 12-month term, 30 days notice after month 3 |
| Written for | Organisations running physical or virtual estates without a dedicated platform team |
Infrastructure gets attention when it fails and funding shortly after. In between it drifts: patches slip, capacity is guessed at, and nobody can say with confidence what runs where.
What you receive
Named artifacts, not activities. If one of these is not delivered, the engagement is not complete.
- A maintained dependency map, so a change is a controlled change rather than an outage with a conference bridge
- Patching and firmware management against an agreed window, with evidence it ran
- Capacity monitoring against an evidenced peak rather than a feared one
- Backup verification: a restore actually tested, not a job that reported success
- A monthly report stating what changed, what is at risk, and what we recommend next
How it runs
- Month 1 is discovery: inventory, dependency mapping, access, runbooks and a baseline. Steady state from month 2.
- Monthly review with the same engineer, and a quarterly capacity and lifecycle look-ahead.
What this deliberately does not include
Published with the same prominence as the deliverables. A scope with no stated exclusions is a scope that will be argued about later, and the argument always happens at the worst possible moment.
- Application support and application-level troubleshooting.
- Hardware procurement and vendor warranty claims, though we will tell you what to buy.
- Anything outside the agreed estate, which is listed by name in the order.
How you know it is finished
You can answer what runs where, when it was last patched, and when the backup was last restored, from a report rather than from a person's memory.
What you need ready
An inventory if one exists, appropriately scoped access, and a named person on your side.
Every engagement starts with a written scope confirmation before any invoice is raised. Nothing here is a click-to-buy: we confirm what you need, agree the scope in writing, then invoice. If the scoping conversation shows that a smaller engagement, or none at all, is the right answer, we say so before anything is signed.
Request this engagement Talk it through first Size it against an evidenced peak first
We use privacy-friendly analytics by default. Optional analytics cookies load only if you accept.