The offshore contract a startup founder sends me usually has 14 pages, 47 clauses, and four mistakes that would make it useless if either party tried to enforce it across borders. The contract a senior offshore freelancer sends back is usually 3 pages and covers the things that actually matter.
The asymmetry tells you something important: most contract length is defensive theater, not protection. Lawyers add clauses because they're paid to add clauses. Most clauses never get tested. Some of them quietly contradict each other. Many of them aren't enforceable in the freelancer's home jurisdiction even if you wanted to try.
This isn't an argument for skipping contracts. It's an argument for knowing which parts of the contract carry weight and which parts are filler. Get the load-bearing clauses right and you can simplify the rest.
I'm not a lawyer. This article isn't legal advice. It's the framing I use when reviewing contracts with my own clients, drawn from a decade of cross-border freelance work and watching what actually gets enforced versus what just sits in PDFs collecting dust.
The five clauses that matter
These five carry almost all the weight in a real dispute. Get these right and most other clauses become decoration.
1. Scope and deliverables (in detail)
The single most-disputed clause in freelance contracts is "what was actually agreed to be done." Not "did the developer write code" — that's rarely contested. The dispute is about whether the code that was written matches what the contract said would be delivered.
A weak scope clause: "Developer will build a software product as described in conversations with Client."
A strong scope clause: "Developer will deliver a web application with the features listed in Schedule A, deployed to the hosting environment described in Schedule B, with the success criteria defined in Schedule C, by the dates in Schedule D."
The schedules are where the work goes. Without them, "what was agreed" is whatever the louder party remembers in arbitration. With them, the contract is enforceable because both parties know what "done" means.
The discipline: if the scope clause is shorter than your brief, the contract is too vague. If you didn't read The Eight-Question Brief That Saves $10,000 in Offshore Hiring Mistakes, the brief content is exactly what should appear in the scope schedules.
2. IP ownership and assignment
The default in most jurisdictions: the person who creates the work owns it, unless the contract says otherwise. "Pays for the work" doesn't automatically transfer ownership. "Was on a contract during the work" doesn't either.
If you skip this clause, you may end up with a license to use the code rather than ownership of the code. That's fine until you try to sell the company, raise money, open-source a portion, or relicense the work. At those moments, the original developer's signature is required, and they may decline.
The clause to insist on:
All work product created by Developer in performance of this Agreement is "work made for hire" under applicable copyright law. To the extent any work product does not qualify as work made for hire, Developer hereby assigns to Client all right, title, and interest (including all intellectual property rights) in and to the work product, effective upon creation.
That's it. One paragraph. It doesn't need to be 14 paragraphs of related-rights, neighbouring-rights, perpetual-irrevocable-worldwide-royalty-free language. The assignment in the paragraph above does the work.
What this clause does NOT cover (deliberately): pre-existing tools, libraries, and frameworks the developer used to build the work. The developer owned those before the contract; they still own them after. A separate "background IP" clause can list what's pre-existing and exclude it from the assignment. This is normal and should not alarm you.
3. Payment terms
Three things matter:
- The rate (or fixed price)
- The payment schedule (weekly? milestone? net-30?)
- What happens if you don't pay
The third is where most contracts fail in practice. Without it, late payment becomes a recurring negotiation. With it, the freelancer has a clear right to suspend work, and you have a clear obligation.
Realistic terms for international contractor work:
- Hourly: invoiced weekly or biweekly. Payment due within 7 days. Work suspends after 14 days unpaid. Late fee: 1.5% per month or jurisdiction-allowed maximum.
- Fixed price: 30–50% deposit before work starts. Milestone payments tied to specific deliverables. Final payment within 7 days of acceptance. Same suspension and late-fee terms.
- Retainer: monthly in advance. Refundable on a pro-rata basis if cancelled mid-month. No services rendered during any period of unpaid retainer.
The "what happens if you don't pay" clause is what protects the freelancer from working forever on hope. It also protects you from the freelancer disappearing without notice — they're contractually required to give notice and continue work during the cure period.
4. Termination and notice
Both parties need to be able to exit the arrangement. The clause to look for: 30 days notice from either party, with payment due for all work completed up to the termination date, and an obligation to provide reasonable handoff materials.
Avoid contracts with termination clauses that:
- Require the freelancer to continue working for months after notice (slavery-adjacent and unenforceable in most jurisdictions anyway)
- Charge "early termination fees" that exceed the next month or two of fees (usually unenforceable as unliquidated damages)
- Permit termination only "for cause" with cause defined narrowly (creates an exit trap for both sides)
Mutual 30-day-notice termination is the cleanest arrangement and the one that holds up cross-border.
5. Confidentiality (without the theatre)
A simple confidentiality clause covers anything not yet public, lasts the duration of the relationship plus 1–3 years, and has clear exceptions for things like compelled disclosure or information that becomes public through no fault of the recipient.
What you don't need: 7-page NDAs with dozens of defined terms, perpetual confidentiality even on stale information, "non-circumvention" clauses preventing the freelancer from working with anyone you've ever introduced them to. These look protective but are mostly unenforceable internationally and signal that you don't trust the relationship.
What you should include: a return-or-destroy obligation at end of engagement (so the freelancer doesn't have your data sitting on their laptop forever), and a clear "can use generic learnings for own business" carve-out (the freelancer's own skills and patterns aren't your IP, and pretending they are creates a contract neither party will respect).
The five clauses that are mostly theater
These show up in templated contracts and feel important but rarely carry the weight people think they do.
1. Non-compete clauses
A clause saying "Developer will not work for any of Client's competitors for X years after termination" is mostly unenforceable internationally. Even in jurisdictions where it's technically enforceable, the cross-border enforcement cost is so high that nobody actually litigates these.
The realistic protection isn't a non-compete — it's a confidentiality clause that prevents disclosure of specific information. The freelancer can work with your competitors after the engagement ends, but they can't bring your customer list, your roadmap, or your code. That protection is real. The non-compete protection is theatre.
2. Non-solicitation of employees
Same problem, smaller stakes. "Developer will not hire Client's employees for X years" assumes the freelancer is in a position to hire your employees, which is rarely true. When it is true, the harm to you is small enough that nobody pursues it.
Skip this clause unless the freelancer is also a recruiter or running a competing business. In normal hiring it's filler.
3. Specific jurisdiction and governing law
Contracts often specify "governed by California law, exclusive jurisdiction in San Francisco County." For an offshore freelancer in Manila, this is decorative — California courts can issue judgments, but enforcing them against assets in the Philippines requires a separate proceeding under Philippine law that's expensive enough to make the original judgment irrelevant for any dispute under $200k.
What actually matters: agreed-upon arbitration with a recognised international body (AAA, ICC, or even just a clear "we'll mediate first, then arbitrate" structure), or a willingness to accept that disputes under $50k are practically not enforceable across borders and need to be handled through the relationship rather than the contract.
The honest read: cross-border contract enforcement for small sums is theoretical. The contract's real job is to prevent disputes by being clear, not to win disputes after they happen.
4. Liquidated damages and penalties
Fixed-amount damages clauses ("$500 per day of late delivery") are often unenforceable as penalties rather than legitimate damages estimates. Even when enforceable, the freelancer typically doesn't have the assets to pay them, so they're symbolic.
The realistic version: actual demonstrable losses (not pre-set amounts), capped at the total contract value, with a mutual obligation to mitigate. Anything more aggressive is either unenforceable or pointless.
5. Mutual indemnification with unlimited liability
Boilerplate templates often include "Each party indemnifies the other for all losses, damages, and costs arising from the engagement, without limit." This is industry standard and signed without thought, and it's also a clause that would bankrupt the freelancer if ever invoked literally.
The realistic version: indemnification capped at fees paid in the prior 12 months, with carve-outs for IP infringement and gross negligence. This is what serious contracts converge on once both parties have lawyers who actually negotiate.
How cross-border enforcement actually works
The hard truth: small disputes between Western SMBs and offshore freelancers rarely get litigated, because the cost of cross-border enforcement is higher than most disputed amounts. A US client who's owed $5,000 by a Manila freelancer (or vice versa) is almost never going to recover it through courts. The litigation cost dwarfs the recovery.
What this means in practice:
- The contract's job is to prevent disputes, not win them. Clear scope, clear payment terms, clear termination clauses keep both sides aligned. Detailed enforcement language is mostly decorative.
- Reputation does the work courts can't. A freelancer who burns clients gets bad reviews and stops getting work. A client who refuses to pay gets blacklisted in the freelance community. Both parties have skin in the game beyond the contract.
- For larger sums (>$50k), real enforcement is possible. International arbitration is workable. Recognised arbitration awards are enforceable under the New York Convention in 170+ countries. But this is the exception, not the rule.
- Escrow services and payment platforms (Upwork, Toptal, etc.) provide cheap dispute resolution for marketplace work. Direct contractual relationships outside platforms have to handle this themselves, which is one of the trade-offs of direct hiring.
A pragmatic contract template
Three pages. Hits the load-bearing clauses, skips the theater. The structure I'd recommend for most SMB-to-offshore-freelancer contracts:
- Parties and effective date
- Scope (with schedules attached)
- Payment terms (rate or fixed price, schedule, late-payment terms)
- Term and termination (30 days notice mutual)
- IP assignment (work-made-for-hire + assignment language)
- Confidentiality (mutual, time-limited, with carve-outs)
- Limitations of liability (capped at fees paid)
- Dispute resolution (mediation first, arbitration if needed)
- General provisions (no oral modifications, severability, governing law)
That's it. If a template you receive is much longer than this, ask your lawyer which additional clauses are actually necessary for your specific situation. Most won't be.
What to do next
If you've got a workable brief and contract framework, the next decisions are payment mechanics and time-zone arrangement. See Paying International Contractors: Stripe, Wise, PayPal, or Bank Transfer? and Time Zones for Offshore Work: What Overlap You Actually Need.
If you'd like to talk about specific work, the most common shape is the Lead Steer monthly retainer — $500/mo for 10 hours of mixed dev / tech / EA work, hired direct.
---
Part of the Offshore Hiring pillar guide. This article is not legal advice — review specific contracts with a qualified lawyer in your jurisdiction.