What Should You Own After Paying a Developer to Build Your Website?

Who Owns Your Website? What a Developer Must Hand Over When It's Built

A
Arijeniwa Oluwasina Oromidayo
Reviewed by Arijeniwa Oluwasina OromidayoOctober 2, 202614 min read

Here is a story that plays out more often than it should. A founder pays a freelancer in full, the website goes live, and everyone is happy. Two years later an investor asks one question: "Do you own the code?" Nobody can prove it. The freelancer has moved cities and stopped answering, the hosting is on his personal account, and the domain is registered to an email address nobody remembers. The deal stalls for weeks while the founder tracks him down.

None of that needs to happen. This guide pulls together everything we know about the day a website changes hands: what you should legally own, what the developer must give you, how people end up locked in without noticing, how to protect the site while the work is going on, and how to move to a new developer if you are already stuck. It is general information, not legal advice. For anything large, have a Nigerian lawyer read your agreement.

Paying for it is not the same as owning it

When someone creates something original, such as code or a design, the copyright generally starts with that person. Paying them does not automatically move it to you. Many countries work this way, and the safe assumption in Nigeria is the same: copyright starts with the creator, and a transfer needs to be in writing.

So without a signed agreement, the developer may still hold the copyright to the code they wrote for you, and you may only have the right to use it. Plenty of developers never make trouble about this. But "they probably will not" is a weak foundation for something your business depends on.

A diagram showing what a client should own, what is licensed, and what the developer keeps

What should be yours

  • The domain name, registered in your name with an email you control.
  • Every account the site depends on: hosting, DNS, email, analytics, payment gateway and SMS or messaging accounts.
  • The custom code written for you, through a written assignment of copyright, usually effective once you have paid in full.
  • Design files and brand assets: logo files, design source files and any artwork made for you.
  • Your content: the text, photos and videos you supplied or paid for.
  • Your data: customer lists, orders, messages and records, with the right to export them.
  • Credentials and keys for everything the site uses.
  • Backups and written instructions.

What you usually will not own, and that is normal

Open-source software. Most modern websites are built on free tools and libraries that belong to their authors. A developer cannot give you ownership of those. You get the right to use them under their licence, which is usually generous.

The developer's reusable tools. Many developers keep a personal library of code they use on every project. A fair arrangement is that they keep ownership of it and you receive a permanent, unrestricted licence to use it inside your project. Ask for the words "perpetual" and "irrevocable" so it cannot be taken away later.

Paid themes, plugins and stock images. You buy a licence, not ownership. Make sure the licence is in your name and covers commercial use.

Subscription platforms. If your site runs on a hosted platform, you are renting it. That is a legitimate choice, as long as you know you are renting.

When ownership passes, and what to put in writing

The usual arrangement is that ownership of the custom work transfers when you have paid the full amount. That protects the developer from non-payment and is reasonable. What matters is that the clause exists and that the transfer happens automatically, without the developer needing to agree again later.

A short agreement should cover at least these points:

  • what is being built, the total price and the payment dates;
  • that copyright in the custom work passes to you on full payment;
  • that you get a licence to any pre-existing tools or third-party parts the developer uses;
  • that the domain, hosting and accounts are in your name;
  • that you receive the full code, data and access at the end;
  • how either side can end the agreement.

None of this needs complicated language. Chat messages can show intention, but "we agreed on WhatsApp" is a weak way to settle ownership. If you already have a project with no agreement, ask the developer for a simple written confirmation now. Most will sign it, and it is far easier before a quarrel than after.

What a proper handover contains

