UiPath Reviews

UiPath is used to automate processes, eliminating the need to increase headcount.

There was an increase in both quality and quantity while not having to increase admin simultaneously. We have successfully automated the majority of our automation projects.

The UiPath automation has helped us to keep our bottom lines down across the board.

UiPath has helped our organization with its environmental and social initiatives.

It has freed staff time for other tasks, improved their work quality, and saved hundreds of hours per month.

UiPath is the best automation solution available today. The process and task management are the most valuable features.

UiPath's Unassisted Task Mining has room for improvement.

I have been using UiPath for four years.

UiPath's stability is reliable, especially now that we've moved to the cloud.

UiPath scales well. We have not had any issues.

UiPath support has been responsive to us.

Positive

UiPath has successfully met our expectations by reducing project costs through automation, demonstrating a strong return on investment.

I would rate UiPath ten out of ten.

I have used UiPath in my last three companies.

We use the solution for the implementation of automation for normal processes. We deliver use cases to customers.

The ability to automate everything is great. You can also do process mining and optimize costs. It can help save a lot of money in an organization. 

Depending on the business, and how you calculate the cost vs savings, the time to value varies. 

It's a complete ecosystem. It has everything you need. You can do attended or unattended bots. There's AI. There are document processes that you can do as well.

It's very easy to create any type of automation. It's the best solution so far in the market. 

We are able to implement end-to-end automation. It's important that you can automate anything with UiPath. You are not limited. You don't have to have any extra connectors. 

It has helped minimize our on-premises footprint. You can migrate to the cloud if you like. However, many companies, like banks, do not prefer the cloud. They prefer on-premises setups. 

I've used the Academy courses. I've started one and haven't finished it. My plan in the future is to utilize it more. The structure and details are great. If you are new to UiPath, it's very good. It helps effectively onboard new people. 

It helps reduce human error. 

We can free up employee time by 90%. 

If you are saving time, you are saving money, and therefore, it has helped save costs. 

Everything is working well. Of course, there can always be improvements.

I would like to see them integrate with generative AI like ChatGPT. It might make a developer's life easier. 

I've been using UiPath since 2019. However, I have not been continuously working on it.

The solution has been very stable. I'd rate stability nine out of ten. 

The solution is very easy to scale. 

I've never been in contact with technical support. 

We previously used a different solution. 

The implementation is very easy. The deployment is similar to other products. You create a file and share it with a customer and they import it. 

Through our methodologies, we define, design, deploy, and maintain. 

Pre-deployment, we need to do some testing. After that, once it's accepted, you deploy. You don't need much staff. 

There is some maintenance required for future changes in the application and any issues that may arise (like bugs). Typically, there's a business analyst and people from IT as well as someone from whatever department it's being deployed to. 

The customer deploys the solution. We take care of the design and implementation. 

I have noticed an ROI while using the solution. In general, a business analyst would do the calculations to see how much money would be saved if a robot was deployed. 

I do not deal with the licensing. 

We are UiPath partners. 

I'm not certified in UiPath, although I do have experience with it. 

I have not used the AI functionality yet.

I'd rate the solution nine out of ten. It's easy to work with UiPath. It has very good documentation. 

I work in finance, and we have diverse use cases for UiPath.We use it for invoice processing, ML detection, and tag categorization of items that we sell. 

UiPath Action Center is very valuable. 

We ran into issues during the upgrade. It was not warned before. 

I have been using the solution for five years. 

UiPath is stable. 

The product is scalable. 

We get good resolutions when we raise issues. 

We did on-premise deployment and had to check load balancers, SQL server, and Redis. It took us about eight to nine months to get into production, which was cumbersome. 

We have seen millions of dollars of ROI. 

UiPath is expensive. 

Our business objective in automation implementation was to eliminate manual labor. Initially, we started with RPA. The finance department has a lot of manual work, including prescriptive things like driver's licenses and transcribing. We started using RPA to gain ROI.  

The use of automation has enhanced our accuracy. 

UiPath has helped us save 100,000 hours, which translates to millions of dollars saved. 

I rate the product an eight out of ten. 

I have automated finance use cases, as well as banking, NOC, and call-center use cases. I have also done email and Excel automations.

