The Institutional Gap Is the Feature

In discussions of AI adoption in African institutional contexts, the most common framing is one of disadvantage. African organisations face constraints — resource limitations, connectivity gaps, infrastructure deficits, shallow technical talent pools — that put them behind their counterparts in better-resourced environments. AI will be harder to adopt here. The benefits will arrive later. The gap between Africa and more technologically advanced economies will, in the short term, widen.

I think this framing is wrong. Not because the constraints are not real — they are — but because it misreads what those constraints produce. The environments most likely to build genuinely AI-complete workflows are not the best-resourced environments, where the option of adding staff to manage a process is always available and often cheaper than redesigning it. They are the environments where the gap between what needs to be done and the resources available to do it with is so wide that the process redesign question cannot be avoided.

The institutional gap is not the barrier to AI transformation. For the specific category of AI transformation that matters — the one that eliminates processes rather than optimises them — the institutional gap is the forcing function.

The Resource Optionality Problem

There is a pattern in how well-resourced organisations respond to AI capability. When a new AI tool becomes available that could, in principle, eliminate the need for a category of human work, the organisation's default response is to treat it as an option rather than an imperative. The tool can be deployed to make the existing staff more productive. The existing process can be accelerated. The option of redesigning the process from the ground up exists but is not forced.

This optionality produces a particular kind of AI adoption: widespread deployment of AI as an improvement to existing processes, minimal deployment of AI as a replacement for existing processes. The cost of maintaining the existing process — the staff time, the management overhead, the error rate — is visible and manageable. The cost of redesigning it — the uncertainty, the implementation complexity, the change management required — is also visible and daunting. When the existing process is affordable, the default is to improve it, not redesign it.

In organisations where the existing process is not affordable — where the choice is not between "improve the process" and "redesign the process" but between "redesign the process" and "the process does not happen" — the optionality disappears. The process must either be designed to run without the resources that are not available, or it must not run. This is not a comfortable position to be in. But it is a position that forces the process-elimination question that optionality allows to be deferred indefinitely.

The Kenyan Cases

PBOMaster was built for an environment where the compliance lawyer is not a standard part of a community-based organisation's operating infrastructure. The choice was not between "organisations hire lawyers" and "organisations use PBOMaster." The choice was between "most organisations remain non-compliant" and "build the software that closes the gap." The gap was not a constraint on what could be built. It was the argument for building it.

AccessWASH was built for water utilities operating in counties where the data analyst, the GIS specialist, and the reporting officer are positions that exist on the organisational chart but are unfilled because the budget does not support them. The choice was not between "utilities hire analysts" and "utilities use AccessWASH." The choice was between "utilities continue operating in operational blindness" and "build the platform that provides visibility without requiring the staffing it would require in a better-resourced environment." The operational data infrastructure that well-resourced utilities have through staff was built, in the AccessWASH context, through software that works with the staff that is actually present.¹

M-Pesa is the most cited example of this pattern, and its lessons have been so thoroughly absorbed into development economics discourse that they risk being treated as historical rather than instructive.² The lesson of M-Pesa — that the constraint of an under-developed banking infrastructure produced, not a delayed version of the infrastructure that existed elsewhere, but a categorically different infrastructure that was better suited to the actual population — applies directly to the AI workflow argument. It is being underused.

What the AI Version of This Looks Like

The argument I am making is an extension of the leapfrog thesis, but with a specific mechanism: the institutional gap is the forcing function for AI-complete workflow design, because AI-complete workflows are built in environments where the alternative — staffing the workflow — is not financially viable.

In the compliance infrastructure domain, this is already visible. The PBO Act's requirements cannot be met by most Kenyan CBOs without either legal assistance or a system that replaces legal assistance for the compliance-checking tasks that are amenable to automation. PBOMaster was built because the gap demanded it. The product that was built is, arguably, better than the alternative it replaced: more systematic, more consistent, more accessible to rural organisations than a Nairobi legal market would ever be.

In the procurement domain, ProcureBee was built for companies operating in markets where the finance officer, the procurement manager, and the compliance reviewer are often the same person — or the same person wearing three hats. The agentic procurement workflow that eliminates the approval chain was not built as an improvement on an existing process that was working. It was built for contexts where the existing process was either absent or so burdensome that it was producing non-compliance rather than compliance.

In the knowledge infrastructure domain — the work AnswerTab is doing — the gap is between the volume of information that organisations need to process and the reading capacity available to process it. In organisations with large research teams and dedicated analysts, AI-assisted reading is an improvement on what already exists. In organisations with one programme officer covering three thematic areas and managing four active grants, AI-complete reading is not an improvement. It is the difference between the information being processed and not being processed.

The Implication for Where AI Development Happens

The global AI investment conversation is overwhelmingly focused on the highest-resource environments: Silicon Valley, London, Beijing. This is not surprising. The frontier AI models are being built where the frontier AI researchers are, which is where they can be paid the most, which is where the most capital is.

But the frontier of AI deployment — the edge of what it means to build software that genuinely replaces human processes rather than augmenting them — is not the same geography. It is the geography where the process-elimination question is forced rather than optional. Where the alternative to AI-complete workflows is not a less efficient human process. It is no process.

I am not making a prediction about where AI frontier research will be done. I am making a claim about where the most consequential AI deployments will come from — the ones that change institutional structures rather than making existing ones faster. Those deployments will come disproportionately from environments where the institutional gap makes the process-redesign question non-optional.

Nairobi is one of those environments. Not because of any technological advantage, but because of a specific combination: a sophisticated enough technical infrastructure to build and deploy serious software, and institutional gaps wide enough to make the process-elimination question unavoidable. The compliance officer that a Kenyan CBO cannot afford to hire is the argument for PBOMaster. The procurement team that a Kenyan startup cannot staff is the argument for ProcureBee. The reading capacity that a Kenyan programme officer doesn't have is the argument for AnswerTab.

The Broader Argument

I want to end with the claim I began with, stated precisely.

The most constrained environments are the most fertile ground for AI-complete workflow design because the process-elimination question is forced rather than optional. When staffing the process is not viable, the design question is not "how can AI help our people do this?" It is "how can we build a process that does not require our people to do this?"

The solutions produced in constrained environments are structurally simpler, because they are designed without the assumption of the supporting infrastructure that well-resourced environments take for granted. They work with the organisation that is actually present, not the one that should be present.

And the market is larger than the institutional AI conversation currently assumes. The population of organisations that need AI-complete workflows — that cannot afford the staffing alternative — is not a niche. It is the majority of organisations doing meaningful work in the world. The compliance infrastructure gap I have described in Kenya is the same gap, in different legal clothing, in every African country. The procurement workflow problem is the same problem for every under-resourced organisation that has a spending policy and no mechanism to enforce it except human attention.

The companies that understand this — that the institutional gap is a design brief, not a constraint — will build the most consequential AI products of the next decade. They will build them in Nairobi, in Lagos, in Kampala, in Accra. Not because those cities have advantages over San Francisco in AI research. Because they have a specific kind of problem that San Francisco does not: the alternative to building software that works without the staff is having no software that works.

That is not a disadvantage. That is a feature.