An invoice goes out. The due date comes and goes. Nothing lands in your account.
You know the client is good for it. You also know the reminder email is going to sit half-written in your drafts for four days while you find literally anything else to do. Sending it feels like begging for money you already earned.
That gap is where the money hides. Not in bad clients. In reminders nobody sent. This guide hands you an agent that sends them for you, so you never open that draft again.
What The Machine Actually Does
It watches your open invoices, flags the ones past their due date, and emails the client on a cadence that gets firmer the longer they wait. Polite at first. It gets firmer around a week, then moves to a daily nudge once an invoice crosses two weeks overdue. It logs every excuse it gets back and every client who pays late more than once, so next quarter you are not starting from memory.
You set the rules. It does the asking. You never have to send an awkward payment reminder again.
The build is five steps. You can wire it up with Claude or Codex in an afternoon, and most of that time is you deciding how firm you want to get.
Step One: Give It Your Invoice List
The agent needs somewhere to look. That means a list of your invoices with five things on each row: the amount, the client's email, the date you issued it, the date it was due, and whether it has been paid.
A spreadsheet is fine. An export from your invoicing tool is fine. It does not matter where the list lives, only that those five columns are on it.
Your first real run: point the agent at last month's invoices and ask it to tell you which ones are overdue and by how many days. Do not let it send anything yet. Just read. You want to see it reading your data correctly before it ever touches a client.
The mistake that makes it fail: a list with no due date. If the agent cannot tell late from on time, it cannot do a single thing. Every row needs a due date, not just an issue date.
Step Two: Decide What Late Means
Late is your call, not the agent's. Net 15, net 30, a few days of grace before the first nudge. Whatever you actually run your business on, write it down in one line.
Your first real run: tell the agent your terms in plain words. "An invoice is late the day after its due date. Give a three-day grace period before the first email." Then ask it to re-sort last month's list under that rule and confirm it matches what you would have flagged by hand.
The mistake that makes it fail: treating a one-day-late invoice the same as a thirty-day-late one. The entire point of this machine is the ramp. A flat reminder is just a nag. A ramp is a system.
Step Three: Write The Escalation Ladder
This is the core of the whole thing. The ladder is where you tell the agent how to change its tone as an invoice ages.
Here is a sane default. Treat every row as yours to tune.
| Days overdue | Tone | How often it emails |
|---|---|---|
| 1 to 7 | Friendly nudge. Assumes it slipped their mind. | Once |
| 8 to 14 | Firmer. Names the amount and the due date that passed. | Every few days |
| 15 and up | Final notice. Asks for a specific pay date. | Daily |
The two-week mark is the line that matters. Before it, you are reminding. After it, you are collecting. The agent should sound different on either side of that line, and it should get in touch more often the further past it a client drifts.
Copy the spec below into your agent and swap the bracketed parts for your numbers and your voice.
Copy this.
You handle overdue-invoice follow-ups for [YOUR BUSINESS NAME]. For each overdue invoice, pick the email tone by how many days late it is: - [1] to [7] days late: friendly. One email. Assume it slipped their mind. Reference the invoice number and amount. Ask them to confirm they got it. - [8] to [14] days late: firmer. Send every [3] days. State the amount, state the due date that passed, ask when they plan to pay. - [15]+ days late: final notice. Send daily. Ask for a specific payment date and name what happens if it passes ([pause new work / late fee / hand to accounts]). Sign every email as [YOUR NAME]. Never insult the client. Never threaten anything you would not actually do. The goal is the money and the relationship, in that order.
The mistake that makes it fail: staying friendly forever because firm feels uncomfortable. An email that never changes its tone gets read once and filed under later, which is a folder that means never. The discomfort is the feature.
Copy The Three Emails
The ladder decides which email goes out. These are the emails. Paste them into your agent as the starting text for each stage and let it fill the brackets from the invoice row. Adjust the wording until it sounds like you, then leave it alone.
The friendly nudge, for the first week late:
Copy this.
Subject: Invoice [1024] from [YOUR BUSINESS] Hi [FIRST NAME], Quick one. Invoice [1024] for [amount] was due on [due date] and I have not seen it come through yet. It probably just slipped past. Could you confirm you have it and let me know when it is going out? Thanks, [YOUR NAME]
The firmer email, once it is more than a week late:
Copy this.
Subject: Overdue: invoice [1024], [amount] Hi [FIRST NAME], Invoice [1024] for [amount] is now [10] days past its [due date] due date. I would like to get this cleared. Can you tell me the date you will be paying it? If something is holding it up on your end, let me know and we will sort it. [YOUR NAME]
The final notice, past two weeks:
Copy this.
Subject: Final notice: invoice [1024], [amount] Hi [FIRST NAME], Invoice [1024] for [amount] is now [16] days overdue. I need a firm payment date by [date]. If I do not have one, I will [pause new work / apply the late fee in our terms / pass this to accounts]. I would rather settle this directly. Let me know today. [YOUR NAME]
The mistake that makes it fail: writing three emails that say the same thing in the same voice. Read them top to bottom. If a stranger could not tell the first from the last, the ramp is not working yet.
Step Four: Hand It The Send Button, Or Do Not, Yet
The agent can run in two modes. In draft mode it writes each email and leaves it for you to send. In auto mode it sends on its own.
Run draft mode for the first week. Read what it writes to real clients before a single one goes out. You are checking one thing: does it sound like you, and does it get firmer at the right point.
When the tone is off, correct it in plain words. Say: the second-stage email is too soft, name the amount and the number of days overdue. Say: the final notice reads angry, make it flat and factual. It will adjust and hold the change.
Once a week of drafts reads the way you want, flip it to auto for the early stages and keep the final-notice stage in draft. That way the agent handles the routine nudging and you personally sign off on anything headed to a client who is two weeks late.
The mistake that makes it fail: turning on auto-send before you have read its tone. The first client to get a badly judged email is the one you least wanted to annoy.
Step Five: Keep The Excuse Log And The Repeat List
When a client replies with a reason instead of a payment, that reason is data. Payment is processing. Never got the invoice. My accountant is away. The agent should log each one against the client.
It should also keep a running list of anyone who pays late more than once. That list is worth more than any single reminder. Next quarter it tells you exactly who to move onto shorter terms, who to ask for a deposit up front, and who is quietly costing you a week of cash flow every month.
This is the step everyone skips, because it does not pay off today. It is also the step that compounds. A reminder saves you one email. A repeat-offender list changes who you sign next year.
The onboarding side of this is its own build: the onboarding flow brings a client in clean. This one makes sure the work you did for them actually gets paid. Run both and the two ends of a client relationship stop leaking.
The Limits Worth Knowing Before You Turn It On
Keep a human on the first send to your biggest accounts. An agent judging tone from a due date does not know that this particular client is about to sign a much larger deal. For the relationships that carry your year, read before it sends.
Payment reminders are legal. Harassment is not. Rules on chasing debt vary by country, and the daily-nudge stage is meant for invoices that are genuinely weeks overdue, not for leaning on someone the day after the due date. Set the ramp to match honest lateness, not impatience.
Do not roast anyone. The joke version of this idea going around online ends with the machine digging up dirt to burn the relationship on purpose. That is a bit for a video. In your actual business a firm, factual final notice is what gets you paid and keeps the client. Anger loses both.
It chases, it does not collect. For an account that has gone silent through every stage, the agent has done its job by documenting the trail. From there you escalate to a person, a lawyer, or a collections service. The machine is your first line, not your last.
And it is only as clean as your invoice list. If a paid invoice is still marked unpaid, the agent will email someone who already settled up, which is the one message that actually damages a relationship. Reconcile what has been paid before you let it send.
Do This One Thing This Week
Run Step One in read-only mode. Point the agent at last month's invoices and let it tell you what is overdue and by how much. Do not build the ladder yet. Do not send anything.
Just look at the number it hands back. Most people find money they had quietly written off. If the total is small, you spent ten minutes. If it is not, you just found the first real reason to let the machine start sending.