How to launch an MVNO in 2026: stage-by-stage guide and checklist

An MVNO launch runs in five stages and takes 16 to 26 weeks from a signed host agreement to commercial launch. The calendar is set by the host operator, the regulator and the porting clearinghouse rather than by the software, which is why launches that bought perfectly good platforms still miss their dates. Settle the operating model first, Light, Medium or Full, because it decides every integration downstream.

GSMA Intelligence counted 2,138 MVNOs in operation worldwide in August 2025 and a further 283 expected (November 2025). A good share of those 283 have a board paper that says “launch in six months”. Some will make it. Most of the ones that do not will have bought perfectly good software and still missed the date, because the calendar of an MVNO launch is set by a host operator, a regulator and a porting clearinghouse, none of which report to the project manager. What follows is the sequence of stages as they actually run, who owns each piece, where the slips come from, and what to settle before you sign the host agreement.

Decide the operating model before anything else

The first decision is not which platform to buy but how much of the operator you intend to be. A Reseller or Light MVNO owns the brand and the customer relationship while the host or an enabler runs SIM management, HLR/HSS, rating and billing. A Medium MVNO runs its own BSS (product catalogue, online charging, billing, CRM, self-care) and connects to the host’s network through provisioning, charging and mediation interfaces. A Full MVNO adds the network layer: its own HLR/HSS or subscriber data management, its own packet core or gateways, its own numbering, interconnect and roaming agreements.

Each step up adds control and adds months. It also changes the launch plan in kind, not only in degree. A Light launch on an enabler is mostly a commercial and marketing project. A Medium launch is an integration project. A Full launch is a network build with an integration project attached. Everything below describes the Medium case, with notes on where Full differs, because Medium is where most banks, retailers and ISPs with a real product idea end up. The comparison of who owns what in each model is on the operating models page.

A view, since the evidence supports one: if your proposition is a standard SIM with branded packaging and a few bundles, go Light on an enabler and read no further than the checklist. If the pricing logic is the product (loyalty-linked data, balance-based rewards, sponsored usage, B2B limits), you need your own catalogue and charging engine, and the rest of this guide applies to you.

The five stages, in order

The stages below are the ones Avante uses to plan a launch. Durations are planning assumptions for a Medium MVNO taken from delivered projects. Stages overlap, which is how sixteen to twenty-six weeks of work becomes four to six months of elapsed time.

1. Discovery (2 to 3 weeks). Fix the target model, the launch segments and the opening offers, the service model (digital-only, retail, agent network) and the target IT estate. Scope every integration by name. The output is an MVP scope, a responsibility matrix, a critical path and a preliminary business case. Discovery is short because its job is to decide, not to design.

2. Host agreement and legal framework (the critical path). Wholesale terms, coverage commitments, interface specifications and SLAs with the host; numbering; SIM supply; licence or registration; regulatory approvals. This track belongs to you, the host and the regulator. The BSS vendor’s job here is the technical annex, the interface requirements and getting the host’s engineering team talking as early as the host allows. Nobody can tell you how long this stage takes, because it depends on the host’s commercial appetite and the regulator’s calendar. Everything else in the plan is dated from the day it closes.

3. BSS platform (4 to 8 weeks). Deployment in the environment you chose (your own perimeter, a private cloud or a managed service), configuration of the catalogue and charging rules for the opening offers, and a working test environment. This is the most predictable stage in the plan. It is also the one vendors advertise, which is why buyers sometimes mistake it for the whole project.

4. Integrations (6 to 12 weeks). Host interfaces for provisioning, charging, mediation and SIM or eSIM; number portability certification; KYC or SIM registration; payment and mobile-money gateways; your own app, CRM and data platform; roaming, if you insist on it at launch. This stage runs partly in parallel with stage 3 and is where the elapsed time is decided.

5. Launch (2 to 4 weeks). A pilot with a limited group, then friends and family, then commercial start. Hypercare for the first weeks, and managed operations from day one if you have contracted them. Do not compress this stage to recover time lost in stage 2. The pilot exists to find the provisioning edge cases that the test environment did not.

A Full MVNO runs the same five stages with a longer stage 4 and additional workstreams for the core elements, and plans at eight to ten months. The reasoning behind the sequence, and why integrations rather than software set the pace, is in the integration and launch timeline article.

Who owns which integration

