My client rejected the AI work I delivered. What do I do?
Answer in three moves. Review the receipt and actual deliverable before accepting a handover.
A rejection feels like one event; it is usually two. The client may be saying the work missed the brief, which is a factual claim with a checkable answer, or that they dislike the result, which is a preference with a commercial answer. Treating them as one conversation produces the classic spiral: endless revisions performed under a payment threat.
The record separates them. Against the brief, the handover shows the steps as delivered: the research with its source states, the drafts, your edits. If a requirement was missed, the record shows that too, and the honest move is to fix that item promptly and visibly, as a new step, and let the fix itself demonstrate your process. If the brief was met, the record is your reply: not "trust me," but "here is the work, step by step, against the requirements you set."
Then the commercial move: name one bounded revision path in writing, what it covers, how many rounds, and what it costs if it exceeds the brief. Taste revisions are legitimate work; they are simply new work, priced as such, and recorded the same way. The reply sequence below keeps the order right: record first, revision offer second, payment third, each in its own short message.
Template: the rejection reply sequence
Message 1 (the record): "Here is the delivery record for [job]: [handover link]. Against the brief, the steps are: [requirement, step]. Tell me which requirement you read differently, and I will answer that item directly." Message 2 (the fix or the path): if a requirement was missed: "You are right on [item]; the corrected version is step [n] in the same record." If taste: "For changes beyond the brief, I can do [scope] in [one] revision round by [date] at [price or included]." Message 3 (payment, separate thread): "The invoice for the delivered work stands as agreed; the revision, if you want it, is quoted above."
Worked example
The record message 1 points at is shaped like the public handovers in this section: https://zambo.dev/handover/508a46e2-8d6e-4099-bd12-7ae461c72c55 shows a four-step job a client can read in minutes. A rejection answered with an object like this moves the argument from impressions to items, which is where freelancers win.
Frequently asked questions
The client rejected the work without naming anything specific. What then?
Ask for the item, using the record: "Which requirement in the brief does the delivery miss?" A rejection that cannot name an item is a taste or budget conversation, and it should be priced and scheduled as one.
Should I revise first and argue later to keep the relationship?
Fix a genuinely missed requirement immediately; that builds the relationship. Open-ended taste revisions before the delivered work is settled usually buy neither goodwill nor payment, and the record of the spiral helps no one.
The client says the AI made it, so it is worth less. How do I answer?
With the record's division of labour: the steps show what the AI produced and what you did, reviewed, and stand behind. The contract priced the outcome and the accountability, both of which the record documents.
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