How to Write a Software Services Contract for Overseas Clients

This guide walks you through drafting a software services contract for overseas clients, covering scope, payment, IP, liability, and dispute resolution. You’ll learn what to include, common pitfalls, and how to handle issues when they arise. Before starting, gather your standard terms, project details, and any legal advice you may need.

What You’ll Need

• Your company’s legal name, address, and contact details
• Client’s legal name, address, and contact details
• Project scope: features, deliverables, timeline, and milestones
• Pricing structure (fixed fee, hourly, or milestone-based)
• Payment terms (currency, due dates, late fees)
• Intellectual property ownership preferences
• Confidentiality and non-disclosure requirements
• Warranty and support terms
• Limitation of liability and indemnification clauses
• Dispute resolution mechanism (arbitration, jurisdiction, governing law)
• A lawyer familiar with international contracts (optional but recommended)

Step-by-Step

1. Define the parties clearly. Start with full legal names, addresses, and incorporation details. Specify which entity is the client and which is the service provider. Avoid vague references like “the company” without definition.
2. Describe the services in detail. List the exact deliverables, features, and functionalities. Include acceptance criteria—how the client will verify the work is complete. State what is out of scope to prevent scope creep.
3. Set the timeline and milestones. Provide a development schedule with start and end dates, key milestones, and delivery deadlines. Include a clause for delays caused by the client (e.g., late feedback) that extends the timeline.
4. Specify payment terms. State the total price, currency (e.g., USD, EUR), and payment schedule (e.g., 30% upfront, 40% at milestone, 30% on delivery). Add late payment penalties, interest, and suspension rights for non-payment. Clarify who pays for bank transfer fees.
5. Address taxes and withholding. Determine whether VAT, GST, or withholding taxes apply. Include a clause that the client is responsible for any taxes not included in the fee. If necessary, provide for tax gross-up.
6. Define intellectual property ownership. State that you assign full IP rights to the client upon full payment, or retain ownership if you’re licensing the software. Specify any third-party components and their licenses. Include a clause that you own pre-existing materials.
7. Add confidentiality and data protection. Obligate both parties to keep confidential information private. Address data processing, GDPR or other privacy laws, and security measures. Include a data processing agreement if needed.
8. Include warranty and support terms. State that the software will conform to the specification for a period (e.g., 90 days). Define what support is included (e.g., bug fixes) and what is extra (e.g., new features). Exclude warranties for client-modified code.
9. Limit liability. Cap your total liability to the amount paid by the client. Exclude indirect, consequential, or lost-profit damages. This is crucial for overseas contracts where legal recourse is harder.
10. Set dispute resolution and governing law. Choose a neutral jurisdiction (e.g., Singapore, England) and a governing law. Prefer arbitration over litigation for international disputes—it’s faster and more enforceable under the New York Convention. Specify the arbitration venue and rules (e.g., ICC).
11. Include termination and force majeure. Define how either party can terminate (for convenience with notice, or for breach). Address what happens to payments and IP upon termination. Add a force majeure clause covering events beyond control (pandemics, natural disasters).
12. Review and sign. Have both parties review the contract with legal counsel. Sign in counterparts and exchange via email or e-signature. Keep a signed copy for your records.

Common Mistakes

• Leaving scope vague—leads to disputes over what’s included.
• Ignoring currency fluctuations—if you invoice in a volatile currency, you may lose money.
• Not specifying acceptance criteria—client may reject work arbitrarily.
• Omitting IP transfer conditions—client may assume they own everything, including your pre-existing code.
• Choosing the wrong governing law—your local law may not be enforceable overseas.
• Forgetting data protection—GDPR applies to EU clients even if you’re outside.
• No limitation of liability—you could be sued for consequential damages.

Tips

• Use plain language and define all terms.
• Include a change order process for scope changes.
• Specify communication channels and response times.
• Require client to provide timely feedback and materials.
• Consider escrow for source code if client wants assurance.
• Keep the contract in English, even if client speaks another language.
• Get a local lawyer to review the dispute clause.

Troubleshooting

If the client stops paying, first send a formal notice and suspend work as per the contract. If that fails, invoke the dispute resolution clause. For IP disputes, document your ownership of pre-existing code. If the client requests out-of-scope work, use the change order process to quote additional fees. If a legal issue arises, consult an international attorney before responding. If the contract is breached, gather evidence and consider arbitration—it’s often faster than litigation.

Frequently Asked Questions

What if the client doesn’t pay?

Follow the contract: issue a notice, suspend work, and if necessary, pursue arbitration or legal action. Keep records of all communications.

Who owns the code if the client doesn’t pay?

Your contract should state that IP transfers only upon full payment. If not, you retain ownership until payment is complete.

Can I use my local law?

You can, but it may be hard to enforce overseas. Better to choose a neutral jurisdiction and arbitration under the New York Convention.

What about taxes?

Specify who pays taxes. If withholding tax applies, include a gross-up clause so you receive the full amount.

How do I handle GDPR?

If you process EU personal data, include a data processing agreement and comply with GDPR. This is mandatory, not optional.

What if the client wants source code escrow?

That’s reasonable if they’re paying for full IP. Use a reputable escrow service and define release conditions.

Related

• Pixel 2 Random Shutdowns: Fixes That Work
• Fix WiFi Connected But No Internet on Windows 10
• Fix Fire TV Stick Not Loading Apps: Quick Guide