UiPath Platform Reviews

We use UiPath for developing and implementing technical applications that provide data solutions.

Building automation with UiPath is straightforward. The API tool enables us to automate tasks such as receiving orders, booking travel, and reading emails with ease.

UiPath enables us to implement end-to-end automation, which is important for me as I frequently travel for business. The solution aids in conducting interviews with customers, handling documentation, and facilitating development.

UiPath saves us around 100 hours per week through automation.

I have completed the UiPath Academy introduction courses. In Brazil, it is the sole method available for us to learn about UiPath.

UiPath saves us approximately $200 per week towards the expenses of digital transformation.

UiPath helps to reduce the number of human errors.

UiPath helps our organization save costs by accelerating our tasks through automation.

UiPath's most valuable feature is Orchestrator.

UiPath's price has room for improvement.

I have been using UiPath for five years.

UiPath is expensive. On a scale of one to ten, with ten being the most expensive, I would rate the price an eight out of ten.

I would rate UiPath a seven out of ten, mainly because of its high cost.

I use UiPath for invoice processing. We download all the invoices from our application and then send them individually to the respective customers via email. This involves email automation and automation of the user interface.

Building automation with UiPath is easy. When compared to other automation tools, UiPath offers a more user-friendly development platform.

It enables us to implement end-to-end automation, from the basic extraction of data to the complete uploading of data to the respective applications.

UiPath's User Community is excellent. Whenever I encounter challenges or need information about new developments, version changes, or anything related to UiPath, the community is always there to help. Therefore, I find the community extremely valuable.

UiPath can be a useful tool for anyone. It doesn't require a separate environment or the need for a developer. It is beneficial for anyone dealing with any system. Therefore, I believe it can serve as a regular daily process tool, enabling users to automate various tasks effectively. There are numerous possibilities and applications with UiPath.

In my early days of entering this field of development, I completed the UiPath Academy courses to gain a comprehensive understanding of the interface, the approach we should take, and how to utilize the portal functionalities that UiPath offers.

UiPath has been instrumental in reducing human errors by 99 percent in applications that are maintained correctly, particularly in activities such as typing. There are certain tasks where humans are prone to making mistakes while working with applications, but UiPath ensures that such errors are eliminated. Initially, I had some doubts about UiPath's ability to extract data from PDF files, as the UiPath OCR engine seemed to have limitations. Consequently, we started relying on ABBYY FineReader for this task. However, we are now exploring UiPath's UI for document understanding. As a company, we have already developed around 200 to 300 templates using ABBYY FineReader, making it challenging for us to transition entirely to UiPath document understanding at present. Nevertheless, we are considering the shift because the early versions of UiPath were not very efficient, and we couldn't fully rely on it for data extraction. However, with the recent integration of Google Vision, UiPath has significantly improved and is now providing better results in terms of OCR technology.

The user interface is the most valuable feature of the studio version. It allows us to develop all activities and create custom activities as needed. Additionally, it seamlessly integrates with the latest technologies, such as AI, making it very helpful, even for integrating ABBYY FineReader. Users can extract data from the time scripts, which is also a project involving data extraction from all PDF files.

The UiPath Community does not provide version control for the community edition. Let's say I'm currently using a specific version, and then it automatically upgrades the community version to the latest version without the user having the option to decide whether to update or not. Consequently, we cannot use the older versions in the UiPath community edition.

I encountered some issues with my local machine. I created one of the bots using a different version from the community variation, there were problems with compatibility between different versions in UiPath. While those issues used to exist, currently, it has been a long time since I last modified any of the workflows and migrated between servers and my local machine. I'm not entirely certain at the moment, but previously, there were instances where a particular activity in one version would not work in another version and would result in failure. Additionally, sometimes the select task would not identify the select areas in the actual application, even though it worked on the validators. These scenarios are rare but they do occur.

I have been using UiPath for almost two years.

I would rate the stability of UiPath ten out of ten.

I would rate the scalability of UiPath eight out of ten.

The initial setup is straightforward.

The licensing fee is moderate and is based on the volume of tasks for which we use UiPath. The cost is satisfactory.

I would rate UiPath eight out of ten.

Currently, we are handling approximately 20,000 units of data on a daily basis. Our focus is on efficiently processing this data and integrating it into the scaled servers. We utilize the scale servers for data connectivity, verification, and storage purposes.

