We should say upfront that we have a conflict of interest here. Easy World Techs is a technology vendor. When we write about how to vet one, we are, in effect, telling you how to vet us. We've decided that's fine, because a vendor who is nervous about being vetted is the first red flag on any list, and you should be suspicious of anyone who'd rather you skipped this article.
Here is the uncomfortable truth about how most Nigerian businesses choose a tech vendor: the process is mostly theatre. Three quotes, a demo, a portfolio page, a pleasant phone call, and a decision made on price and gut feeling. Look at what each of those has in common. The vendor controls all of it. The demo is rehearsed. The portfolio is curated. The quote is written to win the job. You are being shown the best hour of the relationship and asked to predict the next twelve months from it.
Real evaluation means going looking for the things the vendor does not control. That is harder, and it makes for a slightly awkward few weeks before you sign. It is still far cheaper than the alternative, which is finding out in month five.
The demo is the least informative hour you will spend
Demos exist to remove doubt. Your job is to put it back.
Instead of asking what they have built, ask about the project that went wrong. Not a polite version of it, the real one: a deadline missed, a client who left unhappy, a system that failed after launch. Then listen to how they tell it. A vendor who takes ownership ("we underestimated the integration work and we should have said so earlier") is showing you how they will behave when your project hits trouble. A vendor who blames the client, the network, the NEPA light, or "a freelancer we used" is showing you the same thing, just in the opposite direction.
And if they say nothing has ever gone wrong? That is our inference, not a statistic, but we read it one of two ways: they haven't done much, or they aren't being straight with you. Neither is what you are paying for.
Find out who actually does the work
The person who sells you the project is very often not the person who builds it. That is not automatically a problem. Agencies have sales people and builders, and that division of labour exists for a reason. The problem starts when you cannot tell where the line is.
Ask two plain questions. Who will be working on this day to day? And will any of the work be handed to someone outside the company? Subcontracting is normal in this industry, and some of it is perfectly good practice. But you are entitled to know, because the person doing the work is the person who will have access to your accounts, your customer data, and your code. Ask to speak to them once, even for ten minutes. You will learn more from how they ask about your business than from anything in the proposal.
Check that they exist the way they say they exist
This takes five minutes and most people skip it. If the vendor presents itself as a company, take the RC number and run it through the Corporate Affairs Commission's public search. Confirm that the registered name matches the name on the quote and on the contract you will be handed, and that the entity shows as active. The search is free, and we've seen it described as available to anyone without an account. Portal addresses at the CAC have changed in recent years, so use the link from the CAC's own website rather than one sent to you by a stranger.
Be clear on what this does and doesn't prove. Registration tells you a legal entity exists. It says nothing about whether that entity is competent, honest, or still operating in practice. Treat it as a floor. If the vendor can't give you an RC number, or the name on the register doesn't match, you've learned something important cheaply.
A registered company is also not automatically better than a good freelancer. Plenty of excellent work in this country is done by individuals. The point isn't to rule anyone out. It's to know who you are actually contracting with, because that decides who you can hold to account if things go wrong.
References: ask for the old client, then ask the second question
Every vendor has references, and every reference has been chosen. So make two small changes. Ask for a client from at least a year ago, not the one they finished last month. And when you call them, do not ask whether they were happy. People are polite. Ask what happened the first time something broke after launch, and how long it took the vendor to respond.
That one question tells you whether the relationship survives past the invoice. Many vendors are excellent while a project is live and the final payment is outstanding. The ones worth hiring are still picking up the phone eight months later.
Then do something no one does: open the live work. Pull up two or three sites or apps they have built, on your phone, on mobile data, not office Wi-Fi. See how long they take to load. Fill in a contact form. Try to break it. A portfolio screenshot has been polished. The live product hasn't.
On the last day of the project, can you log into everything without calling anyone?
What you will own on the last day
This is the part that causes the most pain later, and almost nobody asks about it at the start.
Before you sign, find out who owns what. The source code. The domain name. The hosting account. Any paid theme, plugin, or third-party licence the build depends on. The simplest test is practical rather than legal: at the end of the project, can you log into every one of those accounts with your own email address, without anybody's permission? If the domain is registered in the vendor's name, or the hosting sits on the vendor's personal account, you have rented a website, not bought one. That may be fine if you know about it. It is a nasty surprise if you don't.
On the legal side, here is what we can say with reasonable confidence, and where we have to stop. Computer programs are treated as literary works under Nigeria's Copyright Act 2022, and the commentary we read says an assignment of copyright has no effect unless it is in writing. What we could not settle is the default position when a business commissions software and nothing is written down. The sources we read disagree: one says the commissioning party is presumed to own the work unless the parties agree otherwise, another says that without an assignment the commissioner may hold little more than a licence to use it for the purpose it was commissioned. We are not lawyers, and we are not going to pretend that disagreement away. The practical lesson is that you shouldn't rely on the default either way. Put the ownership terms in writing, and have a lawyer read that clause before you sign.
Where your customers' data goes
If the system being built will touch personal data (customer names, phone numbers, payment details, student records), then your vendor is almost certainly handling that data on your behalf. Whether that makes them a data processor in the legal sense depends on the facts of each project, so treat that as our reading rather than a ruling. The Nigeria Data Protection Act 2023 speaks to this relationship directly. Section 29 says a controller that engages a processor must ensure the processor meets the Act's obligations, and it says those measures include a written agreement between the two.
Practically, that means a few questions before you sign, not after something leaks:
- Where will the data be hosted, and who at the vendor can access it?
- If there is a breach, how quickly will they tell you, and in what form?
- Will they use other companies (hosting providers, SMS gateways, analytics tools) that also touch the data, and will they tell you which ones?
- What happens to your data if the relationship ends?
The Nigeria Data Protection Commission has also issued guidance on registration for controllers and processors classed as being of major importance. Whether you or your vendor fall into that class is a question for a data protection professional, and we would rather say that plainly than guess.
How they behave when you push back
Everything so far is research. This last test is observation, and it's the one we'd weight most heavily.
Somewhere in the conversation, push. Tell them the timeline looks short. Ask what would make this project take twice as long. Ask what is not included in the price. Then watch. A good vendor will answer with specifics, even if the specifics are inconvenient: the content you haven't supplied yet, the third-party integration that is out of their hands, the feature that sounds small and is not. A vendor who says yes to everything is not being agreeable. They are deferring the argument until you've paid.
The same goes for money. Be wary of a payment structure where nearly everything is due before anything is delivered. Our view, and it is an opinion rather than a rule, is that payment tied to milestones keeps both sides honest, because it gives each of you a reason to finish. And ask for the scope in writing, including a short list of what is explicitly out of it. Most disputes we hear about in this industry, and that is anecdote, not data, come down to two people who each believed something was included.
If you only have one afternoon
Do three things. Speak to the person who will actually build it. Call one reference from over a year ago and ask what happened when something broke. And read the clause on ownership, with a lawyer if you can.
None of that is sophisticated. That is rather the point. Vendor choices usually go wrong not because the buyer missed something technical, but because nobody asked the dull, awkward questions while the relationship was still friendly. We'd rather you asked us all of these. A vendor worth working with will be glad you did.