How Talabat actually grew this fast and what it means for the next era of app growth

How Talabat actually grew this fast and what it means for the next era of app growth

Mulenga Agley
Contents
  1. 1. The Compounding Timeline Behind The Headline Growth
  2. 2. Localisation Is Not Translation, It Is Unit Economics
  3. 3. Why Acquisitions Mattered Operationally, Not Just Financially
  4. 4. Partner Density As Distribution
  5. 5. Grocery Was A Frequency Decision
  6. 6. The Revenue Curve Shows What The Machine Is Capable Of
  7. 7. Power Users Tell You What The Product Should Become
  8. 8. What The Next Era Of App Growth Will Reward

The compounding timeline behind the headline growth

Talabat looks inevitable now, but the speed comes from a timeline where each move made the next one cheaper. It starts with being early in 2004. That was before "food delivery apps" were a category people described with any confidence. The real advantage was not novelty, it was habit formation. When you are early in a marketplace, you get to teach customers and suppliers what "normal" looks like, from how menus are presented to how reliable delivery should be. The second inflection is 2012, when Talabat expanded across Bahrain, the UAE, and Oman, then continued entering additional Middle East markets. Expansion is often described like a rollout. In reality, expansion is product development with a different postcode. If you win one city by building density and reliability, you get a template, but you do not get copy paste growth because payment habits, peak times, cuisine mix, and customer support expectations all change conversion and repeat. Then you see the capital and platform leverage phases. Talabat was acquired for $170M in 2015 by Rocket Internet, and then acquired again in 2016 by Delivery Hero. Those are not trivia points. They signal that the flywheel was already working, and that the next constraint was scale execution, not demand generation. Finally, 2019 is where the curve changes again with the launch of grocery delivery. The CEO, Tomaso Rodriguez, has spoken about arriving in Dubai in 2019 because he saw "raw diamond" potential. Grocery is not a side category. It is an attempt to change ordering frequency, basket size, and the set of moments when the app is the default. If you want a modern analogue, it is not "be first". It is being first to make a specific behaviour feel normal in a region, demographic, or occasion, then compounding that with disciplined expansion and an operational playbook.

Localisation is not translation, it is unit economics

Most teams underestimate localisation because they treat it as brand work. In hyper local categories like food and grocery, localisation is a retention and margin strategy. It changes how many sessions convert, how often people reorder, how many issues end up in customer support, and whether riders and partners can operate efficiently during peaks. Talabat's 2012 expansion across Bahrain, the UAE, and Oman is useful precisely because it forces the question. What is the default payment method in a given market, card, cash, wallet? What are the culturally normal meal times and weekend peaks? What cuisines are high frequency and what cuisines are special occasion? Even support tone matters because it affects whether a late order becomes a refund, a churn event, or a solved moment that builds trust. The practical mechanism is to treat each market like a product line with its own performance baseline. Your best growth teams run market level experimentation that touches acquisition and product. That means market specific home feeds, search ranking tuned to local intent, offers designed around peak congestion, and partner tool prompts that reflect what that market's restaurants actually struggle with. A simple tactic we see work in multi market apps is to operationalise localisation through feature flags and holdouts. You can ship a home feed layout that prioritises late night convenience in one city, while another city weights family bundles and scheduled delivery, then measure order value, cancellations, support contacts, and next week repeat. That is localisation that moves unit economics. The punchline is that localisation is not a cost. It is one of the few levers that improves conversion and retention without permanently inflating incentives. When you get it right, growth gets cheaper because the product fits the market tightly enough that paid acquisition does less heavy lifting.

Why acquisitions mattered operationally, not just financially

