UiPath Reviews

I use UiPath to automate getting the relevant data from Excel and PDF files and for normalizing the data.

It helps reduce human error in data retrieval from PDFs and Excel documents. We get accurate output that is easy for us to make decisions on, helping us move forward to next steps. It makes us more productive.

End-to-end processes are useful for us because they give us positive output and increase our business productivity as well as staff availability. It saves a lot of time and human resources.

The amount of time an automation saves depends on the complexity of the task. Some save a lot, some save less, but it works well for us.

Automating tasks makes them more scalable and makes our client relationships better. We are able to provide solutions in less time than we expected.

The most valuable feature is the ability to retrieve data from Excel files, including filtering the data. It is also straightforward and easy to navigate when building automations and makes our tasks easy to perform. It is very easy to use without any prior coding knowledge.

Another important aspect is the UiPath community. It's critical when you face an issue. You can post it to the community and there are always people there who are ready to solve your issues. It works well in every scenario, and I would give a 10 out of 10 to the user community.

The UiPath Academy also helps a lot. I did a course last year because I wanted to know more about the new features. For anyone who wants to improve their skills related to UiPath, they should do courses from the UiPath Academy. It's very helpful.

The user interface needs a little bit of improvement because it looks a little cheap due to being a very old tool. Otherwise, it works well.

I would also like to see the ability for applications to work offline. Currently, they only work when online. If that is possible, that should be included in a future release.

I have been using UiPath for the last two and a half years.

The stability is good, a 10 out of 10.

The scalability is also good. I give it a 10 out of 10 for scalability.

Last year I faced an issue related to UiPath and I posted a question on the developer community forum. After approximately two to three hours I got a response and that was all I required to resolve the issue.

Positive

I used Microsoft Power Automate. I switched because UiPath is cheaper and it has a large developer community.

It gives a great ROI. If you invest $1,000 in a project, it returns approximately two to three times, or $2,000 to $3,000. 

The time it takes to set up an automation depends on the project size or complexity. It can take 15 or 20 minutes, and sometimes, it takes hours or a whole day.

Sometimes maintenance is required because it slows down due to new features or an upgrade going on. 

We have about 10 to 15 people maintaining things, doing testing or helping when anyone faces an issue. We have 200 to 300 end-users in our organization.

We use UiPath for replicating manual tasks and PDF automation. 

UiPath saves us a significant amount of time and is recognized as the leader in Robotic Process Automation. It helps us a lot. It makes us much more efficient at dealing with repetitive tasks, reduces costs, and makes automating processes easier compared to other automation solutions.

The solution reduces human error; automating manual cases lowers the risk of error by over 90%, including recurrent mistakes. This keeps our clients happy.  

The product frees up a significant amount of employee time by automating manual tasks and being so user-friendly and time-efficient, meaning we don't have to spend much time using the app. 

I like how easy it is to automate tasks and how time-efficient the product is.

UiPath is very user-friendly, so even employees with no coding experience can use it, which adds value to staff with less experience in coding.

Building automation using UiPath is easy; creating scripts for automated test apps and PDFs isn't difficult.  

The solution enables us to build end-to-end automation, which is important to us, and it's one of the only automation apps that can provide this.   

We use the platform's AI functionality in our automation program, which has significantly contributed to our end-to-end automation. It's cost and time-efficient, and that's what we want from an automation app.   

UiPath speeds up and reduces the cost of digital transformation without requiring expensive or complex application upgrades or IT support. It provides features in a cost-efficient way.  

The interactive selection could be more accurate.

The customer support could be faster. 

We've been using the solution for between three and six months. 

UiPath is a stable app; I give it nine out of ten for stability.

The solution is scalable; I can't see any ways in which there would be a problem or limitation with scalability.

We contacted technical support, and they have solved most of our issues lately. Sometimes we don't get the solution we want and are dissatisfied, but overall, I rate them very highly.

Positive

UiPath is the only automation solution I have used. 

I wasn't involved in the solution's deployment, and apart from keeping the version up to date, it doesn't require any maintenance. 

The solution saves costs for our organization, though I'm not aware of precisely how much.

We didn't evaluate any other options, the company provided UiPath, and we didn't have a choice in the matter. It's an excellent product, and we don't have any problems with it. No solution is perfect, but that's to be expected.

I rate the solution 10 out of 10.

We use UiPath to automate processes that deal with a ''good cause'' we are involved in; specifically, we use it for employee diversity.  

