“We’ll build your website” sounds like a complete sentence. It isn’t. The part that actually matters — who owns the thing once it’s built — rarely gets discussed until something goes wrong.
Here’s a scenario that happens more often than it should: a business pays for a website, it launches, everyone’s happy. A year later they want to switch developers, or the original one stops responding, or a small text change turns into a week of silence. Only then do they discover the domain is registered in the developer’s name, the hosting account belongs to the developer, and there’s no way to log in and change anything without going through them.
That’s not a website you own. That’s a website you’re renting, with extra steps.
What “you own it” actually means, concretely
Not a vague promise — four specific, checkable things:
- The domain is registered in your name, on an account you control the login for. Not the developer’s registrar account with your domain sitting inside it.
- Hosting is under your name and your billing, even if the developer set it up and picked the provider. You should be able to see the invoice and cancel it yourself if you ever wanted to.
- You have the actual source code — not just “the website exists,” but the files, in a place you control (even just a folder, or a private GitHub repo under your own account).
- You have admin access to update it — a CMS login, or at minimum, someone who can walk you through what changing text or a phone number actually involves.
If any one of these lives exclusively in someone else’s account, with no path for you to get it into yours, you don’t have a website — you have a dependency on that person staying reachable, reasonable, and in business.
Why this happens
Rarely malice. More often, it’s just easier for a developer to register the domain and hosting under an account they already have set up, and “we’ll transfer it later” quietly never happens because nobody’s forcing the issue. Sometimes it’s less innocent — an agency keeps things under their control on purpose, because it makes switching providers hard, which makes their next “maintenance fee” easier to justify.
Either way, the fix is the same: ask for this explicitly, in writing, before work starts — not after the site is live and the leverage has shifted.
What to actually ask before you hire anyone
Four direct questions, and the answers should be immediate and specific, not vague reassurance:
- “Whose name will the domain be registered under?” — the answer should be yours, from day one, not “we’ll transfer it after.”
- “Whose hosting account will this run on?” — same answer.
- “Do I get the actual code, or just a working website I can’t move?” — you want the files, not just the result.
- “If I never spoke to you again after launch, could I still update my own site?” — if the honest answer is no, that’s worth knowing before you pay, not after.
None of these are unreasonable to ask. A developer who’s actually planning to hand things over properly will have straightforward answers ready, because it’s how they always work — not something they have to think about.
What a proper handover actually looks like
At the end of a project, you should get: your domain registrar login (or the domain already transferred to an account you control), your hosting login and billing details, the complete source code, and a short walkthrough of how to make basic changes yourself — even if you never plan to touch the code again. That last part matters more than it sounds: it’s the difference between a developer who wants you dependent on them, and one who’s fine with you not needing them for small things.
The honest trade-off
Full ownership does mean you’re responsible for renewing the domain and paying the hosting bill each year, rather than it quietly happening on someone else’s account. That’s a small amount of admin in exchange for never being stuck. Most people find that trade obviously worth it once they’ve heard the alternative version of this story from someone it happened to.
If you’re evaluating a quote for a new site, or trying to figure out whether you actually own the one you already have, that’s exactly the kind of thing covered under website design & development — or just ask and I’ll tell you honestly what to look for.