A client is refusing to pay my invoice. What are my options?
A handover brings the recorded AI work and its verifiable receipts into one proof link. Review the evidence behind each claim, check what was and was not observed, then Accept or Flag.
Scope: general information about options and sequence, not legal advice. The right path depends on the amount, the contract, and your jurisdiction; a short consultation early often pays for itself.
The mistake in refusal situations is jumping rungs: threatening court in the first message (which hardens), or sending endless reminders (which teaches). The ladder works because each rung changes the situation formally, not emotionally. Rung one is private: assemble the facts from the record, the agreement, the delivery with its steps and timestamps, the acceptance if one was recorded, and the exact amount with its due date. Many refusals soften at this rung, when the client learns the facts exist in this form.
Rung two is the factual reminder, rung three the demand letter, both specified in this cluster (the pillar page carries the letter template). Rung four is choosing the structured path. Platform work goes to the platform's dispute process with the evidence bundle. Direct work divides by amount: mediation suits mid-sized disputes where the relationship or the amount justifies a facilitated conversation; small claims suits smaller amounts where filing is cheap and lawyers are optional; collection services suit clear-cut debts you would rather sell at a discount than chase.
At every rung the record is doing quiet work: it shortens each process, because each decision-maker, arbitrator, mediator, judge, collector, starts from documents instead of from two stories. Keep copies of everything each rung produces in the job folder; the folder is the case if the case ever becomes one.
Checklist: the refusal ladder
Rung 1, facts: agreement, delivery record, acceptance state, amount, due date, assembled in the job folder. Rung 2, reminder: one message, record attached, new date named. Rung 3, demand letter: the cluster pillar's template, sent by a channel that shows receipt. Rung 4, structured path, choose one: platform dispute with the evidence bundle; mediation; small claims filing; collection service. At each rung: a deadline, a single next step, and everything filed. Stop rule: no rung is repeated; a missed deadline moves you up, not louder.
Worked example
Rung 1's core document in public form: https://zambo.dev/handover/45434a17-4afc-486a-9646-e689bcee4297 shows a delivered job with the client's recorded acceptance. A refusal that meets this object at rung 2 frequently ends there, because the remaining argument is only about the payment date.
Frequently asked questions
Should I stop all work for this client immediately?
Pause new work once a refusal is explicit, politely and in writing, and say it resumes on payment. Continuing to deliver into a refusal converts a strong position into a larger unpaid balance; pausing is standard, not hostile.
The amount is small. Is any of this worth it?
The early rungs are worth it at almost any amount because they are cheap, and they protect the pattern of your business. Below your time's value, a collection service or a written-off lesson are both rational; decide once, in numbers, not in frustration.
The client says they will pay when I fix unrelated complaints. What then?
Separate the conversations in writing: the invoice for delivered and accepted work stands on its rung; complaints get their own itemised answer from the record. Bundling is the client's leverage; the ladder's order is yours.
By Brennan Zambo, founder of Zambo.
Last verified: 2026-10-17.
Try a handover
A handover gives your client one proof link with verifiable receipts to review, then Accept or Flag.
try it: say 'use zambo to hand this over to <client>' in your ai