IT Runbook
A written, plain‑English runbook for your business systems — how they work, who owns what, and the exact steps to take when something breaks. It turns tribal knowledge into something anyone on the team can act on.
The runbook your team actually uses
I interview your team, map the systems, and write it all down in language a new hire or an on‑call engineer can follow at 2am. You keep every document — no lock‑in.
This is the right tier when your main pain is knowledge: things work, but only one person really knows why, and that's a risk.
- Systems inventory & architecture map
- Ownership, access, and vendor directory
- "When X breaks, do this" failure playbooks
- Documented logins/locations (secure)
- Plain‑English summary for leadership
- Knowledge‑transfer session for your team
Clear process, no surprises
Intro call
20 minutes. Tell me what your systems are and where knowledge lives.
Scoped quote
A written quote and plan, before any work begins.
Document
I interview your team and map the systems into a runbook.
Hand off
You get the docs plus a transfer session so the team owns it.
Is a runbook the right call?
A great fit if…
- IT knowledge lives in one or two people's heads
- Key‑person risk keeps you up at night
- Contractors come and go and take knowledge with them
- You want documentation, not ongoing monitoring
Look elsewhere if…
- You need ongoing security oversight → Fractional CISO
- You want a security posture review too → Runbook + Assessment
- It's just a single device or one quick fix
Runbook questions
Not sure which tier fits?
Ready to get your systems documented?
Book a free intro call — I'll tell you honestly whether a runbook is what you need.
Book a free intro call →