Sample deliverable
What “documented, you own it” looks like.
Every build ships with a runbook and a recorded walkthrough, so the system is yours to run and hand off. Below is an illustrative template - not real client work - to show the shape of it.
Five sections, plain language.
- 01
What this system does
One paragraph in plain language: the trigger, the steps, and what lands where. Written so a new operator understands it in a minute, not an afternoon.
- 02
Day-to-day operation
What runs on its own, what needs a human, and where to look to confirm it worked. No jargon, no assumed context.
- 03
When something looks off
The handful of things that can go wrong, how each one shows up, and the first thing to check. Plus who to contact and what to send them.
- 04
Access and ownership
Which accounts the system lives in, who holds the keys, and how to rotate them. You own all of it - nothing is locked to me.
- 05
Changing it later
Where the editable settings live (templates, thresholds, routing rules) and how to change them safely without booking an engineer.
A recorded tour of the system.
The walkthrough records me operating the system end to end: where to click, what good looks like, and what to do when it is not. New operators get up to speed in minutes.
Send the workflow that is costing you.
One business day for a written audit. Every build ships with a runbook and walkthrough like the one above, in your accounts.