You are about to have a website built. The conversations went well and the person across the table feels trustworthy. Then asking "shall we put this in writing?" feels almost rude. Yet anything that is not written down is remembered differently by everyone a few months later.
In this article I explain what a website contract, or at least a detailed written quote, should contain. I am not giving legal advice; I am giving you a list of questions to ask. Before you sign the final text, please show it to a lawyer.
Why does it need to be written?
In a spoken agreement both sides act in good faith but understand the same sentence differently. When you say "website," you may mean a booking form, phone layout and the text. The builder may have understood just an empty design. A written document is not there to blame anyone. It is there to make sure you are talking about the same thing.
Scope, timing and payment
Scope: what exactly will be done?
This is the most important part. Ask for these to be spelled out:
- How many pages, and which ones?
- Is mobile layout, meaning looking right on a phone, included?
- Is there a contact or booking form?
- Who prepares the text and photos?
- Are the basic settings that help the site be found on Google included?
- What is outside the scope?
The last point is very valuable. A list saying "the following is not included" prevents most later arguments.
Delivery date and process
Write down when the work starts and when it ends. But remember: delivery time does not depend only on the builder. If you hand over text, logo or photos late, the schedule slips. A good document sees both sides:
- Which materials are expected from you, and by when
- How a delay in materials affects the delivery date
- When interim steps, such as the first design draft, will be shown
Revisions: how many changes do you get?
A revision is a change you ask for after seeing the draft. Unlimited revisions sound nice but in practice drag the work out. A limited number can be fair as long as it is clear how they are counted. Ask:
- How many rounds of changes are included?
- Does a round mean one batch of notes sent together?
- How will big changes after design approval be handled?
Payment plan
Write down when and in which stages payment is made. You will need a number somewhere, but the topic here is structure, not figures. Look at:
- Is payment in one go or in stages?
- Which milestone triggers which payment?
- Will additional work get a separate quote?
Ownership and what you receive
Who holds the domain and hosting?
This heading is often skipped and later causes the biggest trouble. The domain is your site's internet address. Hosting is the place where the site's files are kept. Have these written down:
- Whose name will the domain be registered in? The right answer is yours.
- Whose name will the hosting account be opened in?
- Who tracks renewal dates and who sends the reminders?
- Who pays the renewal fees?
It is like the deed to a house. For years nothing happens, but the day you go separate ways, whoever holds the deed has the say.
What do you get at handover?
When the site goes live, what ends up in your hands? Put this list in the contract:
- Administrator login for the site
- Login details for the domain and hosting accounts
- Your copies of the logo, photo and design files
- A backup of the site
- A list of the template, plugins or third-party services used
- A short how-to-use guide
Also have it written clearly who holds the right to use the text, photos and design. If stock photos or a ready-made template were used, ask whether their license covers you. This part is a legal matter, so please ask a lawyer.
Support and cancellation
Support after launch
The job does not end the day the site goes live. Small glitches can appear in the first weeks. Clarify:
- Is there a free correction period after launch?
- How will small changes be charged afterwards?
- If the site does not open, whom do you contact and how soon should you expect a reply?
- Who does updates, backups and security work?
Cancellation and parting ways
Nobody likes thinking about it, but it is one of the most useful clauses. What happens if the job is left half done?
- If you back out, how is the work done so far settled?
- If the builder stops, will the prepared materials be handed to you?
- If there is a disagreement, how will you first try to talk it through?
It is safest to have a lawyer write or check these clauses.
Quick checklist
| Heading | The one sentence to ask |
|---|---|
| Scope | What is included and what is not? |
| Delivery date | What is expected from me and when? |
| Revisions | How many rounds of changes do I get? |
| Payment | What do I pay at which stage? |
| Ownership | Whose name are the domain and accounts in? |
| Handover | What will I have in hand at launch? |
| Support | Who looks after problems after launch? |
| Cancellation | What happens if the job stops halfway? |
Frequently asked questions
Do I need a contract for a small site too?
There is no rule that you do not. Even a short, clear written quote prevents most problems. Even for a small job, scope and ownership should be in writing.
Is a written quote the same as a contract?
No. A quote describes what will be done; a contract also binds both sides to their obligations. If your quote is detailed enough and approved by both, it may do the job, but ask a lawyer to be sure.
Which clause should I never skip?
In my experience, domain ownership and out-of-scope work are what get skipped most. Writing these two down avoids a large share of later problems.
Where do I get a contract?
The builder usually offers their own template. Read it, ask about anything you do not understand, and show it to a lawyer before you sign. You do not have to accept a ready-made text as it is.
Conclusion
A good written document comes from mutual clarity, not distrust. If you write down scope, dates, payment, ownership and support up front, both you and the builder can relax. Always show the final text to a lawyer. If you would like to plan your website together and pin down what gets written and how, you can reach me through my website design page.