The short answer
Every account and file your site depends on should be in your company's name, with at least two people on your team able to get in. Your builder works as a guest you can remove. Put that in the contract, with the scope, payments, revisions, ownership and support, before work starts.
This chapter is practical guidance from how we run projects. It is not legal advice. For a contract with real money or risk in it, ask a lawyer where you are based to read it.
What you should own
Go through this list for every project, new build or redesign. The right column is what to check on handover day.
| Thing | Whose name | Check on handover |
|---|---|---|
| Domain name | Your company, at a registrar account you control | You can log in, and renewal is on your card |
| Platform or hosting account | Your company's account or workspace | Your team are owners or admins |
| Code repository, for coded sites | Your company's organisation | You can see the code and the deploy settings |
| CMS project, such as Sanity | Your company's account | Your team are admins |
| Design files, such as Figma | Your team or a file moved to it | You can open and duplicate them |
| Fonts | A licence in your company's name, or a free licence | You have the licence terms on file |
| Photos and illustrations | Licences or written rights for your use | You know where each one came from |
| Analytics and Search Console | Your company's Google account | Your team hold the owner or admin role |
| Forms, CRM and email tools | Your company's accounts | Leads arrive where you expect |
If a builder has set up something in their own name to save time, that is fine during the build. It just needs a date when it moves to you.
Domain, hosting and workspaces
Domain. The registrant is the person or company the domain is registered to. ICANN, which oversees domain names, says the registrant takes sole responsibility for the registration and must keep its details accurate and current (ICANN). That is a strong reason for the registrant to be your company, not your builder.
Webflow. Webflow has a guest role for this exact case. The client keeps ownership of the Workspace and invites the agency or freelancer as a guest, who can work on its sites without seeing the Workspace's confidential settings. The guest needs an Agency or Freelancer Workspace plan (Webflow help). If the site was built in the agency's Workspace, Webflow lets Freelancer and Agency Workspace plans transfer it to the client, along with its Site plan and connected custom domains (Webflow help).
Coded sites. For an Astro site, the repository, the hosting project and the CMS project should each sit under your company's account, with the builder added as a member. Then removing the builder is one click on each, and nothing has to move.
Analytics and search accounts
These are easy to forget, and painful to recover.
- Search Console. Google says a property must have at least one verified owner, or no users will have access to it, and that owners can add and remove other users (Search Console Help). Make sure a verified owner is someone at your company.
- Google Analytics. Google says adding or changing users needs the Administrator role, and that the last Administrator cannot remove themselves (Analytics Help). Keep at least two Administrators on your side.
- Tag managers, ad pixels and CRM. Same rule: the account is yours, the builder is a user.
If an old agency or freelancer still owns any of these from a past project, sort it out before the new build starts. It is far easier while everyone is still talking.
What to put in writing
A website contract does not need to be long, but it should cover these points in plain words. Use it as a list to check any contract you are sent.
- Scope. Pages, layouts, CMS, integrations, migration and content, as in your quote grid
- Price and payments. The amount, when each part is due, and what is extra
- Changes. How a request outside the scope is quoted and approved
- Reviews. How many review rounds, at which stages, and what approval means
- Ownership. What you own and when, usually on full payment
- Accounts. Whose name every account is in, and when anything moves
- Support. How long after launch, what it covers and what it does not
- Confidentiality. How your logins and unreleased work are kept private
- Ending early. What happens to work and payments if either side stops
Agree all of this before the first payment. Changing terms halfway through a project is much harder than setting them at the start.
What Kookies' terms say
To show what this looks like in practice, here is a plain summary of Kookies' terms of service. These are our terms only, for our own projects. Other teams' terms will differ, and none of this is legal advice.
- Every project starts with a written scope and a fixed price. Work outside the scope is quoted separately before we do it.
- Fixed projects are usually paid half upfront and half at launch. Care plans are billed monthly in advance.
- Once you approve a stage, changes to it may be quoted as new work.
- Once the project is paid in full, you own the design, the content and the code we made for you.
- Platform accounts such as Webflow, Framer, Shopify, Sanity or Vercel are in your name and paid by you to the vendor.
- Every project includes 30 days of support after launch for safe changes, covered in chapter 6.
- We keep your business information, logins and unreleased work private.
- We do not refund work that has already been done, and our total liability for a project is limited to the fees paid for it.
The full wording, including governing law and how disputes are handled, is on the terms page.
The access list and handover day
On handover day, walk through a written access list together. One row per account, with these columns:
| Account | Owner at your company | Second admin | Builder access | Remove builder by |
|---|---|---|---|---|
| Domain registrar | ||||
| Platform or hosting | ||||
| Repository and CMS | ||||
| Design files | ||||
| Analytics, tag manager, Search Console | ||||
| Forms, CRM and email |
Alongside it, ask for a short handover note: where every form sends leads, which tools are connected, how to publish, and who to call for what. Test each form while you are together. Our website handover checklist has the full list to copy.
Decision rule If you cannot log in to something yourself on handover day, it is not handed over yet. Do not sign off until every row has a name from your team.


