What proof tool works when my client does not use AI software?

Use a tool whose proof opens in a plain browser. With Zambo, the work is recorded on your side of the connection, and your client receives one handover link: the steps, the results, the source states, and an Accept or Flag decision. No account, no app, no AI software on their side.

Last updated: 2026-10-17

Recipient friction kills more proof than disputes do. If checking your work means installing something, creating an account, or learning a dashboard, most clients will skim your summary instead and pay late while they "review" it. The tool has to meet the client where they already are: a link in an email, opened in the browser they already use.

That is the design constraint behind the handover. You do the technical part once, by running the work through the connection. The client does the human part: read the steps in order, open any step to see its saved result recomputed, note which sources were not checked, and record a decision. The language on the page is delivery language, not engineering language, because the reader is a client, not a developer.

This also protects you. A client who "never got around to checking" has usually been given homework. A client with one link and two buttons has been given a decision, and the record shows the decision state either way: accepted, flagged with a reason, or still pending with the release on hold.

Checklist: the zero-install client test

Before you send proof to a non-technical client, confirm all five: 1. The link opens in a browser with nothing installed. 2. No account or password is asked for at any point. 3. The first screen shows the steps and the decision state without scrolling through settings. 4. Every technical term on the page is either absent or explained in the sentence that uses it. 5. The client can finish with one of two actions: Accept or Flag. If any item fails, the tool is built for you, not for them.

Worked example

Open https://zambo.dev/handover/bd7e5325-33fd-4c5e-b029-76b781fa2f51 the way a client would: a fresh browser, no login. Five steps, their saved results, the source states, and a pending decision with the release on hold. Nothing on that page needs explaining over the phone, which is exactly the point.

Frequently asked questions

My client is not technical at all. Will they understand the check?

The page speaks in steps and results, not in digests and schemas. The underlying check is technical; the reading of it is not. If a client can read an itemized invoice, they can read a handover.

What if the client's company blocks outside links?

Send the handover export as an attachment through the channel they already accept, and keep the link as the checkable original they can open from any network. The export carries the same steps and states.

Does the client need to know the work was AI-assisted?

The record shows the producer label recorded on each step, so AI assistance is visible in the work itself. Most clients care less about the label than about being able to check, which is why the link works.

By Brennan Zambo, founder of Zambo.

Last verified: 2026-10-17.

Send your next delivery as one link your client can open with zero setup: start at https://zambo.dev/demo/ .

Try a handover

A handover gives your client one proof link with verifiable receipts to review, then Accept or Flag.

try it: say 'use zambo to hand this over to <client>' in your ai

Add Zambo · Handover docs · Real public handover · AER-1