Direct answer
Is there a tool that gives my client a link to check AI work before they pay?
Yes: a Zambo handover. The job's steps roll into one page behind a single link. Your client opens it in a browser, reads each step with its saved result, checks any step's verifiable receipt, and clicks Accept or Flag. The decision is recorded on the page, so the check happens before the payment.
By Brennan Zambo, creator of Zambo. Updated October 17, 2026.
What your client sees
The link opens a plain page, no account, no install, no AI tool on their side. The job is listed step by step in the order it ran: what each step did, what it produced, and the source states behind it, marked resolved, not resolved, or not checked, so gaps are visible instead of hidden. Every step carries its verifiable AER-1 receipt, and the client can run the receipt's check from the page: the format is IETF Internet-Draft draft-zambo-aer1-23, a public procedure their own tools could recompute too. Any single receipt can also be checked on its own at zambo.dev/verify. At the bottom sit the two buttons that matter: Accept, or Flag with a reason.
What is in the packet
The brief: what the job was, as agreed.
The steps: every step that ran, in order, each with its saved result.
The receipts: one verifiable AER-1 receipt per step, checkable from the page.
The sources: each source marked resolved, not resolved, or not checked.
The decision: Accept or Flag, with who decided and when, recorded on the same page.
A real one is public: handover 45434a17 on zambo.dev shows four steps, all in checked state, and a client decision of accepted with ok_to_release, recorded on the page the client opened. That is the whole packet: no attachment, no walkthrough call, nothing to install.
How it becomes the payment gate
Send the handover link with the delivery, before the invoice conversation starts. The agreement writes itself: the client checks the record, Accept records their decision with their name and the time, and payment follows a decision that exists in writing. If they Flag a step instead, you learn exactly which step and why, while the rest of the job stands accepted around it. Compare that with the usual sequence, a delivery email, silence, a chase, a call, and the proof fight this page exists to skip. The sibling page on this hub covers the client's side of the same moment: my client won't pay until they can check the work.
What Accept and Flag each record
Accept closes the job into a summary receipt: the steps, the decision, who made it, and when, in one record both sides can point to later. Flag keeps the job open and names the step in question, so the fix is a step, not a restart. Either way the decision lives on the record, not in an email thread one side can lose. Work you hand over this way also builds the habit that protects the next job: the proof-before-payment page lays out the full loop.
The honest part
The handover proves the steps that ran through the connection and that their saved results were not changed afterwards. It does not prove the work was good, and steps done outside the connection are not in it. A client can still reject work on quality; what they cannot honestly do is claim the work never happened, or that the record changed after they saw it.
Frequently asked questions
Is there a tool that gives my client a link to check AI work before they pay?
Yes. On Zambo the job's steps roll into a handover behind one link. Your client opens it in a browser with no account, reads each step and its saved result, checks any step's verifiable AER-1 receipt from the page, and records Accept or Flag on the same page. Send the link with the delivery and the check happens before payment, as a recorded decision instead of an email argument.
Does my client need an account or an AI tool?
No. The handover is a web page. Your client needs a browser and the link, nothing else: no Zambo account, no AI subscription, no install. That is deliberate, because verification that requires the client to adopt your tools dies on friction. The receipt checks run in the browser, and Accept and Flag are buttons on the page.
What happens when a client flags a step?
The flag is recorded on the handover with the step it names and the reason the client gives, and the job stays open instead of accepted. You fix that step, its new run adds its own receipt to the record, and the client re-checks the same page. The rest of the job, and the fact that it was checked, stays exactly as it was.
Can the client check the receipts themselves, or do they trust the page?
They check the receipts themselves. Each receipt's verification recomputes the commitment over the step's saved fields in the browser, and the AER-1 format is published as an IETF Internet-Draft, draft-zambo-aer1-23, so the procedure does not depend on Zambo's word. If a saved result had been changed after the fact, the recomputation would not match, for the client exactly as for you.
What does it cost to send a check link?
The record behind the link is free to start: calls on the free tier write their receipts at no charge, up to 20 free calls per metered tool per day. A heavy delivery day costs a $0.99 Day Pass, one time. Private, branded handover links with PDF and JSON export come with the Zambo Pass at $29 a month. The client never pays anything to check.
Your AI said "done." For $0.99, prove it: https://zambo.dev/day-pass/
The main site answers the tool search directly: a tool that gives my client a link to check AI work before they pay, and what the client can inspect on that link.