TL;DR
- A web design contract decides whether your project ships on budget or turns into a months-long argument, so read it before you sign, not after.
- The lines most contracts get wrong are the same three every time: who owns the files, what counts as a revision, and how either side walks away.
- If ownership of the design files and source code is not transferred to you in writing, you do not really own your website.
- Tie payments to approved deliverables, not calendar dates, and get the change-request rate in writing before you need it.
- With Zero Dollar Website there is no contract trap at all: we build and host your site for $0, and you only pay for optional services you choose. The questions below still protect you with any designer you hire.
Hiring someone to build your website usually starts with excitement and ends with a contract nobody read closely. That is where the trouble hides. Owners skim the document, sign it, and then learn that two rounds of revisions meant two per page, the design files were never theirs to keep, and leaving early triggers a fee worth most of the remaining quote. That is not bad luck. It is the result of not asking the right questions first.
This guide is the checklist we wish every small business owner carried into a signing call. It covers what actually breaks web projects: vague scope, fuzzy file ownership, payment splits that punish a slow week, and warranties that quietly exclude the likely failures. At Zero Dollar Website we removed this whole problem for the build itself, because we build and host your site for free and you sign nothing that locks you in. But plenty of owners still hire outside help for design, custom apps, or specialist work, so these questions are worth knowing either way.
Why a contract checklist matters more than you think
Scope creep is the quiet killer of web projects. The Project Management Institute, in its Pulse of the Profession research, has reported that roughly half of projects experience scope creep, where the work grows beyond what was first agreed. When that happens on a fixed quote with no change-order pricing, the extra hours get billed at whatever rate the vendor picks, and a friendly kickoff turns into a standoff over money.
The questions below sit in seven plain buckets: scope, ownership, files and handoff, milestones and payment, change requests, post-launch support, and how the relationship ends. If a designer pushes back hard on more than two or three, that resistance is itself your answer. Before you negotiate, it helps to know what a fair deal looks like, which is why our pricing page lays out what is free and what is optional with no fine print.
Scope: pin down what you are actually buying
The phrase "build my website" can mean a tidy five-page brochure site or a sprawling store with dozens of templates. That gap is where most billing fights begin, so get specific before money changes hands.
Which pages, states, and screen sizes are included? The agreement should name every page (home, services, contact, the empty cart, the error screen, the thank-you page) and confirm which screen sizes are covered. "Roughly ten pages" is an invitation to argue later. Ask for a written page list in the contract. When we build a done-for-you website, the page set is agreed up front so there is no guessing about what arrives.
What is the exact deliverable list? A sitemap, wireframes, finished designs, a clickable preview, and a written style guide are five separate things. If a deliverable is not named, assume it is not coming. Browse our website examples to see the standard you should be holding any quote against.
How many revision rounds, and what counts as one? "Two rounds" has to define whether a round means all your feedback gathered into one document, or two stray comments from three different people on your team. The first is reasonable. The second is a trap that ends your revisions before you have really used them.
Does the price include testing on real devices? A design that looks perfect in the tool is not the same as one confirmed to work on an older phone, so make sure mobile testing on actual devices is written in. If you are updating an existing site rather than starting fresh, our website redesign checklist walks through the scope questions specific to a rebuild.
Ownership: who owns the site, and from when
Owners skip this section because it reads like legal boilerplate, yet it is the most expensive part to get wrong. The whole point of paying for a website is to end up owning it, and that only happens if the contract says so plainly.
When does ownership transfer to you? A reasonable contract transfers ownership on final payment, in clear language. A clause that says ownership passes "on completion" without defining completion leaves you exposed, because the vendor decides when that day arrives.
What about templates, plugins, and stock assets? If the designer uses a paid theme, a stock photo library, or a third-party plugin, the contract should disclose it and grant you a lasting licence to keep using it. Otherwise you can end up renting pieces of your own site indefinitely.
Who owns anything generated with AI tools? Many designers now use AI to draft layouts, copy, or images. The contract should state that any AI-assisted output is assigned to you, and that the work does not break the terms of the tools used to make it. This is easy to overlook and awkward to fix after launch. The same care applies to marketing assets and local SEO content if a vendor produces those for you too.
This is exactly the trap we built Zero Dollar Website to avoid. There is nothing to claw back, because your site and its content are yours from day one with no ownership clause to negotiate. If you prefer a fully managed arrangement where build, hosting, and growth work are bundled, the older subscription model still lives on our agency page.
Files and handoff: ownership means nothing without the files
Owning your website on paper is useless if you never receive the files that let you edit or move it, and many contracts grant ownership then stay silent on what gets delivered.
What files do I receive at handoff? At minimum you want the editable design source, exported images and icons in usable formats, and a written handover document. If the designer also codes the build, add the code repository, a setup guide, and instructions for deploying or moving the site. "Final files" with no list attached is too vague to enforce.
Where does the site live, and how do I get access? The contract should name where the code and the site are hosted, state when you get access, and confirm you keep that access after the work ends. This matters most when the site sits on accounts the vendor controls.
Is anything tied to the vendor's own accounts? If your site depends on the designer's hosting login, domain registrar, or email service, you need a written plan to move those into your name. Otherwise you can own the work and still be unable to touch it. With our build, hosting is handled for you and the path to take your site elsewhere is never blocked.
Milestones and payment: tie money to approved work
A healthy payment plan asks for a deposit up front, then releases the rest as each stage is approved, with a final slice held until launch. A plan that wants half up front and half on "completion" is a cash-flow arrangement dressed up as a project, and gives the vendor little reason to finish well.
Are payments tied to dates or to approved work? Tie them to approved deliverables, with target dates as guidance only. A payment that triggers on a date no matter what has been delivered removes the incentive to ship something you are happy with.
How long do I have to review, and what happens if I am slow? A review window of about a week is fair. A good contract also adds a deemed-acceptance line after a written reminder, which protects the designer from a client who vanishes and protects you from being billed for work you never saw. The table below shows a structure that keeps both sides honest:
| Stage | Share of total | What triggers it |
|---|---|---|
| Kickoff and planning | 25 to 30 percent | Signed contract and brief delivered |
| Sitemap and wireframes | 20 percent | Wireframes approved by you |
| Finished design and preview | 25 percent | Designs approved by you |
| Build and handoff | 15 percent | Handover walkthrough complete |
| Launch and warranty start | 10 to 15 percent | Site live and confirmed |
Most of the money sits behind work you have actually approved, which is the structure to aim for. If a quote front-loads the payments, ask why. For a sense of how the free build sits next to optional paid stages, compare it on our pricing page.
Change requests: the line item that prevents fights
Every project changes as it goes. The contract's job is to make change predictable rather than a fresh negotiation each time. Two questions handle most of it.
What is the rate for out-of-scope work, in writing? Get the actual number. "To be decided" means whatever the vendor feels like charging on the day, usually when you have the least leverage. A clear rate keeps surprises off the invoice.
What is the change process, and who signs off? A real process looks like this: you email the request, the vendor quotes it within a few business days, you approve in writing, then work begins. Naming a single approver on each side prevents the "but someone on your team said yes" dispute. For owners spending carefully, this clause is the difference between controlled costs and a budget that quietly runs away. Once the site is live, growth work like marketing and local SEO should follow the same approved-before-it-starts pattern.
Post-launch support and warranty
The cheapest moment to fix a bug is during the warranty window right after launch. Once that closes, you pay full rate for the same fix, so understand the terms before you sign.
What does the warranty cover, and for how long? A common window runs from one to three months after launch, covering bugs in the delivered work. The contract should also spell out exclusions, such as brand-new features, breakages caused by third-party tools, and changes you make yourself. A vague promise of "reasonable support" causes more disputes than a clear, limited warranty ever does.
What are the ongoing support options and rates? Support usually comes in three shapes: pay as you go, a monthly retainer, or a contract with guaranteed response times. Decide which you need before launch, not during your first emergency. Our model differs here too: ongoing care is available through our Concierge service so the site stays current without negotiating a support clause from scratch. The outcomes that approach produces are visible in our case studies.
Ending the relationship: kill fees and the exit ramp
You may never use this section, and that is exactly why it matters. Knowing the exit terms before you need them is the difference between a clean break and a legal mess.
What is the termination clause on both sides? A fair one lets either party end the work with written notice, pays the vendor for work completed and approved, and transfers all in-progress files and ownership to you once the final invoice is settled. Watch for lopsided terms where you pay a penalty to leave but the vendor walks free, and for any clause that ties your right to leave to the vendor's own judgment.
What happens if the vendor closes or the lead person leaves? Even a small project benefits from a clause requiring delivery of all current files and login details within a set number of days. None of this applies to a Zero Dollar Website build, because there is no lock-in, but it is essential reading for any outside contract you sign.
Key takeaways
- Name every page, screen size, and deliverable in writing, so there is a list you can point to later.
- Confirm that ownership, design files, source code, and any AI-assisted output transfer to you in writing.
- Tie payments to approved work, with the percentages adding up to 100, and a slice held back until launch.
- Get the change-request rate and process defined before you need them, not in the middle of a dispute.
- With Zero Dollar Website none of these traps exist, because the build is free, the site is yours, and nothing locks you in.
FAQ
Is a website design contract different from a development contract?
They often sit in one document but should keep separate sections for scope, deliverables, and warranty. Design covers the look, the layout, and the style guide. Development covers the code, the build, and going live. If one provider handles both, make sure each side is itemised so you can measure progress and payments against the right stage.
How much should I pay a web designer up front?
A deposit of around a quarter to a third is normal. Asking for half or more before any work is shown is unusual for a small project and can signal a vendor stretched on cash flow. The rest should release across stages tied to approved work, with a final portion held until the site is live.
Can I get my files if the contract does not mention them?
Practically, you are in a weak spot. Without a clear ownership clause and a defined handover, you may have the right to use the finished site without ever receiving the editable files behind it. That is why ownership, file delivery, and account access are three separate questions here. Pin all three down before signing.
Are termination clauses really needed on a small website project?
Yes, arguably more so. The smaller the job, the more likely one side decides to walk. A short termination clause with a clear notice period and a clean handover stops weeks of awkward emails and pushes both sides to take the work seriously from week one.
What if the designer refuses to define these terms?
Treat it as a preview of the whole project. A designer who will not cap revisions, name an ownership trigger, or quote a change rate is showing you how the relationship will run under pressure. Plenty of professionals will walk this checklist with you, so be selective.
Does Zero Dollar Website make me sign a contract like this?
No. We build and host your site for $0, your site and its content are yours, and there is no lock-in clause to negotiate your way out of. You only pay for optional services you actively choose, such as SEO, marketing, branding, apps, or Concierge support. The checklist here is for when you hire other help, so you can spot a fair deal from a risky one.
Where can I see what a finished result should look like?
Start with our website examples for the visual standard, then read real outcomes in our case studies. Together they give you a benchmark for judging any quote. You can also browse more guidance on the blog.
Ready to skip the contract trap entirely? Get a real, professionally built website at no cost. Claim your free done-for-you website today, and see what is free and what is optional on our pricing page. No lock-in, no clawback, no fine print, just a site that is yours from day one.
