UiPath Reviews

Right now, the primary use case is document retrieval from our client system. We are a healthcare billing company, so we have to pull things like medical records and different documents from hospital stays. So, we used the robots to pull those versus an FTE.

We have both unintended and attended robotics that we use. We haven't really delved into Studio a lot yet. That's going to be part of our staging and going into the next phase. We built all of our basic bots, so now we're going into the more complex bots.

We are on-premise. We were looking at moving to the cloud, so that will be something in our next steps.

It has a really good turnaround time for our operations department to start working on claims, because all the information has already been pulled upfront with the bots. Instead of having to go into an account and request medical records or a certain type of document, it's normally already been pulled on the front-end as soon as the account loads because we run everything through the bots.

The most valuable feature right now is we have been able to utilize our staff better with the bots. We can put them on more high priority items. That was the one thing that everyone was afraid of: The bots would replace them. What we did is retrain them to do other tasks that we needed, as that was more of a priority for us.

We do deal somewhat with Citrix. It depends on the client and how the bot has to be set up. We have some clients who do run through Citrix, then we have some who use a VPN tunnel to get in. So, we have it on both.

The implementations or integrations through Citrix are really good. The only problem that we are coming across is just maintenance. If the Citrix platform gets updated and we're not notified, it breaks. So, we have to reconfigure our bot to the new updates. Unfortunately, that's just the name of the game, and that would be true if we were pulling them manually versus a bot. We would still run into that with the Citrix platforms.

I would rate stability as a five (out of five). We have not actually had any issues with UiPath. Most of our issues have been with just platforms changing, breaking, and the regular maintenance.

We have about 40 bots right now with 30 ready to be made.

Our team is really small. We have roughly six people who are working with the developers and actually running the bots. We're the only department using the solution. Our department was asked to lead this on, so we've been very fortunate to be able to lead it and be able to help our own department first. Now, we're starting to look at other areas of the company to deploy RPA.

We have not used UiPath technical support.

The initial setup was a little complex, but that was because we really didn't even know what we were getting into. We were told by upper management (our CFO) that automation was the next frontier and we had to go that route. We were sort of the pioneers going through this for our company,

It probably took about six to eight weeks for us to talk with development and for them to get the context of what we wanted. It took them about five weeks to actually build the bot. Then, once they built the bot, it was in production. Of course, we had to go back and do some maintenance because it did not work first time. After we got the hang of it, it's been great.

We got some consulting from UiPath. We do use their developers. Other than that, we do not go through a third-party. We did everything else ourselves.

Our experience with UiPath services was good. There were some bumps along the way. It's just trying to understand the process and RPA from what we've seen.

It took us about six months to really see what the bots could do. We then started tracking financial savings and how it's helping the company. We set out a bit differently. Our CFO came out, and said, "Automation is where we're going," but on top of that, "This is X amount of money that you have to save in the process."

We have spent the last 18 months tracking how much we are spending and how much we're saving. We hit the goal with no problems because we were able to shift staff. We did eliminate some staff, but this solution really brought out the skill level of our employees. Those employees with the higher skills were able to transfer to more important projects.

Within the first year, we saved a little over $600,000. That totaled to almost 19 FTEs which we ended up saving.

We haven't used any other vendors.

We are on spreadsheets and data. I keep saying we're stuck in 1996. It's been nice to have the vision of being able to be in the 21st century and really be able to use the bots the way we want to use them.

We have not taken part in the UiPath training. That's something that we talked about right before this conference. We really need to start utilizing more of the training that's offered. We want to turn some of our soft coders into people who can really code for us, not always relying on developers to do all of our work. That's definitely something that we're implementing soon.

I would rate it at least a four (out of five) for ease of use. We don't deal so much with UiPath, but from what we do deal with outside of developers, we have not had any problems. It has been very user-friendly, for those of us that don't know coding. We are able to look at things, sort of fix things, etc.

I rated them a four for ease of use, not a five, because we want to see what UiPath can do. We have a lot on the table. We have 30 bots ready to go. A lot of it's more screen scraping, which will be more complex. So, we want to see really if UiPath can do what they say the solution can do. We want to test its scalability.

