Running the selection · Chapter 16
AI automation contracts, IP and exit terms
This is where the handshake becomes binding. A clear contract protects both sides. This chapter covers the clauses that matter most.
“A verbal contract isn't worth the paper it's written on.”
What an AI automation contract should cover
A good contract answers five questions. Cover each one before you sign.
- Who owns the code, workflows and IP?
- Who owns and can export the data?
- How and when is payment made?
- What support and SLA apply after launch?
- How do you exit cleanly?
IP and ownership clauses
Make the assignment explicit and in writing. It should cover code, workflows and documentation. See the ownership chapter for why this matters most.
Data and confidentiality
Your data must stay yours, with the right to export. Add an NDA for confidential information. Add a data processing agreement for personal data. See the security chapter for the detail.
Milestones and payment
Never pay it all upfront. Split payment across delivered stages. Keep the last payment for handover.
This split keeps the agency motivated to finish. It also protects you if things stall.
Support and SLA terms
Bake the support terms into the contract. Set response times and support hours in writing. See the support chapter for what an SLA should promise.
Exit and termination terms
Plan the exit before you start. Good terms let you leave without disruption.
- A fair notice period for either side.
- A full handover of code and accounts.
- The right to export your data.
- Credentials and documentation handed over.
- No holding your build to ransom.
Contract checklist
Use this as a final check before signing. Each row should be a clear yes.
| Clause | What good looks like |
|---|---|
| IP assignment | Code and IP are yours |
| Data rights | Yours, with export |
| Payment | Tied to milestones |
| SLA | Response times in writing |
| Exit | Notice, handover, no lock-in |
This chapter is general guidance, not legal advice. Have a lawyer review a significant contract.
Contracts by company size
For small teams
A clear statement of work is often enough. Make sure IP, data and exit are still covered.
For enterprises
Expect a master agreement plus a statement of work. Route IP, data and exit terms through legal.
Common contract mistakes
Key takeaways
- Assign the code and IP to you in writing.
- Keep your data yours, with export rights.
- Tie payment to milestones, last on handover.
- Agree a clean exit before you start.
Ready to sign with an agency?
Browse the directory to find and compare agencies.
Browse the directoryFrequently asked questions
What should an AI automation contract include?+
It should assign the IP and code to you. It should confirm your data stays yours, with export rights. It should tie payment to milestones. It should set support and SLA terms. And it should spell out clean exit and handover.
Who owns the IP in an AI automation project?+
It depends on the contract, so make it explicit. By default, ownership can sit with the agency. Add an IP assignment clause so the work is yours. That should cover code, workflows and documentation. Never leave ownership to assumption.
How should I structure payment milestones?+
Split payment across the project, not all upfront. A common split is deposit, two milestones and handover. Tie each payment to a delivered stage. Keep the final payment for handover and sign-off. That keeps the agency motivated to finish well.
What exit terms should an AI automation contract have?+
It should set a notice period for either side. It should require a full handover of code and accounts. It should confirm you can export your data. It should hand over credentials and documentation. Good exit terms let you leave without disruption.
Do I need an NDA with an AI automation agency?+
Usually yes, if you share sensitive data. An NDA protects your confidential information. Pair it with a data processing agreement for personal data. Sign both before you hand anything over. For most projects, this is standard practice.
Should a lawyer review an AI automation contract?+
For anything significant, yes. A lawyer catches gaps in IP, data and exit terms. Small, low-risk builds may only need a clear statement of work. Match the legal effort to the value and risk. This chapter is guidance, not legal advice.