Legacy Modernization
Phased OSS/BSS migration that keeps subscriber operations running.
Telecom
Telecom software for operators who cannot take the BSS down to ship a feature.
Senior engineers for OSS/BSS modernization, subscriber-facing systems, and the integration layer — not a five-nines SLA we did not run on your network.
Telecom software engineering where legacy BSS and live subscribers share a timeline
Telecom delivery is modernization under load: rating and billing, care portals, inventory, and vendor platforms that predate the current team. Maxiom has named telecom and communications work in this repo with British Telecom (BT) and AT&T. We have shipped software since 2002. We do not invent reliability percentages, subscriber counts, or OpEx reductions for a network we are not operating.
- 2002
- Founded
- $100M+
- Delivered
- 98%
- Satisfaction
The problem
BSS you are not allowed to restart
Rating, care, and activation share a timeline with a stack nobody wants to own. Big-bang rewrites are how outages get scheduled.
Vendor platforms as the real architecture
Ericsson, Amdocs, CSG, and home-grown mediation layers are the system. Custom software has to live next to them honestly.
Reliability slogans instead of operations
Five-nines copy on a marketing page is not an SLO. We will talk about failover and monitoring in scope, not as a badge.
Relevant services
Tech Debt Resolution
When mediation, rating, and care have diverged enough that every change is an incident risk.
Tech Debt ResolutionAI Code Oversight
Senior review of AI-assisted code on identity, mediation, and billing-adjacent paths.
AI Code OversightFederal and Government
When the telecom work sits inside a government or contractor security boundary.
Federal and GovernmentNot sure which path?
A thirty-minute scoping call. We will map the right engagement — or tell you if we are not the fit.
British Telecom (BT)
Enterprise telecom software work documented in our case studies — not a subscriber-count badge.
AT&T
Named communications engagement in this repo. Government-adjacent AT&T work also shows up on the federal page.
Since 2002
$100M+ delivered, 221+ clients, Clutch-reviewed. No invented five-nines claim.
- NDA signed before access
- Read-only repository only
- Senior engineers every time
- Report in 10 business days
Frequently asked questions
What telecom engineering does Maxiom do?
OSS/BSS modernization, subscriber and care portals, and integration against incumbent vendor stacks. Incremental strangler work so rating, care, and activation keep running.
Which telecom clients are named here?
British Telecom (BT) and AT&T appear as case studies in this repo. Federal/contractor communications work is a separate conversation on /industries/federal/.
Do you follow TM Forum Open APIs?
When the operator’s architecture already does. We will not pretend every engagement is a greenfield Frameworx implementation. Scope names the interfaces you actually expose.
Can you modernize a legacy BSS without a cutover weekend?
That is the job: wrap, strangle, and migrate capabilities. We will not promise zero disruption as a slogan. We will write the sequence and the rollback.
Is 5G / MEC / network slicing in scope?
Only if that is the actual program. Most buyers on this page need billing, care, and inventory to stop being a museum. We will not lead with a 5G tile to look current.
Will you review AI-generated telecom code?
Yes. AI code oversight on mediation, rating-adjacent, and identity paths. Client code stays in your environment and is not sent through third-party AI tools.
How do telecom engagements start?
A scoping call on the BSS/OSS map, vendor lock-in, and whether this is portal work, integration, or a multi-year modernization. Written scope and NDA first.
Who staffs the work?
Senior engineers. A named engineer owns the engagement.