UiPath Platform Reviews

We use it with ServiceNow for maintaining tickets. Our task works to automate some scenarios such as software updates. In that scenario, there are some repeated steps. We use UiPath with Python scripting to automate those repetitive steps.

One of our use cases is for our insurance team where we have built a prototype which has helped the insurance team cut pricing. That is one of the automations that has made a difference.

Also, the fact that this is a SaaS solution means we are able to innovate much faster when it comes to automation. We have been able to complete use cases in as little as one month. There can be problems with the on-premises version because there are certain restrictions for accessing that database. But because this is on the cloud, we can access the data from anywhere in the world. That is very beneficial.

UiPath has also helped to reduce the amount of maintenance work related to our automation operations. It has a feature to keep the different automatic tasks monitored. That monitoring helps us if there's any problem in an automation. We get notification that there is a problem. If we don't know about those problems then, after some time, maintenance on them will be harder. It does help us to maintain things.

Before, we were using the on-premises service for our automation activity. By using UiPath Automation Cloud, we don't need to go anywhere. There is a single tool where we can keep track of the maintenance. Doing so with the on-prem solution was much more time consuming and slow. With UiPath it's so much faster so it helps us cut costs.

And in terms of overall cost savings, before we implemented one of our automations there were around 100 people taking care of the task. Using UiPath, we have automated that task and we have saved the fees of 100 people.

The speed is much better because we're doing it on the cloud. With other solutions there were network problems, but in UiPath I have found that network connectivity is much stronger when transferring data from the back end to the front end. It is much faster.

The Portal for enabling business users to trigger jobs with business input and for monitoring those jobs is great.

There is also the granular, role-based access control and management which is very important in our organization because we have different roles. Our manager has a much higher role, so that if there are some changes in an automated step, there are permissions from that higher authority. Otherwise, low-level employees could make changes without informing the higher levels and there could be a lot of conflicts. This way, we don't allow the lower-level employee to make any changes without proper permission from the higher authority.

The solution's single sign-on is also important because without it, a user ID and password could be compromised by a third-party or hacker. Single sign-on gives us another level of security when logging in to UiPath. It's very important and a good security feature.

UiPath also continues to add services to the Portal. There are proper updates that come out monthly or quarterly. They update different features or any problems with features, so the updates are very useful for us. It's very important that all the services are managed from the same place because no matter where a team is, if there is a glitch and we raise a question with customer support, and they do some fixing, that fix is available for all the users who are using UiPath. It comes from the centralized location, which is a very good thing. It is available for all our users around the world.

They should include new machine learning and AI algorithms for better forecasting and analytics.

I've been using UiPath Automation Cloud for two years.

It is very stable. In most software, we find that when we increase the data size, there is some kind of decrease in network connectivity, a delay or lag. But UiPath is very stable because they release updates very frequently.

We use it for day-to-day purposes. The tools are working on different jobs, daily. We have plans to automate more scenarios and we are working on a PoC for them. If they go well they will be implemented in UiPath as well.

Their support is very proactive. When we reach out to them, they fix our problem within a day. We can also use the Portal to have a chat about any issues that come up. Customer support is good and the community support is also great.

The fact that we don't have to worry about future installations and upgrades of Orchestrator, was important in our decision to go with UiPath, because those things are already built in. We don't need to worry about the infrastructure part. It is maintained by the UiPath team. They also have better community support to help us if we face any problems. That is one of the great things about UiPath.

The initial setup was very easy. The vendor was very active and the community is very active so there was no delay in communication. It was very straightforward.

We started UiPath as a desktop application and then we slowly moved to the cloud.

And in terms of the setup costs of our automation operations, UiPath doesn't have a lot of dependencies, so it is quick. We don't need to contact another party to maintain things because the UiPath community helps us with every aspect. It works. 

The pricing is good compared to other software. Based on the features that UiPath is providing, and the community support, the price is reasonable.

I have used different tools like Blue Prism and Automation Anywhere. When comparing all three, when it comes to cost, UiPath is great. It is also easy to use. Anyone can learn to use it within a couple of weeks. It is very useful and user-friendly.

The user interface and the usability of the other solutions is not as user-friendly. We also found some glitches in those solutions, things like network delays.

We haven't found any problems with UiPath. It is working great. It's a great tool. I would suggest that everyone go with a UiPath because it has helped us a lot.

We use UiPath Studio, Orchestrator and Robots, all unattended currently. Our primary use case is one-off for mediation projects because we're trying to set up our infrastructure. Once the infrastructure is set up, we plan on creating a federated model throughout our entire organization.

