TALECRAFTERS
← All posts
METHODBUYINGETHICS

What to Tell a Client About AI in the Pitch

Konstantinos Chatzimichail3 min read
METHOD

Disclose which stages used generative tools, what the client owns, who is accountable for the output, and how the saving is shared. Clients are asking all four. A studio that answers them unprompted is easier to buy from than one that waits to be asked.

A few years ago the awkward question was whether you used generative tools at all. It stopped being awkward because almost everybody does, somewhere — previsualisation, versioning, asset preparation, clean-up, localisation. The question that replaced it is sharper and better: who is capturing the efficiency, and what am I actually buying.

The four questions procurement asks now

THE QUESTIONWHAT IT MEANSA GOOD ANSWER
"Where in this process is AI used?"Am I paying craft rates for automated steps?A stage-by-stage list. Not a policy statement — a list.
"What do we own at the end?"Can we continue this without you?Assets, project files, lock file, consent files, input schedule.
"Who is accountable if it is wrong?"Is there a human signature on this?A named person, at named checkpoints, at any volume.
"Are we getting the saving?"Has the price moved with the cost?An honest account of where the cost went, because it moved rather than vanished.
What they ask, what they mean, and what a good answer contains

The fourth is the one studios fear and the one worth meeting head-on, because the true answer is more interesting than the evasion. The cost did not disappear; it moved from shooting to writing, rights, review and systems. A client who understands that is buying the right thing. A client who is told nothing assumes the saving was pocketed, and they are sometimes correct.

What to put in the pitch, unprompted

  1. A stage map with the method against each stage: filmed, generated, hybrid, automated, or human-only. One page.
  2. What is human at every volume: the brief, the structure, the creative decisions, the final sign-off.
  3. The deliverable specification, including what makes the work continuable without you.
  4. The disclosure position for the finished work, decided now rather than at delivery, to the strictest of platform policy, advertising code and applicable law.
  5. The consent position for anybody appearing in it.
  6. Where the budget actually goes, as a proportion. This single slide changes more pitch conversations than any showreel.

What not to do

  • Do not present a generated frame as filmed. It will be found out, and the cost is the relationship rather than the frame.
  • Do not board at a fidelity you cannot deliver. A photoreal board for an uncertain shot is a promise somebody will hold you to.
  • Do not quote a traditional rate for an automated stage and hope nobody asks. They now ask.
  • Do not treat disclosure as the client’s problem. Legal responsibility usually sits with the advertiser, and a studio that will not advise on it has not read the rules.
  • Do not claim the work is entirely human when it is not. This is the one that ends relationships, and it is entirely avoidable.

When the client does not want AI used

Some do not, for reasons ranging from brand positioning to talent agreements to their own client’s policy. That is a legitimate constraint and it should be taken at face value rather than argued with.

What it needs is precision, because "no AI" means different things to different people. Does it exclude generative imagery in the final asset? Generative previz that nobody sees? Automated versioning? Machine transcription? Upscaling? Most people mean the first and are surprised to learn how much of the last four is already standard in every post house they have ever used.

Write the boundary down, in the brief, in specific terms, and price against it. A constraint that everybody understands is workable. A constraint nobody defined is a dispute waiting for a delivery date.

Where the method, the locks, the disclosure position and the deliverable specification sit, before any of this becomes a conversation about trust.

THE BRIEF TEMPLATE

Questions people actually ask

Should you tell clients you used AI?

Yes, unprompted, as a stage-by-stage list rather than a policy statement. Almost every production uses generative tools somewhere now, so the question is not whether but where — and a studio that answers before being asked is easier to buy from.

What do clients actually want to know about AI use?

Four things: which stages used it, what they own at the end, who is accountable if something is wrong, and whether the price moved with the cost. The fourth is the one studios avoid and the one worth meeting directly.

Did generative tools make production cheaper?

They compressed the expensive invisible parts — previsualisation, versioning, asset preparation, clean-up. They did not compress writing, structure, rights, review or accountability, which is what a client is actually paying for. The cost moved rather than vanished.

What should you never do when pitching generative work?

Present a generated frame as filmed, board at a fidelity you cannot deliver, quote traditional rates for automated stages, treat disclosure as purely the client’s problem, or claim the work is entirely human when it is not. The last ends relationships and is entirely avoidable.

What if a client says they do not want AI used at all?

Take it at face value and then make it precise, because "no AI" means different things to different people — generative imagery in the final asset, previz nobody sees, automated versioning, machine transcription and upscaling are very different things. Write the boundary into the brief in specific terms and price against it.

WRITTEN BY

Konstantinos Chatzimichail
FOUNDER AND CREATIVE DIRECTOR, TALECRAFTERS

Founder of TaleCrafters. Writes the pipelines the studio works to, directs the films that come out of them, and publishes both.

More from Konstantinos

TERMS USED HERE

TAKE THE TOOL WITH YOU

READ NEXT