A web design contract is the document that turns a verbal agreement and a friendly proposal into a real, enforceable working relationship. It defines what you're getting, what you're paying, who owns it at the end, and what happens when something goes wrong. Most clients skim it and sign. Read it carefully — it's the most important page of the project.

I'm David Campbell, founder of Nerd Stack. After nine years of agency engagements, the projects that go off the rails almost always do so because the contract was vague about something the parties later disagreed about. This guide covers what should be in a web design contract, what to negotiate, and the red flags worth pushing back on. Note: this is an overview for business owners, not legal advice — for a project of any meaningful size, have your attorney review the document. It pairs with our guide to choosing a web design agency.

What a Web Design Contract Actually Is

A web design contract — sometimes called a services agreement, a Statement of Work, or a Master Services Agreement plus an SOW — is the binding written agreement between you and the agency or freelancer. It governs the entire project: what gets built, on what schedule, for what fee, with what rights at the end. Anything you and the agency talked about that isn't in the contract is, when push comes to shove, not in the deal.

That's not because agencies are out to get you. It's because human memory is unreliable; whatever you remember six months in won't match what they remember. The contract is what you both can point to.

The Essentials Every Web Design Contract Should Cover

  • Scope of work. A specific description of what's being built — pages, features, deliverables — written clearly enough that two outside readers would agree on what's included. Vague scope is the single biggest cause of project conflict.
  • Deliverables. The concrete artifacts the agency will hand over — designs, the live site, source files, documentation, training. List them by name.
  • Timeline and milestones. Key dates and what triggers each milestone. "Launch within 12 weeks" is weaker than a milestone schedule with named deliverables.
  • Fees and payment schedule. The total fee and how it's broken into milestone payments. A typical structure is 30–50% up front, milestone payments, and a final payment at launch.
  • Revisions. How many rounds of revisions are included at each stage, and what happens after — usually billed hourly or as a change order.
  • Change orders. The process for adding scope mid-project: how it's requested, priced, and approved.
  • Intellectual property ownership. Who owns the final website, the design files, and the source code at the end of the project — and at what point ownership transfers (usually on final payment).
  • Third-party assets. Who's responsible for licensing stock photos, fonts, plugins, or any third-party material used in the build.
  • Hosting and post-launch. What happens at launch — who hosts, who maintains, what's included for how long, and what costs extra after.
  • Termination. How either party can end the relationship if needed, on what notice, and what happens to in-progress work and money already paid.
  • Warranties and limits of liability. What the agency warrants the work to be, and the cap on their liability if something goes wrong.
  • Confidentiality. Both directions — neither party can blab about the other's business.

The Single Most Important Clause

If you read only one part of a web design contract carefully, read the intellectual property clause. It decides whether, at the end of the project, you fully own the website your business now depends on — or whether the agency does, and is licensing it to you.

You want a clean transfer on final payment of:

  • The final website (code, content, design as delivered).
  • Design files (Figma, Photoshop, etc.) in editable formats.
  • Any custom code, templates, or assets created specifically for your project.

The agency may legitimately retain rights to their own pre-existing frameworks, libraries, and standard components — that's normal. What you shouldn't accept is the agency owning your custom build and only "licensing" it to you. That's a vendor lock-in arrangement masquerading as a project, and it gets ugly the first time you want to move agencies.

Payment Schedules: What's Normal

The structure of payment in a web design contract is more standardized than it looks. Common patterns:

  • 30–50% deposit on signing. A real agency will not take all of the money up front, but they will require a meaningful deposit. 100% deposit is a red flag; a small or zero deposit is also unusual.
  • Milestone payments tied to deliverables. Discovery complete, designs approved, development complete, launch — each unlocking a portion of the fee.
  • Final payment at launch. Withholding 10–20% of the fee until launch is reasonable on both sides — it gives the agency a clear finish line and gives you leverage that the project gets actually finished.

Watch for: payment schedules with no clear milestones (just "every 30 days"); schedules that demand the entire balance before the site goes live (you lose all leverage); or hourly billing without a cap (a fixed-scope project should be fixed-fee or hourly with a ceiling).

Contract Red Flags Worth Pushing Back On

  • Vague scope. "A modern website" is not scope. If you can't tell from the contract what's being built, the project will not be on time or on budget.
  • Auto-renewing maintenance. A maintenance plan that automatically renews on the same terms every year, without an explicit opt-in. Maintenance should renew on your decision, not by default.
  • "All rights reserved by agency." Some contracts have the agency retaining ownership of your custom build. Decline.
  • One-sided indemnification. Indemnification clauses should be mutual — you indemnify them for misuse of their work, they indemnify you for their infringement of someone else's. One-direction indemnification is a vendor protecting itself at your expense.
  • Unlimited liability for the client. Limits of liability should be balanced. An agency that caps its own liability at "the fees paid" while leaving yours unlimited is not negotiating in good faith.
  • Mandatory long-term lock-in. A project contract with multi-year exclusive ongoing obligations should give you pause.

What's Reasonable to Negotiate

Web design contracts are negotiable — most agencies expect at least some pushback on specifics. Reasonable asks:

  • More clarity on scope. Always reasonable. "Can you list specifically what's included on the homepage?" is a fair request.
  • Mutual revision rounds. If you're getting two rounds of revisions, make sure the agency can use them productively too.
  • Payment milestones tied to specific deliverables. "Final payment at launch" is fairer than "final payment 60 days from signing regardless of launch."
  • IP transfer on final payment. Not a negotiation, really — but if it's not in the contract, ask for it.
  • Mutual NDAs and indemnification. Always make confidentiality and indemnification clauses mutual.

Frequently Asked Questions

Do I need a contract for a small web design project?

Yes — even for a small project. A short, clear contract protects both sides and prevents the most common project disputes (scope creep, late payment, IP confusion). For a small project the contract can be shorter, but it shouldn't be absent.

Who owns my website when the project is done?

You should — the contract should transfer the final website (code, content, custom design) to you on final payment. The agency may retain rights to their own pre-existing frameworks and libraries, which is normal. What you shouldn't accept is the agency owning your custom build and only licensing it to you.

How much should I pay upfront for a web design project?

A typical deposit is 30–50% of the total fee on signing. Anything close to 100% is a red flag; a deposit much smaller than that is also unusual. The remaining balance is paid against milestones, with the final portion at launch.

What are the biggest red flags in a web design contract?

Vague scope, the agency retaining ownership of your custom build, one-sided indemnification or liability caps, payment schedules with no clear milestones, and auto-renewing maintenance plans. None are necessarily deal-breakers, but each is worth pushing back on.

Should I have a lawyer review my web design contract?

For any project of meaningful size, yes. The cost of legal review is small relative to the project, and an experienced lawyer will catch terms you wouldn't. This blog post is an overview, not legal advice — for actual review, use an actual lawyer.

Bottom Line

A web design contract is the moment all the friendly conversation gets turned into something real. Read it carefully — especially the scope, IP, payment, and termination clauses — push back on anything that's vague or one-sided, and have your attorney look at it before you sign on a meaningful project. A good agency will negotiate in good faith on the things that should be balanced; one that won't has told you something useful about how the project itself will go.

We use clear, balanced contracts at Nerd Stack — fixed scope, milestone payments, IP transfer on final payment, no surprises. See our web design service or book a free call.

Sources: AIGA — Standard Form of Agreement for Design Services.