Website Contract Basics for New Web Designers: What to Put in Writing
A simple website contract should put in writing who is involved, the scope of work, what the client must provide, the timeline, price and payment, revisions, approval and launch, ownership, hosting and domain costs, how the agreement ends, and what you do not promise. Use plain words, and ask a lawyer to review your draft.
Most website disputes are not about bad work. They are about two people who each thought something different had been agreed. A short, clear contract fixes that before it starts.
I have run a marketing agency for 15 years and worked with 100+ agency clients. Many of the arguments I have seen came down to something that was never written down: how many changes were included, who owned the domain, or who was waiting on whom.
This guide covers the parts a simple website contract should include, in plain words. I am not a lawyer and this is general information, not legal advice. At the end I explain when to ask a lawyer to look at your draft.
Why a contract matters even for a small job
A small business owner may feel a contract is too formal for a simple site. In fact, a short written agreement makes the owner feel safer. It shows you are serious and it tells them exactly what they will get.
For you, it is protection. If a client goes quiet, asks for far more than agreed, or disputes a payment, you have a document to point to. Without one, you have memories, and memories differ.
A contract can be one or two pages. It does not need heavy legal language. It does need to be specific.
The core clauses
1. Who is involved
Name both sides in full: your business and the client's business, with the person who has the authority to sign. Many small business owners are the only decision maker, but if a partner or family member also has a say, say so. Disputes often start when a second person appears late and wants changes.
2. Scope of work
This is the most important part. "Build a website" is not a scope. List what you will actually deliver:
- The pages, for example home, services, about and contact.
- Features, such as a contact form or a click to call button.
- What is not included, such as writing the text, taking photos, or running ads.
A clear list of exclusions is just as valuable as the list of inclusions. If the owner later asks for an online booking system, you can point to the scope and quote a new price, calmly and fairly.
3. What the client must provide
Websites are late most often because the client has not sent text, photos or logins. Write down what you need and by when. If you want a ready list, see the client website content checklist, and the guide on how to hand over a website to a client for the account and login side. You can say that if materials arrive late, the schedule moves by the same number of days.
4. Timeline
Give a realistic start date, a date for the first draft and a date for launch, tied to the client sending their materials. Avoid hard promises you cannot control. Say "within X days after I receive your materials."
5. Price and payment
State the total price, the schedule, the accepted methods and what happens if a payment is late. Common choices are a deposit up front with the balance at launch, or payments in stages. Pick what you are comfortable with and say it clearly.
Write the numbers in the contract, not in a separate email. If a monthly plan is included, show it as its own line with its own terms. The guide on the monthly website care plan shows what to include in that part.
6. Revisions
Decide how many rounds of changes are included, and define a round. A common approach is one or two rounds, where a round means one consolidated list of changes from the client. Extra rounds can be quoted at an hourly rate or as a new job. Without this clause, small requests keep arriving and the project never ends.
7. Approval and launch
Say how the client approves the work, for example by email or by a signed form, and that launch happens once the final payment is received. Note who is responsible for checking the site before it goes live. The proposal guide shows how to present these steps in a way an owner can follow.
8. Ownership
Be clear about who owns what, and when. A common arrangement is that the client owns the finished site, text and photos they supplied once paid in full, and that the domain is registered in the client's name from day one. Also say who owns anything you reuse across projects, such as a layout you built yourself. Check that you have the right to use any photos, fonts or tools you include.
9. Hosting, domain and ongoing costs
Say who pays for the domain, hosting and any paid tools, and who renews them. Many owners do not know these are separate costs. Spell out whether hosting is included in your price, billed separately or left to the client.
10. Ending the agreement
Explain what happens if either side stops the project. For example, the client pays for work done to date, and the deposit is non-refundable once work has started. Some places limit what you can keep, so choose terms that are fair to both sides and match the law where you live.
11. Results and promises
Add a line that you cannot promise search rankings, visitor numbers, calls or sales. This keeps both of you honest. It also keeps you from agreeing to something no one can control.
Here is what the main clauses protect, side by side.
| Clause | What it protects against |
|---|---|
| Scope of work | "Just one more page" requests that were never priced |
| What the client provides | Delays while you wait for text, photos and logins |
| Revisions | Small requests that keep arriving and never end |
| Ownership | Arguments over who owns the site and the domain |
| Hosting and ongoing costs | Surprise bills the owner did not know were separate |
| Results and promises | Agreeing to rankings, calls or sales no one controls |
Plain language wins
Write the contract the way you would explain it to a friend. Short sentences. Common words. If the owner can read it in five minutes and understand it, they are more likely to sign and less likely to argue later.
Avoid copying long legal text from random places. Terms that do not fit your situation can confuse the owner and cause problems of their own.
Using templates safely
Templates are a good start, not a final answer. If you use one:
- Remove clauses that do not apply to you.
- Change anything that does not match your actual process.
- Fill in every blank. A half-filled template looks careless.
- Read it again as if you were the client. Does it feel fair?
Laws about contracts, electronic signatures and consumer rights differ by country and by state. A template written for one place may not fit another.
Getting it signed
Many designers use a simple electronic signature service, or a scanned signed copy sent by email. Send the contract with the proposal, give the owner a day or two to read it, and answer questions kindly. Do not begin work until you have a signed agreement and the agreed deposit. Keep a copy of everything in a folder for each client.
When to ask a lawyer
Ask a lawyer to review your contract before you rely on it, especially if:
- You expect larger projects.
- You will sign with customers in other states or countries.
- You handle customer data, payments or regulated work.
- You plan to offer long term monthly services.
A one time review of your main template is often a modest cost compared with a single dispute. You can then reuse it for many clients.
Where SiteRevive fits
SiteRevive does not write or sign contracts for you. It helps with the step before that: finding local U.S. businesses with old or missing websites, checking each site, and taking the owner's email from the business's own website. You pick a trade and a U.S. state. With Run with your AI, you paste one prompt into your AI. It builds a one-page preview site for each business and drafts or sends a short first note from your own inbox. You can choose "drafts only."
If an owner says yes, the agreement, the price and the work that follows are yours to set. SiteRevive plans start at $97 a month, plus your own AI plan. There is a 7-day money-back guarantee, no questions asked. It does not promise replies or sales. SiteRevive's servers never send email; your own AI sends from your own account, or saves drafts. See the SiteRevive home page or try the free website check.
Frequently asked questions
Do I need a contract for a small website job?
A written agreement is strongly recommended, even for a small job. A one page agreement protects both sides by setting scope, payment and revisions so nothing is left to memory. This is general information, not legal advice.
What should a website contract include?
The parties, the scope and exclusions, what the client must supply, a timeline, price and payment terms, revisions, approval, ownership, hosting and domain costs, and how either side can end the work.
How many revisions should I include?
Many designers include one or two rounds, where a round is one combined list of changes. Extra rounds are quoted separately. Pick what suits your work and write it down.
Who should own the domain name?
Usually the client, registered in their name from the start, with you added as a helper if the registrar allows it. That avoids problems at handover. Ask a lawyer if your situation is unusual.
Can I use a free contract template?
You can use one as a starting point. Edit it to match your process and local law, and have a lawyer check your main version if the jobs are large.
Does SiteRevive provide contracts?
No. SiteRevive finds businesses and, with Run with your AI, has your own AI build a preview and draft or send the first note. Contracts and pricing are your decision. SiteRevive's servers never send email; your own AI sends from your own account, or saves drafts.