Circles Software Spinoff Separates Its Telco Platform From Circles.Life

Circles Group is spinning off its telecom software business, despite previously keeping that platform beside its consumer mobile operation. The Circles software spinoff gives the platform greater independence and creates an opening for a new technology or investment partner.

The Singapore-based group confirmed the separation during a strategic review, according to the reported separation. Spokesperson Fabian Sossa said Circles wants a partner or technology investor for the platform’s next growth stage.

That structure reverses the logic behind Circles’ original advantage. Its software emerged from operating Circles.Life, giving developers a live consumer business where they could test digital telecom products. Independence can make the platform easier to fund and sell globally, but it also weakens that direct organizational connection.

The decision therefore carries more weight than a routine corporate reorganization. Circles must show that its software can compete as an independent vendor, not merely as technology developed inside a digital operator.

What the Circles Software Spinoff Changes

Circles is separating the business that sells digital telecom software from the group that operates Circles.Life.

Bloomberg reported that Circles is working with a financial adviser and has contacted possible investors. Those parties reportedly include technology companies and private equity firms. The exact process, valuation, potential investors, and transaction terms remain undisclosed.

The company describes the change as a separation that will let the platform invest according to its own growth requirements. That wording suggests more than internal accounting. It points toward a business with distinct capital needs, partners, management priorities, and possibly separate ownership.

Circles has not publicly identified the new entity’s final name, ownership structure, management team, or legal completion date. It also has not said whether existing shareholders will retain full control after the separation.

Those omissions matter because “spinoff” can describe several arrangements. A company can distribute shares to existing owners, establish a controlled subsidiary, or admit an outside investor. It can also prepare a business for a later sale.

For now, the verified event is narrower. Circles is separating its telecom software operation and seeking a partner for its next stage. Any claim that a complete sale has already occurred would go beyond the available evidence.

The business being separated supplies software to telecom operators launching or modernizing digital services. Circles says its operator footprint extends across 15 countries and six continents. Named partners include KDDI, e&, AT&T, and Telkomsel.

Its technology supports activities that sit above the physical mobile network. These include customer onboarding, subscription management, billing interactions, digital storefronts, support, personalization, and product launches.

Such functions often fall within business support systems, or BSS. A BSS manages commercial operations such as customer accounts, orders, charging, and service plans. It differs from the network equipment that carries mobile traffic.

Circles also owns Circles.Life, its consumer-facing digital mobile business. Circles.Life operates without building a nationwide radio network of its own. It instead uses infrastructure supplied by established network operators under commercial agreements.

This combination gave Circles two roles. It competed for mobile customers while also selling software and operating experience to other telecom companies.

The separation draws a clearer boundary between those roles. Telecom customers will deal with a software-focused company, while Circles.Life remains a consumer operator within the broader group.

That distinction could reduce a sensitive sales objection. An operator evaluating Circles’ platform might hesitate to share product plans and customer data with a supplier that also runs a mobile brand.

An independent platform has a cleaner answer. Its commercial purpose becomes serving operators, rather than balancing their interests against a related consumer business.

However, legal separation does not automatically eliminate concerns about data governance, intellectual property, or shared employees. Those details depend on contracts and the final ownership arrangement.

The Circles software spinoff should therefore be judged through its operating boundaries. Customers need to know which entity controls their data, develops the platform, and accepts responsibility when services fail.

Why Independence Matters Now

The platform needs capital and commercial neutrality at the same time that telecom software is becoming more expensive to build and harder to replace.

Circles launched its cloud-native software platform in 2019 after developing technology for its own digital mobile operation. Cloud-native software uses modular services designed to run and scale across cloud infrastructure.

A 2023 account of the platform build said Circles helped launch an Indonesian digital brand in less than 60 days. That figure came from Circles through a Google Cloud customer story.

The same account said its teams could release products weekly. Circles attributed that speed to modular architecture, automated delivery practices, and infrastructure running on Google Cloud.

Those capabilities require sustained spending. Telecom platforms must handle sensitive account data, integrate with network and billing systems, and remain available during constant customer activity.

They must also accommodate different regulations, currencies, tax rules, product catalogs, and identity systems. Every new market can introduce integrations that do not transfer neatly from another deployment.

Artificial intelligence has added another investment layer. Circles is building automated support and personalization services that connect customer histories, account actions, and real-time behavior.

A recent account of its AI deployments reported that CareX, its multi-agent support architecture, resolves 65% of supported customer interactions without human intervention. Circles also reported a 22% increase in average revenue per user among customers receiving AI recommendations in Singapore.

