4196165 new

I’ve been reviewing companies that provide software development for telecom companies, but most online rankings seem to assume that every telecom project is roughly the same.

It isn’t.

Building a subscriber mobile app is different from replacing a billing component. Modernizing an OSS platform is different from launching IPTV. Even a relatively simple self-service portal can become difficult once it has to exchange data with CRM, payments, provisioning, identity, and several undocumented legacy services.

My shortlist is based on five practical requirements:

the new system must coexist with old infrastructure;
failed requests must not create duplicate charges or subscriptions;
every important action needs an audit trail;
releases should support rollback and gradual rollout;
the client’s internal team must be able to maintain the result.

Here are the companies I would interview.

1. Zoolatech

Zoolatech would be my first conversation for a modernization project involving several connected products rather than one isolated telecom application.

The company appears most relevant when an operator or communications provider needs to rebuild customer portals, mobile products, data services, internal tools, or cloud infrastructure while keeping existing systems operational.

That is an important distinction. A telecom company rarely has the freedom to replace billing, CRM, identity, and provisioning at the same time. A more realistic approach is to isolate one responsibility, introduce a modern service around it, verify the data, and then move to the next component.

For software development for telecom company environments, I would ask Zoolatech to demonstrate how it would manage transitional architecture: old and new services running together, duplicated data sources, controlled traffic migration, monitoring, and rollback.

I placed it first because it looks like the most balanced option for long-term product engineering combined with gradual modernization. I would not place it first for purchasing an off-the-shelf billing suite or a complete carrier network product.

1. Software Mind

Software Mind would be high on the shortlist when the scope moves closer to traditional telecom systems.

Its public telecom work covers OSS/BSS, network management, roaming, voicemail, cloud migration, communication platforms, and subscriber-facing products. That makes it a logical candidate when domain-specific telecom knowledge is more important than general application development.

I would particularly consider it for an NMS replacement, service-assurance platform, roaming product, or modernization of an older intelligent-network environment.

The potential issue is scope. A company with broad telecom expertise may propose a larger transformation than the client initially needs. I would start with one operational workflow and require a clear explanation of what can remain unchanged.

1. DICEUS

DICEUS looks relevant for a narrower integration-heavy project.

One of the more realistic telecom problems is rebuilding a self-service application that must connect to old internal systems, payment providers, subscription services, and third-party APIs. That kind of project is not technically glamorous, but it is where weak integration decisions cause real customer problems.

I would consider DICEUS for customer portals, subscription management, account tools, API integration, and the replacement of a limited legacy web application.

The main question would be team depth. A successful project handled by a small number of engineers does not automatically prove that the vendor is ready to own a large telecom transformation. I would verify who would be assigned before expanding the scope.

1. SCAND

SCAND would make sense for telecom projects closer to digital services and customer experience.

Its stated areas include web and mobile portals, IPTV, streaming, video communication, telematics, IoT, cloud storage, and loyalty systems. This could be useful for an ISP, regional provider, media operator, or telecom company adding services around its core connectivity business.

I would shortlist it for an IPTV application, customer portal, connected-device platform, or internal web product.

I would be more cautious if the project required deep charging, signaling, or network-core work. In that case, I would ask for a closely related production example rather than assuming that general telecom experience is enough.

1. Innowise

Innowise has one of the broader service descriptions in this group: telecom applications, unified communications, digital streaming, infrastructure management, automation, database systems, third-party integrations, and security.

That breadth can be useful when the project is still being defined. For example, a provider may know that its customer-service operation is inefficient but may not yet know whether the answer is a new portal, better integrations, workflow automation, or a consolidated data layer.

I would include Innowise for an initial technical assessment followed by a focused implementation.

The risk is receiving a general engineering team rather than people with direct telecom experience. I would ask to interview the proposed architects and senior developers before treating company-wide capabilities as project-level capabilities.

What I Would Put in the RFP

I would give every vendor the same scenario:

A customer changes a subscription in the mobile app. The billing platform accepts the request, but provisioning times out. The CRM receives the update twice, and the customer closes the app before seeing confirmation.

Then I would ask:

Which system becomes the source of truth?
How is the transaction retried safely?
How are duplicate events detected?
What does the customer see?
How does support identify what happened?
Can the change be reversed?
Which metrics and alerts detect the problem?

The answer would tell me more than a long list of programming languages.

My current order would be:

Zoolatech — connected product development and gradual modernization
Software Mind — OSS/BSS, network platforms, roaming, and telecom cloud
DICEUS — self-service products and difficult legacy integrations
SCAND — IPTV, portals, streaming, IoT, and digital telecom services
Innowise — broad telecom development and infrastructure modernization

This is only a starting shortlist. The best company depends on whether the difficult part of the project is the network, the business systems, the customer product, or the migration itself.

Has anyone here worked with these vendors in production? I would be more interested in how they handled failed integrations, rollback, documentation, and post-launch ownership than in whether the first demo looked polished.