If Robotiq.ai bots run inside your bank, insurer or telco, the next eight weeks are the only point at which you have leverage over what happens to them. HCLSoftware announced on September 28, 2026 that it will buy the Zagreb RPA vendor and fold it into HCL UnO Agentic, with closing expected in November. The release describes the strategy in detail and your contract in no detail at all — nothing on standalone licences, support terms, pricing or the product roadmap. For an EU financial entity, that silence is exactly the kind of "material change" DORA expects you to act on before it becomes a fact.
This is a small deal. That is precisely why nobody will call you about it.
What Is HCL Actually Buying for €9 Million?
HCL is buying a profitable but tiny software company whose value to HCL is a capability, not a customer base. According to HCLTech's stock-exchange disclosure, as reported by Whalesbook, HCL Technologies Austria GmbH is acquiring 100% of the equity of Robotiq.ai, a company founded in 2018, for €9 million. Robotiq.ai booked €1.4 million of revenue and €0.2 million of profit in 2025.
FourWeekMBA's read of the same filing adds the rest of the shape: an all-cash deal at an enterprise value of €9 million subject to post-closing adjustments, completion expected by the end of November 2026, revenue of €0.9 million in both 2023 and 2024 before the 2025 jump, and net worth of €0.8 million at the end of 2025. By that publication's arithmetic, HCL is paying about 6.4x trailing revenue.
What it gets, in the words of the HCLSoftware release, is "enterprise RPA capabilities that allow AI-driven workflows to automate tasks in applications where APIs are unavailable or insufficient." That is the whole thesis. HCL UnO Agentic, which HCLSoftware launched on May 8, 2025 as part of its Automation Orchestrator Suite, already claims to coordinate "AI agents, robots, people and systems." What it lacked was its own robot for the green-screen and desktop applications an agent cannot call through an API. Robotiq.ai is that robot.
Robotic process automation (RPA) is software that drives an application's user interface the way a person would — clicking, typing, reading screens — so that a process can be automated without an API. In a bank, that usually means the core system nobody is allowed to touch.
Who Is Running Robotiq.ai Bots Today?
The release says Robotiq.ai's platform "is used in large banks, insurance groups and telecom providers" — which means the customers most exposed to this deal are also the ones most tightly regulated on vendor change. Robotiq.ai's own homepage says it is "trusted by 150+ enterprises around the world," names Orbico and Hipotekarna Bank, and stresses that "your data stays within your infrastructure" — i.e., many of these bots run on premises.
The vendor's case studies page lists BDO saving "over €200,000 annually," Lev Ins Insurance cutting processing "from days into hours," Arena Hospitality Group automating financial data flows "across 29 hotels," and FINA running timesheet automation "at national scale." These are the vendor's own claims, unaudited.
Put the two numbers side by side and the economics of this vendor become clear. If the 150-customer claim and the €1.4 million filed revenue are both right, the average Robotiq.ai customer pays something under €10,000 a year. That is our arithmetic on a marketing number, and customer counts on vendor homepages are generous by nature — but the order of magnitude is the point. You are almost certainly not a customer whose renewal anyone at HCL will be reviewing personally.
The platform itself, per the product page, is built around the Robotiq HQ orchestrator and "100+ Ready-to-Use Automation Steps," with "ISO-certified security, audit logs, and flexible deployment options." HCL UnO is also an orchestrator. Two control planes doing the same job inside one portfolio is the usual precondition for one of them being retired.
What Does the Release Leave Out?
Everything a customer would need to plan a renewal is absent. The announcement carries a quote from Kalyan Kumar, President of HCLSoftware — "Enterprises are looking beyond AI experimentation toward production-scale automation that is secure, governed and reliable" — and one from Robotiq.ai CEO and co-founder Darko Jovišić about automation being "useful, fast to deploy, and reliable in production." It does not say whether:
- Robotiq.ai will continue to be sold as a standalone product, or only as a capability inside UnO Agentic
- Robotiq HQ will be maintained alongside UnO, or migrated into it
- existing licences, prices and support SLAs will be honoured, and for how long
- on-premises deployments will remain supported, or be steered to HCL's hosted offering
- the Zagreb support team stays the team that answers your ticket
None of this is unusual for an announcement. It is unusual to accept it as an answer.
What Has HCL Done to Acquired Products Before?
HCL's own record says the licence model you signed will not be the licence model you renew on. After taking over IBM's Notes and Domino, HCLSoftware published a licensing notice in October 2024 setting End of Support for the former IBM Enterprise and Messaging CALs on June 11, 2025, and telling customers: "To mitigate Version EOS and continue Support, you must re-license to CCB Term and/or Messaging Express Term (if not already) and upgrade to a supported Version." The same post steers customers toward subscription Term agreements, saying that "signing a multi-year (3 or more) Term agreement will offer the most attractive price, and price protection for the coming years."
That is not a scandal. It is a vendor rationalising an acquired price list onto its own model, with years of notice, which is what vendors do. But it tells you the direction of travel: customers get pushed toward term subscriptions, and legacy SKUs get an end-of-support date. A Robotiq.ai licence is a far smaller line item than Domino ever was, which cuts both ways — cheap to keep, and cheap for HCL to retire.
Steel-man the other side. For many customers this deal lowers risk. A vendor with €1.4 million of revenue is one bad year from insolvency, and DORA already required you to plan for that. An HCL-owned product has a balance sheet behind it, a global support organisation, and a clear reason to keep existing bots working: they are the proof that UnO can reach the systems agents cannot. If your automation estate is small and non-critical, "wait and see" is a defensible position. It is just not a free one if you are regulated.
Why Does DORA Make This Your Problem Now?
The Digital Operational Resilience Act has applied since January 17, 2025 to EU banks, insurers and investment firms, and it treats a change in who owns your ICT provider as something you are expected to assess, not merely notice. Article 28(7) requires that contracts can be terminated where monitoring identifies "material changes that affect the arrangement or the situation of the ICT third-party service provider." A change of owner, with the product's future unstated, fits that description.
Article 30 is where the leverage sits. Every ICT contract must include "termination rights and related minimum notice periods" (Article 30(2)(h)) and provisions for "access, recovery and return in an easily accessible format" of your data on termination or on the provider discontinuing its business (Article 30(2)(d)). Where the bots support a critical or important function, the contract must also carry notice obligations for "any development that might have a material impact" (Article 30(3)(b)) and an exit strategy with "a mandatory adequate transition period" during which the provider keeps delivering the service (Article 30(3)(f)).
And Article 28(8) requires a documented, tested exit plan for any provider supporting a critical or important function, one that lets you leave "without disruption to their business activities."
Ask yourself honestly whether a contract signed with a Zagreb startup in 2021 or 2022 contains all of that. If it does not, you were already out of compliance, and a change of control is the cleanest moment to fix it: the seller wants a smooth close, and the buyer does not want regulated customers raising issues in the first quarter of ownership. We made the same argument when Adlib bought Paperbox and when Kiteworks bought Bonfy. The pattern holds: the terms you get before close are the terms you keep.
What Should Robotiq.ai and HCL UnO Customers Do?
The work is to turn a press release into a contract addendum before November, and to know your exit cost either way.
This Week:
- Find every Robotiq.ai bot in production and the process it serves. Tag each one against your DORA register of information: is it supporting a critical or important function? That answer decides how much of Article 30(3) applies.
- Pull the contract and check it against Article 30(2) — termination rights, notice periods, data return, subcontracting. Write down each gap. That list is your negotiating agenda.
- Ask Robotiq.ai, in writing, five questions: standalone availability, Robotiq HQ's support horizon, price protection at renewal, on-premises support, and whether support staff and SLAs transfer unchanged. Dated answers from before the close are worth more than anything said after it.
This Month:
- Request a continuity addendum that commits to support for the current version for at least 24 months after close, holds renewal pricing, and gives 12 months' notice of any end-of-support or forced migration to UnO. Pair it with an export clause that returns your bot definitions, credentials vault entries and run logs in a documented format.
- Price the exit now. Rebuild your two most important bots in an alternative — UiPath, Automation Anywhere or Microsoft's computer-use agents — and record the effort. Our UiPath FUSION 2026 recap and the Copilot Studio computer-use analysis cover what those options cost to adopt.
- Update the Article 28(8) exit plan with the named alternative and the measured rebuild time, and file it with your third-party risk owner.
Before Renewal:
- If you run HCL UnO already, ask whether Robotiq.ai becomes an included capability or a new SKU. It is the gap UnO had; make HCL price it before you depend on it. Our framework for picking agent orchestration platforms argues for scoring exit terms first, which applies doubly here.
- Decide renew, extend with addendum, or migrate — on the basis of what HCL put in writing, not what the release implied.
The Bottom Line
A €9 million tuck-in rarely changes a market, and this one will not. What it changes is the owner of software that clicks through core banking screens in regulated institutions, bought by a company whose stated interest is a capability for a different product. The last time HCL absorbed a large installed base, the old licences got an end-of-support date and customers got a new subscription model. That was reasonable. It was also not optional.
Regulators wrote DORA's contract rules for exactly the moment when a vendor's future stops being the vendor's own decision. Use them while the deal is still open.
Silence from the buyer is not a promise. Get the promise.
Continue Reading
- Adlib Buys Paperbox, Which Trains on Insurers' Anonymized Mail
- Kiteworks Bought Bonfy. Ask for the Terms WAMNET Got.
- UiPath Shipped Delegate at FUSION 2026 and Left Its Price Blank
- Visa Bought BioCatch. Get Neutrality in Writing.
- Britain Regulated Four Clouds. Not the Models Inside.
- Bending Spoons Closed Airtable in 31 Days. Miro Says Q4.