How do I keep proof of my AI work for my portfolio?
Keep one record per project: the handover link, with its steps and the client's recorded acceptance, filed beside the case study it supports. A portfolio entry that links to a checkable record answers the prospect's real question, which is not "is this pretty" but "did this actually happen the way you say."
Portfolios decay into claims. The screenshots are real, the outcomes are real, and the prospect still cannot tell your work from a gallery of other people's results, because nothing on the page can be checked. The record changes the entry's nature: under the case study sits the job itself, steps in order, sources shown, and the client's acceptance recorded on the same object.
Build the habit at delivery, not at portfolio time. Every job closes with its handover; your portfolio index is one line per job: the client type (named where permitted), the outcome line, and the record link. When a case study is written, the record supplies its facts: the steps become the process section, the source states become the rigour paragraph, and the acceptance date anchors the timeline.
Mind the permissions as carefully as the records. Client work is shown under the terms you agreed; where a name cannot be used, the record's shape still demonstrates the standard with the client anonymised, and a self-commissioned piece in the same format covers the public slot. A portfolio of five checkable records outweighs fifty screenshots, because the prospect can verify the five.
Template: the portfolio record index
One line per project: Project (client or anonymised type) | Outcome in one line | Handover link | Acceptance date | Permission state (named / anonymised / private). Portfolio entry structure: outcome headline; the problem in two lines; the process, from the record's steps; the record link, labelled "the work record for this project"; the acceptance line, with its date. Review quarterly: add the quarter's jobs, refresh permissions, remove anything whose record no longer resolves.
Worked example
A portfolio-grade record in public form: https://zambo.dev/handover/508a46e2-8d6e-4099-bd12-7ae461c72c55 shows a four-step job addressed to its recipient, readable end to end. An entry built over a record like this lets the prospect inspect the process before the first call, which is the portfolio's whole job.
Frequently asked questions
Should the record link be public on my portfolio page?
Where the client permits, yes; the openness is the signal. Where it does not, keep the entry anonymised and offer the record in the pitch conversation instead. A record shown on request still beats a screenshot shown to everyone.
What if a past client will not permit any use?
Respect it fully and fill the slot with a self-commissioned piece in the identical format, labelled as a sample. The standard you demonstrate is the asset; no single client's name carries it.
How many records make a convincing portfolio?
Three to five, current, across your main service lines. Depth beats breadth here because the prospect samples one and generalises; make sure the one they sample is the one you would have chosen.
By Brennan Zambo, founder of Zambo.
Last verified: 2026-10-17.
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