How to choose the right web developer in Abuja or Lagos

In this article14 sections

1. Why choosing a web developer in Abuja or Lagos is harder than it looks
2. Step one: know what you need before you call any developer
3. Where to find a good web developer in Abuja or Lagos
4. How to check a portfolio and references properly
5. Questions to ask a web developer before you pay anything
6. Red flags: how to spot a bad web developer in Nigeria
7. Freelancer, agency or a consultant-led team: who should you hire?
8. Contracts, payments and ownership: how to protect your money
9. How to manage the project so it finishes on time
10. After launch: support, training and maintenance
11. Does it matter if your web developer is in Abuja or Lagos?
12. Key takeaways
13. Frequently asked questions
14. Your next step: talk to a developer you can check

Musa owns a restaurant in Wuse 2 in Abuja. Last year he paid ₦150,000 upfront to a “developer” he found through a friend’s WhatsApp status, and another ₦100,000 two weeks later when the young man said the design was “almost ready”. Then the calls stopped ringing. The number went to voicemail, the WhatsApp ticks turned grey, and someone told Musa that the developer had moved to Dubai. Three months later, Musa had no website, no refund and no idea who owned the domain name he had paid for.

Choosing a web developer in Abuja or Lagos should not feel like gambling, but for many business owners it does. Nobody in Nigeria needs a licence to call themselves a developer. Some are brilliant and have built systems for banks and startups. Some learned last month and are practising on your money. From the outside, both can show you a pretty screenshot. This guide will show you how to tell them apart.

I have been building websites and business software for eight years, and I have also been hired many times to fix other people’s unfinished projects. In this article I will give you a clear process: what to prepare, where to look, how to check a portfolio, the exact questions to ask, the red flags to run from, how to structure payments and contracts, and how to protect yourself after launch. You can use it whether you hire me, a friend, a freelancer or a big agency.

Why choosing a web developer in Abuja or Lagos is harder than it looks

Buying a website is not like buying a bag of rice. You cannot inspect it on the spot, and you often cannot judge the quality until months later when something breaks. That gap between what you can see and what you are really buying is where most bad experiences begin.

Anybody can call themselves a developer

There is no council for web developers in Nigeria, no exam and no licence. A person with a laptop and a free template can advertise on Instagram tomorrow morning. That is not always bad, because many of the best people I know are self-taught. But it means the title tells you nothing. Your protection has to come from your own checking, not from a certificate on the wall.

The japa effect

Many experienced Nigerian developers have moved abroad in the japa wave, and many more now work remotely for foreign companies, paid in dollars. That is good for them, but it means fewer senior people are available for small local projects, and those who remain can be busy or expensive. It also means some clients end up with beginners who are excited to take any job at any price. There is a gap between those two groups, and the right developer for you often sits in that gap: experienced enough to be reliable, and committed to local clients.

Deals on WhatsApp with no paperwork

Most website deals in Nigeria happen on WhatsApp voice notes and bank transfers. There is no written scope, no contract and no clear delivery date. When a problem comes, each side remembers the deal differently. Then the client says “you promised me a booking system” and the developer says “I never said that”. A short written agreement, even a two-page one, solves most of these arguments before they start.

Why this matters in Nigeria: your customers’ data and your reputation

A developer does not only build pages. They often get access to your customer enquiries, your email, your payment gateway settings and sometimes your bank-facing accounts. A careless or dishonest developer can leak customer phone numbers, leave a payment page open to fraud, or lock you out of your own accounts. The Nigeria Data Protection Act expects businesses to handle personal information responsibly, and if a customer complains, the business owner answers, not the developer who has moved on.

So think of the choice as hiring a person who will hold a set of keys to your business. Ask how they store passwords, whether they use a shared password manager, and who else will have access to your site. Aisha, who runs a diagnostic centre in Abuja, told her developer that only two named people would ever have admin access, and that any change of staff would be reported to her within a day. It was a small rule that made the whole arrangement feel safer for both of them.

Step one: know what you need before you call any developer

