How Telecom Software Vendors Price You
A telecommunications IT contract is priced on metrics that grow automatically with your business. Where a manufacturer might license by named user, a carrier is metered by the subscriber, the connected device, or the business document — units that multiply with every new customer and every new self-service feature. That structural difference is why telecom estates carry some of the largest unbudgeted True-Up exposure of any sector, a pattern we examine across the industry negotiation pillar.
The market is moving fast. In January 2026 Cerillion signed a £42.5m (≈$57.1m) BSS/OSS contract with Omantel — its largest to date — and Tier-1 operators across the Middle East and Europe are replatforming billing and assurance stacks at pace. Every one of those modernisation deals resets the licensing metric, and every reset is a negotiation the operator can either control or concede.
SAP Digital Access: The Telecom Time Bomb
The single largest hidden liability in a telecommunications IT contract is SAP Digital Access. SAP charges for every business document that a third-party system creates in your SAP landscape, and telecom is the worst-case profile: an order management platform that activates a service writes a sales order; a dealer portal that changes a plan writes another; a self-service app does the same at consumer scale. SAP has booked over $1bn in Digital Access revenue since the model launched in 2018.
The arithmetic is unforgiving. A large operator can generate 20–50 million qualifying documents a year. With nine document types — sales, invoice, purchase, service, manufacturing, quality, time, financial and material, the last two counted at 0.2 each — a multi-year audit lookback can produce a back-charge claim in the tens of millions before a single new licence is bought.
We model the customer-defensible document count first, then negotiate. Telecom Digital Access settlements routinely close 60–70% below SAP's opening claim — and DAAP-style conversion deals can still secure 90%+ discounts on the documents you genuinely need to license.
The fix is contractual, not technical. Map every external system that writes into SAP, agree a fixed annual document entitlement, and write a cap on retroactive charges into the agreement. The SAP vendor hub and our SAP S/4HANA guide set out the mitigation clauses in detail.
Oracle BRM and Subscriber Licensing
Oracle Communications products — Billing and Revenue Management (BRM), Order and Service Management, and the wider telco stack — are licensed on subscriber metrics. Oracle's definition is broad: a working telephone number, an activated handset or paging device, a residential cable drop, or a live connected utility meter each counts as a subscriber. Oracle publishes no standard price for these, so two operators of similar size can pay wildly different rates depending on installed base and renewal history.
The exposure is metric drift. If your active subscriber count, or the service definitions Oracle audits against, exceed the licensed position, the resulting True-Up can run from six to nine figures. We treat the subscriber definition itself as a negotiation point — pinning down what counts, excluding suspended and machine-to-machine lines where defensible, and capping annual metric growth. The Oracle vendor hub covers the audit-defence playbook, which overlaps closely with the connected-meter exposure in the energy sector.
OSS/BSS and Managed-Services Levers
Beyond the licensing meters sits the managed-services layer — the OSS/BSS run contracts with vendors such as Netcracker, Comarch, Qvantel and Amdocs. These multi-year deals are where operators quietly overspend: modules licensed but never activated, headroom bought for subscriber growth that never arrived, and support tiers priced as a flat percentage of an inflated licence base.
The levers that work are consolidation and benchmarking applied together. Strategic renegotiation of telecom software and managed-services contracts typically returns 10–25% savings, rising to 25–40% where an operator consolidates vendors and benchmarks rates against market data in the same cycle. Independent benchmarking alone adds 10–15% on top of an internal effort. The discipline mirrors the multi-supplier coordination we describe for logistics and supply-chain estates.
| Telecom Contract Lever | Typical Exposure | Achievable Outcome |
|---|---|---|
| SAP Digital Access claim | Tens of millions (5-yr lookback) | 60–70% below opening claim |
| Oracle BRM subscriber True-Up | 6–9 figures on metric drift | Capped growth + excluded line types |
| OSS/BSS managed services | Unused modules, inflated support % | 10–25% renegotiation saving |
| Vendor consolidation + benchmark | Fragmented multi-vendor spend | 25–40% combined saving |
Building the Telecom Contract Strategy
Sequence is everything. Start 9–12 months before any major billing, ERP, or OSS/BSS renewal — telecom estates are too large and too metric-heavy to reconcile under deadline pressure. First, reconcile your active subscriber count and service definitions against every Oracle and SAP metric. Second, map every system that writes documents into SAP and quantify the defensible Digital Access position. Third, benchmark managed-services rates before the vendor frames the renewal around its own quarter-end.
The objective is to convert open-ended, automatically-growing exposure into fixed, negotiated entitlements — a fixed document count, a capped subscriber metric, a benchmarked support rate. The same regulatory-and-cost discipline applies in adjacent regulated sectors such as financial services and content-heavy operators in media and entertainment. If a telecom renewal or audit is on your horizon, request a confidential briefing and we will model the defensible position before the vendor sets the agenda.