CELORA /
Your website is live. Do you have what you need to run it?
The design is approved and the website is live. Six months later, you need to update a phone number or renew the domain, and discover that only the previous developer can do it. The missing piece is a complete handover.
Here is what to agree before commissioning a website and what to collect at launch. You do not need to become a developer; you need enough control to keep your business running.
In this article
The domain: who can renew your web address?
Check whose registrar account holds the domain, who is listed as its administrator and where renewal notices arrive. Your business should have access to that account and its recovery method. A website admin password is not a substitute for registrar access.
Decide this before registration: appoint someone from the business and agree how the developer receives temporary access. For an existing domain, record its current setup before work starts. Email delivery and search verification may also depend on DNS records.
Hosting and services: what will you pay after launch?
Ask for a list of ongoing costs: hosting, domain renewal, paid extensions, email delivery and external integrations. Each entry should explain its purpose, account owner and renewal process. Usage-based charges need a separate explanation.
A subscription platform can be a sensible choice. Know what can be exported and what depends on that platform. For custom development, clarify the runtime and dependencies. Receiving an archive does not automatically make a website portable.
Source files and a deployed copy are different
The folder serving visitors may not include the files used to build the project. Agree which source code, design files, assets and build instructions you will receive, subject to the contract and relevant licences.
Ask for a practical demonstration: where do you change a phone number, edit a service description and publish an update? If a developer is needed, clarify how to request the work and what support covers. A complex content management system may be unnecessary for two updates a year.
Enquiries: test receipt, not just the submit button
Send an agreed test enquiry from a phone and confirm that the intended person receives it. Check the subject line, customer contact details and error feedback. Establish where submissions are stored and who can access them.
Record who controls the email delivery service. Transfer passwords and secret keys securely, rather than leaving them in a public repository or a handover document. When changing providers, plan access changes without interrupting the form.
Analytics access should remain with the business
Confirm that your business representative has an appropriate role in Google Analytics, Yandex Metrica and search webmaster tools, where installed. Give the agency a separate working role. One contractor’s account should not be the only route to your data.
Document what each tracked event means: a submitted form, a phone-link click or a messenger visit. A click and a received enquiry are different events. This shared definition helps when reviewing marketing or changing specialists.
Backups: where are they, and how do you restore them?
A backup needs a date and a short description of its contents and restoration requirements. If the website uses a database, a file archive alone may be incomplete. Configuration and secrets require separate secure handling.
Agree on a restoration test in a staging environment if this is part of the scope. Without a test, an archive is not a verified recovery plan. Decide who creates new backups after updates and how long earlier copies are kept.
A short check before closing the project
Keep one handover document for operational information. It should not be a password list.
| Item | Useful confirmation |
|---|---|
| Domain and hosting | Your business can log in and understands renewal |
| Project materials | The delivered files and update process are clear |
| Enquiries | The intended person received an agreed test |
| Analytics | Access and event definitions are documented |
| Backup | Date, contents and restoration procedure are recorded |
| Support | Responsibilities and scope are agreed |
A missing item is a reason to clarify the handover, not automatically rebuild the website. You might arrange a separate source export or resolve domain access with its current administrator.
Discuss a manageable launch with CELORA
When planning a website, we propose agreeing account ownership, deliverables and support before launch. CELORA is based in Saint Petersburg and works remotely with businesses in other cities and countries. International website projects start at $500 or €500; scope and delivery dates are agreed for the task.
Already have a website but cannot tell where access is held or how to update it? Describe the situation and we can agree a useful review scope. A website address and your goal are enough for the first conversation. Do not send passwords through the enquiry form.
Discuss a website or handover · Website development · Preparing a useful brief