Moving up the MVNO maturity curve

When, why and how to evaluate the Migration from Light into Full MVNO

The majority of MVNO projects start around a customer segment, a commercial idea, a distribution model or an existing asset. Those projects need to reach the market fast, without unnecessary complexity, and are typically not focused on mobile core network ownership.

This is the attractiveness of the Light MVNO model. It allows a new MVNO to launch fast, reduce upfront investment, and focus on the areas that usually matter at the beginning: its own brand, acquisition discipline, competitive pricing, customer care, channels, and retention strategy. For many MVNOs, this model is not only sufficient, but the right one for launch.

Many MVNOs will remain light for years and build a healthy business around their focused value proposition, their efficient distribution and their good commercial execution. However, as they grow, some MVNOs may initiate their analysis of a migration towards Full MVNO.

At a certain point, the same model that facilitated the fast MVNO entrance into the market may start inhibiting its growth. Product launches may take longer, margins may not improve along with business volume, B2B customers may ask for capabilities that are difficult to support, or IoT deployments may require more network control than initially expected. Due to this, MVNO’s teams start spending more and more efforts in bridging the operational constraints rather than building the next stage of their business.

This is usually the moment when the discussion about migrating from Light MVNO into Full MVNO becomes serious. When a new service offer is designed, when a new business opportunity is clear, when the team wants to move forward, but it cannot execute because too many critical capabilities are outside their direct control.

Control is the real question

The difference between Light MVNO and Full MVNO is often explained through network diagrams. While those diagrams are useful, they do not always help in making a decision on the required model. The actual question is simpler: how much control does the MVNO need to execute its strategy?

A Light MVNO normally relies on its host operator and other partners for many network-related functions. MVNO owns the customer relationship, the brand, the commercial proposition, and the customer care experience. But many service capabilities remain managed by others.

A Full MVNO still depends on the host operator’s radio access network. That dependency does not disappear; the share of responsibility is what changes. The Full MVNO takes ownership of more core functions, such as subscriber management, service logic, policy control, interconnection, routing, messaging, charging integration, security, fraud controls, and operational monitoring.

Becoming a Full MVNO is not about increasing the technological footprint, but about making a sound decision on which parts of the operating model are far too important to leave them dependent on third parties.

More control creates increased speed, more flexibility, and better economics, but it also creates accountability. So, higher MVNO control implies a wider responsibility emerging from such operational autonomy.

Why MVNOs start considering migration?

In practice, MVNOs rarely migrate because of one single reason. The business case will usually appear gradually, and as a combination of diverse factors:

• Product limitations. At launch, the MVNO may accept a standard product set because speed matters more than flexibility. Later through the growth phases more differentiated service propositions may be proposed (specific roaming bundles, family plans, enterprise controls, IoT policies, digital onboarding flows, or more flexible data products). The challenge may be whether the MVNO has the required technical capabilities to launch them at the speed the market requires.
• The Light MVNO model can be financially efficient during the early phase because it avoids heavy initial investment. But as business volumes increase, economies of scale are easier to materialize under a Full MVNO model where wholesale costs, enablement fees, support costs, and network features are under full control of the MVNO.
• Customer requirements. Business customers and IoT models typically pose additional demands. Enterprise customers may require private APNs, specific routing policies, stronger reporting, security controls, service-level visibility, and faster support escalation. IoT customers may require large-scale SIM lifecycle management, roaming control, device behavior monitoring, automation, and stronger fraud prevention. All these requirements can seldom be supported in a Light MVNO model with the speed, granularity, or autonomy required by the business.

When a combination of these factors becomes an obstacle to continued MVNO growth, then migration into a Full MVNO architecture becomes a strategic decision rather than a technological consideration.

When is the right time?

There is not a universal subscriber volume to trigger the consideration of becoming a Full MVNO. The threshold that makes sense in one market or segment might be irrelevant in another. The right timing depends on the MVNO’s commercial model, target segment, wholesale agreement terms, internal operational capabilities, relationship with its host MNO, local regulatory context, and ultimately the MVNO’s long-term business ambition.

A Full MVNO is not automatically better than a Light MVNO. It becomes better only if and when the additional control the MVNO gains will solve real operational challenges and when the organization is ready to manage the associated additional responsibility.

Some practical questions may help the MVNO leaders in the decision process:

