UiPath Reviews

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.

UiPath fills the gaps; it's a type of bridge between daily tasks and end-users. For example, on a daily basis, a user may need to prepare and send a report on time. There are many tasks like that on a daily basis that are boring if you are doing them continuously. UiPath can act smartly, eliminate human involvement, and capture everything.

If you have a meeting but also want to prepare a report, a robot can do it on your behalf and do so with zero errors. Whatever we program it to do is what it will do. It reduces human error by more than 90 percent.

And talking about digital transformation, I have worked with a lot of the taxation forms in the APAC region, Indonesia, and the Philippines, and these forms are a bit tricky and a challenge. The new digital product they brought in is very nice and is able to crack them and capture all the necessary data from those forms. It's pretty cool, using the AI.

UiPath also reduces the time people spend on tasks. I'm working with a client whose only KPI is the time things take, and the dashboard is showing automation is saving 90 percent of human time with UiPath.

Some organizations have an exact ditto—a mirror environment set up between their production and UAT environments. But a few organizations are not like this. Their UATs slightly deviate from the production environment. In this scenario, we have what we call PAT, production acceptance testing, before things are moved to production. UiPath overcomes the challenges of that. It enables you to easily update any changes between these environments. That will not take much time for the developer. Selectors play a major, vital role in automation, and if a selector is changed from one environment to another, it is not that hard to update it. It's very easy, actually, meaning you can do it in less time.

It's a no-code platform. You don't need to have in-depth coding knowledge, which means people can adopt it and move forward with it. It's very convenient to use. If you are interested in learning new things, UiPath is an open platform that you can play around with however you want. And there are a lot of roles, not only as a developer but other roles as well.

Also, if an organization has more than 50 processes and you want to monitor them at the end of the day, there is a very good dashboard called Orchestrator. It will show you a report on process status, success or failure. If it failed, it will show you the exact reason. It's good to have this kind of dashboard in your life.

For financial payments, for example, at the end of the day, humans are smarter than a robot. Only humans know the scenarios that decide whether we can make a payment or not. So humans fill this gap at a certain point in time. UiPath has introduced a product called Action Center. With this product, a robot will process all the payments, and then it will ask permission through Action Center for whether it can proceed or not. If they press OK or approve something, the robot will continue. Otherwise, it will not. It's end-to-end automation.

When we recruit any new employees, we first suggest that they sign in to the UiPath Academy and go through the courses. One of the good things I like about it is that they keep updating it. Whenever there are new features, they are immediately reflected in the Academy. It gives you detailed information, both text and video. And at the end of the module, they check your knowledge, what you have learned from it. They also have certifications, such as UiPath for developers, associates, and business analysts. They want to encourage the community to use the Academy. I recently received my UiPath certification, which is a bit harder than other certifications. You have to have in-depth knowledge to get it. Overall, the Academy is good.

I have gone through all the new AI features. They say the robot is able to smartly create the body of an email based on your content. I have already done some testing on that, and it worked fine. It's pretty cool.

Whenever they release a new version, there are some bugs. They should strengthen their testing team to avoid these errors and not release the product to the market with bugs. They do release patches, but they should take their time. Their target is to release a new update quarterly. I would suggest they take an extra 15 days to do proper testing and then release. As a developer, I see a lot of Activities have bugs.

I have been using UiPath for almost six years.

The stability is an eight out of 10.

The scalability is a nine out of 10.

Their technical support is very fast. I have created a few tickets for license-related bugs, and they have replied fast. Their support is good.

Positive

Deployment takes three to four days, generally. They will say it takes hours, but every organization is different in terms of its IT security policies, et cetera. It takes some time.

There isn't any separate maintenance required for the solutions. A robot will just keep on working. All you need is a good backup system.

ROI may differ from company to company. Some think about human resources, and some think about money. But I have seen ROI in all these ways. It saves you a lot of time and money as well. If you have an employee that was responsible for a process, they can now spend that time on other tasks.

There are a lot of automation tools in the market, such as Power Automate, but UiPath is number one right now. Initially, we started with it for automation purposes, but they have released many other products as well. Day by day, it's getting bigger.

I have worked with other tools as well, but in a complex situation, such as HR-related processes, where there are mathematical calculations, it's those calculations that are a challenge for users as well as developers. But UiPath will come up with a very good way to do a lot of arithmetical calculations. That makes it very easy to finish a complex process. With other tools, it may take some time. As a developer, UiPath is easier.

There are a lot of pros and cons when you're comparing one product to another. One important difference is robot speed. Power Automate works much faster than UiPath. When I develop, I can see a difference in the time it takes. This is something for UiPath to think about. And the pricing, of course. People say the robot license for UiPath is costly. Power Automate provides a very cheap rate, like $50 per month. UiPath is an annual subscription, but with Power Automate you can pay monthly as well. UiPath doesn't have that option.

If you have a very simple task, you can achieve it very quickly with UiPath. But complex tasks can also be achieved very easily. If you have good developers and they have the knowledge, they can easily crack more difficult tasks. I have worked on a lot of calculation-type tasks, Excel-based complex applications. We do well with this solution.

My advice is to go ahead and install it. As long as you're ready to invest in the product, it will give you better results. But go with the option of a proper project management team as well as developers. With that kind of team, you will see value for your money. The product is good, but you should have the proper people.

Our use case started with the financial sector. We are expanding it to the navy's other operational aspects, such as HR, legal, procurement, etc. 

UiPath's most valuable features are automation and document understanding. 

I want our relationship to be better because of the nature of what we do. 

I have been working with the solution for four to five years. 

The solution is very stable. 

UiPath is scalable. 

We work very closely with our UiPath representative. 

Positive

