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.
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
- 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.
- 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.
- 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.
- 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.
- Build the core platform. CRM, catalogue, provisioning, rating, billing, care tooling, self-service, reporting. Integrated to the host's interfaces and to payments.
- 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.
- 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.
- 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
- The tariff was designed as marketing, not logic. Bundles interact, proration bites, and the first bill run produces complaints and refunds. Tariff logic needs test coverage against real usage patterns before launch, not after.
- Porting was treated as paperwork. Porting has contractual windows with the host and visible failures. Customers trying to join you are the ones who feel it first.
- No daily revenue assurance. Rated usage, billed amounts, and host settlement files must reconcile every day. Leakage found by the accountant at year end is unrecoverable.
- Launch without a maintenance team. Hosts change interfaces. Tax rules change invoicing. Tariffs change monthly. An MVNO platform is a living product; budget for the team that keeps it alive.
- The brand out-ran the operations. Marketing that scales faster than provisioning and care produces a social-media problem that discounts cannot fix.
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?
What is the biggest technical risk?
Do we need to build everything?
What team do we need after launch?
How do we check an MVNO platform before we commit?
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.
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