The Super App Problem
Chasing the super app dream, Pathao built ten products and nearly destroyed the one thing users actually loved.
At some point around 2018, someone opened a board meeting with a slide that said: “Pathao Super App.”
Everyone nodded. Of course. Gojek was doing it. Grab was doing it. WeChat had essentially become a country unto itself in China. The logic felt airtight: we already had the users, we already had the riders, we already had the infrastructure. All we had to do was keep adding services on top. Rides. Food. Courier. Cars. Keep stacking. Keep expanding. Build the everything app.
So we did.
At our peak, Pathao had ten verticals. Ten. Rides. Courier. Cars. Food delivery. Health. Pathao TV, where users could watch content inside a ride-hailing app, as if the thing people desperately needed between booking a bike and reaching their destination was a streaming service. Ten different product lines, each with their own teams, their own roadmaps, their own monthly reviews where someone presented numbers and someone else asked what we were doing to grow them.
The answer was always the same: build more.
How It Starts
It never feels like sprawl from the inside. Every vertical feels like a logical extension of the last.
Courier was first. That was the original Pathao, three riders, a spreadsheet, a woman named Poter Bibi negotiating us down to 60 taka per delivery. Scrappy and real and actually working.
Then we launched rides because our riders had dead hours between deliveries and we needed to sweat those idle assets. That worked too. Students outside BRAC University, five minutes instead of thirty, word spreading through campus Facebook groups without us spending a taka on ads.
Then Uber entered Bangladesh with cars and we needed to fight back, so we launched Pathao Cars. Then the margins on bikes were thin and food delivery had better economics, and HungryNaki and Foodpanda weren’t serving the Star Kabab crowd, so we launched Pathao Food. Then we were in Dhaka and quietly expanded to Chittagong before Uber could get there.
Every decision had a rational explanation. Every expansion was defensible in a board deck.
Then came health. The pitch was that we had a captive audience, people sitting on the back of a bike with nothing to do but stare at their phones, so why not connect them to doctors, clinics, health services? It sounded compelling in the meeting room. In practice, we were a ride-sharing company trying to build healthcare company without clinical expertise, regulatory relationships, medical trust, or the focused attention the category actually demanded. We launched anyway.
Then came Pathao TV. We had an app with a large daily active user base, so why not keep people inside it longer? The problem was we had neither the capacity nor the budget to produce anything worth watching. So we brought in content partners. Those partners had their own incentives and their own definition of quality. Users opened the Pathao app to book a ride. Nobody opened it to watch a show. The data was unambiguous. The usage numbers on Pathao TV were embarrassing. But we kept it alive for months because killing it meant admitting we had wasted the engineering time that built it, time that could have gone toward making our core rides product better, faster, more reliable, more loved.
That is the hidden cost nobody talks about. Not just the cost of building the wrong thing. The cost of not building the right thing with those same hours.
Why Bangladesh Doesn’t Work Like China
Here is what nobody says loudly enough in founder circles: the super app is a Chinese invention, born in a very specific context that almost nowhere else in the world actually replicates.
WeChat works because China had no dominant incumbent apps when smartphones arrived. The infrastructure gap meant WeChat could colonize everything, messaging, payments, commerce, services, all at once, into a single daily habit. People did not already have a banking app, a food app, a messaging app. WeChat became all of those things by default, before alternatives existed, and with the added tailwind of a government-controlled internet that kept Western competitors out entirely.
Gojek succeeded in Indonesia because the ojek, the motorcycle taxi, was already culturally embedded before the app arrived. The trust existed in the physical world before the product did. Gojek layered services onto a relationship that was already habitual. Grab did something similar across Southeast Asia, starting from a core behavior people were doing every single day long before any app told them to — but here’s the secret — 95% of the volume comes from top 3 services.
Even then, truly successful super apps you can count on one hand globally. The companies that tried to copy the model without those underlying conditions mostly burned through capital trying to manufacture the kind of habitual daily use that only comes organically, from solving one problem so completely that people cannot imagine their day without you.
We were trying to do it in Bangladesh, a market of 170 million people that sounds enormous until a French investor over breakfast in Singapore asks you how many of them can actually spend money on your service regularly. The honest answer is around five million. That is your real addressable market, the people who use ride-hailing daily, order food delivery multiple times a week, and have the disposable income to make those habits stick. Five million people. Smaller than the city of Singapore.
And here is the painful irony. Once you understand the addressable market is that narrow, you also understand why you were tempted to build ten verticals in the first place. Because no single product, in a market that size, will ever build a company worth building on its own. You need to stack revenue streams just to survive.
The Conglomerate Lesson Bangladesh Already Knew
The old money in Bangladesh figured this out decades before startups arrived, and they did it without ever calling it a super app.
Look at Bashundhara Group. Cement. Paper. LPG. Real estate. Media. Food. Steel. They are in everything, and that is not an accident or a lack of strategic focus. It is the only rational response to building in a small market. You diversify because any single industry has a ceiling that arrives too quickly. You spread across sectors not to become everything to everyone, but to pool operational resources, shared distribution, shared brand equity, shared management bandwidth, so that each business line does not have to carry the full overhead of running entirely alone.
Pran-RFL is the same story. They manufacture food products, plastic goods, beverages, garments, agro-processing. They export to over 140 countries. The multi-vertical structure was never their weakness. It was always the point. The shared physical infrastructure, the factories, the supply chains, the distribution networks, that is what makes each individual business viable at a scale a standalone company in Bangladesh could never reach on its own.
A conglomerate is, in its own way, a super app. Shared resources. Multiple revenue lines. One holding structure. But here is the crucial distinction that Pathao missed and Bashundhara never confused: conglomerates never told their customers that the reason to engage with them was because they did everything. Bashundhara did not build a single consumer-facing app and ask you to buy cement, order food, read their newspaper, and pay your electricity bill all in one place. They built businesses that happened to share infrastructure on the back end, while presenting each product to the market on its own terms.
We were trying to do the opposite. We were trying to tell users: come to the Pathao app because we do everything. And what users heard was: we’re not sure what we are anymore.
The super app strategy only works when your users have a reason to live inside your product all day. WeChat earned that because it owned social communication first. In Bangladesh, Pathao earned something real too: the daily commute. That is a meaningful relationship. It is not an all-day relationship. And trying to turn a rides relationship into an everything relationship, through health features and streaming content and services people could get elsewhere with two taps, is not strategy. It is wishful thinking dressed up in a board deck.
The Push and Pull No One Prepares You For
So here is the genuine tension that every founder building in a small market eventually hits.
On one side: the market is too small for a single-product company to justify the capital required to build it properly. You need multiple products to hit numbers that satisfy investors, attract senior talent, and give you enough runway to survive the inevitable hard stretches.
On the other side: if you spread across too many verticals without real traction in each one, you end up with a bloated product that confuses users, drains engineering focus, and creates the illusion of a company while the core slowly weakens underneath all the noise.
Both things are true at the same time. And there is no clean resolution. What you are really doing is managing the tension.
The mistake we made was chasing the super app narrative rather than the super app economics. We added verticals because investors liked the story, because Gojek’s valuation kept climbing, because building felt like momentum. We did not ask, for each new vertical, whether we had a genuine right to win in that space. Health required clinical depth we did not have. TV required content production we could not afford to do properly. We launched them anyway, because momentum is seductive, and standing still feels like dying.
What Actually Works: Build Sharp Here, Expand Everywhere
Spotify was founded in Sweden. Population: ten million people. A market so small that by the logic of the super app believers, it should never have produced a global company worth hundreds of billions of dollars.
What Spotify did instead of expanding verticals was obsessively deepen the one thing it had. They did not launch Spotify Health or Spotify TV or Spotify Rides. For years they built a single music streaming experience and they built it until it was so frictionless, so genuinely better than every alternative, that the product itself became the argument for using it. When they finally moved into podcasts, the criticism was loud and immediate. Investors questioned the logic. Journalists wrote about scope creep. Even internally, the move was contested.
But the expansion held because Spotify applied a test that most founders skip: is the user habit the same? Music and podcasts are both about listening. You open the app, put something in your ears, and move through your day. The behavior did not change. The content did. That is an adjacent expansion that reinforces the core relationship rather than replacing it with a new one.
When Spotify eventually moved into audiobooks, same test, same answer. Listening is listening. The habit transferred.
Compare that to Pathao TV. Watching video and booking a motorcycle ride are not the same habit. The user who opens the Pathao app has a specific, time-pressured intention: I need to get somewhere. Putting a content tab in that context is not expanding the relationship. It is confusing it. The user who wants to watch TV is not the same user who needs a bike in eight minutes, and designing a product that tries to serve both in the same moment, in the same app session, is designing a product that does neither well.
The question before any expansion is not “do we have the technical capability to build this?” The question is: “is the underlying user habit identical, or are we asking users to change how they relate to us entirely?” If the answer is the latter, you are not deepening your product. You are starting a new one inside the same app and calling it a strategy.
The real model for small-market founders is more specific still. Use a small market as a laboratory. Build something that the market’s low competition and low operating costs allow you to test and refine without burning through capital fighting well-funded incumbents. Get genuinely good at it. Make it sharp. Make it operationally excellent. And then expand geographically, not into more features, but into more markets where the same product meets the same core habit.
Nepal was our proof of this. We did not take Pathao TV to Kathmandu. We did not take Pathao Health. We took the one thing we actually knew how to operate, bike-based ride-hailing, and we dropped it into a city that looked like Dhaka three years earlier. Narrow roads, gridlocked traffic, a bike culture already embedded in daily life, and no well-funded competitor in sight.
The first few weeks were electric. We had made history, the first Bangladeshi startup to cross a border and set up internationally. Then the taxi cartel found out about us. Thirty drivers surrounded our office while our employees were still inside. They threw rocks through the windows. They followed our riders and rammed their bikes with taxis to make them feel unsafe. Some riders quit out of fear. Some of our own staff handed in their notice.
We could not fight this battle the way we had fought regulatory battles in Dhaka. There, we knew the players, the ministries, the press contacts, the political angles. In Kathmandu we were outsiders. Bangladeshis in a Nepali market, seen as interlopers. If we tried to handle it ourselves we would get crushed.
So we stepped back and let the Nepali team lead. They went to the media, to influencers, to politicians. They framed Pathao as a solution to Kathmandu’s transportation chaos, as employment for young people, as a public good the city needed. The cartel’s intimidation became a story about powerful incumbents trying to strangle competition. The narrative flipped. More riders signed up. More users ditched taxis for bikes. We won.
And what made that possible was precisely the fact that we had not tried to bring ten products into a foreign market. We had brought one product that we understood completely, that we had stress-tested in Dhaka for years, that we knew how to operate under pressure and in chaos and against hostile incumbents. The focus that the multi-vertical strategy had robbed us of in Bangladesh was exactly what saved us in Nepal.
What the Sprawl Actually Cost
I want to be honest about this because founders tend to nod along to the lesson about focus without really feeling the weight of what unfocused expansion costs. The money spent building things nobody uses is visible. The cost underneath it is harder to see.
When Pathao was running ten verticals, our best engineers were not working on making rides better. They were distributed across health features nobody opened, content infrastructure that served no one, and partner integrations that should never have been priorities in the first place. Every sprint, product managers who each believed their vertical was the most urgent thing in the company competed for the same engineering hours. They were not wrong individually. They were collectively producing a company that excelled at nothing.
The core rides product, the thing that had gotten us to a hundred thousand rides a day, the thing users actually loved and depended on and talked about, stopped getting the attention it deserved. Bugs that should have been fixed in a week sat for a month. Features that would have meaningfully improved the booking experience got pushed down the backlog in favor of Pathao TV integrations that served a user base of nearly zero.
And while we were distracted, the competition was not standing still. Every sprint we spent building something nobody asked for was a sprint we did not spend making sure a user who had a bad experience would give us another chance.
That is what unfocused expansion actually costs. Not just the money spent building the wrong thing. The compounded cost of the right thing not getting better, month after month, while the roadmap kept growing and the focus kept fracturing and the users who mattered most quietly started looking at what else was available.
The road has to lead somewhere. Not ten places. Somewhere. Build until your answer to “what are you?” is so clear and undeniable that no investor, no competitor, no internal meeting can muddy it. Then ask what comes next.