It has definitely reduced the cost of the process I have automated. It has reduced the number of employees required for some processes and improved process efficiency. It has improved accuracy and error rates. All of these factors reduce the cost of the processes.

Because there is no human involvement and there is a fixed flow that bots follow, it has minimized the human errors that occurred before.

The Excel automation in UiPath is very easy to use. Even for complex scenarios, we can easily automate the process. And that is true for email automation as well.

Building automations in UiPath is done through simple activities. We just drag and drop into a workflow, build the flow, and execute it. It's that simple.

We use UiPath Academy courses as well, and they give us an idea of how we can use it professionally. They have given us a complete idea of how to use the solution.

When it comes to web automation, a change order should be able to be handled more easily.

I have been using UiPath for almost three years.

Compared to other tools, UiPath is very stable, as well as easy to install, manage, and upgrade.

It is more scalable than Automation Anywhere.

I have not contacted their technical support.

UiPath has more costly licenses than Automation Anywhere and, of course, Power Automate.

There are multiple differences between UiPath and Automation Anywhere. Automation Anywhere has a good handle on desktop automation as well as its IQ Bots for document understanding.

I would rate UiPath at seven out of 10 overall.

We primarily use the solution for automation.

UiPath has been quite useful for the organization. It's helped reduce workloads.

The processing time is the best aspect of the solution. There are also fewer coding requirements. It takes less time to develop and implement projects using UiPath for this reason. 

It's easy to build automation. The organization has a variety of projects and we can complete the projects faster using automation using UiPath.

The product enables us to implement end-to-end automation.

We use the UiPath user community. If you have any doubts about what you are doing, you can turn to the community and they'll answer your questions - which is very helpful. 

The Academy courses are very useful. If you want to do any certifications, it's very simple.

We use the AI functionality. It helps automate processes that are more involved. However, it's something the team works on; I don't know much about it. 

The solution helps us reduce human error as we can run many projects without much human involvement. Once we reduce human interactions, we can reduce human error quite significantly.

It's also helped us free up employee time thanks to the automation. It's freed up maybe 30% to 40% of our time since we started implementing automation.

We've tried to use test automation, however, I'm not sure how well it works.

I've been using the solution for one year. 

The solution is stable. 

The solution is scalable. 

We took about three or four months to deploy the solution. The process itself is moderate. We were able to manage the process ourselves. While it's rather easy, it does take some time.

The licensing cost is quite high. It could be reduced. 

I'm an end-user of UiPath. I'm an RPA developer. 

I'd rate the solution seven out of ten. There should still be more opportunities to make the solution less expensive. 

I used UiPath for the energy sector and HR, but they were almost industrial processes. The bots were performing and doing transactions all the time.

The use cases were mostly about the extractions from several websites to manipulate data and to put data into other websites to update. We also had campaigns, and we needed to trigger and send lots of emails.

Our clients could automate manual tasks that were boring. They also implemented a chatbot using UiPath where whenever people called, they just entered the application, and UiPath could retrieve information about the person without them having to go to System A, System B, and System C.

UiPath enabled us to implement end-to-end automation. I went to a system, took the information, and went to a website to submit the information and take out the output. That was end-to-end automation.

It speeds up digital transformation.

UiPath reduces human error, but it also depends on the use cases. It has had a positive effect on our clients' businesses. 

Employee time has been reduced because bots can work faster than humans. It saved a lot of time for our clients, but I do not have the metrics.

UiPath, depending on the use case and the company's infrastructure, can save a lot of money. It saved a client's company half a million or a million. It is worth the money.

The best feature of UiPath is that it is easy to use. UiPath Orchestrator is also easy to use. 

Data scraping is very powerful in UiPath. It is very versatile.

I have not explored all the UiPath functionalities. I am exploring it a little bit more now, but they are moving to the modern experience, which is something I do not like. They are going in the wrong direction. I like the classic experience for developing, and as a developer, I am used to it, but they are going to the modern experience with selectors and other things. It might have certain advantages, but I do not like it. They should maintain the classic activities. They can consider providing both options instead of taking the classic ones away.

I have been using UiPath for almost three years.

I have always worked with UiPath for industrial processes. For instance, it was used for a company that was always processing contracts. They submitted new contracts and ended lots of them at the same time. We did not use it for filling forms or small automations. 

