UiPath Reviews

Organizational internal processes automation — especially in areas of operation and admin (back-office).

I believe that UiPath opened topics of RPA and AI/ML in our company (which consequently led to a shift and much stronger orientation of our company — globally — towards technologies and technological areas like software development, the blockchain, IoT, etc.). I believe that this role ("enabler" role) was crucial and also helped tremendously in raising overall 'digital'/'ICT' and 'programming/integration concepts' awareness company-wide. You might agree that the impact of this scale might be much higher and more important than any time and costs saved by actual automation.

UiPath Studio as a whole (the very 'core' component of the entire platform) allows you to concatenate all the different pieces/actions/sources you need — and doesn't matter which one that is (API, web, database, legacy system, OS application, email, or anything else like Excel, data transformation or even OCR).

Also, I'd like to highlight Academy (and e-learns) — it's very good and provides you with everything necessary you need to know.

2018.3 and 2018.4 releases made a huge leap in terms of functionality — we're not missing anything currently.

Good.

Very good (up to 10k robots — definitely OK).

Very good.

No.

The entire Orchestrator setup is a bit tricky (a lot of different components — Kibana, Elasticsearch, URL Rewrite, PowerShell scripts), but we had guidance and description on the web which is also very good.

In-house.

One year.

Strategic partnership might bring you a significant discount (it also depends on the size of your company and future potential of the vendor — your business cases).

Yes (Kofax, Blue Prism).

We are using UiPath in our finance and accounting area but we do see it as a tool that we can use across the whole of the business.

We're really in the early days of what we're doing but even with the first robotized process, what we've seen is that it's given us the opportunity to really assess the process, understand where the waste is so that we could eradicate that, simplify the process and then really engage with the operations people to build a robust, streamlined process. And then the automation of course, has got rid of the mundane transactional work and given the people a much more fulfilling part of the process overall.

We've used a number of automation technologies previous, I mean we are a technology company so we understand automation and we've used a lot of BPMS tools in the past, but this has just given us something that we didn't have, and I think that's the advantage we're seeing from UiPath.

I think it's the relative ease of use. It's really bridging that gap between the human interface with the technology that we're using and giving us an automation advantage that you just couldn't get from any other type of solution.

I think it's a little bit early to say at the moment, I think UiPath are ahead of us in our thinking at the moment, maybe in a year's time we might have areas where we see gaps but at the moment, everything we need I think is there, out of the box.

I think like any tool, like any software technology, you have to follow the recommended framework and use proper coding standards so it's easy to use, but I think to scale up and make it robust in a scaled environment, you have to have rigor, you have to have a solid operating model in place. But we've done that and yeah, I think it's a very stable product.

Before we entered into this, we did some benchmarking and we looked at best practices and we're seeing companies that are scaling significantly using this technology. We believe we can scale to a significant level, and again, the key thing is to put that operating model in the infrastructure in place to give you that solid foundation.

I would say it's excellent to be honest with you, getting our first robot up and running we had some pitfalls as you would expect in the early days, but we picked up the phone, we got hold of UiPath, they sent people both in physical and remote support forms. And it was second to none, it was really effective and we got up and running very quickly as a result.

I think setting up the software is very easy to do. It is really about spending the time up front to think about your operating model and think about how you're going look at the processes, how you're going to simplify them and then how you're going to robotize them. So you could get up and running with a robotized process very quickly, but if you want to do it on scale, you do need to take some time to think about how you're going to scale that.

we did use a partner, I won't name who that was. We worked with them. It was good to have that experience to bring somebody in who'd seen it in other companies and could help to give us that kickstart. We do want to be self-sufficient, we do want to build our own competence but I think everybody needs that boost in the beginning.

I think the first thing is that I always see these things a starting point, it isn't cost, per se, it's really about the improvement to the process, the quality, the service and overall value that you can deliver to the customer. But what's great is that coming out of that, you do get a cost advantage and obviously unattended robots give us a significant cost advantage, but even attended robots, you're seeing very much an ROI which is in the two times plus level.

If we look at ROI, if we look at our first robot, that's the only one we've got fully engaged and in production, it's probably going to give us an ROI in about one, maximum, two months.

It's been very quick to get up and running and it's saved significant amount of time. We're basically only talking about initially one FTE, when we scale it up to the rest, globally it's going to be be three FTEs. Within one to two months, it's going to giving us a return on investment and we've now got a pipeline and a backlog of robotized processes which we expect to be giving us ROI of less than three months.

It is always difficult to say exactly the percentage, but it's certainly got rid of human errors. I think one of the most important things is that we're 100% certain that the processes run right, so we know that day, that time that the processes run correctly, or if not where the errors were.

