Building where the tools don't reach

For a great many builders across this continent, the tutorial ends on that line. Not because they lack the skill to follow it — because the tool on the other side was never built with them in mind. The instruction assumes a country, a banking system, a passport that the reader doesn't have. And so the lesson quietly becomes a different one: this was not made for you. Find another way.

We find another way constantly. It is the unspoken curriculum of building technology in Africa.

The defaults that aren't ours

Most of the tools we build on carry invisible assumptions, set somewhere else, by people solving their own problems. Reliable grid power. Cheap, abundant bandwidth. A street address that maps to a delivery. A card in every pocket. A payment processor that operates in your country. Identity systems that recognise your documents.

None of those are safe assumptions here, and the numbers say so plainly. As of 2024, only around 38% of Africans used the internet — the lowest rate of any world region, against a global average near 68%, per the ITU. The divide inside that number is starker still: roughly 57% of urban dwellers online versus about 23% in rural areas, the widest urban–rural gap of any region on earth. Just over 1% of Africans have access to 5G, where the global figure is above 20%. And only about 43% of the continent has reliable access to electricity at all — meaning that for a huge share of your potential users, the first constraint isn't your app, it's whether the phone is charged.

Take any one of those defaults away and a whole stack of "standard" solutions stops working. Take several away at once — which is the daily reality for most of the continent — and you are no longer using technology so much as negotiating with it. The founder rebuilding a payment flow because the global processor won't onboard her. The team writing their own addressing system because the map renders their whole neighbourhood as a blank. The engineer designing for the phone that drops to 2G on the commute and rations every megabyte, because data can cost a meaningful slice of a day's wage.

None of this is a deficiency in the builder. It is a gap between the tool and the ground. But the gap is real, and someone has to cross it. Usually alone, usually uncredited, usually for the third time that year — because three other teams crossed the same gap last quarter and no one wrote it down.

The hidden cost is repetition

Here is the part that should bother us most. The problem is rarely that something can't be solved. Africans solve these problems all the time — brilliantly, and against the odds. The problem is that we solve them separately.

A thousand builders each privately reinventing the same workaround is not a thousand acts of genius. It is one act of genius, paid for a thousand times, in the most expensive currency a developing technology ecosystem has: the time of its best people. Every hour spent re-crossing a gap someone already mapped is an hour not spent building the thing that didn't exist before.

This is the quiet tax underneath the headline numbers. Africa's developer population is growing faster than anywhere else on earth, but a growing crowd of builders each starting from zero is not the same as an ecosystem that compounds. Isolation turns shared problems into private taxes — and that tax, not talent, is the single biggest drag on how fast this continent can build.

What we prove when we build our own

And yet — look at what happens when we do build for our own ground.

When the imported tools didn't fit, East Africa didn't wait. It built mobile money, and in doing so leapfrogged the entire branch-banking era that the wealthy world is only now, slowly, dismantling. Money moved over a feature phone, person to person, no card and no bank branch required — years before the rest of the world decided that was the future. The constraint didn't produce a worse solution. It produced a better one, because it was designed from the ground we actually stand on rather than borrowed from ground we don't.

That is the deeper thesis of building here: the places where the tools don't reach are not only obstacles. They are the places where the most original work is waiting to be done. A constraint that forces you to build from first principles, for a real context, is how genuinely new things get made — offline-first software, low-bandwidth protocols, identity that works without legacy documents, payments that assume no card. The rest of the world will eventually need what gets built for the hard edges. They just don't know it yet.

But that only works if the knowledge compounds. A breakthrough that stays locked in one team's heads helps no one cross the next gap. A breakthrough shared becomes a road others can travel — and the whole ecosystem moves faster.

From private workaround to shared infrastructure

So the question that matters isn't whether African builders are capable. That was never in doubt. It is whether we keep paying the private tax of solving alone — or turn our hard-won knowledge into something the whole ecosystem can build on.

That choice is why the Bundu Foundation exists.

Bundu is a research foundation. Its main work — the thing everything else is downstream of — is research into the infrastructure gaps that hold African and emerging markets back, and publishing what it finds as open frameworks and standards: a commons anyone can build on. Not another walled product. Shared infrastructure. When offline-first connectivity, identity, addressing, or payment gets solved well, it should become a road everyone can travel — researched, documented, published in the open, maintained as a commons — not a wheel each team privately reinvents in the dark.

And this isn't sentiment. In the Bundu Ecosystem, Ubuntu — umuntu ngumuntu ngabantu, a person is a person through other persons — is treated as an engineering constraint, not a slogan. Every design has to pass one test: does this benefit the community, or only the individual? An open framework passes it. A private workaround, hoarded as advantage, does not.

Everything points at a single outcome: to ease how Africa builds — to shrink the distance between an African builder and the thing they are trying to make.

And telia is where that work lives as a community. It is the room where the person who already crossed a gap tells you how; where a hard week becomes the seed of the next standard; where research becomes conversation, and conversation feeds back into the research. The foundation publishes; the community builds, tests, and sharpens what gets published. One feeds the other.

The talent was never the problem. The infrastructure gaps — and the isolation of facing them alone — are. We intend to close them, in the open, together. Built from Zimbabwe, for Africa, for the world.

Ndiri nekuti tiri. I am because we are. Come build it with us.