What is a web development contract?
A web development contract covers building a site or application from agreed requirements. It addresses testing, acceptance, defects, hosting and who owns the code.
Use it when
- You build websites or web apps for clients.
- You want clear acceptance criteria and a bug-fix window.
- You need to explain what happens to the code, accounts and credentials at hand-over.
Do not use it when
- You are building something that handles regulated data, such as health or financial data, without expert advice.
- You work as the client's staff member on their team.
- You are hosting and maintaining the site long term. Add a retainer agreement.
What it covers
RequirementsA list or linked document of what will be built.
Milestones and acceptanceHow the client tests and approves each stage.
Defects and warrantyA fixed period to fix bugs and what is not covered.
Hosting and accountsWho sets up and pays for hosting, domains and services.
Third-party codeOpen source and licensed components used in the build.
Code ownershipWhat passes to the client and what you keep, such as your own libraries.
Security and backupsWhat you do and what the client is responsible for.
Limits on liabilityA cap tied to the fees, and no promise of uninterrupted operation.
A sample clause
Your contract is built from your answers. Parts in brackets are filled in by you. This is an example of the plain wording we use.
After each milestone, the Client has [five] business days to test the work and report defects in writing. The Freelancer will fix defects that do not match the agreed requirements. If the Client does not report defects within that time, the milestone is accepted and the next payment falls due.
Sample text for illustration. Not legal advice and not a complete contract.
Before you send it
- Write requirements as testable statements.
- Keep a short list of what is not included, such as content writing or ongoing updates.
- Hand over credentials through a password manager, not email.
Questions
Should I give a warranty?
A short bug-fix period for work that does not match the requirements is common. Avoid promising a site will be bug-free or always online.
Who owns the code?
Often the client owns the custom code on payment in full, and you keep your reusable tools. State it either way.
What about changes after launch?
Treat them as new work under a retainer or a change order.