We are currently not using the AI functionality, but our company is anticipating a new project. The assignment of this project will happen very soon, and the company is considering the use of AI for it. However, this decision will ultimately depend on the user and the environment. If we determine that using AI functionality is necessary, we will integrate it into the project. At present, we have not encountered any users who explicitly require AI in their business logic. Therefore, we are not utilizing AI at the moment. Nevertheless, if any future clients request it, we will be prepared to integrate AI functionality accordingly.

Our organization has started using automation with UiPath. Before implementing UiPath, everything was done manually.

If the initial development is done correctly, then the maintenance would actually be significantly reduced. As a developer, we need to ensure that the code is always reviewed by developers, and they should always be available for this purpose. If the initial development is not carried out correctly according to the requirements, then imagine the consequences in the future. The development might need to be revisited for up to 15 years, or at least five years. If it is not done that way, the maintenance cost would be very high because the business processes keep changing. Therefore, to keep the system functioning well and the applications up-to-date, as they are not static, we need to continuously maintain the code. For instance, in the past six months, we've had to make two changes to the application we are working on. Many alterations occurred, such as UI element changes, shifting locations, and complete interface and navigation changes. Hence, it's essential for developers to always keep the code protected and up-to-date.

I recommend conducting a proof of concept using UiPath to ensure that the budget and return on investment are sufficient to implement the solution within an organization.

I have used UiPath for a city utility. The main purpose is if they want to dig in a particular location, they need to know how many pipelines are underneath the road, what the situation is regarding high-tension wires, gas pipelines, et cetera. For that, we needed to go to about 18 websites and scrape the maps from them into a local repository. We use UiPath to save that data from all the websites.

From there, there is an AI/ML solution that identifies the danger signals and notations on the map. It summarizes them and sends them to a mobile application used by a person who is at that location. That person can determine whether they are able to dig in that particular location or not.

UiPath reduces human error by automating a lot of manual steps. 

It also helps free up employee time. The amount of time depends on the use case. For the use case I described above, for the utility, the whole process of preparing one package would take one person two and a half hours. Automating it using UiPath and AI reduced it to two and a half minutes.

In terms of costs, for that use case, it has saved that company 30 to 40 percent.

Scraping with UiPath is easy, as is integration with some services. It's also easy to deploy solutions. 

Building automation takes place in a normal programming environment like Visual Studio. It's the same environment developers use. If you know development, building automation in UiPath is easy. Visually, it's all interactive and easy to work on.

The platform also has features for logging and monitoring things and communicating when there are errors.

The UiPath user community is a very good ecosystem with information about a lot of new features like AI, chat integration, and WhatsApp integration.

For training purposes and certification, we use the UiPath Academy. It's a very good resource and you get very good support from the community.

We also use the solution's AI functionality but so far only on low- to medium-complexity processes.

I would like to see them transition to the cloud and provide services there. That would be an improvement.

Also, it needs more integration with external services, and I would like it to have generative AI and more artificial intelligence features.

I have been using UiPath for about one and a half years.

The stability is good. I am satisfied with it.

The scalability is also good.

UiPath's technical support is good.

Positive

I used Automation Anywhere. I switched because our clients switched since UiPath is cheaper.

There is definitely ROI from using UiPath. Based on the fees and the load of the input, ROI will be calculated and used to decide whether the use case is worthwhile or not. It will be decided in the analysis and discovery phases. If ROI is feasible, only then will development take place.

With UiPath, there is an additional cost for Document Understanding. If the use case demands it, that feature should be used.

Even though our clients may have an Automation Anywhere ecosystem, they choose UiPath due to budget and cost. Apart from cost, both platforms offer almost all the features. However, from a technical perspective, Automation Anywhere has more utilities and components for building bots.

If it weren't for the cost, I would personally choose Automation Anywhere, on the technical side, because it has huge utilities and components for building bots. The move to UiPath is driven by budgets and costs.

As for end-to-end processing, when you are trying to come up with use cases for RPA, you will probably look at existing legacy applications that are not extendable. They won't have any more new releases but we still need to extract value from them. Use cases include reducing the processing steps and manual steps done, day-to-day, by people. End-to-end automation will help to stitch all the gaps and reduce the processing time.

UiPath is not cloud-based yet, so most of the work is done on-premises.

In terms of maintenance, one person on our support team monitors all the bots and attends to any problems.

I would recommend UiPath for small and medium-sized automation. If a company doesn't have a large budget, UiPath is the solution.

We primarily use UiPath for science-related automations.

