The Infrastructure Problem: Why Every African Tech Company Is Also a Logistics Company

There is a question that gets asked about African tech companies that reveals more about the questioner than the companies themselves. The question is: "Why does it take so long?" Why does a payments startup in Lagos take 18 months to reach product-market fit when a comparable product in San Francisco took 6? Why does an e-commerce company in Nairobi have costs that an American counterpart would never recognise?

The answer is not execution quality, talent gap, or regulatory dysfunction — though all of those factors play roles. The deeper answer is infrastructure. Building a technology product in Africa frequently requires building, alongside the product itself, foundational infrastructure that the American or European equivalent gets for free from decades of prior public and private investment.

This is not a complaint about Africa. It is an observation about where the most valuable assets in African tech get built — and therefore where the deepest moats come from. The founders who understand this spend their first 18 months differently than their counterparts elsewhere. They come out the other side with something competitors cannot easily replicate: infrastructure that took years to build, that is now proprietary, and that sits underneath a product that anyone can see but very few can match.

The Four Infrastructure Gaps That Define African Tech

There are dozens of infrastructure gaps that African tech founders navigate. Four are structural — present in virtually every market, across virtually every product category, with costs that compound at scale.

Gap 1: Power

Six hundred million people in Sub-Saharan Africa lack access to reliable electricity. Even in cities where grid connection is widespread, reliability is a different question. Lagos averages more than 15 power outages per month in commercial districts. In rural Sub-Saharan Africa, grid-connected locations average under 4 hours of reliable electricity per day. The World Bank estimates that power unreliability costs African businesses 2–4% of annual revenue in lost productivity and damage to equipment.

For tech companies, the power gap has two primary expressions. First, data center infrastructure requires reliable power to operate. This is not optional — a fintech processing transactions on a server that loses power loses transactions, loses data integrity, and loses customer trust. The minimum viable solution is 48 hours of backup generation capacity, which for a small data center represents $40,000–$80,000 in generator and fuel storage CapEx that a US cloud provider simply does not incur. Second, agent networks and physical distribution points — the offline touch points through which many African tech companies acquire and service customers — require power for POS terminals, smartphones, and connectivity devices. Agent banking networks in power-unreliable environments have built entire supply chains for solar-powered agent kits: solar panel, battery backup, router, POS terminal, and smartphone, bundled and deployed to tens of thousands of agents. This is infrastructure that a neobank in London never thinks about.

Gap 2: Last-Mile Address

Seventy percent of Africa has no formal addressing system. In most of the continent, "1247 Lagos-Abeokuta Expressway, opposite the petrol station, next to the blue building" is not a workaround for a missing address — it is the address. This is not a problem unique to Africa; many parts of rural Asia and Latin America share it. But in Africa it is pervasive enough to define the logistics economics of any business that needs to physically locate customers or deliver goods.

For logistics and e-commerce companies, address resolution is a pre-requisite for delivery. Kobo360 built its own GPS-based route logging system because the routing software built for Western markets with formal addresses could not navigate Nigerian road networks. Companies like Lori Systems and Sendy built similar proprietary geo-coordinate systems for their respective markets. What3words has mapped over 50 million African locations to 3-word address codes — a valuable partial solution that is being adopted slowly by logistics companies but has not yet reached the ubiquity that would make it a standard.

For consumer-facing products that require customer location — whether for delivery, for field sales, or for verification — the absence of formal addresses adds an engineering and operational layer that simply does not exist in markets where Google Maps and a postal code solve the problem. Every African e-commerce company has built some version of address normalisation: a system that takes what customers provide and resolves it to a delivery coordinate. This is infrastructure built from scratch, maintained continuously, and not available as a commodity API at any price comparable to what Google Maps charges in Western markets.

Gap 3: Payment Rails

