A web design contract needs, at minimum, a locked scope of work, a staged payment schedule with a non-refundable deposit, a defined revision limit, and clear IP transfer terms tied to final payment. Everything else is negotiable; those four are not.
This follows directly from pricing your projects and writing a winning proposal — a contract is what turns the price and scope you proposed into something legally enforceable if a client tries to renegotiate mid-project.
Why Freelancers Skip Contracts (And Why That's Expensive)
Early-career freelancers often skip contracts because a handshake feels sufficient with a client they like, or because drafting one feels like it slows down a deal. Both instincts are backwards. A contract isn't there for clients you trust — it's there for the 1 in 10 deals that goes sideways, and without one, you have no leverage when it does.
The Essential Clauses
1. Scope of Work (tied directly to your proposal)
The single biggest source of disputes. Reference the exact deliverables from your proposal, page by page, feature by feature — vague scope language ("a modern, professional website") is unenforceable when a client claims something wasn't included.
Include:
- Exact page count and names
- Specific features (contact form, e-commerce, booking, etc.)
- What's explicitly not included (content writing, stock photo licensing, ongoing hosting)
2. Payment Terms and Deposit
| Clause | Recommended term | |---|---| | Deposit | 40-50%, non-refundable once work begins | | Milestone payment | 25-30% at design approval | | Final payment | 20-25% before final files/access are delivered | | Late payment | Interest or a flat late fee after 7-14 days overdue | | Currency/method | Specify exactly — avoids disputes over exchange rate timing on international work |
The non-refundable deposit clause is what protects you if a client disappears mid-project. Without it, "the client ghosted" becomes a total loss instead of a partial one.
3. Revision Limits
State a specific number (2 rounds is standard) and define what counts as a "round." Without this, "just one more small change" repeats indefinitely and eats your margin. This is the single most common source of scope creep — a contract clause is your first line of defense against it, before it becomes a conversation you have to have mid-project.
4. Intellectual Property Transfer
Specify that full ownership of the final design and code transfers to the client only upon final payment — not upon delivery. This gives you leverage if a client tries to use the completed site without paying the final installment.
"All intellectual property rights in the final deliverables transfer to
the Client upon receipt of final payment in full. Prior to final
payment, all work product remains the property of [Your Business]."
5. Timeline and Client Responsiveness
Protect your own timeline commitments by making them conditional on the client meeting theirs:
"Delivery timelines assume client feedback and required assets (content, images, logo) are provided within 3 business days of request. Delays in client response extend the delivery date accordingly."
6. Termination Clause
Define what happens if either party wants out mid-project:
- Client-initiated termination: deposit is forfeited, plus payment for work completed to date
- Freelancer-initiated termination (rare, but cover it): pro-rated refund for undelivered work
7. Kill Fee for Cancelled Projects
If a client cancels after work has started but before completion, a kill fee (typically the deposit plus a percentage of remaining work completed) ensures you're compensated for time already spent, not just the deposit.
8. Confidentiality and Non-Disparagement (optional but useful)
For clients in competitive or sensitive industries (law, medical, finance), a mutual confidentiality clause is often expected and signals professionalism.
Contract Checklist
Use this before sending any contract for signature:
- [ ] Scope matches the proposal exactly, page by page
- [ ] Deposit percentage and non-refundable terms are explicit
- [ ] Payment schedule has specific dates or milestone triggers, not just percentages
- [ ] Revision limit is a specific number, with a defined cost for extra rounds
- [ ] IP transfer is tied to final payment, not delivery
- [ ] Timeline includes a clause protecting you from client delays
- [ ] Termination and kill fee terms are covered
- [ ] Governing jurisdiction is specified (matters for cross-border clients)
- [ ] Both parties' contact and business details are correct
- [ ] Signature and date fields for both parties
Mistakes to Avoid
- Using a generic contract template with no scope reference. A contract that doesn't name specific deliverables is nearly as weak as no contract at all.
- No jurisdiction clause on international work. If you're taking on clients outside your own country — a growing pattern as freelancers prospect further afield — specify which country's law governs disputes.
- Verbal scope changes. Any change to scope needs a written amendment, even a short email confirmation, or it doesn't hold up as agreed terms.
- Sending the contract after work has started. Get it signed before any work begins, always — including before the "quick mockup to show you my style" freebie that never gets formalized.
Where Contracts Fit Into Client Onboarding
A signed contract isn't the finish line — it's the first item in a proper onboarding sequence. See the client onboarding checklist for what comes immediately after signature, from asset collection to kickoff scheduling.
Contracts Protect Deals You've Already Won — Not Deals You Haven't Found
A strong contract protects the revenue you've already secured. It doesn't create new revenue. The freelancers who benefit most from tight contracts are the ones with a steady stream of qualified prospects to apply them to.
Runvax keeps that pipeline full — surfacing local businesses with no website so you're consistently signing new contracts, not just protecting the ones you already have.