What is our primary use case?
We play significantly in the BFSI and healthcare space. A lot of use cases have been related to BFSI. Insurance is much bigger, with claims and underwriting, policy admin, health benefits, and so on so forth. There are also good use cases on the functional level, HR and finance, and that cuts across industries.
How has it helped my organization?
As an example, looking at fatality insurance for pets, clients had a high volume of documents come in, claims in all different forms, and they had to apply logic eligibility. There's a simple rule of whether you allow or disallow. If they don't allow the claim, then there's a comp process. By a sheer ability to read whichever way the document comes in, clients are able to load the system and quickly get the eligibility.
This dramatically improves their claims operation by a big margin. Whenever there is some complexity in one, then we do an exception. We crunched the time so well and made the process so cost-effective it has given the client a huge benefit.
What is most valuable?
The democratization, automation, and attended automation, all of these are pretty good features. Those are all good value add to what it was there previously.
The moment a machine takes over, there are fewer errors. That is inherent. When you say value, that is the cost-benefit.
What needs improvement?
We have seen a lot of benefits on the backend, but then the algorithm is constrained, which can't transform because of the older technology.
Sometimes in their partner communication, they aren't consistent. This maybe is related to the fact they are growing as a company.
What do I think about the stability of the solution?
The solution is fairly stable.
How was the initial setup?
The initial setup is always complex. Clients don't know the hardware, the licensing, or how it works. Any large organization will always have an initial hurdle.
We have roughly around 164-165 trained RPA credentials on the engineering side, all on UiPath.
You do have complexity when it comes to maintenance, as you get to 50, 100 bots.
What was our ROI?
As an example, one of the customers for whom we did an early bird, we estimated we could save this one division of their company $44 million. They only may have to invest about $4 million. There's $44.5 million for about 12 months. That's what we think we could save.
The adoption of RPA has definitely been increasing and we know that all of that has been largely in the back office. In the back office, it's easier to check ROI. We've actually gone beyond ROI because ROI is a very simple statement, so we start showing clients value.
How long it takes to achieve ROI actually depends upon the client's way of implementing it. For example, some people will wait to take away the manual effort while they will stand by. Because what if it doesn't work? What if it fails? What if then my backlog increases dramatically? So, it is really up to them. If it is simple task automation, we can do it in about four or six weeks. In eight to 10 weeks they'll see the benefit.
What other advice do I have?
We're using all components of UiPath: attended, unattended robotics, and Orchestrator Studio. We have a very wide customer base and our clients use all of them.
Cloud adoption is increasing. Deployment models are a little bit more a logistic question than anything else because companies who want on-site are a little bit more conscious of security, but they take a normal amount of time, just to figure out the infrastructure. If we moved clients to the cloud, we can make it easier to implement. With email on the cloud, they have a huge set of processes. The larger the company, the larger the processing. With the cloud, it becomes faster.
I've got a deep partnership with UiPath. I would absolutely rate them high. I'd give them a ten out of ten.
Start Your UiPath Free Trial
Accelerate your digital transformation now with free access to the UiPath Platform