Runbook
Tasks tonight1,284
02:20Monday report sent
02:20Monday report sent
02:20Monday report sent
Part 01 / 04What it does
What runswhile nobody is in.
Revenue, pipeline, cash, delivery and support figures are pulled from each system overnight, reconciled and written up as one short page with the changes that matter flagged. It is in the inbox at 07:00 on Monday and in Slack on the other days, and the month-end pack builds itself from the same data.
What you get
- 01The workflow built in your own accounts, documented and yours to keep
- 02A test run on real records before anything goes live
- 03A log line for every run and an alert to us when one fails
- 04A person watching the first week, then the monthly care plan
Part 02 / 04How it runs
Trigger, steps,result.
Every run follows the same drawn path. A step that cannot complete parks the record for a person and says why.
- TriggerA record changes in your tools: a job closes, a form lands, a message arrives.
- 01ReadThe record is read from the tool it lives in: who, what, how much.
- 02CheckRules run against it. Anything odd is parked for a person, nothing odd is parked for nobody.
- 03ActThe document is built, the message sent, the field updated, in your own tone.
- 04LogOne line in the night log, with the time and the outcome, so you can read what ran.
- Result02:20 · Monday report sent
Part 03 / 04Tools
The toolsit runs on.
Runs on
- Google Sheets
- Looker Studio
- Xero
- HubSpot
- Slack
SalesUsed in 4 workflowsCRM
Every lead, deal and note in one place, kept current by the workflows rather than by people.Connects toHubSpot, Pipedrive, Salesforce
FinanceUsed in 3 workflowsInvoicing
Quotes become invoices, invoices become reconciled cash.Connects toXero, QuickBooks, Stripe
CommsUsed in 5 workflowsInbox
Mail read, sorted and drafted before you open it.Connects toGmail, Outlook, Slack
Part 04 / 04Results
What it didfor others.
Part 01 / 04What it does
What runswhile nobody is in.
Revenue, pipeline, cash, delivery and support figures are pulled from each system overnight, reconciled and written up as one short page with the changes that matter flagged. It is in the inbox at 07:00 on Monday and in Slack on the other days, and the month-end pack builds itself from the same data.
What you get
- 01The workflow built in your own accounts, documented and yours to keep
- 02A test run on real records before anything goes live
- 03A log line for every run and an alert to us when one fails
- 04A person watching the first week, then the monthly care plan
Part 02 / 04How it runs
Trigger, steps,result.
Every run follows the same drawn path. A step that cannot complete parks the record for a person and says why.
- TriggerA record changes in your tools: a job closes, a form lands, a message arrives.
- 01ReadThe record is read from the tool it lives in: who, what, how much.
- 02CheckRules run against it. Anything odd is parked for a person, nothing odd is parked for nobody.
- 03ActThe document is built, the message sent, the field updated, in your own tone.
- 04LogOne line in the night log, with the time and the outcome, so you can read what ran.
- Result02:20 · Monday report sent
Part 03 / 04Tools
The toolsit runs on.
Runs on
- Google Sheets
- Looker Studio
- Xero
- HubSpot
- Slack
- SalesUsed in 4 workflows
CRM
Every lead, deal and note in one place, kept current by the workflows rather than by people.Connects toHubSpot, Pipedrive, Salesforce - FinanceUsed in 3 workflows
Invoicing
Quotes become invoices, invoices become reconciled cash.Connects toXero, QuickBooks, Stripe - CommsUsed in 5 workflows
Inbox
Mail read, sorted and drafted before you open it.Connects toGmail, Outlook, Slack
Part 04 / 04Results
What it didfor others.
Part 01 / 04What it does
What runswhile nobody is in.
Revenue, pipeline, cash, delivery and support figures are pulled from each system overnight, reconciled and written up as one short page with the changes that matter flagged. It is in the inbox at 07:00 on Monday and in Slack on the other days, and the month-end pack builds itself from the same data.
What you get
- 01The workflow built in your own accounts, documented and yours to keep
- 02A test run on real records before anything goes live
- 03A log line for every run and an alert to us when one fails
- 04A person watching the first week, then the monthly care plan
Part 02 / 04How it runs
Trigger, steps,result.
Every run follows the same drawn path. A step that cannot complete parks the record for a person and says why.
- TriggerA record changes in your tools: a job closes, a form lands, a message arrives.
- 01ReadThe record is read from the tool it lives in: who, what, how much.
- 02CheckRules run against it. Anything odd is parked for a person, nothing odd is parked for nobody.
- 03ActThe document is built, the message sent, the field updated, in your own tone.
- 04LogOne line in the night log, with the time and the outcome, so you can read what ran.
- Result02:20 · Monday report sent
Part 03 / 04Tools
The toolsit runs on.
Runs on
- Google Sheets
- Looker Studio
- Xero
- HubSpot
- Slack
- SalesUsed in 4 workflows
CRM
Every lead, deal and note in one place, kept current by the workflows rather than by people.Connects toHubSpot, Pipedrive, Salesforce - FinanceUsed in 3 workflows
Invoicing
Quotes become invoices, invoices become reconciled cash.Connects toXero, QuickBooks, Stripe - CommsUsed in 5 workflows
Inbox
Mail read, sorted and drafted before you open it.Connects toGmail, Outlook, Slack
Part 04 / 04Results
What it didfor others.
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.