A web design contract is a written agreement that defines the scope, cost, timeline, ownership, and responsibilities of a website project. It protects both the client and the designer by setting clear expectations, limiting revision rounds, defining payment terms, and specifying who owns the final files and assets.
Key Takeaways
- A contract prevents the two most common project disputes: scope creep and payment delays.
- Define the deliverables precisely, including page count, revision rounds, and what is explicitly out of scope.
- Payment terms should include a deposit, milestone payments, and clear conditions for the final payment.
- Intellectual property and ownership clauses decide who controls the site, the files, and third-party assets after launch.
- A clear contract makes the working relationship easier, because both sides know exactly what was agreed.
Why Every Web Design Project Needs a Contract
A handshake agreement feels friendly until something goes wrong. Without a contract, a project lives in the gap between what the client imagined and what the designer planned. That gap is where disputes grow: the client expected five rounds of revisions, the designer planned for two; the client thought ecommerce was included, the designer scoped a brochure site.
A contract closes that gap. It is not about distrust. It is a shared reference document that both parties agreed to when everyone was calm and reasonable. When a disagreement arises mid-project, the contract answers the question instead of two people arguing from memory. For clients, it guarantees what they are paying for. For designers, it protects against unpaid scope expansion. Everyone benefits from clarity.
Project Scope and Deliverables
Scope is the heart of the contract and the source of most disputes. Vague scope is the enemy.
Define What Is Included
List the deliverables in concrete terms. State the exact number of unique page templates, for example a homepage, an about page, a services page, a blog template, and a contact page. Specify the platform, such as a website built in Framer. Note included features like contact forms, a content management setup, basic SEO configuration, and responsive design across desktop, tablet, and mobile.
Define What Is Excluded
Just as important, state what is not included. Common exclusions are copywriting, photography, logo design, ongoing maintenance, paid advertising setup, and third-party software costs. If the client wants any of these, they become a separate line item. Naming exclusions explicitly prevents the awkward conversation where a client assumes copywriting was part of the deal. Our website design process guide explains how scope fits into the overall project flow.
Revision Rounds
Specify how many revision rounds are included, typically two or three. Define what counts as a revision: a consolidated set of feedback, not an endless drip of individual change requests. State the hourly or per-round rate for revisions beyond the included amount. This single clause prevents the most common form of scope creep, the project that never ends because feedback never stops.
Payment Terms
Clear payment terms protect cash flow for the designer and budget certainty for the client.
Deposit and Milestones
Most agencies require a deposit before work begins, commonly 30 to 50 percent of the total. The deposit confirms commitment and covers early-stage work. Break the rest into milestone payments tied to deliverables: a payment when designs are approved, another when development is complete, and the final payment before the site goes live. Milestone payments keep the project moving and reduce risk for both sides.
Final Payment and Late Fees
State clearly that the final payment is due before the site is published to the client’s live domain or before final files are transferred. This is standard practice and protects the designer. Include a late payment clause specifying interest or a flat fee on overdue invoices, and the date a payment is considered late. Specify the currency and accepted payment methods. For context on how projects are typically priced, see our web design pricing guide.
Timeline and Responsibilities
A project has two parties, and delays are often caused by the client, not the designer.
Project Schedule
Include a realistic timeline with key milestones and dates. Make clear that the timeline assumes the client provides feedback and materials on schedule. State a reasonable response window for client feedback, for example five business days, after which the timeline shifts accordingly. This protects the designer from being blamed for delays caused by a slow client.
Client Responsibilities
List what the client must provide and when: brand assets, logo files, written content, images, access to domains and hosting, and timely feedback. If the contract does not name these obligations, a client who fails to deliver content can still expect an on-time launch. Spelling out client responsibilities makes the partnership genuinely two-sided.
Intellectual Property and Ownership
Ownership is one of the most overlooked and most important clauses.
Who Owns the Final Website
State clearly that ownership of the final website design transfers to the client upon receipt of full payment. Before final payment, the work remains the property of the designer. This protects the designer if a client disappears after the deposit, and it gives the client clear ownership once they have paid in full.
Third-Party Assets and Licensing
Websites use fonts, stock photos, icons, and sometimes plugins or templates that carry their own licenses. The contract should clarify that licensed third-party assets remain subject to their original licenses and that the client is responsible for ongoing license costs. Also address platform accounts. A Framer site lives on a Framer subscription, and the contract should state whether the client owns that account or the agency manages it.
Portfolio Rights
Most designers include a clause reserving the right to display the completed project in their portfolio and case studies. If a client needs confidentiality, that should be negotiated and noted explicitly.
Additional Clauses Worth Including
A few extra clauses prevent edge-case disputes.
Cancellation and Kill Fee
Define what happens if either party ends the project early. Typically the deposit is non-refundable, and the client pays for work completed up to the cancellation date. A kill fee compensates the designer for reserved time and lost opportunity.
Warranty and Bug Fixes
Offer a short warranty period, often 30 days after launch, during which you fix genuine bugs at no cost. Make clear that the warranty covers defects, not new features or design changes, which fall under a separate maintenance agreement. Our website maintenance cost guide explains how ongoing support is typically structured.
Limitation of Liability
Include a clause limiting the designer’s liability, usually capped at the total project fee. This is standard professional practice and prevents disproportionate claims over issues outside the designer’s control, such as third-party hosting outages.
How a Contract Improves the Client Relationship
A good contract is not a barrier between client and designer. It is the foundation of a calm, professional relationship. When expectations are written down, nobody has to guess. The client knows exactly what they are getting, what it costs, and when it arrives. The designer knows the scope is fixed and payment is structured. Both can focus on the actual work rather than negotiating from memory.
If you are choosing a web designer, the quality of their contract tells you a lot about how they run projects. A clear, fair, detailed contract signals an organized, experienced partner. Our guide on how to find a website designer covers what else to look for.
Looking for a web design partner who works with clear scope, fair contracts, and transparent pricing? We build fast, conversion-focused websites in Framer with a straightforward process from proposal to launch. Reach out to our team to discuss your project, or review our pricing to see exactly what is included.
Frequently Asked Questions
Do I really need a contract for a small website project?
Yes. Project size does not change the risk of misaligned expectations. A small project can still suffer scope creep, payment delays, and ownership confusion. A short, clear contract covering scope, payment, revisions, and ownership protects both parties regardless of budget and takes very little time to put in place.
Who owns the website after the project is finished?
In a well-written contract, ownership of the final website design transfers to the client once full payment is received. Before final payment, the work remains the designer’s property. Third-party assets like fonts and stock photos stay under their own licenses, and platform subscription accounts should be addressed separately.
How many revision rounds should a contract include?
Two or three rounds is standard for most web design projects. The contract should define what counts as a single round, usually one consolidated set of feedback, and state the rate for additional revisions beyond the included amount. This prevents endless change requests from stretching the project indefinitely.
What happens if a client cancels the project mid-way?
A cancellation clause handles this. Typically the deposit is non-refundable, and the client pays for all work completed up to the cancellation date. Some contracts also include a kill fee to compensate the designer for reserved time. These terms should be agreed and written into the contract before work begins.