Right now, our remediation teams do a lot of large one-time projects where they have to have policies for scaling up and scaling down the volume of full-time employees. I know we have avoided that situation in at least three cases now where they have not had to hire or remove people because they have been able to automate the remediation process.

The most valuable features for me in Studio can be anything that helps me test or debug. It saves me a lot of time and it saves our QA team a lot of time setting up separate environments, test data, and things like that.

The most valuable thing in Orchestrator is just how easy it is and the fact that it's cloud-based. It is also useful in that it allows non-technical users to get information about their projects. For example, they can find out if independent components are up and functioning; if something is down they can find out what went wrong.

In the next release of the solution, my biggest hope would be getting more accessibility to test data processing information. I was told that this feature was coming already. Being able to see what my variables and my arguments look like when things are being passed and making the processes very clear to my customers when we are doing test cases for UAT (User Acceptance Testing). That would be invaluable. It would help the customer to see and understand the data flow more easily without having to go through training or being very tech-savvy.

I think Studio has a little more room for improvement and could use a few more features. They just announced Studio X and Studio 2 which actually addressed many of the issues I hope to see resolved, but that is assuming that they come through in development and do what they say they are going to do.

On a scale from one to five, where one is not stable and five is very stable, I would rate the stability of the UiPath platform as a four-and-a-half. I've only seen one or two buggy behaviors, so I think that qualifies as extremely stable.

In our organization, there are five full-time people involved in the automation program. We can drag people in from different departments in the business on a case-by-case basis when necessary for resolving issues with automating.

Before we started, all of us were involved in using UiPath Academy RPA training and learning through it. On a scale from one to five where one is the least beneficial and five is the most, the Academy is something I would give a three. I say that because I don't think they went into enough detail. I understand that they didn't because they are trying to save time for non-technical people, but I love knowing everything and I would love to see more detail in their presentations or have options to do so.

Customer support overall is very responsive and they say a lot of helpful things, but I'm often able to find the same information and answers on the forums. It would be nice at times to be able to talk to someone from support over the phone. I can describe my problems without having to send dozens of emails back and forth in order to get an answer. It just isn't terribly efficient.

The decision to automate and the product selection for the solution were completed before I was brought on as part of the team. I was actually brought on as an expert from another company in order to help them stabilize their deployment. The product vendors which were on the short-list actually include some vendors which the company has licenses for in addition to UiPath, like Blue Prism. They are exploring multiple options because we are a global entity. They want to offer the option to entities to choose whatever partner they prefer to go with.

The approach to the initial setup which was selected was a complicated process. I don't know much more than it took a long time, it wasn't very successful and that's why they brought me on.

They did the entire implementation in-house.

We have seen some return on investment to a certain extent, but a lot of it's coming from one-time processes and not from recurring processes. In other words, the ROI is already there, but it is from one-time processes we've deployed. These are processes that we would run a bunch of items through one time and the circumstances are not repeatable the next year or even the next week.

I'm not sure about the exact numbers, but I know that the cost of our department has been saved roughly four times over. Again, a lot of those savings are from one-time events that won't be recurring in the following year so they can't really be seen as predicting the future results.

The solution has helped to eliminate human errors in some cases and that also has value. In addition, there is the benefit of saving the employees time. Right now I believe that we have approximated that we saved somewhere between 40,000 and 45,000 human hours. That resource can be re-allocated.

Part of our deployment is in a virtual environment and part of it is not. The implementation is actually still in progress. We are in the phase of setting up our infrastructure and trying to automate some POCs (Proof of Concepts) and some early successes to show the financial benefits of RPA to the C-suite (C-level executives such as the CEO and CFO).

On a scale from one to five where one is very difficult and five is very easy, I would rate the ease of use of the platform as a four. I think the product is fairly intuitive. Because I come from a tech background though, I feel like it is going to be a little easier for me to understand than some other people who don't have that same background. The only reason I don't give it a five is because the integration between Orchestrator, Robots, and Studio does require a little bit of intimate knowledge to be able to connect them all and make sure that they stay connected.

We have not used attended robots yet, so I'm not sure how cost-effective they are because we don't have any data on that. We use unattended bots and they seem to be effective solutions, but I don't know what they pay for them.

On a scale from one to ten where one is the worst and ten is the best, I would rate this product as a nine. The only reason I'm not going to give it a ten is that I have struggled with certain errors and stability issues. Whether that is our fault or a general bug in the actual software is yet to be seen. I have a few open tickets, but I've really liked this software overall.

