Will the reminders damage the client relationship?
The escalation ladder is built to avoid that. Early touches assume an oversight, which is usually true, and firm language only appears once an invoice is well outside your stated terms.
Ops
Send the payment reminders you keep putting off, in a tone that keeps the relationship intact.
Follows the Agent Skills open format, works with Claude Code, Cursor, Hermes Agent, OpenClaw, and 30+ compatible agents.
What it does
This skill takes your aging report or a copied list of unpaid invoices and writes the reminder each one actually needs. A five-day-late invoice from a good client gets a light nudge. A sixty-day-late invoice gets a firm message that names the amount, the terms, and what happens next.
Most small teams do not have a collections problem so much as an awkwardness problem: the reminder never gets written because the tone is hard to get right. The pack picks the escalation level from days overdue, amount, and relationship value, then drafts to that level so you are not deciding how blunt to be every time.
Every draft states the invoice number, the amount, the original due date, and one clear payment path. It never threatens anything you have not actually agreed to in your terms.
Who it is for
Requirements
Overdue invoice list
Aging report export or a list with invoice number, amount, and due date
Payment terms
Your net terms, late fees if any, and what you will actually enforce
Relationship notes
Optional. Clients who need a softer tone or have a known approval delay.
Invoicing tool
Optional. Source for the aging export and the payment link you include.
Sample output
Invoice INV-1042 - Palewood Studio - $4,800 - 38 days overdue Escalation level: 3 of 4 (firm, still cooperative) Subject: Invoice INV-1042 - now 38 days past due Hi Dana, invoice INV-1042 for $4,800 was due on 12 June and is now 38 days past due. Our terms are net 30, so this one is well outside them. Can you confirm today whether it is scheduled for payment, and the date? If there is a problem with the invoice itself, tell me what it is and I will fix it this week. Payment link and bank details are in the original invoice, resent below. Next touch: 5 days. If unpaid and unanswered, move to level 4 and pause new work. If they ask for a payment plan: offer two equal payments 14 days apart, in writing, before resuming delivery.
What's in this pack
Included: Outcome definition
What exact job this pack solves
Included: Operating instructions
Step-by-step workflow the agent follows
Included: Input contract
Required and optional fields defined as a schema
Included: Output contract
Exact output structure the agent must return
Included: Worked examples(6 files)
3 standard, 1 ambiguous, 1 bad-fit, and 1 edge-case scenario
Test & eval set
FAQ
The escalation ladder is built to avoid that. Early touches assume an oversight, which is usually true, and firm language only appears once an invoice is well outside your stated terms.
Yes. When a client pushes back on an amount, the pack drafts a response that separates the disputed line from the undisputed balance so the rest can still be paid.
No. It drafts and schedules them on paper. Payment chasing is a relationship decision, so a human sends every message.
Bundle option
This pack is also included in Founder Ops Pack, which groups related workflows for a faster setup.
View bundleRelated packs
Ops
Turn a signed deal into a week-one onboarding plan, kickoff email, and task checklist.
Test cases with expected outputs and pass/fail criteria
Included: QA checklist
Human review checklist for output quality
Ops
Turn a messy process walkthrough into a step-by-step SOP your team or agent can run.
Ops
Summarize weekly metrics, outliers, likely drivers, and recommended follow-up in one operating brief.