Service · Web development

Custom telecom software.

Custom software for operators, MVNOs, ISPs and B2B telecom providers. Customer portals, billing, order management, provisioning and OSS/BSS integrations that run alongside your existing stack — where Amdocs, Netcracker or Hansen don't quite fit.

BSS & OSSCustomer portalBilling & CDRMVNO stack

Telecom software is a stack, not a package.

A telecom operator never runs on a single system. There is a network layer with HSS, AAA, IMS and an EPC or 5G core; above it an OSS layer for service provisioning, fault management and performance management; above that a BSS layer with CRM, billing, product catalogue and order management; and on the outside the customer portal, the app, the IVR and the chatbot. Which layer is causing you pain determines what kind of custom software we build.

We don't replace Amdocs, Netcracker, Ericsson, Hansen Technologies or CSG Systems in a full-stack enterprise — that isn't what we do. What we do build is the parts that don't fit into a standard package, or where a package is overkill: a white-label customer portal for your brand, a BSS stack for a mid-market MVNO start-up, custom flows that can't be configured in an out-of-the-box telco platform, and integrations between multiple existing systems so they work as a whole.

The companies that come to us are usually operators, MVNOs, ISPs, B2B telecom providers or service providers with a telecom component. Sometimes also IPTV or FAST channel platforms and data centre or colocation providers with a customer billing challenge. What they have in common is that they feel a gap somewhere between their systems, and that a large package implementation is out of proportion to what they need. For the broader context around integrations between telecom systems, see also our page on smart API integrations.

Three flavours of telecom software.

Depending on where you sit in the stack and which problem comes first, we build different things. The three profiles below give a feel for the scope; in practice we shift the modules into exactly the mix that suits your situation.

Compact project · fixed sprint budget

Customer portal and self-service for operators

A white-label customer portal that runs alongside your existing BSS. Bundle overview, usage meters for data, calling and SMS minutes, invoice overview, cancellation and upgrade flow, SIM activation and SIM swap, and self-service for payments, reminders and payment arrangements. Login via SSO or magic link, connected to billing and provisioning via API. Suitable for companies that see their out-of-the-box portal as the weak link and want their brand to move with the product proposition.

Bundle & usageSelf-service paymentSIM swapCustomer invoices
Mid-sized project · fixed sprint budget

BSS modules for MVNOs and mid-market operators

For MVNOs, branded operators and smaller telecom providers that don't need the whole Amdocs or Netcracker box, but do need a serious BSS layer. We build order management with dependencies between orders, a product catalogue that supports family bundles and B2B contracts, billing for prepay, postpay and usage-based invoicing, and CDR processing as input for billing. Including a reseller or dealer portal for your distribution channel and the integrations with the MVNE platform, payment providers and credit-check services.

Order managementBilling & CDRProduct catalogueReseller portal
Larger project · fixed sprint budget

OSS integrations and custom flows alongside enterprise packages

Mission-critical custom software that runs on top of an existing Amdocs, Ericsson or Hansen stack. Provisioning integrations to the network to activate lines, SIM cards and services, number management with porting and range administration, integrations between BSS and OSS so that an order signal automatically becomes a service activation, and custom flows that can't be configured in the package. Also suitable for IPTV and FAST channel management, business VoIP and cloud PBX portals, and CTI interfaces between telephony and CRM with call pop and click-to-dial.

ProvisioningNumber managementCTI & cloud PBXIPTV / FAST

Which modules we build in practice.

The telecom stack has a fairly fixed anatomy: BSS on the business side, OSS on the operational side, orchestration in between and the network underneath. What we build for our clients sits largely in the BSS layer, with regular OSS integrations when an order flow needs to continue on to provisioning. Here are some of the modules we build most often. The list isn't exhaustive, but it is representative.

Customer portal with bundle overview, real-time usage (data, minutes, SMS), invoice history, cancellation and upgrade flows and self-service payment options. Order management where multiple product lines can run through a single order: mobile plus fixed plus TV bundle, with dependencies between orders, phased activation and automatic rollback on failure. For the wider context around order processing and fulfilment flows, our page on a custom order management system is good further reading. Subscription and billing engine for prepay, postpay, family bundles, usage-based billing and B2B contract models. If that's exactly where you feel the pain, our page on building a subscription management platform is good further reading.

CDR processing as input for billing: Call Detail Records from the switch or IMS platform, rating per tariff plan, mediation and subtotals per customer and invoice period. Provisioning integrations that turn order signals into network actions: activating a line, linking a SIM to an MSISDN, changing a speed on a BNG connection. Number management with porting (mobile and fixed), range administration and BIPT or ACM reporting. CTI interfaces between the telephone exchange and CRM with call pop-ups, click-to-dial and wrap-up screens for your customer service. Reseller and dealer portals with multi-tenant role management and commission overviews for your distribution channel. Finally, we regularly build MVNE/MVNO components for branded operators that run on a wholesale platform but want their own customer, billing and commerce flows.

