Global B2C travel connectivity platform
eROAMING eSIM
eROAMING brought together customer applications, partner integrations, payments, eSIM journeys and operational systems within one international product environment. My role has involved technical architecture, programme delivery, service operation and the coordination required to move the platform from concept through launch and continued improvement.
- Coverage
- Products operating across 165+ countries
- Scope
- Concept to production
- Teams
- UK · India · Sri Lanka
Platform overview
eROAMING is a travel connectivity product: customers buy and activate eSIM-based data plans for international trips through the website and mobile applications, supported by a product catalogue, payments, customer communications and operational tooling behind the scenes.
The platform connects several moving parts — customer-facing applications, backend services, partner integrations and the admin tools that operations and support teams use every day.
The need
Travellers want mobile data abroad without physical SIM cards, roaming surprises or complicated setup. The business needed a single product environment that could sell, deliver and support eSIM connectivity internationally, while remaining operable by a real support and operations team.
My role
- CTO at eROAMING
- Technical architecture and delivery direction
- Technical programme coordination
- Platform and service operations
- Partner and integration coordination
- Continuous product improvement
Areas of responsibility
- Defining the technical approach with engineering teams and partners
- Coordinating delivery across web, mobile and backend workstreams
- Payments, onboarding and customer journey execution
- Operational readiness, escalations and service improvement
- Prioritising the roadmap with product and commercial teams
Delivery environment
- Cross-border engineering teams across the UK, India and Sri Lanka
- External technology providers and telecom partners
- Parallel workstreams: payments, onboarding, compliance, integrations
- A live customer base — changes ship into a running service
Technical & operational considerations
- eSIM journeys must work reliably for customers who are often mid-journey and time-pressed
- Payments and product catalogue changes need careful release coordination
- Partner integrations bring external dependencies into every delivery plan
- Operational and support teams need visibility, not just customers
Continuous improvement
The platform improves continuously after launch: customer feedback, support patterns and operational data feed a steady stream of product and process changes, from customer communications to internal tooling.
Key learning
An international consumer product is as much an operational system as a technical one. The architecture, the delivery plan and the support model have to be designed together — a feature is not finished until the operations team can run it.
Platform areas
- Customer website
- Mobile applications
- Customer onboarding
- eSIM journeys
- Payments
- Product catalogue
- Usage-related customer journeys
- Customer communications
- Backend services
- Partner integrations
- Admin and operational tools
- Support processes