Runbook
Tasks tonight1,284
Insight
The Monday report: eight numbers, one page
Built overnight from every system, read in a minute, and nobody builds it.
19 Aug 2026 · 5 min read
Insight
The Monday report: eight numbers, one page
Built overnight from every system, read in a minute, and nobody builds it.
19 Aug 2026 · 5 min read
Insight
The Monday report: eight numbers, one page
Built overnight from every system, read in a minute, and nobody builds it.
19 Aug 2026 · 5 min read
Most reporting is building the report. The reading takes a minute. So the job of a reporting workflow is to remove the building completely and make the minute worth it.
Eight numbers
Cash in the bank, invoices outstanding, revenue this month against plan, pipeline value, leads this week, jobs delivered, support tickets open, and one number specific to the business. Any more than eight and nobody reads it.
One page
The number, the change since last week, and a one-line note when the change is outside the normal range. No charts on the page; a link to the dashboard for the people who want to dig.
Built overnight
- Each system is read between 04:00 and 06:00
- Figures are reconciled against each other (invoiced revenue must match the accounting ledger)
- The page is written and checked for missing data
- It arrives at 07:00 on Monday, with a short version in Slack on the other days
What it replaced
At one client, a finance manager spent Monday morning on this. At another, an operations lead spent Sunday evening. Both still read the report. Neither builds it.
If a number has to be explained every week, the number is wrong, not the reader.
Month end
The month-end pack is the same data over a longer window. Once the weekly report is trustworthy, the month-end pack builds itself from it in minutes rather than days.
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.
01Report4 Aug 20266 min readWhat manual admin costs a 20-person company
190 hours a month, measured across 38 audits. Where the hours hide and what the first three workflows recover.Read the article
02Guide6 Oct 20265 min readWhich 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.Read the articleMost reporting is building the report. The reading takes a minute. So the job of a reporting workflow is to remove the building completely and make the minute worth it.
Eight numbers
Cash in the bank, invoices outstanding, revenue this month against plan, pipeline value, leads this week, jobs delivered, support tickets open, and one number specific to the business. Any more than eight and nobody reads it.
One page
The number, the change since last week, and a one-line note when the change is outside the normal range. No charts on the page; a link to the dashboard for the people who want to dig.
Built overnight
- Each system is read between 04:00 and 06:00
- Figures are reconciled against each other (invoiced revenue must match the accounting ledger)
- The page is written and checked for missing data
- It arrives at 07:00 on Monday, with a short version in Slack on the other days
What it replaced
At one client, a finance manager spent Monday morning on this. At another, an operations lead spent Sunday evening. Both still read the report. Neither builds it.
If a number has to be explained every week, the number is wrong, not the reader.
Month end
The month-end pack is the same data over a longer window. Once the weekly report is trustworthy, the month-end pack builds itself from it in minutes rather than days.
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.
01Report4 Aug 20266 min readWhat manual admin costs a 20-person company
190 hours a month, measured across 38 audits. Where the hours hide and what the first three workflows recover.Read the article02Guide6 Oct 20265 min readWhich 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.Read the articleMost reporting is building the report. The reading takes a minute. So the job of a reporting workflow is to remove the building completely and make the minute worth it.
Eight numbers
Cash in the bank, invoices outstanding, revenue this month against plan, pipeline value, leads this week, jobs delivered, support tickets open, and one number specific to the business. Any more than eight and nobody reads it.
One page
The number, the change since last week, and a one-line note when the change is outside the normal range. No charts on the page; a link to the dashboard for the people who want to dig.
Built overnight
- Each system is read between 04:00 and 06:00
- Figures are reconciled against each other (invoiced revenue must match the accounting ledger)
- The page is written and checked for missing data
- It arrives at 07:00 on Monday, with a short version in Slack on the other days
What it replaced
At one client, a finance manager spent Monday morning on this. At another, an operations lead spent Sunday evening. Both still read the report. Neither builds it.
If a number has to be explained every week, the number is wrong, not the reader.
Month end
The month-end pack is the same data over a longer window. Once the weekly report is trustworthy, the month-end pack builds itself from it in minutes rather than days.
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.
01Report4 Aug 20266 min readWhat manual admin costs a 20-person company
190 hours a month, measured across 38 audits. Where the hours hide and what the first three workflows recover.Read the article02Guide6 Oct 20265 min readWhich 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.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.