Runbook
Tasks tonight1,284
Insight
Which workflow to automate first
Sort the list by hours lost, not by what looks clever. A ten-minute scoring method that picks the first project.
6 Oct 2026 · 5 min read
Insight
Which workflow to automate first
Sort the list by hours lost, not by what looks clever. A ten-minute scoring method that picks the first project.
6 Oct 2026 · 5 min read
Insight
Which workflow to automate first
Sort the list by hours lost, not by what looks clever. A ten-minute scoring method that picks the first project.
6 Oct 2026 · 5 min read
Every company that calls us has a list of things it would like to automate. The list is usually sorted by what looks clever. Sort it by hours instead and the first project picks itself.
Score each task on three things
- Hours a week it takes across the whole team, counted honestly
- How often it goes wrong when a person does it tired or in a hurry
- How many systems it touches: a task that copies the same data into three tools is the best candidate there is
Multiply the three and the top of the list is your first workflow. In our experience it is invoicing or lead follow-up about four times out of five.
Leave these for later
Anything that needs judgement on every run, anything that happens twice a year, and anything you are still changing every week. Automate a process after it has settled, not while you are designing it.
The ten-minute version
Ask each person for the one task they would hand over tomorrow. You will hear the same two or three answers. Those are the ones.
The first workflow should pay for itself inside a month and be visible to everyone. Momentum matters more than ambition at the start.
What a good first project looks like
It removes a task completely rather than making it faster. It has one owner. It writes a log you can read. And when it fails, it tells someone, which is more than the manual version ever did.
Something in your week that should run itself?
Tell us what eats the hours. A 20-minute call, a map of the first workflow, no deck.
Keep reading
Two more from the night shift.
01Insight26 Sep 20266 min readZapier, Make or n8n: which one your business should run on
Same apps, different owners, different costs at volume. How we choose, and where AI agents fit.Read the article
02Guide15 Sep 20265 min readChasing invoices without chasing anyone
A four-step sequence in the client's own tone, tied to the day the work finishes, that stops the moment the money lands.Read the articleEvery company that calls us has a list of things it would like to automate. The list is usually sorted by what looks clever. Sort it by hours instead and the first project picks itself.
Score each task on three things
- Hours a week it takes across the whole team, counted honestly
- How often it goes wrong when a person does it tired or in a hurry
- How many systems it touches: a task that copies the same data into three tools is the best candidate there is
Multiply the three and the top of the list is your first workflow. In our experience it is invoicing or lead follow-up about four times out of five.
Leave these for later
Anything that needs judgement on every run, anything that happens twice a year, and anything you are still changing every week. Automate a process after it has settled, not while you are designing it.
The ten-minute version
Ask each person for the one task they would hand over tomorrow. You will hear the same two or three answers. Those are the ones.
The first workflow should pay for itself inside a month and be visible to everyone. Momentum matters more than ambition at the start.
What a good first project looks like
It removes a task completely rather than making it faster. It has one owner. It writes a log you can read. And when it fails, it tells someone, which is more than the manual version ever did.
Something in your week that should run itself?
Tell us what eats the hours. A 20-minute call, a map of the first workflow, no deck.
Keep reading
Two more from the night shift.
01Insight26 Sep 20266 min readZapier, Make or n8n: which one your business should run on
Same apps, different owners, different costs at volume. How we choose, and where AI agents fit.Read the article02Guide15 Sep 20265 min readChasing invoices without chasing anyone
A four-step sequence in the client's own tone, tied to the day the work finishes, that stops the moment the money lands.Read the articleEvery company that calls us has a list of things it would like to automate. The list is usually sorted by what looks clever. Sort it by hours instead and the first project picks itself.
Score each task on three things
- Hours a week it takes across the whole team, counted honestly
- How often it goes wrong when a person does it tired or in a hurry
- How many systems it touches: a task that copies the same data into three tools is the best candidate there is
Multiply the three and the top of the list is your first workflow. In our experience it is invoicing or lead follow-up about four times out of five.
Leave these for later
Anything that needs judgement on every run, anything that happens twice a year, and anything you are still changing every week. Automate a process after it has settled, not while you are designing it.
The ten-minute version
Ask each person for the one task they would hand over tomorrow. You will hear the same two or three answers. Those are the ones.
The first workflow should pay for itself inside a month and be visible to everyone. Momentum matters more than ambition at the start.
What a good first project looks like
It removes a task completely rather than making it faster. It has one owner. It writes a log you can read. And when it fails, it tells someone, which is more than the manual version ever did.
Something in your week that should run itself?
Tell us what eats the hours. A 20-minute call, a map of the first workflow, no deck.
Keep reading
Two more from the night shift.
01Insight26 Sep 20266 min readZapier, Make or n8n: which one your business should run on
Same apps, different owners, different costs at volume. How we choose, and where AI agents fit.Read the article02Guide15 Sep 20265 min readChasing invoices without chasing anyone
A four-step sequence in the client's own tone, tied to the day the work finishes, that stops the moment the money lands.Read the article
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.