The platform was ready in month four. The MVNO went live in month eleven. The seven months in between were spent almost entirely on integrations — specifically, on a number portability adapter that failed certification testing twice, and on an HLR/HSS provisioning interface with the host MNO that required three rounds of technical alignment because the MNO had upgraded its core network between specification sign-off and the testing window.
The BSS vendor was not at fault. The platform itself was functioning correctly from month four. The project manager had built the delivery plan around platform milestones. Integrations were treated as a parallel workstream that would "run in parallel." They did — until the parallel workstream became the critical path and stayed there for seven months.
This is the most common source of MVNO launch delays. It is also the least commonly anticipated at project initiation. Platform capability is visible and evaluable. Integration scope is diffuse, dependent on third parties with their own schedules, and genuinely unpleasant to scope in detail before a contract is signed. So it tends not to get scoped properly.
What actually needs to connect
An MVNO sits between the host MNO's network and its own subscribers. The BSS platform manages the subscriber relationship — billing, products, lifecycle — but it cannot operate in isolation. It needs to communicate with the MNO's network, with regulatory systems, with the MVNO's commercial platforms, and with operational infrastructure. Each connection is a discrete project.
MNO network interfaces
The most critical integration is the HLR/HSS — the database that maps each SIM to its active service profile on the host network. When a subscriber activates, changes their plan, or is suspended, the MVNO's BSS must send a provisioning instruction to the MNO's HLR/HSS and receive confirmation. This is not a simple API call. The interface uses SS7 or Diameter signaling protocols, and the MNO has its own engineering change control process. Booking a testing slot on the MNO's network engineering calendar typically takes 6 to 12 weeks after technical specification is agreed — regardless of how quickly the MVNO's side is ready.
Beyond HLR/HSS, there may be PCRF integration for data session policy management, SMS-C for message routing, and USSD gateway integration for markets where USSD-based self-service is standard. This includes most of Sub-Saharan Africa and parts of the Middle East, where USSD-based top-up and balance checks are the primary subscriber interaction channel.
Regulatory interfaces
Number portability is the wild card in most MVNO projects. In markets with mobile number portability, the MVNO must integrate with the national clearinghouse and complete certification testing before porting any subscriber numbers. Certification slots are booked through the regulatory body on its own calendar. In some markets the next available slot is 8 to 12 weeks away at any given point. In markets where number portability is relatively recent — parts of the Gulf, several African markets — the interfaces are less mature and certification processes more involved.
KYC adds another dependency. Most markets require subscriber identity verification at activation, and the technical approach varies: document upload with manual review, real-time biometric verification, or integration with national identity databases. Each provider has its own sandbox environment and certification process, and these do not run on the MVNO project's schedule.
Commercial and business systems
CRM, ERP, payment gateway, dealer management systems — these tend to be treated as lower-risk because the technology teams involved are more familiar with them. Payment gateways in particular look straightforward on paper. REST APIs, well documented. In practice, each payment provider has its own fraud rules, its own certification requirements for new merchants, and a sandbox that may behave differently from production. In markets where mobile money is the primary top-up channel — M-Pesa, Orange Money, MTN MoMo — the integration specifications and approval processes are provider-specific and cannot be assumed from prior experience with other payment systems.
Roaming
Setting up roaming requires bilateral agreements with partner networks, registration with GSMA clearing systems (TAP/NRTRDE for clearing, GRX or IPX for data transport), and live testing with a representative set of partner networks. Commercial negotiations, technical setup and testing combined take four to six months for basic roaming capability. Roaming is often deferred to post-launch to manage initial timeline risk. For MVNOs where it is material to the proposition — business-focused, diaspora-focused, or dual-SIM targeting — this is a sequencing decision with commercial consequences that should be explicit in the project plan, not implicit.
Why different integration categories fail in different ways
MNO network interfaces are usually well-documented — the MNO has done this before — but they are schedule-dependent on the MNO's engineering organisation. The MVNO cannot accelerate the MNO's internal change control process. The only mitigation is starting the technical alignment earlier than feels necessary and getting a completed specification into the MNO's queue before the overall project plan is finalised.
Regulatory integrations fail because of factors outside anyone's control: certification slot availability, interface changes made by the regulatory body, testing failures that require a fresh queue position rather than a simple re-test. Number portability failures are particularly costly because they typically block commercial launch entirely. An MVNO that cannot port numbers in cannot take subscribers from competitor networks.
Commercial integrations fail for a different reason: scope drift. The CRM integration that was "a simple data sync" becomes more complex when the data model doesn't map cleanly to BSS subscriber records, or when the required synchronisation frequency creates performance issues under load. ERP integrations follow the same pattern — financial reporting requirements that seemed clear at specification stage acquire complexity when the BSS's handling of multi-period billing cycles meets the ERP's accounting logic.
What "pre-built integration" actually means
MVNO platform vendors routinely claim large integration libraries. 200 or more pre-built integrations is common in vendor materials. Understanding what this means in practice requires asking more specific questions.
There is a real difference between:
- A connector built for a previous customer deployment, sitting in the vendor's codebase, not deployed since
- A connector actively maintained, certified against the current version of the external system, deployed in production at multiple customers
- Something the vendor is confident they can build, based on experience with similar interfaces
The first requires a scoping exercise before anyone knows if it is fit for purpose. The second can be treated as a reusable asset. The third is a custom integration project with a delivery timeline and a risk profile, regardless of how it is described in the sales conversation.
Four questions that distinguish between these categories:
- How many current production deployments does this specific connector have?
- What version of the external system's API is it certified against, and when was it last updated?
- When the external system publishes an API change, who owns the connector maintenance — the platform vendor or the customer?
- Is this connector included in the standard platform licence, or is it scoped and priced separately for each implementation?
For integrations critical to the deployment — HLR/HSS provisioning, number portability, the primary payment gateway — these questions should have specific answers before the contract is signed.
Building a timeline that reflects reality
Most MVNO project timelines are built around platform delivery milestones. The platform vendor knows their own delivery capability and quotes accordingly. Third-party integration timelines get estimated, usually optimistically.
A timeline built around integration critical paths looks different. Realistic ranges for common integration types — actual durations vary by market and provider:
- HLR/HSS provisioning interface with host MNO: 8–14 weeks from specification sign-off to confirmed testing completion, dependent on MNO engineering schedule
- Number portability certification: 10–20 weeks, dependent on regulatory body availability and first-time pass rate
- Primary payment gateway: 4–8 weeks from sandbox access to production certification
- Roaming setup (basic bilateral capability): 16–24 weeks from commercial agreement to live testing
- KYC integration: 4–10 weeks, heavily provider and market dependent
A project manager working toward a 6-month launch needs to verify at planning stage that the HLR/HSS testing window can be booked within weeks 6–10, that number portability certification can be completed before month 5, and that no roaming capability is required at launch. If any of those assumptions don't hold, the timeline doesn't hold either.
Integration due diligence before project start
These are the questions that surface integration risk before a delivery commitment is made:
On the MNO side:
- What is the typical lead time from technical specification agreement to testing window availability on your HLR/HSS?
- Are any core network upgrades planned during the implementation period?
On regulatory interfaces:
- What is the current wait time for a number portability certification slot in this market?
- Has the regulatory body made interface changes in the past 18 months?
On the platform vendor's integration library:
- For each critical integration in this deployment, how many current production instances does the connector have?
- Which integrations require custom development, and what does that add to the delivery timeline?
On roaming:
- Is basic roaming capability required at commercial launch, or can it follow within three to six months?
- Who manages the GSMA clearing registration and bilateral agreement process?
How Avante MVNx Suite addresses this
Avante MVNx Suite includes a library of pre-built connectors covering MNO network interfaces, number portability adapters across multiple markets, payment and mobile money gateways, and roaming clearing integrations. Avante's implementation methodology includes an integration scoping phase before project planning is finalised — to identify which connectors are reusable from prior deployments and which require custom development, and to build timelines that reflect third-party schedule dependencies rather than platform-only milestones. The connectors in MVNx Suite's integration library represent active deployments across more than 20 operator environments, not historical one-off implementations.
FAQ
Why do MVNO integrations take longer than the project plan says they will?
Usually a combination of three things. Third-party schedules that the project cannot control — the MNO's engineering queue, the regulatory body's certification calendar, the payment provider's merchant approval process. Specification gaps that only become visible when the actual system interfaces are examined. And first-time certification failures, which reset queue position rather than allowing an immediate retry. Each of these is predictable in the abstract and still manages to catch projects off-guard in practice.
What actually distinguishes a pre-built connector from a custom integration?
A genuine pre-built connector has been deployed in production before, is maintained by the platform vendor against the current API version of the external system, and can be configured for a new deployment rather than re-developed. A custom integration starts from code that has not been deployed in that context — which means the development, testing, and certification cycle runs on the project's timeline. The practical difference in delivery time is usually 4–8 weeks for a configured connector versus 8–20 weeks for a custom build.
What is the single most effective way to reduce integration risk before project start?
Start the MNO interface alignment and number portability certification enquiry before the platform contract is signed. Both of these are long-lead items with third-party schedule dependencies, and finding out the next available certification slot is 14 weeks away is useful information before project commitments are made, not after.