ZAMBO.

Direct answer

Payment is being held for fixes nobody agreed. Sort the list first.

The work is delivered, the invoice is due, and back comes a list: fix this, adjust that, redo the other thing, and then we can talk about payment. Read closely and the list is two different animals wearing one label. A few items are real defects in work you agreed to deliver, and those are yours. Most of the list is new work, things nobody asked for until the invoice arrived, now dressed up as fixes so they ride free and hold the payment up while they do it. Arguing about the list as a whole loses either way: refuse everything and you look like you are dodging defects, do everything and you have taught the client that the invoice is where free scope lives. Sort every item against the original agreement, out loud, in writing. Here is the sort and the reply that follows from it.

See the instrument first: the live demo runs one real call and hands you its verifiable receipt, no signup.

Updated October 31, 2026. First published October 31, 2026. The two delivery records quoted below are real and public, with their client decision states read back from the live service.

Step 1. Get the whole list in writing, one item per line

Nothing gets sorted from a call summary or a sentence like the few things we discussed. Ask for the complete list in one message, each fix as its own numbered item, and say plainly that you will answer every item in writing. This does three jobs at once: it stops the list growing between conversations, it forces vague dissatisfaction into named items that can be checked against the agreement, and it creates the document your reply will mirror line by line. If an item is too vague to check, send it back for specifics before you classify it: which deliverable, what is wrong with it, and what done looks like. A client with real defects can always name them. A client building leverage usually produces a shorter, more honest list the second time they have to write it down.

Step 2. Sort every item into three piles against the agreement

The ruler is the original agreement: the brief, the quote, and the changes both sides accepted in writing while the job ran. Pile one, defect: the agreement required it and the delivered work fails it, it is broken, missing, or wrong against the spec you accepted. Pile one is yours, fixed free, and it is the only pile that was ever a fix. Pile two, preference: the delivered work matches the agreement, and the client wants it different, a different layout, tone, structure, or direction. The work is not wrong, it is no longer what they want, and changing it is new work. Pile three, never mentioned: the item appears nowhere in the agreement or the thread before the invoice. It may be a fine idea. It is still new work, because an agreement is the whole list of what a price buys, and items outside it were never priced. Classify in the open, quoting the agreement line each pile rests on, so the client argues with the document instead of with you.

Step 3. Read the two states the delivery can sit in while you sort

Whether the client already accepted the delivered work changes what a new fix list even is, and acceptance is a state a record shows better than memory does. The record format is AER-1, published as an IETF Internet-Draft (draft-zambo-aer1-26), and each step carries a verifiable receipt: a receipt proves the saved result was not changed since it was saved. The two public records below show the states a delivery can carry:

Accepted: the decision is on the record

Pending: checked, and still waiting on a decision

An accepted record, 4 of 4 steps checked, decided_by client, release_hint ok_to_release, decided 2026-10-16T14:31:51.146Z in that example, means the client side already walked the agreed work and closed it. A fix list that arrives after that acceptance is, by the record's own shape, a request for a new stage after a finished one, apart from genuine defects that surface later and still belong to pile one. A pending record, 5 of 5 steps checked and release_hint hold, means the work is checked and still waiting for its decision, and there the clean order is: sort the list first, clear pile one, get the agreed scope accepted at its agreed price, and only then scope the new items, so the new list never becomes the reason the original job stays undecided forever.

Step 4. Answer in one message, pile by pile, with the invoice standing

Reply once, in writing, in the list's own numbering. Against pile one: the item, the fix, and the date it will be done, no charge, no defensiveness. Against piles two and three: the item, one line on why it sits outside the agreement, and its price as part of a named next stage with its own start condition. Close with the accounting in plain words: the original invoice covers the agreed work, which stands delivered, and it remains due on its original date; the new stage is separate and starts on acceptance of its price. The tone matters as much as the split: cheerful about the defects, factual about the boundary, silent about motives. You are not accusing the client of inventing fixes. You are showing that every item already has a home, a price, or a repair date, and that none of the homes is the unpaid invoice.

Step 5. Fix pile one fast, and record the fixes as their own steps

Your credibility for the whole boundary is the speed and visibility of the defect pile. Fix those items first, before any argument about the rest is fully settled if you can, and deliver the fixes the same way the work was delivered: as steps on the record the client can open, so the fixed state replaces the broken state in the one place both sides look. Then confirm in the thread: pile one complete, items named, check them on the link. Every day a real defect sits unfixed, it works as evidence for the client's framing that the job is not finished. Every defect closed on the record shrinks the hold to its honest size, which is the price of work nobody has agreed yet, and an invoice that was never honestly in dispute.