The biggest benefit we get from UiPath is saving time. We work with small and medium-sized businesses that need to perform multiple mundane, repetitive tasks. UiPath reduces the time we spend on these tasks by about 60 to 70 percent. By automating low-level jobs, employees can focus on high-priority tasks. Automation has sped up our invoicing because we can process invoices 24/7. We saved more than $200,000 using UiPath.

UiPath helped us reduce our on-prem footprint. Using bots eliminates human error from most jobs if we develop the correct logic and business exceptions, but we still need humans working upstream. 

Building automations is quite straightforward. They offer free courses for developers, and we take advantage of those. The UiPath community has also had a tremendous impact on our operations.

The artificial intelligence and machine learning features are good, but there is some room for improvement. 

I have used UiPath for more than five years.

UiPath is stable. 

UiPath is scalable. 

I rate UiPath support an eight out of ten.

Positive

I have used several RPA tools, including Blue Prism, Automation Anywhere, and Microsoft Power Automate. UiPath is easier to learn and more user-friendly than other solutions. There are also lots of open-source resources you can use. Power Automate was included with our Office 365 license, so we use it for some things. However, it isn't our primary RPA solution. 

Deploying UiPath is straightforward and only takes a couple of minutes. One person is enough to install it. 

UiPath is quite expensive compared to Power Automate. That's the main difference, and we have to purchase a new license for every feature. 

I rate UiPath a seven out of ten. I would recommend it to others, but I can't give it a higher score because I'm not happy with the licensing model. That's what bothers me the most about UiPath. 

We used this solution to automate monitoring, implement robots, and monitor the robots. We use it for network monitoring, ticketing systems, and remediation activities. This is a SaaS solution. 

This solution is mostly used by network engineers in managed services. The engineers look after telecom networks, and they are the end users. For automation, a sizable team of developers, specialized automation developers, and solution architects used the solution. There were about 40 RPA developers and 10 solution architects.

We plan to automate some of the business processes regarding financial reporting.

We used this solution in the automation of a legacy Jira application that was used for CR management. We use the change request template, and we're able to collect data from various systems through APIs and submitting requests.

Since we started using this solution, our team has had more time to work on other tasks.

The solution has reduced human error by processing the data directly from the source and into the destination application without human intervention.

Our internal clients are glad that KPIs are increasing.

A lot of my colleagues have used the UiPath Academy course. There were also colleagues who used the course and weren't involved in the day-to-day automation process.

It really helps employees be aware of how the tool works, how they can better describe processes, and with what level of detail they need us to describe processes so we can automate their work.

One of the biggest improvements was that some of our colleagues who weren't technical and weren't working in the automation domain started to build their own robots to automate some parts of their work without help from our automation team.

UiPath's community is used by quite a lot of our developers to solve some issues and get resolutions faster. The community is quite big compared to other communities. We get more resources, and it's more active than other communities.

We use Attended Automation for some of the monitoring, like creating outlets based on network events. Attended Automation helped scale RPA benefits in our organization by automating department or role-specific processes that require human-robot collaboration. 

With the involvement of a lot of colleagues from different departments, mostly using Attended Automation, we have increased the awareness of automation and robot automation in the company.

I like the interface. It's simple to interact with. We can replicate and multiply the robots when we need to change something.

It's easy to build automations using UiPath. Colleagues who aren't very technical can develop their own automations.

The developer studio could be improved. There have been glitches, but it improved from year to year.

I have used this solution for three years.

We had some issues with stability because of some unattended robots. During execution, there were stability issues.

We didn't have many issues with scalability.

We have a good relationship with UiPath. We are in Romania, and they have an office here.

I would rate support an eight out of ten. 

Positive

The setup was easy. Within one month, we migrated from Blue Prism to UiPath and started implementing some robots.

We had a small POC to discover how it would fit in our infrastructure and how feasible it would be to have all the functionality from our previous tools. We rolled it out for a small department and migrated all automation to UiPath. Then, we gradually rolled it out to other areas.

Overall, the solution saved costs. Last year, it saved us between 8% and 12% of costs.

We increased the speed of delivery of automation, so it's a good return on investment.

We also evaluated Blue Prism. Due to its subscription pattern, it wasn't flexible enough for everybody to understand it and work with the tools. Licensing was a bottleneck.

Blue Prism didn't reduce the cost of automation, but it increased the number of automations we did in the same period by 30%.

I would rate this solution seven out of ten. 