The thing with human errors, even if they're infrequent, you don't often know until much later on that the error occurred, so it's that certainly of knowing when you've got 100% accuracy and when you've not, you can very quickly rectify that. So I think that's probably the biggest impact we've seen. So far, over 80% of the lead time and process time has been reduced.

We are accountants and consultants and there are many mundane processes in auditing. Using RPA to automate not only allows us to be more precise, but we can also audit a larger population of material. We get accuracy and speed, and those are our main goals.

We have been able to do our work in a more timely fashion, more accurately, and it opens up other paths of customer use cases which will enable us to expand our business as well. 

In terms of performance benefits, I would rate it a nine out of ten.

• The OCR capabilities, to take somewhat structured data and put them into more structured data so that we can do our analysis.
• Screen scraping.
• The overall process of integrating it with other applications that we use in our analysis.
• It has also exceeded our expectations in the fact that it's a lot quicker to implement than we thought it would be.

It's easy to use but I think it will be a lot easier as it continues to develop. Right now, we do need some development capabilities, to understand certain computer languages, to put in the bots. They're on the right roadmap to make this even easier to engage so that anyone, even people without programming language experience, will be able to use it.

I would like them to continue to build and make Studio easier to use for non-technical people.

Looking at it as a marketplace, I think it's very stable.

We have used their customer support. It has been good for us, although it hasn't been perfect because they're growing so fast that there are a lot of new employees coming on board. That's a challenge to manage for any company. Certainly, the online tools, the Academy training, allow for a nice implementation. It's more an issue when it comes to getting in touch with someone, where we need something customized and we have questions.

I have used UiPath RPA Academy training. It's been great. I think it is developing as well. They continue to add training, change and modify some of it, which is great. You can feel that it is evolving.

With most of our clients, generally, it's humans who are doing manual, mundane tasks - what I refer to as the "low-hanging fruit" side of it. They see right away, when we take their current process that they're doing, how the automation can handle it and be more accurate than what the human employee is doing right now.

The important criteria for our clients in selecting an RPA solution are price, that is always one, but also accuracy and security are factors they're most interested in.

I was involved in the initial set up of UiPath in my company. On a relative basis, it's straightforward. There are certainly some complexities to it, but it is definitely less complex than I expected it to be.

Our clients have seen considerable ROI from using UiPath. Once our customers get their heads around it, and then we implement it, they see the benefits of using it straight away.

Scalability is there. There are so many use cases, certainly for our company. There are many opportunities. We're essentially automating what I would consider to be the low-hanging fruit, and there are so many things to build on top of that, as we get that foundation.

UiPath absolutely is capable of scaling.

Usually, it's Blue Prism and Automation Anywhere.

One of the main reasons that clients go with UiPath is the Academy, where they can get free training, where they can send their internal people to get the training. Having access to it and learning about it is a big hurdle a lot of times. Having access to the learning is a great thing.

I think it's the best RPA solution that I've looked at and I would suggest that you take a hard look. It's easy to start working with it. You can get it stood up pretty quickly and you're going to reap benefits right away.

This is a fast-growing industry, so staying on top of, and executing, plans is important. So far, from what I've heard regarding the roadmap, UiPath is certainly on their way to doing that.

Right now, we're in an interesting spot where a discussion point is how much our customer will own of what we sell to them. We're developing bots right now. The infrastructure, in our use case, typically, is owned by the customer. For us, it's about educating our customers on what we can help them with in terms of infrastructure: We can run it ourselves or they can own it. A lot of our customers want to own that infrastructure.

I think of all of the things it can do - the integration with different applications, solving what are important problems, and saving many labor hours for those who are using it  - and they are the main reasons I rate it a nine out of ten. The only reason it's not a ten is it's not totally done by someone that doesn't know technology and programing. I think they'll get there but you still need some skill sets in your organization.

My primary use case is mainframe automation from legacy mainframes that previously hadn't been automated with other automation tools. The product worked like a dream with the mainframe automation.

We're trying to get rid of the boring, mundane tasks that people do every day so that they can spend more time doing more important things like figuring out why there are issues happening rather than just putting a Band-Aid on.

In our first year of jumping into it, we set up the infrastructure and everything, so it's been less of a year of development, but we have saved a hundred thousand hours.

The automation efficiency depends on what the job at hand is and how much it saves. But some of the tasks done constantly throughout the day, even if it's only saving five minutes, add up really fast. 

We use Task Capture all the time. We have a bank business analyst who uses it and teaches people how to use it. We're constantly getting process definition documents to review and add to our pipeline.  

Studio itself has all its great features and is easy to use. 

There are bugs here and there. My only complaint is that each time we open a new ticket, we get someone new and have to explain how everything is set up all over again. 

It would be nice if they had that somewhere on record for support.

I have been using UiPath for two years. 

