How a BOT Agreement Secures Your Code and Intellectual Property from Day One

Most companies that explore nearshore outsourcing spend the bulk of their due diligence evaluating talent quality, cost structures, and time zone overlap. These are the right things to evaluate. But there is a layer underneath all of it that tends to get addressed too late in the process, and that layer is legal protection. Specifically, who owns the code, who owns the systems, and what happens to all of it if the engagement does not go the way you planned. The BOT agreement is the document that answers all of those questions. A well-constructed legal BOT framework does not just outline how the engagement will run. It establishes IP ownership, access rights, confidentiality obligations, and transition protocols from the moment work begins. According to the World Intellectual Property Organization, software IP disputes in cross-border technology arrangements are among the most complex and costly to resolve, often taking years and costing significantly more than the original engagement was worth. Getting the legal structure right at the start is not a formality. It is the foundation your entire offshore arrangement sits on.

Why IP Protection in a BOT Arrangement Is Different from Standard Outsourcing

In a traditional outsourcing arrangement, IP ownership is often vague by default. The vendor owns the tools, the people, and frequently the work product unless your contract explicitly states otherwise. Many companies discover this gap only when the engagement ends and they try to take possession of something they assumed was theirs all along.

The BOT model is structurally different because the entire point of the engagement is eventual ownership. Your BOT partner is building something for you to take possession of. That ownership intent has to be written into the legal BOT framework from day one, not tacked on at the Transfer stage when disputes are harder and more expensive to resolve.

What a Weak BOT Agreement Looks Like in Practice

A weak BOT agreement is one that focuses heavily on the operational mechanics of the Build and Operate phases but leaves IP ownership, code access rights, and Transfer conditions vague or subject to future negotiation. These gaps seem harmless during the honeymoon period of a new engagement. They become serious problems when something goes wrong, when a key developer leaves, when the vendor relationship deteriorates, or when you want to exercise your Transfer right and the partner disagrees about what exactly is being transferred.

The most common gaps in poorly structured BOT agreements include undefined work-for-hire provisions, missing assignment clauses for inventions developed during the engagement, vague confidentiality obligations that do not survive termination, and Transfer clauses that do not specify exactly what assets are included in the handover. Any one of these gaps can turn a successful operational engagement into a protracted legal dispute.

What a Strong BOT Agreement Establishes from the Start

A strong legal BOT framework resolves these questions before the first line of code is written. It establishes that all work product created during the engagement is work-for-hire owned by the client. It includes explicit IP assignment clauses covering code, documentation, architecture designs, and any inventions or processes developed specifically for the client's product. It defines confidentiality obligations that apply to the vendor, all employees working on the engagement, and any subcontractors involved.

It also establishes your right to access the codebase, the infrastructure, and all project documentation at any point during the engagement, not just at Transfer. This access right is more important than most clients realize. Without it, you are dependent on your partner's cooperation to understand the state of your own product.

The Key IP Clauses Every BOT Agreement Needs

Work-for-Hire and Assignment Provisions

The foundation of software intellectual property protection in any cross-border engagement is the work-for-hire doctrine paired with an explicit assignment clause. Work-for-hire establishes that the output created by your nearshore team during the engagement belongs to you by default. The assignment clause ensures that any rights that do not automatically transfer under work-for-hire, including moral rights in certain jurisdictions, are explicitly assigned to you.

These provisions need to flow through the entire legal structure. Your BOT agreement should require that your partner's employment contracts with your nearshore team include individual IP assignment clauses that mirror the obligations in the main agreement. If a developer's employment contract does not include these provisions, there is a gap in your IP chain that an assignment clause in the main agreement cannot fully close.

Source Code Access and Escrow Rights

Your BOT agreement should give you continuous access to the source code repository throughout the engagement, not just at Transfer. This means your team should have read access to the codebase at all times and the agreement should specify how version control is managed, where code is stored, and what happens to repository access if the engagement is terminated early.

For engagements involving particularly sensitive or critical software intellectual property, a source code escrow arrangement is worth considering. An escrow agent holds a current copy of the codebase and releases it to you under defined trigger conditions, such as vendor insolvency or material breach. The National Cybersecurity Alliance consistently identifies IP and data access continuity as a critical risk management consideration for companies operating across international technology partnerships.

Confidentiality That Survives Termination

Standard confidentiality clauses apply during the engagement. What many BOT agreements miss is post-termination confidentiality protection. When the engagement ends, whether through Transfer completion or early termination, every person who worked on your product has detailed knowledge of your architecture, your codebase, your security infrastructure, and your business logic.

Your BOT agreement should include post-termination confidentiality obligations that cover the vendor and all former employees of the nearshore team for a defined period after the engagement ends. These obligations should be reinforced at the individual employment contract level so that each team member is personally bound, not just the vendor entity.

Transfer Clause Specificity

The Transfer clause is the most important section of the entire BOT agreement and the one that most commonly gets written too broadly. A Transfer clause that says the vendor will transfer the operation to the client at the end of the Operate phase tells you very little about what actually happens. A strong Transfer clause specifies exactly what is being transferred, including the employment contracts, the legal entity if applicable, all IP rights, all infrastructure access credentials, all vendor relationships and contracts that support the operation, all documentation, and all data.

It should also specify the process, timeline, and conditions under which Transfer occurs, what happens if the client is not satisfied with the state of the operation at Transfer time, and what remedies are available if the vendor does not cooperate with the handover process.

