# Seven ownership questions to ask before hiring a website agency > Clarify account ownership, source files, licensing, editing, support, and exit arrangements before your website project begins. - Page: https://www.brandbakery.tech/pulse/website-agency-ownership-questions - Last updated: 2026-10-01 Breadcrumb: [Home](https://www.brandbakery.tech/) > [Pulse](https://www.brandbakery.tech/pulse) > Seven ownership questions to ask before hiring a website agency - **By:** Abhishek - **Published:** 2026-10-01 - **Reading time:** 4 min - **Topics:** Digital Growth The best time to ask who owns your website is before somebody starts building it. That conversation can feel less exciting than choosing layouts, but it prevents an unpleasant surprise later: a domain registered under a former contractor’s account, an essential subscription nobody knew about, or a site that only one person can update. Ownership is not one yes-or-no question. A website involves accounts, software, content, licensed assets, and ongoing services. Ask these seven questions and put the agreed answers in the project scope. This is a procurement checklist, not a substitute for legal advice on a contract. ## 1. Who controls the domain? Ask whose account will hold the domain registration, who receives renewal notices, and how the business can recover access. The business should have a clear, durable route to control its own address. An agency can help configure a domain without being the only person able to access it. Keep recovery details current and use business-controlled accounts where practical. Record when the domain renews and who pays for it. Also ask who can change DNS records. Those records may affect email as well as the website, so a website update should not casually disrupt business mail. ## 2. Who owns the hosting and service accounts? List the services required to operate the site: hosting, email delivery, content management, analytics, forms, booking, payments, or anything else in scope. Ask whether each account belongs to you or is managed by the agency. Either arrangement needs clear responsibilities. If the agency manages a service, understand what is included, how access works, and what happens if you stop working together. Ask for recurring costs separately from the build fee. A low project price can become difficult to compare when essential subscriptions appear only near launch. ## 3. What files and rights are included? Ask what you receive at handover: website source code where applicable, design files, logos, written content, image exports, and configuration documentation. Be specific about editable files rather than assuming “all assets” means the same thing to both parties. Some components may be licensed from third parties. Typefaces, stock images, plugins, templates, and software can have different terms. Ask who holds each licence and whether continued use requires a subscription or separate payment. Do not assume that commissioning a project automatically settles every intellectual-property question. Put the agreed rights and exclusions in writing and seek qualified advice if the arrangement is material to your business. ## 4. What can our team update safely? List the edits you expect to make: opening hours, service descriptions, articles, photographs, prices, or team profiles. Ask for a demonstration of those exact tasks. A claim that the site is “fully editable” is less useful than watching a non-technical colleague update a service description without breaking the layout. Clarify whether changing page structure requires developer work. Agree what training and documentation are included. A short recorded walkthrough or written guide can be more useful than a long handover call nobody remembers. ## 5. How do enquiries reach us? Ask where form submissions go, which service sends them, and what happens if delivery fails. Test the real receiving inbox before accepting the project as complete. Clarify who monitors failures and who handles spam. If enquiries are stored, ask where, who has access, and how retention is managed. Sensitive message content should not casually appear in public analytics or debugging tools. Include the reply path in testing. A message arriving from a notification address is not enough if clicking Reply sends your response somewhere the customer will never see. ## 6. What support continues after launch? Separate defect fixes from ongoing changes. Ask how long launch support lasts, what it covers, and how a request is submitted. Clarify expected response arrangements without assuming round-the-clock support is included. For ongoing maintenance, ask who updates dependencies, checks contact delivery, manages backups where needed, and responds to outages. Some sites require more care than others; the agreement should reflect the actual system. Avoid buying an undefined maintenance package simply because it sounds reassuring. Ask what work is performed and what evidence you receive. ## 7. What happens if we change agencies? Discuss exit while everyone is on good terms. Ask what gets transferred, in which format, and whether there are migration costs or technical restrictions. Establish how access is removed after handover without locking out the business. A useful handover record includes account owners, service names, renewal responsibilities, repository location where relevant, deployment instructions, and recovery procedures. It should not be a document filled with unprotected passwords. Use these answers to compare proposals on the same basis. The cheapest option may still be right for a limited need, but the limitations should be visible before you buy. Our [business website service](https://www.brandbakery.tech/services/web) includes a discussion of scope and handover from the start. Bring this list to the conversation, whichever agency you choose. A clear arrangement protects the project as much as it protects the finished website. ## Keep reading - [More from Pulse](https://www.brandbakery.tech/pulse) - Start a project: https://www.brandbakery.tech/contact --- Brand Bakery is a design-first digital studio in New Delhi. Start an enquiry at https://www.brandbakery.tech/contact or email support@brandbakery.tech. This is the Markdown copy of https://www.brandbakery.tech/pulse/website-agency-ownership-questions; the site index for language models is https://www.brandbakery.tech/llms.txt.