Those numbers illustrate the platform’s commercial pitch, but they need careful interpretation. The publication describes Circles’ implementation and relies on measurements supplied by the participating companies.

It does not provide a complete independent audit, market comparison, or deployment-wide sample. Results from one operating environment might not transfer to another operator with different data and processes.

Still, the product direction is clear. Circles is moving beyond launching digital mobile brands. It wants its software to influence support costs, customer retention, product recommendations, and revenue growth.

That expansion increases the platform’s addressable work, but it also increases technical and regulatory obligations. Automated systems touching bills, subscriptions, and personal data require controlled access and reliable escalation.

Circles says its architecture limits each AI agent to the information needed for a specific task. The company also describes encryption, human escalation, phased releases, rate limits, and rollback controls.

An independent business can direct capital toward these platform requirements without competing against the consumer operation’s marketing and network costs. It can also hire leaders whose incentives reflect software growth rather than mobile subscriber growth.

The search for a partner offers another advantage. A technology investor could contribute infrastructure, distribution, product expertise, or access to enterprise customers.

A financial investor would bring different strengths. It might support acquisitions, expand sales capacity, or prepare the platform for a future transaction.

Yet outside capital creates expectations. Investors normally want measurable recurring revenue, improving margins, durable contracts, and a credible path toward liquidity.

Circles has not disclosed the platform’s revenue, profitability, customer concentration, retention, or contract backlog. Without those figures, outsiders cannot determine whether the separation reflects momentum, capital pressure, or both.

The timing also follows an earlier restructuring pattern. In December 2024, Circles announced the Jetpac separation of its travel eSIM business.

Circles said that move created room for additional strategic partners. It paired the decision with leadership appointments and an expansion of its software business into the Americas.

The latest separation goes further because the software platform sits near Circles’ original strategic center. It is the technology built from the group’s experience running Circles.Life.

That makes independence a test of whether the platform has matured beyond its internal proving ground.

The Main Tradeoff Is Independence Versus Operator DNA

Circles gains focus by separating its software, but it risks weakening the operating feedback loop that made the platform distinctive.

Large telecom software vendors often sell deep integration, global support, and decades of deployment experience. Smaller cloud vendors usually compete through speed, modularity, and more flexible product development.

Circles positioned itself between those groups. It sold cloud software while claiming practical knowledge gained from running a digital mobile operator.

That “operator DNA” was not only a marketing phrase. Circles.Life gave product teams exposure to real activation failures, billing questions, customer complaints, plan changes, and churn.

A software team can learn from those events faster when the operator sits inside the same organization. Product managers can observe where customers abandon a signup flow or misunderstand a roaming option.

Developers can also test changes against a live operating environment. They can see whether a technically correct feature reduces support work or creates another exception.

This model differs from traditional vendor relationships. A conventional supplier often receives requirements through contracts, governance meetings, and formal change requests.

That distance protects accountability but slows learning. It can also turn a product problem into a negotiation over customization, responsibility, and cost.

The Circles software spinoff makes the organization look more like a conventional supplier. That can improve focus and reassure customers, yet it adds distance from Circles.Life.

The effect will depend on the agreements connecting the two businesses. Circles.Life could remain a flagship customer, testing partner, or reference deployment for the independent platform.

A long-term product agreement would preserve part of the feedback loop. Shared data must still follow clear consent, security, and governance rules.

The platform could also gain better feedback from external operators. Independence may encourage customers to participate in road maps without fearing that their insights help a related consumer competitor.

That benefit grows as Circles serves operators with different commercial models. A product designed around one digital brand can become more reusable after confronting varied markets and legacy systems.

However, customer requests can pull a platform in conflicting directions. One operator might want a complete managed stack, while another wants modular components inside its existing architecture.

One market might permit public cloud processing for customer data. Another might require local hosting, private infrastructure, or stricter control over automated decisions.

An independent Circles will need to decide where configuration ends and custom development begins. Too much customization can turn subscription software into a services business with uneven margins.

Too little flexibility can exclude major carriers whose billing and operational systems cannot be replaced quickly. Telecom modernization rarely begins with an empty technical environment.

The company’s central promise is therefore under pressure from both sides. Circles needs enough standardization to scale and enough adaptability to integrate with complex operators.

Its AI strategy sharpens that tension. Automated support works best when systems can access current account, product, and usage information.

Each integration introduces dependencies and permission questions. An agent cannot safely change a subscription unless identity, eligibility, billing, and rollback processes agree.

