Most web design contracts are written by agencies, for agencies. The default language protects the agency’s revenue, limits their liability, and leaves the client with vague protections that are difficult to enforce. Understanding which clauses matter — and how to negotiate them before you sign — is the difference between a project that goes well and one where you’re arguing about deliverables while your launch date passes.
This is not legal advice. It’s a practitioner’s guide to what contracts in this industry actually say and what should concern you.
Intellectual Property Assignment: The Most Critical Clause
Everything else in the contract is secondary to this. Who owns the work product — the design, the code, the custom theme, the database structure — determines whether you have an asset or a dependency when the project is done.
What you want: explicit IP assignment to you, triggered at a defined milestone. Typically: full assignment upon receipt of final payment.
What to watch for:
- “Work for hire” language is generally favorable — it means the agency creates the work as an employee-equivalent, and you own it
- Assignment language that’s conditional on future obligations — “IP transfers upon final payment and completion of any outstanding technical support requirements” — can be used to delay transfer indefinitely
- Blanket retention of design files — some agencies assign the built website but retain the design source files (Figma, Sketch, PSD). This means you own the deployed site but can’t modify the design without going back to them
Ask directly: “At what point does all intellectual property — code, design files, and assets — transfer to us?” Get the answer in writing, in the contract.
What you should never accept: “Agency retains ownership of all work product and grants Client a license to use.” This means you’re renting the website, not buying it. Any license can be revoked or conditioned. If you see this language, either negotiate it out or walk away.
Scope Definition: Where Budget Disputes Are Born
A contract with a vague scope is a liability. The scope section should reference a separate, attached document that lists every deliverable by name, every feature by description, and every explicit exclusion.
What strong scope language looks like:
- Deliverables listed by name with acceptance criteria defined
- An explicit list of what is NOT included
- A defined process for handling scope changes — who can authorize them, what documentation is required, and how the cost impact is communicated before work begins
- A statement that any change order must be in writing and signed before implementation
What weak scope language looks like:
- “A professional website of approximately X pages”
- “Standard design and development services”
- “Features as discussed” — this phrase should never appear in a contract
- Scope defined only in the proposal without being incorporated into the contract
If your scope is defined in a proposal that was sent before the contract, make sure the contract explicitly incorporates that proposal by reference. “As described in the proposal dated [date], attached hereto as Exhibit A” is the standard way to do this.
Kevin ran a dental group and signed a contract with a scope section that read “custom WordPress website with online booking.” When the developer delivered a site using a standard page builder template with a third-party booking plugin, Kevin objected. The agency’s position was that the scope didn’t specify custom code or a native booking build. Kevin’s attorney agreed that the language was ambiguous. The dispute settled at 60 cents on the dollar — less than Kevin deserved, more than he should have had to pay. Specific scope language would have prevented the dispute entirely.
Payment Schedule: Who Bears the Risk at Each Stage
Standard agency payment schedules: 50% deposit, 50% at launch. This structure is common, and it puts significant risk on the client — you’ve paid half before seeing anything.
A fairer payment schedule:
- 25–33% deposit to begin work
- 25–33% at design approval
- 25–33% at staging site delivery
- Remainder at final launch approval and handoff
This structure aligns payment milestones with delivery milestones. You release funds when the agency has proven they can deliver, not upfront on faith.
What to negotiate:
- Never pay the final installment until you have received all credentials, files, and documentation specified in the handoff checklist
- Add language that the final payment constitutes acceptance of all deliverables — and that you have X days to identify deficiencies before final payment is due
- Ensure that deposits are refundable, in part, if the agency fails to begin work within a specified timeframe
Our fixed-price packages structure payment around deliverable milestones. That’s not uncommon — it’s the right way to do it, and clients should require it regardless of which agency they’re working with.
Revision Rounds: Define Them Precisely
“Two rounds of revisions” is not a defined term until the contract specifies what constitutes a round. Without that definition, the agency can count a round any way that suits them.
What the contract should specify:
- What a revision round consists of — one consolidated batch of written feedback, one implementation cycle, one review
- What triggers a new round vs. what counts as a correction within an existing round
- Whether corrections to design or development errors (as opposed to client preferences) count against revision allowances
- The cost and process for additional rounds beyond the included number
Read the revision rounds guide for a detailed breakdown of how these cycles work in practice — understanding the mechanics makes the contract language easier to negotiate.
Termination Clause: Your Exit Rights
You should be able to exit the contract if the agency materially fails to perform. And the agency should be able to exit if you fail to make payments. Both sides need clear terms.
What the termination clause should include:
- Conditions that constitute material breach by either party
- Notice requirements before termination is triggered (typically 10–30 days written notice with an opportunity to cure)
- What happens to work completed at termination — who owns it, and what portions of the deposit are refundable
- A timeline for delivering all completed work product to the client upon termination
What to watch for:
- Language that makes it extremely difficult for you to terminate — requiring lengthy cure periods on issues that can’t be cured
- Termination clauses that allow the agency to keep the deposit in full, regardless of work completed, if you exit early
- No-compete provisions that restrict you from hiring another agency to complete the same type of project — these are occasionally present and should be struck
If you ever need to exit a contract mid-project, the guide to firing a web design agency covers the practical sequence.
Warranty and Defects: What Happens After Launch
A website is software. Software has bugs. The contract should specify what warranty period applies after launch, what constitutes a warranted defect, and what the remedy is.
Standard warranty language:
- 30–90 day post-launch warranty covering bugs, errors, and functional issues with the delivered scope
- Exclusions for issues caused by client modifications, hosting changes, or third-party plugin updates
- Clear process for reporting defects and expected response times
What to add:
- Performance guarantees, if the agency has committed to specific benchmarks (PageSpeed score, uptime, load time)
- Browser and device compatibility commitments — which browsers, which operating systems, which minimum viewport sizes
- ADA or WCAG compliance commitment if accessibility is a requirement
Elena hired an agency for a WooCommerce build and launched to find that the checkout process broke on iOS Safari — the browser used by nearly a third of her target demographic. The agency’s contract had no browser compatibility clause. Their position was that the issue was a “post-launch defect” and not covered by the warranty because it wasn’t discovered during staging review. After a two-week dispute, they fixed it. The time cost — two weeks of broken checkout on a live store — was not recoverable.
Liability Limitations: Know What the Cap Is
Most agency contracts include a limitation of liability clause that caps the agency’s financial exposure. The cap is typically the total project fee or a fraction of it.
This means: if the agency’s work causes you $100,000 in lost revenue — because a broken checkout prevented sales for a month — your contractual remedy may be limited to the project fee of $15,000 or less.
Liability caps are standard in the industry and largely unavoidable. What you should understand:
- What the cap is — know the number before you sign
- Whether consequential damages are excluded (lost profits, business interruption) — they almost always are
- Whether there are carve-outs for gross negligence or willful misconduct
For high-stakes projects where downtime is genuinely costly, have a business attorney review the liability section specifically. The cap may be negotiable.
Five Non-Negotiables Before Signing Any Web Design Contract
If you do nothing else, verify these five items before signing:
- IP assignment is explicit, triggered at a specific milestone, and includes design files — not just deployed code
- Scope is attached as a named exhibit with specific deliverables and explicit exclusions
- Termination rights allow you to exit with pro-rated refund of unearned fees upon material breach
- Final payment is not due until credential and file handoff is complete and accepted
- Revision rounds are defined in terms of what constitutes a round, not just how many are included
These aren’t exotic protections. They’re what a fair contract looks like. If an agency resists any of them, that resistance is a preview of how they’ll behave when something goes wrong during the build.
Frequently Asked Questions
Do I need a lawyer to review a web design contract? For projects under $10,000, probably not — the cost of review may exceed the stakes. For projects above $15,000, a 1–2 hour attorney review is worth $150–$400 and can identify clauses that would cost far more to deal with mid-project. At a minimum, read the contract yourself and flag any clause you don’t understand before signing. Agencies that resist explaining their own contract language are agencies you should be cautious about.
What should I do if the agency uses a standard template contract and won’t negotiate? Some smaller agencies use template contracts and have no legal infrastructure to negotiate custom terms. This isn’t automatically a red flag — but it means you’re accepting their standard terms. Read those terms. If something is specifically objectionable, raise it. Many agencies will amend individual clauses even if they won’t do a full negotiation. The willingness to discuss terms tells you something about the relationship quality.
Can I use my own contract instead of the agency’s? Yes. If you frequently hire contractors, it’s worth having a standard service agreement that your attorney has drafted. Many agencies will accept a client-provided contract, particularly for larger engagements. The practical challenge is that agencies are faster at processing their own paperwork — using your contract may add a week to the start of the project while they review it.
What does “work for hire” mean in a web design context? “Work for hire” is a US copyright concept that means the commissioned work is created as if the agency were your employee — meaning you own the copyright automatically, without a separate assignment clause. It’s favorable language for clients. However, it has specific legal requirements to apply, and for independent contractors, it requires explicit contractual agreement. Don’t assume work-for-hire applies unless the contract says so explicitly.
What’s the most common contract mistake clients make? Signing before reading. The second most common: treating the proposal as the contract. A proposal is a sales document. The contract is the legal agreement. When they conflict, the contract governs. If everything you were promised in the proposal isn’t in the contract, it doesn’t exist legally. Before signing, compare the contract against the proposal line by line and flag any discrepancy. See our website handoff guide for a parallel checklist of what the contract should commit the agency to deliver at project end.