Optiva Alternatives for Operators and MVNOs: Move Up Market, Move Sideways, or Build Your Own

Why teams start looking for an Optiva alternative

Buyers arrive here from two very different places. Some are established operators who chose a challenger platform to escape incumbent pricing and are now asking whether they gave up too much capability, or whether the vendor is large enough to carry them through the next regulatory cycle. Others are MVNOs and connectivity brands who bought a platform to get to market quickly and have discovered that the thing they want to differentiate on, the product, the pricing experiments, the app, the onboarding flow, is exactly the part the platform makes slow to change.

The second group is the more interesting one, because their complaint is strategic rather than commercial. A mobile virtual operator does not compete on network, since the network belongs to the host. It competes on product design, price shape and customer experience. When those live inside a vendor's configuration model and every new idea needs a release slot, the business is renting its own differentiation. That realisation, more than any invoice, is what starts the search.

A third and more mundane trigger is vendor scale. Smaller platform vendors carry a real advantage in attention and price, and a real disadvantage in ecosystem: fewer implementation partners, a smaller hiring pool for people who know the product, and a narrower bench when you need three specialists at once. That is not a criticism of any specific company, it is simply the structural trade of buying from a challenger, and it deserves to be weighed openly rather than discovered during a crisis.

What Optiva genuinely does well

Optiva serves a segment that the largest vendors treat as an afterthought. Tier two and tier three operators, regional carriers and virtual operators need convergent charging, billing and policy that behave properly, and they need it without signing a transformation programme sized for a national incumbent. Meeting that need credibly is worth respecting.

The cloud stance is the other genuine differentiator. Optiva has been public about running its business support software on public cloud infrastructure rather than assuming a data centre deployment, and for a smaller operator that changes the shape of the problem: less hardware to procure, less capacity to buy ahead of demand, and an operational model closer to the rest of a modern technology estate. If your alternative was an on premises install with a hardware refresh cycle, that is a meaningful improvement rather than a marketing line.

Where it actually strains

• Configuration ceilings on product design. Charging and billing platforms express the offers their model can express. Novel structures, partner revenue shares and experimental pricing tend to become development work, which is precisely where a challenger brand wants to move fastest.
• Scope boundaries. A charging and billing platform is not a complete operations stack. Customer relationship management (CRM), self service, dealer channels, order management, SIM logistics and analytics still need to exist somewhere, and the integration between them is your responsibility.
• Ecosystem depth. Fewer certified partners and a smaller specialist labour market means slower ramp when you need external help, and more dependence on the vendor's own delivery capacity.
• Change velocity is bounded by the vendor. However responsive the relationship, your roadmap sits inside somebody else's release plan, which is the same constraint you would face with a larger vendor.
• Licence economics tied to subscribers. Cost that scales with connection count sits awkwardly with low revenue lines such as internet of things or a value brand, where margin per connection is thin by design.
• Data portability. Subscriber records, balances, rated usage and product configuration live in the vendor's model. The size of the extraction project is the real measure of your switching cost, and it is worth quantifying before renewal rather than after.

Your realistic options

• Stay and renegotiate. Bring evidence: the change requests you raised, how long each took, and which should have been configuration. Challenger vendors are often more willing than incumbents to reshape a commercial arrangement to keep a reference customer.
• Move up market. Amdocs, CSG Systems, Netcracker, Comarch and Hansen serve larger operators, and MATRIXX competes specifically on real time charging. You gain depth and ecosystem, you pay considerably more, and you take on a longer implementation. This is right for operators whose complexity has genuinely outgrown the platform, and wrong for anyone hoping a bigger logo will make product changes faster.
• Move to an MVNE. Mobile virtual network enablers run the platform and the host operator relationship for you as a service. This is the fastest path for a brand that wants no technical estate at all, at the price of near total dependence on the enabler for product changes and margin.
• Build your own operations platform. For MVNOs and connectivity brands specifically, this has become a realistic option rather than an ambitious one.

When a custom build pays back

Be precise about what an operations platform for a virtual operator actually contains, because it is smaller than people assume. Product and plan definition. Customer signup, identity checks and onboarding. SIM and embedded SIM inventory and assignment. Provisioning against the host network's interfaces. Usage collection from the host's records. Rating and invoicing, or balance decrement if you sell prepaid. Payments, dunning and refunds. Self service in an app or portal. Care tooling. Regulatory reporting and number portability handling. That is a substantial list and it is a knowable one.

The case for building it is that most of those components are ordinary software problems, and the two that are not, real time credit control and the host network interfaces, can be bought or bounded. If your product does not need live session level credit control, and many enterprise, internet of things and postpaid consumer products do not, you can rate usage on a cycle and skip the hardest component entirely. If it does, buy a charging engine and build everything else around it.

The payoff is speed on the things that decide whether your brand works. Launching a new plan shape in a week. Running a pricing experiment on a cohort. Changing the onboarding flow because the drop off data told you to. An operator whose differentiation is customer experience and product design should own the systems that express both.

The case against is equally clear. If you are a licensed operator with hundreds of thousands of subscribers, mandated regulatory reporting, interconnect settlement and lawful intercept obligations, the surface is far larger and the tolerance for error far smaller. Buy, and negotiate.

Migration reality

Two things dominate the plan: balances and the host operator relationship.

Balances and entitlements move like money. Migrate in cohorts, take a snapshot with activity quiesced, verify totals against the source before switching the live path, and define rollback per cohort including how you treat usage that arrived after the snapshot. Start with staff and test subscribers, then a friendly cohort, then volume.

The host operator side is the item that slips schedules. Provisioning interfaces, usage record formats, testing windows and certification all run on the host's timetable, not yours, and they involve their engineers as much as your own. Get those commitments in writing early, because a platform that is ready and uncertified is not ready.

Around that, plan for SIM inventory reconciliation, number portability processes with their regulated timings, payment mandate and stored card migration with its own compliance rules, tax configuration, and retention of historic usage records for the period your regulator requires. Run a full billing cycle in parallel and reconcile invoice lines individually rather than in aggregate. Retrain care staff before cutover, because they absorb every gap the migration leaves.

Cost bands

Business support platform pricing in this segment is quoted rather than published, generally scaled to subscriber volume with implementation and change delivered as services, and it recurs annually. Enablement services from an MVNE are typically priced per subscriber or as a revenue share, which is comfortable at launch and expensive once you have scale. On the custom side, using what Digital Heroes typically delivers as the frame: a focused first release covering signup, provisioning against the host, usage collection, rating, payments and self service runs roughly $70k to $180k over 12 to 18 weeks. A complete operations platform adding care tooling, dealer channels, SIM logistics, analytics and regulatory reporting runs roughly $150k to $400k. Add a charging engine licence separately if your product genuinely requires real time credit control.

The honest recommendation

Licensed operators with scale and regulatory weight should stay on a supported platform and spend their energy on the commercial terms and on the layers above it. Challenger brands, MVNOs, internet of things providers and connectivity businesses should look hard at building, because the platform is where their product lives and renting it caps how quickly they can compete. If you are somewhere in the middle, take the middle path: buy the one genuinely hard component if you need it, own everything that touches your customer, and make sure that whatever you sign this year, you know precisely what it would cost to leave.