The product's automation helps a lot in achieving the results regarding our ''good cause''; we encounter fewer errors compared to other automation apps.

Being a part of the UiPath user community is valuable.  

I recommend the solution and have recommended it to many of my friends who work in the same domain. 

We have yet to use any UiPath Academy courses, but we plan to in the future.

Our company uses the solution for financing, accounting, and commercial operations. Right now, we are automating the lowest-hanging fruit. We look at people or personal productivity and automate their desktop tasks. 

We currently do not use AI functionality. 

The solution saves our company 10,000 hours annually. Automations have removed menial tasks from people's desks so there is instant gratification.

Studio and StudioX are really powerful tools. From the development side, business users have realized much success and have made great strides with StudioX because it is easy to use.

Automations are really easy to build with a minimal technical background. For example, my background is in accounting and finance but I am the manager of an automation team so that speaks to how easy it is to learn and develop. 

It would be useful to have co-authoring because we have many staff members working on the same project. 

I have been using the solution for four years. 

The solution is fairly stable. We have to perform maintenance on things we are doing and see some infrastructure issues for on-premises users. Many of these issues would be addressed if we switched to the cloud so that is under consideration.

I can see the solution's scalability. I think you need the right organizational buy-in for scaling but there isn't anything that the solution should be doing differently. 

The community is great and we learn so much there. We would like the community to bring back in-person user groups because we found a lot of value in knowing and connecting with other customers in our area. But, the community as a whole is awesome and invaluable. 

When we started our journey with the solution, we utilized the Academy for training. Since then, we have used the Academy to train three new team members because it quickly gets them up to speed so they can start developing. 

Technical support is good and we utilize it a lot. Sometimes it takes a little while to hear back from support. Though we understand, it also causes us heartache when tickets are automatically closed without a response. For example, sometimes we contact support on a Friday and the ticket closes on a Sunday which does not give us time to review our email and can be difficult. Otherwise, we like the technical support provided and rate it seven out of ten. 

Neutral

Our company did not previously use another solution. 

I was not involved in the initial setup. 

The price is high in comparison to Power Platform that Microsoft provides as part of its enterprise license. 

The pricing can be a bit confusing because many new products have been added. We just renewed our licenses and got all new SKUs because products have changed so much since our initial implementation.

I was not on the evaluation team but I do not believe other options were evaluated. The solution was chosen because it was a known leader in the industry.

The solution is great, works well, and is learnable. Users will be able to pick it up easily. People who are interested in change will find a way to make it happen, so you might as well give them a good tool.

There is nothing comparable in the industry that provides the same ease of use, great community, and good products.

I rate the solution an eight out of ten. 

We have a lot of use cases. A lot of them are based on SAP transactions. From SAP to SAP, or SAP to local documents, or local documents to transfer information to SAP.

The main benefit is to save manpower in-house. The second benefit for me is avoiding printing on paper. That is the second KPI that I am working to reduce in the company, reducing paper usage. In one project, for example, we managed to save more than 1,000 pieces of paper daily.

The UiPath Studio has been very necessary for us. 

Orchestrator is a vital feature. We have a sizable infrastructure, so it is necessary to have Orchestrator deploy all of the robots in all of our servers. It is not possible to work only with one computer. Therefore, that is an essential feature for me.

We've been able to save on man hours. We save around 60 manhours daily per department. For example, the maintenance department works with many people, and we can save on labor.

All departments use automation; however, mainly the logistics department benefits. The finance department comes in second, and after that, production. We've created more than 40 automation so far. We use both attended and unattended robots. 

Even if you are just on a laptop, you can have UiPath. 

I've used the UiPath Academy. It's necessary to have credentials for the infrastructure. It helps us understand the features of UiPath properly.

I use the UiPath community a lot. When I have a job, I can write a question about it and get a response from an expert. It's quite a valuable service. With the community, we can reduce the time to resolve issues. We can learn from other people who have faced similar challenges. 

Setting up automation can be easy or complex, depending on the project. 

All documentation and transaction areas can always be improved. 

We'd like to see mobile robots in the future. We have a lot of cell phone tasks, and it would be ideal to replicate automation from the iPhone, for example. If you were at a certain location, you maybe could set up an automation that could send a message or open a cart. 

I've been using UiPath for four years. My company has worked with the solution for longer. 

The solution has been 95% stable. 

