The InvoiceYou
The invoice goes out late, because sending it sat on your list under everything else.
Case Study 09 / 09
The Collections Loop
Operations was one of the four workflows I removed myself from, and chasing money was the part I put off longest. Writing the invoice is easy. Reminding a client about it, again, in a tone that keeps the relationship, is the chore that quietly never happens. So the loop owns the cadence now: invoice, ledger, reminders on schedule. The only thing that reaches me is the one that's actually stuck.
06 Steps Before
01 Stays Yours
01The Workflow, BeforeEvery badge is you
The WaitYou
You notice it's unpaid by accident, weeks in, while looking for something else.
The ReminderYou
You draft the reminder four times, trying to sound relaxed about your own money.
The CadenceYou
The second reminder feels worse than the first, so it waits, and the waiting becomes the system.
The LedgerYou
You only know who owes what when you sit down and count, and you avoid sitting down.
The EscalationYou
By the time it's clearly a problem, it's been quietly unpaid for months and the conversation is hard.
02The Same Workflow, Running on AgentsSame steps, new owners
The InvoiceAgent
The invoice goes out the day the work says it should, every time.
The WaitAgent
Paid or unpaid is tracked from the moment it sends. Nothing gets discovered by accident.
The ReminderAgent
Reminders are written once, in a tone you approved, and sent without any of your dread in them.
The CadenceAgent
The follow-ups keep their schedule whether you had a brave week or not.
The LedgerAgent
Who owes what is a list you can read, current to the day.
The EscalationYou
Only the stuck ones reach you, early enough that the conversation is still easy. Each arrives with its story so far: every reminder sent, every silence after.
The Hand-Off · The loop chases. You only hear about the stuck ones
03The System MapYou sit outside the loop
Invoicer
Ledger Keeper
Reminder Clock
Escalation Flag
The Loop
Escalations Only
YouOutside the loop
04The ArtifactsWhat the loop produces
The Ledger01 / 02
The Escalation Note02 / 02
05What Stays Yours
-
You
The grace. Who gets slack and how much is a relationship call. The loop doesn't make it. Pause a client and the pause goes on record as your decision, not a lapse.
-
You
The hard conversation. When a client truly can't pay, the machine stops and a person decides.
-
You
The line. When to stop working for someone who doesn't pay is yours alone.
06The Verdict FrameWhat a session would call this
In a session, this workflow gets one of three verdicts: automate it now, fix it manually first, or leave it alone.
Collections is close to a default "automate it now", because the whole system is cadence and a machine keeps cadence better than a person who hates the task. The exception is upstream: if the invoices themselves go out wrong, wrong amounts, wrong dates, the verdict is "fix it manually first", because a reminder about a wrong invoice just escalates the mistake. And if your clients already pay on time, leave it alone. There's nothing to chase.
Sixty minutes. The spec for this, written live.
Book the session