A demonstration inside Circles.Life does not settle those issues for another carrier. External operators use different systems and apply different risk controls.

The separated platform must prove that its operating knowledge is transferable. It cannot rely forever on the argument that one affiliated mobile brand validates the entire product.

Independence succeeds if Circles preserves practical learning while becoming neutral enough for more operators. It fails if separation removes the advantage without removing integration complexity.

A Crowded Telecom Software Market Raises the Stakes

Circles is not entering an empty category, and independence makes direct comparison with established software vendors unavoidable.

Telecom operators have spent years replacing tightly connected billing and operations systems with cloud-based components. The work remains difficult because these systems support services that customers expect to function continuously.

Operators also carry years of product rules, discounts, account histories, and regulatory obligations. A migration must preserve that logic while improving development speed.

TM Forum says operators reconsider BSS suppliers based on cost, cloud alignment, software strategy, and partner ecosystems. Its review of supplier priorities also notes that privacy rules can limit public-cloud deployments.

Those criteria create an opportunity for Circles. A cloud-oriented platform can appeal to operators seeking faster product launches or a separate digital brand.

The platform can also support a gradual strategy. An operator might launch a new digital service without immediately replacing every legacy billing and customer system.

That approach lowers the initial migration scope. It lets the operator test customer demand before attempting a company-wide transformation.

Circles has used this entry point with partner brands. Its public materials cite projects involving KDDI, e&, AT&T, Telkomsel, and other operators.

However, the company competes with several vendor groups. Ericsson and Amdocs offer broad telecom software portfolios and long-standing relationships with major carriers.

Netcracker, Optiva, Cerillion, and other specialists sell billing, charging, customer management, and digital monetization systems. Systems integrators also assemble platforms from several suppliers.

Some large operators build more software internally. Open standards and modular architectures can help those carriers reduce dependence on one vendor.

Each route offers a different tradeoff. A broad incumbent can assume responsibility across more systems, but its projects can become large and complicated.

A focused cloud platform can move faster in a defined area. It still has to connect with everything that remains outside that area.

Internal development provides control and customization. It requires engineering talent that smaller operators may struggle to recruit and retain.

Circles’ most credible position lies between a full legacy replacement and a collection of isolated applications. It can provide a pre-integrated digital operating layer while connecting to existing network infrastructure.

That pitch becomes stronger when deployment speed produces measurable business results. It weakens when implementation depends on extensive bespoke work.

The separated company will need evidence that customers can repeat successful deployments. Case studies should identify implementation scope, operating conditions, and measurement periods.

Customer concentration is another competitive issue. Enterprise telecom contracts are large, slow to win, and difficult to replace.

A platform with a short list of major clients can grow quickly after one contract. It can also suffer when one customer delays an expansion or changes suppliers.

Circles has named prominent partners but has not released revenue concentration figures. The difference between pilot projects and broad production deployments is also not always visible publicly.

Independent governance could help operators evaluate that distinction. A software-focused company can publish clearer product metrics, security practices, release schedules, and customer retention data.

The investor process could also reveal how strategic buyers value the platform. Interest from another technology company might validate its product position or supply a larger distribution channel.

Private equity interest would carry a different signal. It could indicate confidence in recurring contracts, but it might also introduce pressure for faster margin improvement.

Neither form of interest guarantees a successful transaction. Prospective investors will examine revenue quality, renewal risk, implementation costs, intellectual property, and liabilities shared with Circles.Life.

The market will ultimately measure the platform against alternatives, not its origin story. Independence removes one organizational ambiguity while exposing its economics to closer scrutiny.

The Separation Leaves Important Questions Unanswered

Circles has explained the strategic logic, but it has not supplied enough financial or operational detail to evaluate the separation fully.

The first uncertainty concerns ownership. Circles says it wants a partner or technology investor, yet it has not said how much control that party might receive.

A minority investment would leave the existing owners in command. A majority transaction could change strategy, leadership, staffing, and customer relationships.

The second question concerns the platform’s perimeter. Circles offers several software capabilities, digital advisory services, and AI products.

The company has not specified which assets, employees, contracts, patents, or product names will move into the separated business. It has not explained whether Circles.Life will license the same technology.

That boundary affects both sides. The platform needs control over its road map and intellectual property. Circles.Life needs predictable access to software supporting its consumer operation.

The third uncertainty concerns financial performance. Circles has not published separate revenue, margin, cash flow, or growth figures for the platform.

Customer logos and geographic reach establish market presence, but they do not reveal contract value or profitability. They also do not show how much revenue comes from implementation work.

