IT outsourcing contracts: the IP, NDA and exit clauses to check before signing
The contract clauses that decide whether outsourcing is safe: IP assignment, confidentiality, infrastructure control, notice and hand-over - with a pre-signing checklist.
Four clauses decide whether an outsourcing relationship is safe: IP assignment (everything produced for you is yours, explicitly), confidentiality (an NDA covering code, data and business information), infrastructure control (repositories and accounts in your name, access you can revoke), and exit terms (notice, hand-over obligations, transition support). Get these four right and most outsourcing horror stories become impossible; leave them vague and no rate card compensates. Here is what each clause must say, and the red flags that should end a negotiation.
Why does the contract matter more offshore?
Not because offshore vendors are less honest - but because distance raises the cost of ambiguity. When your vendor is across town, a dispute is a meeting; across continents, it is jurisdiction, language and time zones. A good outsourcing contract doesn’t try to win future disputes: it makes them structurally unnecessary by removing every ambiguity about who owns what, who may see what, and how the relationship ends.
What must the IP clause actually say?
The center of the agreement. Check for four specifics:
- Assignment, not license. Deliverables are assigned to you - your property - not licensed for your use. The distinction decides whether you can sell the company, change vendors or open-source the code later.
- Scope covers everything produced for you: code, documentation, designs, configurations, test suites - including work done by the vendor’s subcontractors or freelancers.
- Timing: ownership transfers on creation or on payment, not “upon final delivery” of a multi-year engagement.
- Pre-existing components declared. Vendors legitimately reuse internal libraries; the contract should list them and grant you a perpetual license, so your product doesn’t secretly depend on someone else’s property.
Ask the vendor to walk you through their standard IP clause on the first call. A partner who answers in one sentence - “everything we build for you is yours” - and shows the wording has had this conversation many times. Hesitation is information.
What makes confidentiality real rather than theatrical?
An NDA is necessary and not sufficient. Practical confidentiality comes from three layers:
- The NDA itself - signed before technical discussions, covering business information as well as code, surviving the contract’s end.
- Structural control - work happens in your repositories, cloud accounts and ticket systems where feasible; the vendor’s people get named, revocable accounts. Then leaving the vendor never means asking for your code back - you already have it.
- A counterpart with something to lose - an established, regulated entity (in Thailand, BOI promotion is a verifiable signal) values its standing more than any single engagement.
What does a healthy exit clause look like?
Judge an outsourcing agreement by how calmly it lets you leave:
| Element | What to require | Red flag |
|---|---|---|
| Notice period | Symmetric, 1–3 months typical | Vendor may exit fast, you may not |
| Hand-over | Defined deliverable: docs, KT sessions, access transfer | ”Reasonable assistance” with no definition |
| Transition support | Vendor supports successor for a defined period | Support ends the day notice lands |
| Lock-in | None beyond notice | Termination fees, ransom pricing for hand-over |
| Non-solicitation | Mutual and reasonable | One-sided bans on hiring anyone, ever |
A vendor confident in its service doesn’t need contractual walls to keep you. We put hand-over in our agreements as a deliverable precisely because an executable exit is what makes clients comfortable enough to stay for years.
Which clauses complete the checklist?
- Payment terms - monthly for T&M and dedicated teams, milestones for fixed price, each milestone tied to verifiable acceptance criteria.
- Data protection - if personal data is involved, processing terms aligned with the laws that apply to you (GDPR for EU data; Thailand’s PDPA locally).
- Liability - sensible caps are market practice; total exclusion of vendor liability is not.
- Governing law and disputes - workable under either party’s law or neutral arbitration; what matters is that your counsel reviewed it and the counterpart is real.
- Named key people - for dedicated teams, the lead’s continuity and replacement process written down.
In short
- Four clauses carry the risk: IP assignment, NDA, infrastructure control, exit - fix these and rate negotiations become the easy part.
- Demand assignment on creation/payment, covering subcontractors, with pre-existing components declared and licensed.
- Real confidentiality is structural: your repos, your accounts, revocable access - plus a counterpart with a reputation to protect.
- The exit test: could you actually leave in 90 days with code, docs and knowledge intact? If yes, you’ll probably never need to.
- A vendor who resists any of this before signing will not improve after.
AD System Asia contracts the way this article recommends - client-owned IP, NDAs before technical talks, work in client-controlled infrastructure on request, and hand-over as a written deliverable. Ask us for our standard terms and put them in front of your counsel.
Frequently asked questions
Who owns the intellectual property in an outsourcing contract?
Whatever the contract says - which is why the assignment clause matters. Insist on explicit wording that all code, documentation and deliverables produced for you are your property upon creation or payment, including work by subcontractors, with no license-back you didn't agree to.
Is an NDA with a foreign vendor actually enforceable?
A well-drafted NDA with an established legal entity is enforceable, but practical protection comes mostly from structure: work in repositories and systems you control, access you can revoke, and a vendor with a reputation and regulated status worth protecting - in Thailand, BOI promotion is one such signal.
What should the exit clause of an outsourcing agreement include?
Notice periods both sides can live with, a defined hand-over deliverable (documentation, knowledge-transfer sessions, access transfer), continued support during transition, and no punitive lock-in. An exit you could actually execute is the best test of a healthy agreement.
Should the contract be under Thai law or my home jurisdiction?
Both are workable; what matters more is contracting with a real, verifiable entity and keeping practical control of code and infrastructure. Many cross-border agreements choose a neutral arbitration clause. Have counsel review it - and treat a vendor who resists legal review as a red flag.
What payment terms are normal in IT outsourcing?
Monthly invoicing for T&M and dedicated teams; milestone-based payments for fixed price, with milestones tied to acceptance criteria you can verify. Large upfront payments are not standard practice and shift risk to you without a compensating benefit.