How IP Protection Works Across the Three BOT Phases

IP Protections During the Build Phase

During the Build phase, your BOT partner is recruiting, hiring, and onboarding the team that will build your product. This is when the employment contracts get signed, which means this is when individual IP assignment clauses need to be in place. Every person hired into your nearshore team during the Build phase should sign an employment agreement that includes explicit IP assignment, confidentiality, and non-compete provisions consistent with your main BOT agreement.

This is also when your infrastructure gets configured. Make sure your BOT agreement specifies that all infrastructure is provisioned under your accounts or that full account transfer is included in the handover obligations. Infrastructure that lives under your partner's accounts creates access dependency that can become a problem at Transfer time.

IP Protections During the Operate Phase

During the Operate phase, your team is actively building. This is when your IP exposure is at its highest because the volume of proprietary code, architecture decisions, and product knowledge being generated is greatest. Your BOT agreement should give you real-time visibility into this output, including access to version control, the ability to conduct security audits, and clear protocols for handling any security incidents.

You can read more about how the Operate phase runs in practice in our guide on defining KPIs in the Operate phase. The performance management and IP protection layers of the Operate phase are closely connected. A well-managed Operate phase protects both your product quality and your legal position.

IP Protections During the Transfer Phase

The Transfer phase is when all of the IP protections built into your agreement get tested. A clean Transfer requires a systematic handover of every asset covered by the Transfer clause. This means a formal IP assignment document executed at Transfer time, transfer of all repository access, handover of all infrastructure credentials, assignment or novation of all vendor and contractor agreements supporting the operation, and a period of transition support during which your partner remains available to address any gaps.

Our step-by-step breakdown of the Build, Operate, and Transfer phases covers the full Transfer process in detail, including what a clean handover looks like operationally and where IP-related friction most commonly occurs.

Jurisdiction and Governing Law in Cross-Border BOT Agreements

One of the decisions that gets made too quickly in BOT agreement negotiations is governing law and dispute resolution. Which country's law governs the agreement? Which courts or arbitration bodies have jurisdiction over disputes? These decisions have real consequences for how enforceable your IP protections actually are.

For most US-based companies setting up nearshore operations in LATAM, the preferred approach is to govern the main BOT agreement under US law or a neutral jurisdiction like New York or Delaware, with a binding arbitration clause specifying an international arbitration body such as the International Chamber of Commerce or the American Arbitration Association. Individual employment contracts with nearshore team members are typically governed by local law since employment law is territorial, but the IP assignment and confidentiality provisions within those contracts should be drafted to be as enforceable as possible under local law.

Working with legal counsel who has experience in both US technology contracting and the specific LATAM country you are operating in is not optional for this layer. The International Bar Association's cross-border IP guidelines provide a useful framework for understanding how IP rights interact across jurisdictions in international technology engagements.

Frequently Asked Questions About BOT Agreement IP Protection

Does the BOT Model Offer Stronger IP Protection Than Traditional Outsourcing?

Yes, when the agreement is structured correctly. The BOT model is designed with the client's eventual ownership as the endpoint, which means a well-drafted BOT agreement builds IP ownership rights into the engagement from the start rather than leaving them to be negotiated at the end. Traditional outsourcing agreements often default to vendor ownership of work product unless explicitly overridden, and many companies only discover this when they try to terminate or transition an engagement.

What Happens to IP If the BOT Transfer Does Not Complete?

This depends entirely on your agreement. A well-structured BOT agreement should include provisions that protect your IP rights regardless of whether the Transfer completes. This means your work-for-hire and IP assignment clauses should operate independently of the Transfer clause so that you own the code and systems even if the Transfer itself falls through. You should also have rights to a full copy of the codebase and all documentation upon termination for any reason.

How Do You Protect IP When Team Members Leave During the Operate Phase?

Individual IP assignment clauses in employment contracts are the primary protection here. When a developer leaves your nearshore team, their obligation to assign any IP they created during the engagement should survive their departure. Your BOT agreement should require your partner to enforce these provisions and to notify you promptly of any departures that could affect IP continuity. You can read more about managing team stability during the Operate phase in our post on the full checklist for setting up a software hub in LATAM.

Should You Use a Local or International Law Firm to Draft the BOT Agreement?

Both. The main BOT agreement and its IP provisions are best handled by a firm with experience in US technology contracting and international IP law. The individual employment contracts for your nearshore team need to be drafted or reviewed by local counsel who understands the specific labor and IP laws of the country where your team is based. Using only one or the other creates gaps in enforceability that can be costly to close later.

Why Work with BOT LATAM

Getting the legal BOT framework right is one of the most important things you can do before your first hire starts. At BOT LATAM, we have structured engagements across multiple LATAM markets and we understand the IP protections that need to be in place at every phase, from the first employment contract signed during the Build phase to the final IP assignment executed at Transfer. We work with clients to ensure their BOT agreements cover every relevant asset, that their nearshore team's employment contracts include enforceable IP assignment and confidentiality provisions, and that the Transfer process delivers complete legal ownership with no gaps. If you are starting to explore a nearshore BOT arrangement and want to make sure your software intellectual property is protected from day one, we offer a free first call to walk through the legal structure with you. Reach out to us today and let us help you build something you can fully own.

‍