A website build agreement covers designing, building and launching a site: pages, CMS, rounds of changes, hosting handover and ownership. Describe your deal in a sentence and Lex drafts it, with Plain English beside every clause.
Draft this with Lex
Free for the other side
Lex drafts it in Plain English beside the legal wording. Share one link; both sides agree and sign.
What is a website build agreement?
A website build agreement covers a web design and development project from first concept to launch. Beyond scope and price, it usually deals with things specific to software: which browsers and devices are supported, who supplies content and when, acceptance testing before launch, third-party plugins and their licences, hosting and domain handover, and a bug-fix window after launch.
Also called: web design contract, website development agreement.
What are you deciding in a website build agreement?
Pages, templates, features and the CMS
Rounds of design changes included
Who supplies copy and images, and by when
Acceptance testing and the launch date
Ownership of code and design, and third-party licences
The clauses, in Plain English
Example wording Lex starts from, with what each clause means. Your draft is written around your deal, so the wording changes with it.
Legal wording · example
1Acceptance
The Client shall test the Website within [10] working days of notice that it is ready and either accept it or list defects. Silence after that period counts as acceptance.
In Plain English
The client has a set time to test and flag problems; if they say nothing, the site counts as accepted.
Legal wording · example
2Ownership
On payment in full, the Developer assigns to the Client all rights in the bespoke design and code. Third-party components remain subject to their own licences.
In Plain English
Once paid, the client owns the custom design and code. Plugins and libraries stay under their own licences.
The Developer will fix defects reported within [30] days of launch at no charge. After that, support is provided at [rate].
In Plain English
Bugs found in the first month after launch are fixed free; later support is paid.
Does the law where you are change a website build agreement?
The governing-law clause decides which legal system reads the contract. Some rules, such as how documents are signed, time limits for claims and terms that cannot be excluded, differ by place. These pages cite the legislation:
Is there a website build agreement file to download?
+
No, there is no blank Word or PDF file. You describe the deal in a sentence, Lex drafts the website build agreement with your details already in it, and you share one link. The other side reads it in Plain English, suggests changes and signs in the browser, free.
Who owns a website after it is built?
+
Whoever the contract says. Commonly the client owns the custom design and code on final payment, while the developer keeps reusable tools and third-party components stay under their own licences.
What if the client keeps asking for changes?
+
The agreement usually limits included rounds of changes and sets a rate or a change-request process for anything beyond. That is the main defence against scope creep.
Should hosting be in the same contract?
+
It can be, but ongoing hosting and maintenance are often a separate agreement or retainer, because they run after the build ends.