Africa has a deployment problem, not an innovation problem.
Governments have the strategies. Africa has the developers. What is missing is someone whose job is to put a working system inside a ministry, a border post or a clinic. That is our job. We find the point where a system is stuck, bring in African technologists to fix it, prove it works, and hand it over to the people with the budget and the mandate to scale it.
A ministry writes the strategy. A donor funds the study. A consultancy delivers the report. Nobody's job is to build the system.
That is not a failure of government. Ministries can set strategy, but they cannot staff a build team. Consultancies deliver reports. Development partners pay for studies, and rarely for the slow work of making a system run inside a real institution. Accelerators find good startups, and those founders then have no way into the national problems where their skills would count most.
Each of them does their own job well. The job in the middle belongs to nobody, so the constraints stay exactly where they are. ITC exists to hold that job, and to show, one deployment at a time, what changes when somebody does.
Every mission runs four phases.
We run every Deploy Africa mission the same way, and we take a mission on only if what it unlocks afterwards is worth at least ten times what the deployment cost.
Identify the bottleneck
We find a specific technical constraint and an institution willing to co-sign a Deployment Brief before any work starts.
Output: A Deployment Brief, co-signed by ITC and the institutional partner.
Brief the builders
We publish a precise challenge brief. A hackathon then picks the team that is most ready to deploy, not the one with the best pitch, and we commission that team.
Output: A commissioned deployment team.
Deploy
The team works inside the institution and builds a production system. Funding is released as each milestone is met.
Output: A production system running in the partner’s real environment.
Unlock and replicate
We step back and record what the system unlocked: government budget, development finance, private investment. Then the model travels to neighbouring countries.
Output: Evidence, a handed-over system and a cohort of technologists who have deployed before.
Two institutes and a fund.
African Institute of Public Policy
Finds where systems are really stuck, lines up the institutional partner and clears the regulatory path. Home to Deploy Africa and The Commons Table.
Explore the Institute →Institute of Advanced Learning
Trains the partner's own staff alongside the deployment team, so a system keeps running after ITC steps back. Runs the Deployer Corps and the Credential.
Explore the Institute →Apex Fund
Seed and early-stage funding for African startups, with ITC's deployment support and institutional network behind the founder.
Explore the Fund →One question. One room. Nothing said is attributed.
We bring practitioners to a table for an evening and put one hard question about technology in Africa in front of them. No panels, no slides, no speeches.
Dinner Two goes to Lusaka, on who owns Africa's data when it trains a model. Dinner Three goes to Kigali, on what sovereign AI means. If you carry either question, register your interest.
Markets, cities, ministries and classrooms.
What ITC runs.
Three initiatives sit under ITC. The two Institutes find the problem and build the people who keep the system running. The Fund backs the founders who build for it.
African Institute of Public Policy
The Institute is how ITC knows where a system is really stuck. It works with governments and regional institutions to surface the bottleneck, secure the partner who will co-sign the Deployment Brief, and clear the regulatory path. Two projects sit inside it.
Institute of Advanced Learning
A deployment that needs ITC forever has failed. The Institute trains the partner's own staff alongside the deployment team, and runs the Deployer Corps and the Credential, so the people who built one system can build the next.
Apex Fund
Seed and early-stage funding for tech-enabled African startups. The founder also gets ITC's deployment support and its institutional network, which decide whether a good product ever reaches a government.
African Institute of Public Policy
Desk research tells you where donors think a system is stuck. Relationships inside governments and regional institutions tell you where it really is. The Institute is how ITC tells the difference, and it runs the two projects that act on what it learns.
It finds where the system is really stuck.
Through its relationships with governments and regional institutions, the Institute surfaces candidate bottlenecks and secures the partner who will co-sign the Deployment Brief. It then handles regulatory liaison, so a team building inside a ministry is not stopped by a rule nobody mapped.
When a deployment needs a regulation changed before it can run, the Institute sets up a policy sandbox, a bounded space to test the rule alongside the technology. Its research and forums put policymakers, technologists and citizens in one room around a named national problem, and the findings go straight to the next mission team.
Systems stop where people actually queue.
Two projects, one question.
Both start from the same place: where exactly is this system stuck, and who will fix it?
Deploy Africa
The mission cycle. We identify a binding constraint, commission the team, deploy a production system and document what it unlocks.
Read the project →The Commons Table
One hard question per evening, in a private room of practitioners. Dinner One has been held in Harare. Lusaka and Kigali are next.
Read the project →Deploy Africa: break the bottleneck, prove it works, step back.
Africa does not have a talent problem or a strategy problem. It has a deployment problem. Deploy Africa connects the continent's technical talent to national problems that technology can solve and that nobody is yet deploying it to solve.
A strategy, a study, a 200-page report, and still no working system.
A government publishes a digital health strategy. A donor funds a feasibility study. A consultancy produces a readiness assessment. Eighteen months later the report is on the shelf and the rural clinic still has no triage support, so another study is commissioned. Nobody in that sequence failed at their job. Each did what the system rewards, and the system was never built to reward a deployment.
Meanwhile a dozen developers in the same country could have built the triage system. They have the skills and they have seen the problem. They have no route through procurement, no sandbox to operate in and no deployment infrastructure behind them, so they build a consumer app and enter a hackathon. Nothing is deployed.
Five structural failures.
No one is mandated to deploy. Governments set strategy and hold the mandate, but no institution carries it across into a working deployment. In its absence the work defaults to foreign consultancies that produce reports rather than systems.
The private sector will not move first. Commercial firms need proof of demand and a de-risked environment. Without a working system there is no proof, and without private investment the system never gets built.
Development partners fund strategy, not deployment. Money flows to strategy documents and feasibility studies. It rarely reaches the iterative technical work of building inside a real institution, with real data governance, procurement rules and political dynamics.
Africa's innovators have no institutional pathway to these problems. Hackathons exist. Pathways to deployment do not.
Funding strands good ideas between prototype and deployment. The patient, milestone-linked capital that pays for getting a system into production inside a government is almost absent from the continent's innovation finance. Good ideas die in that gap.
Fifteen million young Africans enter the workforce every year, into economies that cannot absorb them. The people who pay most for every unbroken bottleneck are the farmer without reliable prices, the patient in an uncoordinated health system and the young person shut out of skills and capital.
Strategy gets written in the capital. Systems break in the district office, the clinic and at the border post.
Four phases, each with a deliverable.
Bottleneck identification
Through its government relationships, ITC finds a constraint where a targeted deployment would open up value across a whole system. Every candidate must pass five tests, listed below.
Output: a Deployment Brief, co-signed by ITC and the institutional partner.
The mission brief
ITC issues a precision challenge brief: the problem, the institutional environment, the data constraints and the success criteria. The hackathon selects the most deployment-ready technical approach, not the best pitch.
Output: a commissioned deployment team.
Deployment
The team is embedded in the institution with technical mentorship, architecture review, QA, policy-sandbox access and regulatory navigation. Milestone-linked funding keeps accountability and momentum.
Output: a production system built to the partner's real environment.
Catalytic unlock
ITC steps back and documents the unlock: budget commitments, development finance mandates, private entry, cross-border replication interest. The proven model then goes to adjacent countries.
Output: evidence, a handed-over system and a cohort of deployment-tested technologists.
The Phase 1 filter. Every candidate problem has to clear all five.
Missions are chosen for catalytic potential, never for geography. Country selection follows the bottleneck.
What matters is what the deployment unlocks afterwards.
ITC does not try to own or scale the solution. We break the bottleneck so that the actors with more reach, capital and mandate can move in.
AI + DPI
~$120K
Farmer identity and advisory system in one district
$2–10M in agricultural investment becomes viable; government funds national rollout
Blockchain + DPI
~$100K
Digital customs integration at one border post
Regional body adopts it for the full corridor; private logistics firms invest
AI
~$100K
Community health triage in one province
Health ministry secures development finance for national scale
DPI
~$130K
Interoperable data exchange across three ministries
Government commits budget for a full e-government platform
What each partner gets.
A proof you own outright
A working system built in months, alongside your own people, inside your procurement rules and regulatory framework. It becomes the evidence base for national-scale investment, and the capability behind it stays with you. ITC steps back.
Paid work on national problems
Direct access to national-scale problems with institutional backing: policy-sandbox access, regulatory navigation and deployment-grade mentorship. This is milestone-funded work, not a prize, and it leaves a verified deployment record.
Documented unlock ratios
Every mission produces structured evidence of the follow-on commitments it triggered. The portfolio spreads across bottleneck types, countries and technology stacks, and the model is built to replicate through actors with greater reach.
Which technology, and when.
Artificial intelligence
Extends scarce human capacity where there are too few doctors, extension officers or inspectors: health triage, agricultural advisory, multilingual citizen engagement, fraud detection in procurement.
Blockchain
Gives verification where institutional trust is thin: land registries, commodity provenance, customs documentation, credential checks.
Digital public infrastructure
The foundation layer: identity, payments and data exchange built for African conditions, including the trade facilitation that AfCFTA implementation needs.
Most missions combine all three. A farmer platform might use DPI for identity, blockchain to verify transactions and AI for advice. What we bring is the architecture. No single tool does the job.
Targets for the first two years.
At twelve months, ITC aims for three to four completed missions across different countries and challenge domains, each with a working system handed over, documented unlock evidence for each one, and fifteen to twenty deployment-experienced innovators in the network.
At twenty-four months the target is six to eight completed missions with at least two cross-border replications, at least one deployment at national scale through government adoption, and a network of forty to sixty deployment-experienced innovators. These are targets, and ITC will publish the evidence against them as it accumulates.
Institute of Advanced Learning: the system keeps running after we leave.
A deployment that needs ITC forever has failed. The Institute makes sure the partner's own staff can run the system, and that the people who built it carry what they learned into the next one.
Training starts on day one.
The Institute trains the deployment team and the partner's own staff in parallel, on the AI, blockchain and DPI stack the mission uses. Handover readiness is a milestone in the deployment plan, not something we bolt on at the end.
Skills built under the pressure of a real deployment last longer than a workshop certificate, so the Institute's programmes attach to live missions wherever possible.
Every system we leave behind needs people who can run it.
Who in Africa has done this before?
Firms join the Deployer Corps. Individuals earn the Credential at the close of a deployment, once they have taken a system from brief to operating handover inside an institution.
Governments and development partners ask that question all the time, and today nobody can answer it. Each mission adds to the number of people who can.
The Commons Table: one question, one room, no audience.
A private dinner series for the people who build, fund, regulate and use technology in Africa, hosted with ITC. Each evening takes one question the field hasn't answered yet and stays with it until the room has said something true.
How an evening works.
Deploy Africa starts with a hard question: where exactly is this system stuck? Desk research rarely answers it. A private table of practitioners is one of the places ITC listens for the answer, and the question each dinner leaves open can feed the next Deployment Brief.
Three dinners, three cities.
AI Beyond the Tech: Are Our Institutions Ready for What Comes Next?
The first table asked what surrounds the technology: the schools, laws, workplaces and norms that decide whether AI helps or harms. It left three questions open, and two of them became the next two dinners.
The Language Commons: Who Owns Africa's Data When It Trains a Model
Dinner One ended on trust: pooled infrastructure needs it, and nobody has built it yet. Lusaka takes that problem to its raw material. African-language models are being trained now on speech and text collected from African communities. Who holds that data? Who licenses it? Who benefits when it trains a model? The table asks what a data commons would have to guarantee before a ministry, a lab and a community would all put something into it.
The Right to Refuse: What Sovereign AI Means
Dinner One left a different gap: Africa has no single line for what its AI is for. Kigali asks what sovereignty means in practice. Is it owning a model, owning compute, owning the data, or holding the power to decline a system, a contract or a dependency? If a country cannot say no, what is it sovereign over?
What the room said.
The table was cross-sectoral on purpose: government, law, the creative industries, funding, digital transformation, music and the media. What follows is the host's record, grouped by theme and written without attribution.
Many guests arrived sceptical, mostly on the fear that AI will take their jobs. Most found the opposite, on one condition: nobody lets the human out of the process. By the end of the evening the theme, AI beyond the tech, had stopped being a slogan and become the argument.
The human stays in the loop
AI worked best where the person stayed engaged, knew what they were doing and knew what they were aiming for. The relationship is symbiotic, and it only holds if both sides stay in it.
The technology is the easy part
What matters is everything around it: an honest understanding of the needs being served, the policy frameworks, the regulation and the skills.
Why countries build alone
Every country wants its own data centre and its own systems. Would pooled infrastructure be more powerful? The room backed the idea of coming together, with caveats, and named trust as the biggest barrier. The practical case for trying anyway was funding, since funders and large companies engage better where there is coordination.
Government support and de-risking
The large hyperscalers received a great deal of direct and indirect support until they became viable. Africa does not do the same, and support of that kind de-risks execution. It tied back to a wider view that the continent does not do enough research and development.
Should Africa build its own models?
One view held that Africa will always be behind for now. Another held that it does not need its own models at all, and could influence the models in development or build on top of them. Dropping the assumption removes an artificial urgency: countries need to be certain what they want to achieve, then build toward it. The table also asked where the regulators are.
Talent and the road home
Africans around the world are doing cutting-edge work. Could they be pooled and brought back? The room split on whether they would come, with scholarship return clauses cited as a measure that did not work, and humanity, family and patriotism cited as what brings people home.
The psychology underneath
Nobody feared a terminator-style apocalypse, and nobody thought AI is simply making people dumber. The worry was quieter: handing a device to a child and walking away. Being more engaged and more human with children is how a generation gets a moral compass.
Putting government to the test
A direct challenge went to government: innovate, and let us see what happens. The room also insisted Africa is not sitting on its laurels in the AI race, and that Africa tells too little of its own story, its successes and its needs.
Four takeaways.
The first was intentionality: knowing what we want AI to do for us before deciding how to build it. The second was the human element, which guests returned to whether the subject was work, models or children. The third was that we are not solving a tech problem. The fourth was that Africa needs to come together.
Three questions for the next tables.
- What is Africa's single line for what its AI is for, given that other blocs can state theirs in a sentence?
- How can countries build the trust that pooling infrastructure would require?
- What would actually bring African talent home: money, continuity or belonging?
Lusaka takes the second. Kigali takes the first. The third is held for a later table.
Tell us which question you carry.
Seats are by invitation, and curation decides the table. Registering interest is not a booking. It tells the host who is working on the problem a dinner names, and it is how people outside the host's network reach the room.
Apex Fund: seed capital, and ITC behind the founder.
Apex Fund invests in seed and early-stage, tech-enabled African startups. The cheque is only part of what a founder gets. ITC adds technical deployment support and a route into its institutional network, and those two things decide whether a good product ever reaches a government, a utility or a regulator.
Three things from one backer.
Capital
Seed and early-stage funding for tech-enabled African startups.
Technical deployment support
ITC's deployment practice behind the founder: architecture review, quality assurance and help getting a system running inside a real institution.
Institutional network
Access to the governments, regional bodies and development partners that ITC works with through the African Institute of Public Policy.
The cheque is half the job. The other half is getting the product in front of a ministry.
Alongside the two Institutes.
The Fund sits beside the Institutes. When a founder's technology fits a bottleneck that a Deploy Africa mission has identified, the Institutes open the door to the institution that needs it and the Fund supplies the capital.
Applications and enquiries go to info@itcentre.africa until the application form is published on this page.
What we are learning, written down.
ITC's writing meets the same standard as its deployments. Every claim is checked and every figure is sourced.
The newsletter on Africa's startup and innovation ecosystem.
Founders Footprint follows the builders whose work ITC's missions draw on: what they ship, where they get stuck and what the rest of the field can learn from both.
Subscribe to get each issue as it is published.
Three essays by Garikai Nhongo.
- 18 Aug 2025Accelerating Development in Developing Countries: Directing Resources Towards Holistic Technological Integration
- 18 Aug 2025Everyday Intelligence: Does AI Have a Place in Africa's Streets and Farms?
- 18 Aug 2025Zimbabwe's Quiet Revolution: Africa's Next Tech Frontier?
Bring us a constraint.
If you run a government system that is stuck, fund work that has to run in production, build technology, or belong at the Commons Table, start here.
Write to us.
info@itcentre.africa
Tell us what you are bringing: a constraint to examine, a partnership to discuss, a team to put forward for a mission, an Apex Fund application or enquiry, or a request for a seat at the Commons Table. For the Commons Table you can also register interest directly.