UiPath Reviews

I find the solution easier to use than other platforms and it's a user-friendly way to automate.

I work with Excel files, and I find it helps make it easier to work with the files.

The ease of building automation is okay. I just use the community version, however, I have found it's much better than others. Their community version is more user-friendly than many options. I really appreciate the useability of document processing. I mostly use the solution for document processing and invoice comparisons. It's simple. 

I've used the user community and have been in touch with one person who was very helpful. They've helped guide me. I've gotten positive responses and good answers. It's helped me learn how to do comparisons between two Excel files, for example. 

I've enrolled in UiPath Academy courses. I've also enrolled in Coursera courses. I'm still in the learning process. They have good tutorials.

I've used some of the AI processes. It is very efficient to use the AI functionality. We've gotten very good responses and results so far. We have found the responses we're getting are good. It helps with creating more efficiencies. 

It has helped speed up digital transformation. 

UiPath has helped to reduce human error. We're able to build effective automation. We're creating software boards where the bot will do what we say and pull what we are trying to pull.

The solution does help us save time.

I'm still learning the solution; it has yet to help me save money.

I'm not sure how UiPath is at data scanning. I need to look into this further.

They need to work on security.

I have used the solution for about one month.

I haven't faced any stability difficulties, at least on the community version. 

I've never contacted technical support.

I've used Power Automate and ElectroNeek. I found there were a lot of issues with ElectroNeek and Power Automate. For example, they are not good with ChatGPT or data scraping. They are also not as user-friendly.

The solution was very easy to set up.

The implementation took only ten to 15 minutes. It was my first attempt to set it up. Aside from an internet issue, I had no problems. 

I handled the initial setup myself. 

I don't have any insights into the pricing of the solution. I'm using the community version. If I like it, I will buy the paid version.

I'm an RPA developer who started working with the solution. I recently worked with Power Automate. I'm familiar with the UiPath community version. I'm not extremely familiar with UiPath as I haven't used it for very long.

I'd rate the solution nine out of ten - at least, for the community version. 

The use cases have been really broad for us. We have been trying to go in a bunch of different directions. The use cases started out small with attended automation, trying to automate a bunch of reports for our operations departments. That's where we started just to prove the concept, and now we're branching out into some of the document understanding.

We're in the financial services industry. I work specifically for our security clearing division. I do stock trading, bonds, and all that kind of stuff. Our main objective was productivity, trying to prevent from having to hire so many people to run our ops department.

We have also done task mining. It has been really great for us. It's helped not only document what we're going to do for automation but also document processes in general. There are a lot of departments that just don't have any documentation. 

We've really been leveraging it in that way to try and get better documentation around all processes. 

The features we've used are somewhat limited at the moment. We've been doing a lot of basic reports. We automate daily reporting tasks. 

A lot of our back-office business is driven around emails right now, and there's no automation whatsoever around any of that at the moment. That's where we're really looking to go.

The biggest struggle that we've had is understanding how to get in and properly set up all the architecture and orchestrate everything correctly from the get-go rather than trial and error and then fixing it as we go.

I have been using UiPath for a year. 

I haven't had any issues with stability. 

We have a very small team at the moment, so we're still trying to scale up.

Scalability is open to interpretation because it depends on how your environment is set up. 

Personally, we have to deploy a lot of our stuff on our own servers, behind our own firewall. It's left up to us to maintain the scalability, whereas other firms may be able to use more of the cloud robots and not have to worry about it as much. 

Scalability has been a little bit of an issue, but it's our own issue, not really UiPath's issue.

The customer service and support are very responsive and helpful. We have run into a few issues where they haven't been able to give us a definitive solution.

For example, one of the biggest issues we've had is that we have a lot of integration issues with our Outlook. I don't know if it's how we set it up or issues with UiPath activities, but we've been struggling there and going back and forth with support.

Positive

We use Microsoft Power Automate a little bit. Power Automate has a little bit of orchestration. UiPath is definitely a lot more sophisticated. That's definitely a big advantage at the moment.

Our use case for Power Automate has been very limited at the moment. Mainly, we've been targeting areas where we struggled with UiPath and using Power Automate, mostly in the Microsoft integrations where that works seamlessly out of the box. In contrast, we've run into some hurdles around certain Outlook and Teams-type activities with UiPath.

We're using Cloud Orchestrators so the setup was pretty straightforward. We have its cloud Orchestration by all of our robots running on-prem servers.

There were two people involved in the deployment process. 

