What a Claude Code skill for invoice chasing can recover
Money sitting past due costs you every month it sits there. Here is yours.
What it does
It reads your list, sorts it by how late, and writes each message.
What it is, underneath
A plain text file that tells Claude Code what to do with your list. No app, no server, no subscription to a chasing product: what a Claude Code skill is, and how to write one yourself.
Where the week goes
It takes the remembering and the writing. Who to push stays with you.
The three parts in full
- Remembering
- Noticing that today is day 31 on this one. Gone completely.
- Writing
- A polite, firm note with the right reference and amount. Nearly all gone.
- Deciding
- Nudge, phone call, or leave it this week. Still yours.
The dread lives in the last one, and it drags the first two late with it.
Day 31, 61, 91
Same list, three tones: a nudge, then a firmer note, then a final one.
What it does, step by step
- Read the overdue list: one row per invoice, due date and amount.
- Take each due date off today's date. Drop anything not yet due.
- Group the rest at 30, 60 or 90 days.
- Pick the tone from the group.
- Write one message per invoice, with the real reference and amount.
- Put the biggest first and hand the queue to you.
Step two is the one that earns its keep, because it happens on bad weeks too.
It never sends
A wrong chase costs you the customer, not just the invoice. You press send.
The line, either side of it
- Give it
- Reading your own list, grouping by how late, writing from tones you wrote once, sorting the queue by value.
- Never give it
- The send button on any channel, a customer with an open dispute, anything that reads as a legal threat, your payment portal or bank login.
On drafts, the worst failure is a message you delete. With send, it lands in an inbox.
What you need
A list with due dates, three tones written once, and one laptop.
The honest limit
A chasing skill cannot make a customer solvent, and it cannot win an argument about whether the work was done. It only removes the excuse that nobody got round to it. If your overdue money is disputed rather than forgotten, do not buy one.
Setup detail: what you need to run one.
I will scope your chase, free
Tell me what columns your overdue list has. You get a written scope back inside 24 hours, with a straight answer on whether this is worth building for your ledger.
- Scope
- Free, written, inside 24 hours
- Price
- $250 fixed, paid only after you agree the scope
- Delivery
- Tested skill within 5 business days of payment
- If it misses
- I fix it free until it does what the scope says
Questions
What is a Claude Code skill for invoice chasing?
A text file that reads your overdue list, sorts it by how late each invoice is, and writes one message per invoice. It never sends.
What is the overdue money costing me?
Your overdue balance times the rate you borrow at, divided by twelve. That is what the wait costs you every month.
Should it email customers on its own?
No. A wrong chase can cost you the customer rather than the invoice, so a person reads every message and presses send.
How much must it recover to pay for itself?
The $250 build price divided by your average invoice. For most trades that is under one invoice.
Does it work from a spreadsheet?
Yes, as long as every row carries a due date and an amount. A CSV export from your accounting software is enough.
Where every figure here comes from
Sources: the $250 fixed price, the free written scope within 24 hours, the tested skill within 5 business days of payment and the fixed-free guarantee are the terms published on the custom build page and in the Terms. That a skill is a plain text file is set out in what Claude Code skills are. Every other figure here is one you typed in yourself.
Related: the same sum in hours, build it or buy it, and what one costs. Need one built? Free scope in 24 hours, $250 fixed.