An MVNO launch has four parties doing technical work: the MVNO itself, the host operator, the BSS vendor (or enabler) and a set of third parties, each with a calendar of their own. Confusion over who owns a piece is the most common cause of a quiet month in the plan. The table shows the split used for a Medium MVNO.

In RACI terms the picture fits in one paragraph. The MVNO is accountable for everything and responsible for the commercial, legal and regulatory tracks: the proposition, the host agreement, the licence, the third-party contracts and, after launch, the operation or the decision to delegate it. The BSS vendor is responsible for the platform and for every technical integration that touches it, certification included, and is consulted on the technical annex and the business case. The host is responsible for its own interfaces and test environments and is consulted on wholesale inputs; it is not accountable for your date and will not behave as if it were. The regulator decides and is informed; it is never on the project’s calendar. Third parties (KYC, payments, clearinghouse, roaming sponsor) are responsible for their piece and informed of the plan. Write this down in Discovery. Half the disputes in month four are about a line in this paragraph.

Five integration risks

Platform milestones are visible and can be checked weekly. Integrations depend on third parties. The ranges below come from delivered projects rather than from a brochure, and actual durations vary by market and provider.

The first risk is the host’s provisioning interface. From specification sign-off to confirmed testing the plan allows eight to fourteen weeks, and the range is set by the host’s engineering schedule and change control, not by yours. A host that has never had an MVNO tenant has no interface document to hand you, and a host planning a core upgrade will freeze changes for months. Ask both questions before the agreement is signed.

The second is number portability certification, at ten to twenty weeks. The clearinghouse or the regulator runs a certification calendar, and a failed first attempt puts you back in the queue. It helps to know that the next slot is fourteen weeks away before the board commits to a date. This is one of two items Avante starts before the platform contract is signed.

The third is the primary payment gateway, at four to eight weeks from sandbox to production. The delays here are merchant approval, fraud rules and certification, which are procedural rather than technical. Mobile-money integrations in African markets add operator-side approvals with timelines of their own.

The fourth is KYC and SIM registration, at four to ten weeks. The range depends on the method the market requires: document upload, biometric capture or a check against a national identity database. A digital-only MVNO lives or dies on this flow, so test it with real customers in the pilot, not only with test identities.

The fifth is roaming. Basic bilateral roaming takes sixteen to twenty-four weeks from commercial agreement to live testing, through bilateral agreements and GSMA clearing registration. Most launches defer it. If your proposition needs roaming on day one (a bank serving frequent travellers, say), plan the launch around it or use a sponsored roaming or multi-IMSI arrangement through the host or a sponsor.

Checklist before you sign the host agreement

The host agreement is the document the whole plan hangs from. These are the points to have settled, or at least written down as open, before signature.

• Wholesale pricing structure: per-unit, bundle or capacity-based, with volume tiers and the review mechanism named.
• Coverage and technology commitments: which network generations, whether VoLTE and eSIM are included from day one.
• Interface specifications attached as a technical annex: provisioning, charging or CDR feeds, SIM and eSIM lifecycle, with test environment access and a named engineering contact.
• The host’s change-control process and any planned core upgrades in the next twelve months.
• Whether the host has hosted an MVNO before, and whether an existing interface can be reused.
• Numbering: who holds the range, and how numbers are allocated and returned.
• SIM supply: who orders, who profiles, who pays, and how eSIM profiles are provisioned.
• Number portability: who is the porting party of record, and how port-in and port-out costs are shared.
• Data access: which subscriber and usage data you receive, in what format, how often, and who owns it.
• Priority, SLA and service credits, with the escalation path for outages that affect your customers.
• Lawful interception and regulatory reporting: what the host does, what you must do, and what the regulator expects from each.
• Roaming: whether the host’s agreements extend to you, on what terms, and when.
• Exit: minimum term, notice period, and what happens to numbers, SIMs and data when you leave or add a second host.
• Regulatory prerequisites: licence or registration category, timelines, and whether the host requires them before signing.
• Your BSS vendor’s review of the technical annex, so the interfaces you are promised are the ones the platform will integrate with.

None of this is exotic. It is simply that the commercial team signing the agreement and the technical team living with it are rarely in the same room. Put them there.

Regulatory notes for four markets

Regulation does not change the five stages, but it changes the length of stage 2 and the content of stage 4. Four examples that come up most often with readers in Africa and Europe. Each deserves a guide of its own; the notes here are what a launch plan needs to know.

South Africa: RICA and portability

