Software Product Development for MasMovil Group
Project Overview
Location
Spain, Ukraine
Industries
Expertise
High Load Systems
Cloud Solutions
DevOps
CRM
Microservices Architecture
OSS/BSS Vendor Integration
Multi-brand Platform Unification
Team
15 people
Technologies
Scala
Java
JavaScript, React
GCP
About The Project
Background
MasMovil was one of Spain's largest telecommunications operators at the time of this engagement, with mobile, fixed-line, and internet services covering more than 90% of the country across residential, business, and wholesale segments. The group ran multiple consumer brands — including Yoigo, MasMovil, Pepephone, Lebara, and others — each on partially separate infrastructure, which created integration debt across CRM, billing, and customer experience layers.
What Masmovil Needed
MasMovil needed to unify its brand portfolio under a single customer-facing architecture to enable cross-selling, simplify support operations, and consolidate document and contract management. The engagement scope for Bluepes included extending the document management system across brands and hardening the security perimeter of the new shared infrastructure.
Project Goals
The engagement focused on helping the in-house team unify operations across the group's different brands. The two priority outcomes were a consolidated document management system and full visibility into customers and product availability across brands, both required to enable cross-selling. The Bluepes dedicated team covered the areas listed below.
Microservices Architecture
Extend the Microservices Architecture to integrate the new User Interface with several new products and the core back-office.
Secure Infrastructure
Create a production-grade infrastructure with continuous integration, replication, and monitoring.
Integration
Integration of the Java apps with Maven, Docker, and CircleCI.
More
Multi-cloud strategy evaluation.
Application deployment to Kubernetes with Helm Architecture.
Full-cycle development of the new UI with React.
Development of UI with JavaScript (React).
Improving performance and extending the core app with Scala.
Unification and simplification of the Content Management System with several third-party tools.
Why telecom integration projects look like this
Multi-brand operators
Telecom groups built through M&A typically inherit fragmented CRMs, separate billing logic, and per-brand catalogs.
- Manual cross-selling across brands
- No unified customer view
- Per-brand work for every product launch
- Inconsistent support experience
Vendor BSS/OSS extensions
Standard configuration of platforms like QVantel, Amdocs, or Netcracker covers the core, but rarely fits operator-specific business logic.
- Catalog logic outgrowing platform limits
- Custom event models needed for charging
- CI/CD cadence faster than vendor releases
- Integration glue for non-standard data flows
Carrier-grade engineering
Telecom platforms have constraints that generic enterprise software does not — and ignoring them creates expensive incidents.
- High-throughput CDR processing
- Idempotency for prepaid/postpaid charging
- Lawful interception and audit requirements
- Multi-region failover and replication
Our Solutions
The Solution: One-Stop IT Outsourcing
The main concern for Bluepes was to create a working environment where disparate teams could integrate easily. With a good flow of communication, the Bluepes team could minimize the impact on in-house teams. Another important benchmark was for Bluepes to become a multi-faceted partner and provide a wide range of high-quality services for all of Masmovil's needs. Bluepes seamlessly integrated its many on-site and off-site hubs throughout Spain, Ukraine and Finland to establish better collaboration as well as more effective management.
DevOps Dedicated Team
Bluepes combined on-site and off-site developers into a dedicated DevOps team focused on infrastructure modernization. The team began by auditing the existing cloud setup, then deployed the new application stack on Kubernetes with Helm Architecture, with continuous integration and replication built in from the start.
The Core Team
The core product team combined Java, React, and Node.js developers working closely with the in-house UX team to modernize and extend the CRM and improve customer visibility across MasMovil's brands. The two teams worked on simplifying contract storage and invoice processing across brands, and on building a unified customer profile that supported cross-selling without forcing each brand into a single product catalog. The final architecture used microservices to give the front-end flexibility per brand while keeping the back-end on a production-grade CI/CD pipeline. The team worked with Java Spring WebFlux, vert.x, Maven, Docker, and CircleCI.
The Integrations Team
The Integrations Team worked directly with QVantel — the Finnish vendor whose billing platform underpins the MasMovil charging stack — to support and extend the billing integration. Pre-paid and post-paid charging operate on different latency budgets, and rating windows for 3G/4G traffic require strict idempotency in the integration layer; the team was scoped specifically around this class of problem and staffed with Scala developers experienced in carrier billing.
Projects
SuperYachtsMonaco — sale, purchase and charter of yachts of all sizes
/ e-commerce
/ project_management
/ software_development
Healthcare Platform Project Development
/ health-tech
/ fin-tech
/ healthcare
/ product development
/ software development
Software Product Development for MasMovil Group
/ telecommunication
/ product_development
/ software_development
We have completed an array of projects, each of them unique from the perspective of business logic and generally common in terms of technologies, and vice versa. Basically, there’s no possibility (and we mean no, zero, null, non c'è) chances that we’ll start a new project out of blue (pun intended).
See all