MVNO back-office running on spreadsheets and manual processes that worked at 2,000 subscribers but are breaking at 20,000?
Subscriber provisioning taking hours of manual work because there is no automation for SIM activation, plan assignment, and number porting?
MVNO Platform Development
Custom MVNO platform for mobile virtual network operators -- subscriber management, SIM provisioning, number porting, billing integration, and back-office operations in one system, not a collection of spreadsheets and manual processes that break as subscriber count grows.
Built for MVNOs where back-office operations work at 2,000 subscribers but are visibly failing at 20,000, and where SIM activation and number porting still require hours of manual steps by an operations team member.
Subscriber lifecycle management -- onboarding, SIM activation, plan assignment, suspension, and deactivation
SIM and eSIM provisioning with number range management and SIM swap
Inbound and outbound number portability automation with MNP gateway integration
HLR and HSS integration for subscriber records, authentication, and roaming profiles
RaftLabs builds custom MVNO platforms covering subscriber lifecycle management, SIM and eSIM provisioning, inbound and outbound number portability automation, HLR and HSS integration for subscriber record management, CDR mediation and billing system feed, and a back-office agent portal for account management and bulk operations. Most MVNO platform projects deliver in 14-18 weeks at a fixed cost.
100+Products shipped
·24+Industries served
·FixedCost delivery
·12-14Week delivery cycles
Manual processes that work at 2,000 subscribers do not scale to 20,000
Every MVNO starts with manual processes. SIM activation is a ticket in a helpdesk tool that someone works through by logging into the MNO portal. Number porting is handled by emailing the MNO operations team and tracking status in a spreadsheet. Billing is a monthly export sent to whoever generates the invoices. At low subscriber counts, this is acceptable -- the team knows the process, the edge cases are familiar, and the ticket volume is manageable.
The problem is that this approach does not scale linearly. At 2,000 subscribers, a team of two operations staff can keep up. At 10,000, they cannot. The activation backlog grows. Porting requests take days because tracking is manual and staff move between tasks. Billing errors increase because the export process has manual steps where data gets lost or corrupted. Customer complaints escalate and churn increases.
A custom MVNO platform automates the operations that do not require human judgment. SIM activation runs in seconds with no manual intervention. Number porting requests are submitted and tracked automatically against the MNP gateway. Billing records are produced by the system and delivered to the billing platform without manual export steps. The operations team handles exceptions and customer escalations -- not the routine steps that should never require a person.
What we build
Subscriber lifecycle management
Subscriber onboarding from application through KYC verification, SIM assignment, plan selection, and account activation. Identity verification integration with KYC providers for document checks and identity confirmation. Automated account creation with subscriber profile, plan entitlements, and billing record synchronised on activation. Plan change management -- upgrade, downgrade, and mid-cycle changes rated correctly for the remainder of the billing period. Account suspension for non-payment with automated re-activation on payment receipt. Voluntary deactivation, number release, and SIM decommission workflow. Every stage in a subscriber's lifetime managed by the system rather than by operations team memory.
SIM and number management
SIM inventory management tracking physical SIM cards from receipt to assignment, activation, swap, and retirement. SIM batch import with ICCID range recording and status tracking. SIM assignment to subscriber account at activation with IMSI and MSISDN linkage. SIM swap workflow for damaged or lost SIMs -- new SIM assignment, profile transfer, and HLR update triggered automatically. Number range management covering allocated MSISDN ranges, available numbers, reserved numbers, and number retirement. eSIM profile management for devices that support downloadable SIM profiles -- profile generation, activation code delivery, and profile status tracking.
Number portability automation
Inbound porting -- customer requests to port their existing number to your MVNO -- automated from request submission through donor MNO notification, PAC code validation, porting date scheduling, and cutover confirmation. Outbound porting -- customer requests to leave your network -- managed through PAC code generation, request acknowledgement, and subscriber deactivation on the porting date. MNP gateway integration for automated request submission and status polling. Porting status tracking with customer notification at each stage. Failed porting handling with retry logic and operations team escalation for cases that cannot be resolved automatically. Porting audit trail for regulatory compliance and dispute resolution.
HLR and HSS integration
Home Location Register integration for 2G and 3G subscriber record management -- subscriber profile provisioning, authentication triplet management, roaming profile configuration, and service activation flags. Home Subscriber Server integration for 4G LTE and 5G subscriber management -- EPS profile, authentication vector management, VoLTE provisioning, and IMS service configuration. Subscriber record synchronisation between the MVNO platform and the HLR or HSS to ensure every account change is reflected in the network element. Profile rollback capability for failed provisioning events. Bulk provisioning operations for plan migrations affecting large subscriber groups.
Usage data mediation
CDR collection from the host MNO or MVNO enabler via SFTP, API, or real-time stream depending on what the MNO provides. CDR format normalisation to convert from the MNO's proprietary format into the schema your billing platform expects. Duplicate record detection and removal before records are passed to billing. Gap detection with automated re-request for missing record sequences. Wholesale cost record processing -- matching wholesale CDRs to retail subscriber CDRs for margin tracking. Delivery to the billing system in the format and schedule the billing platform requires. The mediation layer that ensures your billing system receives complete, clean usage data without manual intervention.
Back-office management
Agent portal for customer service teams -- full subscriber account view, plan history, usage summary, payment history, and communication log in one screen. Account management actions available directly in the portal -- plan change, SIM swap, suspension, credit application -- without requiring a separate system login. Bulk operations for fleet and enterprise customers -- mass plan changes, SIM activations in bulk, and group invoicing. Reporting dashboards for operations management -- active subscribers, activations and deactivations by period, porting volumes, and provisioning error rates. API layer for integration with third-party systems -- CRM, billing platforms, and retail channel partners. The operational layer that your team and your partners use to manage subscribers without touching the network directly.
Frequently asked questions
An MVNO platform is the back-office system that manages the subscriber-facing and operational side of an MVNO business. It handles subscriber onboarding and lifecycle management, SIM and number inventory, number portability, integration with the host MNO's network elements, usage data collection for billing, and the agent portal used by the customer service team. It is distinct from the billing system -- which handles rating, invoicing, and payment collection -- and from the network itself, which the host MNO operates. An MVNO platform sits in the middle: it tells the network what subscribers exist and what services they have, collects usage data from the network, and presents the subscriber record to the operations team.
Integration requirements vary by host MNO and MVNO enabler. For HLR and HSS integration, we build to the interfaces the MNO exposes -- typically MAP over SS7 for HLR, Diameter for HSS, or proprietary provisioning APIs where the MNO provides them. For CDR delivery, we work with SFTP batch delivery, real-time CDR streams, or API-based collection depending on what the MNO provides. MVNO enabler platforms like MVNE aggregators and BSS wholesale providers typically expose REST or SOAP APIs for provisioning and CDR retrieval. We confirm the specific interfaces available during discovery by reviewing the MNO's technical specification documentation before scoping the integration work.
Number portability automation requires integration with the national MNP gateway or clearinghouse in your market -- for example, Syniverse or NXTPORT in most European markets. We build the integration to submit porting requests, receive status updates, and trigger the cutover sequence at the agreed porting date and time. For inbound porting, that means accepting the customer's PAC code, submitting the port request to the donor MNO via the clearinghouse, polling for confirmation, and triggering the subscriber profile activation at cutover. For outbound porting, it means generating PAC codes, acknowledging port requests from gaining MNOs, and deactivating the subscriber record at cutover. The process that was a manual series of emails and spreadsheet updates becomes a sequence the system runs without human input.
MVNO platforms vary significantly by business model. A full MVNO that manages its own HLR needs direct HLR integration and full subscriber record management. A light MVNO that relies on the MNO for network functions may only need API-based provisioning through the MNO's wholesale portal. An MVNE-hosted MVNO typically provisions through the MVNE's API layer rather than directly to network elements. A branded reseller may not need number porting automation if the MNO handles porting on their behalf. We scope the platform to your specific arrangement with your host MNO or MVNE -- the right scope depends on what you control vs. what the network partner controls.
Telecom Billing Software -- usage rating, invoice generation, payment processing, and revenue reporting for MVNOs and ISPs
Talk to us about your MVNO platform project.
Tell us your host MNO arrangement, current subscriber count, where manual operations are slowing you down, and what growth you are planning. We will scope the right platform and give you a fixed cost.