My advice is that depending on the business domain where you want to implement the solution, it's more feasible for document processing and ingesting data in applications, not for executing commands in various application servers or infrastructure. 

Stability is an issue. In large deployments where you have a lot of robots, these issues can cause a lot of intermittent problems with the operation of the robots.

We use this solution for voice processing, user onboarding, offboarding, marketing, email consolidation, text form generation, text form ingestion, AP, and AR.

We are using UiPath's AI functionality although we have not been able to do much complex configuration. Theoretically, it works but as soon as we start adding different invoices, it's a very cumbersome, long, and human-centric process. Our company is planning to scale our automation efforts.

This solution is easy to use for the end user. The Academy courses make this possible as well as the community forums. I am a senior manager and my role is building the center of excellence. I learned how to write code on UiPath using the Academy and learned from my peers in community forums. 

This has been the biggest benefit. With other vendors, you had to pay thousands of dollars to learn how to use their solutions. With UiPath, you can learn on your own and expand your knowledge.

The task capture and task binding features have been most valuable. These features make it easier for a team who are not that familiar with RPA to successfully use UiPath. They generate the PDD the way it's supposed to be and capture the right screenshot.

The stability of the bots could be improved. The bots could be expanded to have more objects already prebuilt. It would be useful if it was clear to the end user that there are objects already built. It should be easily available or there should be a very simple search for objects. Many users don't know that Marketplace exists or that it gives you free bots. 

I have been using this solution for eight years. 

This is a stable solution and we have not experienced any crashes. The challenge we have experienced is when developers do not document requirements correctly but we have had no issues with the software itself. 

This is a scalable solution. 

Customer support is provided mostly by a consulting firm. We usually raise a ticket and get an answer. We would like the technical support to be sharper and faster rather than going through the consulting firm as this can take more than a week. 

I would rate the support for this solution a six or seven out of ten. This score could be improved if we had a single point of contact. 

Neutral

Before UiPath, we used Blue Prism. We switched due to the ease of use of UiPath as I could learn how to use it myself and teach the team. This training is free and also offers free software. 

If you are new to UiPath, the initial setup is not that straightforward. It is easier now that I have been working with the solution for a few years. The most challenging part of the setup is getting information on how UiPath connects with other systems. Only 1% of the community actually knows this. 

For the setup, our infrastructure team followed the instructions sent by UiPath. At that time, there was no cloud functionality. UiPath could offer better communication around the overall implementation and where data is stored.  The instructions are very easy to follow but the security approvals cause a lot of blockers. 

We have experienced ROI in two ways. Within the first three to six months, whatever we invested came back to us in terms of time-saving and money-saving. We have also seen an increase in client satisfaction in the sense that we can look up client information using attended bots. 

This tool makes it easy to build a team that can manage it because of the availability of the academy and certifications for upskilling. The courses are set up to ensure the user fully understands what the certification is about before they are awarded it. 

It's easy to use and the dashboards give me easy access to insights. This is why I always recommend UiPath to others. Some organizations can waste millions of dollars trying to set up other solutions. 

I would rate UiPath a seven out of ten.

Our company uses the solution to automate processing of intended and unintended regulatory transactions in the banking industry. 

We are just starting to use the AI function of the solution. 

The solution has been a tremendous efficiency game for our company. 

We have delivered hundreds of thousands of hours of efficiency over 300 robotic process automations. 

The speed to market is amazing because an automation can go from the initial planning conversation to production in weeks.

Most of our automations have been without a user interface and we need the ability to interact with users directly. That should be coming in the next release for us. 

I have been using the solution for four years. 

The solution has been very stable across hundreds of automations. 

We scaled from dozens to hundreds of automations and are very satisfied with the solution's scalability. 

Technical support has been great and I rate it an eight out of ten.

The solution's community forums are great and help solve many issues. We can easily reference documentation for similar issues and that provides a lot of assistance. 

Positive

We previously used Pega but switched to the solution for its speed-to-market benefit. 

Our strategy is to use automation for maintainable, high-quality, repeatable processes while delivering excellent speed. 

I was not involved in the initial setup within our environment, but have managed the deployment of several hundred automations and the process is straightforward. 

It is very easy to use our CICD pipeline to deploy and monitor solutions via the orchestrator tool. 

Our ROI is saving hundreds of thousands of hours in time by automating processes that used to be managed by staff. 

Academy courses have been very helpful in preparing our developers for certifications.

I rate the solution a nine 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.