Runbook
Tasks tonight1,284
Insight
Chasing 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.
15 Sep 2026 · 5 min read
Insight
Chasing 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.
15 Sep 2026 · 5 min read
Insight
Chasing 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.
15 Sep 2026 · 5 min read
The money is usually there. The invoice just has not been seen by the right person yet. Chasing well is a sequence, not a phone call, and a sequence is something a workflow does better than a founder.
Send it the day the work finishes
An invoice sent at month end for work done on the 3rd is already four weeks late. Tie the invoice to the event that ends the work: a milestone marked done, a delivery confirmed, a timesheet approved.
The sequence we use
- Day 0: invoice with a payment link, addressed to the person who approves it
- Day 7: a short note, no apology, the link again
- Day 14: a note that names the amount and the date it was due
- Day 21: a note that says what happens next, copied to the person who signed the contract
Each note is written in the client's own tone. The sequence stops the moment the payment lands, which is the part people get wrong when they do it by hand.
Make paying easy
Card, bank transfer and direct debit on the same page. A client who can pay in one click on a phone pays on the day they read the mail.
Average days to payment for our clients went from 44 to 31 in the first quarter after the sequence went live. Nobody on their side chased anyone.
When to involve a person
Disputes and part-payments. The workflow should spot both and hand them over with the history attached, then stop sending reminders until someone has looked.
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.
01Insight2 Sep 20266 min readWhat an AI agent should and should not answer in support
About 70 % of tickets can close on their own. The other 30 % is where the setup matters.Read the article
02Guide19 Aug 20265 min readThe Monday report: eight numbers, one page
Built overnight from every system, read in a minute, and nobody builds it.Read the articleThe money is usually there. The invoice just has not been seen by the right person yet. Chasing well is a sequence, not a phone call, and a sequence is something a workflow does better than a founder.
Send it the day the work finishes
An invoice sent at month end for work done on the 3rd is already four weeks late. Tie the invoice to the event that ends the work: a milestone marked done, a delivery confirmed, a timesheet approved.
The sequence we use
- Day 0: invoice with a payment link, addressed to the person who approves it
- Day 7: a short note, no apology, the link again
- Day 14: a note that names the amount and the date it was due
- Day 21: a note that says what happens next, copied to the person who signed the contract
Each note is written in the client's own tone. The sequence stops the moment the payment lands, which is the part people get wrong when they do it by hand.
Make paying easy
Card, bank transfer and direct debit on the same page. A client who can pay in one click on a phone pays on the day they read the mail.
Average days to payment for our clients went from 44 to 31 in the first quarter after the sequence went live. Nobody on their side chased anyone.
When to involve a person
Disputes and part-payments. The workflow should spot both and hand them over with the history attached, then stop sending reminders until someone has looked.
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.
01Insight2 Sep 20266 min readWhat an AI agent should and should not answer in support
About 70 % of tickets can close on their own. The other 30 % is where the setup matters.Read the article02Guide19 Aug 20265 min readThe Monday report: eight numbers, one page
Built overnight from every system, read in a minute, and nobody builds it.Read the articleThe money is usually there. The invoice just has not been seen by the right person yet. Chasing well is a sequence, not a phone call, and a sequence is something a workflow does better than a founder.
Send it the day the work finishes
An invoice sent at month end for work done on the 3rd is already four weeks late. Tie the invoice to the event that ends the work: a milestone marked done, a delivery confirmed, a timesheet approved.
The sequence we use
- Day 0: invoice with a payment link, addressed to the person who approves it
- Day 7: a short note, no apology, the link again
- Day 14: a note that names the amount and the date it was due
- Day 21: a note that says what happens next, copied to the person who signed the contract
Each note is written in the client's own tone. The sequence stops the moment the payment lands, which is the part people get wrong when they do it by hand.
Make paying easy
Card, bank transfer and direct debit on the same page. A client who can pay in one click on a phone pays on the day they read the mail.
Average days to payment for our clients went from 44 to 31 in the first quarter after the sequence went live. Nobody on their side chased anyone.
When to involve a person
Disputes and part-payments. The workflow should spot both and hand them over with the history attached, then stop sending reminders until someone has looked.
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.
01Insight2 Sep 20266 min readWhat an AI agent should and should not answer in support
About 70 % of tickets can close on their own. The other 30 % is where the setup matters.Read the article02Guide19 Aug 20265 min readThe Monday report: eight numbers, one page
Built overnight from every system, read in a minute, and nobody builds it.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.