Before you sign for a website, ask who will own each account and asset when the project ends, because most proposals do not say.
I build websites, and I want my clients to own all of it. I would rather a client stay because the work is good than because leaving is hard.
Which seven accounts and assets should I own?
| Asset | Why it matters |
|---|---|
| The domain | Registered to you, in an account you can log into. Providers often register it in their own name. |
| Hosting | An account in your name, with your billing on it. A sub-account inside a provider's reseller plan leaves them in control of it. |
| The code | A repository you have access to, or at minimum a copy of the files delivered to you at launch. |
| The content management login | An administrator account. An editor account cannot export the site or add users. |
| Google Business Profile | Yours, in your own Google account. |
| Analytics | Your property, with the provider added as a user. The reverse arrangement means your traffic history leaves with them. |
| Email at the domain | Under your control, because losing it means losing password resets for everything else on this list. |
Why does the domain come first?
You can replace everything else with some effort. Code can be rebuilt, hosting can move in a day, and you can recover from losing analytics history.
Your email, your printed materials and the address customers type all depend on the domain. If your provider holds it, you cannot leave without their cooperation.
Providers usually register it in their own name because that was faster during setup, and then nobody changes it for years. Ask early, and a good provider will transfer it.
Two questions before you sign
"When we finish, which of these will be in my name?" Ask it about the list above, specifically, and get the answer in writing. The answer should be all of them.
"If I wanted to move to another provider next year, what would that involve?" The answer you want is a description of a process. The answer that should worry you is reassurance that you would not want to.
What can a provider reasonably keep?
Providers can reasonably keep their own internal tooling, their project management system, and any general-purpose components they built before you and will use again after you. Reusing components is normal, and it keeps prices down.
They should not keep your domain, your listing, your analytics history, or a content management system you cannot administer. If something is specific to your business, it should be yours.
If you are already in this situation
Ask for the transfer plainly. Most providers will do it, and some never realised the client wanted it.
If the provider resists, you have learned what kind of provider you hired before any dispute starts. A domain can be recovered through the registrar's own transfer process in most cases, and it is much easier while the relationship is still cordial.
Related, on choosing between a solo operator and an agency and what to ask either: what one operator can deliver, and what a website costs.
Part of the guide AI websites and getting found by AI search.