Contents
The site is built, launched, everyone is happy. A year later the studio is busy with other clients, or has closed, and the founder needs a change. That’s when it turns out the domain is registered to the agency, the hosting runs on someone else’s account, and nobody can say how to add a new page.
It happens with WordPress, Webflow, Framer and custom code alike. The stack matters less than what was agreed at the start. This article covers what a startup should own from day one, what a proper handover includes, and what to ask a studio before signing.
What You Should Own From Day One
Everything the site depends on should sit in accounts the company controls. The studio gets access as a team member, and that access can be removed at any time.
- The domain. Registered in the company’s own account with the registrar, with renewal on the company’s card.
- Hosting and deployment. Vercel, Netlify, a server or the website builder’s plan, on a company account.
- The code. A repository in the company’s GitHub organisation, if the site has code at all.
- The database and the CMS. Where the content lives, and the admin logins for it.
- Analytics and search. Google Analytics, Search Console and any tracking, created by the company and shared with the studio.
- Everything around it. Email sending, forms, payments, maps, fonts with their licences.
What a Handover Includes
Owning the accounts is half of it. The other half is being able to understand what’s inside. A handover usually includes:
- A README: how to run the project locally and how to deploy it.
- A list of environment variables and services, without the secret values, and who pays for each service.
- A short overview of the structure: where pages live, where content comes from, how a new page or block is added.
- A guide or a short video on editing content in the CMS.
- The design files and the brand assets the site uses.
A site is fully yours when another developer can open it and keep going.
The Stack Decides Who Can Pick It Up
WordPress has the largest pool of developers, and quality varies widely. Webflow and Framer need no code to edit, and anyone familiar with the builder can take over, but the site lives on that platform. We covered where that becomes a limit in When a Startup Outgrows Framer.
A custom site on Next.js runs on one of the most widely used web frameworks, so finding a developer is easy. What makes the difference is how the code is written. A standard structure, a common CMS such as Payload, Sanity or WordPress, and documentation make a site easy to hand over. A CMS one agency invented for itself, or code generated without any structure, makes it hard. The second case is common with products built quickly with AI tools, which we wrote about in From AI Prototype to Product.
Questions to Ask Before You Sign
Whose accounts will the domain, hosting and code be in? The answer should be yours, from the first day of the project.
What does the handover include? Ask to see a handover document from a past project.
Which CMS, and why? A widely used one is easier to support later than a custom build.
What happens after launch? A bug-fix period, a support plan, or neither. All three are fine as long as you know which one you’re getting.
These questions fit naturally into the scope of work, next to deliverables and timelines. For the wider picture of choosing a studio, see How to Choose a Branding Agency.
FAQ
Who should own the domain?
The company, in its own registrar account. The studio can be added to manage DNS during the project.
Is it a problem if the agency hosts the site?
It’s convenient during the project. Make sure the account is in your name, or that the agency will transfer it whenever you ask, and get that in writing.
Can another developer take over a Next.js site?
Yes, if the code follows a standard structure and comes with documentation. Next.js is among the most widely used frameworks, so there’s no shortage of people who know it.
What if the site runs on a custom CMS?
Ask who maintains it and how content would be moved out. If the answer is unclear, a common CMS is the safer choice for the next rebuild.
Conclusion
Keep the accounts in the company’s name, ask for a real handover, and choose a stack another developer can read. Then the site keeps working for you whoever builds the next version. If you’re planning a new site and want it set up this way, tell us what’s coming up.

