Most people hiring a web developer for the first time focus on exactly one thing: the quote. Whoever comes in cheapest, or whoever has the nicest portfolio, gets the job. That's not an unreasonable way to shop for most things — but a website isn't most things. It's the one piece of your business where the person you hire can quietly control whether you own what you're paying for.
A good price and a good developer aren't the same thing, and a slick portfolio doesn't tell you what happens six months after launch when something breaks, or two years from now when you want to switch providers. The questions that protect you are rarely the ones people think to ask up front.
Here's what's worth asking before you say yes to anyone.
The Questions That Actually Matter
"Will the domain and hosting be in my name?"
This is the single most important question on the list, and the one most people skip. If a developer registers your domain or sets up your hosting under their own account "to make it easier," the site stays tied to their account, and every change, renewal, or move depends on them. Ask for it in writing: domain registrar account in your name, hosting account in your name, you holding the login for both before the project even starts.
"What happens after launch?"
A site going live isn't the end of the relationship — something will eventually need a fix, an update, or a password reset. Ask whether that's covered, for how long, and what it costs once it isn't. A developer who can't answer this clearly probably hasn't thought past delivery day.
"Can I get the actual source files, not just a login?"
A login to a site builder or CMS isn't the same as owning the code behind it. If the build is custom, ask for a copy of the source files and database as part of the handoff — not as a favor, as a standard deliverable. A developer who builds this way will usually offer it before you even ask.
"What if you become unavailable?"
Freelancers get busy, change careers, or simply stop responding. Ask what documentation you'd be left with if that happened tomorrow — admin credentials, a list of what plugins or services the site depends on, anything another developer would need to pick up where it left off. A one-page handoff document costs the developer almost nothing to write and saves you from starting over blind.
None of these four questions is about distrust. They're about making sure the answer to "who controls my website" is you, by default, from day one.
What These Questions Won't Protect You From
It's worth being honest about the limits here too.
Asking the right questions doesn't guarantee good answers, and a confident answer isn't the same as a true one. Someone can tell you "of course it'll be in your name" and still set things up under their own account out of habit, not malice — the only way to actually confirm it is to check the registrar and hosting panel yourself once the project is live, not just take the verbal answer at face value.
These questions also won't fix a mismatch in scope or expectations. A developer can answer every one of them perfectly and still not be the right fit if what you need is a quick one-page site and they only build complex custom systems, or the reverse. Ownership and communication are table stakes — they don't replace checking that the work itself fits what you're trying to build.
And price still matters. These questions aren't a reason to ignore your budget — they're a filter for what a given price includes. The cheapest quote and the most expensive one can both come with full ownership and a clear handoff plan, or neither. Asking tells you which one you're getting.
What This Comes Down To
A good developer answers these questions without flinching, because the answers were never a secret — ownership, documentation, and a plan for "what if" are just part of doing the work properly. Someone who's never been asked before might need a second to think about it, and that's fine. What you're looking for is a clear, specific answer — that's usually a good sign of how the rest of the project will go.
Closing
Hiring a developer isn't just buying a website — it's deciding who gets to hold the keys to it. The quote tells you what it costs. These four questions tell you what you actually get. Ask them before you sign anything, not after something's already gone wrong.
If you're about to hire someone for your site and aren't sure what to ask, that's the part I can help with.
Further reading
- 3 Things You Should Actually Own on Your Own Website — czerwin.net
- What a Website Should Actually Cost You — czerwin.net