The biggest reason projects go wrong is not the developer. It is that the client cannot say clearly what they want. A developer who hears “I need a website” will build whatever is easiest for them. A developer who hears a clear brief will build something that helps your business.

Write the one job of your website

Finish this sentence: “After the website launches, I want more people to ____.” It could be call me, book a table, request a quote, buy online, apply for admission or donate. If you have three jobs, choose the most important one first. Everything else can come in stage two. For a plain-English guide on this, my article on why every Nigerian business needs a proper website in 2026 shows how to decide.

List your pages and must-have features

Write a simple list. Home, about, services, gallery, contact and FAQ. Do you need online payment? A booking calendar? A place to upload documents? A blog? WhatsApp button? Also list three websites you like and say why, and one you hate and say why. That single page saves hours of guessing.

Decide your budget range

Give the developer a range, not a secret. If you say “I have between ₦300,000 and ₦500,000”, a good developer will tell you honestly what fits inside it. If you hide the budget, you will get random quotes that are impossible to compare. To set a realistic range, read my breakdown of website costs in Nigeria in 2026.

Prepare your content early

Gather your logo, photos, prices, addresses, phone numbers, CAC details and any customer reviews you can share. The more you prepare, the faster and cheaper your project will be. Late content is the top cause of delays in projects I manage, far more common than technical problems.

Where to find a good web developer in Abuja or Lagos

You will find developers everywhere, but the quality of the source matters. Here are the places I recommend, with honest pros and cons.

Start with referrals

Ask three business owners in your area whose website you admire who built it. Then go to the site on your phone and check whether you would trust it as a stranger. Ask the owner two things: did the developer finish on time, and would you hire them again? That single conversation is worth more than ten adverts.

Look at how they present themselves

A developer who builds websites should have a decent website. Look at how they write, whether they answer your first message clearly, and whether their own site loads quickly on your phone. If the person building your site is careless with their own, do not expect them to be careful with yours.

Use communities carefully

Tech communities in Lagos and Abuja, alumni groups from programmes like Andela, and developer meetups are good places to meet real engineers. Post exactly what you need and your budget range, and be ready to receive many replies. Then shortlist two or three and follow the checking steps in the next sections.

How to check a portfolio and references properly

Every developer shows a portfolio. Very few clients check it properly. A portfolio can be a page of screenshots taken from templates or from other people’s work. You must see the real thing.

Open the live sites on your phone

Ask for links to at least three live websites, not images. Open each one on your phone, using mobile data and not office Wi-Fi. Count the seconds it takes to load. Tap the menu, the phone number and the contact form. Try the site in both portrait and landscape. If pages are slow, buttons are tiny or text runs off the screen, that is how your site will look too.

Call two past clients

Ask the developer for two clients you can phone, not only testimonials on a page. When you call, ask simple questions:

• Did the project finish on the date promised?
• Did the final price match the quote?
• What happened when something went wrong after launch?
• Who owns the domain and hosting today?
• Would you hire them again?

If the developer cannot give you any phone numbers, ask why. Sometimes the answer is fair, for example, an NDA (a confidentiality agreement) with a big client. Often the answer is that there are no happy clients to call.

Look at results, not just design

A beautiful site that brings no enquiries is a failure. Ask each developer: “What changed for your client after the website went live?” Good answers are specific: more bookings, faster enquiries, fewer WhatsApp questions, better Google visibility. Weak answers are “they were very happy” and “it looked great”.

Check that they really built it

Some people copy screenshots from other developers. Ask the developer to explain how they built one project: what tools they used, what was difficult, what they would do differently. A real builder will speak easily and honestly, including about mistakes. Someone bluffing will speak in buzzwords.

Questions to ask a web developer before you pay anything

A good meeting with a developer feels like a doctor’s consultation. They ask you many questions first. Then you ask yours. Here are the questions I want every client to ask me, and any other developer, grouped by topic. Write the answers down, because later you will forget who said what.

About ownership

1. Will the domain name be registered in my name or my company’s name?
2. Will I receive the hosting login, the admin login and the email settings when the project ends?
3. Who owns the design files and the code after I pay in full?