I have not contacted their support. I have used the UiPath Community. It is very easy to use. There are lots of people asking questions and lots of people answering them. I usually go there to consult other people. Their community is very valuable.

UiPath was the first RPA tool that I used. Before UiPath, I had only worked with BPM and BPMN solutions such as Appian and Bizagi. I switched to UiPath because my company chose it. We had a client who wanted to implement UiPath.

I have seen it deployed on-premises and also on the cloud. I do not know about the deployment of the UiPath infrastructure. I only know how to allocate licenses or install the UiPath license on a computer, which is not hard. It is easy.

It is worth the money if you have enough automation and enough use cases. That is applicable to every automation platform. As long as you have the use cases and you can automate them through that application, it will be worth the money.

It is expensive, and it is now getting more expensive. They are the number one in the market, and they are taking advantage of that. It is hard for the companies that have the full infrastructure supported on UiPath to change it. They have to keep it. UiPath is taking advantage of it.

Its cost depends on the company and the contract.

I used UiPath in my previous organization. I recently changed my organization, and I am now comparing RPA tools.

I would recommend UiPath to others if they have use cases for it.

I am certified in UiPath. I have used UiPath Academy courses. They are useful when you start developing. I have also attended their seminars.

I have not used UiPath's AI functionality in the automation programs. We started to use it, but then I changed the company.

Overall, I would rate UiPath an eight out of ten. I cannot compare it to others because I never used any other solution, but I find UiPath to be simple and easy to use.

We suggested UiPath for one of our company's clients to automate DevOps processes. This is a part the company doesn't want to touch. They tried automating with Ansible Playbook and Terraform. We wanted to eliminate human intervention altogether. We are still transitioning from dev to staging and then production. We have done most of the research. We will move from staging to production if it works with our architecture and can be scaled.

Our client is one of the biggest companies out there. There are maybe a million users worldwide. They primarily focus on the Asia-Pacific region, but there are also users in Europe and the Americas. The client has several web applications and a hybrid structure. Some data are on the cloud, while other data is on the on-premise servers. We created solutions for them over the years. We have an SI and DevOps team working in parallel for years. Our goal was to automate everything that could happen without intervention. 

It's a massive project that will take time, and we still haven't moved out of development. We try to make the processes more streamlined. All the associates are researching it and working on their parts. Right now, I can only say how it has benefited me. I've automated some fundamental DevOps tasks. 

It saves a lot of time because you don't have to come in on weekends to provide service or troubleshoot. You can automate these tasks and schedule them to run automatically. You can optimize your work and how you spend your time. For example, some services need to be routinely patched, so we automated patching every third Sunday. However, we still needed to come in on weekends to troubleshoot after the patch was applied. 

We have shadow scripting to automate these processes, but we had to go online to see if it's up and the ports are open. I automated this with UiPath and scheduled it for the weekend, so I no longer need to come in on weekends. It saves around two to four hours per week. That is about 16 hours a month. It wasn't easy in the early stages. It took around two months to understand the tool. I was also working on other projects simultaneously.

There is a recording feature that copies each step of a task. You can automate every process via this recording. It's a cool feature that helps you define the variables. I also like their trial version, which lets you experiment with the solution and learn the capabilities before buying the license.

I still haven't used the drag-and-drop APIs, but I look forward to this feature. We currently use Jenkins for our continuous integration tools. There are some APIs from Jenkins, and we extract the job details from those APIs.

UiPath's interface and user experience could be improved. The name is UiPath, but their UI is not that great. It's outdated. It seems like a 2014 or 2015 software. They should look at other products on the market.

Another thing is that UiPath lacks online training resources. Maybe they can start their own YouTube channel. You have to rely on the documentation to learn. There are some resources, but they aren't available on the official site.

We have been using UiPath for six months.

UiPath is quite stable. I haven't seen any downtime. I can also pause the upgrade itself if I don't want the upgrades to cause instability. The long-term version is available as well.

We are still in the development stage, so we don't know whether it will be scalable. 

I have never had a need to contact UiPath support. I usually try to Google answers or figure the issues out on my own. 

I am from the build release team, so I automate the deployment and build process. I work on CI/CDs and try to automate most things. The deployment was highly complex. I was new to this project, so it was challenging for me. I was learning on the job and trying to understand the process itself because it was already partially built when I joined, and I was responsible for making some of it. 

