For Distributors & Telecoms
One Relationship,
A Whole Catalogue
Telecoms, retailers, OEMs, app stores, banks and ISPs across North Africa all want the same thing: more premium global content to offer their customers, ideally as a differentiator against the operator next door. What makes that hard isn't appetite. It's that sourcing global consumer apps means negotiating with each one separately, then building the billing and localisation work per app, per market.
The sourcing problem
A single global app deal is a months-long negotiation with a company whose priorities are elsewhere and whose legal team has never heard of your market. Doing that once is expensive. Doing it a dozen times, across categories, to assemble a catalogue worth marketing to your customers, is a programme rather than a project.
Then each deal needs the same billing integration, the same entitlement handling, the same Arabic and French localisation, repeated. The cost is largely fixed per app and almost entirely repeated work.
One commercial and technical relationship
Clementine holds the publisher agreements and does the local billing and localisation work once, then makes the whole catalogue available through a single relationship. You integrate once and get whatever is in the catalogue, including what is added later.
- ▸Publisher agreements negotiated and held centrally, so you don't chase them app by app.
- ▸Billing integration against carrier billing and mobile-money rails, built per market and reused across the catalogue.
- ▸Localisation in Arabic and French with full right-to-left presentation.
- ▸Category breadth across health, education, entertainment, dating, mobility, productivity, travel, family safety and gaming, which is the mix that makes a bundle worth marketing.
Three ways to integrate
Same catalogue, same billing rails, same localisation work, with three different technical commitments, so the path can match your team rather than the other way round. The full comparison lives on the How It Works page.
- ▸Mobile SDK adds the catalogue inside your existing consumer app. Best if you already have an app and an installed base.
- ▸REST API gives you headless access to catalogue, billing and localisation so you can build your own storefront or content-club experience. Best if you have a platform team and a design system.
- ▸White-label app is a ready-to-brand iOS and Android app, pre-wired. Best if you want to launch fast, or have no existing consumer app to build on.
Why app bundling works as a telecom product
This is not a speculative product category. Bundling premium third-party subscriptions as a customer perk is an established, working model. Revolut's Ultra tier bundles free access to a dozen-plus unrelated global consumer apps across categories, which demonstrates that a third-party distribution layer can move real premium subscriptions to real consumer brands at scale without those brands building local sales infrastructure.
Regionally, the precedent is carrier billing itself. Anghami built MENA's leading music app on more than 35 telecom carrier-billing partnerships, and Orange Morocco enabled carrier billing for Spotify Premium in 2023. Operators in this region already run this kind of relationship. What has been missing is a way to run one of them and get a catalogue rather than a single app.
None of these are Clementine's deals. They are cited as third-party industry precedent.
Common questions
What does the catalogue actually contain today?+
Clementine is a new company at the pre-launch and early-partnership stage with no signed publishers. The categories described here are what the platform is built to carry, not a roster of secured titles. We would rather tell you that plainly now than describe a catalogue that doesn't exist yet.
Which integration path should we choose?+
If you already have a consumer app with an installed base, the SDK is usually the lightest route to a real in-app surface. If you have a platform team and want full control of the experience, the REST API. If you want to move quickly or have no existing app, the white-label app. See the comparison table on How It Works.
Can we start on one path and change later?+
Yes. All three are front ends onto the same catalogue and the same billing and localisation services. Launching on the white-label app and later building your own storefront on the API is a normal progression, not a re-platforming.
Which markets do you cover?+
Morocco, Algeria, Tunisia, Libya, Mauritania and Egypt. See the Markets page for operator, payments and carrier-billing-maturity detail on each.
Tell us about your business
Organisation, markets, customer base and channel. We'll come back to you on which integration path fits and what launching would involve.
Related reading
Sources
Figures on this page are drawn from the public sources below. Companies and deals referenced are cited as third-party industry precedent — none is a Clementine client, partner or completed deal.