About the process

4. How many pages and features are included in this price, and what is not included?
5. Who will actually build my site: you, a team member or someone outsourced?
6. Will you show me progress on a private link before launch?
7. How many rounds of changes are included?

About money and time

8. What are the payment stages, and what do I receive at each one?
9. What is the delivery date, and what happens if you or I cause a delay?
10. What yearly costs should I expect after launch?

About support

11. How long is the free warranty for fixing bugs after launch?
12. Do you offer a maintenance plan, and what does it include?

What a good written proposal looks like

After your first call, a serious developer sends a proposal. It does not need to be fancy. It should be one to three pages and answer the questions above without being asked. Look for a short summary of your business and your goal in the developer’s own words, so you know they listened. Look for a page list, the features included, a price with payment stages, a timeline with dates, and the yearly costs that come after launch. Look for a line that says what is not included, because honest developers know where scope creeps.

Compare two proposals side by side. The better proposal is not always longer. It is the one that leaves the fewest questions unanswered. If two developers quote the same price and one of them explains what you will receive at each stage while the other only lists a total, pick the one who explains. Clarity at the quote stage usually predicts clarity during the project.

Red flags: how to spot a bad web developer in Nigeria

After many rescue projects, I can usually smell trouble in the first call. Here are the warning signs, grouped so that you can remember them.

Money red flags

• Full payment upfront. An honest developer may ask for a deposit, but not everything.
• Payment only into a personal account with no receipt and no company name to match.
• A price far below every other quote. Someone is cutting a corner, and you will find out later which one.
• New charges that appear halfway for things that should have been included, like a contact form or mobile layout.

Communication red flags

• They take days to answer simple questions before you have even paid. It will only get worse.
• They never ask about your customers, your competitors or your goals.
• They promise big results such as “page one of Google in two weeks”. Nobody can promise that honestly.
• They avoid a call or a meeting and want everything on voice notes.

Technical red flags

• They will not show you a private preview link until the “final” version.
• They plan to use pirated themes or plugins, which often carry hidden malware.
• They cannot explain how backups and security will work.
• They talk only about design and never about speed, mobile or search.

Ngozi runs a beauty salon in Port Harcourt. A developer told her he would finish her website in five days for ₦80,000, if she paid all of it that evening. Something about the rush felt wrong, so she asked to see a live project and to speak to one of his clients. He gave excuses and went quiet. Two weeks later she found out he had taken money from three other salons in the same way. She lost nothing because she asked two questions. Her lesson to me was short: “If he cannot show me one happy client, I do not need to pay him to find out why.”

Freelancer, agency or a consultant-led team: who should you hire?

There is no universal winner. The right choice depends on your project, your budget and how much support you want. Here is how I see the trade-offs from someone who has worked in both worlds.

Solo freelancer

A freelancer is one person doing the design, coding and support. The strengths are lower prices, direct contact and speed. The weakness is what happens if that person falls sick, travels, or takes a full-time job abroad. Ask any freelancer what happens to your project if they cannot continue, and ask them to record all logins and files in a shared folder that you also own.

Agency

Agencies give you a team: strategist, designer, developer, project manager. Big agencies can handle bigger projects and give you a formal process. The trade-off is price and sometimes the feeling of being a small client at a big place. Ask who will actually do the work, and whether you can speak to that person.

Consultant-led team

This is the model I use. You speak directly with one senior person who is accountable for your project, and that person works with a small trusted team for design, writing and testing. You get the direct contact of a freelancer and the depth of an agency, with a smaller overhead than a large firm. It works well for small and medium businesses that want a proper result without a big-agency bill. If you want to know what I offer, see my professional business website service.

Contracts, payments and ownership: how to protect your money

You do not need a lawyer for every small website, but you do need something in writing. A short agreement that both sides sign keeps the relationship honest and gives you something to refer to when memories differ.

What a simple agreement must say