I definitely would say UiPath is the way, especially with everything that they're coming out with now. It helps you understand more about RPA instead of just being thrown into things. It helps you understand all that on a smaller level. It is what everyone else has said here at the conference too, "Start with a small project. Don't go out with a big thing because it's not going to work." Luckily, we did start small, and we've just grown from there. Those would be my suggestions.

I would rate the solution a 10 out of 10.

The primary use case is data management.

The object cloning in UiPath is a lot more consistent than Automation Anywhere. The consistency with which it captures the information that it's supposed to in order to do the rest of the process is probably the most useful component of the tool package.

1. Navigating the directory of objects needs improvement. I would like a better way of finding the command which allows you do the thing that you're trying to do. This would help. For example, there was this one command that I was wrongly using for months. Then, someone told me, "You can do that by just using this one command instead of three jerry-rigged together." Therefore, I would like to be able to put in keywords that would allow me to figure out what command will allow me to do the task that I am trying to do.
2. The testing could be a bit easier. There are error handling steps in the platform tool, but it's not super robust. It's very user friendly from a development perspective. However, from a testing perspective, it is unclear what I am looking at. Maybe, they could add more commenting. 

When the complexity increases, the bug related issues go up. There are limitations to utilizing RPA software, in general, where sometimes you have business leaders who think something is a good process. Then, they ignore the technical advice to not move forward, or choose to. Thus, you're left in a situation where you're trying to automate a process that isn't great for automation.

One of the easiest things about UiPath is you click one link, it downloads, then you are done. With Automation Anywhere, we have a whole days worth of setting up that needs to be done. This is another component that UiPath is leading the industry in.

UiPath works best when there is a strong understanding of the capabilities and limitations of RPA. I have seen it work best when you have an experienced practitioner who has seen what an implementation looks like. Therefore, they know the right questions to ask as you are determining which process to automate. It is better to have skilled developers, who are more technically capability, to develop solutions using the tools which come with the package to make sure it is working correctly. 

There is the upfront work of talking to clients. There is a middle part of developing it, then the maintenance and operations post-implementation. You have to manage the bot after it's built, and it works best when you have someone who comes in and knows all three of the step components are equally important to a quality end product.

The ROI on all of our RPA use cases is from a throughput perspective. Processing time improvement is anywhere between 70 percent faster to 300 to 400 percent faster. For the right processes, there is even up to 7X to 10X improvement from a throughput perspective, even though it works through the UI. 

The most impressive use case that I've heard of was about saving a year's worth of FTE time in a month's worth of development, testing, and deployment, then doing the processing.

I have used all of the major RPA platforms: primarily Automation Anywhere, UiPath, and Kofax.

UiPath is the most open in getting people to use their software. I think they understand that the most successful relationships in sales come from people playing with the solution.

I started out as an Automation Anywhere person and will always be better at Automation Anywhere because of my affinity with it. Where Automation Anywhere might have UiPath beat is the speed at which you can automate simple processes, like being able to create and automate simple processes. Automation Anywhere is a better point of departure because the way you look at the script in it, there is almost like a sentence that you can read. Being able to understand what a process is supposed to do, you can just replicate the steps in your head. A non-technical person can open this web browser, type here, and press enter.

With UiPath, it's more from a process perspective, which is more useful if you're looking at automating a process. Instead of something simple, like for training, we'll have people look up the weather in five, ten, or a 100 cities. From that perspective, it's easier to start up than Automation Anywhere. 

UiPath makes up for its steeper learning curve by being a more reliable product. 

If you are looking on the spectrum of which is most to least technical and most to least scalable, UiPath is a happy medium compared to Kofax, Automation Anywhere, and Blue Prism. UiPath is less technical and not so hard, but it's also scalable, so it's a happy medium.

UiPath Academy is by far the best online training resource. From an online content training perspective, their videos and training modules are leading the industry.

We are working on trying to optimize some of the current processes which have been selected for review. I have been talking with our business partner to try and find the best way or tool to optimize these processes.

I have only been with the company a month, so I am only aware of a couple of scenarios/cases where it has already been implemented, such as:

• Transferring data from one system.
• Looking data up on the internet from a browser.
• Performing logins and copying data tables, then putting them into Excel. Afterwards, manipulating and putting them into the right system.

These are our best cases, so far.

It is great for automation. It can reduce the time needed for the entire work assignment, freeing up time for something more exciting.

There is a very steep learning curve for business users.

From everything that I have seen, we still have stuff that we need to figure out on the inside:

• How to spin up servers.
• How to get compliant.
• How to create A/B uses for the robots. 

It would help to have some guidelines, which I haven't found yet. It seems like UiPath is trying to keep out of the guidance part, because they want to leave it open for us to interpret how to use the tool. 

I don't even know all the features available yet. I would love to see the roadmap. I love that going forward UiPath is simplifying the roadmap, trying to make it available for development within the business, not only IT.

The stability has been good, so far. I haven't had any complaints.

The scalability seems good. 

I haven't been through to customer support yet. I use our internal tech support (in-house). We have some knowledge, and they have been working in this area for quite some time.

I love UiPath Academy. While it is dull and I can't do more than an hour or two at a time in sequence, I think it is great. It's available to everyone, which is awesome.

The implementation for virtual environments went fine for the cases I've seen. We are using Citrix for some of them and virtual machines for the Unattended Robots, which seems to have been flawless.

We used consultants at some point.

It has saved us time. We are still doing the business cases to determine return of investment.

We expect to see ROI and performance benefits. I would rate the performance benefits as a ten out of ten.

I have nothing to do with licensing.

We are using multiple solutions for RPA within the whole region. UiPath is doing something right with its open community, sharing and involving users, then providing a platform for us to share our findings and snippets. That's the way to go and why I would recommend UiPath.

We have a huge strategy on digitalization, so automation technology is very important. It's a common goal: Optimizing and putting stuff into categories, which can be optimized. 

While I believe it has been helpful in the elimination of reducing human error since it is doing the same task every time, I'm fairly certain we didn't have many error previously.

I am a developer, and I find the product pretty easy to understand since I understand the logic of data containers and data types. However, I have been speaking with a lot of our business partners on the business side, and they are finding it hard to use.

Learning RPA:

Open source (community version) of UiPath, and their Academy — one of the best Academy for RPA in the market. They split the content into different courses and content into similar sections which is easy and makes it easy for self-learning.

Coming to the design/implementation part: It's completely easy and simple to work on. It reduces the complication at ease. There are different options available for all the IT solution which can be utilized for effective management.

I'm usually solving infrastructure related automation like Exchange 2013, Windows.

The benefits that are in the ITIS sector: The work is the same that has to be replicated to different customers at different points in time. UiPath gives an option to resolve this duplication of work and saves time as well as resources.

It has an effective/simple user interference monitoring option available with the charts and graphs which help in handling the exception cases. And help in a case study for further development and implementation.

With this simple UI, my experience with UiPath is approximately four months. Whatever, I have noticed their priority is "feel the experience while using UiPath", and by the end of the day, this is what makes it different even in the business revenue.

There are different webpages for different uses: state, UiPath Academy, UiPath Connect, etc. They should bind all together into a single webpage. So having all in one place would be helpful.

And also they need to provide another couple of robots for the community version user for enriching their skill and for learning purposes. And also they need to have sample projects available to help new learns to learn complete automated skills rather than bits and pieces while taking courses in Academy.

And there should be a sample cheatsheet provided. UiPath is a simple tool which can be learned by anyone in less than a span of five weeks. If they have provided a sample cheatsheet, it would be easier to follow.

Trial/evaluations only.

Completely stable and reliable with all the scheduled jobs. It gets the job done in most of the cases.

It was quick and effective in handling all the assigned tasks and simple to handle.

Didn't have a chance to raise many cases with their technical support team for their assistance. But whatever the cases I have raised or saw, they were quick and responsive.

This is the first RPA tool I have chosen over Blue Prism for a simple reason: open source and an active community to share the views and new ideas.

It was straightforward; I didn't face many problems. It's one of the simple tools that can be set up with basic knowledge. 

Didn't implement via vendor team, but did set up a couple of components. It works like a charm and is completely reusable.

