Why DNET
Five reasons clients keep the number.
We have been here since 1997 — and we answer the phone in year eight
We have delivered connectivity and voice services to the same international foundation continuously since 2014, and our institutional work reaches back to 1999. In a market where suppliers appear for a contract and vanish before the warranty expires, continuity is not a soft benefit. It is the difference between a system that still works in 2031 and a system nobody can service.
We run the network, not just sell the box
DNET held a Nigerian Communications Commission internet service provider licence, operated its own autonomous system number and IPv4 allocation through AfriNIC, peered via BGP, and contracted capacity directly from submarine cable and terrestrial fibre carriers — and still delivers enterprise internet and voice under a live contract today. Very few equipment suppliers can diagnose a routing problem. We built routing tables for a living.
National delivery is a routine, not a mobilisation
Supporting thirty-eight sites across all thirty-six states and the FCT on a scheduled monthly cycle means we already hold the logistics, the technician coverage and the spares discipline that multi-site contracts demand. A client in Maiduguri gets the same service definition as a client in Wuse.
One accountable party from specification to support
We specify, source, deliver, install, test, commission, train and maintain. When something fails, there is no argument about whether it is the hardware vendor, the cabling contractor or the software house. It is us.
Institutional clients have audited us and stayed
United Nations agencies, international development organisations and federal institutions do not award or renew casually. They run procurement processes, service level agreements and performance reviews. We have been through those and come out the other side, repeatedly.
The test we set ourselves
Any capability we publish is one we will put in a contract, price at a fixed figure, and accept a service level against. We do not list capabilities we would not sign for.
How we deliver
Seven stages, one accountable party.
The same method whether the engagement is twenty tablets or a national service contract — because the discipline that makes a large programme work is the discipline that makes a small order arrive on the promised day.
Understand
We start from the requirement as the client states it, in their terms, and ask the questions that surface what is missing — site conditions, existing infrastructure, power, who will actually use it, what happens when it breaks. Most specification failures are discovered here, or discovered expensively later.
Specify
We produce a written specification and a fixed commercial proposal: what is included, what is excluded, delivery timescale, and the acceptance criteria the work will be judged against. Nothing proceeds on a verbal understanding.
Source
Procurement through authorised channels, with manufacturer authorisation documentation where required, and a second supply route identified before a delivery date is committed.
Deploy
Site preparation, installation and configuration to the agreed build standard, by our own engineers, with progress visible to the client throughout.
Prove
System testing against the specification, commissioning, and a documented acceptance record signed at each site. Work is not complete because it is installed; it is complete because it has been demonstrated to work.
Hand over
As-built documentation, configuration records, warranty registration and user orientation — so the organisation owns the system rather than renting our memory of it.
Sustain
Maintenance under a service level agreement, with defined fault categories, response and restoration targets, escalation levels and periodic reporting.
Service framework
The terms we contract to.
Drawn from service level agreements DNET already operates with institutional clients. Offered as a starting position and tuned to each engagement.
| Fault category | Impact | Diagnostic time | Mean time to repair |
|---|---|---|---|
| Emergency | Service unusable — total loss of connectivity or function | 30 minutes | 2 hours |
| Major | Service significantly degraded — high impact or partial loss | 30 minutes | 6 hours |
| Minor | Minor degradation, non-service-affecting issues, technical queries and change requests | 60 minutes | 36 hours |
What comes with it
- Guaranteed circuit availability against a stated percentage, measured monthly and excluding planned outages
- A published planned-outage window with five working days' notice of scheduled maintenance
- A named escalation path with defined levels and response commitments at each
- Proactive monitoring and periodic performance reporting
- Defined incident classification, agreed between the parties rather than asserted afterwards
Why this matters in a bid
Any supplier can promise support. A supplier that can hand you a fault-category table, an availability guarantee and an escalation matrix on day one is a supplier that has been held to them before — and has the field capacity to meet them across the country rather than in one city.
Hold us to it.
Ask for the service terms before you award. We would rather negotiate them at bid stage than discover a mismatch in month three.