Telecommunications companies operate one of the most complex enterprise software landscapes of any industry — BSS, OSS, network management, CRM, billing, and an increasingly cloud-native 5G infrastructure stack. Vendors exploit network deployment dependencies and long integration cycles to maintain pricing power. This guide covers the major software categories, licensing models, and negotiation strategies that deliver 20–35% cost reductions.
Telecommunications companies are simultaneously technology companies, infrastructure operators, and service businesses — which means their software estates are among the most complex and costly of any industry. The distinction between BSS (Business Support Systems — billing, CRM, product catalogue) and OSS (Operations Support Systems — network inventory, provisioning, assurance) creates two distinct software domains with different vendor ecosystems, commercial models, and negotiation dynamics.
This guide is part of our industry-specific negotiation series. It covers the major software categories in telecommunications, their licensing models, and the negotiation strategies that work best in this sector. For foundational negotiation strategy, see our IT contract negotiation strategy guide.
Business Support Systems — the software that handles customer billing, product catalogue management, order management, and customer care — are among the longest-running and most deeply embedded systems in any telco's IT estate. Tier 1 operators often run BSS platforms that have been in production for 10–20 years, with hundreds of downstream system integrations that make replacement projects multi-year, multi-hundred-million-dollar undertakings.
Vendors of legacy BSS platforms (Amdocs, CSGI, Oracle Communications, Nokia) know that their customers face enormous switching costs. This knowledge shapes their commercial behaviour: maintenance rates are high, upgrade costs are substantial, and new feature pricing is at list rate. The counter-strategy is to invest systematically in demonstrating migration optionality — even if actual migration is not planned.
The cloud-native BSS wave (Ericsson BSCS, Netcracker TCS, Comarch BSS) has created genuine competitive alternatives for telcos willing to invest in migration. For operators with BSS contracts up for renewal in 2025–2028, a structured evaluation of cloud-native BSS alternatives creates the competitive tension needed to extract meaningful pricing concessions from incumbent vendors. See our competitive bidding guide for methodology applicable to large telco BSS evaluations.
BSS licensing models vary significantly by vendor and platform generation:
Operations Support Systems — network inventory, topology management, network provisioning, service assurance, and fault management — are the operational backbone of any telecommunications network. OSS vendors (IBM Netcracker, Ericsson, Nokia, TEKELEC, and increasingly cloud-native players like Rakuten Symphony) have historically operated in a proprietary, specification-intensive environment that limited competitive alternatives.
Want independent help negotiating better terms? We rank the top advisory firms across 14 vendor categories — free matching, no commitment.
Network inventory systems (IBM Rational, Netcracker, Amdocs Network) are priced on a combination of named users and managed network elements (nodes, circuits, capacity units). As networks grow — 5G base station densification, fibre rollout — the managed element count increases automatically, driving licence cost growth. Negotiate managed element pricing with volume caps and tiered rates for large-scale network deployments.
ServiceNow has become the dominant ITSM platform for telecommunications companies, with Telecom Service Management (TSM) and Telecom Network Inventory (TNI) modules. ServiceNow's telco modules command premium pricing above the standard ITSM licence costs. Negotiate ServiceNow Enterprise agreements that cover ITSM, TSM, and TNI in a single deal — bundled pricing consistently delivers 15–25% savings versus module-by-module procurement. See our general IT contract negotiation strategy for ServiceNow-applicable tactics.
SAP's telecommunications industry solution covers ERP (finance, HR, procurement), SAP Revenue Accounting and Reporting (IFRS 15 compliance), SAP Convergent Charging, and SAP Convergent Invoicing — the latter two forming SAP's BSS charging and billing offering. Telcos running SAP for both ERP and BSS functions have a complex licensing estate that spans multiple SAP product lines with different commercial models.
IFRS 15 / ASC 606 compliance requirements drove SAP RAR adoption across the sector. SAP RAR is licensed separately from the core ERP licence and priced on a combination of users and transaction volume (performance obligation items processed). Negotiate SAP RAR pricing as part of your overall SAP enterprise agreement renewal — it should not be purchased as a standalone product at list rate.
Telcos running SAP as ERP alongside Salesforce CRM, Amdocs billing, or Oracle Communications products have indirect access exposure from the integration layer. Customer orders created in Salesforce that flow into SAP for financial processing, subscription records created by the billing system that trigger SAP contract accounting — these generate Digital Access documents under SAP's current commercial model. Quantify this before renewal using our SAP indirect access guide methodology.
5G network deployments are driving a fundamental change in telecom software architecture — from proprietary, hardware-integrated systems to cloud-native, containerised, microservices-based platforms. This transition creates both new commercial models and new negotiation opportunities.
Get the IT Negotiation Playbook — free
Used by 4,200+ IT directors and procurement leads. Oracle, Microsoft, SAP, Cloud — all covered.
| 5G Software Category | Key Vendors | Licensing Model | Negotiation Lever |
|---|---|---|---|
| Core Network (5GC) | Ericsson, Nokia, Cisco, Samsung | Per-subscriber or capacity-based | Multi-vendor disaggregation threat; capacity tier caps |
| vRAN / Open RAN | Ericsson, Nokia, Rakuten, Mavenir | Per base station or per-sector | Open RAN multivendor competition is real |
| Cloud-Native BSS | Amdocs, Comarch, Netcracker, CFORIA | Subscription per subscriber | Evaluate alongside legacy BSS migration decisions |
| Network Analytics/AI | IBM, Guavus (Thales), Ericsson AI | Per-use or enterprise licence | Emerging competition from hyperscaler AI platforms |
| Cloud Infrastructure | AWS, Azure, GCP, OpenStack | Consumption + commit | Telco-specific EDP/MACC with network cloud workloads |
Open RAN (O-RAN) architecture separates RAN hardware from software, enabling multi-vendor network deployments. While Open RAN adoption is still maturing, the credible threat of disaggregation has created genuine leverage with Ericsson and Nokia in radio access network procurement. Document your Open RAN evaluation programme formally — even if incumbent vendor retention is the likely outcome. Ericsson and Nokia have both made commercial concessions to retain customers who have demonstrated Open RAN evaluation commitment.
The single most impactful thing a telco can do for its software commercial position is invest in reducing BSS/OSS switching costs over time. This means: maintaining clean data models with documented integration architecture, negotiating data portability provisions in all BSS/OSS contracts, investing in integration middleware that reduces direct system coupling, and periodically running market evaluations of alternative platforms. This investment pays dividends at every renewal by making migration threats credible.
Any software that prices per network element, per subscriber, or per managed node will automatically increase in cost as the network grows. 5G densification, fibre rollout, and subscriber base growth all drive licence cost growth independent of vendor behaviour. At every renewal, cap the per-element pricing at your projected network scale for the contract term — negotiate the full deployment volume pricing at contract execution, not incrementally as the network grows.
Telecom companies typically negotiate enterprise IT software (SAP, Oracle, Microsoft, Salesforce) separately from network and operations software (Ericsson, Nokia, Amdocs, IBM). Some vendors are present in both domains — Oracle has both ERP and OSS products; IBM has both enterprise analytics and network management platforms. Coordinate negotiations across IT and OSS domains for vendors with presence in both to extract enterprise-level pricing. See our IT contract negotiation strategy for cross-vendor coordination tactics.
Commission a formal Open RAN evaluation for at least one network domain — even if incumbent retention is the likely outcome. A documented evaluation process with alternative vendor PoC results changes the negotiating dynamic with Ericsson and Nokia at RAN software renewal. The evaluation process itself typically delivers 10–20% pricing improvements from incumbents who want to prevent defection before a PoC reveals how competitive alternatives have become.
5G core and edge cloud deployments on AWS, Azure, or GCP create significant cloud infrastructure commitment opportunities. Structure hyperscaler commitments (EDP, MACC, GCP Commit) to account for 5G network cloud workloads — these are typically excluded from enterprise IT cloud commitment discussions. Including network cloud workloads in hyperscaler EDPs can increase commitment levels to qualify for better discount tiers on both IT and network cloud workloads. See our cloud enterprise discount guide.
Telecom CRM is increasingly dominated by Salesforce, which serves both consumer and enterprise customer management. Most telcos have multiple Salesforce deployments (B2C and B2B, with separate clouds and contracts). Consolidating these into a single Salesforce Enterprise Agreement typically delivers 20–30% savings. Use the consolidation conversation to also negotiate Salesforce Communications Cloud (formerly Vlocity, now part of Salesforce Industries) pricing. See our Salesforce contract negotiation guide.
Legacy OSS and BSS platforms on older versions have emerging third-party support options. While third-party support is less mature for telecom-specific platforms than for Oracle and SAP, the principle applies: use the availability or feasibility of alternative support models to negotiate vendor support rate reductions. Vendors who believe they are the only viable support option price accordingly — challenging that assumption changes the dynamic even before a formal third-party evaluation concludes. See our software maintenance negotiation guide.
BSS contracts that price per active subscriber, per rated event, or per invoice generated will automatically increase costs as the business grows — which is exactly the opposite of what a commercial contract should do. Ensure BSS contracts include: volume tier pricing with step-down rates above thresholds, annual caps on cost growth from volume increases (capped at a percentage of the previous year's spend), and the right to renegotiate pricing metrics at defined growth milestones.
Vendors offering 5G core, RAN software, and network management platforms routinely propose multi-year deployment commitments tied to network rollout milestones. These commitments sound reasonable during network planning but become expensive when network rollout timelines slip (which they almost always do). Negotiate 5G software contracts with: deployment timeline flexibility, milestone-based payment structures, and the ability to defer deployment without penalty if network rollout is delayed. See our software contract red flags guide.
Many telecom OSS platforms run on Oracle Database — network inventory, provisioning, and assurance systems often use Oracle as their persistence layer. Oracle's standard licensing terms apply to these deployments, including the virtualisation exposure on VMware environments. Telecom operators running Oracle Database to support OSS platforms have the same audit risk as any other Oracle customer. Quantify this exposure proactively. See our Oracle database licensing guide.
Specialist negotiation advisors with telecommunications sector experience and current benchmarks consistently identify 20–35% in avoidable spend. Start with a no-cost assessment of your BSS, OSS, and enterprise IT positions.