Return on investment — not applicable. Still, I don't have any project that is completely commercial that went live. But I will have a better ROI using the UiPath tool. It's trustworthy.

UiPath's best package for everyone in the market. Starting from the free community version. It's all for the taking.

• Growth in the market
• Ease of use
• Reliability, and 
• Management.

There could be an improvement on the library packages and other built-in options.

We have acquired UiPath with both the robot and orchestrator. I want to make sure that we get the right return on investment and with the orchestrator you are not only able to use the robots during the day, but you are also able to schedule them during the night. You maximize your investment 24/7.

Lombard International Insurance is the number one in wealth investment and for us the onboarding process is a critical one. We have started with KYC (know your client) which is an extremely painful process, a lot of manual work, but now have some very good friends and colleagues that are happy to have Ruby the robot as their assistant. 

On top of this we also have tax reporting, overdraft, reinvestment, so there are several processes, some like KYC for instance.

The commitment that we have made internally is that we're going to reduce the workload as much as 20%-50% and I would say this is the promise that we have delivered.

In KYC it's 50%, in another process it's 20%, it's also very much depending on the maturity of the processes and how much manual work do you currently have because the robot will only take away the manual work.Whenever you need to have validation because you need to have the four-eye check, that still remains.

When it comes to automation in our organization, we have a certain strategy. Automation and technology is only one pillar of our strategy, but we have an integrated strategy which means that we have the business model, the operating model and the technology.

When you build a house, if you do not have a strong foundation, it's just going to fall apart, so, for us, it's a pillar. It's not the only one, but it is the cherry on the cake, that it is the one that is actually enabling the business to go further and to provide better services to our clients.

At least for our case, I would say it's not the cost that was driven by attended or unattended robots. At the end of the day, my department, business transformation, I am there to transform the business for better.

In some cases, you have processes in which you still need human interaction, you still need somebody to validate and make sure that, once all the data are prepared for you in the onboarding process, you certified and you double checked four eyes principle that everything is correct.

In some cases you do need the attended robot. In some other cases, tax reporting for instance, you can just run it unattended and it's perfectly. You don't even need to know it. Before morning, you have the report prepared for your local authorities, and that is fine, so I think it's just a mix, depending on your business and how it's bringing much more value to you. Sometimes, it's only attended, sometimes, it's unattended, but I think, in most of the cases, you will have in any companies a mix between attended and unattended.

We are proud to say that we have not encountered any issues. Yes, sometimes I hear some colleagues like, "Oh, I have KYC and he stopped." Well, there are also some reasons because, if your password expired and, guess what, somebody needs to update it before it's expiring, the robot will stop. Yes, but so is if you're a human and your password expired, you need to change it.

It is scalable for us. I will have to be honest, we do not have 1,000 robots.

We have not had any opportunity to work with them because that was very stable so far, so we had only in the beginning a partner which worked with us in this journey.

I have actually a story with a CEO in our previous company who was saying, "I didn't know when we did the email migration." I said, "Well, then it means my department is very successful. If you do not hear, if you do not see it, it means we do a good job, so I can only assume they do a good job if we do not interact with them."

It was quite straightforward. Not only this but you see they go more and more into the direction that makes this open and collaborative even for the business users. So that is a very strong advantage for us.

We selected Fujitsu in Luxembourg because our company is headquartered in Luxembourg. Fujitsu had proven not only that they have the technology knowledge, but also the market and local legislation which, Luxembourg people know that it's heavy regulated and you need to really know the ins and outs, so, for us, they seem to be the right partner.

In terms of ROI, I think it's also depending and this is probably critical and I can advise other companies that are starting this journey, make sure one of the critical success factors is select value reach processes. What does this mean? It means that you need to select critical process for your business but also those in which you do have high manual work and you run maybe that process frequently.

You will see ROI in probably 9-12 months, at least as I said, if we look at our processes. Now, we do not like to talk about savings in term of money because we have a different philosophy, meaning that what we want to create we want to create workload reduction for our users.