It is a stable solution; everything seems to be running pretty smoothly altogether. The biggest issues are not on the UiPath end, but on our company's end like, network issues and issues like that keep popping up every now and then.

The support's been pretty decent. We have a TAM, so we have someone we are constantly in contact with.

We meet with them weekly, and they're very helpful. If we do have to open up a support ticket, there's a bigger issue that they can't help with. They usually help get the ball rolling.

Support has been pretty helpful. Like any other support though, they ask all the basic questions in the beginning just to figure out what has or hasn't been done.

My only complaint is that each time we open a new ticket, we get someone new, and we have to explain how everything is set up all over again. So it would be nice if they had that somewhere on record.

Positive

The initial setup was straightforward. There's plenty of documentation that is easy to follow. 

The hardest part was more on our company's network and infrastructure, trying to navigate all the hoops that we have to go through just to make sure it's secure and the network's secure. Getting access to what we need to get access to.

We're still kind of new to things and working on migrating to the cloud. We're one small team in the organization. By moving to the cloud, we're hoping we can onboard more and more teams to be able to use it and spread it throughout the company.

UiPath helped us along the way. 

There are other automation tools that the company uses, but they can't do everything that UiPath can. All of the potential automations just kept being pushed to the side until we started using it.

We used Microsoft Automate for a very short time. We started looking into it for some tasks. The issue is that we're trying to automate it deep inside our corporate network, so, we haven't really been able to use Power Automate.

Overall, I would rate the solution a nine out of ten. The amount we could do in one year is pretty impressive. 

I work in development, creating robots, and I use UiPath for automation.

UiPath has helped to minimize our on-premise footprint and reduced human error. It has also sped up digital transformation and reduced its cost without requiring any expensive or complex application upgrades.

UiPath's best feature is that it's low code. UiPath also has the best community I can think of in the IT sector.

UiPath would be improved by integrating AI.

I've been working with UiPath for four years.

UiPath is very stable.

UiPath is very easy to scale.

UiPath makes it easy to build automations, monitor the activity of the robots, and let the business side interact with the robots. It also has a lot of applications, starting from test capture and process mining to reporting the activity of the robots. UiPath is a simple solution if you're looking to save time and money, but in the long term, I would suggest customizing the main applications you're using. I would rate UiPath nine out of ten.

We use it for unattended automation. Most of it is centered around finance for various reporting purposes. We also use this solution to move data between systems.

The biggest improvement is giving people time back in their day. We're still not where we'd like to be with our automation journey, so we don't have the time savings that we would like at the moment. However, we are continuing on that journey and helping to free up users and allowing them to work on things they want to work on.

The Excel integration is definitely good. We use that a lot because our finance department uses Excel. Overall, I really like Studio and unattended automation. Automation Cloud is very good as well. The platform as a whole has been good for us.

I like the UiPath user community, and the forums are really good. Most of the time, I can find answers there to any issues I'm having. The UiPath forums are very active, and I like seeing the employees in there as well.

We onboard any new developers that we have for RPA using UiPath Academy. It reduces the amount of training time in which the RPA team is involved because the Academy courses can take care of a lot of the fundamentals on UiPath.

Integration is an area for improvement. I still encounter issues with it, like getting errors when I try to use a connection.

We've been using it since 2019.

I have no complaints regarding the stability of UiPath. We have never had any issues with regressions or weird bugs.

We're still in the early stage of our journey with UiPath. Right now, we have six unattended robots and about 25 processes running on those, which is not at a scale where we might see issues. However, I have no complaints with regard to scalability so far.  Also, achieving the scalability we may need seems pretty straightforward.

UiPath's technical support is on par with that of other companies. We seem to spend a lot of time sending logs back and forth, and because of that, I would give technical support a rating of seven out of ten.

Neutral

The initial setup was not too bad. We started in the finance units since they were the ones pushing for RPA, and they've been our biggest internal customers so far.

We worked with our reseller who guided us through the entire setup. They did a few automations for us until we had that practice in-house.

In terms of ROI, we are saving more than what the platform costs us. We are at about 1.5 million in savings due to recent automation. It was a little less than that before. These are soft savings and don't show up on balance sheets. We're trying to work toward automation that actually do lead to hard savings. We've saved about 43,000 hours in a year so far.

The licensing makes sense, but it does lead to a few adoption issues when a lot of the licenses are per user. Convincing some of our business units to pay for user licenses for either Action Center or attended robots can be a roadblock.

We looked at Blue Prism. The biggest reason for going with UiPath is that we are a heavy .NET shop. Therefore, the fact that UiPath is based on .NET and that we can write our own custom activities in C# bar and Visual Basic were big factors for us. It meant that we would be able to adopt UiPath faster and that it would fit with our current Microsoft stack as well. We also liked where the UiPath platform as a whole was going, becoming not just RPA development but integrations as well. In comparison, Blue Prism seemed to have stuck with RPA and not expanded much beyond that.

