What to get in writing before you pay for a website
When ownership actually transfers, spelled out in the contract
"You'll own everything once it's done," is a sentence a lot of buyers hear on a first call and never see again in writing anywhere. Verbal assurances evaporate the moment there is a disagreement, and a one-page agreement with no ownership clause leaves that promise unenforceable in any real sense.
The contract needs a specific sentence: ownership of the design, code, and content transfers to the client upon final payment, or upon a defined milestone if the project runs in phases. "Final payment," not "project completion," is the trigger that actually protects you. A project can be functionally finished while an invoice sits unpaid for months, leaving ownership in limbo the whole time.
Vague ownership language leaning on phrases like "full rights" without saying what transfers, and when, is worth pushing back on before signing. Ask for a rewrite. The full ownership landscape this term is meant to protect sits underneath a much bigger question about who owns what across an entire build, not just this one clause.
A delivery list specific enough to check against
A contract that says "a website will be built" describes nothing useful at all. A contract that lists the pages, the number of design revisions included, whether copywriting is part of the scope, and which files get handed over at the end gives you something to check against later, page by page.
Specificity protects both sides equally. A designer who lists exactly what is included has a clear boundary against scope creeping in for free, project after project. A client who reads that list before signing knows precisely what they are paying for, rather than discovering gaps only after the invoice clears and the work is already underway.
If a one-page agreement you were sent skips this list entirely, ask for it before you pay a deposit. Ask in writing, not on a call. A short conversation now costs far less than a dispute later over what was actually promised.
Even a simple bullet list attached to the main agreement is enough, as long as both sides sign it. It does not need to read like a legal document to do its job. It just needs to exist somewhere both parties can point back to later.
Access and credentials, written down as their own line
Domain, hosting, CMS login, and any third-party account tied to the build deserve their own line in the contract, separate from the ownership clause entirely. A general statement about "full ownership" does not guarantee you actually hold the passwords when the project wraps.
The line should say plainly who registers each account, under whose name, and when credentials get shared with the client. "Upon request" is weaker than a set number of business days after completion, because "upon request" can quietly turn into never, especially once the invoice is settled.
This is exactly the kind of term a buyer forgets to ask about before signing, and it is also one of the last things actually checked before a project counts as done. The sign-off checklist that closes out a website project once every contract term has been met treats credential handover as one item among several to confirm, not assume, before the engagement wraps.
What the contract says if payment stops or the project ends early
Projects stall. Budgets change. A client goes quiet, or a designer does, and neither side planned for it when the work started. What the contract says about this moment matters more than what it says about the version of events where everything goes exactly to plan.
Non-payment terms should specify what happens to work already completed: does partial payment earn partial ownership of the code produced so far, or does nothing transfer until the full amount clears? Early termination terms should answer the same question from the other direction, covering what a client is owed if they choose to walk away midway through the project.
Neither answer is universally right. Both are defensible, in different situations, for different reasons. The real problem is silence on the question, which leaves both sides guessing during the exact moment guessing is most likely to end in a dispute nobody wanted.
A short paragraph covering exactly this, added while both sides are still on good terms, costs nothing and prevents a lot of bad feeling later. It is far easier to agree on fair terms before either side has a reason to feel wronged by the other.
Revisions and file retention, set before work begins
How many rounds of revisions are included, and what counts as a revision versus a new request, belongs in writing before the first draft is even shown to you. Without it, "just one more small change" can repeat indefinitely, with neither side agreeing on where the line actually sits.
File retention matters just as much and gets skipped far more often. Ask how long source files, from design mockups to the final code, get kept after the project wraps up. Ask whether requesting them later carries any resistance, delay, or extra cost tacked on.
Neither of these terms takes more than a sentence to write down. Both are the kind of thing nobody thinks to ask about until the moment they actually need it, which is exactly the wrong time to be negotiating from scratch.
Write them down anyway, even if the project feels friendly and low-risk right now. A good relationship at the start of a project is not a substitute for a clear paper trail if anything changes later.
Once a draft contract exists, reading the actual handover clause line by line is a separate skill from knowing what to ask for in the first place. What that clause needs to say, and where vague language hides is worth reading closely before you sign. The specific checklist of files worth requesting, beyond just the live pages, deserves its own answer too.
More from the blog
- Will a professionally built website actually get you more customers
- When a booking system is worth adding to your site
- What has to be on your website before a stranger will choose you
- What to ask before a monthly retainer adds a new tool to your site
- Where your website's contact form submissions actually go