Advice that I would give to a colleague at another company researching this or similar solutions would be that they look at their organization and see if they are really ready for deploying RPA solutions. A lot of RPA solutions are sold with the promise that anyone can build solutions with the products and the bots are going to deploy quickly. I don't think quick deployment is deceiving, but I do think that trying to implement a solution that does move so quickly like this into an organization that doesn't move quickly can create friction.

We are targeting utilizing Gen AI for some social media marketing. We haven't really implemented it yet.

Implementing AI and automation has streamlined our processes, allowing us to focus on more important day-to-day work instead of repetitive tasks. This has helped with customer satisfaction. 

We have been able to automate a lot of internal processes, saving significant time for our managers and increasing the accuracy of reports and monitoring. We saved about 350 hours, which corresponds to approximately $500,000 in money saved.

The most valuable features are the autopilot or copilot AI feature and Insights. We haven't used it yet. I know that understanding the document is highly powerful and really useful.

I would like improvements in UiPath Studio speed. The development environment is sometimes slow, depending on the workflows, especially with legacy workflows.

This should be the third year of working with the solution.

We utilize the cloud Orchestrator, and it has been really stable with no issues.

We started with three bots and have maintained that number, with the addition of one test bot test license. We are always using it to scale.

We access resources at UiPath to assist us, however, resources can be hard to get. Better access to resources might improve the process.

Positive

The initial setup was simple for us. I am aware it could be more challenging for on-premises deployments.

We didn't use a partner for the initial setup.

We realized a return on investment by saving about $500,000 due to automation of tasks that took longer manually.

It is probably in line with the market. I am unsure about pricing for AI units as we haven't implemented them yet.

I would rate UiPath a nine out of ten.

We're a financial institution, and we started using UiPath for small, simple processes and day-to-day tasks, such as adding and removing users and updating information, but we're also exploring opportunities to automate lending processes.

We typically evaluate a process first to see if it's appropriate for automation. Sometimes, we've identified bad processes and needed to update documentation before we can implement them.

UiPath has allowed our employees to focus more on servicing our members rather than being bogged down by mundane tasks. In the last year, we have saved about 6,500 hours for our users, equating to the time of two full-time employees.

With UiPath, we've saved costs, increased productivity, and reduced stress on our employees. It has saved our employees time. They're thinking more about their processes instead of just doing what they're told. It places more onus on employee creativity.

I primarily work with task capture, which has been valuable. We have created a template for ourselves and reused it for all these processes. Other departments also use it for their procedures, even if the process is not automated.

We struggle to demo our processes. For whatever reason, we can't get the bot to run so that someone can watch it simultaneously. We press the button, and it shows that it's done rather than showing how the bot works. 

We started using UiPath with a partner two years ago and transitioned to handling everything in-house last year.

The stability of UiPath is good. We do not encounter issues with logging in or frequent service failures.

I rate UiPath support nine out of 10. Their customer service is good. They are always willing to help us and address our concerns. 

Positive

We initially used a UiPath partner but have since moved operations in-house. Our in-house experience has been better.

We have seen a return on investment. The 6,500 hundred hours we saved using UiPath translates to a savings of about $56,000 per year.

I rate UiPath 10 out of 10.

We use UiPath Studio, specifically the enterprise version, for developing projects per organizational requirements.

UiPath makes building automation processes easy and accurate. It allows us to create a wide variety of feasible automations. Even complex processes can be tackled using UiPath's features, such as object repositories and document understanding.

UiPath offers end-to-end automation, which is crucial for our work. This allows me to handle various tasks. I can efficiently open any web application required by the organization or our clients. I can download documents from web applications and fill in the necessary details within them. I can extract important metadata from documents or web portals. I can store the extracted data in a designated data queue. I would rate the process a ten out of ten.

By automating tasks through the use of robots, we can achieve significant time and manpower savings. This, in turn, leads to reduced costs for the company. Additionally, automation improves accuracy, as robots are less prone to errors compared to humans performing repetitive tasks daily.

I use the UiPath Academy courses in my free time to get some diploma-level certifications.

UiPath reduces the cost of digital transformation.

UiPath helps reduce human error.

UiPath helps to save staff 70 percent of their time through automation. 

The community version of UiPath has a limited feature set, which can make it challenging for users to fully explore its capabilities without purchasing the enterprise version. Offering a trial period for all features could provide a more comprehensive evaluation experience for potential users.

I have been using UiPath for four years.

