Web Design Contracts: 9 Clauses That Prevent Nightmares

By Cameron Kirdzik — Founder @WebHunt.ai

· 8 min read

A contract with nine highlighted clauses next to a laptop displaying a website prototype ready for approval.

TL;DR

  • Compressing builds to hours makes scope, timelines, and ownership the real risk—your contract must control those explicitly.
  • Use deposits, auto‑acceptance windows, and capped revisions to align with 24–72 hour delivery.
  • Change all “can we just…” into priced change orders with fixed fees tied to pages, features, and integrations.
  • Clients own the final paid deliverables; you retain process files and component libraries. Disclose third‑party and AI asset limits.
  • Add a kill fee and pause rules so content delays and early exits don’t nuke your calendar.

Why contracts matter more in the AI era (and what they must now do)

AI build tools (Framer AI, Replit, Lovable, Base44, v0, Bolt, Cursor, Windsurf, Codex Sites, Claude Design/Code) compress delivery from weeks to hours. That flips your risk profile. The project rarely blows up in production anymore; it blows up in scope creep, content delays, non‑payment, and unclear ownership. Your contract must explicitly control those.

Because you can credibly ship a pilot in 24–72 hours, align payment triggers and acceptance rules to rapid delivery: deposit before build, fast review windows, and auto‑acceptance if feedback stalls. Price pressure at the $0–$1,000 brochure tier means you can’t bankroll unlimited revisions. Lock counts, time‑boxes, and change‑order pricing.

Plain‑English wins. Your goal is operational clarity, not legalese. This is practical guidance, not legal advice. Run final language by your counsel.

Key takeaway: In the AI era, fulfillment is cheap; ambiguity is expensive. Contracts convert ambiguity into priced, time‑boxed steps.

Clause 1: Scope of Work (exactly what’s included — and excluded)

Spell out the deliverables you actually owe and what you do not.

  • Deliverables list: pages (Home, Services, About, Contact), features (contact form, booking link), and integrations (Google Maps, Calendly).
  • Out‑of‑scope examples to name: custom web app features, ongoing SEO/content, complex booking systems, copywriting beyond X words, brand identity beyond a basic style pass.
  • AI‑era twist: if you generate an initial draft via AI (Framer AI, Replit, Lovable), say it’s a starting point still bound by the page/feature list — not a blank check for more templates.

Sample language:

  • “Project includes up to 5 pages and 2 integrations listed above. Any additional page/feature requires a written change order and separate fee.”
  • “Initial AI‑generated draft is a prototype aligned to the agreed pages/features; further templates or theme explorations are out of scope unless added via change order.”

If you want a fast way to shape a concrete scope, WebHunt.ai can generate per‑lead AI opportunity briefs that audit a prospect’s current site and suggest a pitch angle. Use that to pre‑define pages, features, and exclusions before you ever send a proposal.

Clause 2: Change Control (how requests become paid change orders)

“Can we just add a gallery and a blog?” becomes a ticket, not a text. Define the pipe:

  1. Client requests in writing → 2) You evaluate impact → 3) You quote a fixed fee/time → 4) Client approves in writing → 5) You schedule.

Baseline prices (tie them to your AI‑enabled speed, not hourly ambiguity):

  • Additional page: $150–$300
  • New integration (e.g., Calendly, CRM form): $200–$500
  • New template variant/theme exploration: $75–$150

Protect the timeline: approved changes extend delivery. Work pauses until the change‑order deposit (e.g., 50%) is paid. AI‑era twist: fast iterations tempt “let’s just try it.” Require written approval and a change order before exploring a different visual theme, CMS switch, or major layout alternative.

Sample language:

  • “No change is performed without a signed change order. Approved changes extend the delivery date by the quoted amount and require a 50% deposit.”

Clause 3: Client Responsibilities, Content & Timeline

Make the client’s inputs (and dates) explicit.

  • Client must supply: logo files, brand colors, page copy, images, domain/DNS/hosting access, and credentials for third‑party tools.
  • Content deadline: “Client provides all content within 7 days of deposit.”
  • Delay guardrails: if content is late, project pauses; after 14 days of inactivity, a $100–$250 restart fee applies and timelines shift.
  • AI‑era twist: offer to generate placeholder copy/images via AI to keep momentum, but state placeholders auto‑publish if client doesn’t replace them within X days; client remains responsible for accuracy and approvals.

Sample language:

  • “Designer may use AI‑generated placeholder text/images to prevent schedule slips. Placeholders will be published if not replaced within 7 days of staging, and Client is solely responsible for final accuracy and approvals.”

Where to find clients who’ll actually hit deadlines? If you prefer pre‑qualified prospects, WebHunt.ai lists and scores local businesses by website weakness and buy‑likelihood, with filters by trade and city. That helps you prioritize owners likely to move quickly once you set content dates.