Take a look at UiPath's platform as a whole and what it can do aside from just RPA automation. I would also advise you not to discount the tech stack. Overall, I like the platform, and I think it's headed in the right direction. Because of that, I would give it a rating of nine on a scale from one to ten.

The use of this solution is spread out across our organization. On the IT side, we use it for synoptic notes like admission process, reviewing invoices and giving usage access.

The insights that this solution provides have been most valuable. We use these insights to report to higher management on the performance of our processes. 

UiPath also helps us reduce manual work although we do not yet use UiPath's AI functionality. We have learned a lot from the UiPath community and gained knowledge about future products and enhancements. 

The support for this solution is tedious. I would rate it a five out of ten. If we don't respond or the ticket closes, we do not get a response from them.

I have been using this solution for six years. 

This is a scalable solution. 

The support for this solution is tedious. I would rate it a five out of ten. If we don't respond or the ticket closes, we do not get a response from them. We then need to go through the process again and reopen a ticket with the same information.

Neutral

I have a little bit of experience using Automation Anywhere, but I prefer UiPath. The coding with Automation Anywhere was not developer friendly. 

Our whole team was new to this solution so there was a learning curve involved for all of us which made the setup difficult at times. At this stage, UiPath was one or two years old with limited documentation. The deployment did not take long.

We deployed this solution with the help of a partner called Ernst & Young.

We have experienced a return on investment using the solution as it has led to three million in savings since we started using it. 

We would prefer it if the licences were packaged together. When it comes to developer licences, we need to pay to transfer licences when a developer leaves and this also creates additional work for our IT team. 

Overall, I would rate this solution a nine out of ten. 

I would recommend UiPath to others because it is a good tool and has a lot of potential to expand. 

I'm not currently using UiPath, but in my previous organization, which I left seven months ago, we had a complex trading application that included a web form and a Windows form. And on the Windows form was an Electron framework. If you want to run a web application inside a Windows application, Electron is a bridge between the web application and the actual Windows app. Because it was a complex application, it was not very easy to automate. That's where UiPath came in. It perfectly fit our automation testing scenario.

Before UiPath came into the picture, we were planning on doing automation testing with Selenium. The test plan with Selenium was going to take about three months. When UiPath was introduced and we started working on it, we completed the whole automation, end-to-end, in about one and a half months. It saved us that much time. And we made sure that our product was delivered with the required quality and that we did not compromise on that.

Because UiPath is SaaS, we were able to automate everything in a very productive manner. We were able to cross-verify all the flows and all the functionalities. And UiPath didn't require a huge amount of setup. It runs on minimal requirements.

In terms of human error, we saw a reduction, of course. It's not possible for a human to catch every error when new functionality is built. With UiPath automation, we were able to analyze errors right away and resolve them.

Another benefit was that it freed up employee time. It did a lot of the work by itself. The user only had to make sure that the correct workflow was involved and he could just sit back and check that everything was going correctly. It probably saved us 45 minutes daily.

UiPath makes you more productive because it comes with a lot of drag-and-drop features. You don't need to know the APIs to access particular elements on the screen. You can just drag and drop and define your actions and go ahead with the workflow. You can focus on the workflow rather than learning about the APIs, which is what happens with Selenium and other automation tools. That is one of the most beneficial features of UiPath.

I don't know if I was doing something wrong, and I did get assistance from the UiPath guys on this, but sometimes UiPath wasn't able to find an element on the screen. But that's what UiPath is for, and we wanted to make sure that our workflows were working correctly. Sometimes it was able to find an element and sometimes it was not. UiPath support did give us a solution, but it was not helpful enough.

The issue that I mentioned earlier, that sometimes it wasn't able to find the elements, was the only issue I saw with respect to UiPath. Otherwise, nothing was breaking and nothing was problematic on the UiPath side.

They were very friendly and they tried to be very helpful, but they weren't able to solve the issue I raised.

Positive

The version of UiPath that we used involved a direct installation. We asked our in-house team to get it installed because we didn't have the permissions to install software. They installed it in our system and we started using it right away. It was very straightforward.

I have worked with Selenium, which is an automation tool. That has quite a learning curve, but with UiPath it only takes you one or two weeks to get started. Once you're familiar with the basic tools, you can start writing a workflow. It is straightforward; nothing complex.

I never did the UiPath Academy courses because we had senior team members to help us and, in that company, we had a "learning playground" where we could go through the slides directly, without going through a whole learning process. We were then able to start our work right away.

UiPath did a good job. Before going into production, we needed to make sure that every test scenario and every case was handled. That's where we took advantage of the UiPath. We would run UiPath again and again and there were no breakages in our code and nothing was falling apart before going into production. I was working for an investment bank and every record was important.