While UiPath has disconnected on a few rare occasions, it has generally been stable.

UiPath is scalable 80 percent of the time.

The initial deployment is moderate. 

The implementation was completed in-house.

UiPath is expensive.

I would rate UiPath nine out of ten. There are many RPA tools and UiPath is at the top of the list.

UiPath requires maintenance for any changes that are made.

I recommend reviewing the documentation and completing the UiPath Academy courses before using the solution to automate processes.

I developed several use cases using UiPath. One involved website scraping, where I extracted data like temperature, humidity, and pressure for various cities from a specific website and displayed it in an Excel sheet. This was a small project, but my main focus was a prototype for a client: digital marketing automation. Using UiPath, I created an automation to automatically post articles on different social media platforms.

UiPath has certainly improved our operational efficiency. My prototype adheres to its principles.  UiPath has a sheer number of functionalities and features in UiPath. While these are beneficial, considering operational efficiency, UiPath excels thanks to its modularity. It's comprised of distinct components like Orchestrate, robots, and studios. This breakdown allows each component to function independently, increasing work flexibility and ease of use.

I would rate the ease of building automation using UiPath an eight out of ten with ten being the easiest.

I would rate the UiPath User Community ten out of ten. It is the best community I have used.

I'm taking advantage of the UiPath Academy courses and find them helpful.

UiPath helps to speed up our digital transformation and reduce costs.

Automation through UiPath helps reduce 80 to 90 percent of human errors.

The UiPath User Community is the best feature. We can find a solution to all of our issues there.

UiPath's interface element identification is arguably more reliable than Automation Anywhere's. This is because it utilizes an element descriptor method, which essentially locates "anchors" within the target element, not just relying on its absolute position. In simpler terms, it seeks a stable reference point within the element itself, even if its overall position on the screen shifts. As a result, changes to the website's UI are less likely to break our automation, as the code doesn't depend solely on the element's position. Additionally, UiPath offers a wider range of app integrations and features compared to Automation Anywhere or Blue Prism, making it more versatile for different automation needs.

Logging is also valuable. We can see any system, business, or technical errors.

One area that could be improved is how we access the UiPath Academy courses. While it's fantastic that each course provides an assignment, it would be more convenient if we could view the solutions directly within the platform rather than downloading them each time and opening them in our individual UiPath Studio applications. Ideally, there would be an interface integrated into the course platform itself where we could access and review the solutions directly within the browser. This would save time and streamline the learning process.

In Automation Anywhere, each line of code is displayed in a list view, offering clearer visibility. In contrast, UiPath condenses everything into a boxed view or flowchart, which can become cumbersome when dealing with numerous intricate conditions. Pinpointing specific segments for modification within such a condensed format proves challenging. Therefore, UiPath's UI design could benefit from an overhaul to enhance clarity and ease of navigation, especially for managing complex workflows.

I have been using UiPath for one year.

I rate the stability of UiPath an eight out of ten.

I rate the scalability of UiPath a nine out of ten.

I find Automation Anywhere to be more user-friendly for newcomers.

While I have more experience with Automation Anywhere, and it's where I've worked more extensively, UiPath is currently the market leader in the field. This prompts me to explore what's behind its success and delve deeper into learning UiPath. There must be compelling reasons why it holds the top position.

UiPath is more expensive than Automation Anywhere.

I would rate UiPath nine out of ten.

I recommend UiPath as the leading RPA technology, considering the current market trends.

I am working with a Telecommunication company. I work on the software side and IT infrastructure side for the company. We had an EFT, and we needed to automate some functions. That is the main reason for using UiPath. We are able to do service failure handling, order handling, and other tasks. Currently, there are ten to twelve use cases related to telecommunication, but we are planning to automate most of the systems.

We have not yet used the AI functionality, but we are planning to use it in the next year.

UiPath automation has been helpful for the support team. With the error rate that we had, we could not manage the system. We could not manage the work with the people we had. We had five people on the team. By automating five or six operations, we are operating with two people. The other three people are working in other areas. We also did some automation for operations for the service provisioning team. In that team also, they had some resource issues with two to three people. They are now running operations without any issues. We have also automated use cases related to workflow for the call center back office. We have automated processes related to broadband customer changes. The savings vary from use case to use case. Overall, the support team has replaced five to six members, and the back office team now works with half the team. In some cases, we did not have human resources at all. We automated those processes, and they are functioning without human resources.

UiPath has helped to minimize our on-prem footprint.

UiPath has helped to automate repetitive tasks. Our teams were getting tired because they were doing the same thing. There are also benefits in terms of efficiency because bots can run 24/7.

