Every founder gets asked
Sooner or later, a founder building a payments app, a ride service or a marketplace in Lagos, Accra or Nairobi is asked by an investor: "So when do you become a super app?" The question assumes the answer is yes, and that the only matter is timing.
We think the question deserves more suspicion. Super apps are real and some are enormous. But the idea has travelled further than the conditions that produced it.
What a super app actually is
A super app is a single application that hosts many services: payments, messaging, shopping, transport, food, loans, and often third party mini programs built inside it. The best known examples come from Asia, where one app became the front door for daily life.
Two ingredients tend to sit underneath. First, a very large daily use habit, usually messaging or payments, that people open many times a day. Second, a shared identity and wallet that make adding a new service nearly free for the user. Once someone is verified and has money in the app, ordering a ride is a tap, not a signup.
Everything else follows from those two. The breadth is a consequence, not a plan.
Why the African case is different
Africa is not one market, so we will be careful. But a few conditions recur across the places we work.
Fragmented rails. Bank transfers, mobile money, cards and agent networks coexist, and they differ by country and sometimes by operator. A single wallet that works everywhere is harder to build than it looks, and regulation of stored value varies from one jurisdiction to the next.
Regulation by activity. Payments, lending, insurance and investment are licensed separately. A company that adds services also adds regulators. The cost of breadth is not just engineering.
Existing giants. In several markets, telecom operators and banks already hold the daily habit and the identity layer. A new entrant is not filling an empty seat.
Uneven devices and data. App size, data cost and low end phones all push toward lightweight products. Heavy, do everything apps are a harder sell when storage and bandwidth are precious.
None of this makes super apps impossible. It means the Asian route is not a template.
Other routes to the same destination
Several shapes compete with the single app, and some suit these markets better.
- Platform plus partners. Provide identity, payments and distribution as infrastructure, and let other businesses build the customer facing services. You win by being the thing others depend on, not the thing users open.
- Embedded services. Put the financial product inside someone else's flow: a loan at checkout, a wallet inside a logistics app. The user never visits your app. They still use your service.
- A strong vertical. Be the best at one job for one kind of business, then widen gradually, because users already trust you there.
Each is a way to capture the value that a super app promises, with less to carry on day one.
When going broad does make sense
We would consider it if, and only if, there is a genuine daily habit already, not a hoped for one. If people open your app daily for one reason, adding a second reason is cheap. If they open it monthly, adding features just gives them more things to ignore monthly.
It also helps when your shared layer is truly shared. If a new service needs its own onboarding, its own verification and its own wallet, you have built two products under one icon.
A hypothetical that tests the idea
Picture a payments startup with a wallet, a few hundred thousand users and a good reputation for reliable transfers. Its board asks for a ride hailing feature, a food ordering feature and a bill payments hub, all in one app, within the year.
Each looks small. Ride hailing means drivers, a pricing engine, safety processes and a support operation. Food ordering means restaurants, couriers and disputes. Bill payments means billers, each with its own integration. The wallet, which was the strength, is now one of four businesses the team must run, each with different unit economics. Meanwhile, the competitors in each of those categories do nothing else.
The founders would be better served by asking what the wallet can offer to those businesses as a partner. Let the ride company and the food company accept the wallet at checkout. The company keeps its focus, and the wallet still gains volume.
What the question hides
The super app question mixes up two ideas: owning the customer relationship and owning every service. They are not the same. A company can own the relationship through identity, a wallet and a trusted brand while others deliver the services. That is closer to what many successful platforms do, and it asks far less of a young company.
It also hides a timing question. Companies that became super apps usually did so after they had won something narrower, and with a large base. Starting from the destination, without the base, tends to produce a thin version of everything.
Questions that cut through it
Before expanding, ask what the daily action is and who does it. Ask which regulator each new service adds. Ask whether the partner route would reach the same customers with a tenth of the work. And ask whether the pull toward becoming a super app comes from users, or only from a slide in a pitch deck.
Depth tends to make a company hard to leave. Breadth, on its own, usually just makes it hard to run.