Cash accounts for approximately 75% of transaction volume in Sub-Saharan Africa by number of transactions. This is not primarily a smartphone penetration problem or a digital literacy problem — in many markets, the majority of the population that is actively trading and spending in the informal economy simply has no reliable digital payment option that works across the full range of their daily transactions. Mobile money has made enormous progress — GSMA estimates that there are 781 million registered mobile money accounts in Sub-Saharan Africa — but active usage rates, acceptance by merchants, and reliability across network outages create a payment landscape that is radically more fragmented than any Western equivalent.

For every consumer-facing African tech company, this means building a multi-rail payment collection layer that integrates: bank transfer, mobile money (Paystack, Flutterwave, and direct integrations for MTN MoMo, Airtel Money, OPay, PalmPay), USSD payment flows for customers without smartphones, cash collection via agents, and for some segments, card payment. Each of these integrations requires engineering time, compliance work, and ongoing maintenance. The equivalent in a Western market is a single Stripe integration — typically achievable in 4–8 engineering hours and with a standard API that changes infrequently. The multi-rail African payment integration runs to 400+ engineering hours and involves APIs that change on different cycles, with different reliability profiles, and different compliance requirements. This is not hypothetical overhead — it is a real cost that every African consumer tech company carries.

Gap 4: Trust Infrastructure

In developed markets, trust infrastructure is ambient. Credit bureaus accumulate years of payment history to tell lenders whether a borrower is creditworthy. Yelp and Google Reviews tell consumers whether a merchant is legitimate. LinkedIn and professional registries tell B2B buyers whether a company is what it claims. These systems exist because decades of investment — public and private, regulatory and market-driven — created and maintained them.

In most of Africa, these systems are partial, fragmented, or absent. Credit bureaus exist in most major African markets but have thin coverage for the informal economy — where most economic activity occurs and where most fintech lending opportunity lives. Consumer review platforms have not reached critical mass in most African markets to serve as reliable trust signals. Business registries are often inaccessible digitally, incomplete, or not maintained in real time. The absence of ambient trust infrastructure means that every marketplace, every lending product, and every B2B platform in Africa must build its own trust layer from scratch: its own identity verification, its own seller/provider rating system, its own dispute resolution mechanism, its own default consequence architecture. This is infrastructure that the market takes years to build and that cannot be bought from a vendor.

Companies That Won by Building Infrastructure First

The pattern across Africa's most successful tech companies is consistent: they invested in infrastructure before they invested in product polish, and the infrastructure they built became the competitive moat that protected them when better-capitalised competitors arrived.

M-Pesa is the canonical case. When Safaricom launched M-Pesa in 2007, it was not launching a mobile payments app. It was launching a physical infrastructure network: 16,000 agents across Kenya, each trained to conduct cash-in and cash-out transactions, each integrated into a financial system that could store, transfer, and settle value. The agent network was the product. The mobile money capability ran on top of it. Safaricom spent 18 months building the agent network before M-Pesa processed its first transaction at scale. By the time competitors recognised the opportunity and began building competing mobile money products, Safaricom had 25,000 agents and 5 million customers. The infrastructure was the moat. It is now, nearly two decades later, 170,000 agents and 30 million customers — a network so embedded in Kenyan economic life that every subsequent attempt to build a competing mobile money product has failed or operated in a permanent second-tier position.

Kobo360, the Nigerian freight marketplace, encountered the trust infrastructure gap immediately. When it tried to launch a marketplace connecting shippers with truckers, it discovered that the fundamental mechanics of marketplace trust — verified carriers, load tracking, payment on delivery — were absent. Nigerian trucking operated on cash, relationship, and reputation networks that did not extend beyond personal acquaintance. Kobo360 spent its first operational year not building the marketplace product but building the infrastructure that made the marketplace possible: a payment system that advanced fuel money to truckers before delivery (solving the cash flow problem that prevented truckers from accepting long-haul loads from unknown shippers), a GPS tracking system that gave shippers visibility into their cargo, and a rating system that created portable reputation for carriers. The marketplace product came second. The infrastructure came first — and it became the competitive moat. By the time a competitor tried to enter Nigerian freight aggregation, Kobo360 had the payment relationships, the GPS network, and the carrier reputations already built. Replicating it would have required years, not months.

