Software services

MVNO platform development

An MVNO is a billing machine wearing a brand. The network is rented, but the promises to customers are yours, and every one of them lands on software: provisioning, rating, billing, care, and reporting. This is what that software stack actually involves.

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

An MVNO rents capacity from a host network and sells it under its own brand. The host moves the packets. The MVNO owns everything the customer experiences: the tariff, the SIM, the activation, the bill, the support call, and the renewal.

That means an MVNO lives or dies on software that most people never see. This article sets out what an MVNO platform actually consists of, where build-versus-buy decisions sit, the failure points that end MVNO ventures early, and the questions to ask any development partner. It is written from delivery experience. It deliberately does not document our own implementations; it tells you what to expect and what to demand.

The stack, in plain terms

Industry jargon splits this into BSS (business support systems) and OSS (operations support systems). In plain terms:

1. Commercial catalogue and CRM. What you sell, to whom, at what price, and the record of who your customers are. Product catalogue, orders, customer accounts, consents.
2. Activation and provisioning. The handshake with the host network that turns a sale into a working SIM or eSIM profile. Speed and reliability here define your customer's first impression.
3. Rating and charging. Turning usage events into money in real time: data sessions, calls, texts, roaming, add-ons, caps, and fair-use policies. Errors here become complaints, refunds, or regulatory attention.
4. Billing and invoicing. Periodic bills, payment collection, dunning, credit control, and refunds, each reconciled to the rated events that produced them.
5. Number porting. Moving customers in and out between networks on schedule without service loss. Porting that slips damages customers who were leaving competitors, and competitors talk.
6. Care and self-service. Agent tooling and a customer app or portal: usage, top-ups, plan changes, bars and unbars, eSIM reissue. Every care action must write back to the same source of truth.
7. Reporting and revenue assurance. Daily reconciliation of what was sold, what was rated, what was billed, and what was paid, against what the host network says. The gaps are your margin leaking.

A light MVNO buys more of this off the shelf. A fuller MVNO differentiates on more of it. Either way, the seams between components are where projects go wrong, which is why integration experience matters more than feature lists.

Build, buy, or hybrid

• Buy suits commodity pieces: payment collection, standard billing cycles, a self-service shell.
• Build suits everything that differentiates the brand: the catalogue, the tariff logic, the care flows, the reporting that tells you which products make money.
• Hybrid is the honest answer for most MVNOs, and the hard part is the contracts between the pieces: who holds the truth about a balance, an entitlement, an activation state. Define that before signing anything.

The failure points we see from the inside

• Underestimating rating. Tariffs that read simply are rarely simple. Caps, bundles, shared data, roaming zones, and proration interact. Testing coverage, not cleverness, is what keeps the bills right.
• Treating porting as a detail. Porting has deadlines and contractual windows with the host. Missing them is visible to customers and to the industry.
• Skipping reconciliation. Without daily revenue assurance, leakage is discovered by the accountant months later, when it is unrecoverable.
• Building without a maintenance plan. Tariffs change monthly. Host integrations change. An MVNO platform without a committed maintenance team decays in its first year.

The questions to ask any supplier

How Fuzzelogic works

Fuzzelogic Solutions has built and maintained software for commercial and regulated operations since 2007, with platforms running on three continents. We scope MVNO platforms with a fixed-price assessment, two to four weeks, and you own the verdict and the roadmap whether or not we build any of it. Builds are disciplined enough to land a working core in 12 to 16 weeks, and our support team stays after launch, because a telecoms platform is judged over years, not demos.

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

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