A website is not finished when it looks finished. It is finished when you can run it without the person who built it. Agree the handover in the contract from the start and tie the final payment to it.

  1. The source code with its history. It should live in a repository (a code storage service such as GitHub) that you own or that is moved into your account. Ask for the full history of changes, not only a zip of the final version. The history shows what changed and why, and it is very valuable to the next developer.
  2. Admin access at the highest level. You should be an owner of the live site, not only an editor.
  3. Every account in your name, plus a list showing each service, what it does, who pays and how much. Move credentials through a password manager, not an old email thread.
  4. A full backup of the database and uploaded files as of launch day, stored where you control it. Someone should confirm it can really be restored, because an untested backup is only a hope.
  5. Short written instructions: how the project is organised, how to run it, how it goes online, what the settings are (not the secret values) and which outside services it uses. A short screen recording of the admin area helps you and your staff.
  6. Licences and keys for paid themes and tools, in your name so updates keep arriving.
  7. Training and a support period. A short session on editing content and handling orders, and a few weeks after launch in which bugs are fixed at no extra cost.

Before you pay the final instalment, run a small fire drill. Can you log into every account on the list? Can you add a product or publish a post yourself? Can the backup be restored on a test copy? Could a colleague of the developer put a tiny change online using only the instructions? If any answer is no, the handover is not complete.

Eight ways people end up locked in

Lock-in sounds technical, but the idea is simple: you cannot leave without losing something important. Sometimes it is deliberate. More often it builds up quietly through small choices nobody questioned. Each trap has a cheap fix on day one.

  • Hosting on the developer's own server. They control whether the site stays online. Open the hosting account yourself and add the developer as a user.
  • The domain in their name. Legally and practically, they hold your address. Register it yourself, with your email and your payment.
  • Code you cannot get. If the source lives on their laptop, you own a site you can never change. Keep it in a repository you control and ask for steady updates as the work progresses. Seeing it fill up over the weeks is also a good sign the work is real.
  • A home-made setup. If everything runs on a private system only they understand, the next developer will struggle. Ask what the site is built with. Popular, well-supported tools mean you can find another developer easily.
  • No documentation. A working site nobody has explained is a car with no manual and a locked bonnet.
  • Licences and accounts in their name. You lose the paid theme or plugin when you leave. Buy them yourself or have them transferred before the final payment.
  • Long contracts with exit penalties. A twelve-month maintenance contract with heavy penalties for leaving is lock-in on paper. Prefer short, monthly arrangements.
  • Your data in someone else's system. You should be able to export customer lists, orders and content in an ordinary format whenever you like. Ask early: "How do I get all my data out, and how long does it take?"

Write your exit into the agreement in plain words: on request, and within a set number of days, the developer will hand over the code, the data and all access, and will cooperate with the next developer. A fair developer agrees. One who refuses has told you something.

A quick test: if this developer stopped replying tomorrow, could someone else take over within a week? Do you have the code, the logins, the backups and the instructions? If not, you are locked in whatever the contract says, and the time to fix that is while the relationship is good.

A word about platforms, including ours

Ready-made platforms and site builders, ours included, work differently. You use a system someone else built and runs instead of owning custom code. For many small businesses that is the right trade, since it is faster and far cheaper and there is nothing to maintain. But it is still a trade. Whatever you use, make sure your domain is registered in your own name and that you know how to get your customer and order data out if you ever leave. Ask any provider those two questions before you commit.

Protect the site while the developer is working

Hiring a developer lets someone into the back rooms of your business. They may be able to see customer details, change pages, touch payment settings or take the site offline. Most are honest and careful, but even honest people make mistakes. These habits protect you either way, and none needs technical skill.

  • Give only the access that is needed. Never hand over an owner password. Create a separate login with just the permissions the job needs. A designer changing a page does not need your customer list or payment settings.
  • Keep the important accounts in your name, and be wary of anyone who insists on holding them for you.
  • Turn on two-step login for email, domain registrar, hosting and payment accounts. Your email is the master key to everything else, so protect it first. Share credentials through a password manager, not WhatsApp.
  • Make them work on a staging copy. A half-finished change should never go live while customers are using the site.
  • Take a backup before anything big, and ask in writing: "Please confirm a full backup was taken today and where it is."
  • Pay in stages: a deposit to begin, a payment when you see a working first version and the balance after delivery and checking.
  • Ask about licences. Some developers use pirated "nulled" themes and plugins, which often hide code that gives someone else access to your site.
  • Look after your customers' data. If the site collects names, phone numbers or payment details, you are responsible for protecting them even when someone else handles the technical side. The Nigeria Data Protection Act 2023 expects organisations to look after personal data properly. Ask where data is stored, who can see it and how it is backed up.
  • Remove access when the work ends. Delete the developer's logins and rotate shared passwords and keys. Old access nobody remembers is one of the quietest risks in a small business.

