Government & Public Sector

Almost every state government we work with is under the same arithmetic. Federation Account allocations are volatile, the wage bill and pension liability are not, and the gap has to be closed by internally generated revenue. Yet the collection machinery is usually fragmented: land use charge sits in one ministry, motor licensing in another, market levies with local government, and none of them reconcile. Demand notices are printed and hand-delivered, receipts are manual, and a meaningful share of what citizens actually pay never reaches the Treasury Single Account. The revenue is not missing because citizens refuse to pay. It is missing because nobody can see it.

The second pressure is data isolation between ministries, departments and agencies. The Head of Service cannot reconcile the nominal roll against the payroll; the Ministry of Finance cannot tell which agency has already procured the same equipment; the Bureau of Public Procurement cannot see contract performance history when evaluating a bidder. Each MDA has bought its own system, often from a different vendor, with no integration budget and no common identifier for a citizen, a staff member or a vendor. Ghost workers, duplicate payments and stalled contracts all live in the space between those systems.

The third pressure is procedural, and it is where most vendors come unstuck. A public IT project must pass through the Public Procurement Act 2007 and its due-process regime, obtain NITDA clearance where the threshold applies, use a registered indigenous provider, satisfy the Nigeria Data Protection Act 2023 for citizen data, and produce an audit trail the state Auditor-General will accept years later. Technology that cannot produce that evidence is a liability regardless of how well it performs. We build the evidence pack alongside the system.