If I am projecting growth, if I need 10-15%  growth next year, how do I cover this? Do I hire more people? Do I streamline my processes? Well they are kind of lean. Do I use technology? Yes. Well that's your answer. So it means you need to use that technology in a smart in order to enable your people to process more, be it transaction, terms of processing, be it in finance and they have a lot of invoices, it does not matter. It's the same, it means that if we are able and we were able to save roughly around 40%, more than 8,000 hours, per year that we have managed to save, for us that was the ROI.

This is how we are able, for instance next year, to reach the five billion target. I would advise other companies to go more in that direction.

I think one of the advantages that we had with UiPath is that we tested other products such as Automation Anywhere because they are the big players.

We did not yet implement UiPath in Citrix, we have Citrix in our environment, we work with Fujitsu too because there are some aspects that you need to take into account.

I would give it an 8.9 because the extractor is not there, probably now with the extractor I would give it a 9.3. In terms of what it is as options, as I said, I think they are the only player at this moment that has attended, unattended, and an orchestrator, you can customize it.

We use UiPath for our accounts receivable and accounts payable. We are a wood company that uses it primarily for customer care and finance.

UiPath helps us to reduce human error and eliminate some repetitive tasks involved in processing invoices, so our employees can focus on critical work. We have been able to assign users to different tasks. These tasks are done faster with fewer errors, and our customers our happier. 

The task recording is awesome. I love being able to see the processes and find out the issues a lot better.

I can't really say about the pricing and licensing.

I rate UiPath nine out of 10.

We use UiPath to minimize human effort by automating repetitive business processes.

For a technically sound person, it is easy to build automation using UiPath.

We send out live surveys to thousands of people, and we use UiPath to develop bots that can take the information and create graphs that individuals can easily analyze.

We see good value in UiPath's User Community.

In most situations, end-to-end automation is possible using UiPath.

UiPath has helped improve our organization by automating sales scripts and performing daily calculations to provide quarterly profit analyses to our clients.

It has helped reduce our on-premises footprint and increase our digital footprint.

All of our users must first complete the Academy courses before working on any tasks involving UiPath.

We use AI Center and machine learning to extract more complex information from our image-based PDFs and purchase orders.

During the first six months, we faced many challenges and had to improve our processes. However, since then, UiPath has helped us to accelerate our digital transformation and reduce costs.

UiPath has helped our employees save 60 to 70 percent of their time. Tasks that used to take one hour to complete can now be done in one minute with UiPath.

Excel, PDF, and email automation, as well as document understanding, task mining, and process mining, are valuable features of UiPath.

We have two versions of UiPath: on-premise and cloud. With the on-premise version, we have good control and flexibility. However, the cloud version is less flexible and we often receive errors. We would like UiPath to make some enhancements to the cloud version to provide more flexibility for OCRs, email models, and AI centers. This would allow us to provide better service to our customers.

I have been using UiPath for two years and nine months.

UiPath is not as stable as I would like, and I hope to see improved stability going forward.

UiPath is scalable.

Technical support is good. We receive a response to urgent tickets within an hour.

Positive

The on-premises deployment was complex, but the cloud deployment was straightforward. Five people participated in the deployment.

The pricing for UiPath is reasonable.

I would rate UiPath eight out of ten.

UiPath is deployed across multiple locations. We have around 45 people that are currently using the solution.

The cloud deployment of UiPath does not require any maintenance. 

I recommend UiPath for organizations with multiple daily tasks that can be automated. However, I would not recommend it for just one task.

I use UiPath to automate tasks in our internal HR and finance departments, as well as to dispatch back office requests, close accounts, process insurance claims, and make international money transfers.

Building automation with UiPath is easy. It depends on our level of understanding of the process we want to automate. UiPath offers a wide range of possibilities for automating business processes. For example, we can use UiPath to get input data from files, extract data from databases, or make SQL requests. We can also use UiPath to manipulate applications, perform human actions on the user interface, and introduce back-office processes. Finally, we can use UiPath to distribute the execution of our automation across multiple devices.

UiPath enables us to implement end-to-end automation and orchestrate all processes using the orchestration tool. We can get the inputs for the process and execute the report at the end. We have all kinds of possibilities. For five or six years now, we have been able to automate all the processes that we faced, as long as the inputs are structured and well-structured, and we have a good flow and volume of inputs.

