AI Automation Contract Template (Scope, Data, and the Clauses AI Work Actually Needs)
A general freelance contract misses the things that go wrong on AI projects: who pays for API usage, who owns the prompts, what happens when the model gets something wrong, and where the client's data goes. The clauses below add exactly that protection without turning into a wall of legalese. Copy it, adapt it, and have it signed before you build.
The Example
1. The work. The Contractor will build and deliver: [the automation — e.g. “an AI support assistant with Slack handoff, as scoped in the proposal dated [date]”]. Anything not listed there is out of scope and quoted separately.
2. Out of scope. New channels, additional integrations, and prompt or workflow changes requested after acceptance are handled as separate quoted work, not free revisions.
3. Third-party services & costs. The automation relies on third-party AI providers [e.g. Anthropic, OpenAI]. Their usage fees are the Client's responsibility, billed at cost. The Contractor isn't liable for third-party outages, price changes, or model changes outside their control.
4. AI output & accuracy. AI-generated output can be imperfect. The Contractor will test and tune to an agreed standard, but does not warrant that output is error-free. The Client is responsible for human oversight of [high-stakes actions — e.g. sending refunds, legal or medical replies].
5. Data handling. The Client's data is used only to build and run the automation. It is not used to train third-party models beyond what the chosen provider's business terms allow, and is deleted on request within [30 days] of the agreement ending.
6. Payment. Setup fee: [amount], as a [50%] deposit before work begins and the balance at launch. Monthly retainer: [amount], billed [monthly in advance]. Invoices due within [7 days]; late balances accrue [1.5%] per month.
7. Ownership. On full payment of the setup fee, the custom workflows and prompts created for the Client transfer to the Client. The Contractor keeps their own pre-existing tools and general methods.
8. Maintenance & ending. The retainer covers monitoring and minor changes. Either party may end the retainer with [14 days] written notice; the Client pays for work and the retainer period completed to that point. The deposit is non-refundable.
Signatures
Contractor: ______________ Date: ______
Client: ______________ Date: ______
Why These Clauses Matter
- Scope + a separate out-of-scope clause is your single best defence against the “can it also just…” that makes AI projects unprofitable.
- Passing API costs to the client keeps your margin clean and protects you from a provider's price hike quietly eating your retainer.
- The no-warranty-on-output clause is specific to AI work — it sets a realistic standard and puts human oversight of high-stakes actions where it belongs.
- A data-handling clause is what serious clients (and their lawyers) look for — say plainly what you do with their data and when it's deleted.
- IP that transfers on payment — the custom prompts and workflows are the Client's once paid; your general toolkit stays yours.
Pair this with the AI automation proposal template and the pricing guide so the numbers in your contract match the ones you pitched.
Frequently Asked Questions
What extra clauses does an AI automation contract need?
Beyond a standard freelance contract: an out-of-scope clause, third-party API cost pass-through, a no-warranty-on-AI-output clause with human oversight, a data-handling clause, and a maintenance retainer.
Who pays for the AI API costs?
Usually the client, billed at cost. State it in the contract so a provider's price change doesn't quietly erode your retainer margin.
Who owns the prompts and workflows I build?
Typically the client, on full payment of the setup fee — for the custom work built for them. You keep your own pre-existing tools and general methods.
Am I liable if the AI gives a wrong answer?
A no-warranty-on-output clause sets a realistic standard: you tune to an agreed quality bar, and the client keeps human oversight of high-stakes actions. Have a lawyer confirm the wording for your jurisdiction.
Send It Signed in Minutes.
With Zaxim, the contract is generated from your accepted proposal, pre-signed by you, and signed by the client on the same link — no account, no DocuSign. Every signature gets a tamper-evident certificate (audit trail + SHA-256) built to meet ESIGN, eIDAS, and UNCITRAL, with identity verified by a one-time code to the signer's email. Your first 3 proposals — contract and all — are free, no card.
Try it free- Photography Proposal Template (That Books the Shoot)
- Marketing Proposal Template (That Wins the Retainer)
- Freelance Contract Template (Simple, Fair, and Signable)
- Freelance Invoice Template (That Gets Paid On Time)
- DocuSign Alternative for Freelancers (When You Just Need the Contract Signed)
- Copywriting Proposal Template (That Sells the Words)
- Video Editing Proposal Template (That Wins the Retainer)
- Social Media Management Proposal Template (That Wins the Retainer)
- How to Price AI Automation Services in 2026 (Rates, Models, and a Worked Example)
- AI Automation Proposal Template (That Wins the Build)
- See all proposal guides
- See all 5 designed templates