Who Owns the Work When Another Team Builds It? IP Handover and Repeat Work

When a client pays for an AI agent, they usually expect to own what they paid for. When a freelancer or agency brings in a build partner, the chain of ownership gets longer. The build partner built the code, the agency sold it, and the client uses it. Ownership should be clear at each step, or the client may find that they cannot change, move or keep what they paid for.

Key takeaways

• Decide who owns the final deliverables before the work starts, and write it down.
• Ownership usually passes to the client when the final payment clears, not earlier.
• Third-party platforms and AI models stay under the providers' own terms, so the client needs to know which parts they do not own.
• Repeat work should state whether it uses the same terms, or new ones.

What counts as a deliverable

A deliverable is anything the client receives and pays for. For an AI automation project that can include workflow designs, prompts and instructions, connectors, configuration, documentation, test cases and the code that runs the workflow. Define the list in the scope, so there is no argument later about whether something was included.

Separate your tools from the client's work

Build partners usually have their own internal tools, templates and know-how. Those should stay with the builder. The client should own the specific outcome built for them, including the configuration and the data that flows through it. A clear line between general tools and client-specific work avoids most disputes.

Third-party platforms and models

Many AI projects use platforms, APIs or language models owned by someone else. The client does not own those services, and the provider's terms apply. Explain this in the proposal, so the client understands which costs are paid to whom, and which parts they can move to a different provider later.

When ownership passes

A common approach is to pass ownership of the final deliverables when the final payment clears. Until then, the builder keeps ownership and can pause work if payments are late. This protects the builder, but the wording must be clear enough that the client can plan around it.

Repeat work and reuse

Follow-on projects raise a fresh question: does the client own the new work, and can the builder reuse parts of it for other clients? Set the answer in the agreement. Many arrangements allow the builder to reuse general tools while keeping the client's data and specific outcomes private.

For how Growmerz handles ownership in its own proposals, the pricing and engagement model explains that ownership is agreed up front and written into the proposal. The become a partner page covers the split for partner-led projects.

Frequently asked questions

Does the client own the AI model?

Usually no. The client owns the workflow and outcome built for them. The model belongs to its provider, and the client uses it under the provider's terms.

Can the freelancer keep a copy of the work?

Often yes, for their own records, as long as client data and confidential details are removed. Put this in the contract.

What if the client wants the source code?

Agree the form of delivery in the scope. Source code, configuration exports and documentation may all be included, depending on the project.

Should a lawyer review the ownership terms?

Yes, especially for larger projects or clients in other countries. Ownership rules differ by country and by the type of work.