There are numerous advantages to using UiPath. Firstly, it can significantly increase productivity and reduce processing time. Secondly, UiPath enables scalability, allowing processes to be performed around the clock, seven days a week. Additionally, robots can execute processes with consistent quality, minimizing the risk of errors or incidents. Finally, UiPath can help optimize human resources by delegating tasks with low added value to robots, freeing up human resources to focus on tasks that require higher levels of expertise.

The time it takes to bring UiPath to market can range from a few days to several weeks. The return on investment can become apparent within a few weeks or months, depending on the complexity of the process involved.

When we refer to UiPath as a suite, it includes several tools and features that can greatly facilitate the automation process. For instance, we can group some commonly used features into a single library. Additionally, we can segregate the different layers of our development process. These abundant features can help us organize our work on UiPath, ultimately reducing our on-premises footprint.

UiPath Academy is a place where we can ramp up our skills very quickly and become operational as soon as possible.

UiPath's AI features provide a broad range of API applications, such as handling unstructured inputs. This includes non-digital inputs such as paper forms. Additionally, the system can process false inputs that are not well-organized through character recognition. UiPath also offers machine learning to further enhance its functionalities.

UiPath accelerates digital transformation and significantly lowers the associated costs. The impact is significant as it enables the deployment of production environments in just a few weeks. Additionally, RPA users can collaborate over the weekend to automate applications starting from the human interface. This allows us to automate more processes effectively. Other tools may require access to top-up bases or the use of Unix or scripts, but with RPA, we can automate a wide range of features based solely on the user interface component.

There were no expansive or complex application upgrades or IT application support required.

UiPath helped to decrease human error. By developing autonomous processes and thoroughly testing them, we ensure consistent and reliable execution, which guarantees high-quality results for our customers. Compared to human execution, global execution by robots is both more accurate and quicker.

UiPath saved us around 17 percent of our time.

UiPath helps to save costs in several ways, such as reducing the time required for execution. The main difference between manual and automatic processes is the ability to have UiPath execute tasks on our behalf, based on pre-defined reports. Unlike humans, who typically work from eight o'clock in the morning until six o'clock in the evening, UiPath can work all day, even on weekends. This can result in cost savings of up to 60 percent.

The queue feature is the most interesting to me because it allows us to work on a list of tasks in parallel on several robots.  Additionally, the ability to integrate the OCR components is valuable. We use this feature for one of our banks in Africa. These are the most valuable features that we cannot find with other tools.

The pricing has room for improvement.

I would appreciate UiPath's assistance in simplifying our process of easily and quickly capturing our customers' business requirements within our framework.

I have been using UiPath for almost seven years.

UiPath is stable.

UiPath is scalable.

UiPath's technical support is reactive.

Positive

The initial setup is complex, and obtaining a license for training poses a challenge. As a result, an experienced person is necessary to complete the deployment. Our deployment required two people.

The deployment can take one to two days for an experienced person, but for an inexperienced person, it may take up to three weeks.

The implementation was completed in-house.

The return on investment is based on the complexity of the process that is being automated.

The cost of UiPath is higher in Africa than in Europe and Asia due to differences in salary levels. As a result, the number of customers who are able to use UiPath is limited.

We pay for additional components to include features, in addition to the licensing fees.

We utilized Selenium Test Automation for tests and conducted an evaluation. However, it did not fully meet our business requirements, so we selected UiPath.

I give UiPath a seven out of ten.

Due to the quantity of customer input, the success of automating tasks is not solely dependent on the capabilities of UiPath tools. The quality of the paper scan, document quality, and resolution are also crucial factors that can positively or negatively impact the possibility of a wide range of automation. Therefore, the success of automation is highly reliant on the quality of the source inputs, in addition to UiPath's capabilities.

Our implementation strategy involves beginning with the proof of concept and then separating processes before moving on to scaling the API.

I would recommend UiPath for large enterprise companies, as the cost of the solution may be prohibitive for smaller organizations.

I recommend that anyone assessing UiPath should first create a clear automation roadmap. This will enable them to address questions related to optimization, implementation, and development.