Initially, nobody bought in on the idea of automation so we started building small tasks that we could show to people. It was mostly attended automation on desktops to let the users see how the program works and get comfortable with it. 

We started building a bunch of little automations that aren't huge time savers but demonstrate how UiPath can work for people. That was the implementation approach we took.  

Now we've got some buy-in. People understand who we're starting to reevaluate, try and scale the program, and do it the right way this time.

We have seen a return on investment. We're mostly calculating the time saved at the moment. Now we're starting to get a little more into the cost-benefit analysis of things because we have a a program running. 

For this first year, our biggest metric has been showing upper management the time saved so that we can calculate the number of employees that we need.

The pricing is justified at the moment. It's definitely significantly more expensive than other competitors out there, but at the moment, its technology is good enough to where UiPath can justify it. It'll be interesting to see in the years to come, once Microsoft starts competing more, what the pricing ends up looking like.  

UiPath is definitely the leader right now. I would rate it a nine out of ten.

If you have the resources, try UiPath. Get some consulting to set everything up properly from the get-go, so you don't have to go back and redo it the way that we've done. 

No matter what approach you take, you're going to see some benefit from using it.

We use UiPath to automate business processes. 

The tool's most valuable features are document processing and AI Center. 

I want a dashboard on pending and ongoing automation in Orchestrator. Currently, we have to check folder by folder to see them. 

I have been using the solution for two years. 

UiPath is a stable product. 

The solution is scalable. 

The tool's tech support team is helpful. They will jump on a call immediately in case anything goes wrong. 

Positive

UiPath's pricing is expensive but reasonable for the quality of service that it provides. 

We have saved more than 1000 hours with automation. We have around 100 automation. We save a lot of hours. 

I rate the product a nine out of ten. I recommend it to my friends and clients. 

In my last company, we focused on Document Understanding. We received medical claim forms through Outlook and extracted the data from them. That is one use case. At my current company, I'm doing SAP automation.

My organization has automated around 200 daily processes that were previously manual. Some things that may have taken weeks in the past can be completed in a few hours. UiPath has reduced the costs of digital transformation and improved our productivity because the processes can continue running over the weekend when no one is in the office. 

I like UiPath's Document Understanding and OCR functions. That's UiPath's advantage. It has a native OCR tool, whereas other tools do not, so it provides an end-to-end solution that covers everything. We do not need to integrate other applications. 

It's effortless to build automations in UiPath. Anyone can learn it because it has a drag-and-drop interface. We only use about 10 percent coding. It's easy to understand. The UiPath Academy is also available for anyone who wants to learn the solution. The academy courses are free, and you can get a certification. Anyone can take advantage of it.  

I would like UiPath to add built-in ticketing to Orchestrator so you can raise a ticket directly to the vendor inside the solution and send the error information. We have to build our own error-handling process, which is an enormous task.

I have used UiPath for a little more than a year. 

UiPath is mostly stable, but we have encountered an issue after an update where a process created under a previous version may fail, so we need to update the bot. 

UiPath's scalability is excellent because we are automating processes in India and other countries. We have already automated more than 200. 

I rate UiPath support eight out of 10. 

Positive

I have used Automation Anywhere and Power Automate. UiPath has an advantage over other tools because it can perform end-to-end automation and cover more activities.

Deploying UiPath is straightforward. One person is enough to deploy the solution, but I may need to contact the solution architect if I need access to something. We deploy to multiple locations because we are a multinational company, but we are not providing services to any other company. We have our internal clients, including stakeholders in Denmark, Norway, and some other countries. 

I rate UiPath nine out of 10. UiPath is better than other competing technologies. 

We use UiPath for SAP automation, detecting document sections, web automation, and external applications. 

We use both UiPath RPA and UiPath Document Understanding.

UiPath Document Understanding is for data extraction, while we use UiPath RPA for basic purposes and use .NET.

We also used UiPath once to automate processes dealing with good causes, particularly in Ecolab. The company dealt with floor cleaners and hand sanitizers for hospitals in the US, and at that time, the demand for sanitizers and floor cleaners was through the roof. It was so high that we had to automate processes using UiPath to fulfill the number of orders coming in, for instance, thirty thousand orders a day.

We use UiPath in multiple departments, such as HR, Procurement, and Manufacturing.

We were able to scale our automation and operations through UiPath, for example, up to thirty thousand orders a day, and the direct impact was that all hospitals could order whatever they needed from our company and get what they wanted.