UiPath has also helped with accuracy. We have 100% accuracy.

UiPath has reduced human error. We are not manually entering the values. They are coming directly from Excel. There are no misunderstanding issues. Bots only do what they are instructed or programmed to do.

UiPath has freed up 50% to 60% of the time of our staff.

Its integration is valuable, and it is very easy to use. I could do self-study and get started with the Community edition of UiPath. I have tried Blue Prism and Automation Anywhere. When I compare UiPath with these solutions, UiPath is easier to use. There is also a lot of community support. I have taken a lot of support from the UiPath Community. UiPath has a very good community, so I feel it is very easy.

There were one or two bugs, but they have already been fixed. At the functional level, UiPath is almost perfect. The only area for improvement would be the ability to use code. In Blue Prism and other tools, we can write the code, whereas UiPath is drag-and-drop, so sometimes we have limitations when it comes to implementation.

I have been using UiPath since 2020. It has been almost three years.

We have had some issues with the Community version, but in the licensed version, we have not had any issues. I would rate it a nine out of ten in terms of stability.

It is scalable. We started with one attended bot and one unattended bot, and now, we have three attended bots and three unattended bots. If we increase the number of projects, we can get a new license and deploy the bots. It is very scalable.

If we are not using a license, we can remove that license in the next year, but that has not happened. Every day, we are increasing the processes.

UiPath has a good community. If we have a problem, we can resolve almost all of our problems through the information available on the Internet. The design part is simple, and we have to design the system as the requirement but during the implementation, if we need it, we can get help from the community.

I have also used UiPath Academy. They provide a good foundation. We can learn the basic things about Excel automation and other functions. They cover the user cases for implementation. I have followed many things, and it has been a good support for me.

Positive

I have worked with Blue Prism and Automation Anywhere. Both Automation Anywhere and Blue Prism are complex, whereas UiPath is very simple. It is easy to learn. A beginner can easily and quickly work with UiPath, whereas it takes time to work with Blue Prism. UiPath is easy, and we can quickly learn UiPath. Its learning curve is low.

UiPath has a huge community. The community support is less with other tools.

We have had on-premises and cloud deployments. Currently, we are using the cloud one. The initial deployment took one or two days. It was not that difficult. The implementation of a use case takes one to two months.

In terms of maintenance, we need to maintain our infrastructure and bots. There may be some issues with the bots, and we need to monitor whether the functionalities are completed or not. 

Its price is reasonable. UiPath's licensing is not a problem for us because we are a big company, but for small companies that need automation, it is difficult to afford. I am from Sri Lanka, and in our country, SMBs do not invest this amount of money into licensing. For a big company, it is not an issue. 

Currently, we have five to six bots, and we are planning to increase them every year. It would be nice to have a version that has fewer features and a lower price.

UiPath is one of the best tools I have used. I have worked on Java and most web services technologies. Robotic process automation is one of the best technologies I have come across.

I would rate UiPath a nine out of ten.

I automated the use cases related to medical processes such as posting the payments, downloading the files from the portal, and claiming medicals.

It is easy to create automation, and it is also easy to test for your test case. If you want to go live with a process, that is easy. You can publish the package from UiPath Studio, and in Orchestrator, you can see if the bot is working fine or not in the unattended mode. If the bot is not working fine and continuously throwing an error, you can stop it from your side. You do not have to log in and stop the bot manually.

One of the projects where UiPath has been beneficial is related to payment posting. It is a weekly process that we run on Friday or Saturday. There are about 1,500 records. Before automating it, we could handle 150 to 200 records per day. It took about 20 days to develop the bot, and the testing took two to three hours. After ensuring everything is fine and publishing it, in 10 hours, we are able to post all the records we have. It takes 15 seconds to post one record. We have developed this automation for one client who has multiple clients. We created a master config for that and changed the credentials and the input file. This way the bot processes one client and posts everything, and then the second client and posts everything. It will continuously run every day.

We also used Computer Vision automation for one of the projects, and we also have automation that gets triggered based on a real-time event. For example, on receiving a client email, the bot runs and does the required task.

As compared to other tools, UiPath is more specific. If you need to develop something specific and publish it, UiPath is very helpful for that.

Another valuable feature of UiPath is the training. Those who do not have a programming background and want to understand how UiPath works can go to the UiPath portal to get free training. They can train themselves as a business analyst, a developer, or an automation developer. The training system is good.