Flutterwave spent its first years building payment rails — the technical and regulatory infrastructure that connects Nigerian bank accounts, international cards, and mobile money into a single programmable API — before it built consumer-facing products. The payment rails were not interesting to the consumer press. They were not a social media story. They were a multi-year engineering and compliance project that required building banking relationships in multiple jurisdictions, negotiating with every major card network, and navigating Nigerian and Kenyan central bank regulation simultaneously. By the time Flutterwave was ready to launch Barter (its consumer product), it had the underlying infrastructure to power it and every competitor's product simultaneously. Stripe's $200 million acquisition of Paystack — which had built a comparable payment rails product — was an acquisition of infrastructure, not of a user base.

The Cost Multiplier of Building Your Own Infrastructure

The infrastructure investment required to build an African tech company at scale is quantifiably more expensive than the equivalent in developed markets. Understanding the magnitude of this premium matters for founders planning their runway and for investors modeling returns.

A US SaaS startup in 2026 can assemble its core technology infrastructure for approximately $150–$200 per month in the early stages: AWS for hosting, Stripe for payments, Google Workspace for productivity, Plaid for banking data, Google Maps for geolocation, Persona or Checkr for identity verification. These tools were built as infrastructure-as-a-service by companies that invested billions to make them commodity inputs. The cost of accessing them is negligible.

An African equivalent must substitute home-built or expensive bespoke solutions in several of these categories. Backup power for data infrastructure: $8,000–$40,000 in upfront CapEx plus ongoing fuel costs. Multi-rail payment integration: 400+ engineering hours versus 4–8 hours for Stripe, representing $40,000–$80,000 in engineering cost at African market rates. Address normalisation layer: either built internally (120+ engineering hours) or licensed at a cost that has no Western equivalent in the equivalent category. KYC via Smile Identity or Youverify: $0.25–$0.50 per verification, which at 100,000 verified users represents $25,000–$50,000 — a cost that US consumer fintechs running on instant bank verification do not encounter in the same form. Taken together, the infrastructure cost premium for an African tech company versus a US equivalent ranges from 4× to 6× in total cost of building to equivalent functionality.

This premium is not wasted. It produces something the US startup does not have: proprietary infrastructure that is genuinely difficult to replicate. The payment integration that took 400 hours to build is not available from any vendor at any price. The agent network that took two years to recruit, train, and deploy is not something a competitor can purchase. The infrastructure premium translates, for the companies that survive it, into a moat premium — the infrastructure they built at high cost becomes the asset that makes them worth acquiring.

The M&A Opportunity: Infrastructure as Moat

The clearest evidence that African tech infrastructure is the valuable asset — not the consumer product built on top of it — is where the acquisition value has concentrated in every major African tech deal.

Stripe did not pay $200 million for Paystack's consumer user base. Paystack's consumer product, Checkout, had meaningful adoption but was not the reason for the acquisition price. Stripe paid for Paystack's payment rails: the banking relationships, the card network integrations, the regulatory licenses, and the engineering infrastructure that enabled programmatic payment processing across Nigerian, Ghanaian, and South African markets. The user base came with the infrastructure. The infrastructure was the prize.

Visa paid $110 million for a 20% stake in Interswitch — valuing Interswitch at $1 billion — not because Interswitch's consumer apps had beaten any competitor in user experience but because Interswitch's switching network processed the majority of Nigerian ATM and card transactions. The switching infrastructure — the physical and software layer that routes payment messages between banks — was the moat. No amount of consumer product investment would allow a new entrant to build an equivalent switching network in less than a decade.

