Web design contracts are drafted by people who’ve written dozens of them. Most clients sign one a handful of times in their lives. That information asymmetry tends to work out in the agency’s favor.
Negotiating a web design contract doesn’t mean being adversarial. It means knowing which clauses are boilerplate theater and which ones actually determine whether you own the thing you paid for. There’s a significant difference between the two.
Read the Ownership Clause First
Before anything else, find the intellectual property section. This clause determines who owns the website after you pay for it. Most clients assume they own it. Many contracts say otherwise.
Watch for language like “license to use” rather than “transfers ownership.” A license means the agency retains the underlying IP and grants you usage rights — rights that can be revoked or that expire if you stop paying a maintenance fee. That’s not ownership.
Push for explicit language: all design files, theme code, CSS, JavaScript, and database exports become the client’s sole property upon final payment. No caveats, no ongoing licensing, no withholding of source files.
What “Full Handoff” Should Actually Mean
A proper handoff includes:
- All theme and plugin files
- Complete database export (including content, users, settings)
- Any custom fonts or licensed assets used in the design
- Admin access to the WordPress installation
- Access to the hosting account, or clear documentation for migration
If the contract says “we’ll deliver the website” without specifying what that means, you don’t actually know what you’re getting. Ask for the handoff to be itemized.
The Scope of Work Is the Contract
Agencies spend more time on payment terms than on scope definition. That’s backwards for the client. The scope of work — what exactly will be built — is the document that determines whether you’re happy at the end.
Vague scope language is a setup for scope disputes. “Modern website with 5 pages” tells you almost nothing. Push for specifics:
- Page names and content requirements per page
- Functionality list (forms, filtering, booking, e-commerce features)
- Responsive breakpoints and device targets
- Integration list (CRM, analytics, payment gateway)
- Performance expectations (page load time, Lighthouse score targets)
- Number of revision rounds included
If an agency pushes back on specifying a Lighthouse score floor, that tells you something. We build every site to a PageSpeed score of 90+ and put that in writing because it’s achievable. Agencies who won’t commit to performance benchmarks usually know they can’t hit them.
James ran a dental practice in Atlanta. He signed a contract for a “custom website” at $6,200. The scope said “custom design, 6 pages, mobile responsive.” When the site launched, it was an Elementor build on a $59 theme. Nothing about the contract prevented it — nothing had specified what “custom design” meant. He had no recourse. The agency hadn’t technically lied. They’d just defined everything loosely enough to do whatever was cheapest.
Payment Terms: What’s Normal and What to Push Back On
Standard structure: 50% upfront, 50% on delivery. This is fair for both parties. The agency takes on risk in starting work; the client retains leverage at completion.
Red flags in payment terms:
- Large deposits (70–100%) before any work begins
- Payment milestones tied to vague internal events (“creative approval,” “design phase complete”) rather than deliverable acceptance
- Automatic renewal clauses on maintenance retainers with no cancellation notice window
- Kill fees that are disproportionate to work actually completed
Negotiate a clear acceptance process. “Final payment due on site launch” is not the same as “final payment due when client formally accepts the delivered work meets the agreed scope.” The second version gives you standing to raise issues before paying. Get it in writing.
If you talk to us about a project, we scope it with you, and payment structure, scope, and deliverables are agreed in writing before you commit. That removes most of the asymmetry.
Revision Rounds: Set a Number, Not a Vague Policy
“We include unlimited revisions until you’re satisfied” is not a policy — it’s a liability the agency will reclaim by defining “revision” so narrowly it’s meaningless. Or they’ll cut corners elsewhere to compensate for the open-ended time drain.
Better to negotiate a clear revision structure:
- X rounds of design revisions before final sign-off
- Y rounds of copy/content edits
- Defined hourly rate for out-of-scope changes
Three rounds of design revisions is standard for a competently scoped project. If you’re on round seven, either the brief was poor or the agency missed the brief — either way, that’s a scope and communication problem, not a revision problem.
Timelines and Delay Penalties
Most contracts include a project timeline. Almost none include consequences when the agency misses it.
You can negotiate a delay clause. It doesn’t need to be punitive — something like “if the project exceeds the agreed timeline by more than [X] weeks due to agency delays, the client may terminate the contract and receive a prorated refund of amounts paid for undelivered work.” Agencies who are confident in their delivery timeline won’t balk at this.
What you cannot negotiate around is your own responsibility for delays. If content delivery, feedback rounds, and approval sign-offs are on your side and you miss them, the timeline extends. That’s fair. Make sure the contract defines what the agency needs from you, and by when, to stay on track.
Maria launched an online clothing store in Chicago. Her agency contract had a 10-week timeline with a $15,000 budget. Week 14 came and went. Week 18, the agency said they were “just finishing up.” Week 23, she had a half-built WooCommerce site and an agency that was clearly underwater. Her contract had no delay terms, no milestone deliverables tied to payment, and no exit clause. She paid another developer $4,800 to rescue the build.
The Maintenance Retainer Trap
Many agencies build their business model on post-launch retainers — monthly fees for hosting, updates, backups, and support. These are sometimes legitimate, often padded, and occasionally structured to create lock-in.
Before signing a maintenance clause:
- Get an itemized breakdown of what the retainer covers
- Understand what happens to your site if you cancel (you should retain full access regardless)
- Ask what “updates” specifically means — plugin updates, WordPress core updates, security patches?
- Confirm the notice period for cancellation (30 days is standard; 90+ days is excessive)
A maintenance retainer should buy you a service, not hostage your own site. If cancelling the retainer means losing admin access or the agency “removing their work,” that’s not a service agreement — it’s a licensing structure dressed as one.
What Transparency Actually Looks Like in a Contract
The best contracts are short, specific, and readable. They don’t require a lawyer to decode. They say what will be built, who owns it, when payment is due, what happens if either party fails to deliver, and how the relationship ends.
Our custom WordPress development contracts are structured this way by default. No maintenance lock-in. No license retention. No vague scope.
If you want to assess your current site or a proposal against objective benchmarks before committing, Honest gives you an unbiased read on site health, performance, and risk — without a sales call attached to it.
FAQ
Is it normal to negotiate a web design contract? Yes. Most agencies expect it on larger projects. The key is knowing which terms matter and which are standard boilerplate. Ownership, scope definition, and payment milestones are the three areas worth pushing on in every contract.
What should I do if the agency won’t put ownership terms in writing? Walk away. If an agency is unwilling to commit in writing to you owning the thing you’re paying for, they have a reason for that reluctance. It’s not paperwork aversion — it’s a structural preference.
How much deposit is reasonable? 50% upfront is the industry standard for good reason. It gives the agency confidence to start work while you retain half your leverage until delivery. Anything above 60% upfront on a large project deserves scrutiny.
What does a scope of work need to cover? At minimum: page list, feature list, performance expectations, revision rounds, and what the final handoff includes. If you can’t describe exactly what will be delivered from the contract alone, the scope isn’t specific enough.
Can I add clauses to a web design contract? Yes. Contracts are negotiated documents. You can add delay penalty clauses, ownership confirmation language, specific performance benchmarks, and handoff itemization. Send your proposed additions in writing. An agency that refuses reasonable additions is telling you how they plan to handle disagreements later.