The 2015 Rocket Internet acquisition for $170M, followed by Delivery Hero in 2016, is often interpreted as a simple success story. The more interesting read is operational. In marketplaces, once you have a credible path to local dominance, the bottleneck stops being "can we get users" and becomes "can we execute faster than complexity grows". A platform organisation brings repeatable playbooks. You get shared procurement, better fraud and risk tooling, a stronger performance marketing engine, and a cadence for experimentation that smaller teams struggle to maintain under constant firefighting. Consolidation in delivery is frequently about process leverage. It is the ability to roll out improvements across multiple markets and verticals without reinventing everything. This matters because at Talabat scale, the competitive battlefield moves away from UI polish and towards reliability and cost control. You are managing courier supply, surge, peak forecasting, and partner performance, while also maintaining a customer promise. Those are systems problems. Being part of a larger group can help build the machine that keeps service quality stable while volume grows. One practical thing founders can copy here is to treat operational excellence as a growth surface area. If you can reduce late deliveries, improve accurate ETAs, and handle issues proactively, you are effectively buying retention without spending more on discounts. Reliability becomes a marketing channel because the user does not "decide" each time, they default. The acquisition chapter is a reminder. At some point, the winning move is not another campaign. It is building an organisation and toolchain that can repeat a high quality launch, improve performance quarter over quarter, and absorb new verticals without breaking the core experience.

Partner density as distribution

Talabat operates across 7 countries, Kuwait, Saudi Arabia, UAE, Qatar, Bahrain, Oman, Jordan, with 17,000+ restaurant partners. That number is not just a supply stat. It is a distribution asset. In high intent categories, supply depth reduces the need to persuade. The user opens the app because it has the highest probability of having what they want right now. This is how marketplaces quietly lower CAC over time. When the catalogue is deep, you capture demand that already exists. The conversion rate improves because people do not bounce after two minutes of scrolling and finding nothing relevant. Retention improves because choice reduces churn, even if a single restaurant disappoints. And partners become more dependent on the platform because the platform brings incremental orders at a predictable cadence. The flywheel is familiar, more partners -> more choice -> more consumers -> more orders -> more partner reliance, but the execution detail is where teams win or lose. Partner density only compounds if quality stays high. That means menu availability, accurate prep times, clean content, and realistic delivery promises. If you scale partner numbers without quality controls, the app becomes noisy, and conversion drops. A concrete tactic is to treat partner content and operations like a product funnel. You can systematically improve menu completeness, photo coverage, modifier structure, and out of stock handling, then watch the conversion impact. You can also segment partners by operational reliability and promote the reliable ones more aggressively during peaks. That improves service levels and reduces support volume, which matters as you scale. By 2022 Talabat had around 76% of order value market share in the Middle East region. At that level, the company is not just competing. It is shaping market structure, where restaurants build their operations around the platform and consumers build habits around its availability.

Grocery was a frequency decision

Talabat started grocery delivery in 2019, and that move explains a lot of what comes next. Food delivery can be frequent, but grocery is routine. The strategic point is frequency design. If you can own more occasions, you get more sessions per user, more opportunities to build trust, and more data to personalise the experience. The numbers here are telling. Groceries and retail account for around one third of total GMV, grocery is growing around 50% YoY, and grocery penetration is still roughly 2% of the total offline grocery market. That is the sweet spot for a growth machine. A material contribution today, strong growth, and massive headroom because offline behaviour is still the default. The mechanism is cross occasion utility. A user might order takeaway once or twice a week, but they might need essentials multiple times, and they might need them urgently. When the same app covers lunch at work, late night snacks, and "I need something in 20 minutes" groceries, it becomes a platform, not a single use case. What teams often miss is that multi vertical is not diversification. Done well, it lowers acquisition costs because you are acquiring a customer into a broader set of jobs to be done. It also changes retention maths because even if food lapses for a period, grocery can keep the habit alive. If you are building a marketplace now, the actionable lesson is to pick the adjacent vertical that improves frequency without breaking reliability. Vertical expansion fails when it stretches operations and degrades the core. It succeeds when it reuses the same trust, delivery capability, and local supply relationships to cover more of the user's week.

The revenue curve shows what the machine is capable of

