Production · actively maintained and developed

MVNO Management Platform

An operational platform for virtual mobile network operators, connecting customer service, sales, contracts, telecom resources, billing and self-service.

Conceptual functional overviewA functional overview, not a representation of the system’s internal architecture.

Operational whole

One platform across commercial, service and financial work.

Customer information, agreements, operator resources and financial activity remain connected throughout the service lifecycle. Staff work in the CRM, while customers use a corresponding self-service area built around the same contracts and mobile numbers.

Connected functional scope

From customer onboarding to ongoing service.

The platform supports the connected work needed to acquire a customer, establish and operate services, collect payment and give the customer direct access to everyday account tasks.

  1. Customer operations and protected information

    Customer records support everyday CRM work while personal information is handled in line with the required data-protection rules.

  2. Sales, orders and agreements

    SIM-card and subscription sales connect with orders, contracts, amendments, transfers, number portability, courier fulfilment and electronic signing through banking identity services.

  3. Telecom services and resources

    Operator processes use controlled inventories of SIM cards, telephone numbers and IP addresses, supported by integrations with the external services involved in delivery.

  4. Invoicing and account follow-up

    Invoicing connects with electronic invoice payments and debt-collection workflows, with the financial area later extended to support Poland’s KSeF system.

  5. Customer self-service

    Customers can work with their contracts and mobile numbers and purchase additional services through a portal connected to the wider operating platform.

Customer journey

Customers, sales and agreements

Customer management begins with the information needed to establish and support an account. The CRM keeps that information available to authorised operational work while respecting the required personal-data protection rules.

Sales staff can prepare SIM-card and subscription orders and carry them through to an agreement. The same area supports contract amendments and transfers, as well as the formal process of moving an existing telephone number to the operator.

Fulfilment remains connected to the order. Courier services support delivery, while electronic contract signing uses banking identity services to complete an agreement without turning it into a separate manual process.

Telecom operations

Resources kept in step with the service

A mobile service depends on more than the customer record. The platform maintains inventories of SIM cards, telephone numbers and IP addresses, then makes those resources available to the operator processes that assign and manage them.

Integrations support telecommunications and fulfilment work that crosses system boundaries, keeping those steps connected to the customer, agreement and resources handled by the platform.

Financial operations

Invoicing through to payment and recovery

The financial area covers issuing invoices and accepting electronic invoice payments. When an account remains unpaid, debt-collection workflows keep the follow-up connected to the customer and agreement concerned.

As regulatory requirements changed, invoicing was extended with support for Poland’s KSeF e-invoicing system. This became part of the existing platform rather than a separate product presented to its users.

Customer self-service

Everyday account tasks without a separate process

The customer portal exposes the parts of the service that customers need to handle directly. They can work with their contracts and mobile numbers and purchase additional services without routing every request through operator staff.

Self-service remains part of the broader operating platform. Customer actions, CRM work, service resources and financial information therefore stay connected around the same account instead of becoming parallel records.

High-level product model

Shared product, independently configured deployments

One shared codebase supports independently deployed CRM instances. Operator-specific configuration and permitted customization adapt each instance while the product continues to evolve as a whole.

This view describes the organization of the product at a high level.

  1. Shared product codebase
  2. Operator-specific configuration
  3. Independently deployed instances

A practical starting point

Working through a complex operational system?

Share the processes that need to connect and the constraints that matter. We can begin with the context, without requiring a finished specification.

Back to Selected Work