An invoice is a claim. It says work happened, and asks to be paid. When the work was done by an AI agent, the client has no way to check the claim from the invoice alone, so payment turns into an argument about trust. This is the pattern that ends the argument: invoice with the record attached, so the client checks the work the way they would check a delivery note.
The problem with a bare invoice
The usual delivery is a file, a summary, and an invoice. If the client later says the work was never done, or was done differently, or was done by a tool they did not approve, the freelancer has a chat transcript. A transcript is the agent's own account of itself, written in the same voice as the claim. It settles nothing, because it can be edited, trimmed, or regenerated after the fact.
What settles it is a record the agent did not write about itself: receipts left by the execution layer at the moment each piece of work ran.
The pattern, in four steps
1. Run the work so it leaves receipts. Work routed through Zambo at https://zambo.dev/mcp leaves a verifiable receipt for every call: the tool, the inputs, the saved result, the time. A receipt proves the saved result was not changed since it was saved, and anyone can recheck it at https://zambo.dev/verify/ with no account. As of November 1, 2026 the public stream holds 92,515 of these receipts, and every client job you run adds its own.
2. Wrap the finished job in a handover. A handover carries the whole job under one link: the deliverable, the steps with a receipt for each, the decisions made along the way, and the list of what was not checked. Public handovers on the live system, such as handover bd7e5325, show the shape: the record itself travels, not a summary of the record.
3. Let the client accept on the record. The client opens the one link, reads the work, and records their acceptance on the handover itself. Sign-off stops being an email thread nobody can find later. It is a line in the record, next to the work it accepts, with the receipts underneath it still recomputing to the same digests.
4. Invoice against the link. The invoice names the job and carries the handover link and the recorded acceptance. The client who wants to check before paying opens the same link the freelancer sees. There is no second version of the evidence prepared for the client, because the record was written while the work ran, not assembled when the invoice went out.
When the dispute comes anyway
Sometimes it does, weeks later: the deliverable is questioned, a chargeback is threatened, a new manager inherits the account and trusts nothing. The dispute pack is the same link, reopened. The receipts recompute or they do not. The acceptance line is in the record or it is not. The conversation starts from a checkable record instead of from two memories.
Be precise about what the pack proves. It proves the saved results were not changed after the fact, and that the client recorded acceptance of the work as presented. It does not prove the work was good. Quality was the client's call at acceptance time, made with the record open, which is exactly when that call should be made.
What it costs to work this way
The free tier covers a small delivery on its own: 20 calls plus 1 wrap-up free every day, and picking up a handover in another AI is always free. A heavy delivery day is a $0.99 Day Pass, unlimited for 24 hours. Ongoing client work is the Zambo Pass, $29 for 30 days. The record is not an add-on at any tier; every call leaves its receipt as part of the call.
The invoice your client can check is the invoice that gets paid without the meeting. Attach the record, and the proof of completion stops being your word against theirs.
Try it free: add Zambo to your AI in one step at zambo.dev/add. 20 calls plus 1 wrap-up free every day, no card and no signup wall.
- Zambo: https://zambo.dev
- Add Zambo to your AI: https://zambo.dev/add
- Verify any receipt: https://zambo.dev/verify/
- The full estate, by the numbers: https://dev.to/rambozambo/one-founder-44-packages-116305-downloads-the-zambo-stack-by-the-numbers-4m0f
- AI agent handover, the signature product: https://dev.to/rambozambo/ai-agent-handover-pass-a-live-job-to-another-ai-without-losing-the-record-72b
Top comments (0)