The Invoice Chase Tone Ladder
Five escalating reminders that collect without burning the relationship.
Founders either send nothing for two months or send one furious email. The money is in the five calm messages in between.
That is the gap this drop closes. It is a finance & admin skill built for Claude, and it takes about ten minutes to set up the first time. After that it runs in under a minute.
Who should use it
Anyone invoicing on 30 to 90 day terms in the Gulf.
How it works
The skill file does five things, in this order.
1. Set the ladder. Day 1 after due, day 7, 14, 30, 45. Each with a different job.
2. Match tone to history. A good customer who is late once is not a repeat offender.
3. Give them an easy out. A payment plan option converts more than a threat.
4. Escalate by named person. Accounts, then their manager, then your director. Not louder emails.
5. Write the final notice. Factual, dated, and specific about what happens next.
What comes back
Five ready-to-send drafts per customer, matched to their payment history.
The mistake to avoid
Never open with an apology. 'Sorry to chase' teaches the reader that being chased is something you feel guilty about, and guilt is not a payment trigger.
Running it
Save this as SKILL.md inside a folder named after the skill, then drop the folder into your Claude Code skills directory or upload it to a Claude Project. Claude reads the frontmatter to decide when the skill applies, so keep the description line intact. For a one-off run, paste the prompt block directly.
Where this fits
On its own, one skill saves an hour a week. The compounding happens when three or four of them run in sequence on the same input, the same transcript that produces a scope of work also produces the follow-up email and the project brief. That is the point at which it stops being a prompt and starts being an internal tool. If you want that wired into the systems your team already uses, that is the work 67 Digital does.
In the file
Draft an invoice chase ladder for this customer.
Input: invoice amount, days overdue, our payment history with them, the
relationship value, the named contacts we have.
Produce five messages for day +1, +7, +14, +30, +45. Each must:
- Have a different job. (1) assume oversight (2) offer help (3) create a
specific deadline (4) escalate to a named person (5) state consequences.
- Never open with an apology or the word "just".
- Include the exact amount, invoice number, and due date every time.
- Offer a payment plan from message 3 onward.
Adjust tone for history: FIRST TIME LATE gets warmth throughout. REPEAT
OFFENDER gets formality from message 2. Note which you applied and why.