Programme design
Scopes that survive due process, staged deliverables, and a paper trail that matches how public institutions account for work.
Services
Public Sector Delivery
Public-sector ICT is not private-sector ICT with a coat of arms. We work inside circulars, due process, records obligations, and the reality of multi-stakeholder ownership — without lowering the engineering bar.
The problem
What we usually walk into.
Vendors arrive with private-sector playbooks, miss the political and administrative grain, and leave behind a system nobody owns. The next administration inherits a login screen and a support contract that has expired.
Approach
When the buyer is government.
We plan for handover, capability transfer, and evidence from the first week. Architecture is written so a new Perm Sec can understand it. Security is written so internal audit can test it.
Stakeholder architecture
The ICT department, the user department, the accountant-general’s rules, and the political office — designed for, not surprised by.
Sovereign considerations
Data residency, NDPR, records, and the preference for systems the Nigerian state can still run if a vendor leaves.
Capability building
We leave operators, not only software. Training, runbooks, and paired delivery with the in-house team.
Outcomes we design for
- A programme a ministry can defend in writing
- Systems that survive a change of leadership
- In-house staff who can operate day two
- Evidence packs ready for audit and inquiry
Who this is for
- Federal MDAs and extra-ministerial agencies
- State governments and Boards
- Local Government and development-partner programmes
Other practices
Digital Transformation
A target operating model and system landscape that startups and organisations can actually run.
Workflow Automation
Intelligent workflows and multi-agent systems that move real work — with humans still in command.
Cybersecurity
Identity, architecture, detection, and response designed so compromise is expensive for the adversary — not for you.
Next step
Bring us the hard programme.
If the work needs architecture, security, and a team that will still be there at go-live, we should talk. Discovery conversations are with a senior architect — not a queue.