A bad web design contract doesn’t just lose you money — it hands the client leverage at every disagreement. The good news: most disputes are predictable, and a well-drafted contract eliminates nearly all of them before the project starts. This guide walks through every clause that matters, why it matters, and the exact language patterns that hold up when things go sideways.
Why Most Freelance Contracts Fail
The typical freelance contract downloaded from a template site covers payment and deliverables — and almost nothing else. It leaves silent the questions that actually cause disputes:
- What counts as a “revision”?
- Who owns the work if the client never pays the final invoice?
- What happens if the client ghosts for six weeks?
- Can the client resell or white-label your work?
Silence in a contract is interpreted against the drafter in most common-law jurisdictions. That means you lose the ambiguous argument, not the client.
The 9 Clauses Every Web Design Contract Needs
1. Scope of Work — With a Hard Boundary
Describe deliverables in output terms, not effort terms. “Five-page WordPress site with the pages listed in Exhibit A” is enforceable. “A professional website” is not.
Attach a separate Exhibit A (or Statement of Work) that lists every page, feature, and integration explicitly. Then add: “Any work not listed in Exhibit A is out of scope and subject to a separate change order.”
This single sentence is the most valuable sentence in your contract.
2. Revision Rounds — Defined and Capped
Define what a revision is. A common working definition: a revision is a change to approved work that does not alter the agreed scope. Cap the number of rounds (two is standard for most projects). State that additional rounds are billed at your hourly rate.
Also define what triggers a new revision round — typically client feedback submitted within a specified window (five business days is reasonable).
3. Client Responsibilities and Response Windows
This is the clause most designers forget. List exactly what the client must provide and by when: brand assets, copy, logins, feedback approvals. Then add a stall clause: “If client fails to provide required materials or feedback within 10 business days, the project timeline adjusts accordingly, and ProjEvo may invoice for work completed to date.”
Without this, a client who disappears for two months can come back and claim you missed the deadline.
4. Payment Schedule and Late Fees
Never start work without a deposit. Standard structures:
| Project Size | Deposit | Mid-Point | Completion |
|---|---|---|---|
| Under $3,000 | 50% | — | 50% |
| $3,000–$10,000 | 33% | 33% | 34% |
| Over $10,000 | 25% | 25% | 25% |
Specify a late fee (1.5%/month is common and legally defensible in most US states). More importantly, state that late payment suspends your obligation to deliver — this prevents clients from withholding final payment while demanding continued work.
5. Kill Fee
If a client cancels mid-project, you’ve already spent time. A kill fee clause ensures you’re compensated. A workable structure: all payments made to date are non-refundable, plus a kill fee equal to 25% of the remaining contract value.
Frame it as mutual protection — you also agree not to abandon the project without notice.
6. Intellectual Property Transfer
Under US copyright law, work created by an independent contractor is not automatically a work-for-hire — the client does not own it unless the contract says so. This is leverage, and you should use it deliberately.
Two common approaches:
- Full transfer on final payment: Clean, client-friendly, standard for most projects.
- License until paid in full: You retain copyright until the final invoice clears. This is a powerful collection tool — a client who publishes your work before paying has infringed your copyright.
Whichever you choose, be explicit. Ambiguity defaults to you retaining ownership, but litigating that point is expensive.
7. Hosting, Maintenance, and Post-Launch Scope
Launching a site is not the same as maintaining it. Your contract should state clearly: “Support and maintenance after launch are not included unless covered by a separate maintenance agreement.”
If you offer ongoing hosting or support — which is worth doing for recurring revenue — document it in a separate addendum with its own payment terms. Platforms like ProjEvo let you attach recurring billing directly to a client’s project record, so the handoff from project to retainer is automatic rather than an awkward separate conversation.
Billing
Invoice and subscribe your clients through Stripe or PayPal.
$0
$0
$0
$0
$0
$0
Website care — Pro
renews Jul 6
Hosting — Growth
renews Jul 12
SEO retainer
renews Oct 29
Website care — Lite
renews Jul 2
Auto-billing on — recurring invoices generate and charge on schedule via Stripe & PayPal.
8. Dispute Resolution
Specify governing law (your state/country) and preferred resolution method. Mandatory arbitration clauses are enforceable in most US states and dramatically cheaper than litigation. At minimum, specify that disputes are resolved in your jurisdiction — not the client’s.
9. Portfolio and Credit Rights
Reserve the right to display the finished work in your portfolio and case studies unless the client requests confidentiality in writing. Clients rarely object when it’s in the contract upfront; they often object retroactively when they see your case study.
The Change Order Process
A contract without a change order process is incomplete. When out-of-scope requests come in — and they will — you need a documented workflow:
- Client requests change verbally or in writing
- You respond with a written change order: scope, cost, timeline impact
- Client signs (or approves via email with explicit confirmation)
- Work begins only after approval
This process protects you legally and trains clients to respect scope boundaries. Keeping change orders inside your project management system (rather than scattered across email threads) makes disputes nearly impossible — you have a timestamped paper trail. See how a structured client portal supports this in our post on client portal vs project management software.
Common Mistakes to Avoid
Relying on email threads as your contract. Email exchanges can form a contract in some jurisdictions, but they’re hard to enforce and easy to misread. Always get a signed document.
Vague deliverable language. “Modern design” and “clean layout” are not deliverables. Page count, feature list, and platform are.
No expiry on the proposal. If your proposal has no expiry date, a client can accept it 18 months later at your old pricing. Add a 30-day expiry.
Forgetting third-party licenses. If you use stock photos, premium plugins, or licensed fonts, specify whether those licenses are included in your fee or billed separately. The GPL license governing WordPress themes and plugins has specific implications for commercial work — know them.
Getting Contracts Signed and Stored
A contract that lives in your email drafts doesn’t protect you. Your workflow should be: draft → send for e-signature → store alongside the project record. When your contract, invoices, and project timeline all live in the same place, you can pull up the full client history in seconds if a dispute arises.
For a broader look at how your tooling choices affect operational risk, see our agency software cost teardown and the guide to consolidating your tech stack.
One-Page Contract vs. Full Agreement
For small projects under $1,500, a one-page letter of agreement covering scope, payment, revisions, and IP transfer is usually sufficient. For anything larger, use a full agreement with the nine clauses above. The time investment is the same — the protection is not.