A buyer should know what happens after they pick up the phone.
Most IT suppliers describe their process in a sentence and a diagram. That is not enough to plan around. A finance team needs to know when the price is fixed. An auditor needs to know which documents will exist at the end.
So this is how an IT engagement with Digitplus works, stage by stage. It is the same six steps on every engagement, set out on our approach page. Here they are in practical terms, with what you receive at each one and what we need from you.
Stage 1: How the IT engagement starts
The first call is a conversation, and it costs nothing. We ask what you are trying to fix or build, not which products you want. The two are often different.
Then the assessment. We work through your operations, your constraints, your sites and your budget. For a hardware order that might be a short list of questions about who uses each machine and what they run. For an infrastructure job it means a site survey, because cabling, power and rack space cannot be specified from a phone call. We document the existing conditions before we design anything.
Nothing is specified until we know what success looks like for you.
What we need from you: access to the people who use the systems, not only the person signing the order. And honesty about the budget. A specification built for an imaginary budget gets rebuilt later.
What you receive: a shared understanding of the requirement, which becomes the first section of the proposal.
Stage 2: A written specification and quote
This is the stage that decides whether the rest goes well.
We design a right-sized solution and put it in a line-itemised proposal: scope, specifications, timelines and costs. Every hardware line names the exact model. Warranty terms and lead times are stated. Where there is a real choice, we set out the options with the trade-off attached, and if the cheaper option meets the requirement, we say so.
Two things about the price are worth knowing in advance.
It is dated. Most enterprise hardware is imported and priced in US dollars, so the naira figure tracks the exchange rate. Each quote states the rate it was priced on. Hardware lines hold for 7 calendar days, services and labour for 30. If the rate moves before an order is placed, the exposed lines are rechecked and you are told before anything is ordered.
It is complete. Delivery, installation and configuration either appear as lines on the quote or are listed as exclusions. Nothing is left implied. Our guide to reading an IT quote explains what to look for in any supplier's quote, ours included.
For public-sector and corporate buyers with formal purchasing, this is where the paperwork starts: quotation, then proforma invoice, ready for your approval chain. We fit your process rather than asking you to change it. The detail of that workflow is in our piece on how the LPO process works for public-sector IT.
Stage 3: Procurement and logistics
On approval, we place the order. For LPO-based buyers, we fulfil against the LPO. Lead times are confirmed in writing at this point, because they depend on stock and shipping that only exist once an order is real.
We do not supply grey-market stock. Equipment comes with manufacturer warranties, and every step from order to delivery is recorded, so the file holds up to internal and external audit.
For multi-site programmes, orders are consolidated and delivery is staged by location. One order and one invoice trail, many sites. That is the core of our IT procurement work.
Stage 4: Deployment and installation
Delivery is the middle of the job, not the end of it.
We install and configure to agreed standards, and plan the work around your operating hours. That often means out-of-hours work or a phased rollout, so a live office or branch keeps working while the change happens. Machines are configured consistently, so seven workstations become one image and one support profile rather than seven separate builds.
Where the work happens changes the logistics, so it is planned differently in each city we cover.
Abuja is our headquarters. Equipment is received and configured at our premises before it goes to your site, so what arrives is already imaged. We deliver and install across the FCT, including the satellite towns.
Lagos deployments are scheduled around how the city moves. Kit is staged and configured centrally, each site's readiness is confirmed before anyone travels, and installs are sequenced around realistic time windows.
Port Harcourt and the wider South-South work often involves industrial sites with HSE requirements and restricted access. Those are planned up front rather than discovered on the day. Spares are planned in, and configurations are documented so on-site staff can keep things running between visits.
The method is the same in all three. The constraints are not. For rollouts across several locations, our pre-deployment site survey framework covers what to check before any equipment leaves the warehouse.
Stage 5: Testing and handover
The job ends at sign-off, and sign-off happens when everything works. Not when the boxes are unpacked.
The acceptance criteria are agreed in advance, before installation starts. We test against them. For structured cabling that means every run is tested and labelled at both ends. For a hardware rollout it means each machine confirmed working at its desk with the software it needs.
Then the handover. You receive the documentation, and it stays with you:
- Invoices and delivery notes, matched to the order.
- Warranty records, registered in your organisation's name.
- An asset register: every item, model, serial number, location and warranty expiry.
- As-built records for infrastructure work: labelled layouts and test reports.
We also train the people who will use the systems. Practical handover, at their desks, so the first day they depend on a new system is not the first day they see it.
The asset register keeps paying off long after handover. It turns the next budget cycle into a calculation and the next audit into a short conversation. It also means that if you move support elsewhere, nobody starts from nothing.
Stage 6: Ongoing support
After go-live, support can run one of two ways.
The first is to stop at handover. The equipment is under manufacturer warranty, your own team runs it, and the documentation lets them do that. For a small, stable estate that is a sound arrangement, and we will say so.
The second is managed services. We monitor servers and networks, handle day-to-day issues remotely where we can, and send an engineer where we cannot. Response and resolution targets are agreed in writing, by issue priority, with the scope spelled out and reported against. What an agreement like that should contain is covered in our guide to what an IT SLA should cover.
If you already have support that works, we will tell you that rather than propose a new one.
Frequently asked questions
Does the first consultation cost anything?
No. The first call is a conversation about what you need. A paid engagement starts only when you approve a written proposal.
Do we have to use Digitplus for delivery if we start with advice?
No. Advisory is a standalone service. You can ask us to deliver afterwards, because we will already understand the plan, but it is never a condition.
Can you work within our LPO and approval process?
Yes. We work to formal purchasing workflows: quotation, proforma invoice, LPO fulfilment and itemised delivery notes. We adapt to your approval chain.
Which locations do you cover?
We are headquartered in Abuja, with delivery in Lagos and Port Harcourt. Remote support runs nationwide. On-site work in other locations is agreed per engagement.
If you have a requirement taking shape, book the first call. Bring the problem rather than the product list, and we will start with the assessment.