Already stuck? How to move to a new developer safely

Maybe the developer stopped replying, the site is slow and nobody will fix it, or you have simply outgrown them. The thing you are moving is your business's public face, so the fear of losing pages, orders or rankings is fair. The trick is to move in a careful order and never switch anything off until the new version is proven.

  1. List what you actually have: the domain and who it is registered to, the hosting and who pays, where the code and database live, which outside services are used and who holds each login. Most "lost website" stories start with a piece nobody knew existed.
  2. Secure the accounts that should already be yours. If the domain is in the old developer's name, ask for a transfer, politely and persistently. Do the same for hosting, analytics and payment or messaging accounts.
  3. Take full backups and store them separately: all code, the whole database and every uploaded file. Then try restoring them on a test copy.
  4. Let the new developer review before committing. A short check of code quality and security tells them whether to repair or rebuild. An independent review, such as our code audit service, can tell you honestly whether the current site is worth saving.
  5. Build or fix on a copy, never on the live site.
  6. Protect your Google rankings. Keep page addresses the same wherever you can. Where one must change, set up redirects from the old address to the new one, and map old to new before launch.
  7. Test everything that touches money or customers: a real test order, a small real payment, every form, a customer login and an admin login, and check old accounts and orders survived.
  8. Switch over at a quiet time. A day or two before, have the new developer lower the DNS "time to live" setting so the change spreads faster and is easier to undo. Keep the old version running, untouched, for a while afterwards.
  9. Change every password and key. Rotate hosting, admin, database, API and payment keys. It is not an accusation, only hygiene.

If the old developer will not cooperate, stay calm and keep written records. Send a polite email listing exactly what you need and by when, and keep proof of payments and any agreement. If the domain is in their name, your registrar may have a dispute process. If the code is truly unavailable, the visible pages and design can often be rebuilt from the live site, but the behind-the-scenes logic and database cannot be copied from outside. That is why having the code in your hands from the start matters so much. If it is heading for a real dispute, speak to a Nigerian lawyer.

Three mistakes to avoid on the way: switching off the old site before the new one is proven, forgetting business email that runs through your domain, and forgetting the small integrations such as payment webhooks, SMS sender names and analytics, which all need pointing at the new setup.

A short example

Illustrative example: the people, businesses and numbers in this section are made up to show how this works. They are not real clients or real results.

A boutique owner in Enugu had a shop built by a developer who then went quiet. She found the domain was in her own name but the hosting was in his account. She asked politely, then formally, for a backup, and received a database copy and the files. She paid a new developer for a review, which found the site was usable. The new developer set it up on hosting in her name, tested checkout on a staging copy and switched the domain on a Sunday evening. Orders never stopped. A school down the road had given out its main password instead; a year after its freelancer left, his old login still worked.

Where to go next

Before you hire, read how to hire a web developer in Nigeria without getting burned and how to brief a developer and get a quote you can compare. If you want to talk through a project with us, send a custom project request and ask us the same ownership questions you would ask anyone else. Get the answers in writing.

A
Arijeniwa Oluwasina Oromidayo
Co-Founder

Software engineer with over 9 years of experience in software development and digital technology. B.Sc. in Industrial Chemistry from Adekunle Ajasin University. Has worked across web development, mobile applications, e-commerce platforms, VTU and fintech solutions, API integrations and custom software.

Reviewed by Arijeniwa Oluwasina Oromidayo, Co-Founder

Comments

No comments yet. Be the first to share your thoughts.

Leave a comment

Comments are reviewed before they appear. Links are not allowed.

Related Articles