Web Design Contract Template for Freelancers: What to Include and Why

Web Design Contract Template for Freelancers: What to Include and Why

A web design contract is the single most important document between you and your client. It defines what you'll build, what it costs, when you get paid, and what happens when things go sideways — and things always go sideways eventually. Without one, you're gambling your time, your money, and sometimes your sanity.

This guide covers every clause you need in a freelance web design contract, why each one matters, and a few things most contract templates miss entirely.

Why Most Freelancers Skip the Contract (And Regret It)

Let's be real: contracts feel like friction. You've got a warm lead, the client is excited, you want to just start building. Writing up a legal document feels like it slows everything down and maybe even signals that you don't trust the client.

Here's what actually happens without a contract:

You're three weeks in, the client decides the scope has "always included" an e-commerce section you never discussed. You say it wasn't in scope, they say it was implied. You have nothing to point to.

Or: you deliver the final site, invoice the client, and suddenly they're "not happy with the direction" and want to start over. You've done 40 hours of work and now you're negotiating from zero.

Or the classic: the project drags for six months because the client never gets around to providing content. You've got your development environment frozen waiting for their copy. Your time is gone.

None of these are hypothetical. Every freelance web designer has one of these stories — usually several. A contract doesn't prevent difficult clients, but it changes the conversation. Instead of arguing about what was agreed, you're looking at a document you both signed.

The 10 Clauses Every Web Design Contract Needs

1. Scope of Work

This is the most important section. Be specific to the point of feeling slightly paranoid. Don't write "design and develop a website." Write:

• Five-page website (Home, About, Services, Portfolio, Contact)
• Built on Webflow, hosted on Webflow's Basic plan
• One round of revisions per page after initial design delivery
• Mobile-responsive design based on provided brand guidelines
• Contact form with email notification (no backend database)

Whatever is not listed here is not included. That's the whole point. When the client asks for a sixth page in week three, you can open the contract and say: "That's outside the original scope — I'd love to add it, here's what it costs."

2. Deliverables and Timeline

Define what you're handing over and when. A good deliverables section has two parts:

What you deliver: The finished website, source files (or not — this is your call), CMS documentation, any brand assets you create, login credentials.

When you deliver it: Break the project into milestones. "Discovery + wireframes by [date]. Design mockups by [date]. Development complete by [date]. Launch by [date]." Milestones also tie to payment (more on that below).

Important: build in a clause that says the timeline assumes the client provides required materials (content, images, brand files, feedback) within a specified window — typically 5–7 business days. If they don't, the timeline shifts. This one clause alone will save you months of calendar stress.

3. Revision Policy

This section stops the endless revision spiral. The most common version:

"Two rounds of revisions are included per project phase. A revision round is defined as a consolidated list of changes submitted at one time. Additional revision rounds are billed at [your hourly rate] per hour."

Three things to get right here:

First, define what a "revision" is. Changing a button color is a revision. Adding an entirely new section to a page is a scope change. Put that distinction in writing.

Second, specify how revisions are submitted. Not via WhatsApp. Not across four emails. One consolidated list, submitted through an agreed channel. (This is also where a visual feedback tool like dotts earns its place — clients click directly on the live site and leave pinned comments, so you get structured feedback instead of a photo of a laptop screen with a Post-it note.)

Third, set a window. Revisions submitted after 30 days of delivery are out of scope. This protects you from clients who go quiet for three months and then want to reopen design discussions.

4. Payment Terms

Freelancers lose more money to bad payment terms than almost anything else. Here's a structure that works:

• 50% upfront before any work begins
• 25% at a defined midpoint (design approval, for example)
• 25% on delivery — before the client gets login access or the site goes live

That last point matters. Don't hand over access and then wait for payment. Payment on delivery means payment before the keys change hands.

Also include:

• Invoice due date (net 7 or net 14 — not net 30, you're not a bank)
• Late payment fee (e.g., 1.5% per month after the due date)
• Accepted payment methods (bank transfer, Stripe, PayPal — whatever you use)

If a client pushes back on the upfront deposit, that's useful information. It usually means one of two things: they don't have the budget, or they don't see this as a committed project yet. Either way, you want to know before you start.

5. Content Responsibility

One of the most overlooked clauses. Your contract should state clearly that the client is responsible for providing all written content, images, and media by a specified date. If they miss the deadline, the project timeline adjusts accordingly.

Also include a clause stating that the client is responsible for ensuring they have legal rights to any content they provide — text, photos, logos, fonts. You don't want to be caught in a copyright dispute because a client grabbed stock images from Google.

6. Intellectual Property and Ownership

This one surprises new freelancers. Until you explicitly transfer ownership, you technically own the work you create. Your contract should clarify:

• When ownership transfers (typically: when the client has paid in full)
• Whether you retain the right to show the project in your portfolio
• Whether you're providing source files (Figma files, PSD files, etc.) or only the final output

Most freelancers include a clause retaining portfolio rights. Some clients — especially in finance or healthcare — will want to remove that. If so, it's a negotiation point, not something you just give away.

7. Confidentiality

If you're working on something before launch — a product, a rebrand, a new service — the client may not want it public. A simple non-disclosure clause handles this. You agree not to share, publish, or reference any confidential project information until the client gives the green light (or after a defined embargo period).

This also works the other way: if you share your internal processes, pricing structures, or any proprietary materials during the project, you can include a mutual NDA that protects both parties.

8. Cancellation and Kill Fee

Projects get cancelled. Sometimes it's the client's budget. Sometimes the business pivots. Sometimes you've both decided this isn't working.

A kill fee clause defines what happens financially when that occurs. A standard approach:

• If cancelled before work begins: deposit is non-refundable
• If cancelled after work begins: client pays for all work completed, plus a cancellation fee (often 20–25% of the remaining contract value)

Without this clause, you might deliver three weeks of work and walk away with nothing but the deposit.

9. Warranties and Liability Limitations

You're guaranteeing that your work functions as described. You're not guaranteeing that it'll rank #1 on Google, convert at a specific rate, or survive every possible browser and device combination into perpetuity.

Your contract should limit your liability to the value of the contract. If a client claims your website caused them $50,000 in lost business, you don't want to be on the hook for that without this clause.

Also include: you're not responsible for issues caused by third-party services (hosting, Stripe, Mailchimp, etc.), or for changes the client makes to the site after delivery.

10. Dispute Resolution

If things go really wrong, how do you handle it? Most freelancers include a clause specifying that disputes are resolved through mediation or arbitration rather than court (which is expensive and slow), and that disputes are governed by the laws of a specific jurisdiction.

You don't need to be a lawyer to include this. You just need to pick a jurisdiction (usually where you're based), and specify the resolution process. Most disputes with clear contracts never get to this stage — the clause's main value is demonstrating that you've thought this through.