The implication for founders is strategic. If you are building infrastructure in the process of building your product — payment rails, identity systems, agent networks, logistics routing — you are building the asset that makes you worth acquiring, not just the product that makes you worth using. Thinking about the infrastructure layer as a standalone asset, with its own defensibility analysis and its own value creation logic, is a practice that the most sophisticated African tech founders adopt early.

The Emerging Solutions: Infrastructure-as-a-Service for African Founders

The good news for founders building in Africa today is that much of the infrastructure that M-Pesa, Kobo360, and Flutterwave spent years building from scratch is now available as a purchased service. The founders of 2016 built so that the founders of 2026 can buy.

In address infrastructure, what3words now covers more than 50 million African locations, mapping every 3×3 metre square to a unique three-word address. Sendbox and Shipbubble have built logistics APIs that abstract the carrier fragmentation of African last-mile delivery — integrating GIG Logistics, DHL, Kwik, and dozens of local carriers into a single API that merchants and e-commerce platforms can call without building carrier relationships directly.

In power infrastructure, Arnergy and PowerTrust are building commercial solar-plus-storage products designed explicitly for Nigerian SMEs and small data center operators. The model is power-as-a-service: Arnergy installs the solar and battery system at no upfront cost and charges a monthly power subscription. This converts the CapEx barrier of energy independence into an OpEx line item that early-stage companies can absorb.

In payment infrastructure, Mono has built the open banking API for African markets — providing programmatic access to bank account data, transaction history, and identity information from Nigerian, Ghanaian, and Kenyan banks in a model directly comparable to Plaid in the US. Sudo Africa provides card-issuance-as-a-service, allowing any fintech to issue virtual and physical cards to users without navigating the bank licensing and scheme agreements that card issuance historically required. Stitch is building the equivalent open banking infrastructure for South Africa.

In identity and trust infrastructure, Smile Identity has processed over 60 million identity verifications across Africa using government ID databases, biometric matching, and document OCR — providing KYC as an API that any product can integrate in days rather than building an identity verification system from scratch. Youverify and Identitypass provide comparable document verification for specific African markets. Dojah and Okra are building the aggregation layer that combines identity, banking, and alternative data into a single underwriting API for fintech credit products.

What This Means for Founders and Investors

The infrastructure reality of African tech has two sets of strategic implications — one for the founders building companies and one for the investors evaluating them.

For founders, the critical insight is that the infrastructure investment is not overhead. It is the product. The 18 months you spend building payment rails, agent networks, or last-mile logistics capability is not time away from the product that customers use — it is building the asset that competitors will find impossible to replicate. Plan for it. Budget for it. Hire for it. And think carefully about which infrastructure to build and which to buy: the infrastructure that is genuinely proprietary — because it embeds local relationships, local knowledge, or local regulatory capital that cannot be purchased — is worth building. The infrastructure that is now available as a commodity API from a credible vendor is worth buying, so that engineering time can be invested in the genuinely proprietary layer.

For investors, the infrastructure premium requires a different financial model than the US or European equivalent. The discounted cash flow model for an African tech company must account for infrastructure CapEx that has no US equivalent in the comparable category. Benchmarking burn rates, customer acquisition costs, and time-to-revenue against US SaaS comparables produces a false picture that systematically undervalues African tech companies in early stages and overestimates their risk. The infrastructure investment is not overhead that should be minimised — it is the competitive differentiation that justifies the investment thesis.

The portfolio implication for Africa-focused investors is that infrastructure-layer companies — payment rails, identity systems, logistics aggregators, power-as-a-service — deserve higher revenue multiples than vertical application companies built on top of them. In markets where the infrastructure layer is a de facto monopoly input for every product above it, the infrastructure company captures a portion of the value generated by every company in its vertical. This dynamic is visible in every developed tech market — AWS, Stripe, Twilio, Plaid — and it applies with equal force in Africa. The African companies building the picks and shovels of the continent's tech economy are, on a risk-adjusted basis, among the most attractive investments available.