Why Procurement Reform Matters for Digital Government
Government technology procurement is where digital transformation dreams most frequently die. A government develops an ambitious digital strategy, secures the budget, and then routes the investment through procurement processes designed for physical infrastructure — where the lowest price wins, where technical evaluation is superficial, where contract management is weak, and where vendor accountability is minimal. The result is predictable: expensive systems that do not meet user needs, cannot be integrated with other government platforms, and cannot be maintained without continued expensive vendor dependency.
Procurement reform is not glamorous. It does not make headlines the way digital strategy announcements do. But it is the single most impactful governance change that African governments can make to improve the return on their digital investments. The case for why digital transformation fails when institutions are ignored — documented in the analysis of digital transformation failures — almost always leads back to procurement decisions made without adequate technical rigour.
What Is Wrong With Current Government Technology Procurement
Price-Led Evaluation
When the primary evaluation criterion is price, governments consistently select the cheapest proposal rather than the most capable one. In technology procurement, the cheapest solution is frequently the one with the least capability, the most vendor lock-in, and the most hidden costs in customisation, maintenance, and integration. Evaluating technology on price alone is the equivalent of procuring a hospital by selecting the cheapest builder without checking whether they can build hospitals.
Inadequate Technical Specification
Government procurement specifications for technology systems are often written by non-technical officials who do not know what to require. Requirements like “the system should be easy to use” or “the platform should be scalable” provide no basis for objective evaluation. Without precise technical specifications — covering performance, security, interoperability, data standards, and accessibility — procurement processes cannot distinguish capable systems from incapable ones.
No Knowledge Transfer Requirements
When governments procure technology without requiring knowledge transfer, they create permanent vendor dependency: only the original vendor can maintain, modify, or extend the system, and the government pays accordingly forever. As discussed in the broader context of building genuinely transformative digital government, internal capacity development must be embedded in procurement from the outset.
What Procurement Reform Looks Like
Outcome-Based Contracting
Rather than specifying the technology to be purchased, outcome-based contracts specify the results to be achieved: “95% of applications processed within 48 hours,” “citizen satisfaction score above 4.2 out of 5,” “system availability of 99.5%.” Vendors propose how they will achieve the specified outcomes, and payment is linked to outcome delivery — not to system deployment.
Open Standards and Interoperability Requirements
Every government technology procurement should require compliance with open standards and documented interoperability APIs. This prevents lock-in, enables integration with other government systems, and protects government’s ability to change vendors without losing data or rebuilding integrations from scratch.
Mandatory Penetration Testing and Security Requirements
Security requirements — encryption standards, access control specifications, audit logging, penetration testing before deployment — must be written into every technology contract for systems that process citizen data or government financial information. Vendors who cannot demonstrate compliance should be disqualified at evaluation stage, not discovered to be non-compliant after deployment.
Key Takeaways
- Procurement is where most African government technology failures originate — reforming it is the highest-leverage governance change available.
- Price-led evaluation consistently selects incapable vendors and produces systems that fail citizen expectations.
- Technical specifications must be precise and measurable — vague requirements provide no basis for objective evaluation.
- Knowledge transfer obligations in every contract protect government’s ability to manage, modify, and eventually replace systems independently.
- Outcome-based contracting aligns vendor incentives with citizen service improvement rather than with system deployment.
Frequently Asked Questions
How can Nigerian state governments build procurement capacity for technology projects?
By creating or designating a technical evaluation function within state government — staffed by professionals with technology procurement experience — that reviews all significant technology procurements before contract award. Partnering with federal agencies or development organisations for training of procurement officials in technology evaluation is a practical starting point.
What is vendor lock-in and why does it matter for African governments?
Vendor lock-in occurs when a government becomes dependent on a single vendor for a system that cannot be maintained, modified, or replaced without the original vendor’s involvement. This creates permanent cost and vulnerability: the vendor controls pricing, the government cannot audit the system fully, and any attempt to change vendor requires rebuilding from scratch. Open standards requirements in procurement contracts are the primary protection.
About the Author
Suleiman Isah is the Director General of NSITDEA and an advocate for rigorous, outcome-focused technology procurement in Nigerian public institutions. Read more about his approach.


