Most founders never read the fine print until something goes wrong. A website design contract is the one document that decides who owns your site, when it launches, and what happens when it breaks. Sign it blind and you can end up paying for a website you don’t actually own, delivered months late, with nobody answering the phone when it goes down.
This guide walks through every clause that matters before you pay: ownership, project scope, timelines, payment terms, revisions, and support. It applies whether you’re spending $499 or $50,000. The stakes scale, but the clauses don’t change. By the end you’ll know exactly what to demand in writing, what’s fair, and which red flags mean you should walk away.
Who owns your website? Get it in writing
Most clients assume they own the site because they paid for it. That is not always true. Some agencies keep ownership of the design, the code, or even the domain until final payment clears. A few keep it indefinitely, which means you are renting your own website.
Your contract must state that full ownership of all deliverables — design files, code, content, and database — transfers to you when the final payment is made. It should also say who registers the domain. The answer must be you, in your name, from day one. If the agency buys a premium theme, stock photos, or fonts on your behalf, the contract should clarify who holds those licenses after handover.
Look for the phrase “work for hire” or an IP assignment clause — that’s the legal language that makes the transfer airtight. Without it, copyright law in many countries defaults creative ownership to the creator, not the payer. Also ask about source files: some agencies hand over a working site but keep the original design files (Figma, Photoshop) hostage for future work. Get a written handover checklist covering admin logins, hosting access, analytics accounts, and all source files, delivered by a named date. Ownership disputes are the ugliest fights in web projects, and they are entirely preventable with one paragraph.
Define the project scope precisely
The scope section is where most disputes begin. “A five-page business website” means very different things to different people. List every page by name, every feature (contact form, booking calendar, blog, live chat, e-commerce cart), the platform (WordPress, Shopify, or custom code), and the design deliverables (homepage concept, inner-page templates, mobile versions).
Be explicit about content too. Who writes the text? Who supplies the photos? Many projects stall because the client thought copywriting was included and the agency thought the client would provide it. Add one more line that saves everyone: “Anything not listed here is a change request, quoted and approved separately.” That single sentence turns vague arguments into a clear process. If you’re comparing builders before hiring, our WordPress vs custom website guide explains which route fits which budget.

Timelines, milestones, and what “late” means
Vague timelines are a trap. A solid contract names a start date, dated milestones (design approval, development complete, content uploaded, launch), and who is responsible for each step. Realistic ranges help: a small business site takes three to six weeks, an online store six to twelve. If someone promises a full custom site in three days, be suspicious, not impressed.
Fair contracts also account for your delays. If you take three weeks to approve the homepage, the launch date moves by three weeks. Look for a feedback window — five business days is standard — and a clause that says milestones shift by the same number of days the client delays. On the agency side, ask what happens if they miss dates without a valid reason. A discount, a defined remedy, or at minimum the right to cancel are all reasonable. What you don’t want is a contract where only you have deadlines.
One more thing to pin down: communication. The contract should name your point of contact and a reasonable update rhythm — a short weekly progress note is enough for most projects. It should also define how approvals work: who on your side can sign off on designs, and what counts as approval (a reply saying “looks good” in email is fine; a thumbs-up emoji in a chat is not). Most timeline blowups aren’t caused by slow work. They’re caused by feedback loops where nobody knows whose turn it is.
Payment terms your website design contract should include
The standard structure is simple: a 30 to 50 percent deposit, one or two milestone payments, and a final 10 to 25 percent due at launch. Never pay 100 percent upfront. The contract should tie payments to delivered work, not to calendar dates — you pay when the design is approved, not “on the 15th.”
Insist on a fixed total price with no hidden fees, and get the hourly rate for out-of-scope work stated upfront so extras can’t be billed at mystery rates. The contract should also spell out refund terms: if you cancel halfway, what do you owe for completed work, and what deliverables do you keep? And if the agency cancels, what do they owe you? Paying by card or a platform with buyer protection beats a wire transfer every time. At Vibstack, we send fixed quotes within 24 hours — the number in the contract is the number you pay, and you can see our starting prices on the pricing page.
Support and maintenance after launch
Launch day is not the finish line. The contract must spell out a free bug-fix period — 30 to 90 days is standard — during which the agency fixes anything that doesn’t work as specified, at no charge. It should define what counts as a bug (a broken form) versus a new feature (adding a whole new page), because that line is where post-launch arguments live.
Ask about response times for urgent issues, especially if your site takes orders or bookings. Then look past the free period: what does an ongoing maintenance plan cost, and what does it include — updates, backups, security monitoring? If the agency hosts your site on their own servers, demand an exit plan in writing: how you get your files and database, and how long a migration takes. Founders who skip this clause sometimes discover they can’t move their site without the agency’s cooperation. Write the exit plan in before you ever need it.

Revisions, change requests, and extras
Design is subjective, so you will want changes. A fair contract includes two to three revision rounds per design stage — the homepage concept, then the inner pages, then final polish. That is enough room to get it right without endless rework.
The contract should separate revisions (tweaks within the agreed scope, like moving a button or trying a different headline) from change requests (new pages, new features, new functionality). Change requests need a written quote and your written approval before work begins. Without this distinction, “can you just add a small shop section” becomes a $2,000 surprise invoice. Since the hourly rate for extras is already in the contract from the payment section, quoting change requests stays honest and fast. If you’re planning a bigger overhaul rather than a fresh build, read our website redesign cost breakdown first.
Website design contract red flags: when to walk away
No contract at all is the biggest red flag — a professional who won’t put terms in writing won’t honor verbal promises either. Full payment demanded upfront, the agency keeping your domain or refusing to transfer admin access, and no named timeline or milestones all point the same direction.
Watch for a scope section that says “we’ll figure it out as we go,” no bug-fix period, and no termination clause. Be wary if they can’t show past work with real references, or if they pressure you to sign today for a “limited discount.” A legitimate agency answers hard questions calmly and has heard them all before. If they dodge, delay, or get defensive about standard clauses, thank them for their time and keep looking. The right contract protects both sides, and any agency worth hiring knows that.
Frequently asked questions
What should a website design contract include?
At minimum: ownership transfer, a detailed scope of work, timelines with milestones, payment terms, a revision policy, a free bug-fix period, support and maintenance terms, and a termination clause. These eight items cover nearly every dispute founders run into.
Who owns the website after I pay for it?
You should own it completely. The contract must state that all deliverables — design, code, content, and database — transfer to you on final payment. Also make sure the domain is registered in your name from day one, not the agency’s.
How much deposit should I pay a web designer?
A deposit of 30 to 50 percent is standard. Never pay 100 percent upfront. Tie the remaining payments to milestones: one at design approval, one at development completion, and the final balance at launch.
What is a fair bug-fix period after launch?
Thirty to ninety days is the industry standard. During that window the agency fixes anything that doesn’t work as specified, free of charge. New features or changes you request after launch are billed separately.
Can I cancel a website design contract?
Only cleanly if the contract has a termination clause, which is why you check before signing. It should say what you owe for work completed and which deliverables you keep. Without one, cancelling gets expensive and messy.
Do I need a website design contract for a small project?
Yes. Even a $499 site deserves a page of terms covering ownership, scope, price, and timeline. Small projects go wrong just as often as big ones, and a short contract protects both you and the designer.
Like what you just read?
Tell us about your project and get a clear, fixed quote within 24 hours — free, no obligation.
Get a free quote →