Runbook
Tasks tonight1,284
Process
From auditto autopilot.
The same plan every time: audit, map, build, launch, report. You know what each week needs from you before it starts.
- Fixed planAudit to autopilot
- Week 1The audit
- OngoingThe morning report
Process
From auditto autopilot.
The same plan every time: audit, map, build, launch, report. You know what each week needs from you before it starts.
- Fixed planAudit to autopilot
- Week 1The audit
- OngoingThe morning report
Process
From auditto autopilot.
The same plan every time: audit, map, build, launch, report. You know what each week needs from you before it starts.
- Fixed planAudit to autopilot
- Week 1The audit
- OngoingThe morning report
How it runs
From audit to autopilot.
Five steps from the first call to a business that runs itself. One person on your side, and a morning report from then on.
See the full process
01Week 1Step 01 / 05Audit
We sit with the people who do the work and list every task that repeats. Most teams find thirty; we pick the ten that cost the most hours.
02Week 2Step 02 / 05Map
Each workflow is drawn end to end: the trigger, the tools it touches, the person who signs off. You approve the map before anything is built.
03Weeks 3–4Step 03 / 05Build
We wire the workflows into your CRM, inbox, invoicing and helpdesk, with a test run on real records and a log you can read.
04Week 5Step 04 / 05Launch
Workflows go live one at a time, with a person watching each for its first week. Exceptions land in a queue, never in a void.
05OngoingStep 05 / 05Autopilot
Every morning a report on what ran, what paused and what it saved. We tune, add and retire workflows as the business moves.
How it runs
From audit to autopilot.
Five steps from the first call to a business that runs itself. One person on your side, and a morning report from then on.
See the full process- 01Week 1Step 01 / 05
Audit
We sit with the people who do the work and list every task that repeats. Most teams find thirty; we pick the ten that cost the most hours.
- 02Week 2Step 02 / 05
Map
Each workflow is drawn end to end: the trigger, the tools it touches, the person who signs off. You approve the map before anything is built.
- 03Weeks 3–4Step 03 / 05
Build
We wire the workflows into your CRM, inbox, invoicing and helpdesk, with a test run on real records and a log you can read.
- 04Week 5Step 04 / 05
Launch
Workflows go live one at a time, with a person watching each for its first week. Exceptions land in a queue, never in a void.
- 05OngoingStep 05 / 05
Autopilot
Every morning a report on what ran, what paused and what it saved. We tune, add and retire workflows as the business moves.
How it runs
From audit to autopilot.
Five steps from the first call to a business that runs itself. One person on your side, and a morning report from then on.
See the full process- 01Week 1Step 01 / 05
Audit
We sit with the people who do the work and list every task that repeats. Most teams find thirty; we pick the ten that cost the most hours.
- 02Week 2Step 02 / 05
Map
Each workflow is drawn end to end: the trigger, the tools it touches, the person who signs off. You approve the map before anything is built.
- 03Weeks 3–4Step 03 / 05
Build
We wire the workflows into your CRM, inbox, invoicing and helpdesk, with a test run on real records and a log you can read.
- 04Week 5Step 04 / 05
Launch
Workflows go live one at a time, with a person watching each for its first week. Exceptions land in a queue, never in a void.
- 05OngoingStep 05 / 05
Autopilot
Every morning a report on what ran, what paused and what it saved. We tune, add and retire workflows as the business moves.
Week by week
What each week needs from you.
Five weeks, and most of your part is saying yes on time. This is everything we will ask for, before we ask.
- Week 1Week 1Week 01 / 05
The audit
Two half-days with the people who do the work. We sit beside them, list every task that repeats and count the hours honestly. You do not prepare anything.
What we need from you
- Two half-days of your team's time
- A login to each tool, read-only
- One person who can say yes
- Week 2Week 2Week 02 / 05
The map
Every workflow drawn end to end on one board: the trigger, the tools it touches, who signs off, where it can fail. You read it, correct it, approve it.
What we need from you
- An hour to walk the map with us
- The exceptions you can think of
- Your approval, in writing
- Weeks 3–4Weeks 3–4Week 03 / 05
The build
We wire the workflows into your CRM, inbox, invoicing and helpdesk, run them on real records in a sandbox and keep a log you can read. You see each one before it goes live.
What we need from you
- Admin access to the tools we wire
- Twenty real records to test on
- A reply inside a day when we ask
- Week 5Week 5Week 04 / 05
The launch
Workflows go live one at a time, a person watching each for its first week. Exceptions land in a queue with a name on it; nothing lands in a void.
What we need from you
- A named owner for the exception queue
- Fifteen minutes a day for the first five days
- OngoingOngoingWeek 05 / 05
Autopilot
A report every morning on what ran, what paused and what it saved. We tune, add and retire workflows as the business moves. You read one page a day.
What we need from you
- One page a day, read
- A call a month, thirty minutes
The hand-over
What you hold when we step back.
At the end of week five everything runs in your accounts, with a name on every queue. Six things change hands, signed.
- 01 / 06
The map, as built
Every workflow drawn as it runs, not as it was planned, with its trigger, tools and owner.
- 02 / 06
Logins and ownership
Every scenario, token and connection sits in your accounts. We hold nothing you cannot switch off.
- 03 / 06
The exception queue
Where a paused run lands, who sees it and what they do. One page, pinned in your helpdesk.
- 04 / 06
The night log
A log every run writes to: clock, event, workflow, result. Readable by anyone on your team.
- 05 / 06
The morning report
Eight numbers on one page at 06:00, with the recipients you chose and the thresholds that wake someone.
- 06 / 06
A one-hour hand-over
Recorded, with the questions your team asked. Yours to keep and to replay for the next hire.
Nothing we build sits in our accounts. Switch us off and it keeps running.
17:30Hand-over signed
After launch
Three ways we stay on the line.
Every workflow is watched for its first week on the house. After that, pick how close we stay.
- 01
Watch
Response: Next morningThe log is read every morning and a paused run is fixed before the office opens.
- Morning report
- Exceptions fixed by 09:00
- A call a month
- 02
Tune
Response: Same dayChanges to a running workflow inside a working day, and a new small workflow a month.
- Everything in Watch
- Changes same day
- One new workflow a month
- A call a fortnight
- 03
Run
Response: Inside an hourThe night rota watches your queue around the clock and an engineer answers inside the hour.
- Everything in Tune
- Night rota on your queue
- Answer inside 60 minutes
- Quarterly re-audit
Week by week
What each week needs from you.
Five weeks, and most of your part is saying yes on time. This is everything we will ask for, before we ask.
- Week 1Week 1Week 01 / 05
The audit
Two half-days with the people who do the work. We sit beside them, list every task that repeats and count the hours honestly. You do not prepare anything.
What we need from you
- Two half-days of your team's time
- A login to each tool, read-only
- One person who can say yes
- Week 2Week 2Week 02 / 05
The map
Every workflow drawn end to end on one board: the trigger, the tools it touches, who signs off, where it can fail. You read it, correct it, approve it.
What we need from you
- An hour to walk the map with us
- The exceptions you can think of
- Your approval, in writing
- Weeks 3–4Weeks 3–4Week 03 / 05
The build
We wire the workflows into your CRM, inbox, invoicing and helpdesk, run them on real records in a sandbox and keep a log you can read. You see each one before it goes live.
What we need from you
- Admin access to the tools we wire
- Twenty real records to test on
- A reply inside a day when we ask
- Week 5Week 5Week 04 / 05
The launch
Workflows go live one at a time, a person watching each for its first week. Exceptions land in a queue with a name on it; nothing lands in a void.
What we need from you
- A named owner for the exception queue
- Fifteen minutes a day for the first five days
- OngoingOngoingWeek 05 / 05
Autopilot
A report every morning on what ran, what paused and what it saved. We tune, add and retire workflows as the business moves. You read one page a day.
What we need from you
- One page a day, read
- A call a month, thirty minutes
The hand-over
What you hold when we step back.
At the end of week five everything runs in your accounts, with a name on every queue. Six things change hands, signed.
- 01 / 06
The map, as built
Every workflow drawn as it runs, not as it was planned, with its trigger, tools and owner.
- 02 / 06
Logins and ownership
Every scenario, token and connection sits in your accounts. We hold nothing you cannot switch off.
- 03 / 06
The exception queue
Where a paused run lands, who sees it and what they do. One page, pinned in your helpdesk.
- 04 / 06
The night log
A log every run writes to: clock, event, workflow, result. Readable by anyone on your team.
- 05 / 06
The morning report
Eight numbers on one page at 06:00, with the recipients you chose and the thresholds that wake someone.
- 06 / 06
A one-hour hand-over
Recorded, with the questions your team asked. Yours to keep and to replay for the next hire.
Nothing we build sits in our accounts. Switch us off and it keeps running.
17:30Hand-over signed
After launch
Three ways we stay on the line.
Every workflow is watched for its first week on the house. After that, pick how close we stay.
- 01
Watch
Response: Next morningThe log is read every morning and a paused run is fixed before the office opens.
- Morning report
- Exceptions fixed by 09:00
- A call a month
- 02
Tune
Response: Same dayChanges to a running workflow inside a working day, and a new small workflow a month.
- Everything in Watch
- Changes same day
- One new workflow a month
- A call a fortnight
- 03
Run
Response: Inside an hourThe night rota watches your queue around the clock and an engineer answers inside the hour.
- Everything in Tune
- Night rota on your queue
- Answer inside 60 minutes
- Quarterly re-audit
Week by week
What each week needs from you.
Five weeks, and most of your part is saying yes on time. This is everything we will ask for, before we ask.
- Week 1Week 1Week 01 / 05
The audit
Two half-days with the people who do the work. We sit beside them, list every task that repeats and count the hours honestly. You do not prepare anything.
What we need from you
- Two half-days of your team's time
- A login to each tool, read-only
- One person who can say yes
- Week 2Week 2Week 02 / 05
The map
Every workflow drawn end to end on one board: the trigger, the tools it touches, who signs off, where it can fail. You read it, correct it, approve it.
What we need from you
- An hour to walk the map with us
- The exceptions you can think of
- Your approval, in writing
- Weeks 3–4Weeks 3–4Week 03 / 05
The build
We wire the workflows into your CRM, inbox, invoicing and helpdesk, run them on real records in a sandbox and keep a log you can read. You see each one before it goes live.
What we need from you
- Admin access to the tools we wire
- Twenty real records to test on
- A reply inside a day when we ask
- Week 5Week 5Week 04 / 05
The launch
Workflows go live one at a time, a person watching each for its first week. Exceptions land in a queue with a name on it; nothing lands in a void.
What we need from you
- A named owner for the exception queue
- Fifteen minutes a day for the first five days
- OngoingOngoingWeek 05 / 05
Autopilot
A report every morning on what ran, what paused and what it saved. We tune, add and retire workflows as the business moves. You read one page a day.
What we need from you
- One page a day, read
- A call a month, thirty minutes
The hand-over
What you hold when we step back.
At the end of week five everything runs in your accounts, with a name on every queue. Six things change hands, signed.
- 01 / 06
The map, as built
Every workflow drawn as it runs, not as it was planned, with its trigger, tools and owner.
- 02 / 06
Logins and ownership
Every scenario, token and connection sits in your accounts. We hold nothing you cannot switch off.
- 03 / 06
The exception queue
Where a paused run lands, who sees it and what they do. One page, pinned in your helpdesk.
- 04 / 06
The night log
A log every run writes to: clock, event, workflow, result. Readable by anyone on your team.
- 05 / 06
The morning report
Eight numbers on one page at 06:00, with the recipients you chose and the thresholds that wake someone.
- 06 / 06
A one-hour hand-over
Recorded, with the questions your team asked. Yours to keep and to replay for the next hire.
Nothing we build sits in our accounts. Switch us off and it keeps running.
17:30Hand-over signed
After launch
Three ways we stay on the line.
Every workflow is watched for its first week on the house. After that, pick how close we stay.
- 01
Watch
Response: Next morningThe log is read every morning and a paused run is fixed before the office opens.
- Morning report
- Exceptions fixed by 09:00
- A call a month
- 02
Tune
Response: Same dayChanges to a running workflow inside a working day, and a new small workflow a month.
- Everything in Watch
- Changes same day
- One new workflow a month
- A call a fortnight
- 03
Run
Response: Inside an hourThe night rota watches your queue around the clock and an engineer answers inside the hour.
- Everything in Tune
- Night rota on your queue
- Answer inside 60 minutes
- Quarterly re-audit
Book a call
Tell us what eats your week. We'll automate it.
Pick what fits. On the call we map the first workflow, the tools it touches and the week it goes live.
Book a call
Tell us what eats your week. We'll automate it.
Pick what fits. On the call we map the first workflow, the tools it touches and the week it goes live.
Book a call
Tell us what eats your week. We'll automate it.
Pick what fits. On the call we map the first workflow, the tools it touches and the week it goes live.