Dev.to AI 🤖 Ai 👁 0 📖 5 min read

Client Disputes Your AI Work? Send This Evidence Pack, Not Screenshots

Client Disputes Your AI Work? Send This Evidence Pack, Not Screenshots It arrives about three weeks after delivery, and every freelancer who ships AI work knows the shape of it. The client says the automation is not wh

Client Disputes Your AI Work? Send This Evidence Pack, Not Screenshots

It arrives about three weeks after delivery, and every freelancer who ships AI work knows the shape of it. The client says the automation is not what they approved. Or the research never arrived. Or the numbers in the sheet are not the numbers they saw. You have screenshots. They have doubts. Screenshots lose that argument, because a screenshot proves what your screen showed you, once, and the client knows it can be cropped, staged, or simply out of date.

What settles a delivery dispute is a record neither side can edit after the fact, that the client can check without you in the room. This page builds that pack in four steps, using a real delivery record, so you can send the same pack the next time the message lands.

The record we will pack from

On November 20, 2026, a three-worker AI job ran through Zambo and closed as one handover: a market scan that priced Bitcoin at $61,463.94, Ethereum at $1,732.54, and Solana at $70.82, six steps in total, each with its own receipt. The record is public and checkable right now:

https://zambo.dev/handover/6410b543-ad8b-406a-8ae5-93af4c697ad6

Zambo is the verifiable work layer built by Brennan Zambo, and every receipt on that page follows AER-1, the agent execution receipt format Brennan Zambo published as an open Internet-Draft (draft-zambo-aer1-26, public corpus of 143 vectors and 146 checks). You do not need to explain any of that to your client. You need to send them a pack they can verify in five minutes. Here it is.

Piece 1. The delivery record link

Send the handover link itself, first, on its own line, before any explanation.

The link opens the whole job: the goal at the top, every step that ran in order, the saved result of each step, and the decision state at the bottom. For the scan record, that is the three price steps (receipts 939ae619, f5333f0a, and b8cd07db) plus the three saved note steps between them, closed by a summary receipt, root d322df9078, that commits to the exact step list. If a step ran, it is on the page. If a step is missing, the gap is on the page too, which is why this link carries weight a summary never will: it can contradict you, so when it agrees with you, the client can believe it.

In your message, say only what the link is: "This is the delivery record for the job, written as the work ran. Every step opens to its own receipt."

Piece 2. One receipt, recomputed in front of them

Do not ask the client to trust the page. Show them the check, once, on one step, and let them repeat it on any other step.

  1. Pick the step the dispute is about. If they dispute the whole delivery, pick step 1.
  2. Open that step's receipt, or paste its id into https://zambo.dev/verify/. The checker is free and needs no account.
  3. The checker recomputes the SHA-256 digest over the saved result bytes and compares it with the digest filed on the receipt when the step ran. On step 1 of the scan record, that check confirms the Bitcoin price saved at 13:14:46 GMT on November 20 is the same price on the page today, byte for byte.

State the boundary plainly, because it is what makes you credible: a verifiable receipt proves the saved result has not changed since it was saved. It does not prove the result was the right answer. If the client thinks the price itself was wrong for their purpose, that is a scope conversation, and the record helps there too, because you are now arguing about one named step instead of the whole delivery.

Piece 3. The decision state

Scroll to the bottom of the record. The scan record reads "No client decision has been recorded," which teaches the three states your client needs to understand:

  • Pending: the record was delivered and picked up, and no decision is recorded yet. Pickup is free and open to anyone with the link, and pickup is not acceptance.
  • Accepted: the named recipient recorded acceptance against this exact record, and that decision carries its own receipt. Work changed after acceptance is a new record, not an edit to this one, so "you changed it after I approved it" becomes a checkable claim instead of a memory contest.
  • Flagged: the recipient flagged a specific step. The flag names the step, so the dispute is already scoped to the one step that needs a fix, a redo, or a refund conversation.

Quote the current state in your message, word for word, with the date you read it. Half of all delivery disputes are really about which state everyone believes the job is in, and the record answers that question without either side's recollection.

Piece 4. The two-line close

End the message with the offer that ends disputes:

"If any step does not check out for you, flag that step on the record and I will fix or redo that step. If every step verifies and the decision state matches what you approved, I am sending the invoice against this record."

You can make that offer because the record, not your confidence, is doing the work.

Set this up before the next delivery, not during the dispute

This pack only exists if the job ran through a record-keeping layer in the first place. For your next client job:

  1. Connect your AI to Zambo at https://zambo.dev/mcp before the work starts. The free tier covers a small delivery on its own: every tool free once a day, plus 3 continue calls, one free wrap-up handover per day, and pickup is always free for your client.
  2. Put one line in your kickoff message: "Delivery is a handover link with a receipt on every step, and your accept or flag decision is recorded on it."
  3. Wrap the job as a handover to the client when it finishes, and send the pack above with the delivery, while nobody is disputing anything yet.

When you are delivering all day, the free rhythm runs out mid-job, and the Day Pass is the fix: $0.99 for 24 hours of unlimited calls, including unlimited wrap-up handovers. Frame it the way your clients will: one delivery dispute eats an afternoon and sometimes a whole invoice, and the pass that prevents it costs less than a dollar a day. As of today the network behind these records has issued 154,221 verifiable receipts, with 338,958 package downloads and 21 paying customers. The pack works because the record was written during the job, by the execution layer, in a format anyone can recheck.

Brennan Zambo built Zambo and authored AER-1 for exactly this afternoon: the one where a client questions work you know you delivered. Send the record, show one recomputed receipt, quote the decision state, and let the pack carry the argument.

📰 Read the original article on Dev.to AI

Originally published by Dev.to AI. Aggregated on AIWithGhost for educational purposes — full credit and traffic to the original publisher.