What to Agree On Before You Hire an AI Agent Builder

Before you pay anyone to build you an AI agent or automation, get four things agreed on in writing. Who owns the accounts and the code. Documentation as part of the deal, not a favor. What happens if either of you walks away. And what counts as done. Skip these and you are not buying a business asset. You are renting someone else's black box.

Who owns the accounts, the API keys, and the code?

This is the one people skip because it feels awkward to bring up. Every account the build touches, the AI platform, the automation tool, any API keys, needs to sit under your login, not the builder's. If they set it up under their own account and hand you a shared link, you do not own it. You are a guest on someone else's account, and guests can get removed.

Before you sign anything, get this in writing:

• Every account gets created under your business email and login, or gets transferred to you within an agreed number of days of launch

• You hold the admin login, not a shared or view only seat

• Every API key gets regenerated in your name before the project is called finished

Why should documentation be a deliverable, not a favor?

Ask any builder for documentation and most will say sure, happy to. Then it never gets written, because it is not billable and nobody is forcing the issue. Put it in the contract as its own line item, tied to its own payment, and it actually gets done.

A real handoff document answers three things in plain language:

1. What the build actually does, step by step, written for someone who did not build it

2. Where it lives, and who has access to change it

3. What breaks it, and how you would know

What happens if the person who built it disappears?

We wrote a whole piece on what actually happens when your automation builder leaves, and the short version is it depends entirely on what you agreed to before they started. Ask directly, before you hire: if you disappeared tomorrow, could I keep this running myself or hand it to someone else? If the honest answer is no, that is the gap to close now, while you still have the leverage to ask for it. Once the project is paid and closed, you have none.

Should you pay a fixed price or hourly, and how do you tell if it is fair?

Both models are normal, so that is not the red flag. The red flag is a fixed price quoted before anyone asks how your business actually works. A real builder wants a short conversation first: what tools you already use, what your data looks like, what done means to you, before naming a number. A quote that shows up before that conversation is a guess wearing a price tag.

What are the red flags to watch for before you sign anything?

Any one of these alone might be nothing. Two or more together, walk away:

• No contract at all, just a chat thread and a payment request

• They cannot explain what the build does in plain language, only in tool names

• Documentation gets waved off with "I will get to it"

• No answer for what happens if they stop responding

• Every account stays under their login "for now"

A build you do not hold the keys to is not a business asset. It is a favor someone is doing you until the day they stop.

---

This is how we run every build we do. The client owns every account from day one. Documentation ships as part of the project, not after it. If you want to see what a trained AI agent actually looks like before you hire anyone to build you one, our free demo builds one from your own YouTube videos in about a minute at demo.ajmarketingresults.com.

---

Frequently asked questions

Do I need a written contract for a small AI agent or automation build?

Yes, even a short one. Two pages covering cost, timeline, who owns the accounts and code, and what documentation you get at the end prevents almost every dispute that actually happens on small builds.

Who owns the AI agent once it is built?

You should, completely. The accounts, the training data, the code, all of it, under your login, in your name. If a builder resists that, that alone is a reason to look elsewhere.

What if I do not understand the technical side well enough to ask good questions?

You do not need to know the tools. You need to ask what it does in plain language, and whether someone besides the builder could explain it back to you. If nobody else could ever understand it, that is the actual risk, not your lack of technical background.

Should I pay a fixed price or hourly for an automation build?

Either can work. A fixed price offered before a real conversation about your business is the part to question, not the pricing model itself.

What documentation should I ask for before the project is called done?

A plain explanation of what it does step by step, where it lives, who has login access, and what would break it. If that does not exist, the project is not actually done, no matter what anyone calls it.