What a Contract Can't Do

A contract is not a substitute for judgment. If a client gives you bad vibes during the sales call — vague about budget, dismissive about timelines, mentions they've "been through three designers already" — a contract won't fix that relationship. It just makes the eventual fallout slightly cleaner.

The best use of a contract is with clients you want to work with, to protect a working relationship from the natural friction that complex projects create. It's not a weapon — it's a shared reference point.

A Real-World Example

Sara is a freelance web designer based in Berlin. She builds Webflow sites for local businesses — cafés, consultants, small agencies.

Before she started using a proper contract, she had a recurring nightmare: clients would request "just a few small changes" for weeks after delivery, eating into her margin on every project. She'd spend an extra 5–10 hours per client on unpaid revisions because she didn't have anything to point to.

After implementing a contract with a defined revision policy and a clear scope of work, the dynamic shifted. When a client asked for a fifth revision round, she replied: "Happy to do that — we've used our two included rounds, so this will be billed at my hourly rate of €85/hour. Shall I send an addendum?" The client said yes. She's been doing this for two years now and that awkward conversation never gets easier — but the outcome is always fair.

She also uses dotts to collect revision requests. Clients click directly on the live site and leave pinned comments, which means each revision round is clearly documented with timestamps. If there's ever a dispute about how many rounds were submitted, she has a full record.

The Simplest Way to Start

If you don't have a contract at all, here's the minimum viable version:

1. Scope of work — What are you building, specifically
2. Payment terms — How much, when, and what happens if it's late
3. Revision policy — How many rounds, what counts as a round
4. Timeline and content deadline — When you deliver, and when the client must deliver materials to you
5. Ownership transfer — On full payment

That's five clauses. That's enough to protect you from 80% of the problems that actually happen.

As you grow, add the rest. Get a lawyer to review it once — it's worth the investment. Several freelance contract templates are also available from platforms like Bonsai, AND CO (now HoneyBook), and Docracy that you can adapt.

FAQ: Web Design Contract Template for Freelancers

Do I really need a contract for small projects?

Yes. The smaller the project, the easier it is to skip the contract — and the more likely you are to regret it. A €500 website that doubles in scope without documentation is just as painful as a €5,000 one. Use a shorter, simpler contract for small projects, but use one.

What should I do if a client refuses to sign a contract?

Walk away. This isn't dramatic — it's practical. A client who won't agree to a written scope and payment terms is telling you how the project will go. Clients who take projects seriously have no problem signing a reasonable contract.

Can I use a template I found online?

Yes, as a starting point. But adapt it to your situation, add your specific revision and payment terms, and have a local lawyer review it at least once. Laws around contracts vary by country, and what works in the US may not be fully enforceable in Germany or Australia.

What's a kill fee and is it standard?

A kill fee is a cancellation charge — compensation for the time you've already invested if a project is cancelled mid-stream. It's standard practice in creative industries. Typically 20–25% of the remaining contract value on cancellation after work has begun.

Should I include a web design contract template clause about SEO?

Yes — specifically to say that you are not guaranteeing specific search rankings or traffic numbers. SEO depends on hundreds of factors outside your control. If you're offering SEO as a specific service, define exactly what that service includes (on-page optimization, meta tags, schema markup, etc.) rather than a results-based promise.

What payment terms are standard for freelance web designers?

50% upfront, 25% at a milestone (design approval or development start), 25% on delivery is the most common structure. Net 7 or net 14 for invoice due dates is reasonable. Net 30 is too long for solo freelancers — it's a cash flow problem.

How do I handle scope creep even with a contract?

Document every new request as it comes in and respond in writing with a clear note that it falls outside the original scope, along with a proposed cost to add it. A visual feedback tool with a timestamped record of all comments — like dotts — makes this even cleaner, because every request is logged against a specific element on the live site.

Does a contract need to be notarized to be valid?

In most jurisdictions, no. A signed contract (even a digital signature via DocuSign, HelloSign, or similar) is legally binding. Notarization is generally only required for certain legal documents like property transactions. Check with a local lawyer if you're unsure about your specific country or region.

Stop losing time and money to unclear agreements. [Try dotts free →](https://dotts.se)