Runbook automation for recurring jobs
Every recurring job lives in one person's head, and each new hire costs hours of explaining it again. Runbook automation, every job written as steps, lets anyone pick it up.
One build, quoted after a 30 minute call. Live in four to six weeks.
- 194 systems live
- 0 data lost
- $0 systems cost
On this page
The work this takes off your week
By hand, each job is taught again every time someone new takes it on.
- A new hire shadows a colleague for days to learn the monthly close.
- The job changes, nobody writes it down, and two people end up doing it two ways.
- When the one person who knows is away, the job waits.
With the system, every job has steps anyone can follow.
- Each recurring job is set out as numbered steps, with what goes in and what to check.
- When a job changes, its steps change with it.
- A new hire, or an AI assistant, follows the steps from day one with no walkthrough.
What it would cost you to keep doing it by hand
Example
Three places the hours go when every recurring job is explained by hand.
| # | Situation | What it takes by hand | Hours a month | Cost a month |
|---|---|---|---|---|
| 1 | A new hire learns the recurring jobs | Days of shadowing and the same questions answered again | 14 hours | $2,100 |
| 2 | The one person who knows a job is away | The job waits, or someone rebuilds the steps from old emails | 5 hours | $750 |
| 3 | Two people do the same job two ways | Mistakes traced and fixed, then the right way explained again | 4 hours | $600 |
Together: 23 hours and $3,450, every month.
Example with illustrative figures, priced at $150 an hour.
What runbook automation gets you
-
Written steps for every recurring job.
Each job has numbered steps with what goes in and what to check. Anyone can pick it up.
-
New hires useful sooner.
A new hire or an AI assistant follows the steps on day one, and nobody explains the job twice.
-
Steps that keep up with the job.
When a job changes, its steps change with it. Nobody works from an old version.
How it runs
-
A 30 minute call.
We look at the jobs your team repeats, then quote one price for the build. -
Access and a walkthrough.
You show us how each job runs today, then approve the plan. -
Written and tested in draft.
Every set of steps is tested against the real job before it goes live. -
Live, and kept current.
The steps go live once you approve them, and every change to a job updates them.
Live in four to six weeks.
Proof from one services business
We built this system first for a national services business.
Fully automated operations
One owner runs a multi location services business on 194 systems and no office staff
A national multi location brand with 84 service contractors. Every recurring job, from a new hire to the monthly reports, runs as a system.
0
data lost across every change shipped live
17
automatic checks before any change goes live
$0
systems and architecture cost
- A new hire fills in their profile and their page is on Google. Nobody touches it.
- Mark someone as left and every page that mentioned them updates that night.
Anonymized under NDA. The numbers are real.
What moves the price
Jobs.
How many recurring jobs need written steps.
Know how.
Whether it sits with one person or across the team.
Readers.
Steps for people, for an AI assistant, or both.
What exists.
Checklists, notes or training videos to start from.
One price for the build, quoted after the call.
Operations
Every recurring job, written so anyone can do it.
One 30 minute call about the jobs your team repeats. One price for the build, and you decide after the call.
Prefer to write? Send us a message.
Runbook automation questions
Is runbook automation worth it for a small team?
It is if a few people hold jobs nobody else can do, or new hires take weeks to get going. With two people who never swap roles, a shared document still costs less.
What do you need from us?
A 30 minute call, then a short walkthrough of the jobs your team repeats. We watch how each job gets done today and write the steps from that.
What if nobody has written anything down?
That is where most teams start. We learn each job from the people who do it and write the steps for you to check.
Who keeps the steps current?
The system does. Your team sees the new version the next time they do the job.
Can an AI assistant follow the steps too?
Yes. The steps are written plainly enough for a new hire or an AI assistant to follow without a walkthrough.