Who we build custom telecom software for.

A few profiles we see knocking on our door fairly often. This isn't an exhaustive list, but it gives context on the kinds of organisations where custom software in the telecom stack genuinely makes a difference. Not every company has Amdocs or Netcracker; many work with a combination of smaller systems that no longer mesh properly.

Telecom operators (mobile, fixed, cable) in a market shaped by players such as KPN, T-Mobile/Odido and VodafoneZiggo, who want to strengthen their own flows or customer portal alongside the packaged stack. MVNOs in the Dutch and European landscape (think of brands such as Simpel, Lebara or hollandsnieuwe as market context) that run on a wholesale network but want to control their own customer experience and billing. B2B telecom providers that deliver business telephony, VoIP and cloud PBX and want to automate their customer portal and provisioning.

ISPs and fibre providers where provisioning to BNGs, modems and CPE is a continuous workflow. Data centre and colocation providers with customer billing based on rack units, cross-connects and usage. Service providers and managed services providers with a telecom component alongside their IT services. And finally TV and content services (IPTV platforms, FAST channels and streaming management) that want to orchestrate their subscriptions, content rights and invoicing flows. For the pure billing side of business telecom, our pages on building a payment platform and the broader topic of developing enterprise software are also relevant.

What you get at the end.

A production-ready set of telecom modules that fits into your existing stack, plus everything around it so you can manage it yourself, extend it and hand it over to a new partner should that ever be necessary.

  • The telecom modules themselvesProduction and staging environments, running in your cloud (GCP, AWS, Azure) or with us, with logging, monitoring and alerting on order flow, provisioning and billing events.
  • Integrations with BSS, OSS and the networkWorking integrations with your HSS, AAA, IMS, EPC or 5G core where relevant; and with your CRM, billing engine, MVNE platform and payment providers on the BSS side. See also our API integrations.
  • Codebase with architecture documentationFull source code, build and deployment pipeline, runbooks and an architecture overview that lets your own team or a successor agency carry on without lock-in.
  • Admin manual for your operations teamHow to configure product rules, how to handle number porting requests, how to fix CDR processing errors and how to onboard new resellers in the portal.
  • Training for key users and customer serviceSessions for your billing team, customer service and order desk, plus short video tutorials for less frequent tasks — think shared-credit flows or complex family-bundle changes.
  • Support contract (optional)Monitoring, backups, security patches and ongoing development. A fixed monthly price with clear response-time levels, defined escalation paths and alignment with your own NOC or service desk.

When custom telecom software is the right choice.

Four patterns in which we support operators, MVNOs and B2B providers. If you recognise one of them, we'd be glad to talk further about what a custom layer would actually change in your situation.

Package limits

The standard package dictates your business model

Your product proposition goes beyond what the out-of-the-box platform can handle. Family bundles with non-standard rules, B2B contracts with tiered pricing, or a tariff plan the package doesn't support without expensive customisation. The flow gets stuck in Excel workarounds that nobody can keep track of any more.

Customer experience

The customer portal is a weak link

Customer contact and NPS show you that the existing portal doesn't keep pace with what you do commercially. Bundles are unclear, cancellation flows are cumbersome, and self-service payment doesn't work well. A white-label custom portal alongside the packaged BSS solves that without touching the whole system.

MVNO launch

A lightweight BSS stack for a new MVNO

You're launching an MVNO or branded operator, and full-stack packages are out of proportion to what you need in year one. You want a serious BSS layer with order management, billing and a customer portal, integrated with an MVNE platform, without a multi-year enterprise implementation.

Integration

Multiple systems, no whole

You have CRM here, billing there, a third-party order management tool and a provisioning layer at the network supplier. On paper they cover the flow; in practice orders, statuses and invoices fall through the cracks. You need an orchestration and integration layer that makes it all work together.

How a telecom project works with us.

1

Introduction and stack audit

A conversation in which we walk through your telecom stack: which BSS and OSS components, which network supplier, which MVNE or wholesale platform, and which flows are causing pain right now. We map out the pain points and determine where custom software makes the biggest difference. We often also talk to people from your billing team and customer service, because they know the exceptions that aren't in a process diagram.

2

Scope, architecture and integration plan

A workshop with your operations, IT, billing and commercial teams. We map out the desired BSS/OSS flow, define the integrations (CRM, billing, MVNE, provisioning, payments) and deliver a scope with a sprint plan. The first screen flow for the portal or the new module is on the table. Together we choose which part goes live first — usually where the pain is greatest, often the customer portal or a specific billing flow.

3

Building in sprints with early access