Clause 4: Payment Terms, Deposits, and Late Fees

Match cash flow to fast delivery.

  • Structure: 50–70% deposit to start; balance due on staging approval or 15 days from staging link delivery, whichever comes first.
  • Non‑refundable deposit: covers discovery, AI prototypes, and your reserved build slot.
  • Late payments: 1.5% per month interest or $25 minimum late fee after 15 days past due; work pauses on overdue balances.
  • Card/ACH handling: pass through processing fees (e.g., 2.9% + $0.30 per card transaction) if permitted in your jurisdiction and contractually disclosed 1.
  • Chargeback risk: clients may dispute card payments 60–120 days post‑charge depending on network; keep signed approvals and milestone logs 2.
  • AI‑era twist: same‑day or 48‑hour delivery applies only after deposit clears and domain/DNS access is on file; otherwise, timeline resets without penalty to you.

Sample language:

  • “Work begins upon receipt of a non‑refundable deposit of 60%. Remaining balance is due on staging approval or 15 days after the staging link is delivered, whichever occurs first.”
  • “Card payments incur the pass‑through processing fee disclosed at invoice time.”

Clause 5: Acceptance Criteria & Revisions

Define “done,” cap revisions, and time‑box reviews.

  • Done means: site matches agreed pages/features, loads without critical errors, forms submit correctly, and mobile layout renders within agreed breakpoints.
  • Revisions cap: 2 rounds of reasonable revisions on copy/layout for included pages. Substantial redesigns or extra rounds trigger change orders.
  • Time‑boxed review: client has 5 business days to submit changes per round; no response = auto‑acceptance and invoice triggers.
  • AI‑era twist: “design exploration” beyond the agreed wireframe or theme counts as a revision round or becomes a change order.
  • Accessibility target: aim for WCAG 2.1 Level AA where feasible; exclude client‑supplied content quality issues 3.

Sample language:

  • “Each revision round must be submitted as a single, consolidated list within 5 business days. Absent feedback, the deliverable is deemed accepted.”

Clause 6: Ownership, Licensing, and AI‑Generated Assets

Stop the post‑launch ownership tug‑of‑war.

  • Transfer on full payment: client owns the final site files/content you specifically create; you retain process files, internal components, and non‑exclusive libraries.
  • Third‑party licenses: name fonts, templates, icons, and libraries requiring ongoing client licenses/subscriptions (e.g., premium themes, font EULAs) 4.
  • AI assets: disclose if images/copy are AI‑generated; client is responsible for legal review and approvals. You warrant rights only as allowed by the tool’s terms.
  • Portfolio rights: you retain a perpetual, non‑exclusive right to display screenshots and anonymized results unless the client opts out in writing.
  • Prebuilt components: you may reuse your components elsewhere; no exclusivity unless purchased separately.

Sample language:

  • “Upon receipt of full payment, Client owns the final website output. Designer retains all working files, internal frameworks, and the right to reuse non‑client‑specific components.”

Clause 7: Hosting, Maintenance, and Limited Warranty

Draw the line between launch and forever.

  • Scope split: launch to the client’s host or to a named platform (e.g., Framer/Netlify). Ongoing hosting, backups, and uptime are excluded unless a maintenance plan is purchased.
  • 30‑day defect window: you’ll fix launch‑breaking bugs reported within 30 days at no charge. Changes or new features are billable.
  • Security/updates disclaimer: you’re not liable for third‑party outages, platform changes, or plugin/vendor issues; offer a paid maintenance SLA with response times.
  • Compliance disclaimers: you don’t provide legal compliance guarantees (GDPR/CCPA/ADA). You implement reasonable technical measures and accepted practices on request 5.

Sample language:

  • “Designer is not responsible for third‑party outages or platform updates outside Designer’s control. Optional Maintenance Plan available for backups, updates, and priority fixes.”

Clause 8: Termination, Pause, and Kill Fee

Protect your calendar and prototype work.

  • Mutual termination: either party may terminate for convenience with written notice; for cause after a 7‑day cure period.
  • Kill fee: if the client terminates, they pay for work performed plus 20–50% of the remaining contract to cover scheduling/opportunity cost; deposit is non‑refundable.
  • Pause rules: after 14 days of client inactivity, you may pause; after 30 days, you may terminate with a restart fee required to resume.
  • Deliverables on termination: once all amounts due (including kill fee) are paid, provide work‑in‑progress exports and access handoff notes.
  • AI‑era twist: prototypes are produced early; prototype access and transfer don’t occur until all amounts due are paid.

Sample language:

  • “If Client terminates for convenience, Client shall pay all work performed plus a kill fee equal to 30% of the unpaid contract value. Prototype access transfers only upon payment in full.”