That difference matters for investors. Recurring software subscriptions usually offer greater visibility than project-based integration and consulting.

Telecom platforms often combine both. Early deployments can require substantial configuration, migration, testing, and operational support before recurring revenue becomes meaningful.

The fourth question is whether customers benefit from the change. A new corporate entity could simplify contracting and clarify accountability.

It could also require contract transfers, new service agreements, or revised data-processing terms. Customers will want continuity during any ownership transition.

The fifth uncertainty involves independence itself. A platform separated from Circles.Life might gain neutrality, but common shareholders and shared services can preserve perceived conflicts.

Investors and operators will examine board composition, management authority, information barriers, and related-party agreements. Branding alone will not resolve those concerns.

The sixth question concerns AI performance. Circles has reported encouraging results, including automated support resolution and higher revenue from personalized recommendations.

Those figures need broader validation across external operator environments. Different languages, regulations, product catalogs, and customer behaviors can change outcomes.

Autonomous resolution also requires a precise definition. A closed interaction does not always mean a customer received the correct or satisfactory answer.

Operators should examine repeat contacts, complaint rates, escalation patterns, billing corrections, and customer satisfaction. Cost savings alone do not establish service quality.

The technology must also function when underlying records conflict. Telecom accounts can contain complex family plans, promotions, roaming events, and device financing obligations.

A system that reads the wrong entitlement can create financial harm quickly. Human review and reversible actions remain important even when automation rates rise.

Circles acknowledges several safeguards, including scoped data access and human escalation. The separated company must show how those controls work under each operator’s policies.

Finally, there is execution risk during the corporate transition. Leadership attention can shift from product delivery toward negotiations, legal structures, and investor diligence.

Employees may face uncertainty about reporting lines or equity arrangements. Competitors can use that period to question continuity during customer evaluations.

None of these risks means the strategy is mistaken. They explain why the announcement should be treated as the start of a process, not proof of its outcome.

Three Signals Will Show Whether the Spinoff Works

The next evidence should come from transaction terms, customer commitments, and operating results rather than broader transformation claims.

The first signal is the identity and role of the new partner. A technology company could strengthen product development, infrastructure, or distribution.

Its involvement could also reduce platform neutrality if that company competes with a customer’s preferred cloud or software suppliers. The ownership percentage and governance rights will therefore matter.

A financial investor would raise another set of questions. Readers should watch whether new capital funds engineering and market expansion or mainly provides liquidity to existing shareholders.

A completed transaction with dedicated growth funding would strengthen Circles’ independence argument. A prolonged process without disclosed terms would leave the strategic review unresolved.

The second signal is a major customer renewal or new deployment signed by the separated entity. The strongest validation would involve a recognized operator adopting several platform components in production.

A pilot, memorandum, or innovation workshop would provide weaker evidence. Telecom vendors often announce partnerships well before workloads reach meaningful scale.

Watch for the number of subscribers migrated, the services placed in production, and the implementation timeline. Those details reveal more than a partner logo.

Existing customers also matter. Renewals would show that operators accept the new ownership and contracting structure.

Contract losses or delayed deployments would weaken the case that separation improves focus. They could also indicate transition concerns rather than product weakness, so context will remain important.

The third signal is a clearer set of operating metrics. Circles should distinguish platform revenue from services revenue and identify how much business repeats annually.

It should also explain customer concentration, renewal performance, deployment costs, and progress toward profitability. Private ownership does not require full public reporting, but prospective partners will demand those figures.

Product measures should accompany the financial data. Deployment frequency, implementation time, service availability, and change failure rates can show whether the platform operates consistently.

AI features need outcome measures beyond automation. Resolution accuracy, repeat-contact rates, customer satisfaction, and successful human escalation would provide a fuller picture.

Comparable reporting across multiple operators would strengthen the claim that Circles’ methods travel well. Results confined to Circles.Life would preserve the central doubt about transferability.

The Circles software spinoff has a coherent strategic purpose. It can give the platform dedicated capital, clearer accountability, and a more neutral position with telecom customers.

The cost is equally clear. Circles must preserve the operator feedback that shaped its technology while proving it can stand independently in a crowded market.

Enterprise buyers should follow the structure closely before treating the announcement as a product verdict. Ask who controls the new company, which contracts move, and how customer data remains separated.

Then watch the deployments. If independent customers renew, expand, and document repeatable results, Circles will have validated the separation.

If those signals remain absent, the spinoff will look more like financial restructuring than evidence of a stronger telecom software business.