What to Put in a Web Development Contract with an Overseas Agency

Ammar Sohail 4 min read
What to put in a web development contract with an overseas agency
In this post
  1. Who owns the work: the part most people get wrong
  2. What else to put in a web development contract
  3. Why milestones matter more than legal wording
  4. Practical tips

A good web development contract is not about expecting trouble. It makes sure both sides mean the same thing by "finished" and "yours". That matters more when your developers are in another country, because you cannot drop by their office and going to court is rarely practical. This is general guidance, not legal advice, so have a lawyer review the contract for a large project.

Checklist for a web development contract: scope, milestones, ownership, accounts, confidentiality and ending the project
The six parts to get right.

Who owns the work: the part most people get wrong

Many clients assume that paying for a website means they own it. Often, they do not.

  • United States. An independent contractor generally owns the copyright in what they create. "Work made for hire" only applies to certain categories of commissioned work, and most websites and software do not clearly fit. A written, signed assignment is the safer route.
  • United Kingdom. Commissioning a work does not transfer the copyright by itself. Under the Copyright, Designs and Patents Act 1988, an assignment has to be in writing and signed by the owner.

So do not rely on a line saying that you own everything. Plain wording along these lines is a starting point for your lawyer to check:

Once all fees for the project are paid, [Agency] assigns to [Client] all copyright in the work created for this project. Third-party themes, plugins, fonts and images remain under their own licences and are listed in the project file.

Also ask about the developer's existing tools. An agency may reuse its own code on every project, so you may get a licence to use that part rather than ownership of it.

What else to put in a web development contract

  • Scope. The pages and features included, and a list of what is not.
  • Acceptance. What "finished" means, such as the browsers and phones it must work on, and how long you have to review it.
  • Price and milestones. What you pay at each stage, what must be delivered first, and in which currency.
  • Timeline. Rough dates, and what happens if either side is late, including delays in your own content or feedback.
  • Changes. How extra work is priced and approved before it starts.
  • Accounts. That the domain, hosting and store accounts are in your name, with logins handed over at the end.
  • Confidentiality. An NDA, or a clause in the contract, that covers your data and plans.
  • Customer data. If the agency can see your customers' personal data, your privacy obligations may require a data processing agreement. This is common for UK businesses.
  • Bug fixes. How long after launch problems get fixed for free, and what ongoing support costs after that.
  • Ending the project. What you pay for and what you receive if either side stops early.
  • Governing law. Which country's law applies, and how you will try to settle a dispute before going to court.

Suing an agency in another country is slow and expensive, even when you are in the right. Your real protection is how the money and the work move. Pay in stages, review each stage on a staging site, and keep the domain and accounts in your own name. If things go wrong, you lose one stage and you still control your website.

Practical tips

  • Keep the contract short enough for both sides to actually read.
  • Write down decisions from calls in an email afterwards.
  • Ask for the code and a backup at each milestone, not only at the end.
  • If you run an agency, make sure the rights pass all the way from your developer to your client. See our guide on white-label development.

Our own standard terms are public, and anything we both sign takes priority over them. See how we work with clients in the US and UK, or read our guide on outsourcing web development to Pakistan.

Common questions

If I pay for a website, do I own it?

Not automatically. In both the US and the UK, the developer generally keeps the copyright unless it is transferred in writing. Make sure your contract includes a signed assignment.

Is a work-for-hire clause enough in the US?

Often not. For independent contractors, work for hire only applies to certain categories of work, and most websites do not clearly fit. Include a written copyright assignment as well.

Which country's law should the contract use?

Agree on one and write it down. Each side will usually prefer its own, and going to court across borders is slow and expensive either way, so milestone payments are your best practical protection.

You might also like