The application takes about 10 to 20 seconds to install, but it will take around a week to build the infrastructure. We are just replacing the web service, not the whole application.

We tried a blue-green strategy for implementation. We built blue nodes and ports similar to production and shifted the web services to the new one. If it is up and running and everything works fine, then we can close the previous one, and we can redirect traffic to the new one with the help of load balancers.

We have 25 people on our DevOps team who do everything from architecture to automation. They're not just dealing with one web application. There are hundreds of applications. I worked on several applications building the architecture and helping. For example, let's say we build or add some features to a project. To automate those features, we need to understand them and how it works on Kubernetes or other platforms.

It definitely needs maintenance because we deal with a large user base. It requires a lot of maintenance and downtime to make things work during staging and development. Maintenance is always necessary, and we are the ones who maintain it. We have four or five people on call weekly to maintain the solution. They are the responsible people or points of contact for the developers or application owners if something goes down or goes wrong.

UiPath's price is reasonable. It's not so high relative to the capabilities. I don't know about different licenses or more premium versions. Prices are negotiated on the corporate level. 

We considered Automation Anywhere. However, It doesn't allow for an extended trial. We needed to purchase a license after 50 tasks, and we didn't have enough budget to experiment. Blue Prism is also there. We had the same problem. There wasn't a trial version.

I rate UiPath eight out of ten. UiPath has excellent features, but you need to be patient enough to learn.

I work at a financial firm where we do trade settlement activity. We are using UiPath for cleaning up data, doing reconciliation, and finding where the trade breaks and trade files are. It helps us lay the groundwork for the value add work, which comes later.

It allows us to grow our business. The use case that we have is a huge time saver because we do not have a lot of volume right now. We are looking to sell part of the business and get more clients onto it. The only way we could do that or even open that door for possibility is to automate and go through a lot more volume. 

Our teams are under huge pressure because trade volume has gone up over the past year. UiPath is just getting us back to the status quo and then also opening the pipeline for more volume to go through. We have a very strong program that encourages people to get trained up on tools. 

StudioX is going to be a big game changer for us. We found with the other tools that we use that as soon as we put UiPath in the hands of everyday users and ops users, they will be able to quickly learn it. This will make a big impact because we will get big volumes and projects coming through.

UiPath has done a good job coming up with the broadest use cases. However, I would like to see them dive into more industry-specific use cases. For example, checked OCR and brokerage statements are common. Anything unique to the financial industry would be useful for us.

We have using UiPath since February when it got brought into our team. We just had our first box go live about two weeks ago. We have had three go live so far; one using StudioX and two using Studio.

So far, I haven't heard any issues. We are always going to expect issues, but so far so good and I hope the stability is good. Alteryx had issues at times, which created some pretty big problems. Hopefully, UiPath will not do that as much, because we are expecting to lean on it.

I have not used them directly. 

It was not so much a switch for us. We are still using Alteryx. UiPath is a much better automation tool than what we were using before because it was self-service. We didn't have to have our COE build it and related solutions for us. We have similar functionality with Alteryx. Anyone can learn it and start building and go through our governance process. Doing so, they can have a huge impact on their team.

We are a large company and the initial setup took our COE quite a few months. However, I believe their experience was positive overall. A lot of the issues we had were internal and concerned how we were going to do our governance. We were very strict about that. 

Getting people access was easy and so was learning to build. Everything on the UiPath side went smoothly.

We're a mature automation team. Over the past four years, we've delivered well over 150 FTE. We're always looking for new tools and to pick up some of that automation that we couldn't do before. 

UiPath has helped with data scraping and plugging into websites and combining that with Alteryx. We can attack 90% of our use cases now. We can not deal with the other 10% for internal governance reasons and not so much capability.

The three use cases we have implemented with UiPath have saved about half an FTE. 

I know that the reason we went with UiPath is because it is a lot cheaper than the other vendor we were using. It is of a better quality as well, but it is less expensive to run on an ongoing basis. 

I'm not sure if we evaluated other options. My team does not look into the suite of options. We have a separate COE that sets everything up for us. We are tasked with implementation. 

My advice is to first build a good team that you can trust. Because great tools are useless if you don't have any builders or people that know how to use the tools. That is what we have been focused on. Also, have very specific support for your team.