It's a very good tool, and it's easy to expand in terms of infrastructure. If we need more space or more servers, it's easy to just deploy more. 

I have no experience with direct UiPath support, however, getting help from the community has been great.

I did previously use Auto ITX. It's a library from C# Program. It was only local. I don't know if was a standardization. I'm not sure why the company ultimately decided to begin using UiPath. This product is easy. It's drag-and-drop and very simple to use. 

I have developed automation and uploaded Orchestrator. That's it. I didn't handle the initial implementation. 

I'm a developer and therefore do not handle the licensing aspects of the product.

We're UiPath customers. 

I'm not sure which version we are using. I know it is not the last one. 

I do not use the AI functionality just yet. That's new to me and very interesting. 

While I would recommend the solution to others, it is necessary to have a good developer who understands the tool's value. Technical knowledge is necessary.

I'd rate the solution ten out of ten.

We have multiple use cases for this solution. We have applications built on Microsoft platforms and we use UiPath for our automation and automation testing. Being able to do this means that we do not need to keep reverting back to test every use case when we complete upgrades. 

We also use this solution for the automation of responses to support tickets. Any tickets that come through that can be automated, rather than it being done manually. 

UiPath has improved the ease of building automations. We were using SeleniumBase testing which is a legacy application and required a lot of manual work to maintain it. 

UiPath has made a significant difference on our staff's workload capacity and freed up team members to take on new endeavors versus getting stuck with manual tasks. 

This solution has been most valuable for our support ticketing processes. This has created efficiencies within our team and freed up time for them to focus on project work. It has prevented the need for them to stop what they are doing to complete a mundane task and then get back to what they were doing. 

We previously built automation repositories before it was offered by UiPath. There's no smooth migration from what we built to the newer studio that they have at the moment. This is the biggest hurdle we are facing. We would also need to rebuild all previous automations built in another solution called SeleniumBase.

I have been using this solution for one and a half years. 

We experienced some performance issues because our libraries are growing and we experience crashes from time to time. This usually means we need to reboot. The stability could be improved in this regard. The ability to handle large-scale applications or multiple applications could be improved as our operations and libraries are going to continue to grow. Currently, our libraries need to be split and this creates more maintenance for us. 

We are satisfied with the scalability. We are aware of new features coming in the future and we will be able to adapt and expand our applications based on these new features. 

The technical support for this solution could be improved. They take longer to respond than I would expect. We would like a 24 to 48-hour SLA in place to manage expectations. 

I would rate their support a six out of ten. This is not due to their ability to resolve an issue. It is due to their lack of transparency and keeping us updated on how issues are being resolved. They are not good at communicating when we can expect our issue to be resolved. 

Neutral

We used SeleniumBase. We needed a solution with enhanced technical capabilities and this is why we switched to UiPath. UiPath offered us a lot in terms of functionality. 

I was a part of the implementation team in our organization where I made sure there were no roadblocks. I was working with UiPath's points of contact and they were coordinating and making sure the implementation happened as planned.

The initial setup was complex. It happened three years ago and we still have some questions about the setup. In order to get answers to these questions, we need to raise a support ticket. I feel like the knowledge of the support individuals could be elevated so we could receive answers right away. 

We implemented this solution in-house. 

We have not yet experienced ROI using this solution as we have only been using it for a year and a half. We don't have control over the domain to see the metrics and KPIs at the moment. We are hoping that once some of our core applications are in operation, we will be able to assess the ROI. 

UiPath has reduced our manual effort and improved the overall efficiency of our team. 

We considered Microsoft's Power Platform which does offer very similar functionality to UiPath including a Desktop AI Builder. However, this solution had limitations that UiPath does not. UiPath is focused on automation and offers a lot of support in this regard whereas Microsoft focuses on so many different areas. 

I would advise others to hang in there for the first six to eight months as the initial learning curve can be frustrating. Once you get a hang of it, you will clearly see the benefit of using this solution. 

I would rate this solution an eight out of ten. Our test automations need to be improved for migration purposes and overall performance could be improved. If those two were resolved, I would give it a ten out of ten. 

My organization is an outsourcing company. We work with various clients. So, we have many use cases. The current use case I'm working on is related to invoice processing.

We don't use attended automation. We use its AI functions a bit. Usually, we work with document understanding.

Currently, I'm using the latest version. It is deployed on the cloud and on-premises. It is the UiPath cloud.

