finance
Invoice follow-up on autopilot
Late invoices chased on a polite, escalating schedule, in your voice. You approve the tone once; the consistency is her job.
How she runs it
- 1 Tell her your ladder once: when the friendly nudge goes, when the tone turns direct, where the boundary sits.
- 2 She tracks every invoice date and sends each rung on schedule, in your voice.
- 3 Replies land in your shared inbox; anything a client says that needs judgment comes to you as one question.
- 4 The boundary rung never goes out without your yes.
Chasing an invoice is a system pretending to be an awkward conversation. The system part is easy to design and brutal to run: the right message, on the right day, for every client, forever. That second part is the whole job, and it is the part that quietly stops happening the week you get busy.
Amber runs the ladder you design. The friendly bump goes out the day an invoice slips. The direct ask follows on your schedule, with the invoice reattached and the amount restated so nobody digs through a thread. The firm rung waits for your yes. Every reply lands where you can see it, and the first one that needs an actual decision becomes one clear question instead of a guilt spiral.
The chasing guide covers how to write a ladder worth running, and the 9-day rule covers the calendar. This page is the part where you stop being the one who runs it.
Fair questions
Will she send anything without asking me?
Only the rungs you approved when you set the ladder up. The firm boundary message and anything a client reply makes unusual come back to you as one clear question first.
What tone does she use?
Yours. She drafts from the messages you approve at setup, and the early rungs stay warm on purpose: most late payments are forgetfulness, and forgetfulness only needs a shrug.
What happens when a client actually cannot pay?
That is a judgment call, so it stops being her job. The moment a reply needs a decision, it lands with you, with the invoice history attached.