What EdTech Companies Get Wrong About MENA Expansion

What EdTech Companies Get Wrong About MENA Expansion

Education and language-learning apps should, in theory, be some of the easiest global products to bring into North Africa. The audience is young, multilingual by necessity, and already motivated to spend time and money on learning — English, French, and Arabic literacy all carry real economic value across the region. And yet a lot of edtech companies either avoid North Africa entirely or enter, stall, and quietly deprioritize it. The reasons are consistent enough to name directly.

Mistake 1: Treating “MENA” as a Single Market

Morocco, Algeria, and Tunisia are Francophone-leaning Maghreb markets with their own dialects, currencies, and telecom structures. Egypt is a much larger, Arabic-first market with a materially more developed payments and carrier-billing landscape. Libya and Mauritania are smaller and less served by almost every kind of digital infrastructure than either of the other two groups. A single “Arabic version” of a product, built once and shipped everywhere, undercounts French usage across the Maghreb and flattens differences that actually affect conversion. Treating six countries as one launch is the first mistake, and it tends to make every decision after it worse.

Mistake 2: Confusing Translation With Localization

Shipping Arabic and French strings is not the same thing as localizing a product. Arabic is a right-to-left language — a translated interface sitting inside a layout that was never built to mirror (navigation, icons, form fields, card alignment) reads as an afterthought, because it is one. Real localization means the interface direction, not just the text, respects the language. It also means content relevance: a language-learning app’s example sentences, cultural references, and even its assumed starting fluency level land differently for an Egyptian Arabic speaker than for a Moroccan French-Arabic bilingual user. Translation is a task you can outsource in a week. Localization is a product decision.

Mistake 3: Building the Checkout for a Card That Isn’t There

Most global edtech subscription flows assume a credit card. In Egypt, the region’s largest market, credit card penetration is as low as roughly 10%. Cash and cash-on-delivery dominate general commerce, and several regional currencies aren’t freely convertible against the dollar or euro — which breaks a lot of standard international billing integrations before a user ever sees a paywall. An edtech company can have real organic pull in North Africa, and plenty do, and still see subscription conversion near zero, because the payment method on offer isn’t one most interested users can actually use.

Mistake 4: Not Treating Carrier Billing and Mobile Money as the Default

This is the mistake that compounds the previous one. Regional consumers already pay for digital subscriptions routinely — just not by card. Carrier billing already moves subscription revenue at scale in the region: Anghami built its entire MENA music business on more than 35 telecom carrier-billing partnerships, Deezer entered the region through an Orange partnership in 2018, and Spotify enabled carrier billing with Orange Morocco in 2023. None of that is education-specific, but it establishes that the rail already works for recurring subscription products generally, which is exactly what most language-learning and edtech pricing looks like.

There’s a more directly relevant precedent, too. Revolut Ultra, a fintech subscription tier, currently bundles free access to a set of unrelated global consumer apps — including Duolingo — alongside Flo, NordVPN, Tinder, Headspace, MasterClass, and Chess.com, as a customer perk. That’s a third-party distribution layer moving a language-learning product to real consumers at scale, without Duolingo building that sales relationship itself. It’s a different mechanism than carrier billing, but the lesson for edtech teams is the same one: you don’t have to build the distribution and payment layer yourself for a product to reach a market at scale.

Mistake 5: Negotiating Every Telecom Relationship One at a Time

An edtech company’s core competency is content and pedagogy, not carrier commercial negotiation. Trying to strike individual billing and distribution deals with telecom operators across six different countries — six different languages, currencies, and commercial norms — is slow, and it isn’t what most edtech teams are built to do well. This is precisely the gap a distribution partner is meant to close. Clementine is built to offer a single commercial and technical relationship — the SDK, API, or white-label integration a distributor runs to bring the edtech catalogue onto its own platform, depending on that distributor’s integration appetite — designed to unlock carrier billing and mobile-money rails plus Arabic/French localization across all six markets at once, rather than requiring six separate negotiations run in-house. That’s a description of the model Clementine is built around, not a signed edtech partnership; the company has no signed clients yet in this or any category.

Mistake 6: Scheduling Localization Like a Launch-Week Task

Because payments and localization aren’t string-replacement problems, teams that budget two weeks for “MENA readiness” get burned quietly, months later, in poor retention and unclear conversion data. RTL layout work, dialect and language-variant decisions, and payment-rail integration are roadmap-level work, not a pre-launch checklist item — and treating it that way is usually what turns a promising regional entry into a deprioritized side project.

What Getting It Right Looks Like

The edtech companies that avoid these mistakes tend to do a few things differently: they plan for six markets, not one; they treat RTL and dialect handling as product work, not a translation ticket; they build or plug into carrier billing and mobile money instead of waiting on card penetration to improve; and they use a single distribution relationship instead of six bilateral ones. None of that requires abandoning a global product or its pricing model. It requires accepting that North Africa’s constraint has never really been demand for language learning and education. It has always been the rails underneath it.