"What distinguished RaftLabs from other providers was their fantastic ability to build real-time engagement-based products."
Georgina D.
CEO & Co-Founder, People Supported Technologies
Telecom Software Development | BSS, OSS, MVNO
Telecom operators and MVNOs run on BSS and OSS platforms that were built when launching a new product meant a 6-month billing configuration project. The market moves faster than that now, bundled offers, usage-based pricing, and IoT connectivity require a stack that can change without a systems integrator.
RaftLabs builds custom telecom software for operators, MVNOs, ISPs, and telecom product companies. Billing platforms, customer self-service portals, network operations tooling, and the product configurators that let you launch new offers in days. We have not yet shipped a public telecom BSS/OSS case study; our closest verified proof is a large-scale utility billing and account-platform migration for Energia, an energy and utilities provider.
BSS and billing platforms that support flexible pricing models without a 6-month configuration cycle
Customer self-service portals that handle plan changes, usage queries, and support without a call center
MVNO stacks, the full BSS layer for virtual operators running on a host network
AI-assisted network operations, churn prediction, anomaly detection, fraud scoring (see also our dedicated AI for telecom service)
Bring the problem, the current workflow, or the existing code. We reply with a practical next step within one business day.
Trusted by
The brief
Good software decisions begin with the constraint, not a list of features or a preferred technology.
Launching a new bundle or pricing change takes 4 months because three legacy systems need coordinated updates?
Customer portal that shows a PDF bill and a phone number, no self-service, every query goes to the call center?
Plain answer
RaftLabs builds BSS platforms, MVNO stacks, customer portals, and network operations tooling for telecom operators across the US, UK, Europe, Canada, GCC, South Africa, and Southeast Asia. Fixed-price engagements from $60K. No public telecom case study yet; closest verified proof is a utility billing-platform migration for Energia.
What to remember
Proof
Commercial BSS platforms are built for stability, not speed. Launching a new bundle means raising a change request, waiting for the next quarterly release, and then spending three months in configuration and testing. Meanwhile your competitors launched the same offer in 6 weeks.
According to a 2025 IDC report commissioned by Ericsson, OSS/BSS-related capital expenditure is forecast to reach $211B globally between 2025 and 2028, driven by operators trying to escape legacy systems that can no longer support flexible pricing, 5G monetization, or real-time customer experience. The investment reflects how deeply broken the status quo is, not optional modernization, but survival-level infrastructure debt.
The operators who move faster than their BSS vendor do it by building a thin product and pricing layer on top, a configurator and order management layer that talks to billing via API, without touching the commercial platform's core configuration. The billing system handles rating and invoicing. The custom layer handles the product catalog, the customer experience, and the operational workflows the BSS was never designed for.
We have not yet shipped a public telecom BSS/OSS platform, so we won't claim delivery we can't back up. The closest verified proof is Energia, an energy and utilities provider, where we ran a large-scale billing and account-platform migration and rebuild: a comparable regulated-utility billing pattern, not telecom-specific. Confirm direct telecom-sector experience during scoping.
For AI capabilities (churn prediction, network anomaly detection, SIM swap fraud detection), see our dedicated AI for telecom service.
Capabilities
Billing built for flexible pricing: subscription and usage-based rating for voice, data, and SMS, bundled offers with shared usage pools, roaming, and promotional credits. Product catalog management lets you launch a new bundle without a systems integrator, and a revenue assurance layer reconciles billed revenue against network usage to surface rating gaps and unbilled usage. Payment gateway integration and invoicing in the format your enterprise customers require.
Portals that handle contact center queries before they become calls. Real-time usage dashboards showing data, minutes, and SMS against the subscriber's plan; plan changes with eligibility checking, proration, and immediate BSS execution; bill explanation in plain language; and fault reporting that checks for known network issues and gives live status. White-labelled to your brand and mobile-first across web and native apps.
The complete BSS layer for a virtual network operator: subscriber management, a tariff engine for rate plans and out-of-bundle charging, billing and invoicing from rated CDRs, product catalog, customer portal, and support tooling. We've built MVNO platforms for operators running on all the major UK and European host networks.
Operational dashboards and tooling for network engineering teams that need more than commercial NMS platforms provide. Network inventory updated from provisioning events rather than manual spreadsheets; fault management with event correlation, alarm deduplication, and ticketing; performance dashboards built for the specific views your NOC monitors; and capacity planning that forecasts traffic growth against current headroom.
Revenue assurance pipelines reconcile network usage against billing records to find what's delivered but not billed, and billed but not delivered. Fraud management covers SIM swap detection scored against account history, international revenue share fraud on anomalous call patterns, and account takeover detection from login and device signals. All findings surface in a case management workflow so the team works prioritized exceptions rather than raw discrepancy files.
Compliance tooling built to the specific requirements of your regulator. UK Ofcom: lawful intercept audit trails, number portability reporting, and consumer contract information delivery. US FCC: CPNI access controls and disclosure logging, E911 provisioning validation, and STIR/SHAKEN certificate management. EU BEREC: net neutrality logging and portability SLA reporting. GDPR: consent management, data subject access request handling, and retention policy enforcement.
How we work
We start by understanding your existing BSS/OSS landscape, what commercial platforms you run, which APIs they expose, where the gaps are between what the platforms do and what your operations need. Most engagements are a custom layer built on top of existing systems, not a replacement. The audit identifies exactly what to build and what to integrate with, so the architecture is right before development starts.
Telecom software is integration-heavy. Before writing a line of product code, we map every API call the new system will make: subscriber queries, plan change executions, usage data pulls, provisioning events, and fault management hooks. For BSS platforms with limited API coverage, we identify the integration path, REST API, SOAP, database view, or file-based, and design the integration layer. You review the integration design before build begins.
Development runs in 2-week sprints with working software at each milestone. For telecom specifically, we build and test against your actual BSS in a staging environment, not a mock, so integration failures surface during development, not at launch. Subscriber scenarios are tested end-to-end: activation, usage, plan change, billing, and disconnection. Regulatory compliance controls validated against your jurisdiction's requirements before launch.
Production deployment with monitoring for the integration points that matter most in telecom: billing API response times, provisioning event processing rates, and portal session error rates. Full source code handover with documentation covering the BSS integration points, the rating logic, and the operational runbooks your NOC team needs. No ongoing dependency on us to keep the system running.
Why us
The engineers who assess your problem also build the solution. No bait-and-switch, no offshore handoff after the contract is signed. The team you meet in week 1 ships in week 12.
We scope the work, calculate the cost, and lock it in writing before any development starts. A scope change is a change request: priced, agreed, or dropped. It never absorbs into the project and appears on the final invoice.
Real engagements across SaaS, fintech, healthcare, and logistics, not every one published as a named case study. We have not yet shipped a public telecom BSS/OSS case study; our closest verified proof is a large-scale billing and account-platform migration for Energia, an energy and utilities provider.
Ofcom, FCC, BEREC, and GDPR requirements are scoped in week 1, not retrofitted before launch. We have shipped CPNI-compliant systems for US operators, Ofcom-compliant platforms for UK operators, and GDPR-compliant subscriber data handling for European markets.
Scope and price
Start with a single system, such as a customer self-service portal integrated with your existing BSS, or a product configurator that talks to your billing system.
The BSS layer is built on top of the host network for MVNOs; existing BSS platforms are integrated through their APIs, not replaced by default.
Starting investment
$60K to $100K
Fixed-price engagements from $60K. A full MVNO BSS stack covering billing, subscriber management, product catalog, and customer portal typically runs $100K to $200K.
Proof
Three-year average engagement. Founders and operators describing the work in their own words. No marketing varnish.
Thanks to RL Remotely team for experimenting with an innovative remote work application for employee engagement and enterprise productivity.
Mohit S.
Founder, WorxRemotely
"What distinguished RaftLabs from other providers was their fantastic ability to build real-time engagement-based products."
Georgina D.
CEO & Co-Founder, People Supported Technologies
Work with us
Fixed cost, full source code ownership, no vendor lock-in. Tell us what you need to build.
Straight answers to what buyers ask before they scope. Still stuck? .
BSS (Business Support Systems) covers the commercial layer of a telecom operation: the product catalog (what you sell), billing (how you charge for it), order management (how subscriptions are provisioned and changed), CRM (how you manage customer relationships), and revenue assurance (how you verify you're billing correctly for everything you're delivering). OSS (Operations Support Systems) covers the network layer: network inventory (what equipment you have and where), fault management (detecting and resolving network issues), configuration management (provisioning and changing network elements), and performance management (measuring and optimizing network quality). Most operators run commercial BSS platforms (Amdocs, Comverse, Oracle Communications) alongside custom-built internal tools for the processes the commercial platforms don't handle well. We build the custom layer, the product configurator that's faster than the billing system's native UI, the customer portal that talks to the BSS via API, the operational dashboard the network team actually uses.
An MVNO running on a host network needs the BSS layer the host doesn't provide: a product catalog and pricing engine that defines what the MVNO sells (independent of the host's product catalog), a billing and invoicing system that rates usage data from the host against MVNO subscriber tariffs, a subscriber management system that handles activation, deactivation, plan changes, and account management, a customer portal for subscriber self-service, a support tooling layer for customer operations, and a revenue assurance layer that reconciles MVNO billing against host network wholesale invoices. Some MVNOs also need a SIM management system, an eSIM provisioning API, and a number portability integration. The extent of custom build vs commercial MVNO platform (BSCS, Netcracker, Optiva) depends on your subscriber volume, the complexity of your tariff structure, and how fast you need to move to market.
Most telecom call center contacts fall into a small number of categories: balance and usage queries, plan change requests, bill explanation, fault reporting, and device unlock requests. A well-built self-service portal handles all five without a human. Usage dashboards showing real-time data, minutes, and SMS consumption against the subscriber's plan. Plan change workflows that check eligibility, show the upgrade price with proration, and execute the change immediately against the BSS via API. Bill explanation that breaks down each charge with plain-language descriptions. Fault reporting that opens a ticket, checks for known network issues in the subscriber's area, and gives a live status update without needing to call. Operators running self-service portals typically deflect 30-50% of contact center volume within 6 months of launch.
Yes. We build the API layer between your existing BSS and the customer-facing or operational tools you need. Most commercial BSS platforms expose REST or SOAP APIs for subscriber management, billing queries, product changes, and order management. We integrate against those APIs to build the modern UI your customers see and the operational tooling your team uses, without replacing the billing system itself. For systems with limited API coverage, we build against database views or file-based integrations where necessary. We've integrated with Amdocs, Comverse, Oracle Communications, Netcracker, and Ericsson BSS platforms.
UK (Ofcom): number portability compliance, General Conditions of Entitlement requirements, consumer contract information requirements under the Telecoms Consumer Protection regulation, and GDPR for subscriber personal data. US (FCC): CPNI (Customer Proprietary Network Information) rules governing the use and protection of call records and location data, E911 compliance for VoIP services, and TCPA compliance for outbound messaging campaigns. EU (BEREC): number portability, net neutrality compliance logging, and GDPR for subscriber data. We work with your legal and compliance team to validate jurisdiction-specific requirements and build the audit trails, consent management, and data handling processes they require. The duties themselves stay with your organisation: as the operator, you are the one answerable to Ofcom, the FCC, or your EU regulator. They apply to systems like this one because it holds subscriber data and creates the records those duties cover. We build the parts scoping names, and your legal and compliance team validates them. Compliance is shared work; no software build makes an operator compliant on its own.
A focused single-system build, a customer self-service portal integrated with your existing BSS, or a product configurator that talks to your billing system, typically runs $60K-$100K. A full MVNO BSS stack covering billing, subscriber management, product catalog, and customer portal typically runs $100K-$200K. Network operations tooling covering fault management, performance dashboards, and capacity planning runs $60K-$120K depending on the number of network elements and data sources integrated. A complete quote names the systems in scope, the BSS and network system connections, who does what and who can see and change what, what 'done' looks like for each system, moving your subscriber and billing data over, and anything left out. If the scope changes, the change is priced and approved in writing before the work is done. All engagements run at a fixed cost agreed before development starts.
No. Most engagements are a custom layer built on top of the BSS you already run, not a replacement. The audit stage identifies what to build and what to integrate with. The billing system keeps handling rating and invoicing, while the custom layer handles the product catalog, the customer experience, and the operational workflows the BSS was never designed for.
You do, from day one. The code, the accounts, your subscriber and billing data, and the project notes are yours from the first day of the engagement, not handed over at the end. Accounts are opened in your name, and the notes stay current through the build, so another team could take over at any point.
Nothing needs to be handed back, because you already hold it: the code, the accounts in your name, your data, and project notes and runbooks that stay current through the build. We do not offer source-code escrow, because nothing is held back for escrow to release. Another team can pick the system up and run it without us.
Penetration testing is taken care of before launch. No production data is used in development, always. Backups are tested, always. When someone leaves a team, there are offboarding steps that remove their access. Any third-party services the system depends on, such as your BSS platform, payment gateways, or eSIM provisioning services, are named in the scope document before you sign. We claim practices we can show you, not certifications.
Support is a separate arrangement, agreed in writing: an ongoing arrangement for changes and new offers, a further fixed phase, or your own team running the system from the project notes and runbooks. The costs that keep running sit in your categories: your commercial BSS platform licences, payment gateway charges, hosting, and any SIM or eSIM provisioning services the system uses.
There is no standard range, because telecom builds turn on the stack you already run. The work moves through four stages: a stack and integration audit, integration design and API mapping, a phased build in 2-week sprints with working software at each milestone, and launch. The calendar is driven by ordinary things: how quickly API access and answers come from your BSS vendor, when a staging environment is available for testing, and the time your legal and compliance team needs to validate the regulatory controls. The scope document gives the dates in writing before development starts.
We work on five principles. Switch to Async: the state of the build is written down where your team can read it, so nobody waits on a meeting to learn where things stand. Be Prepared: calls come with the material sent ahead and a clear ask. Write: decisions, integration mappings, and open questions are recorded in writing, not left in call memory. Ask and tell: if an API turns out to cover less than its documentation promises, we say so plainly and early. Own: the team on your project owns its outcomes, not just its tasks.
Yes. We sign the client's NDA before anything sensitive is shared. Your tariff plans, subscriber figures, and network details stay confidential, and scoping conversations stay between us.
No. The engineers who scope your platform also build it, and the people on your calls are the people on your project. Our team works across India & Ireland, and there is no handoff to another company after signing.