UiPath also helped us send information, particularly the list of requirements to vendors, for example, the number of materials needed, the size of each material, etc., so we found UiPath useful.

One of the features of UiPath that we found good is Document Understanding. We also like using the prebuilt AI models in UiPath rather than creating our own AI models.

We also liked how UiPath enabled us to implement end-to-end automation.

The UiPath Community is very good. When UiPath started, there was no community and documentation, but then UiPath built its community and started giving all courses and training for free along with IT requirements. We found that very helpful, especially then, because other solutions, such as Blue Prism and Automation Anywhere, were not providing free tutorials. Only UiPath provided free tutorials; it was the first company to do that. It even gave practical use cases along with the required data and even built its own application and website, which was why we could automate, including learning about automation.

We found the UiPath Community very helpful because we get answers when we input some queries. We feel that it's always good to look in the UiPath Community to keep learning from the questions other users ask and even reply to questions by other users. If we want to dig deep and further understand how things work, we go to the UiPath Community, which we find good.

The UiPath Academy courses beneficial. I've even completed the advanced course there.

We started using the AI functionality in UiPath for our automation programs. As the solution comes with three built-in AI models, we like that we can directly use those current AI models rather than building custom models. We can plug and play the built-in AI models in UiPath, which helps make our development faster than last year's development speed.

We found that UiPath made digital transformation happen within our company. Digital transformation increased for us.

We also like that the solution helped reduce mistakes and freed up the time or hours of our workers, as seen on our dashboard, which helps keep track of the number of hours worked. UiPath helped in freeing up sixty percent of the workers' time.

An area for improvement I saw in UiPath is API integration, particularly with Microsoft. If you compare my experience with Power Automate in terms of integration, it is seamless, and you don't have to create trust with other applications. Integration via Power Automate is easy, more of dragging and dropping and then starting, which is still not the case with UiPath, so that should be improved.

I've been working with UiPath for eight years now.

UiPath is a stable solution.

Scalability-wise, I'd give UiPath a seven out of ten.

I would rate the UiPath technical support as eight out of ten.

Positive

The initial setup for UiPath was a bit complex in 2017 because the documentation available at the time was not that great, but nowadays, setting it up may be fine.

We've seen ROI from UiPath in our organization.

Whether UiPath has reasonable or expensive pricing depends on the scale of your organization. It could be a bit pricey for startups, but if you belong to at least a mid-level organization, then the pricing would be okay.

I'm a customer of UiPath.

Whether building automation in UiPath would be easy or difficult depends on the application interface or the website. You first have to check if the application, interface, or UI is going to change over some time. If it won't, you must check whether the selectors are stable enough or if there are runtime changes. This is the initial check you must do to determine if it would be easy or challenging to build automation in UiPath.

In terms of UiPath minimizing the on-premise footprint, my company doesn't have anything on-premises except for SAP systems, so most of it is on the cloud and a portal.

I cannot exactly see currently if company costs were reduced or not by UiPath.

In terms of my organization's implementation strategy, the team started with one bot for development, which was the attended bot, and then scaled it into ten or twenty bots and also used bot operators for the implementation, and then after COVID, switched the automations to unattended.

The number of people required to deploy UiPath depends on the number of deployments your organization has.

UiPath requires some maintenance, but since my organization moved to the cloud, the maintenance part is only secondary and only involves updating the firmware, so there is no maintenance from our side.

Overall, UiPath is an eight out of ten for me.

My advice to others looking into implementing UiPath is to deploy it at a medium scale rather than deploying it at the start, as that would be a bit expensive.

We are a distributor and most of our customers were manufacturing and financial companies, so the use cases fell into categories like financial, accounting, and procurement departments. We used it to improve business processes.

With UiPath, my clients were able to free their employees and staff for other types of work. They saw value in that. Staff didn't have to get up at 6 AM or work around the clock in front of a monitor all day. It freed up staff that had been doing menial, manual, repetitive tasks to do something more valuable.

In some cases, it reduced the time it took to get a task done from hours to a couple of minutes. Workflows that would take up to four or five hours were reduced to taking 10 to 15 minutes.

It also definitely reduced the amount of human error to almost zero. 

UiPath Studio has all kinds of tools and it's practical to navigate around the application. Implementing any project can be done very quickly using UiPath. Also, the robot capacity is phenomenal. They work as long and as much as you need them to and provide optimal performance.

Building automation with UiPath is easy and takes a small amount of time. It's really intuitive and doesn't require advanced development or any technical skills. It's easy for anyone to pick up and understand. Any lower-skill employee or developer can learn to use it quickly.