• The scope: pages, features, integrations and what is excluded.
• The price and the payment stages.
• The start date, the delivery date and what happens with delays.
• How many revision rounds are included.
• Who owns the domain, hosting, design files and code after final payment.
• The warranty period for bugs, and the terms of any support plan.

If a developer refuses to write any of this down, that is information you need before you pay.

Payment stages that protect both sides

A fair pattern for a small project is forty percent to start, thirty percent when you approve the design, and thirty percent when the site is tested and ready to go live. For larger projects, use more stages, one for each working milestone. Never release the final payment before you have the logins, tested the site on your phone and seen the domain in your name. For big amounts, you can also use an escrow arrangement, where a neutral party holds the money until the work is approved. You can read a plain definition of how escrow works if it is new to you.

How to pay safely

Pay by bank transfer to an account whose name matches the developer or their registered company, and keep the receipt. If the account name is a stranger’s name, ask why. Avoid cash for large amounts. Ask for an invoice or receipt for each payment. It is your proof, and it helps your bookkeeping if you claim the cost as a business expense.

Domain, hosting, code and content

Ownership is where most long-term disputes happen, so I want to be direct. Insist on the following:

• Domain name: registered in your name or your company’s name, using an email address you control.
• Hosting account: created under your details or shared with full admin access for you.
• Admin login: you must have full administrator access to your website.
• Design and code: agreed in writing. Many developers keep reusable tools and give you full rights to what was built for you.
• Images and fonts: licensed properly. Photos copied from Google can bring you a legal claim.

What to do if the project goes wrong

Even with good preparation, some projects stall. Do not panic, and do not send angry voice notes. Follow these steps in order:

1. Write down the problem. Send a calm written message that lists what was agreed, what has been delivered and what is missing, with dates.
2. Give a fair deadline. Ask for a specific date, for example seven days, to fix the problem or deliver the next stage.
3. Stop further payments until the agreed work for the current stage is delivered.
4. Secure what is yours. Ask for the domain transfer, the hosting login and a full backup of whatever exists so far.
5. Bring in a neutral person. A mutual friend, an association, or a second developer to review the work can settle many disputes without court.
6. Decide whether to continue or restart. Sometimes the cheapest choice is to finish with another developer using the existing design, and sometimes it is to start fresh.

This is exactly why the written agreement and the receipts matter. They turn “he said, she said” into facts. Most disputes end quietly when the developer sees that the client has records and a calm plan. If the amount is large and the developer refuses to respond, seek proper legal advice, and consider reporting fraud to the appropriate authorities, using your messages and receipts as evidence.

How to manage the project so it finishes on time

Even a great developer cannot finish a project when the client goes silent for two weeks. A website is a partnership, and your part matters as much as theirs. These habits keep projects moving.

Choose one decision-maker on your side

The most common delay I see is the committee problem. A church website has five committee members, each sending different changes at different times. A family company has three siblings who disagree about colours. Every extra opinion adds days. Choose one person who collects feedback, settles disagreements and gives one clear answer to the developer. Everyone else sends their comments to that person.

Send content early and in one place

Put logo, photos, text and prices in one shared folder and send the link. Do not send twenty separate WhatsApp messages over three weeks, because things get lost and the developer has to hunt for them. If you have not written the text yet, say so at the start, so the developer can plan for writing help or a later delivery date.

Review in rounds and give written feedback

Send your feedback as a numbered list, in one message, instead of ten separate voice notes at midnight. “1. Change the phone number on the contact page. 2. Make the logo bigger on mobile. 3. Add my Gwarinpa branch address.” A list is easier to complete, easier to track and easier to check afterwards.

Test on your own phone before you approve

Do not approve a design because it looks good on the developer’s laptop screen. Open the private preview on your own phone, on mobile data, while you are away from your desk. Try to find the price. Try to call. Try to submit the form. Ask a friend who has never seen the site to do the same. If either of you struggles, tell the developer before launch, not after.

After launch: support, training and maintenance

The day the site goes live is not the end of the relationship. It is the day real customers start using it, and real customers find problems that nobody thought about. This is the part of the deal many people forget to discuss.

