The Brief
What Questions Should Be in a Web Design Contract?
Eight clauses to insist on before you sign a web design contract. Miss any one of them and you're exposed. Written from the designer's side.
A founder sent me a contract last week to review before signing with another designer. Three sentences in I told him not to sign it.
The clauses that matter in a web design contract aren’t legal boilerplate. They’re the specific agreements that stop projects from going sideways. Missing any one of them and you’re exposed. I’ve seen each of these go badly for a founder who skipped it.
Here are the eight clauses to insist on before you sign anything.
1. Scope of work with specific deliverables
Not “a website.” Not “design and development.” A numbered list of every page the designer will deliver, every CMS collection they’ll build, every integration, every custom component.
Example of good scope: 1 homepage, 3 service pages, 1 pricing page, 1 contact page, 1 blog index, 1 blog detail template, 2 CMS collections (blog, testimonials), HubSpot form embed, Google Analytics setup.
Example of bad scope: “5-7 page marketing website.”
The vague version is where every scope-creep fight starts. The specific version makes additions easy to price separately.
2. Timeline with milestones, not just a launch date
A launch date alone tells you nothing about whether the project is on track. By the time you miss it, you’ve already lost two weeks.
Insist on milestone dates: strategy complete, wireframes approved, design v1 delivered, design approved, build complete, QA complete, launch. Each milestone has a date. Each milestone is tied to a payment.
If a milestone slips more than a week, you know early. You can renegotiate or walk away before you’ve paid for a project that isn’t coming.
3. Revision rounds — how many, what counts
“Revisions included” is not a clause. It’s a trap.
A proper clause specifies: 2 rounds of revisions on design, 2 rounds on build. Each round is defined (a consolidated list of changes from your side, not a drip of 20 Loom videos over three weeks). Additional rounds are quoted at a specific hourly rate.
This protects both sides. You know what you’re getting. The designer knows when they’re done.
4. Payment schedule tied to milestones
A standard split: 30% upfront to start, 40% at design approval, 30% at launch.
Avoid: 100% upfront (nothing is holding the designer accountable), or 100% on completion (nothing is holding you accountable). Both are failure modes.
Milestone-based payment keeps both sides committed. If the project stalls, both parties have reason to resolve it quickly.
5. Ownership of files and source documents
On final payment, you receive: the Framer project transferred to your account (or Webflow, or whatever platform), all Figma files with you as editor, all third-party service credentials, all CMS content.
If this clause is missing, the designer owns your website. You rent it from them. Every change requires them. If they disappear, your site is stuck.
A designer who resists this clause is telling you something about how they do business. Walk away.
6. Post-launch support window
Standard is 30 days of free bug fixes after launch. That covers things that broke due to the build, not things you want to change.
After 30 days, there should be clear hourly rate or a retainer option listed. You know in advance what ongoing work costs. The designer knows they’re not on the hook forever for a project that ended.
7. Termination clause
What happens if the project goes sideways? Can you walk away? Does the designer keep the files? Do you get a refund on unfinished work?
A fair termination clause: either party can terminate with 7 days notice. Payment is prorated based on completed milestones. You retain all deliverables completed and paid for.
Without this clause, you’re locked in. If the designer disappears or starts delivering bad work, you have no exit.
8. Confidentiality
Especially for AI and SaaS startups: your pre-launch product deserves an NDA. Pricing strategy, roadmap, unreleased features — all of it needs to be covered.
A one-page mutual NDA attached to the main contract is standard. If the designer resists signing one, they’ve either never worked with real companies or they don’t understand how yours operates.
The red flag clauses that shouldn’t be there
A clause giving the designer exclusive right to all future work on the site. (Lock-in disguised as a partnership.)
A clause letting the designer use your site in their portfolio without permission. (Especially bad for sensitive pre-launch work.)
A clause auto-renewing a retainer unless you cancel 90 days in advance. (Designed to catch founders who forgot.)
A clause that says “deliverables are final after approval” without defining what approval means. (Lets the designer claim you approved something you didn’t.)
How I contract
Every project I run starts with a scope document and a proper contract. Milestone payments. Framer project transfer on final payment. 30 days of free post-launch support. Mutual NDA signed before any confidential work.
If you’re about to sign a contract with another designer and want a second pair of eyes, send it over. Happy to review for free — takes 15 minutes and might save you from signing something you’ll regret.
New to Framer? 3 months free on the Pro plan with my referral: framer.link/framerexpert
New to Framer? Get 3 months free on the Pro plan when you sign up yearly with my referral link: framer.link/framerexpert or click the text here.
Keep reading