We would usually do a pilot project with a company and, afterward, transfer all the knowledge and capabilities to them so that they were able to develop things themselves. Especially with the UiPath Academy, which provides online courses, and the UiPath forums, everyone could learn how to use it. My clients had no problem picking it up after our first pilot project. The advanced developer courses help a new developer quickly learn how to use it.

There can be technical issues, but it's rarely about a server quitting. They are more like connectivity, platform, and software version issues, but there are no issues with UiPath performance.

I would also like to see UiPath assist clients in scaling up their usage of the application because most of our clients had trouble expanding their usage into other departments. It was hard for them to calculate the exact value they were getting. Some of our clients were flying blind.

Some of our clients hadn't really seen enormous impact from implementing and using automation yet. They had just started, and they saw the value in it, but it was hard for them to expand or add more value to automations with UiPath.

I worked with UiPath from 2019 to 2022.

It can take their technical support some time to respond. And sometimes, the assigned staff doesn't have the right knowledge, but that doesn't happen often.

Neutral

The initial setup is straightforward. Our clients did ask for tips and tricks, but they didn't need a full consultation. They managed it themselves. It's really intuitive.

UiPath pricing is high and sometimes it's quite complicated as well, because there are loads of components and loads of product portfolios. It works, but it could be better. The pricing could be more attractive.

UiPath definitely speeds up digital transformation but whether it reduces the costs of doing so depends on a number of factors.

Over the years, UiPath has done a pretty good job of continuously improving its product by adding robot capacities and changing versions. In terms of features, they have everything covered, with AI features, data mining, process mining, and all that was done quite ahead of everybody else.

I would say that UiPath, as a company, was better in the past. Nowadays, I have less confidence in the company's situation, not that I don't think it's stable. And their ability to improve is a 10 out of 10.

My advice is to study your use cases and go to the UiPath Academy. You'll find everything you're looking for and there is a big community. UiPath is easy to use, but you have to understand your work processes thoroughly and not just depend on the application to help you.

Our primary use case is for RPA. We use it for checking invoices and sending out electronic letters. It is also going to check the absence entered by people when they are sick and see if those fill-outs are correct.

UiPath enables us to implement end-to-end automation. It is very important. It makes us more efficient. It does not require that much labor.

We find UiPath quite good in terms of ease of building automations. It does not require an enormous amount of knowledge. It is quite easy to use, but we need to do some scripting and programming in addition to the software.

We use UiPath's AI functionality in our automation program. It is necessary to interpret PDFs. We only use it in one process so far. It has only been six months, so it hasn't enabled us to automate more processes overall.

UiPath speeds up digital transformation and reduces the cost of digital transformation. This digital transformation does not require expensive or complex application upgrades or IT application support.

UiPath has reduced human error. In the use case for checking the invoices, it helps us to handle an invoice more correctly and send the invoice to the correct person internally so that it does not go in a loop somewhere.

UiPath has freed up employee time. By the end of this year, it would have saved us two whole man-years.

UiPath has saved us costs. In the six months of running it, it has saved us something like one and a half million.

The software does what it is supposed to do. I do not have any specific features that are valuable. We mainly use it for automation. We use the standard application screens. It meets our requirements.

We would like to use several modules of UiPath, but they are very costly. All the additional features that we need are there, but they are in the modules that we have not bought.

Its stability could have been better. 

It was installed around September of last year.

The stability could have been better. We started out with one developer license and then we had another developer license. When both developers are working in the cloud platform, it shuts down. I am not sure if it is solved yet.

I do not know about the scalability yet. I hope it is scalable.

We have not used their technical support. We used the UiPath community for some issues. We were trying to learn how to program, and we were stuck and trying to figure out how to do certain things. We posted a couple of questions to the community. There are always people there who are willing to help and come up with good ideas to solve the problems that you have been stuck with.

We did not use any solution previously.

It is in the cloud. Our cloud provider is Digital Workforce.

The deployment took four months. It was straightforward. There were no issues. The integration between the cloud platform and our internal networks with the firewalls was really smooth.

It does not require any maintenance from our side.

It was Digital Workforce that showed us that this is how we would want to do it. We based everything on their strategy.

With the rate at which we are going with automations, it should take us a year and a half or two years.

UiPath has several modules that we would like to use. They will enhance our installation, but they are very costly. 