Operational stories are easy to romanticise, so it helps to anchor on the financial trajectory. Talabat's revenue went from $1.38B in 2022 to $1.68B in 2023, a 21.5% increase, then to $2.40B in 2024, a 43.3% increase. In Q1 2025 revenue was $846M, up 34% YoY, and Q2 2025 was $982M. Last twelve months as of Aug 2025 is $3.68B, with an end 2025 projection of $3B+ annual revenue cited based on Q1 to Q2 momentum. What matters is not just the size, it is the acceleration. A marketplace that is "mature" does not usually re accelerate without a meaningful expansion in frequency, basket, or geography. The multi vertical mix is a strong candidate, with groceries and retail at around a third of GMV. Profitability is also part of the story. Adjusted EBITDA margins are around 6.7% of GMV, with a target profit margin range of 5-7%. There is also a quarterly profit figure of around $140M on a Q1 2025 basis. Delivery businesses are operationally heavy, so those numbers suggest the machine is not purely buying growth with incentives, it is moving towards a sustainable operating model. Geographically, around 84% of GMV comes from GCC markets, UAE, Kuwait, Qatar, Bahrain, Oman, with around 16% from non GCC regions, Egypt, Jordan, Iraq. That split matters because it hints where the reliable, high value base is, and where growth might be more complex but strategically necessary. The practical growth implication is to watch whether your growth is quality growth. If revenue is rising but margins are not stable, you are probably overpaying in incentives or failing to control operational costs. Talabat's reported targets imply disciplined trade offs, not just top line chasing.

Power users tell you what the product should become

One of the most revealing Talabat data points is about the top 0.1% of customers, or less. They order 120-130 times per month, more than 3 times a day, and they skew young, 18-22 years old. That is not a casual convenience use case. That is a behavioural platform with an extreme power cohort. Growth teams love average metrics because they are neat. Power user behaviour is messy, but it is where your roadmap should start. If someone is ordering three times a day, friction compounds quickly. A slow app, a confusing reorder flow, or a single bad service recovery is not a small issue, it is a daily irritation that risks breaking a habit. The mechanism here is to design for speed and trust. Reorder flows, saved baskets, smart defaults, and checkout that is effectively one tap are not nice to have. They are the difference between a habit and a choice. At this usage level, even customer support becomes product. Proactive delay handling, clear refund flows, and transparent ETAs reduce the cognitive load of ordering. There is also a long term LTV angle that too many teams ignore. If 18-22 year olds build this habit now, you are training a decade of default behaviour. That cohort will move homes, start families, change jobs, and if the app stays reliable, the habit carries. The compounding is real. A practical tactic is to identify your future power users early. Look for signals in the first week, session frequency, reorders, and category diversity, then give those users a smoother path, better personalisation, and membership options that reward consistency without destroying margin. In my experience, this is where retention becomes an unfair advantage.

What the next era of app growth will reward

Talabat's story points to where app growth is heading, and it is not a return to cheap installs. It is a shift towards distribution that is earned through reliability, coverage, and product loops that make repeat feel effortless. One data point worth noting is that Talabat's Y/Y user acquisition growth rate was reported at around 2x higher versus the previous year in Q3 2025. Even if you do not know the exact base, the directional signal is that the machine can still pull new users in, likely because the product has become the default in more moments. The next era will reward algorithmic merchandising, but only when it is grounded in operational reality. A home screen that behaves more like an intent feed, fewer searches and more contextual recommendations, only works if availability and ETAs are trustworthy. Otherwise you are just accelerating disappointment. It will also reward partner tooling. When you have 17,000+ restaurant partners, partner performance is growth. Tools that help restaurants optimise menus, plan promos, and forecast demand are not "B2B extras". They directly affect conversion, prep time accuracy, cancellations, and customer satisfaction. Onboarding will change too. Most apps still rely on a blunt first order discount. The better play is habit building in week one, getting users to set delivery preferences, save go to orders, and experience a fast reorder loop. If you can get a user to their second and third order quickly, you are no longer in acquisition mode, you are in behaviour formation. My controversial view is that the strongest delivery platforms will stop being judged as "delivery companies" at all. They will be judged as local commerce operating systems, where trust is the brand and reliability is the growth channel. The teams that keep treating growth as a media problem will keep paying for it. The teams that treat growth as compounding operational trust will keep taking share.

Book a discovery call

Want help turning your growth into something that compounds? Tell us your market and bottleneck, and we will map a practical plan you can execute.

  1. 1 ABOUT YOU
  2. 2 YOUR NEEDS
  3. 3 BOOKING
I agree to the Privacy Policy

Which of our services do you need?

Type

Size

Funding

We'll email you shortly
Prefer to call now?
USA
+1 (347) 657 3386
UK
+44 203 870 3186