The Regulation of Interception of Communications and Provision of Communication-related Information Act (RICA) requires a subscriber’s full name, identity number, address and MSISDN to be captured before activation, and an eSIM is treated as a SIM for these purposes (De Rebus, September 2025). Self-registration in an app is now standard practice: Pick n Pay Mobile relaunched in July 2025 with instant eSIM and self-RICA (TechCentral). Number portability regulations came into effect on 7 March 2022 (Bowmans), so MNP certification sits on your critical path. The hosting market is unusually developed. TechCentral counted 23 MVNOs in June 2025, with Cell C hosting 13 and MTN 9, and MVNE platforms at Cell C, Vodacom (2024) and Huge NXTGN (2025), with Telkom announced. A detailed guide is in Launching an MVNO in South Africa.

Nigeria: NIN-SIM linkage and the NCC tiers

Nigeria’s rule linking every SIM to a verified National Identification Number means the KYC integration is a national-database check, not a document upload. BusinessDay reported 153 million linked SIMs and 96 per cent compliance in August 2024. The Nigerian Communications Commission licenses MVNOs in five tiers; Tier 4 (Virtual Aggregator/Enabler) and Tier 5 (Unified Virtual Operator) carry fees of NGN 150 million and NGN 250 million on a ten-year tenure (International Bar Association, June 2022). A caution from the market: Nairametrics counted 43 to 46 licensees in November 2025 and only one or two active, which says something about the distance between a licence and a launch. The tiers are covered in MVNO licensing in Nigeria.

Kenya: SIM Registration Regulations 2025

Kenya’s SIM Registration Regulations 2025 (Legal Notice 90) took effect on 30 May 2025 and require verification of subscriber details against government databases (CM Advocates, July 2025). As in Nigeria, plan the KYC integration as a database check with the access agreement that goes with it, and budget stage 4 time for it. Equitel, Equity Bank’s MVNO on Airtel, has been licensed since 2014 and held 1.51 million subscriptions in Communications Authority data reported in June 2026 (Citizen Digital), which is the local proof that a bank-led MVNO can operate at scale under these rules.

European Union: porting within one working day

Article 106 of the European Electronic Communications Code (Directive 2018/1972) requires that a ported number be activated within one working day. National regulators implement this differently, and the porting clearinghouse and its certification process differ by country, so stage 4 planning for an EU launch starts with the national porting scheme rather than with the directive. Identification rules for new subscribers also vary by member state. Own numbering ranges for a Medium MVNO are available in some markets and not in others, and that decides whether you are the porting party of record.

Honest timelines

Published market ranges and a vendor’s own planning assumptions measure different things, and both are worth having. MVNO Index publishes market estimates of two to four months for a reseller, four to nine months for a thin or light MVNO, nine to fourteen for a thick MVNO and twelve to eighteen months or more for a full MVNO. These come from a single aggregator source and are quoted here as market estimates, nothing more.

Avante’s planning assumptions for its own delivery are three months to platform readiness for a standard mono-MVNO, four to six months to commercial launch for a Medium MVNO from the point the host agreement and legal framework are confirmed, and eight to ten months for a Full MVNO. Note the qualifier. The clock starts when stage 2 closes, and nobody outside your organisation, the host and the regulator can say when that will be. One published case helps calibrate: a leading banking MVNO in the CIS was delivered on Avante in six months, to the bank’s security and integration requirements.

The two sets of numbers are consistent once you separate them. The market range for a light MVNO includes stage 2. Avante’s range excludes it and assumes the integrations were scoped in Discovery and the long-lead items (host interface alignment, the porting certification enquiry) started before the platform contract. What it costs to get there, and how the cost splits between one-off and running items, is in What it costs to launch an MVNO.

Where Avante fits

Avante is a BSS vendor, not an enabler: it supplies the platform an MVNO, MVNE or MVNA runs, and does not resell airtime or operate a network. For a Medium launch, Avante MVNx Suite covers the product catalogue, online charging (Avante OCS), convergent billing, CRM, self-care, partner management, mediation and provisioning, plus the MNP, KYC and payment integrations, delivered on-premises, in a private cloud or as a managed service with 24x7 support. Beyond the software, the team builds the financial model with you, drafts the technical annex for the host agreement and supports the negotiation, and prepares the regulatory documentation per market. Full adds network elements through partners on the same platform, with no second subscriber migration. The stage plan, the responsibility matrix and an interactive timeline builder are on the launch page.

Frequently asked questions