Software services

How to launch an MVNO

Launching an MVNO is not hard because the technology is exotic. It is hard because eight workstreams must land together, and the two that get underestimated are tariff logic and porting. Here is the sequence, and where the bodies are buried.

By Zakir Hoosen, Director, Fuzzelogic Solutions. Plain English guidance for business leaders.

Every MVNO starts the same way: a brand has an audience, mobile is the missing product, and the market looks crowded but not served. The ventures that launch successfully are not the ones with the best decks. They are the ones that respected the sequence. This article is that sequence, written by people who build and run the systems underneath.

It deliberately holds back the detail that is ours to sell. It gives you the map: the order of work, the decisions that cannot be deferred, and the failure points that end MVNOs in their first year.

The sequence

  1. Define the niche and the promise. Whose phone is this, and why do they switch? Bundle economics, community membership, or price alone. The promise dictates every technical choice after it.
  2. Secure the host agreement. Capacity, wholesale rates, service levels, porting windows, and integration support from the MNO or MVNE. The commercial envelope you sign here bounds everything you can build later.
  3. Choose the operating model. Light MVNO (host does more, you move faster with less control) through to full MVNO (you own more of the stack, you differentiate more). This decision shapes your build-versus-buy split.
  4. Design the commercial catalogue. Tariffs, bundles, add-ons, fair use, roaming zones. Write the rules as testable logic, because a tariff is a program, not a poster.
  5. Build the core platform. CRM, catalogue, provisioning, rating, billing, care tooling, self-service, reporting. Integrated to the host's interfaces and to payments.
  6. Prepare porting and compliance. Number porting processes both ways, regulatory registrations for your markets, data protection, and the customer-information obligations that come with telecoms.
  7. Run the dress rehearsal. Real usage data rated against your tariffs, bills produced and reconciled, a SIM activated and ported end to end, a care agent resolving a live fault. Launch is a rehearsal that worked.
  8. Launch small, then scale. First customers watched daily. Reconciliation reports read by a human every morning in the first months. Scale what survives contact.

Where ventures get hurt

Timeline reality

A focused team and a cooperative host can stand up a working MVNO core in months, not years. The fixed-price assessment we run takes two to four weeks and produces the architecture, the sequencing, and the honest risks, and you own that verdict whether or not we build. Our delivery model lands a working core in 12 to 16 weeks rather than a 12 to 18 month programme, and the same team that built it maintains it after launch.

Fuzzelogic Solutions has been building and maintaining commercial platforms since 2007. Nine regulated financial institutions sit among our clients and our platforms run on three continents. When you are ready to talk software, maintenance, or AI, call Fuzzelogic Solutions and ask for Zak.

Frequently Asked Questions

How long does it take to launch an MVNO?

With a signed host agreement and a focused build, a working core in months is realistic. Our delivery model targets 12 to 16 weeks for the core platform.

What is the biggest technical risk?

Tariff logic and porting. Tariffs are programs that interact; porting has contractual windows. Both need rehearsal before launch, not correction after.

Do we need to build everything?

No. Buy the commodity pieces, build what differentiates the brand, and define which system holds the truth about balances and entitlements before signing vendor contracts.

What team do we need after launch?

Maintenance is not optional: host integrations change, tariffs change monthly, and reconciliation needs a daily owner. Plan the run team at the same time as the build team.

How do we check an MVNO platform before we commit?

Run a fixed-price assessment. Two to four weeks, and you own the architecture, sequencing, and risk list whether or not you build with the assessor.

www.FuzzelogicSolutions.com | info@FuzzelogicSolutions.com | +44 (0)1624 618950

Zakir Hoosen, Director Suite 1B, 11 Circular Road, Douglas, Isle of Man IM1 1AF +44 (0)7624 482071 | +44 (0)1624 618950

Start with the assessment

Two to four weeks, fixed price, and you own the verdict and the roadmap whether or not we build any of it.

Get in touch

When you are ready to talk software, maintenance, or AI, call Fuzzelogic Solutions and ask for Zak.

www.FuzzelogicSolutions.com | info@FuzzelogicSolutions.com | +44 (0)1624 618950