Free template

Website development agreement template

A website development agreement keeps a web project on track by pinning down the pages and features, the milestone payments, how the site is tested and accepted, and who owns the design and code at the end. Edit it in the browser and send it for signature from the same page; the free plan includes 5 sends a month and never asks for a card.

When to use it

  • A freelance developer or agency building a site for a small business.
  • A redesign where content, hosting and launch responsibilities need to be split clearly.
  • Any web project paid in milestones rather than one invoice.

What's in it

  1. 1.Project
  2. 2.Milestones and fees
  3. 3.Client content and access
  4. 4.Changes
  5. 5.Testing and acceptance
  6. 6.Hosting, domains and third-party services
  7. 7.Ownership
  8. 8.Warranty and support
  9. 9.Liability and termination
  10. 10.General

Plus signature, name and date fields for client and developer.

The full template

The text you start from, exactly as it opens in the editor. Bracketed blanks are yours to fill in; highlighted fields are filled by each signer.

Website Development Agreement

This Website Development Agreement (the “Agreement”) is made as of Date signed — Client between [Client name] (the “Client”) and [Developer name or studio] (the “Developer”).

1. Project

The Developer will design and build a website for the Client as described here: [pages, features, integrations, content management system, browsers and devices supported] (the “Website”).

Out of scope: [e.g. copywriting, photography, ongoing maintenance, search engine marketing].

2. Milestones and fees

Total fee: $[amount], payable as follows.

  • [Deposit, e.g. 40%] on signing: $[amount]

  • On approval of designs: $[amount]

  • On launch: $[amount]

Invoices are due within [fifteen (15)] days. Work may pause while an invoice is overdue.

3. Client content and access

The Client will supply text, images, logins and approvals by the dates in the project plan, and confirms it has the right to use everything it supplies. Late content may move the launch date.

4. Changes

The fee includes [two (2)] rounds of revisions at the design stage. Other changes to the scope are quoted in writing and start only once the Client approves the quote.

5. Testing and acceptance

Before launch the Developer will deliver the Website on a staging address. The Client has [ten (10)] business days to test it and report, in writing, anything that does not match this Agreement. The Developer will fix reported defects; a Website not rejected in that period, or launched at the Client's request, is accepted.

6. Hosting, domains and third-party services

Hosting, domain names, themes, plug-ins and paid services are [bought by the Client in its own name / supplied by the Developer and billed at cost]. They are subject to their providers' own terms, and the Developer is not responsible for their outages or changes.

7. Ownership

On full payment, the Client owns the Website's custom design and the content it supplied, and receives a perpetual license to use the code delivered. The Developer keeps its pre-existing code, libraries and tools, and open-source components remain under their own licenses. The Developer may show the Website in its portfolio unless the Client objects in writing.

8. Warranty and support

For [thirty (30)] days after launch the Developer will fix, at no charge, defects that cause the Website to differ from this Agreement. Ongoing maintenance after that is [not included / available at $[rate] per hour / covered by a separate support plan].

9. Liability and termination

Neither party is liable for indirect or consequential damages, and the Developer's total liability is limited to the fees paid. Either party may end this Agreement on written notice; the Client pays for work done to that date, and ownership transfers only for work paid for.

10. General

The Developer is an independent contractor. This Agreement is governed by the laws of the State of [State] and is the entire agreement on its subject.


Signatures

Client

Signature: Signature — Client

Name: Full name — Client

Date: Date signed — Client

Developer

Signature: Signature — Developer

Name: Full name — Developer

Date: Date signed — Developer

This template is a general-purpose starting point written in plain English for use in the United States. It is not legal advice and has not been reviewed for your situation; for anything high-stakes, have a lawyer review the final version.

How to send it for signature

  1. Step 1

    Start from the template

    It opens as a document in the editor with both parties' signature, name and date fields already placed. Fill in the bracketed blanks and change any clause.

  2. Step 2

    Add who signs

    Put an email address on each party, set the signing order if it matters, add an access code if you want one, and add a viewer for anyone who only needs to read it.

  3. Step 3

    Send it and track it

    Each signer gets a link and signs in the browser, no account needed. You see who has opened and signed, and everyone gets the completed PDF with a certificate of completion.

Questions

Who owns the website code?
In this template, the client owns the custom design and its own content on full payment and gets a perpetual license to the code. The developer keeps its reusable code and tools, and open-source parts stay under their own licenses.
How is the site accepted?
The developer delivers it on a staging address and the client has a set number of business days to report defects in writing. A site not rejected in that window, or launched at the client's request, is accepted.
Is ongoing maintenance included?
Only a short warranty period for defects. Maintenance after that is left for you to price in the agreement or a separate support plan.

Your own templates, too.

Save any document as a template for the team, with its parties and signature blocks, and start the next one from it in a click.