A business owner in Lagos hires a developer to build a website for her company.
The developer sends a quotation for ₦450,000. The package includes domain registration, hosting, website design, professional email setup, and one year of maintenance.
It sounds convenient. She pays the invoice, sends her company logo and product photographs, and waits for the project to be completed.
Three weeks later, the website goes live.
Everything looks good. Customers can browse the services, submit enquiries, and contact the business. The developer hands over a WordPress username and password, and the business owner assumes the project is complete.
For the next two years, she rarely thinks about the technical side of the website.
Then the business decides to redesign its website.
She contacts a new developer, who asks for access to the domain registrar, hosting control panel, and website files.
She doesn't have any of those details.
The original developer registered the domain using his own account, purchased the hosting under his business, and retained the administrative credentials.
The only access she has is a WordPress account that allows her to edit pages.
Now she wants to move the website, but she cannot independently change the nameservers, access the hosting account, or initiate a domain transfer.
The developer is no longer responding to messages.
She paid for the website. She has used it for two years. Her customers recognise the domain.
But she cannot fully control the infrastructure behind it.
This is a hypothetical situation, but it illustrates a problem that can affect businesses of different sizes.
Paying for a website does not automatically mean you control every account, licence, domain, and technical asset associated with it.
That distinction is worth understanding before you commission a website, not after a disagreement with your developer.
When most people think about website ownership, they imagine the visible website.
The homepage, company logo, service pages, photographs, contact form, and product catalogue.
But what visitors see is only one part of the system.
Behind a typical business website are several components that may be managed by different companies and individuals.
There is the domain name, which provides the public address.
There is the hosting account, which supplies the environment where the website runs.
There are website files, databases, themes, plugins, and other software.
There may also be business email accounts, payment gateway integrations, analytics services, security tools, and third-party subscriptions.
These components do not necessarily have the same owner, administrator, or legal status.
For example, you might own the copyright in your original website content while your developer controls the hosting account. You might control the hosting account but have no access to the domain registrar.
You might even have administrator access to WordPress without having permission to transfer a premium theme licence to another provider.
This is why I encourage business owners to think beyond the question, "Who designed my website?"
The more important question is:
Who controls the accounts and assets required to keep my website operating?
Let's begin with the domain.
Suppose your company operates at yourcompany.com.ng.
Customers have saved that address. It appears on invoices, business cards, social media profiles, and perhaps company vehicles.
Over time, the domain becomes an important part of how customers recognise and reach your business.
A domain registration does not mean you own a piece of the internet permanently. It gives the registered holder contractual rights to use the domain for a specified registration period, subject to the applicable registry and registrar rules.
That distinction matters.
The domain must be renewed, and its registration information must remain accurate.
If a developer registers your domain using their own account and contact information, the arrangement may become complicated when you want to manage or transfer it.
The registrant is the party identified in the registration records as holding the domain registration rights.
Depending on the domain extension and applicable rules, registrant information may be accessible through registration data lookup services, although personal details may be redacted.
For many generic top-level domains, ICANN's registration framework establishes important rules concerning registrants, registrars, and domain transfers.
For .ng domains, the applicable registry policies and registrar processes must also be considered.
The safest arrangement for most businesses is to ensure that the domain is registered with accurate business-controlled details and that the business has appropriate access to the registrar account.
If a developer is assisting with registration, they can still perform the technical work without becoming the only person capable of managing the domain.
At SIRSTEVEHQ, businesses can register domains and manage relevant domain settings through their Client Area.
A business owner can maintain control of the domain account while allowing a developer to assist with website configuration.
This is generally preferable to placing an essential business domain entirely under an unrelated personal account.
Your domain is the address. Your hosting account is the environment where your website files and applications operate.
If the developer purchases hosting under their own account, they may control important functions such as account administration, billing, file access, database management, and service cancellation.
This arrangement is not automatically improper.
Some developers and agencies offer fully managed website services, where hosting is part of a broader maintenance contract.
In those cases, the agency may reasonably administer the hosting environment on the client's behalf.
The problem arises when the business owner does not understand the arrangement or when the contract does not explain what happens if the relationship ends.
For example, can the client request a backup?
Can the website be migrated to another provider?
Who is responsible for renewing the hosting service?
What happens if the agency closes or the developer becomes unavailable?
These questions should be answered before the website goes live.
If you are hiring a developer to build a website, you can purchase an appropriate SIRSTEVEHQ hosting plan under your own business account.
Depending on your requirements, this could be cPanel Hosting, WordPress Hosting, Cloud Hosting, or another suitable hosting service.
The developer can then receive the access necessary to complete the project.
The important principle is that the business remains responsible for its primary account and billing relationship.
If you later change developers, you can review and revoke the previous developer's access without necessarily changing your hosting provider.
For customers who need to move a hosting service to another SIRSTEVEHQ account, an account-to-account service transfer can be requested through the Client Area support ticket system, subject to the applicable verification and service requirements.
This is different from simply giving someone your primary account password, which may expose unrelated services managed under the same account.
This is one of the most misunderstood parts of website management.
A developer finishes a WordPress project and sends the business owner a login link.
The business owner can edit pages, publish blog posts, upload photographs, and manage website content.
Everything appears normal.
But WordPress access and hosting account access are different things.
A WordPress administrator may have extensive permissions within the WordPress application, including the ability to manage users and plugins, depending on the site's configuration.
However, that access does not necessarily provide control over the domain registration, hosting billing, DNS settings, server configuration, or backups stored outside WordPress.
Likewise, having access to the hosting control panel does not automatically give you ownership of third-party software licences or content created under a separate agreement.
A proper handover should therefore cover more than one username and password.
For a typical WordPress website, the business should understand how to access the WordPress dashboard, hosting environment, domain account, and any essential third-party services.
Where possible, use individual accounts and appropriate access permissions instead of sharing a single administrator password.
This is where the discussion becomes more complicated.
Paying a developer to create a website does not always mean that every element of the finished project becomes your intellectual property.
Ownership depends on the applicable law, contractual terms, licensing arrangements, and the nature of the work.
For example, your business may provide its own logo, photographs, product descriptions, and other original materials.
Those assets may already belong to your business or be licensed for its use.
The developer may create custom layouts, graphics, code, or written content as part of the project.
Whether copyright in those deliverables transfers to the client should be addressed in the agreement.
The website may also contain third-party components.
WordPress itself is distributed under the GNU General Public License. Many WordPress plugins and themes have their own licensing arrangements, and premium services may require ongoing subscriptions.
Your developer cannot necessarily transfer rights they do not possess.
In Nigeria, the Copyright Act 2022 provides the legal framework for many copyright-related questions, but the outcome of a particular dispute depends on the facts and applicable contractual arrangements.
For substantial projects, it is worth having a qualified legal professional review the ownership and intellectual property provisions.
A well-written development agreement should identify the deliverables, the rights being granted or assigned, and any third-party components that remain subject to separate licences.
Imagine your developer sets up your company email addresses as part of the website project.
You begin using hello@yourcompany.com and accounts@yourcompany.com for customer communication.
Everything works until you decide to change your website hosting.
You then discover that the email accounts were created inside the developer's hosting environment.
This can create additional migration work, especially if the business has years of important correspondence stored in those mailboxes.
Email should therefore be included in your website ownership and continuity planning.
Find out who administers the mailboxes, where messages are stored, what backup options exist, and how email can be migrated if the service changes.
For businesses that want email to be managed separately from website hosting, SIRSTEVEHQ Email Hosting provides a dedicated solution for professional custom-domain email.
This can be useful when a company wants to maintain its email service independently of future website redesigns or hosting changes.
However, the business should still maintain control of the domain, DNS configuration, and relevant administrative credentials.
Separating services can improve flexibility, but it does not eliminate the need for proper account management.
This is a situation nobody wants to experience.
You have paid for the website, but the developer refuses to provide the credentials or information required to manage it.
The first step is to establish exactly what the agreement says.
Review your quotation, invoices, contract, emails, and messages.
Look for provisions concerning domain registration, hosting, intellectual property, administrative access, maintenance, and project handover.
Next, identify which assets are affected.
Is the developer withholding WordPress access, hosting credentials, domain management, source files, or all of them?
The appropriate solution depends on the specific issue.
If your business is the verified registrant of a domain, you may be able to pursue account recovery or a transfer through the registrar's established processes.
If the domain is registered under the developer's details, the situation may require additional evidence or a contractual resolution.
Hosting providers must also respect account ownership, privacy, and security obligations.
A provider generally cannot grant access to someone else's hosting account simply because another party claims to have paid for the website.
At SIRSTEVEHQ, requests involving account access or service transfers must follow the appropriate verification and support procedures.
If a dispute cannot be resolved through communication, seek legal advice rather than attempting unauthorised access to the developer's accounts.
Most importantly, avoid allowing the dispute to escalate into a situation where your domain expires or important website data becomes unavailable.
The best time to establish control over your digital assets is before the project begins.
You do not need to become a technical expert.
You simply need to make a few important decisions early.
Choose a domain that represents your company and register it through an account you control.
If you use SIRSTEVEHQ Domain Registration, keep the primary Client Area credentials and recovery information under your control.
Your developer can assist with DNS configuration without becoming the only person responsible for the domain.
Decide whether your business will purchase hosting directly or whether the developer will provide a managed hosting service.
Either approach can work, but the responsibilities and exit arrangements should be documented.
If you prefer direct control, purchase your SIRSTEVEHQ hosting service under your business account and provide the developer with appropriately limited access.
Your agreement should clearly identify who owns or is licensed to use the final website deliverables.
It should also explain what access, documentation, backups, and files will be provided at completion.
Do not rely solely on verbal assurances.
Avoid giving a developer your primary domain registrar password, email account password, or hosting billing credentials unless absolutely necessary.
Where supported, create individual user accounts with the permissions required for the work.
After the project, review those permissions and remove access that is no longer needed.
A backup can help protect your business if the website becomes unavailable or the working relationship ends.
But not every backup contains everything required for a complete restoration.
For a WordPress website, you may need website files, the database, configuration information, and details of third-party dependencies.
If your SIRSTEVEHQ hosting service includes or supports backup options, understand what is covered, how long backups are retained, and how restoration works.
Do not assume that the existence of a backup feature removes the need for a recovery plan.
When you purchase a physical shop, you expect to receive the keys and the documents relevant to your occupancy or ownership.
A website project deserves a similarly structured handover.
The developer should explain where the website is hosted, how it is managed, which accounts are essential, and what ongoing services must be renewed.
A good handover should also include enough documentation for another qualified professional to maintain the website.
For example, if the site uses WordPress, you should know which plugins are important, whether any require paid licences, and how updates and backups are handled.
If the website includes payment integrations, you should know which business accounts are connected and who controls the relevant credentials.
If it uses a third-party email service, you should know where the mailboxes are administered.
A website is not properly handed over simply because the homepage is visible and the developer has received final payment.
The business needs the information and access required to operate it responsibly.
Before accepting a completed website project, review the following:
| Asset or access | What to confirm |
|---|---|
| Domain name | Correct registrant details, registrar access, renewal responsibility |
| Hosting account | Account ownership, billing access, control panel access |
| Website application | Appropriate administrator access |
| Website files and database | Availability of usable backups or exports |
| Business email | Mailbox administration, recovery, and migration arrangements |
| SSL certificate | Renewal and configuration responsibilities |
| Premium themes and plugins | Licence ownership, renewal costs, transfer restrictions |
| Payment integrations | Business-controlled payment accounts and credentials |
| Analytics and search tools | Appropriate ownership and administrator permissions |
| Website documentation | Important configurations, dependencies, and maintenance instructions |
| Developer access | Clear permissions and a process for revocation |
| Intellectual property | Written ownership or licensing terms for deliverables |
You may not need every item for a simple website.
However, the more important your website becomes to daily business operations, the more valuable this documentation will be.
There is nothing inherently wrong with allowing a developer or agency to manage your website.
Many business owners do not have the time or technical knowledge to maintain hosting infrastructure, install updates, troubleshoot errors, or monitor website security.
Delegating those responsibilities can be a sensible business decision.
The distinction is between delegating management and surrendering control without understanding the consequences.
A good managed-service arrangement should make responsibilities clear.
The developer or agency may handle technical operations while the business retains the contractual rights, account access, documentation, and exit options established in the agreement.
This arrangement can benefit both parties.
The business receives professional technical assistance, while the developer works within a defined scope.
Problems often arise when neither side has documented the relationship.
The business owner assumes everything belongs to them, while the developer assumes the hosting account, software subscriptions, or technical configuration remain under their own control.
Clear expectations reduce the likelihood of disputes.
Having worked in the hosting industry through SIRSTEVEHQ, I believe website ownership deserves more attention than it typically receives during the early stages of a project.
Many entrepreneurs focus on the visible result.
They want a beautiful homepage, modern design, responsive layout, and an attractive presentation of their services.
Those things matter.
But the invisible parts of the website are equally important.
Who receives domain renewal notices?
Who can change the DNS records?
Who can access the hosting account if the website stops working?
Who has the latest backup?
Who controls the email accounts customers use to contact the business?
These are not questions that should be left until a disagreement occurs.
For a business launching its first website, my recommendation is to establish a clear digital ownership structure from the beginning.
Register your domain through SIRSTEVEHQ using an account controlled by your business.
Choose an appropriate SIRSTEVEHQ hosting environment, whether Shared Hosting, WordPress Hosting, or Cloud Hosting, based on the website's actual requirements.
If you hire a developer, agree on the necessary access and handover arrangements before work begins.
If you need professional email, consider SIRSTEVEHQ Email Hosting as part of your broader communication setup.
The objective is not to make every business owner responsible for technical administration.
It is to ensure that the business can continue operating even when the people managing its technology change.
A website can become one of the most important assets associated with your business.
It may generate enquiries, process orders, support customers, and represent your brand to people who have never met you.
Over time, customers may come to recognise your domain name as readily as they recognise your company name.
That makes proper ownership and access arrangements essential.
Your developer may be talented, trustworthy, and committed to your business. You may have worked together for years without a problem.
Even then, clear documentation and account control are good business practices.
People change jobs. Agencies close. Business relationships evolve. Technical requirements change.
Your website should not become impossible to manage simply because one individual is unavailable.
The real measure of website ownership is not just whether you paid for its development. It is whether you have the rights, access, and information necessary to keep your business online.
Before commissioning your next website, make sure you understand what you are purchasing, what you will control, and what happens when the project ends.
A beautiful website is valuable.
A beautiful website that your business can confidently manage, maintain, and move when necessary is even more valuable.
Not necessarily. Ownership of website content, custom code, design elements, and other deliverables depends on applicable law, contracts, and licensing arrangements. Paying for development does not automatically establish control over domain and hosting accounts.
A developer may register a domain as part of an agreed service arrangement. However, the registrant details, contractual terms, and applicable registry policies determine the relevant rights and responsibilities. Businesses should clarify these arrangements before registration.
Possibly. Migration may be possible if you can obtain the required website files, database, and configuration information. Without access or backups, recovery can become more difficult. Any access or transfer must be authorised.
They do not have to be. Domain registration and hosting can be provided by different companies. What matters is maintaining control of the relevant accounts and understanding how the services connect.
The available access methods depend on the hosting platform and service. Where supported, use separate control panel or application accounts with appropriate permissions. Avoid sharing primary Client Area credentials unnecessarily.
Your options depend on which accounts and assets your business controls. If you retain access to your domain, hosting, website backups, and administrative tools, another qualified developer may be able to continue the work. If essential access is missing, you may need to pursue recovery through the relevant provider or contractual process.
The responsibility should be agreed in advance. If the business purchases the services directly, it should maintain an internal renewal process. If an agency manages renewals, the contract should explain how payments, notices, and service continuity are handled.
SIRSTEVEHQ has a service transfer request process through the Client Area support ticket system. Transfers are subject to the relevant account verification, authorisation, and service requirements.
Comments (0)
No comments yet. Be the first to comment!