"Customer-first" is a claim nobody can check from a website.
Most IT companies in Nigeria say it. The phrase costs nothing to print and it tells a buyer nothing about what will happen when the supplier has a choice between your interest and their margin.
So drop the phrase and look for the behaviour. What customer-first means in an IT company is a short list of things a client can see, in writing, before and after money moves. Here are five. Use them on any supplier. We use them on ourselves.
1. They recommend the cheaper option when it is enough
This is the most expensive behaviour for a supplier, which is why it is the most reliable signal.
A common request is a 10-gigabit network for a small office. The reasoning is sound on its face: faster is better, and the price gap looks small on a single switch. But follow the cost through. Most business desktops still ship with 1-gigabit Ethernet, and many newer motherboards with 2.5-gigabit. Very few come with 10. Going to 10 means an add-in network card in every machine that needs it, and 10-gigabit switch ports to match. Then the cabling: Cat6 carries 10-gigabit only on shorter runs, roughly up to 55 metres. Beyond that you are looking at Cat6A.
For a team moving office documents and the occasional large file, 2.5-gigabit is honestly fast. It is two and a half times a standard gigabit desk, and it runs over the Cat5e or Cat6 already in the wall at full 100-metre lengths. If 10-gigabit is a hard requirement, because you edit video off a shared server all day, then buy it. If it is not, the supplier who says so has just made less money on your order.
Power is the other place this shows up. A request for a 10kVA inverter is common. Whether you need one depends on the load already in the office, and that is something you measure. Add up the running watts of what will actually sit on the inverter, allow for start-up peaks and some growth, and the answer for a typical small office is often well under 10kVA. Our piece on power protection and UPS planning walks through that sizing.
The check: ask a supplier what you could remove from their proposal and still meet the requirement. A supplier working for you has an answer.
2. They say no to work that will not solve the problem
The second behaviour is harder than the first. The client wants to buy something, the supplier could sell it, and the right answer is no.
A typical version: an office complains that the internet is slow and asks for new access points. If the problem is a 20Mbps link shared by forty people, new access points will not change it. The bottleneck is upstream of the Wi-Fi. The honest answer is "No, new access points will not fix this. The link is the limit." Then the reason, then what will fix it.
Another: a request for a server for a ten-person team that needs shared files and a backup. A full server is one way to do that. A network-attached storage device is another, at a fraction of the cost and the power draw, and with far less to maintain. If shared files and backup are the whole requirement, the second option is usually the right one.
The check: ask a supplier about a time they talked a client out of a purchase. A supplier who has never done it either has not been asked the right questions, or has not been listening to the answers.
3. The specification and the handover are in writing
Verbal assurances are free to give and free to forget. A written specification is not.
Before any order, a client should hold a document that states exactly what will be delivered: exact models, quantities, warranty terms, lead times and what is excluded. Our guide to reading an IT quote covers what that document should contain line by line.
After delivery, the client should hold a second document: what was installed, where it sits, the serial numbers, warranty expiry dates and how it was configured. For a network or cabling job that means labelled records and test results. For a hardware rollout it means an asset register.
This is how we work at every step. Requirements and budget are confirmed before a quote is raised. Specifications and warranty terms are confirmed in writing before the order. Testing runs against acceptance criteria agreed in advance, and sign-off happens when those criteria are met. The documentation goes to the client, not into our filing cabinet.
Why does this count as customer-first? Because the written handover is what lets you leave. With an asset register and configuration records, a client can take support to another provider, or in-house, without starting from nothing. A supplier who keeps that knowledge in their own heads has made themselves hard to replace, and that is a choice made for their benefit.
The check: ask to see a sample handover pack before you sign.
4. One party is accountable, end to end
In a multi-supplier project, a technical fault often turns into a boundary dispute. The hardware vendor blames the cabling contractor. The cabling contractor blames the ISP. The client spends a fortnight relaying messages.
Customer-first, here, is structural: one party owns the outcome across planning, procurement, deployment and support. When something fails, there is one place the question goes and one place the responsibility stops. That is how our engagements are structured: one partner from the first assessment to ongoing support, with no hand-off between firms for the client to manage.
This has a cost and it is worth naming. Single accountability works only if the one party is competent across every stage it owns. If a supplier claims end-to-end responsibility but subcontracts the parts it cannot do, you are back to the boundary dispute, with an extra layer in between.
The check: ask who you call when the fault could be the hardware, the network or the software. If the answer is three different numbers, there is no single accountable party.
5. They tell you what they do not know
The last behaviour is the least common and the most useful.
An honest supplier is precise about the edge of its own knowledge. A typical case: a client asks for servers to run AI models. The hardware questions have clear answers. Power per GPU, power supply sizing, cooling, rack space. But which models will run and how the data will flow are questions for the people building the software. A supplier who answers those with confidence they do not have is guessing with your money.
The right sentence is "We do not know the size of the models you will run, so we sized the power and cooling for two GPUs and left a slot for a third." That names the gap and the assumption made to cover it. You can check it, and correct it.
The same applies to price. Where a figure depends on the exchange rate on the day of purchase, the honest answer is a dated quote with a short validity window. A fixed naira number months in advance is a guess presented as a promise.
The check: ask a supplier what assumptions their proposal rests on. Good proposals list them.
What customer-first means when you are choosing a supplier
Use the five checks alongside the wider evaluation in our guide to evaluating IT vendors in Nigeria, which covers references and financial standing. If you are earlier than that and still working out what to buy, a vendor-neutral technology advisory engagement is the place to start. It is a standalone service. Using us for delivery afterwards is never a condition.
Frequently asked questions
How can I tell if an IT supplier really puts customers first?
Look for behaviour rather than claims. Does the proposal include a cheaper option where one would do? Is the specification written down with exact models and warranty terms? Is there one accountable party? Does the supplier list the assumptions behind the proposal?
Should I be suspicious of a supplier who recommends a cheaper option?
No. It costs the supplier margin, which is why it is a strong signal. Check the reasoning, though. A cheaper option should come with the requirement it meets and the point at which it would stop being enough.
Why does written handover documentation matter so much?
It makes you independent of the supplier. An asset register, configuration records and test results let any competent provider, including your own team, support what was installed. Without them, the knowledge sits with whoever did the work.
What should a supplier do when it does not know the answer?
Say so, then state the assumption it is making instead. "We do not know X, so we sized for Y" is a sentence you can check and correct. Confident answers outside a supplier's expertise are the ones that cost money later.
If you have a proposal on your desk and want a second view on what could come out of it, send it to us. We will tell you which lines are doing work and which are not.
