Every era of technology has a default unit of ambition. For the last fifteen years, that unit has been the app: a discrete product solving a discrete problem for a discrete user. The app era produced extraordinary things. It is also, I believe, the wrong unit of ambition for the work that matters most in Africa right now: the modernization of institutions. Institutions do not have discrete problems. They have interconnected operations. And interconnected operations call for a different kind of building altogether: infrastructure.
The difference, precisely
The words get used loosely, so let me be exact. An app is something an institution uses: adopted by choice, for a task, replaceable on a whim. Infrastructure is something an institution runs on, woven into daily execution, carrying mission-critical activity, costly to imagine living without. The test is behavioral, not technical: when the system pauses, does work continue around it, or does work stop? Apps get worked around. Infrastructure gets waited for.
This difference cascades into everything about how you build:
- Apps optimize for engagement; infrastructure optimizes for dependence. An app wants your attention. Infrastructure wants your weight, the full load of operations placed confidently upon it.
- Apps solve functions; infrastructure connects them. The hardest institutional costs live between functions: between collection and reconciliation, between record and report, between decision and communication. Apps digitize the rooms. Infrastructure builds the corridors.
- Apps tolerate failure; infrastructure cannot. An app that fails loses a session. Infrastructure that fails halts an institution. Reliability is not a feature of infrastructure; it is the product.
- Apps are chosen by users; infrastructure is trusted by institutions. And institutional trust is earned only one way, in the daily mechanics of execution, over time, without exception.
Why Africa’s moment demands the harder kind
Africa’s coming decades are institutional decades. The continent’s population will grow fastest where institutions (schools, health systems, cooperatives, civic administration) are already most strained. Those institutions largely run on what I have called fragmented manual systems: operations stitched together by paper, spreadsheets, and individual diligence. You cannot app your way out of that. A thousand isolated tools laid over fragmented operations produce digitized fragmentation: a faster broken process, multiplied.
What the moment requires is an operational infrastructure layer: coordinated ecosystems in which finance, administration, communication, reporting, and accountability function as one system. This is slower work than shipping apps. It demands institutional fluency (how a bursar actually closes a term, why a proprietor distrusts a report, where a payment actually gets stuck) as much as it demands engineering. It is judged not by downloads but by what institutions entrust to it.
What this looks like in practice
My own proving ground is education. School Vault is built as an institutional operating system for modern schools: not a school app or an ERP, but the operational layer a school runs on. The validation has come in the form institutions respect most: over ₦960 million in institutional financial activity carried, which I read strictly as a measure of operational trust. Schools have placed their continuity on this infrastructure. That is the standard the category must be held to.
And the category is bigger than education. The same architecture, with coordination as structure, visibility as default, and trust as a system property, extends to cooperative finance, health administration, and civic coordination across Nigeria and the continent. Wherever an institution’s operations are fragmented, the same infrastructure thesis applies.
A closing word to fellow builders
If you are building for African institutions, the app era’s instincts will mislead you. Do not ask what feature to ship; ask what operations to carry. Do not chase engagement; earn dependence. Do not count users; weigh what institutions have trusted you with. The market will be slower to applaud and far slower to leave, because markets ultimately place the highest value on builders who do not merely launch products, but build the systems institutions eventually depend on.
That is the work I have chosen, from Lagos, for the long horizon: infrastructure, not apps. The institutions of emerging Africa deserve nothing less than ground solid enough to build their futures on.