The Silicon Valley Illusion
In the early 2010s, Uber disrupted global transportation by commoditizing an entirely invisible transaction. Driven by a rigid Silicon Valley philosophy, the platform demanded that users maintain an active credit card on file.
This completely divorced the physical act of transport from the cognitive friction of payment. You push a button, a car arrives, and you get out. It was frictionless, seamless, and magical.
But when Uber exported this uncompromising card-only architecture to emerging markets like India and subsequently Africa, the magic broke.
Uber’s frictionless dream crashed into the heavy reality of low credit card penetration and a deep, systemic lack of institutional trust.
To survive, a trillion-dollar tech giant had to humble its global playbook, break its own design rules, and introduce the ultimate friction. They had to introduce physical cash.
They were not alone. Netflix is a platform engineered for 4K Smart TVs and infinite broadband. But when they looked at Africa, they realized they couldn’t just translate their app into local languages. To penetrate the market, they had to fundamentally re-architect their video encoding using AV1 codecs and launch mobile-only plans to combat severe data scarcity.
I constantly see startups making this exact mistake today. When you blindly export Silicon Valley’s obsession with frictionless UI to Lagos or Nairobi, you don’t get a seamless user journey. You build a “Digital Norman Door.” You end up with a product that looks beautiful in an air-conditioned boardroom but completely fails the user in the real world.
In the Global South, falling into this aesthetic-usability trap is fatal. To build products that actually scale here, product architects must stop building for the user they want and start engineering for the human they have.
To do that, we must kill the marketing persona.
The True Barriers of the African Market
Most startups begin their product development by drafting a marketing persona. It usually reads something like this:
“Meet Sarah. She is a 24-year-old professional in Lagos who loves artisanal coffee and wants a faster, more delightful way to send money.”
Sarah is a fantastic tool for an advertising agency. However, she is completely useless to a software product development team.
Knowing Sarah’s hobbies does not help a developer design a secure API, optimize a localized escrow system, or decide whether to build on USSD or React Native.
To build resilient financial infrastructure in Africa, we must utilize Constraint-Based Personas. Instead of defining a user by their desires, we need to define them exclusively by their limitations. We must map out what they cannot do, the hardware they are forced to use, and the trust deficits they navigate daily.
When you look at the hard macroeconomic data of Nigeria, the baseline constraints become very clear.
First, we have the hardware constraint. According to 2023 mobile operating system data from StatCounter, Android controls over 85 percent of the Nigerian mobile market. However, market intelligence reports from the International Data Corporation (IDC) indicate that the average mass-market device is severely limited. These phones typically run on just 2GB to 4GB of RAM and have 32GB to 64GB of internal storage. Users are in a constant state of digital triage, regularly deleting apps just to make space.
Second, we have to account for the data constraint. Internet is not a utility in this market; it is a strictly metered commodity. Based on pricing data tracked by the Nigerian Communications Commission (NCC) and the Alliance for Affordable Internet, the average cost of 1 Gigabyte of data in 2023 was roughly 287 Naira. Against the national minimum wage of 30,000 Naira at the time, 1 Gigabyte of data consumed nearly 1 percent of a user’s monthly income.
Finally, there is the institutional trust constraint. The 2023 EFInA Access to Financial Services in Nigeria survey highlights that while formal financial inclusion hovers around 64 percent, a critical 10 percent of the adult population relies exclusively on informal, offline financial services. These individuals use traditional Ajo or Esusu collectors because they prefer physical human accountability over digital clouds.
When you map these verified constraints, the true architectural challenge reveals itself.
Paga and the Offline Reality
Long before the current era of digital banking, Paga recognized the absolute necessity of constraint-based design.
The friction in the market was obvious. The Nigerian economy was heavily cash-driven, making the act of carrying physical cash dangerous and inefficient. Yet, as EFInA data historically showed, the vast majority of the population was entirely unbanked and disconnected from the internet.
If Paga had designed for “Sarah,” they would have built a heavy, data-intensive mobile app. Instead, they built a constraint persona: a consumer who needs to transfer funds safely but does not possess a smartphone, has zero access to mobile data, and lacks formal digital identification.
This led to a very specific design question: How might we facilitate secure electronic money transfers for users without smartphones, internet, or even modern USSD banking rails?
To answer this, Paga built their foundational MVP architecture around an ingenious SMS-to-Voice flow and a physical agent network. A user could simply send a text message to initiate a transfer. Because SMS is unencrypted and insecure, Paga’s system would instantly trigger an automated voice call back to the user, prompting them to securely enter their PIN on their phone’s keypad to authorize the transaction.
There was no graphical user interface, no 10-megabyte download, and no internet requirement. For those who couldn’t even manage an SMS, Paga deployed human agents across neighborhoods to act as physical cash-in and cash-out nodes. Paga stripped away the aesthetic entirely to solve the core mathematical constraint of the environment. They didn’t build a beautiful app; they built a financial lifeline.
PiggyVest and the Cognitive Constraint
When we move beyond physical hardware limitations, we encounter the psychological barriers of the user. In the financial sector, one of the most difficult constraints to design for is human discipline.
In late 2015, a conversation went viral on Nigerian Twitter. A woman revealed she had saved 365,000 Naira over the course of a year simply by putting 1,000 Naira every single day into a physical wooden savings box, locally known as a ‘kolo’.
This viral moment exposed a massive friction point in the market. The founders of PiggyVest recognized that traditional bank accounts were fundamentally designed for immediate transactions, not sustained saving. Young earners faced severe “spending urgency,” meaning their salaries were spent almost as soon as they hit their accounts. People desperately wanted to adopt a disciplined saving culture, but they were relying on an insecure, physical method because the digital alternatives failed to understand their psychology.
Furthermore, this demographic was operating in a low-trust environment. The market was highly skeptical of digital financial tools, especially following the recent collapse of rampant Ponzi schemes like MMM in Nigeria.
If the founders had designed for a traditional marketing persona, they would have built a standard, flexible digital wallet with a beautiful interface. Instead, they built a constraint persona: a young earner battling daily micro-expenses, who wants to save small amounts but fundamentally lacks the discipline to not spend their own money, and who is highly suspicious of digital platforms.
The resulting “How Might We” question was brilliant. How might we digitize the strict discipline of a physical wooden box, protecting a user’s money from their own spending urges while proving the system is not a scam?
Within two weeks of that viral tweet, the team built the Minimum Viable Product for Piggybank.ng. The platform digitized the wooden box concept by automating daily, weekly, or monthly savings directly into a digital wallet.
But the true genius was in how they designed the constraint. To distinguish themselves from standard bank accounts and promote true saving, they implemented a deliberate friction point. Users could only access their funds for free once every quarter. They essentially digitized the physical friction of “breaking the box.”
To solve the institutional trust constraint, they did not rely on expensive marketing billboards. They relied on raw, organic community proof. When their early users successfully withdrew their locked savings on December 31, 2016, those users took to social media to share their positive experiences. That user-generated validation proved the system worked, instantly bridging the trust gap and fueling their exponential growth the following year.
Moniepoint and the Institutional Trust Constraint
Perhaps the most difficult barrier to cross in the Global South is the lack of institutional trust.
Before founding Moniepoint, Tosin Eniolorunda and his team at TeamApt were building backend software solutions for traditional commercial banks. During this time, they noticed a glaring disconnect. The traditional banking industry was entirely obsessed with building sleek online products for urban, digitally connected areas. Meanwhile, a massive, underserved population across the country was being completely neglected.
This offline demographic faced terrible friction. Transaction failure rates were high, interoperability was poor, and physical ATMs were largely inaccessible. More importantly, a significant portion of this population lacked basic digital literacy.
If you build a state-of-the-art mobile banking app for a market trader who does not understand how to navigate nested menus, you have built a Digital Norman Door. When an unbanked individual loses money in a digital transaction, they do not want to call a toll-free customer support hotline. They want to speak to a human being.
Recognizing this, the team pivoted their business model entirely. They stopped trying to force a digital-only experience and asked a new architectural question. How might we deliver reliable banking infrastructure to offline communities by leveraging pre-existing local relationships rather than demanding digital literacy?
Their solution was the agency banking model. Instead of expecting users to trust a faceless app, Moniepoint placed human agents directly within the communities.
These agents were onboarded by people the community already knew and trusted. The human agent became a physical branch. If a transaction failed or an issue arose, the customer had a familiar, physical point of contact to hold accountable.
Moniepoint also had to engineer around severe hardware constraints at the agent level. Point-of-Sale (POS) devices in the market were highly fragmented and ran on poorly written code. To solve this, the engineering team developed a unified virtual machine environment that allowed their software to be written once and run seamlessly across various hardware manufacturers.
They did not demand that the Nigerian masses adapt to complex software. They adapted their software to operate through trusted human proxies.
Chowdeck and the Vendor Infrastructure Constraint
The constraints of the Global South do not only apply to the end consumer. Often, the most severe friction lies with the merchants and the physical infrastructure required to serve them.
Before Chowdeck entered the market, the primary friction was that existing food delivery services were tailored to a niche, international-style market.
These platforms focused heavily on items like pizza and burgers, which the average Nigerian did not eat on a daily basis. The real, mass-market demand was for local staple foods like Amala and Pounded Yam, but the existing infrastructure simply was not designed to handle the logistical complexities of transporting these local dishes. Furthermore, accepting food delivery in Nigeria often meant accepting a waiting period of two to three hours.
The constraint persona for their merchant side was a local food vendor, or ‘buka’ owner, operating in a highly informal commercial environment. Many of these early vendors did not have the digital literacy or high-end hardware required to manage a complex restaurant-facing tablet application.
The architectural question became clear. How might we integrate local, offline food vendors into a rapid delivery network without forcing them to adopt complex new software?
Because the founders were former software engineers at Paystack, they had the technical capacity to build anything. In fact, they built the very first version of their customer-facing mobile app in just three weeks to capture demand. However, they made a brilliant constraint-based design choice for the backend.
Instead of over-engineering a complex merchant portal that local vendors would struggle to use, they intentionally kept the backend operations heavily manual at the start. When an order came through the customer app, the Chowdeck team coordinated with roadside vendors and riders using direct, everyday communication channels like SMS, WhatsApp, and regular phone calls.
This manual approach allowed them to physically deconstruct the logistics. They mapped the bottlenecks, rider reliability, and vendor preparation times in the real world before they ever tried to automate it with code.
They stripped away the assumption that vendors needed state-of-the-art hardware, choosing instead to meet the merchant exactly where their technological capacity ended. To secure the vendors’ trust, Chowdeck broke industry norms by paying merchants as quickly as possible, ensuring these small businesses had the daily liquidity they needed to survive.
The Blueprint for the Next Billion Users
As a product architect, I constantly see teams fall into the trap of trying to design their way out of foundational infrastructure problems using pretty interfaces. We obsess over pixel-perfect layouts, seamless animations, and the “happy path” of a user journey. But in emerging markets, consumer behavior does not passively adapt to the requirements of Western software. Rather, software must forcefully deconstruct and rebuild itself to survive the physical, financial, and regulatory constraints of the market.
The history of global business expansion is replete with case studies of rigid corporate playbooks collapsing under the weight of localized socio-economic realities. When you look at the trajectory of Paga, PiggyVest, Moniepoint, and Chowdeck, a unified blueprint emerges.
None of these companies succeeded by building frictionless, data-heavy applications for an imaginary, upper-middle-class marketing persona.
They succeeded by looking brutally at the hard metrics of their environment. They accepted that mass-market devices operate on 2GB to 4GB of RAM. They respected the fact that a single gigabyte of data consumes nearly 1 percent of a minimum wage earner’s monthly income. They understood that a massive segment of the population relies exclusively on offline, informal trust networks.
You cannot achieve true scale in the Global South by building a Digital Norman Door. A beautiful application that requires a 4G connection and a modern smartphone in a market dominated by cracked screens and expensive data is a failure of product design.
If you want to build solutions that actually change lives, you have to stop designing for the user you want. Kill the marketing persona, and start architecting for the constraints of the human you have.
About the Author
Faheed Alli-Balogun is a Senior Product Designer, Architect, and active contributor to Africa’s digital ecosystem. With a background spanning product leadership at Chimoney (Techstars ’23) to advising early-stage fintechs, Faheed specializes in open payments infrastructure and the mechanics of trust in digital platforms. As a guest lecturer at institutions like Covenant University and Alabama A&M University (AAMU), he champions “Designing for Agency”, a philosophy dedicated to building resilient, constraint-aware financial products that prioritize the human over the system. He also actively mentors early-stage builders through Dreamax.Â