We used Microsoft Power Automate. UiPath suits our cloud environment better than Microsoft Power Automate. 

Deployment was complex because of our environment since we needed to get approvals. 

We work very closely with Deloitte. 

We had evaluated Automation Anywhere. 

Our business objectives for AI-powered automation are finding inefficiencies and improving efficiency and ROI. 

AI-powered automation has helped our organization to be more efficient and faster. It is working 24/7. 

UiPath has enhanced the accuracy of our operations. We were able to recoup funds that we previously knew didn't exist. It has boosted people's morale since they are not working on tedious tasks. 

We estimate that UiPath has saved the Navy about 156,000 hours. I rate it a ten out of ten. You need to understand the tool's processes. 

I have been in three different organizations working with UiPath. In all of them, I had to create the center of excellence for UiPath. For automation, we decided to use UiPath because it was easy to learn. We had citizen developers involved. Most of the use cases were typical manual repetitive tasks and did not involve too much intelligence. I did not use the AI components in any of the use cases that I have done in the past. We mainly had end-to-end automation of simple processes. They were not too complex.

I have worked in the energy sector, and there were processes that were connected to renewable energy projects, but they were not related to a good cause, such as improving sustainability. We also had processes that did not provide any financial gains for the company, but they improved the motivation of employees. For example, we automated a process to check employees' birthdays and sent an email congratulating the person and tagging their manager as well. There were no financial gains, but it had a good impact on employees.

In most cases, it is easy to do automation with UiPath. It is not always the best solution, but in most cases, you can imitate what a user is doing. You can substitute that and create a process. It is very easy to do this. The complexity normally comes from the reengineering of the process to make it more efficient, but that is not about UiPath. That is more about the company thinking that we have been doing this for a long time and how we can make it better. It is very easy and straightforward most of the time. From the thousands of activities UiPath has, I end up using the same activities 90% of the time. It is very easy to remember and organize in my mind. As soon as I hear a process, I know how I am going to do it. For example, on receiving an email with an Excel file, we will extract the data that goes line by line into SAP or another platform. We will then save it and then write back the status by email. This is a very simple case, but it would be very hard to implement using any other technology. When it comes to end-to-end automation, about 90% of the time, you can do end-to-end automation with UiPath, but there are times when UiPath is not the best solution.

The main benefit of UiPath is that it is easy to develop and deliver automation. We can do this while software engineers are dealing with a more robust solution for the future. For example, when we need to connect different applications, and there are no API calls they can connect to, UiPath can provide a bridge for the short to medium term while resources are working on the final solution. I do believe that UiPath has a lot of strengths, but in terms of maintenance, there is one more application in the middle that we need to make sure is working for the end-to-end process to not fail. I can deliver a solution in one to two weeks instead of waiting six months for the final solution, but there will be more maintenance.

UiPath has freed up employee time, but the time saved depends on the use case. We had some very big processes that saved a few days. Overall, it frees up about 10% of our employees' time. 

UiPath has saved us costs in theory, but in practice, I am not sure. It saves the time of our people, but we are not letting go of those people, so the cost of those people is the same. However, these people might be doing other work that might bring money to the company. 

It is very easy to develop and deploy. It is easy to work with different applications at the same time. For example, I can read an Excel file and then go to SAP or any other platform. I can then open Outlook and send an email from Outlook. I can even use Teams. Being able to combine all these applications is the main thing that I like. 

I also like how fast it is to develop a big, low-code platform engine. You just drag and drop, and most of the activities are done. It is very fast to create processes. I like it.

Its pricing changed again this year. I do not know why it just went up, but I do not like that. This is something that I would like them to improve for sure. 

It would be nice to have the possibility to change the values in the middle of the debug. For example, I am debugging a process, and I write at a place. The value of that level is one, but I want to see the results of it if I change it to two. It does not seem possible in UiPath. It is possible in other software, but in UiPath, it is not yet possible.

I have been using UiPath for six years.

The Orchestrator, cloud, and everything else have been stable.

It is scalable. We have about 20 people using it. It will impact around 40 to 50 people.

I do not have direct contact with the UiPath technical support because we have a vendor, and we go through the vendor. 

The UiPath community is very good. I myself do not contribute much to the community, but anytime I have doubts, it is very easy to find a solution in the UiPath community. The community gives a lot back. There are a lot of people writing back. It is very well established. About 90% of the time, I find the solution, and the other 10% of the time, I find a way to the solution. It normally takes me less than a day. There are a lot of activities created by the community as well, which are very helpful. I know some of the people who create these activities. People just give back.

In my current organization, we were not using any other solution previously. In other companies where I worked, UiPath was the first solution, but in one company, I also worked with Blue Prism. We had both UiPath and Blue Prism at the same time.

UiPath is easier to learn. It has certain activities that Blue Prism does not have. Visually, UiPath is much more appealing. I know the visual appeal does not matter much to a lot of people, but it matters to me.

It is deployed on the cloud. We moved to the cloud last year, and it took us two months to set it up and go from on-prem to the cloud. About 50% of the time was spent on things related to our company in terms of security and other things. It was not on the UiPath side. On the UiPath side, it was pretty straightforward. It was pretty nice.

Five people were involved in total, but they were not involved not full-time. 

We have seen an ROI, but I do not have the metrics.

Its price is fair, but I would prefer it to be lower.

I would recommend UiPath. I would recommend starting with very simple processes. Do not go for a very big end-to-end process. Start with a part of it, gain confidence in it, and then start building on top of it. Many times, the process that people want to implement is too complex, and they do not put it down on paper. They do not do a cleanup of the process, and most of the discussion is happening while developing, which makes it complex, so I would recommend starting with something small, seeing the results, and growing from there.

Overall, I would rate UiPath an eight out of ten.