We are quite happy with the solution as it is. If I were to go for UiPath again, I would not choose Digital Workforce as a supplier.

I do not have any experience with any other solution, but we have had some glitches, so I would rate UiPath an eight out of ten.

We have very restricted usage, primarily around integration situations where we don't have any APIs. We primarily want to do just unattended automation. We discourage attended automation at this time. We have ten to twenty processes happening right now.

The improvements we've seen are primarily around the time and cost savings that surround someone sitting and manually syncing data between SaaS platforms. Although we use the latest and greatest SaaS platforms, they still don't have to interact with each other. There are no APIs in most cases. In those situations, rather than having someone manually sit and do it or have the product vendor customize it, we use UiPath.

For example, a couple of automations save us at least a year's worth of manual effort. Day in and day out, there is a SaaS platform that creates new data, and that needs to go through the different SaaS platforms. And that's the major statement we have. Then there are a few legacy applications we have that are near end of life. We don't intend to bring new APIs to them. Instead, we use UiPath.

I personally use the Academy often, and I have encouraged a couple of .NET developers within the organization to take up the certification. We have system integrators and local offshore vendors. They don't have certification right now. However, I am encouraging them to get certified. They're using UiPath Academy.

For me, the biggest win for the Academy was around the infrastructure and the sales switch around it. In my role, I'm required to go and talk to business functions and technology leaders. I have to tell them what the product can do, how it is deployed, etc., at the level of ownership. Plus, thought leadership needs to come from me, and those academic courses help me a lot.

The user community is definitely robust. I see lots of contributions, and people are willing to come and respond to any posted queries. 

The key reason we are not able to adopt it fully compared to other customers is the security model. Usually, what happens is whenever we talk to a business stakeholder, the first concern is data security. The moment that you talk about a bot in an unattended fashion going and reading the data source, concerns arise since there's not much control at a certain point.

Security remains a concern. We have completed all our security assessments. However, that continues to be a key question. There are use cases that are based out of Europe. If we have an instance in North America, again, the question of GDPR and all those questions arise. For example, does that mean that we have to have multiple tenants in different geographies? We are still trying to solve those kinds of questions.

There are situations in the community where, due to the fact that the product is so rapidly evolving, lots of the content out there is outdated. It leads to that lost effort when you try to do what they're saying, and it doesn't work due to it being a different version. That's probably one problem that I have noticed so far.

I've used the solution for a little over three years.

The stability of the product is very good. 

If you look at the key components and the visuals, I mean the Studio, the Bot, and the Orchestrator, the Bot and the Studio are within our environment. We haven't experienced any issues. What is left is the Orchestrator, and we haven't seen any outages so far.

I don't have any concerns with scaling.

I haven't created too many support requests. That said, the most recent one did not go well. The engineer had some trouble understanding, and the issue is still ongoing.

It wouldn't be fair for me to judge their support just based on those one or two tickets I worked on. I'm sure they have a good team. It was just that one ticket did not work out.

This was our first RPA tool. 

I was involved in the development and deployment. 

The virtual machine setup and the Robot and Orchestrator connection definitely were a little challenging. However, in the current version of the application, Orchestrator, it's far more seamless. Three years ago, it definitely was not that straightforward. Everything has gotten easier. 

The first automation took between three to six months, from initial procurement and development to deployment.

I did the deployment myself. 

In terms of ROI, we are getting there. It's not like as good as I anticipated. That said, we are getting there.

The pricing is fairly decent. It was not crazy expensive. Their cloud deployment gives you that sweet spot in pricing. You don't have to spend $20,000 for the Orchestrator, for example.

We assessed all the market leaders and did a couple of proofs of concept. It turned out that UiPath checked all the boxes from a capability standpoint and user-friendly developer experience, plus the deployment experience. UiPath was a clear leader.

We do not use UiPath AI functionality in our automation program. At this time, it is limited to OCR capabilities.

We currently are unable to automate more complex or involved processes. It is still in the conceptualization phase. We haven't put it into production yet. However, we are exploring their invoice management capabilities and more.

We have yet to develop some sort of social responsibility initiative using UiPath. However, we might in the future. 

I would invite potential users to look at the library of activities that are there. Make sure that the kind of use cases that they're looking at are present, and the level of security that they are looking for in terms of data. If you have less intensive security challenges, it's a no-brainer to use UiPath in the cloud. However, it might get a little tricky if it turns out to be healthcare or anything of that sort. You'll have to work with your data protection team.

I'd rate the solution a nine out of ten.