Your customers, your data, your domain, and your brand should always be yours, whoever builds the site. The code is where terms differ from one builder to the next, so it needs a written answer: what happens to it, and when. With me the answer is one sentence: at the end of the term, with everything paid, I hand over the source code on request. Knowing which parts are always yours, and getting the rest in writing, is what lets you switch, scale, or hire someone else without starting over.
What should always be yours?
Four things, from day one, whoever you hire: your customers, your data, your domain, and your brand. Your customer list and the data your site collects should be exportable anytime, in a format another system can read. The domain should be registered in your name, in an account you control. The brand — the name, the logo, the copy, and the photos — is yours, as files you hold. If any of those lives only inside someone else's account, you're renting your own presence, and rent can rise or vanish when the provider changes terms or disappears.
What happens to the code?
That depends on the builder, which is exactly why it has to be written down. Some hand over a repository at launch, some run the site for you and never hand anything over, and some keep it "for maintenance" with no terms at all. There's no single right model, but there is a wrong one: the one nobody wrote down. Mine is simple. During the plan I host and run the system for you, and at the end of the term, with everything paid, I hand over the source code on request. Your customers and your data are always yours, before and after.
Where does lock-in hide?
Common traps: a builder who keeps the codebase with no written terms for when, or whether, it comes back; a proprietary platform you can't export your data from cleanly; a domain registered under the agency's account; or monthly fees with nothing in writing about what you keep. None of these are always malicious — but each one makes leaving expensive, which is often the quiet point of setting them up that way. The most common is the domain: if your own web address sits in someone else's account, they hold the keys to your entire online presence, email included. Check who the domain is registered to first — it's the fastest way to learn how locked in you really are.
What should you ask any builder, in writing?
Four questions, before any money changes hands: What happens to the code, and when? Is the domain registered to me? Can I export my customers and my data anytime? And whose are the brand files — the name, the logo, the copy, and the photos? A professional answers all four in writing, with specifics. Vagueness, or "don't worry, that's all taken care of," is the warning sign — because "taken care of" can mean anything. The one that matters most is the first: a written statement of what happens to the code, and when. My own answer is the sentence above.
Why does it matter for SEO and growth?
Because growth depends on control. If you can't change your structure, speed, or content without a gatekeeper, your SEO is capped by someone else's roadmap and priorities. Your domain carries your rankings and your history; your content and your data carry your customers. Keep those in your name and they come with you if you ever move. A site whose terms nobody wrote down is a growth engine with someone else's hand on the throttle.
What happens when nothing is in writing?
The bill comes due exactly when you want to move. A common story: a business outgrows the agency that built its site, asks for the code, and learns there was never an agreement about it — so leaving means rebuilding from scratch or paying a release fee that feels like a ransom. Others find their domain was registered by a former contractor who's now unreachable, freezing every change until it's untangled. None of it looks dramatic until the day it is, and that day always arrives at the worst time — a redesign, a dispute, a provider shutting down. Written terms from the start turn that day into a non-event.
How do I handle it?
The same way on every build: your customers, your data, your domain, and your brand are always yours, and the code follows one written sentence — at the end of the term, with everything paid, I hand over the source code on request. That's the model behind every project in my services: you work with me directly, with no telephone game, and you know from the first day what you keep and when. Your data is exportable anytime, and the domain stays in your account.
Related growth guides
See SEO basics every founder should own, website maintenance explained, and red flags when hiring a web developer.
