Who looks after this once it is running?
What we build we can run. Monitoring, model and vendor changes, cost control, the monthly measurement page, and the next small improvement each month. You keep ownership of everything; we keep it working.
What it is
Automations decay. A model is deprecated, a vendor changes an interface, a cost creeps, a rule stops matching the business as it grew. Without an owner, the first sign is usually a customer. Managed operations gives the automation an owner, a monthly page, and a standing hour for the next small improvement.
The retainer is itemised so you can see what a month buys: monitoring and alerts, the model and vendor changes, cost review, the measurement page, one improvement, and a named person who answers. Nothing is bundled that you cannot see.
This is for you if
- Something we built, or something you built, is now load bearing
- You want a person to answer when it breaks
- You want it to get a little better every month rather than quietly worse
Not for you if
- You have an internal team that wants to own it; we will hand over and train them
- You want a help desk for general IT; that is your IT provider
- The automation is not yet proven; that is a pilot first
How it runs
- 1 · week 1
Take on
Inventory, access in your accounts, alerts set, baseline measures recorded, runbook agreed.
- 2 · monthly
Run
Monitoring, changes, cost review, the page, one improvement. Anything out of pattern is reported the same day.
- 3 · monthly
Report
One page: uptime, runs, cost, the measures, what changed, what is next.
- 4 · any time
Hand back
Runbook, credentials in your accounts, a final page. No exit fee.
In writing, before we start
Three sentences that hold on every engagement. They are the method, written as promises.
The measure, the budget cap and the point at which we stop are set in the written scope before anything is billed. Nothing moves the goalposts afterwards.
Everything we build runs in your accounts and is yours: code, configuration, documentation and measurements. We hand over; there is no dependency on us.
If the pilot does not hit the measure we agreed first, we keep working at no further cost until it does, or we stop and say so in writing. You will not be sold the next step by the first one.
A month, itemised
- Monitoring and alerts on every run
- Model and vendor changes applied and tested
- Cost review against the agreed cap
- The monthly measurement page
- One improvement, scoped with you
- A named person, replies within one business day
What you receive
- A named person responsible for the systems we run
- A monthly report you can put in front of a board
- Monitoring, cost control, and model and vendor changes handled
- One improvement a month, agreed with you
Questions
Can you run something another firm built?
Usually, after a take on review that says what state it is in and what it would cost to make it operable. Sometimes the honest answer is to rebuild the fragile part first.
What counts as an improvement?
Something small enough to finish in the month and useful enough to notice: a new rule, a better check, a report the team asked for.
What if we want to stop?
A month’s notice. Everything is already in your accounts; we hand over the runbook and the last page.
What is load bearing and unowned?
Name the automation or the workflow. The take on review says what state it is in before you commit to anything.
- 1A conversationFree · 15 to 30 minutes
- 2Your one thing, in writingFree · what, cost and saving
- 3You decideNo obligation
I would like AI to answer after hours calls and book the callback.