Clause 9: Liability Caps, Indemnity, and Dispute Resolution

Cap risk and streamline resolution.

  • Liability cap: limit your total liability to the fees paid under the contract; exclude consequential damages (lost profits, business interruption).
  • Client content indemnity: client warrants rights to all content they supply and indemnifies you for claims arising from that content.
  • IP warranties: you warrant rights to materials you provide, subject to third‑party and AI‑tool license limits.
  • Venue/process: specify governing law, venue, and a low‑cost sequence (good‑faith negotiation → mediation → small‑claims or arbitration). Note small‑claims monetary limits vary by state; set venue where you operate.

Sample language:

  • “Designer’s total liability is limited to fees actually paid by Client under this Agreement. Neither party is liable for indirect or consequential damages.”

By the numbers: Most disputes aren’t about design quality—they’re about unclear scope, late content, and payment timing. Contracts price and time‑box all three.

Putting it together: pricing, closing, and red flags

Operationalize this into a 10‑minute close.

  • Template stack: build a base contract covering the 9 clauses plus an Exhibit A for scope/pricing. Duplicate and edit per deal.
  • AI‑era proofs: include a one‑page project brief, a same‑day AI‑generated draft screenshot, and a timeline tied to deposit/access receipt. Tools like Framer AI or Replit make the “preview in hours” promise real.
  • Red flags to walk away from: refuses a deposit, demands unlimited revisions, no single decision‑maker, or “we’ll get you content later.”
  • Negotiation tips: trade scope for price, not price for nothing. Offer a paid micro‑engagement (homepage draft) credited toward the full build.
  • Close‑clarity checklist: signed scope, deposit paid, content deadlines set, access granted, acceptance/revision rules acknowledged.

If you want to show a live draft fast without reinventing the brief, WebHunt.ai can generate a one‑click website prompt pre‑filled with the business’s real details for popular AI builders—handy for same‑day proof. And when you’re juggling multiple prospects, use WebHunt.ai deal pipeline and workflow to save leads, track stages, and export data so contracts and deposits don’t slip through cracks.

Bonus: if you prefer a fuller top‑of‑funnel, WebHunt.ai also offers a human cold‑calling marketplace and an AI Voice Agent SDR that books meetings straight to your calendar—useful when you’ve systematized your contract + delivery motion and just need more at‑bats.


This article is practical guidance, not legal advice. Laws vary by location; consult a qualified attorney to adapt clauses to your jurisdiction and services.

Frequently asked questions

Do I need a lawyer to write my web design contract, or can I use a template?

Start with a solid template that covers the 9 clauses here, then tailor the scope exhibit to each deal. For governing law, liability caps, and payment provisions, run your final draft past a local attorney. A one‑time legal review usually costs less than a single bad dispute.

How many revision rounds should I include in a web design contract?

Two rounds is the sweet spot for AI‑era builds: one for initial alignment, one for polish. Tie each round to a 5‑business‑day window and require consolidated feedback. Anything beyond that becomes a paid change order with fixed pricing.

What’s a reasonable kill fee for small web design projects?

For $0–$1,000 brochure sites, 20–30% of the remaining contract value is typical; for larger scopes, 30–50% is reasonable. The goal is to cover reserved capacity and opportunity cost once you’ve produced early prototypes. Make it explicit that deposits are non‑refundable.

Who owns AI-generated images or copy used in a client’s website?

Ownership depends on the tool’s terms and your contract. State that final paid deliverables transfer to the client, but you make no legal guarantees beyond rights allowed by the tool. Require the client to review and approve AI assets and to secure any necessary third‑party licenses.

How do I handle clients who delay content without losing the deal?

Set a 7‑day content deadline, use AI placeholders to maintain momentum, and add a restart fee after 14 days of inactivity. Make auto‑publish rules clear and keep tone supportive—offer a paid content add‑on if they want you to write or source assets.

Can I charge a processing fee for credit card payments in my state?

Many states allow pass‑through or surcharge models if you disclose fees and follow card‑network rules, but specifics vary. Put fee language in your contract and on invoices, and verify state and processor policies before charging any surcharge.

Sources

  1. 1 Average Credit Card Processing Fees 2026: 1.5%-3.5%
  2. 2 Chargeback Time Limits: 2026 Guide for Buyers & Sellers
  3. 3 WCAG 2.1 Explained: Complete Guide & AA Standard
  4. 4 Open Source Licenses
  5. 5 The Complete CCPA Compliance Guide (2026 Update)

About the author

Cameron Kirdzik — Founder @WebHunt.ai

Cameron is the founder of WebHunt.ai, where he helps web designers, agencies, and freelancers find local businesses that need a website. He writes practical, field-tested guides on prospecting and closing local clients.