The development and practical aspects are also good. When you get a project and you start working with UiPath, you need to buy all the licenses, but you can also develop some processes without buying a license for demo or testing purposes. You can show it to your manager without buying the license.

In advanced features, there is a feature called Document Understanding, which is helpful for scraping the required data from a PDF.

UiPath Academy is very simple. You do not need any guidance on how to use it. After you log in, you get training based on your role, such as whether you are a developer, solution architect, analyst, or delivery manager. You go to the training section accordingly, which not only has text or PDF but also some videos and practical scenarios. They provide some dummy files as well that you can implement in your system. You can use them to see if it is working or not.

The UiPath forum or community is also there. If you have some questions, people will help you with that. Someone will definitely reply to you, and you will get a solution.

Some kind of code repository would be good. Other than that, everything is fine in UiPath. They improve it every quarter and bring something new.

I have been using this solution for three years.

It is a stable product. In the last year, I have not found any kind of issue or server error. I did not have any issues where the server was down, so you can rely on UiPath.

It is scalable. UiPath provides all kinds of solutions. Based on that, you need to build your project and diagram. You can then start the job immediately.

We are in the healthcare business. My client has about 5,000 members, but over the past year, we have deployed about 25 processes along with 30 payment posting processes. We have five developers.

You can buy licenses depending on the number of bots that you have. If you have 10 bots, you do not have to buy 10 licenses. You can buy one license and insert that one license to run the bots one by one. You can buy as many licenses based on your convenience.

When you have a licensed version, you can raise a ticket in case you have any issues. They usually respond within 24 hours, but they can also take two to three days.

We were facing an issue with the Computer Vision process for 20 days, and we were not able to find a solution. We raised a ticket with UiPath. They connected with me in two or three days. They monitored all the things and recommended the changes. After making the changes, everything worked fine.

I would rate them an eight out of ten because they should give an immediate resolution for any production-related issues. They should have connected immediately after we created the ticket, but they connected after two to three days, so we lost the money for two to three days.

Positive

I have only used two or three RPA tools. As compared to Power Automate and Blue Prism, UiPath is the best. The cost of Power Automate is a little bit low in comparison to UiPath, but Power Automate does not have flexibility. If you have a large project, go with your UiPath, and if you have a small project, you can go with Power Automate.

UiPath is also good when you have use cases where you need to save your portal credentials or FTP credentials. You can easily use the features of UiPath Orchestrator for that, whereas, with Power Automate, there is no way to save your credentials. You need to save them somewhere else, such as in a text file or an Excel file, which is not secure because if someone opens the file, they can see the credentials. In the case of UiPath, they can see only the username, not the password. This kind of protection is there.

UiPath provides two options: One is a cloud-based Orchestrator and the other one is an on-premises Orchestrator. For safety purposes, most of the companies are not using the cloud-based Orchestrator. They are using the on-premises Orchestrator, but you need to set up your database and connect it with Orchestrator. This way, all the things that you have done at the project level are stored in your database. UiPath does not take any responsibility for that. If you do not have a database and you want to run a process smoothly, you can go for the cloud one.

My current project is on the cloud because they did not want to install their own database and set up all the things. It was better to use the cloud option because they did not need to install anything on the system.

The deployment probably takes one to three days. When you buy your license and connect with them, they will guide you on how to set up things. It is easy for me because I have been using it for the last three years.

We calculate ROI every month end to see how much we have saved. For example, if we have a bot for downloading four files, we do not need to redevelop it for another client. With a few modifications, we can use the same bot, which saves money.

In comparison to Power Automate, UiPath's price is a little bit high. 

The Community edition of UiPath Studio is free. If you want to learn something or develop a process, you can install the Community edition of UiPath Studio. If you buy a license for UiPath Studio, the updates do not happen automatically, whereas, in the Community edition of UiPath, all the things are updated automatically. Once you log in yourself, after every four months or five months, when there is an update, it will automatically update itself, but if you buy the licensed version, it will not update immediately. It will not impact your project.

It is better to use automation. Nowadays, every company is adopting automation. I would recommend choosing an RPA tool based on your requirements. I have not used Blue Prism or Automation Anywhere much, so I cannot compare it with them. However, UiPath is better than Power Automate. Based on my discussions with other people who use other RPA solutions, it seems UiPath is the best. With separate components such as UiPath Studio and UiPath Orchestrator, you do not mix up things, so you can clearly do your job.

I would rate UiPath a nine out of ten because I have not had any disappointment from using UiPath Studio and UiPath Orchestrator. None of the jobs that I have built so far have failed.