It is easy and fast to build automation using UiPath. All of our automations are created with UiPath. Usually, we do automation for SLA purposes. Most of the time, the clients don't have enough resources or humans to do the job, and they need automation to improve the SLAs.

It enables us to implement end-to-end automation, starting with the process analysis, robot building, and monitoring of automations. It is good for my company. With these benefits, we can implement it and help with the monitoring.

It has reduced a lot of human error. For example, in the project that I'm working on, people were putting the invoice information on a daily basis. There were more than 20 invoices per day, and each invoice had more than 100 line items. Humans would do a lot of mistyping on the number of packages or the number of items in the package. After we applied the document understanding solution there, we can handle around 90% of invoices, and all of them are correct.

It has absolutely saved us time. It has probably saved us more than 20% of the time. People now have more time.

I feel comfortable with UiPath. The thing that I like most is that UiPath has a very large community and a large ecosystem. So, it is easy to connect with other applications or platforms.

UiPath Apps is a great feature, but it still needs time to evolve. They need to add more features. It hasn't increased the number of automations we can create while reducing the time it takes to create them.

I don't like the sequence feature in the UiPath. It is difficult to analyze and read the code.

The variable management is really messy. When I look at the code, I don't know where the variable is and in which scope.

I have been using this solution for around five years.

It is stable.

It is scalable. We have had three enterprises that are really big with more than 1,000 people. The others are small companies.

In our organization, we have 12 people working with it.

I haven't contacted their support. I have been using UiPath's support indirectly. I just put a question on the community forum, and they answer it very fast.

In the previous version of UiPath, it was a nightmare to set it up, but now, it is really comfortable and convenient. Overall, it is fast, but the deployment duration also depends on the solution. If you design a good solution and follow the best practices, it is really fast. It takes a couple of hours at the most.

We always try to split a project into small parts so that we can test each part and apply it easily. I have seen that many people create very big projects, but when you complete them, you cannot test them. It takes a lot of testing from end to end, and we still can't test it completely. That's why we try to split a project into small parts. We can test each part independently, and after the integration, we can deploy with high confidence.

I am not sure how long it takes for our clients to see its benefits after we deploy it for them.

We have a maximum of five people for deployment and maintenance. We sometimes have issues with the infrastructure. In many cases, the infrastructure is handled by the client, and there is no support or cooperation between the RPA department and the IT department. Usually, they will be late, or they did not check our requirements to deploy the bot.

If you use the cloud model of the UiPath, it will reduce a lot of the total cost.

Its AI functionality hasn't enabled us much to automate more processes. Most of the time, when we propose those functions, we don't have an agreement with the client because of the license price. Currently, the license price is the major obstacle.

My advice would be to contact the UiPath sales team directly. I know that they have different license models for different clients and regions.

I would advise following the UiPath Academy and their best practices. That is enough.

They provide very valuable templates for automation purposes. It depends on your purpose, but you can apply the ones that are already there.

I would rate it an eight out of ten.

We use the solution to speed up automation. We were looking to overcome the challenge of handling vast amounts of data, and we use UiPath to create bots to handle that. Tasks can be automated, and human error is reduced.

UiPath improved our organization as it has many benefits; it's straightforward and quick to use, has excellent third-party integration, and simplifies all our task automation.

The software has an excellent UI; it's very user-friendly. The drag-and-drop options are some of my favorite tools, as they speed up the process, and I find that UiPath offers a solution for all kinds of automation.

The solution saves a lot of time via automation; a task that took over an hour now takes around two minutes, and it's all handled by bots.

We use the drag-and-drop options, and they speed up our workflows.

The pricing could be more friendly. 

We have been using the solution for one year. 

The solution is stable, it's a reliable software. 

The product is scalable; it has very good third-party integration and scalability options within the software.

We use the solution in our office, so there are slightly under 100 total users.

The community support and documentation are helpful. I required some training initially, and was able to learn using UiPath websites and YouTube videos. 

Positive

I wasn't directly involved in the initial setup, but it took our team one to two months to get to know the product well.

I'm not directly involved in the financing, but the IT team considers this product costly.

I would rate this solution a nine out of ten. It's an excellent product, but there is always room for improvement. 

I highly recommend UiPath as it's easy to learn and offers significant advantages for all kinds of automation. 

The solution is perfect for our requirements. 