Step 6. Write the next agreement so the list sorts itself

Three short lines in the next quote end this conversation before it starts. Line one, the definition of the work: the deliverables and the standard they are checked against, in words a fix list can be sorted by. Line two, the defect window: defects against that definition are fixed free for a stated period after acceptance, reported as named items. Line three, the change rule: anything outside the definition is a change, priced and accepted in writing before it is done, and changes never reopen the price or the payment date of work already accepted. Clients who intend to pay for what they order sign this happily, because the same lines protect them from a provider who calls every defect a change. Clients who push back on line three in particular are telling you the post-invoice list was the plan, and that is exactly when you want to hear it.

What a record does not settle

A verifiable receipt proves the saved result was not changed since it was saved; it does not prove whether a disputed item is a defect or a change, and it cannot make a client pay an invoice they are determined to hold. The agreement text, the acceptance state, and your pile-by-pile reply in writing are what the conversation stands on. This page is general information, not legal advice.

Frequently asked questions

My client will not pay until I fix things that were never in the original agreement. What do I do?

Do not argue about the list as a whole. Get every item in writing, numbered, then sort each one against the original agreement: a defect is work the agreement required that the delivery fails, and that pile is yours, fixed free and fast. Everything else, work delivered as agreed that they now want different, and items that appear nowhere in the agreement or the thread before the invoice, is new work, priced as its own next stage. Reply once, pile by pile, with repair dates for the defects and prices for the new items, and state plainly that the original invoice covers the agreed work, stands delivered, and remains due on its date. The sort, done in the open with the agreement quoted, is what separates a real defect claim from payment being used as leverage.

How do I tell a defect from a change when the client insists everything is a fix?

Run two tests on each item. Test one, the agreement test: point at the line in the brief, quote, or accepted change that requires this thing. If no line requires it, it cannot be a defect in the agreed work, however much the client dislikes the result. Test two, the failure test: the agreement requires it, so does the delivered work actually fail it, broken, missing, or measurably off the spec? A defect passes both tests. An item that passes the first and fails the second is a preference, and an item that fails the first is new work. Where an item is genuinely arguable, say which way you are treating it and why, in the reply itself; a boundary you explain item by item holds far better than a blanket refusal or a blanket surrender.

Should I just do the small items on the list to keep the client happy?

At most one, and only if you name it as what it is. A tiny item done silently teaches the exact lesson this page exists to undo: that the invoice is where extra scope goes to get done free. If goodwill is worth it, do the one item and write the sentence in the reply: this one is on me as goodwill, it is not part of the original agreement, and the rest of pile two and three are priced as listed. That sentence keeps the gift a gift instead of a precedent. If the small items keep arriving after the reply, they are not small items anymore, they are a method, and the answer is the priced stage with a start condition, started only when it is accepted.

The client says the work is useless to them until these extra things are done. Does that make them defects?

Not by itself. Usefulness has two different sources. If the agreed work cannot do the job it was agreed to do because of something you got wrong, that is pile one and the fix is yours, even if the client only discovered it late. If the work does the agreed job and the client has a further job in mind, a new audience, a new system it must fit, a new feature the plan grew into, then the extra things are what the next stage is for, and their usefulness to that plan does not move them into the original price. Say which of the two you see, item by item, and be honest when it is the first: owning a real usefulness defect quickly is what earns the boundary on the rest.

How do I set up the next job so a fix list cannot hold the invoice up?

Run the job so the agreement, the delivery, and the acceptance live in one record: the scope as agreed stages, each stage delivered as a handover and accepted or flagged as it closes, so by invoice time what was agreed, what was delivered, and what was decided are the same document. When the work runs through Zambo, every step carries a verifiable receipt under AER-1, published as IETF Internet-Draft draft-zambo-aer1-26, and a fix list can be sorted against that record item by item in minutes. New users get 20 calls and 1 wrap-up free every day, and picking up work in another AI is always free. For $0.99, run the next job that way and sort the next list against a record instead of against memory: get the Day Pass. A Day Pass is unlimited for 24 hours, no subscription. Ongoing use is the Zambo Pass at $29 a month or $290 a year, and $19 a month for $ZAMBO holders, which adds private handover links, your branding, and the approval record as PDF and JSON files.

Related