Here is a fact that surprises most founders: if you hire a contractor to write code and you do not have a signed agreement assigning the rights to you, the contractor may own the copyright in that code, not you. It gets more complicated when the developer is in another country. Protecting your intellectual property when you hire offshore is not hard, but it depends on getting a few specific things in writing, and on understanding why a handshake and an invoice are not enough. This is general information, not legal advice, so run your actual contracts past a lawyer.
Key Takeaways
- Absent a signed assignment, a contractor can own the code they write for you. This is the default, not the exception.
- A valid transfer of copyright must be in writing and signed (17 U.S.C. 204(a)).
- Cross-border hiring adds a layer: you need a governing-law and jurisdiction clause, because IP law differs by country.
- An entity-backed provider can consolidate IP for you, but only if the assignment chain is explicit.
Why "I Paid For It" Is Not Enough
In the US, "work made for hire" (where the company automatically owns the work) applies to employees, and to contractors only in a narrow set of enumerated categories that general software is not part of (US Copyright Office, Circular 30). So when you commission a contractor to write code, paying the invoice does not, by itself, transfer ownership. Copyright law requires that a transfer be in a signed writing to be valid (17 U.S.C. 204(a)). Without that written assignment, you may have paid for code you do not fully own, which becomes a real problem in an acquisition or a fundraise when someone does diligence on your IP.
What Changes When the Developer Is Offshore
A written assignment is the foundation everywhere. Hiring across a border adds the question of which country's law governs it. IP and labor law differ by jurisdiction, and some countries treat authorship, moral rights, and contract validity differently from the US. That does not mean your ownership is unprotected. It means the contract needs to say clearly which law governs and where disputes are resolved, whether that is a US state, the developer's country, or neutral arbitration. Get the assignment and the governing-law clause right and you close the cross-border gap. Leave them vague and you have created the ambiguity you were trying to avoid.
| Must-have | Why |
|---|---|
| Written, signed IP assignment | Required for a valid transfer |
| Governing-law + jurisdiction clause | IP law differs by country |
| Confidentiality / NDA | Protects trade secrets and data |
| Open-source disclosure + warranty | Avoids copyleft contamination of your code |
A Concrete Version
A startup built its core product with an overseas contractor on a simple hourly agreement, no IP clause, because it was fast and cheap. Two years later an acquirer's lawyers asked for proof that the company owned its own codebase, and the honest answer was that it did not have a signed assignment from the person who wrote most of it. Chasing that signature after the fact, from a contractor who had since moved on, turned a clean deal into a tense one. A single assignment clause at the start would have prevented the entire scramble. There is also a quieter version of this risk: undisclosed open-source code under a strong copyleft license can quietly compromise ownership of proprietary code, which is exactly the kind of thing diligence hunts for.
The Honest Counterpoint
You can also overthink this to the point of paralysis. A short, clear contract with an IP assignment, a governing-law clause, an NDA, and an open-source warranty covers the large majority of real risk for a normal software engagement. You do not need a forty-page custom agreement negotiated for a month before anyone writes a line of code. The failure mode that actually hurts founders is having no written assignment at all, not an imperfect clause. Get the basics in writing at the start, have a lawyer review the template once, and reuse it. And know that an entity-backed model, where the provider employs the engineer and assigns the IP to you through the contract, can make this cleaner, as long as that assignment chain from engineer to provider to you is written down and not assumed.
Frequently Asked Questions
If I pay a contractor, do I own the code?
Not automatically. In the US, work made for hire covers employees and only narrow categories of commissioned work, which general software is not. You need a signed written assignment to own a contractor's code.
What is different about hiring offshore?
The core requirement, a written assignment, is the same. What is added is the need for a clear governing-law and jurisdiction clause, because IP and labor law differ across countries. Keep it explicit.
Does using an EOR or provider give me the IP automatically?
No, not automatically. An entity-backed provider can deliver clean IP to you, but only when the assignment chain from the engineer to the provider to you is written into the contracts. Confirm it, do not assume it.
The Bottom Line
Protecting your IP offshore comes down to a few written things: a signed IP assignment, a governing-law and jurisdiction clause, an NDA, and an open-source warranty. The default without them is that you may not own what you paid for. Get the basics in writing at the start and have a lawyer review the template. This is general information rather than legal advice. For a related angle, see who owns the code a contractor writes and how to protect your idea when hiring a developer. See available engineers.
Roberto Espinoza is CEO of Ruzora, which helps US startups hire pre-vetted senior LATAM engineers, with a vetted shortlist in 72 hours. See available engineers.
