The Client Proof Pack, Team Edition: Every Hand on the Job, One Link for the Client

The dispute always sounds the same. The invoice says the work was done. The client says their guy looked and could not find half of it. Your team knows the work happened, because three of you touched it: one person scoped it with an agent, another ran the build steps across two sessions, a third checked the deliverable and sent it. The proof, such as it is, lives in three chat histories, one of which rolled off when a session hit its limit in week two.

A solo operator can sometimes reconstruct that. A team cannot, because the record was never one record. This is the team version of the client proof pack: not a folder you assemble when the dispute arrives, but a job structure you run from day one so the pack exists before anyone asks for it.

The roles, and what each one leaves behind

The builder runs the work. Every step their agent takes goes through one endpoint, https://zambo.dev/mcp, so every call lands as an AER-1 receipt the moment it returns: caller, tool, saved result, timestamp, sequence position, and a SHA-256 commitment over the result bytes. The builder's discipline is one sentence long: if a step is not in the job, it did not happen.

The checker is a different person, and that is the point. The checker does not read the builder's summary. The checker opens the job's receipt chain, picks the steps the invoice will rest on, and recomputes their digests. A step that verifies becomes a line the firm can defend. A step that is missing shows as a gap in the sequence while there is still time to run it, not during the dispute.

The sender owns the handoffs. When the job moves, between teammates, between shifts, between the AI the builder started in and the one the checker prefers, it moves as a handover: goal, summary, named recipient, next steps. Pickup is always free. The sender's rule is the mirror of the builder's: a handoff that is not in the record is a rumor the next person has to re-verify by hand.

A pack, sealed this morning

Here is the pack's smallest working unit, run this morning as a sample job: two recorded reference values under a single job, sealed when the job closed. I ran both steps myself for this sample. In a live client job these same two steps would sit in the chain beside the builder's work steps and the checker's recomputations, in sequence, under the same root. Step one saved the BTC reference value, $74,712.00 at the moment it was recorded:

https://zambo.dev/run/cea2a213-3435-4fae-8654-0efed604346d

Step two saved the ETH reference value, $2,112.10:

https://zambo.dev/run/ec29d90a-aff1-43a7-93d0-cf257a3a0f78

And the job sealed into its proof page, the single link that travels with the invoice:

https://zambo.dev/workflow/f28765d5-b8c4-4204-b653-2d8a4bcbe9a4

Open the proof page. Two steps, in sequence, under one root commitment. Open either step and the value that was saved sits on the receipt itself, under its digest, recomputable by the client with no account and no help from us. Rates move after the fact. A saved value stays the value it was at recording time, and the digest is how the client confirms nobody repriced it later. That is the whole pack at job scale. Month end is the same move with more jobs: one link per job, listed on or under the invoice, each chain sealed when its job closed.

The dispute, replayed with a pack

Week six. The client writes back: our reviewer cannot find the rate recordings behind the report, please justify those line items. Without a pack, your week becomes archaeology across three people's sessions. With a pack, the reply is one link per job on the invoice and one sentence: every step behind this invoice is listed in order, each result is sealed, recompute any of them. The existence argument ends there. What the work was worth is still a conversation, but it is a conversation over a record both sides can read, not over your team's memory, your agent's summary, or your firm's good name. The math is either right or it is not, and they can run it themselves.

Notice what the pack does not claim. A receipt proves the saved result was not changed after it was saved. It does not prove the work was good, and a team that ships sloppy work under perfect receipts has simply documented the sloppiness beautifully. The pack answers the question disputes are actually about, which is whether the work on the invoice is the work that ran. Quality is your firm's name. Existence is the receipt's.

What it costs to run this way

The structure rides on the normal ladder: 20 calls plus one wrap-up free every day to start, pickup always free, a $0.99 Day Pass for an unlimited day, the Pass at $29 for 30 days ($19 for $ZAMBO holders), Lifetime at $250 once. One defended invoice pays for years of it. The real cost is the first week of discipline, builders keeping every step inside the job, and after that week the pack stops being a practice and becomes a byproduct. The work was going to run anyway. Now it leaves the record behind as it goes.

Your AI said it did the work, and this time three people and two models touched it before the client ever saw it. Send the receipt.