Builds and runs the billing software that mobile carriers use to charge customers for every call and data session.
At a glance
- Depends onDownstream position: depends on 18 industries, supplies 5
- ScaleMarket cap is above the global median
Builds and runs the billing software that mobile carriers use to charge customers for every call and data session.
Amdocs builds the billing software that mobile carriers use to rate every call, text, and data session in real time — tracking each record against the interconnect settlement rules and revenue assurance logic that determine what a carrier charges and what it owes other networks. Because that software has to run without interruption while understanding both TMF billing standards and the protocol stacks of equipment vendors like Ericsson and Nokia, it can only be built by engineers who hold telecom domain knowledge and carrier-grade software skills at once, a combination that Amdocs has accumulated over years inside its Israel and India development centers. Each new carrier deployment adds another layer of jurisdiction-specific regulatory certification and custom API work written by those same engineers, so the finished system is inseparable from the team that shaped it — a carrier that wants to leave must spend twelve to twenty-four months rebuilding every integration from scratch with a new vendor while keeping live billing running the whole time. The thing that makes switching so costly is also the thing that makes Amdocs hard to rebuild: the shared understanding of why the codebase looks the way it does lives inside those development teams, and if geopolitical restrictions or aggressive recruiting were to hollow out those centers faster than the knowledge could be passed on, it could not be reconstituted before carriers were forced to start migrating away.
How does this company make money?
The company signs multi-year licensing contracts with telecommunications carriers to use its billing software. On top of that, it charges professional services fees each time a new carrier system is implemented or customized. It also collects ongoing maintenance and support fees, which are tied to how many subscribers a carrier has and how many transactions the system processes — so revenue grows as the carrier's own customer base grows.
What makes this company hard to replace?
Replacing this software means running a 12-to-24 month migration cycle while keeping live billing systems running. Every custom API built for that carrier's specific network must be rebuilt from scratch with a new vendor's team. Regulatory compliance certifications do not transfer — they must be re-established with the new system. And all the carrier-specific customizations already paid for cannot be moved to a competitor's platform; they have to be recreated at full cost.
What limits this company?
Growth is capped by how many engineers the company can find who understand TMF billing frameworks, interconnect settlement rules, and carrier-grade software development all at once. Adding 5G makes this harder, not easier — 5G charging logic sits on top of the existing billing architecture rather than replacing it, so every new hire must master the old system and the new one before they can touch a live carrier deployment.
What does this company depend on?
The company cannot operate without TMF standards from the TeleManagement Forum, which define how carrier billing must work. It relies on Oracle and cloud infrastructure platforms to host systems at carrier-grade reliability. It depends on protocol stacks and APIs from equipment vendors like Ericsson and Nokia to connect billing logic to actual network hardware. And it must track regulatory compliance frameworks that differ by country and jurisdiction.
Who depends on this company?
Tier-1 mobile operators like T-Mobile and Vodafone depend on it for billing accuracy — if the system fails, customers get wrong charges and the carrier's service experience breaks down. Communications service providers need its real-time charging capabilities to run 5G monetization at all. Enterprise telecom customers lose B2B service provisioning if the orchestration systems go offline. And telecom regulators lose the compliance reporting they require from carriers if carrier management systems stop working.
How does this company scale?
Once a billing module is built and tested, it can be deployed across additional carrier customers without being rewritten from scratch. But that is where the easy part ends — every new carrier requires custom integration with its own back-office systems, a separate regulatory compliance certification for its jurisdiction, and legacy API mapping that cannot be reused from another carrier's deployment. The engineering work required for each new customer does not shrink as the company grows.
What external forces can significantly affect this company?
European regulations like GDPR and data localization laws in other countries force the company to change how its software stores and moves data, sometimes requiring architectural redesigns. 5G spectrum auctions and deployment timelines set the pace at which carriers modernize their systems, which determines when and how fast new contracts come in. Geopolitical restrictions on technology transfer create direct risk to the Israel and India development centers where the core engineering work happens.
Where is this company structurally vulnerable?
If geopolitical restrictions on technology transfer disrupted the Israel or India development centers, or if cloud infrastructure providers systematically recruited those engineers away, the shared context that makes TMF-plus-5G development possible would begin to fall apart. Because that knowledge is not fully captured in documentation or the codebase itself, it cannot be rebuilt elsewhere in less time than the 12-to-24 months it would take a carrier to migrate away — leaving carriers in the difficult position of deciding whether to start leaving before the gap got worse.
Sign in to view price data.
Sign inStructural observations derived from financial data, industry benchmarks, and supply chain position.
Companies that share the same coordination system — how they create, deliver, or capture value.
Companies that share active interpretations — structural patterns currently present in both stocks.
Screen for dividend patterns
Find other stocks with similar dividend characteristics in the screener.
CompanyGraph