The software sat across them like a conductor managing an orchestra of incompatible instruments.
In the ongoing human effort to make complex systems cooperate, UiPath's Maestro platform found a meaningful proving ground in New Zealand's telecommunications infrastructure, where decades of layered legacy technology had resisted the simple promise of seamless service. Rather than demolishing what existed, the platform assumed the role of interpreter between incompatible systems, enabling One New Zealand to provision mobile services in near real-time. The customer's decision to extend the deployment beyond its original scope speaks to a quiet but consequential truth: the most durable enterprise technology often solves not the newest problems, but the oldest ones.
- One New Zealand faced a structural contradiction — modern service expectations colliding with legacy infrastructure that was never designed to work as a unified whole.
- Maestro entered not as a replacement but as an orchestration layer, threading data between siloed systems fast enough to make near real-time mobile provisioning possible without a costly overhaul.
- The initial deployment succeeded, and the customer is now expanding Maestro into additional mission-critical workflows — the clearest signal that a pilot has become a platform.
- UiPath's stock trades nearly 45% below internal fair value estimates, reflecting investor uncertainty about whether this kind of win can be replicated reliably across industries and at scale.
- Execution risk remains the central tension: Maestro must perform without failure in environments where downtime is immediately visible to customers, and one reference win does not yet constitute a repeatable playbook.
UiPath announced in mid-June that its Maestro platform had been deployed by One New Zealand, the country's telecom operator, to solve a problem familiar to large enterprises everywhere: multiple legacy systems running in parallel, none communicating cleanly with the others. The operator needed to provision mobile services in near real-time, but its patchwork infrastructure made that nearly impossible without a full replacement.
Maestro took a different approach — sitting across the existing systems like a conductor, pulling data from one, transforming it, and pushing it to another quickly enough that customers could activate service almost immediately. The rollout worked, and One New Zealand moved to extend the platform to other mission-critical processes, the kind of expansion that separates a proof-of-concept from a genuine business win.
For investors, the case illustrates UiPath's core proposition: not replacing enterprise systems, but becoming the automation layer that makes legacy infrastructure behave as though it were built yesterday. Telecom operators are a natural fit — they routinely run 1990s billing systems alongside last year's cloud platforms, and everything must somehow work together.
The stock trades at roughly 21% below analyst consensus and nearly 45% below the company's own fair value models, a gap that reflects lingering doubt about whether UiPath can repeat this kind of success at scale and across sectors. Execution risk is real — Maestro must perform reliably in environments where failures are noticed within minutes. One New Zealand's confidence is encouraging, but the open question remains whether UiPath can build a repeatable playbook from individual wins, and whether that playbook can justify the distance between where the stock trades today and where its valuation models suggest it belongs.
UiPath announced in mid-June that its Maestro platform had been deployed by One New Zealand Limited, the country's telecom operator, to untangle a particularly knotty workflow problem. The challenge was familiar to large enterprises everywhere: multiple legacy systems running in parallel, each doing its job but none talking cleanly to the others. One New Zealand needed to provision mobile services in near real-time, but the existing infrastructure—built over years, replaced piecemeal, never fully integrated—made that nearly impossible without a complete overhaul.
Maestro, UiPath's orchestration layer, offered a different path. Rather than rip out the old systems, the software sat across them like a conductor managing an orchestra of incompatible instruments. It pulled data from one system, transformed it, pushed it to another, all fast enough that customers could activate service almost immediately. The initial rollout worked. One New Zealand saw the value and began extending Maestro to other mission-critical processes—the kind of expansion that separates a proof-of-concept from a real business win.
For investors tracking UiPath's stock, the One New Zealand case matters because it illustrates the company's core argument about where it fits in the enterprise software landscape. UiPath is not trying to replace the systems that run large organizations. It is trying to be the glue between them, the automation layer that makes legacy infrastructure behave like it was built yesterday. Telecom operators are particularly good examples of this problem: they run billing systems from the 1990s alongside cloud platforms from last year, and somehow it all has to work together.
The stock itself trades at $10.55, roughly 21 percent below the consensus analyst target of $13.31, and the company's own valuation models suggest it is undervalued by nearly 45 percent. The share price has climbed 11.4 percent over the past month, but the gap between current price and fair value remains substantial. That gap exists partly because investors are still uncertain whether UiPath can repeat wins like One New Zealand at scale, in different industries, without stumbling.
Execution risk is real. Maestro has to work reliably when it is managing workflows that cannot fail—when a telecom operator's provisioning system goes down, customers notice within minutes. UiPath has to prove it can handle that pressure repeatedly, across different sectors, without outages or cost overruns that eat into the customer's savings. One New Zealand's decision to expand the deployment suggests confidence in the platform, but one customer's success does not guarantee the company can build a repeatable playbook.
What the One New Zealand deployment does show is that there is genuine demand for this kind of orchestration layer in large, established enterprises. The telecom operator did not need a flashy new system; it needed something that made its existing systems work better together. That is a less exciting pitch than artificial intelligence or cloud transformation, but it is the kind of problem that affects thousands of enterprises and generates steady, substantial revenue. For UiPath, each reference win like this one helps clarify the product's role and builds credibility with the next prospect facing the same problem. Whether that translates into the kind of growth that justifies the current valuation gap remains the open question.
Notable Quotes
One New Zealand is now extending Maestro to additional mission critical processes after the initial rollout.— UiPath announcement
The Hearth Conversation Another angle on the story
Why does it matter that One New Zealand is expanding Maestro to other processes? Couldn't that just be normal customer growth?
It matters because it shows the customer saw enough value in the first deployment to trust Maestro with additional mission-critical work. That's the difference between a one-off project and a platform becoming embedded in the business.
What's the actual problem Maestro solves that the telecom operator couldn't solve before?
One New Zealand had multiple legacy systems that didn't talk to each other cleanly. Provisioning a mobile service required manual steps or slow batch processes. Maestro sits between those systems and orchestrates the workflow in near real-time, without replacing any of the underlying infrastructure.
Is that a big deal, or just incremental improvement?
It's the difference between a customer waiting hours or days for service activation and getting it in minutes. For a telecom operator, that's competitive advantage. And it's a problem that affects thousands of large enterprises.
The stock is trading well below fair value. Why hasn't the market priced in wins like this?
Because one customer win doesn't prove UiPath can repeat it reliably across different industries and at larger scales. Execution risk is the real question—can they handle mission-critical workflows without failures?
What would change the narrative?
A pattern of similar deployments expanding into broader enterprise footprints, especially in different sectors. One New Zealand is a strong reference, but it's still one reference. The market wants to see if this is repeatable.
Does the fact that they're not replacing legacy systems make this easier or harder for UiPath?
Easier in one sense—enterprises don't have to undertake massive, risky infrastructure replacements. Harder in another—UiPath has to prove it can work reliably as a middleman between systems it doesn't control.