UiPath Reviews

The primary use case for UiPath is to automate tedious tasks in my organization and previous organizations. It's very friendly, offering free licensing, which makes it easy for people to learn and work with it. The ability to automate repetitive activities that take a lot of time is a significant advantage.

UiPath has enabled tasks to be done quickly and on schedule without human errors. It allows repetitive processes to be performed multiple times without issues, freeing human resources from tedious daily activities.

The user interface of UiPath is very easy to understand, and one does not need a technical background to learn it. The community is supportive, providing alternative solutions and quick responses. 

UiPath's flexibility allows for significant automation, reducing manual errors significantly. The ability to have an orchestrator to manage processes efficiently is another valuable feature.

There is a need for more videos and examples on upcoming enhancements and changes. If they can improve the OCR engine and provide more detailed documentation and multiple examples, it would be helpful for adapting to new updates.

I have been using UiPath for almost nine years.

Stability-wise, the tool is good, however, each upgrade requires a lot of preparation, as it involves changing infrastructure and testing new capabilities.

There are no scalability issues mentioned in the transcript.

Technical support is rated seven on a scale from one to ten due to long communication cycles before getting hands-on help. However, they usually provide solutions and alternative methods that are helpful.

Neutral

I previously used other RPA tools, including Blue Prism and Automation Anywhere. UiPath offers free licensing for learning, which is an advantage over other tools.

The initial setup is straightforward. On-premises deployment involves getting the development package and deploying it. Hybrid models require coordination with others but are not complex.

While specific numbers are not provided, UiPath certainly performs well in automating repetitive tasks, which likely contributes to a positive ROI.

Based on past experience, UiPath's pricing is moderate when compared to other tools. I rate it at seven out of ten in terms of cost.

Alternate solutions evaluated include Blue Prism and Automation Anywhere. Each has different strengths, but UiPath is preferred for its user-friendly interface and community support.

I would rate UiPath seven out of ten based on my current experience. For people from both technical and non-technical backgrounds, it's a great tool due to its easy learning curve. The licensing makes it accessible for learning and development.

We use UiPath for claims processing, enrollment, and interpreting what's on documents, and then we use the data that's in them for different purposes. I'm sure there are many other use cases. We're still brainstorming and giving our leaders some ideas. Frontline employees also have process improvement ideas.

UiPath has improved efficiency, turnaround time, and accuracy while eliminating repetitive tasks. 

With generative AI, we can take on even more complex tasks. We've seen a return in claims and enrollment, which has freed up time and resources. There are lots of other possibilities. Our frontline people have seen how it can supplement and focus on more important tasks, and business leaders like seeing the resources freed for various reasons. The growth potential is immense, and we're only in the early stages. 

UiPath is a low-code solution that allows us to build automations fairly quickly and see the results promptly.

Overall, UiPath is relatively straightforward, but there are opportunities to simplify activities. Sometimes, I've hit roadblocks while developing RPA jobs and found it difficult to find the answer. I can usually resolve a problem through a support ticket or an online search. 

We have used UiPath for about a year and a half.

I rate UiPath support eight out of 10. UiPath support is good, but sometimes they give generic users. Maybe I need to take the initiative and give a little more information and context

Positive

There has been a return on investment, though I'm unsure of the specific amount. We've already saved time and thousands of dollars.

I rate UiPath eight out of 10.

Our primary use case involves automating low-hanging fruit processes such as daily reporting, order entry, and AP invoice processing. We are a printing company with 33,000 to 34,000 transactions a year, and 70% of these are repeat orders that we aim to automate.

Implementing UiPath has increased speed and accuracy, freeing up staff to focus on higher-level tasks requiring creativity and attention. It has resolved the issue of order entry delays, reducing a process that could take two to four days to just five minutes.

The document understanding feature has been particularly valuable as it recognizes and extracts data from invoices and purchase orders, greatly saving time.

The fast growth of UiPath can be difficult to keep up with, so more informative sessions or webinars showcasing potential returns on investment for specific industries would be beneficial.

We started using UiPath in 2018.

In general, the stability of the solution has been positive.

UiPath has been able to keep up as our environment grows.

The customer service and support have been great, consistently providing answers or guidance.

Positive

We did not use a different solution previously. We chose UiPath for its user-friendly Studio and comprehensive resources.

We initially partnered with a company that was not the best fit, and have since switched to a more suitable partner, greatly improving our experience.

We have yet to realize a significant return on investment due to initial partnership challenges. However, we are now on track with a new partner.

Pricing is fair. That said, it requires justification for returns due to a tight budget.

I would rate UiPath a ten out of ten.

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.