Digital platforms / Ooredoo Maldives
Ooredoo SuperApp
Bringing telecoms, payments and commerce into one product.
- The problem
- Coordinate several service domains, vendors and customer journeys.
- My contribution
- Vendor coordination, requirements, CI/CD and controlled releases.
- The outcome
- 10+ customer journeys delivered on an app with 1M+ Google Play downloads.
In this case study
Overview
Ooredoo SuperApp brings telecoms, financial services and e-commerce into a shared customer experience. My work focused on coordinating the delivery effort and moving product improvements through recurring releases.
My role
I coordinate requirements, vendors and platform integrations, with 10+ customer journeys delivered across telecoms, payments, loyalty, eSIM, autopay, gamification and localisation. I set up CI/CD release workflows and use controlled rollouts and A/B testing for selected changes. The app is delivered with Ooredoo teams and partners; my contribution is part of that shared effort.
Problem
Combining several service domains in one app creates dependencies across teams, vendors and customer journeys. Delivery had to keep those pieces aligned while introducing features and enhancements to an existing product.
Approach
Coordinate across vendors
Worked with multiple vendors on the telecoms, financial-services and e-commerce integrations, managing milestones across the delivery effort.
Make releases repeatable
Set up CI/CD release workflows and use controlled deployment and A/B testing for selected changes, working through technical dependencies, testing and rollout to reduce release risk and customer disruption.
Connect personalisation touchpoints
My related Digital CVM work integrated the CVM engine into the SuperApp and USSD channels. That work connected personalised offers to customer-facing touchpoints.
System
Several service domains. One shared customer experience.
Ooredoo SuperApp
Many services.
One familiar place.
Challenges
Shared dependencies
An app journey can depend on several service teams. Vendor coordination and milestone management were central to my contribution, alongside the work of the teams implementing each service.
Attributing product impact
The app's reach reflects the combined product and organisation. Downloads are a product-level measure, not a count of active users or an outcome attributable to one contributor.
Outcome
Delivered 10+ customer journeys and introduced CI/CD release workflows, with controlled rollouts and A/B testing for selected changes. My work combines vendor coordination, requirements, testing and production readiness alongside Ooredoo teams and delivery partners.
Product reach & release context
- 1M+App Downloads
- Product-level Google Play downloads reported in the updated CV. Downloads are not unique or active users, and the reporting date is not specified.
- 10+Customer journeys delivered
- CV-reported delivery across telecoms, payments, loyalty, eSIM, autopay, gamification, localisation and related capabilities. This counts customer journeys, not separate platforms or apps.
Source: Yoosuf Sayyid’s CV, selected technical and delivery projects. Figures are self-reported; no independent benchmark or analytics report is linked.
Technology
- Telecom service integrations
- Financial services
- E-commerce
- Digital CVM
- USSD
- CI/CD
- Controlled rollouts
- A/B testing
Integration domains and touchpoints documented in the CV. The ecosystem diagram describes product relationships, not the app's private infrastructure or service topology.