A warranty period for bugs

A fair developer gives you a warranty period after launch, commonly fourteen to thirty days, to fix mistakes in what was agreed and delivered. A bug is when a feature that was promised does not work: the contact form does not send, or the menu breaks on iPhone. A new request, such as adding a new page you did not ask for earlier, is not a bug. Both sides should understand the difference from the start.

Training you can actually use

Ask for a training session, ideally recorded on video. You should learn how to change a price, replace a photo, add a new product or post, and download your enquiries. A ten-minute recording saves you many phone calls. Keep it in the same folder as your logins so that a new staff member can use it later.

A maintenance plan

Websites need updates for security, backups, small text changes and a regular look at whether everything still works. Some clients do this themselves. Most prefer to pay a small monthly amount to someone who does it properly. I explain what to expect and what it costs in my guide on why your website needs regular maintenance after launch.

What if your developer disappears?

Even good developers change jobs, relocate or get busy. Protect yourself from day one. Keep a document with the domain registrar, hosting provider, admin logins and email settings. Ask for a full backup of the site (files and database) at handover, and store it in your own cloud drive. Know one second person who can help, such as a technical friend or another developer, even if you never need them. If the domain and hosting are in your name and you have the backup, a missing developer becomes an inconvenience, not a disaster.

Does it matter if your web developer is in Abuja or Lagos?

Many clients ask me if they should only hire someone in their own city. My honest answer is that location matters less than it did five years ago, but it is not meaningless. Let me explain what really changes.

Meetings and site visits

If you want to meet in person, a developer in your city is convenient, especially at the start. In Lagos, that convenience can be limited by traffic. A meeting between Ikorodu and Victoria Island can eat half a day. In Abuja, distances between Maitama, Gwarinpa, Lugbe and the airport road can be long as well. For that reason, most of my meetings with clients are video calls, with one in-person visit at the start when it matters, for example to photograph a shop, a school or a hotel.

Does the price change?

A little. Agencies with expensive offices may charge more. Senior individuals often charge based on reputation rather than city. I explain the ranges in my full guide to website costs in Nigeria. Do not pick a developer because they are in your city and cheaper. Pick because they can show live work, reliable answers and written terms.

Working with someone in another city

It works well when communication is structured. Use a weekly call, a shared folder, a private preview link and written feedback. Payment by bank transfer is instant across cities. Many of my clients in Port Harcourt, Kano, Ibadan and Enugu have never sat in the same room with me. What matters is that each side knows what to do and by when.

Power, data and reliability

Ask a simple question: how do you work during power cuts? A serious developer has an inverter or generator plan, a backup internet line and maybe Starlink, so that your project does not stop because of a bad network week. It is a fair question for someone who will hold your website and your business logins.

If your project reaches a point where you need more than a website, such as a customer system, a school portal or a mobile app, you may need a technology partner and not just a web developer. My guide on how to choose a technology partner you can trust long term covers that next step.

Key takeaways

• Nobody needs a licence to call themselves a web developer in Nigeria, so your protection comes from checking, not from titles.
• Write the one job of your website, your page list and your budget range before you speak to any developer.
• Open live sites on your phone, on mobile data, and call at least two past clients.
• Ask about ownership first: domain, hosting, admin login, code and images must be in your name or fully handed over.
• Walk away from full upfront payment, unrealistic promises, missing previews and any developer who will not put terms in writing.
• Pay in stages tied to progress, to an account whose name matches the developer or their company, and keep every receipt.
• Choose one decision-maker, send content early, and test the preview on your own phone.
• Plan for after launch: warranty, training, backups and a maintenance plan, plus a copy of everything in your own hands.

Frequently asked questions

Your next step: talk to a developer you can check

If you are comparing developers, I am happy to be one of the people you check. Ask me for live examples, phone numbers of past clients and a written scope, and compare them fairly with everyone else. You can read about how I work on my professional business website service page, see real work on my projects page, or book a free consultation and bring your quotes along. If you prefer to chat, message me on WhatsApp from the site and I will reply the same day.