We build the modules in short sprints. Every iteration produces a working build that your team can test with real CDR data, real orders and real porting requests. BSS and OSS integrations are developed in parallel so the first end-to-end run comes together quickly. By using early access from the start, we uncover edge cases — such as unusual porting scenarios or family-bundle exceptions — before they break in production.

4

Rollout, training and further development

A phased rollout per customer segment or per brand, training for key users and customer service, plus a support phase with continuous improvements. We stay involved for as long as it makes sense and hand over cleanly to your own team where desired. For parties who want to keep building themselves, we deliver a clean codebase and an architecture overview so they aren't locked in to us — a principle we consider important in telecom, where relationships run long.

Frequently asked questions about custom telecom software.

What operators, MVNOs and B2B providers typically ask us before we start.

Will you replace our Amdocs, Netcracker or Hansen platform?
No. Amdocs, Ericsson, Netcracker, Hansen Technologies, CSG Systems, Comviva and Optiva are full-stack enterprise platforms with decades of investment behind them — we don't do that kind of replacement project. What we do is build custom software alongside such a package: a white-label customer portal, a specific order or billing flow the package can't handle, or an integration layer between BSS and OSS so they work as one. For MVNOs and mid-market operators we sometimes do build a complete BSS stack, because enterprise packages are simply out of proportion there.
What is the difference between BSS and OSS, and where do you build the most?
BSS (Business Support Systems) covers everything to do with the customer and the business model: CRM, billing, product catalogue, order management and the customer portal. OSS (Operations Support Systems) covers everything to do with the network and service delivery: provisioning, fault management, performance management and network inventory. We build most of our work in the BSS layer, with regular OSS integrations — for example, when an order in BSS needs to automatically trigger a provisioning action on the network. The deep OSS platforms themselves we leave to the specialist vendors.
Can you build a white-label customer portal for an operator?
Yes. A white-label customer portal is one of the modules we build most often — especially for companies that find their out-of-the-box portal too limiting, or that want to run multiple brands on a single underlying BSS. The portal connects to your existing billing, provisioning and CRM via API, carries your own branding and domain, and includes the flows you need commercially: bundle overview, real-time usage, invoice history, cancellation and upgrade flows, SIM card activation and self-service payments.
Do you also build a billing engine for usage-based invoicing?
For MVNOs and mid-market operators, yes. A custom billing engine with rating per tariff plan, CDR mediation, prepay and postpay flows, family bundles, usage-based invoicing and B2B contract models is within our scope, provided there is a reasonable volume profile behind it. For very high-volume real-time charging in a tier-1 operator context, we refer you to the specialist vendors — that is not what we are the agency for. For the broader context around subscription billing, see also our subscription management platform.
How do you handle compliance, ACM oversight and regulation?
Telecom is heavily regulated: ACM oversight in the Netherlands, BEREC frameworks at EU level, GDPR for customer data, rules on emergency communications (112), and lawful interception requirements that we mention here only because they are sensitive. Euro tariff and roaming rules are built into the product logic. Where relevant, we build in audit logs, retention policies and reporting for BIPT or ACM notifications. What we do not do is give legal advice on that compliance; we do build the software that makes it possible to comply.
What is the difference between B2C and B2B telecom software for you?
At architecture level they have a lot in common; at product and flow level they are very different. B2C is about volume, bundles, cancellation flows and self-service payments for individual consumers. B2B is about contracts, framework agreements, multi-site administration, pooled bundles across employees, and detailed reporting for the customer's procurement and finance departments. A B2B portal typically has a hierarchy of customer administrators, cost centre allocations and API access for automated order placement — a B2C portal is much flatter.
What determines the cost of a telecom software project?
The cost is determined by scope and complexity: which modules are in scope (portal only versus portal plus billing plus order management), the number and depth of the OSS and BSS integrations, whether CDR processing and number management are included, and whether regulatory reporting (BIPT, ACM) is built in. We work with fixed sprint budgets, so you know exactly where the budget is going each sprint. For an initial indication, take a look at custom software costs.
How do you integrate with our existing network and provisioning system?
For provisioning, we work with the APIs or webhook interfaces of your network layer: HSS for subscriber data, AAA for authorisation, IMS for voice services, EPC or 5G core for data, BNG for broadband connections. In practice, this often goes through an MVNE or wholesale platform if you run on another network. We build in retry logic, idempotent provisioning calls and alerting in case a network action fails, and we make sure order statuses in the BSS are reported back properly when provisioning finally succeeds or fails for good.

Talk to us about your telecom software.

A no-obligation introductory call of half an hour. We listen to your stack, whether you're an operator, MVNO, B2B provider or ISP, ask sharp questions about BSS, OSS and the flows that are causing pain right now, and give you direction on where custom software makes a difference and where a package or partner platform is a better fit.

Edit content