• Are product launches repeatedly delayed because key capabilities are outside our control?
• Are wholesale or platform economics limiting our ability to profitably scale?
• Do our customers require network-level controls or features that we cannot properly offer today?
• Is our dependency on external third parties becoming a strategic risk or a hinder for growth?
• Are we ready to step up and autonomously operate our critical services on a 24/7 basis?

If the answer is “yes” to several of these questions, the migration into Full MVNO deserves a serious evaluation.

Sometimes the answer will be to renegotiate with the host MNO, improve processes, change third party partners, or add selected capabilities without becoming fully autonomous. In other cases, the conclusion of the analysis will be that the MVNO has outgrown the model that helped it get started and it needs to be evolved.

Launching as Full MVNO from day one

It is also important to acknowledge that migration is not always necessary. In some cases, launching as a Full MVNO from day one may be the better strategic choice.

An operator entering the market with a strong investment plan, a clearly defined addressable market, a solid wholesale agreement, and the operational capabilities to manage its own core network will gain little from first operating under a Light MVNO model and considering a later migration.

If network control, service differentiation, enterprise or IoT capabilities, or greater commercial autonomy are fundamental to the business case from the outset, building the right level of Full MVNO capability from the beginning avoids a later migration and gives the business more control over how it develops from the beginning.

This approach is not suitable for every new entrant. It requires higher upfront investment, stronger technical and operational readiness, and a clear strategic view of the target operating model. But when the business case already depends on autonomy, starting as a Full MVNO is more coherent than launching light and redesigning the operating model later.

Readiness needs to be assessed

From an initial perspective, migration into Full MVNO may look like another network architecture project, but the reality is that it will radically change how the MVNO operates. Accordingly, MVNO organizational readiness is extremely important.

Most of the technical components required for a Full MVNO are well known in our community: subscriber control databases, signaling, gateways, policy functions, messaging platforms, interconnection, monitoring, security and fraud controls, and BSS/OSS integration. The harder question is to assess whether the MVNO can properly operate all these components.

Before initiating a migration, the MVNO should be clear about what it wants to own on day one and what should remain with partners. Trying to own everything immediately can create unnecessary risk. A more practical approach is to define the minimum viable level of autonomy required to support the business case and then expand over time.

Assessment of operational readiness should include:

• Provisioning and activation processes
• Service assurance and monitoring
• Charging and billing reconciliation
• Fraud detection and security controls
• Incident response and escalation
• Interconnect and routing governance
• BSS/OSS integration
• Regulatory and compliance obligations
• Internal skills and vendor management

All these topics usually determine the success of the migration. The Full MVNO model will give more flexibility, but such flexibility will only be useful if the organization can leverage it.

How to migrate in a controlled manner

The best migrations are usually smooth. MVNO’s customers should not even notice that the operating model behind the service is being changed. They should not need to call into customer care, nor see billing errors or, even worse, experience service disruptions. Migration should be transparent and this can be ensured following some practical considerations:

• No big-bang approach. A phased migration allows the MVNO to test systems, processes, partners, and people under controlled conditions. It will also give the organization time to learn. Starting with the definition of the target operating model and which functions the MVNO will own versus which ones will remain outsourced, the project will deploy and integrate the required new platforms while the existing operations continue.
• Migration tests should be conducted with a limited customer group, typically excluding the most complex customers and/or the most strategic enterprise accounts. Migration will initiate with a manageable customer segment thus allowing the team to validate and tune the new operational processes.
• Customer migration can be completed in batches after the tests, triggering a period of parallel run to ensure that reconciliation criteria are met. MVNO should compare expected and actual results across customer status, usage, charging, billing, service availability, and incident behavior.
• A good migration plan should also include rollback procedures as the key objective is to migrate safely.

Final thoughts

Moving from Light to Full MVNO is not something every operator needs to do. For many MVNOs, staying light will remain the best decision. It can be simpler, more efficient, and fully aligned with their business model. However, other MVNOs may conclude that a Light MVNO model becomes a hinder limiting their business growth.

Signs may typically be identified well before a decision is required: slower service launches, pressure on commercial margins, limited differentiation, requirements from B2B or IoT customers that cannot be supported, and too much dependency on external third party priorities.

The best migrations are not the most ambitious ones but those where the MVNO knows exactly why it is migrating, what additional control it needs, how ready its team is to undertake operation, and what should still remain with partners. Further, carefully planned and phased execution of the migration project is recommended.

A Full MVNO model gives more autonomy which must be turned into better operation, stronger customer propositions, and an overall more resilient MVNO business.