What a Real Website Contract Should Include (and Red Flags to Watch For)
A contract isn’t paperwork for its own sake — it’s what determines exactly what happens if something goes wrong. Most disputes trace back to something that was never written down in the first place.
Photo: Unsplash
Most website disputes aren’t about bad design — they’re about something that was never actually agreed on in writing. A short, specific contract, or even a clear written email exchange, prevents almost all of them before they start.
What a website contract should always include
- Scope of workThe exact pages and features included — specific enough that both sides would describe the finished project the same way.
- Total price and payment scheduleThe full cost, and exactly when each part is due.
- Delivery dateA real date, not an estimate range with no accountability.
- Number of revision roundsHow many rounds of changes are included, and what counts as a revision versus a new request.
- Ownership on completionWho owns the domain, the files, and the code once the project is finished and paid for.
- Cancellation termsWhat happens, and what’s owed, if either side wants to stop partway through.
- Refund conditionsSpecific circumstances and timeframes — not a vague promise to “work it out.”
Ownership: the clause that matters most
This is the single most disputed area in website projects, and the easiest to prevent with one clear sentence: upon final payment, you own the domain, the design, and the code, in full. Without this explicitly stated, a designer can — deliberately or through simple neglect — hold the domain registration, hosting account, or source files in a way that leaves the business unable to actually use what it paid for.
Payment terms that protect both sides
A design preview before any payment, followed by full payment on delivery, protects the client completely — nothing is owed until real work exists. A deposit plus a balance due on delivery is a reasonable middle ground many providers use. What should raise a question is 100% payment required before any design has been shown at all — see our companion article on avoiding bad outcomes with a web designer for more on why that specific pattern is risky.
Scope and revisions: where vague language causes problems
“Unlimited revisions” sounds generous, but in practice it’s one of the most common sources of project delay and disputes — without a defined number of rounds, there’s no clear point where the project is actually finished, and no shared definition of what counts as a small fix versus a new feature request. A fixed, reasonable number of revision rounds (2–3 is typical) with a clear definition of what’s included keeps the project moving and protects both sides from an open-ended disagreement.
Red flags in a contract
- No specific page count or feature list — just a vague promise of “a nice website.”
- No revision limit and no defined scope at all — a recipe for the project never actually finishing.
- A missing or vague ownership clause — leaves the domain and files in a gray area after payment.
- No cancellation or refund terms whatsoever.
- Recurring charges that aren’t clearly disclosed — check carefully for anything that renews automatically.
What if there’s no contract at all?
Plenty of small, legitimate projects run on an email exchange rather than a formal signed document — that’s often fine, as long as the key terms are actually written down somewhere. Before paying anything, get scope, price, delivery date and ownership confirmed in writing, even informally. A clear email is real evidence of what was agreed; a phone call or a verbal promise is not.
This article is general guidance, not legal advice. For a significant project, having an actual lawyer review a contract is a reasonable and inexpensive precaution.
Frequently asked questions
What should be in a website design contract?
At minimum: a specific scope of work, the total price and payment schedule, a real delivery date, the number of revision rounds included, who owns the domain and files on completion, and cancellation and refund terms.
Who owns the website after it’s built?
This should be stated explicitly in the contract — typically, the client owns the domain, design, and code in full once final payment is made. Without this clause written clearly, ownership can end up genuinely disputed.
Is “unlimited revisions” actually a good thing?
It sounds appealing but often causes more problems than it solves — without a defined limit, there’s no clear point where the project is finished, and disagreements about what counts as a “revision” become common. A fixed, reasonable number of rounds is usually healthier for both sides.
Do I need a lawyer to review a website contract?
For a small, standard project, usually not — reading it carefully and asking direct questions about anything unclear covers most cases. For a larger or more complex project, a brief legal review is a reasonable and generally inexpensive precaution.
What if I only have an email, not a formal contract?
That’s often fine, as long as the key terms — scope, price, delivery date, ownership — are actually written down somewhere before you pay. A clear email is real evidence of what was agreed; a verbal promise is much harder to rely on if something goes wrong.
Get a fixed-price quote — terms included
Our scope, pricing, delivery dates and refund conditions are published openly — read them, then get a fixed-price quote.
- Fixed price from $149
- Live in 3 days
Published by Union Web Studio, a trading name of Infivion LLC. This article is general guidance, not legal advice. See our own Terms of Service and Refund Policy for how these principles apply to our own packages.