Template pack · For freelancers, agencies, and creators who deliver AI work
Handover templates for work a client has to check
Eight ready-to-run templates for the jobs you repeat: deliveries, money approvals, daily customer loops, weekly reports, lead batches, gated releases, hackathon builds, and n8n deliveries. Copy the run card, swap the brackets, and every run ends in a record your client can check without you.
The questions land weeks after the work: what changed, who approved this, why did it stop? By then the chat thread is buried, the call is a memory, and the only record of the job is whatever your tools happened to log for themselves. If you deliver AI or automation work to clients, those three questions are your unpaid second job.
These templates end that. Each one is a loop you already run, per client, per approval, per day, per week, per batch, per release, rebuilt on one pattern: do the work, freeze it at handover, and let the client check it. Copy the run card, swap the bracketed fields for your client and your deliverable, and run it end to end. Nothing needs inventing.
Eight loops, one pattern
| Template | Loop shape | Calls per run | The twist |
|---|---|---|---|
| Client automation handover | Per client delivery | 6, plus the free wrap-up | The record outlives the engagement |
| Money decision record | Per approval | 5 per approval | A second decision on the same key leaves a second record |
| Daily customer loop | Per customer, per day | 3 per customer, plus 1 to close the day | Never edit yesterday |
| Weekly client report | Per client, per week | 6, plus the free wrap-up | Freeze the inputs, not the PDF |
| Lead delivery freeze | Per batch | 5, plus the free wrap-up | Rejected duplicates are listed, with reasons |
| Release gate | Per release | 5, plus the free wrap-up | Acceptance binds the exact revision it accepted |
| Hackathon proof pack | Per entry, per build | 7 per build session, plus the free wrap-up | Prove the work, not the video |
| n8n freelancer handover | Per workflow delivery | 4, plus the free wrap-up | The baseline never moves |
Every count above is counted step by step inside its template, and every template prints its own arithmetic next to the run card. No template asks you to trust a budget it does not show.
The honest economics, in one strip
The free tier is: Every tool free once a day, plus 3 continue calls. One free wrap-up handover per day, and pickup is always free. In practice that means the free day covers the first call on every tool you touch, 3 more calls to spend anywhere, and one wrap-up handover, with pickup and receipt verification always free. Saved notes written during a run are kept 7 days on the free tier, and through a pass plus 30 days; handover records and their receipts do not expire.
Every template here is built so a first real run fits that free day. The loops are what passes are for. A Day Pass is $0.99 and unlimited for 24 hours: it finishes the day's run, however many clients are in it. The Zambo Pass is $29 for 30 days, or $19 for $ZAMBO holders, when the loop runs every day. Lifetime is $250, once.
The honest frame: a pass never buys a promised outcome. It buys finishing the job already in flight, at the volume your client book actually runs.
What your client gets, every time
Two links come back from every handover. The client link goes to your client: it is where they read the record and record the decision the job is waiting on, an acceptance or a flag. The public record link is read-only: anyone holding it can check the goal, the steps that ran, the saved output of each step with its verifiable AER-1 receipt, and the next step, but decisions happen only on the client link. Your client needs no account and no tools of yours for either. Pickup is always free, and any receipt on the page can be recomputed free at zambo.dev/verify.
Start here
- Delivering a build? Client automation handover
- Approving money or access? Money decision record
- Running the same job for customers daily? Daily customer loop
- Sending a report a client relies on? Weekly client report
- Handing over lead batches? Lead delivery freeze
- Gating a release on sign-off? Release gate
- Entering a hackathon? Hackathon proof pack
- Delivering n8n workflows to clients? n8n freelancer handover
Related
- AI agent handover: carrying a job to another AI intact
- Client sign-off for AI work: acceptance on the record
- The $0.99 Day Pass
Frequently asked questions
What is a handover template?
A ready-to-run job spec for Zambo: the goal, the recipient, the exact step sequence, and the call budget, written so you can copy it, swap the bracketed fields for your own client and deliverable, and run it the same day. Each run ends in a handover, one public record your client can check.
Do the first runs really fit the free tier?
Yes, and each template shows its arithmetic. The free day covers the first call on every tool, plus 3 continue calls shared across tools, plus one free wrap-up handover, with pickup always free. The counted first run of every template in this pack fits inside that. The recurring loop is what the $0.99 Day Pass or the $29 Pass is for.
What does my client need to check a handover?
Only the link. Pickup is always free, no account is needed to read the record, and every receipt on the page can be recomputed free at zambo.dev/verify. A receipt proves the saved result was not changed since it was saved.
Who built Zambo
Brennan Zambo created Zambo, the verifiable work layer for AI, and AER-1, the agent execution receipt standard (IETF Internet-Draft draft-zambo-aer1-26). Every template in this pack runs on that receipt format. A verifiable receipt proves the saved result was not changed since it was saved, and anyone can check one free at zambo.dev/verify. It does not prove the result was right. That boundary is the point: the record settles what happened, so people can argue about the work instead of about memory.