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.
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 that an OSS layer for service provisioning, fault and performance management; above that a BSS layer with CRM, billing, product catalogue and order management; and on the outside the customer portal, app, IVR and chatbot. Which layer is causing you pain determines the kind of custom development we build.
We don't replace Amdocs, Netcracker, Ericsson, Hansen Technologies or CSG Systems for a full enterprise stack — that isn't what we do. What we do build are the pieces that don't fit a standard package or where a package is too heavy: 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 one.
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 between their systems somewhere, and that a large packaged implementation is not the right fit for what they need. For broader context on integrating telecom systems, see our page on smart API integrations.
Depending on where you sit in the stack and which problem is most pressing, we build different things. The three profiles below give a sense of scope; in practice we shift the modules into the exact mix that suits your situation.
A white-label customer portal that runs alongside your existing BSS. Bundle overview, data, voice and SMS usage meters, invoice overview, cancellation and upgrade flows, SIM activation and SIM swap, and self-service for payments, reminders and payment plans. Signs in with SSO or magic link, and connects via API to billing and provisioning. Suited to companies that see their out-of-the-box portal as a weak link and want their brand to keep pace with their product proposition.
For MVNOs, branded operators and smaller telecom providers that don't need the full Amdocs or Netcracker suite, 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 prepaid, postpaid and usage-based invoicing, and CDR processing as input for billing. Includes a reseller or dealer portal for your distribution channel, and integrations with MVNE platforms, payment providers and credit-check services.
Mission-critical custom software that runs on top of an existing Amdocs, Ericsson or Hansen stack. Provisioning integrations with 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 cannot be configured in the package. Also suited to 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.
The telecom stack has a fairly fixed anatomy: BSS on the business side, OSS on the operational side, orchestration in between and the network beneath. What we build for our clients mostly sits in the BSS layer, with OSS integrations regularly needed when an order flow has to reach provisioning. A number of modules we build often, not exhaustive but representative.
A customer portal with bundle overview, real-time usage (data, minutes, SMS), invoice history, cancellation and upgrade flows and self-service payment options. Order management in which 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 broader context on order processing and fulfilment flows, our page on a custom order management system is good follow-up reading. A subscription and billing engine for prepaid, postpaid, family bundles, usage-based invoicing and B2B contract models. If that's where you feel the pain, our page on building a subscription management platform is good follow-up 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.
Here are a few profiles we see approaching us often. This is not an exhaustive list, but context for the kind of organisations where custom work in the telecom stack genuinely makes a difference. Not every party runs Amdocs or Netcracker; many work with a combination of smaller systems that no longer fit together well.
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 bundle stack. MVNOs in the Dutch and wider European landscape (think of brands such as Simpel or Lebara, as market context) that run on a wholesale network but want to control their own customer experience and billing. B2B telecom providers that supply business telephony, VoIP and cloud PBX and want to automate their customer portal and provisioning.
ISPs and fibre providers where provisioning across BNG, modems and CPE is one continuous workflow. Data centre and colocation providers with customer billing based on rack units, cross-connects and consumption. Service providers and managed services companies with a telecom component alongside IT services. And finally, TV and content services such as IPTV platforms, FAST channels and streaming management, which want to orchestrate their subscriptions, content rights and billing flows. For the pure billing side of business telecoms, our payment platform build and the broader enterprise software development offering are also relevant.
A production-ready set of telecom modules that fits into your existing stack, plus everything around it so you can manage it yourselves, extend it, and hand it over to a new partner should that ever be necessary.
Four patterns in which we support operators, MVNOs and B2B providers. If you recognise one of them, we would be happy to discuss what a custom layer would actually change in your situation.
Your product proposition goes beyond what the out-of-the-box platform can handle. Family bundles with deviating rules, B2B contracts with tiered pricing, or a tariff plan the package does not support without costly customisation. The workflow gets stuck in Excel exceptions that nobody oversees any more.
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.
You are launching an MVNO or branded operator, and the 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, connected to an MVNE platform, without a multi-year enterprise implementation.
You have a CRM here, billing there, an order management tool from a third party and a provisioning layer with the network supplier. On paper they cover the workflow, but in practice orders, statuses and invoices fall through the gaps. You are looking for an orchestration and integration layer that makes the whole thing work.
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.
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 sprint planning. The first screen flow for the portal or new module is on the table. Together we choose which component goes live first, usually where the pain is greatest, often the customer portal or a specific billing flow.
We build the modules in short sprints. Each iteration produces a working build 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 loop closes quickly. By bringing in early access, we uncover edge cases, such as unusual porting scenarios or family bundle exceptions, before they break in production.
Phased rollout per customer segment or per brand, training for key users and customer service, plus a management phase with ongoing improvements. We stay involved for as long as it makes sense and hand over neatly to your own team where desired. For parties who want to build on it themselves, we deliver a clean codebase and architecture overview so they are not tied to us, a principle we consider important in the telecom context, where relationships tend to be long-term.
What operators, MVNOs and B2B providers usually ask us before we start.
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.
Appfront uses cookies and similar technologies to keep the website working properly, for analytics and for marketing. You choose what you allow. Read more in our privacy policy.
