What this checklist is and what it leaves out
A contract for an AI agent is similar to a software development contract, with two differences. An agent can answer the same question in different ways, so acceptance is described by a metric on a set of test questions, not by a list of screens. And the agent works with company and customer data, so the contract gets clauses on personal data.
The checklist is made for a CEO and a project manager: what to find in the text and what to ask about. A lawyer judges the type of contract (work contract, license or mixed), the wording and the industry risks. The articles of the Russian Civil Code and of 152-FZ, Russia’s personal data law, are named below so that you know what to ask the lawyer.
Red flags in a commercial proposal are covered separately. If you have not accepted the proposal yet, start with them: some problems show up before the contract.
Scope and result
The scope of the contract describes the agent’s work, not the technology. In June 2025 Gartner counted about 130 real agent vendors out of thousands that claim to be; the rest renamed chatbots and RPA (software robots that follow fixed rules). The word “agent” in a contract promises nothing; the actions matter.
1. Process and limits: which process the agent takes, which requests it closes by itself and which it passes to a person.
2. Channels and systems: where the agent talks to people (website, messengers such as Telegram, phone), which systems it writes to (CRM, 1C accounting software, email) and with what rights.
3. The model and where it runs: an open model on your server or a cloud model, and in which country the data is processed. The contract bans replacing the model without the customer’s consent or describes the procedure.
4. What the result includes: a configured agent, instructions and a knowledge base in readable form, documentation and a list of accounts. A detailed description of the work goes into the specification, an annex to the contract.
Metric and acceptance
The metric decides what you pay for: without it, the contractor delivers the fact of a launch, not a result. The effect on profit is exactly what 95% of pilots in the MIT NANDA report lacked, so the “before and after” figure is written down before the start.
1. The metric in figures: what it was, what it should become and how to measure it. For example, the share of requests the agent closed without a person, or the response time to a customer.
2. Test set: real questions with correct answers that the customer collects before the start. The agent is tested on it before launch and after each change.
3. Acceptance procedure: the pilot term, who signs the acceptance certificate, how many days for comments, and what counts as a fix and what as a new task.
4. If the metric is not reached: a fix at the contractor’s expense, a discount or the right not to move to the next stage. Payment by stages with results is safer than payment by the hour.
We put the metric into the pilot contract: the pilot costs from $1,499 and takes 14 days.
Rights to the agent, code and data
Under Article 1296 of the Russian Civil Code, the exclusive right to a program created on commission belongs to the customer unless the contract says otherwise. A license instead of a transfer of rights is also a legal option, but you must see in the text what exactly you get.
1. What is transferred: the exclusive right to the code or a license. If a license, is it perpetual, for which territory and for how many users.
2. Third-party components: open tools and models come under their own licenses, and nobody transfers rights to them. The contract lists them with the name of each license.
3. Data and settings: the agent’s instructions, knowledge base, dialog logs and examples belong to the customer and are handed over in a readable format on request and on termination.
4. Accounts: the agent works under the customer’s accounts in the CRM, 1C and telephony, and the contractor’s access is revoked on the day the work ends.
Levels of ownership (subscription, license, code) are covered in the article on who owns an AI agent. With us, after adoption you have the system, a perpetual license, the data and the access, and the source code is bought out separately.
Personal data and 152-FZ
If the agent sees customers’ names, phone numbers or messages, the contractor processes personal data on your instruction. Part 3 of Article 6 of 152-FZ, Russia’s personal data law, requires this instruction to be in the contract and to name the list of data, the actions with it, the purposes, the duty of confidentiality and the protection requirements under Article 19.
You, as the operator, answer to the customer for the contractor’s actions, and the contractor answers to you (Part 5 of Article 6). So the contract states the contractor’s liability for a leak and the time within which it reports one.
Storage location: since 1 March 2023, an operator must notify Roskomnadzor, Russia’s data protection regulator, before transferring personal data abroad, and the data of Russian citizens is collected and stored in databases in Russia. If the agent runs on a foreign model, that is a decision for the lawyer, not the contractor.
The cost of a mistake: for a repeated leak, a company pays 1–3% of its revenue, but not less than $300,000. How we store client data is described on the page about data security.
Support, price and exit from the contract
1. The price and what it includes: the one-time build separately, model and server costs separately, with a monthly estimate for your number of requests.
2. Support: what it includes (monitoring, fixes, a metric report), the monthly price and the right to stop in any month without losing the agent. Our support costs from $480 a month.
3. Failures: the response time, who fixes the agent if it stops answering at night, and where requests go during that time.
4. Exit: what the contractor hands over on termination, in what time, and how it deletes your data from its servers.
5. Confidentiality: a non-disclosure agreement on processes, data and settings, in both directions.