We have four robots. One we're sending out shipping labels as our members do returns. Once they create a return, we used to have someone that was manually entering in and creating the shipping labels. That was like the first robot that we built. The cost savings on that alone covered the costs of UiPath in total. We have a few other ones that we've been playing with, however, that first one was a big one that covered the cost of UiPath. 

UiPath has freed time for our employees. With the shipping label robot, for example, we basically replaced two jobs and now they're able to do other things. They can take on other more vital responsibilities.

I'm really excited about task capture. We haven't started it yet, however, that's going to really help capture the processes that we want to automate. We're excited about that.

The solution is just opening our eyes to what is possible. There are a lot of people in our company who hate doing mundane repetitive things. It's giving enough hope that we can replace those jobs that people hate with automation. We're excited about that.

I'm not a developer, however, the two developers that are under me, like the shipping label bot and found it easy to build. A developer was able to create that in one day and it replaced two positions. I'm sure we can build it better and faster with what we're still learning. With a partner coming on to guide us I foresee that we will definitely get better at it.

We’ve used UiPath's Academy courses. I don't think we would be where we are today without it. My two developers had zero experience with UiPath. They went to the Academy and learned as much as they could and started building right away.

Its biggest value is the continual learning on offer. We're pretty overwhelmed right now with what it can do, however, the Academy just teaches us how or where we can go with it. It’s great.

The setting up of the cloud was a little bit confusing for us. We expected someone to walk us through that process and we just did it ourselves and weren't sure if we were doing it right. We thought that getting assistance with the setup would just be kind of a given or they would at least lay out the steps. We didn't have that. We were asking a lot of questions and trying to figure it out with our salesperson. She was likely not the right person to help us with that. If there were directions on how to set it up, that would have been helpful.

We've had the solution for three months. 

In terms of stability, the robots have been running well. That said, we've had a few failures that we had to go in and fix, however, it was a pretty minimal effort to fix them. I'm not sure of the exact reasons. I remember my developers were telling us one failed and we needed to go figure it out.

It wasn't like an all-day fix. It was just a pretty quick fix which required simply stopping it and restarting it and then it worked. 

In general, for stability, it's been so far so good.

We have the goal of scaling, however, we are still just barely with our heads above water. We're just trying to figure it out as we go. Our biggest asset is bringing a partner on to help us and allow us to build up that scalability. Without their help, we would be lost. We would build without having a good foundation. The partner is coming on for a three months contract to train us and get us up to speed to make sure that we're building a good foundation so that we can scale.

We first created a technical support ticket when we had the issue with the trial license versus our actual license. It was hard for my developer as he didn't have the URL for the cloud. He really couldn't diagnose the issue as we thought it was all on the one referred to us, yet there was that disconnect. We went back and forth over several days trying to figure that out and the tech person couldn't help us. We were lost there. That was a little confusing.

This feedback isn't against the technical team. Maybe it was just the way we didn't get the correct training we needed to set up correctly. UiPath should've killed those trial licenses or transferred them and they never did and that first robot we built was on a trial license. 

It would have been helpful if they told us to import the robot or something over to the real licensing. 

We did not use a different RPA solution previously.

I'm not a tech person, therefore, the setup was a little outside of my wheelhouse. It was a little bit harder for us. We've been trying to figure it out. 

The issue that we've found is we had a trial license and my two developers were on the trial. Then, when we got the actual licenses, a developer was still building under the trial. The trial was allowing them to do things and build over there, however, it wasn't under our automation path. It took us a while to figure out what the disconnect was as I just didn't know how to set everything up. That was a little bit confusing.

We realized ROI on our first robot. 

The automation cloud offering did not decrease the total cost of ownership of UiPath. It was a little bit more, however, we didn't have to set up our own server and maintain that.

We bought the starter package and we were able to cover the full cost of it with one robot within two days. It definitely paid for itself.

We were also looking at Automation Anywhere and it was a pretty close tie between the two.

We chose UiPath as a colleague who had worked with UiPath at his last job and he was a little bit more familiar with it. We thought the security was a little bit better in UiPath as well. Those were the two main reasons that kind of pushed us towards UiPath.

We haven't used the UiPath apps feature yet. We've signed up with someone that is going to be our partner to help us learn all the new aspects. Hopefully, in the next couple of months, we'll be setting everything up, including the automation hub, and trying out apps and task mining.

We do not yet use UiPath's AI functionality.

Based on my lack of knowledge, I would probably rate the solution at an eight out of ten. We've been super happy with it this far and from all the things I've seen, we're excited about where we can go with it.