Client Cancels an AI Project Halfway: What to Do

A client cancels an AI project halfway and three separate things are now at stake: the money you are owed, who owns the work already built, and whether this person ever refers you again. They get resolved on different timelines and by different means, and the mistake almost everyone makes is trying to settle all three in the same reply.

Handle them in that order, and do the first one within 48 hours.

Hour one: do nothing except acknowledge

Reply, confirm receipt, say you will come back with a summary of where things stand and what is outstanding. Nothing else. No arguing the decision, no discount offer, no request for a reason.

This is not politeness for its own sake. The email that arrives an hour after a cancellation is written by someone who has already had the internal conversation and is bracing for a fight. Not giving them one changes the tone of everything that follows, and it buys you a day to look at the contract before you say anything you cannot walk back.

Day one: reconstruct what is actually owed

Open the agreement and find these four things. If any of them are missing, that gap is the lesson for the next contract.

• The termination clause, and whether it requires notice or payment for work in progress.

• The payment schedule, and which milestones have been invoiced against which have been delivered.

• Any deposit or retainer, and whether it was defined as non-refundable.

• The acceptance mechanism, meaning how a milestone was supposed to be signed off. Silence often counts as acceptance after a stated window, and clients frequently do not realise this.

Then write the position note. One page, no adjectives: work delivered, work in progress, amounts invoiced, amounts paid, amount outstanding. Send it as a factual statement of position, not a demand.

Most disputes at this size settle at this step, because the client's mental model of what they owe is usually built on what they can see rather than what was agreed, and a clear ledger corrects that without an argument.

If they simply do not pay, know your baseline before you escalate. Under the EU Late Payment Directive, where a B2B contract sets no payment date, interest becomes payable 30 days after the invoice is received, the statutory rate is at least eight percentage points above the ECB reference rate, and creditors are entitled to a minimum EUR 40 in recovery compensation. Equivalent rules exist in most jurisdictions. You are not being aggressive by mentioning them; you are stating the default the law already set.

Day two: the handover question nobody planned for

Here is where AI projects differ from ordinary ones, and where most standard contracts are quiet.

On a hand-written project, "the code" is the deliverable and ownership follows the contract. On an AI-built project, the asset set is wider and much of it never appeared in a statement of work:

• The prompts and system instructions that make the thing work.

• Evaluation sets, test fixtures, and the examples you tuned against.

• Fine-tuned artifacts or configuration that only make sense with your data.

• Any agent instructions, tool definitions, or scaffolding files.

If the contract assigns "all deliverables" on full payment, decide what you consider a deliverable and say so explicitly, in writing, now. If it says nothing, the default in most jurisdictions is that the creator retains rights until assignment happens, and assignment usually depends on payment.

Two practical rules. Do not hand over anything before the outstanding invoice clears, and do not delete anything either. Deleting looks like retaliation even when it was routine cleanup, and it converts a payment dispute into a much uglier conversation. Archive, freeze, and say you have done so. Our post on who owns AI generated code covers the underlying rights question in more depth.

Week one: work out why the client cancelled

Cancellations come in three flavours and they deserve different endings.

Budget. The project was fine, the money vanished. This client is a warm lead in nine months. Close cleanly, offer to archive the work in a resumable state, ask to be told when budget returns. Say it once and then leave them alone.

Scope. They wanted something other than what was being built. Worth one honest post-mortem, because the failure was usually in the proposal rather than the build, and you can fix that for every future client. Our guide to handling scope creep on an AI project covers the earlier intervention point.

Trust. They stopped believing the work would land. This is the one worth being honest with yourself about. Sometimes it is unreasonable, and sometimes the demos really were thin. Either way, the fix is structural: shorter milestones, earlier working software, no gap longer than two weeks without something the client can click.

What to change before the next contract

Three clauses, and they take an afternoon to add:

1. A kill fee. A stated percentage of the remaining contract value payable on cancellation without cause. It is standard in agency work and almost absent from solo AI contracts.

2. A named list of deliverables that includes AI artifacts. Prompts, evals, and configuration by name, not implied under "code".

3. A shorter milestone cadence. Two weeks maximum. Long milestones concentrate cancellation risk into single large unpaid chunks.

None of that prevents a cancellation. All of it means the next one costs you a fortnight instead of a quarter. If you are rewriting your paperwork anyway, our AI project proposal guide is the natural companion piece.

The deeper protection is not contractual at all. A business whose revenue is one large project at a time is one cancellation away from a bad quarter, which is the real argument for the mixed revenue models in our overview of ways to make money with AI.

FAQ

Can I keep the deposit if the client cancels?

If the contract defined it as non-refundable, usually yes. If it did not, a deposit is generally treated as payment on account, which means it offsets work actually done rather than being retained automatically.

Should I offer a discount to save the project?

Rarely. A discount answers a price objection, and cancellations are almost never price objections. If the real cause is scope or trust, cutting your rate makes the same project worse.

Do I have to hand over the prompts?

That depends on whether they were named as deliverables and whether assignment was conditional on payment. Where the contract is silent, prompts and evals are frequently not covered by a clause written for code, which is exactly why the next contract should name them.

How do I avoid this next time?

Shorter milestones, a kill fee, and a paid pilot before any large engagement. The pilot in particular filters out clients who were never going to finish, which is covered in how to run a paid pilot for an AI project.