UiPath Reviews

I am working for a client. I am using on-premises UiPath Orchestrator. I have installed UiPath Studio and deployed some processes for automation. 

I have used it for SAP automation, Excel automation, and web automation. I have not yet used the AI functionality. I might use it in the future.

Manual tasks are reduced, and in less time, I can complete a task. 

UiPath has sped up our digital transformation by 20%.

UiPath has reduced human error. With automation, correct values get entered, and there is a reduction in human error. There is a 10% reduction.

UiPath has saved us money because there is a reduction in manpower. It has saved about 20% on costs.

In terms of time savings, for Excel automation, the backend activities are much faster, whereas web automation takes time because it requires loading the screen and capturing the elements. For Excel automation, the backend activities take 30% to 40% less time.

UiPath Orchestrator is very user-friendly and easy to understand.

The interface is very good. In the latest one, they have added many more activities, which has made it even easier to do automation.

While doing web automation, I am facing a selector issue. In the web portal, we need to capture a screen element. For capturing the screen element, when I run the job the next time, it fails because the limit is not recognized. It is very difficult to make the selector stable. It is not easy.

I have been using UiPath for more than two years.

At times, when I restart the system, the deployed robots take time to connect to the UiPath Orchestrator. Overall, I would rate UiPath a nine out of ten in terms of stability.

It is scalable. We can use it in different companies or industries, such as hospitality or finance. I would rate UiPath a nine out of ten in terms of scalability.

It is deployed at one location, and we have four to five users of UiPath.

I am satisfied with their support. Whenever I raise a ticket, they provide the required support. 

UiPath has a user community, but I did not use it much. I used the UiPath documentation.

I have also used UiPath Academy and completed three courses. I have done the foundation course, the advanced course, and the continuous learning course. I am satisfied with the UiPath Academy courses.

Positive

I have also used Automation Anywhere. Compared to Automation Anywhere, UiPath is more user-friendly. In Automation Anywhere, we have to do lots of things, whereas in UiPath, we have to do fewer things, which makes it easier to do automation. Also, capturing the screen is much harder in Automation Anywhere. It is easier in UiPath.

The deployment of UiPath Orchestrator only takes one day. 

In terms of maintenance, it only requires yearly license renewal and making sure it is up to date.

We have two people who are involved in the UiPath deployment. 

Overall, I would rate UiPath a nine out of ten.

We are an insurance company. We mainly deal with all types of insurance from casualty and specialty to even aviation and medical stop loss.

I have had use cases where we have been taking information from emails and phone calls to put them into a mainframe. We have done claims intake for insurance, and then we have notifications. For the policy system, we have done a lot of back-office accounting work.

By implementing UiPath, we were trying to seek a way to free hours up at critical times. It is not just about hours saved. It is also the quality of the hours that we save and freeing people up for more value-added work.

UiPath has definitely helped with scalability. The number one reason to use something like UiPath is to increase scalability so that we are less susceptible to changes in the market. We can grow our business without growing our staff hours.

UiPath has changed the way we perceive our processes because even outside of processes that we automate, we look at our processes in a new way in terms of process improvement. Not everything needs to be automated. Some things just need to have the process changed. It has helped us to be very critical of our processes and be more forward-thinking and not just sticking in the same ruts.

UiPath has helped with the accuracy. There is less fat fingering of things. When the robot is entering things into a system, it will put in exactly what was input into it. There is also a chance for transposing things, so there is a lot more accuracy in that respect.

UiPath has freed up time and resources for other tasks. That has been our main focus in terms of the ROI we look for. With the accounting back office practices, our close cycles are shorter, but people are not working more. With automation, we now have things that are on more of a 24-hour cycle. We are able to do a higher volume in less time.

We have saved thousands of hours not just in the back office accounting side for close cycles but also in insurance. We have busy seasons. We sometimes had to hire temporary workers. With the automation of our claims intake and other processes in that area, we are no longer hiring those temporary workers. We do not need them anymore.

The ability to connect various systems that do not have any kind of API between and the areas where we need to mimic what a human does to a system in terms of input and output is valuable. We primarily use UI automation where we simulate what a human does within an application. By using the right selectors, we try to find where on the screen we need to click. We take in information from input files. We use all the logic flowcharts and logic trees to determine where the information needs to go in a system.

Some of the areas around the administration aspect of UiPath, which is what I have been mostly working with over the past few years, can be better. From an organizational standpoint, some of the guidance there could use some work in terms of helping COEs know how to grow and how to take control of their organizations as they spread.

I have been using UiPath for about five years. 

There are still some stability issues. There are sometimes issues related to bots acting up. It can be hard to tell whether that is something related to how we developed it or whether the bots are having an issue. We are not sure why, but there are some stability issues.

Its scalability is fine. It has definitely gotten better over the past few years with all the improvements there. I know there have also been new offerings for serverless robots, which we have looked into, but they do not fit our needs. The UiPath Orchestrator makes it easy to maintain its governability as we scale, which is one of the main differentiators of this solution.

They can sometimes be hard to get a hold of. There have been a few times we have had to go to the UiPath Pro support. While we have eventually gotten to the solution, it has sometimes taken us a while to get in contact with someone who has the right knowledge to help us with our problem. I would rate their support an eight out of ten.

Positive

This is the first one we have been using. We have a group in the company that started using Power Automate. They ran into a problem and turned that back over to us. We are the UiPath team. They tried to automate something with Power Automate, and we ended up taking over that project.

Orchestration is the main differentiator between Power Automate and UiPath. UiPath has orchestration whereas Power Automate does not. Without that orchestration, you lose a lot of the value for these robots, especially at the organizational control level.

I was brought on specifically to do the deployment at my current company. It was fairly easy. I did an on-prem deployment about five years ago, and now, I am doing the cloud deployment. We are using the automation cloud. Having the automation cloud made it much easier to do the deployment this time than trying to set up the on-prem Orchestrator the first time.

In terms of the implementation strategy, we essentially looked at how many processes we had as candidates and what we thought the bot load would be. We stood up that many VMs. We deployed unattended robots to those. In terms of Orchestrator, we just did some basic tenant separation, and as we have grown, we have seen where to increase the bots.

We used one called Accelerate to start with. Our experience was fine. Our goal was always to transition to our own, so after the proof of concept was done, we hired our own developers. We hired our own team and went from there.

We have definitely seen ROI coming from it. For any project we take on, we look at both quantitative and qualitative aspects. Quantitative is usually just the hours saved. If a process is automated, how many hours are saved as compared to the last one? Qualitative would be things like whether we have increased accuracy, whether we have increased any time to the next process in the chain, or whether we have gained redundancy and reduced the fragility of our processes.

If it can be lower, we will always take lower.

Blue Prism was what we looked at pretty heavily. We looked at Pega. We also looked at Power Automate, and some groups within the company decided to try and use that. 

When comparing UiPath and Blue Prism, there is clearly a difference in power and capabilities between the two. We also had a solution partner who could work with us better with UiPath at the time.

We are currently setting up the AI Center. We have not used UiPath Process Mining and Task Mining. We tried to use the task binder where you record something and create a workflow from it, but it was not very useful for us. The output was not very useful for us. The documentation from it was also not useful for us.

If you are evaluating UiPath and other products, I would advise looking at what kind of model you are looking for. Are you looking for a more federated model or a centralized model?  You should look at what kind of governance you need in place for the solution you are looking for. One type of solution is that you put it in someone's hands and leave it and forget it. If you want to empower people and maintain central control, UiPath would be for you.

In terms of deployment, I would go for the automation cloud every time. There is the ease of use of not having to worry about standing up your own servers to monitor that. The US cloud especially has been very stable.

Overall, I would rate UiPath a nine out of ten.

We're a consulting firm and we use the solution to automate various systems, mostly in data processing, including in the customer service department. We're also using it to take advantage of artificial intelligence.

We've noticed a lot of benefits. For example, I've noted a reduction in errors in data processing and analysis. We've also been able to increase our working hours. We don't necessarily need to have a human workforce going around the clock. There are some hours or some shifts where we rely on the robot to take care of the workflow. We've also been able to apply artificial intelligence to our work to amplify the customer service experience and help us be efficient and fast.

The pricing is pretty fair. It fits various types of organizations.

The support has been very good. We appreciate it. Support is in various languages.

Building automation is very easy. You can deploy anywhere and you can even access the platform using a mobile device, web browser, or iPad. This flexibility makes it easy to use. 

It allows us to handle end-to-end automation, mostly for data analytics and data processing. With this option, we are able to work through processes 24/7. This reduces the amount of downtime.

The community has been very helpful. You can go there if you have minimal problems instead of going to support or having to shut down your whole system. You can contact someone in your community, and they can help share insights. It's helpful for teaching staff how to use the platform.

We've been able to reduce our on-premises footprint. At the same time, we've been able to grow our digital footprint.

We have dashboards where we can monitor staff, and even if they are far away or working from home, we are able to monitor everything, and people no longer need to necessarily be on-premises to work.

The solution has a useful Academy that I started using in the past year. When we have new employees who are onboarding to the department, we conduct an initial training. However, after that, they can go to the UiPath Academy and acquire even more skills. The biggest benefit is that it allows any employee to learn on their own time. It gives everyone the potential to grow and learn at their own pace.

We have used the AI functionality from UiPath, mostly in Europe. As an accounting company, we handle tons of Excel worksheets and formulas. The AI makes it all very efficient and helps with analytics and processing. 

It's sped up our digital transformation. Initially, we did not have automation. We only had automation available through other companies. When we adopted UiPath, we developed an automated process that allowed us to bypass having a human behind the computer.

UiPath helps reduce human error. It's reduced it by a huge amount and was a big reason for us acquiring the product.

The solution has helped free up employee time. Employees now have to do less manual work. You don't have to manually look at every receipt or every piece of data. We assign a UiPath automation to the task. Something that would take a human an hour is done in 15 to 20 minutes.

It does save us money. We used to have two shifts before acquiring UiPath. Now, we've reduced the human workforce for the night shift. 60% of the work we can assign to RPA. Less of a human workforce means less money spent on manual productivity. It's helped us reduce our overall operating costs.

The billing plans should be improved. Instead of billing per month, they can offer plans for a year or two.

I've used the solution for a year and eight months. 

The solution is stable, depending on your infrastructure.

The solution is scalable. 

We contacted support in the initial six to eight months of usage. We used to contact them monthly since not all staff were knowledgeable. 

Support was fast enough. Of course, there were sometimes technical errors and it would take two to three hours to get a response.

Positive

We did not previously use any automation solution. 

While we started on the cloud of the free trial, we moved to the on-premises deployment model.

The deployment was easy. We started with the free trial, and after we saw the results, that informed our decision to continue.

We had 20 to 40 people involved in the deployment. 

There is some maintenance required. New employees need to be onboarded and sometimes they mess up and the IT team will have to return the platform to normal.

We didn't go through any other channel during deployment. We had an efficient vendor from UiPath.

We have seen an ROI in that we were able to reduce the need for so many workers on night shifts. That aspect has brought down our operating expenses while driving productivity up.

I'm a customer and end user. 

I'd rate the solution eight out of ten. 

My use cases for UiPath include finance, HR, SAP, and technology. 

The tool's most valuable feature is RPA. 

UiPath should improve its licensing structure. 

I have been using the product since 2018. 

The selectors and modern UI are not stable yet. 

The product is scalable. 

The tool's support is good. 

Positive

The tool's deployment is straightforward. We started with contractors and built some POCs. We had a pilot to select the business criteria. 

UiPath's implementation team helped us with the deployment. 

The solution's pricing is a challenge. Every time I go to renew my contract, the prices increase. It is getting expensive. 

The business objectives we tried to achieve with UiPath include time savings and user satisfaction. 

Automation has freed up our employees' time. 

I rate the solution a nine out of ten. 

I'm using one or two robots. We use the solution for reports. We have another software yet we don't have support. Instead of pulling reports manually, we use the program to get the reports and pull them for us. 

The solution is very simple. We can easily create robots. It's easy to build automation.

UiPath enables us to implement end-to-end automation. We have some manual procedures and it helps to complete those tasks. 

We use the UiPath user community. It's free. 

The amount of work we have is very small. We don't have big workflows. However, employees can now spend time on other things, and it's helped us manage our time around reporting.

The company has helped us minimize our on-site footprint.

We've used Academy courses. I've done classes myself. I don't use it every day. I've only used it once, actually.

The solution speeds up digital transformation and reduces the cost of digital transformation. with UiPath, we do not require expensive or complex application upgrades or IT application support.

UiPath has helped reduce human error. It has also freed up employee time. It has saved about 20 to 30 hours or so.

I've dealt with compatibility issues with Microsoft components. When we upgrade the UiPath framework, we might be able to fix the issue. 

We'd like the accounting team to be able to have improved data out of SAP. 

I've been using the solution for one year. 

The product has been stable.

It's a scalable solution. We have about 150 people using the solution. We may increase the usage in the future if we have an opportunity to apply more robots. 

I haven't worked with technical support.

I did not previously use a different solution. 

We're using the 2023 version of the solution. 

I was involved in the implementation. 

The setup was straightforward with the help of UiPath documentation. The implementation process took less than one day and we implemented with one or two people doing the work.  

UiPath does require a bit of maintenance, however, it is not that much. We're mostly just dealing with compatibility issues with Microsoft. 

We deployed the product ourselves. 

As for the cost, I'm not sure if it has saved us money. The customer still keeps the same number of employees, for example. That said, the important thing is to reduce the time it would take for them to handle tasks. In some ways, it's done that.

Our use case is still very small. Therefore, we don't want to buy a solution that is too big for us. We don't want to pay more than $10,000 USD for a license. Therefore, we're focused more on the community version. 

We did evaluate other options. We found UiPath to be more localized. They were one of the top solutions.

We are UiPath partners. 

We do not use the solution's AI functionality just yet. We're only using small automation. We also have yet to try the document understanding features. We still need to try some advanced features and I look forward to experimenting with it.

I'd rate the solution eight out of ten. 

I would recommend the solution to others who need to create automation. 

Our use cases are generally related to front-end UI-based automations that emulate tasks done by teams. For example, we do front-end SAP automation for data entry and scraping or posting data to websites that are related to the organization. We use UiPath for other automations like extracting and manipulating data from Excel. The primary use cases are in finance, HR, and operations. In logistics, it's used in full-sprint solutions.

UiPath's ability to do end-to-end automation is crucial. If we do the automation in bits and pieces, it's challenging to integrate it. The best part is that the turnaround time is drastically reduced because the process isn't being put on hold in between two manual interventions. The more permissions we apply, the more we reduce the turnaround time. However, the smaller automations don't impact the turnaround time that much. If the logic is set correctly, it can completely eliminate human error. 

The UiPath community development forum is helpful. Developers can access all the information they need if they get stuck. For our use case, we refer to OpenMedia, not any particular program. To understand what are the RDP use cases. I personally follow primary and secondary research forums as well as McKinsey's technology consulting newsletters and documentation.

The UiPath Academy explains various use case scenarios through videos and training sessions. It's all practical, hands-on instruction instead of purely theoretical. That made a significant difference by increasing our confidence in the product and ability to create our own automation. You can track each team member's training steps in parallel because everyone needs to be on the same page.

Uipath doesn't necessarily reduce our on-premise footprint. We use UiPath to automate configuration integration, so I can't say there is any direct impact because RPA is now just part of our on-prem ecosystem. The solution doesn't require expensive or complex application upgrades, but certain applications need scripts to be enabled to get UiPath working on their front end.

It saves time, but the amount varies. Each process has a different impact depending on the frequency of that process. If a process is running daily, the values are high, but sometimes it's low. The organization aims to have one bot per person, so everyone has one attended bot that can replicate their monitor network. It's the equivalent of adding one FTE per year by default per person. Every person can have a bot, scale up the work, and get more done in a day. 

The amount of money saved also depends on how often the process runs. We pay per bot, so if the bot isn't running frequently, we might not save any money. However, if the requirement is to do many more tasks than a single person can handle, it makes sense to use a bot, and we can save a lot of money that way. Sometimes, we have different goals beyond just saving money or reducing the time that our staff members spend on tasks. We might deploy a bot to improve the user experience and save the user some time. In some cases, we might not see short-term savings, but we'll see a benefit from it in the long run as the process volume increases.

The feature I like the most is ONEWEB UI automation. UiPath's OCR technology also works well. There is another feature called Action Center that lets you decide what happens after the data is captured. It passes the data into Action Center, where a person can review and approve it before it goes to the next step. It helps us manage our attended bot processes.

It's generally easy to build processes because of the drag-and-drop configurable suite. However, more complex expressions may require some kind of functional coding. UiPath also has some prebuilt functions in its training module that can be utilized to enter the expressions and get the job done. That's one workaround.

UiPath's built-in integration with Python scripts could be more robust so that I do not have to depend on another technology and I can do everything on one platform. 

Each program you write on UiPath contributes to bot consumption and utilization. As you add more bots, your costs will increase for more actions. Python is open-source, so it is totally free. Depending on our automation needs, we go back and forth between these two technologies. Better integration between these two tools will help organizations cover all areas of automation without more cost-effectively. 

I have used UiPath for approximately two years.

I rate UiPath nine out of 10 for stability. We haven't faced any challenges with UiPath's stability because it is a SaaS product. It runs on the UiPath cloud, and things are working fine. 

UiPath is fully scalable. I haven't faced any challenges in terms of scalability because the cost is not per user or per process. It is priced according to the amount of bots being consumed, so it all depends upon the complexity of your own project. If the complexity is lower you can reuse and share 

I rate UiPath support nine out of 10. They always respond with solutions within the time established by the SLA. 

Positive

We were working with Power Automate. It has benefits from a cost perspective. The cost per developer is much lower relative to UiPath. Power Automate is a more cost-effective solution for larger enterprises. However, UiPath has more technological capabilities, and it's more user-friendly for developers, which is why UiPath is being adopted more over Power Automate. At the same time, Power Automate is continuously improving, so it may reach the same level as UiPath in the future. 

We are using the cloud version of UiPath, which is hosted by the UiPath team themselves. We do not use a private cloud. The network configuration didn't take much time. The deployment involves setting up a UiPath account and configuring permissions. It is a SaaS platform like Office 365.

The deployment time is just the amount of time required to develop processes for the project. It depends on the size and complexity. A project with hundreds of activities might take a few months, but a simple project with only two processes can be done in a few hours. 

I rate UiPath eight out of 10. 

We utilize UiPath to manage workflows and deploy application solutions into our customers' environments. UiPath simplifies various business tasks, such as automating applications, Excel, and segregating data.

We deploy UiPath both on-premises and in the cloud depending on the customer requirements.

Building automation with UiPath is straightforward. Even individuals with limited technical proficiency can utilize UiPath.

We implemented UiPath for one of our partners. They previously required human intervention to manually manipulate data in a 17,000-column Excel spreadsheet for monthly reporting, which used to take one hour. By employing UiPath and incorporating a Python script into the process, we automated the Excel spreadsheet. As a result, the task now only takes three minutes. This automation saved the organization time and money, increased the accuracy of its data, and allowed its employees to focus on more value-added work.

UiPath enables us to implement end-to-end automation. I have a client in Malaysia, and I am from Vietnam. I visited the client on-site for two weeks. They are in the manufacturing industry, and my purpose was to gather information about their automation requirements since they had never utilized automation before. I managed to assist them in standardizing their processes by offering advice on how to implement the solution. I collected the end-user requirements, which were then used to create the necessary documentation. Once the document got approved, the developer and I developed the bot and subjected it to UAT before obtaining final approval for its production release.

The UiPath User Community is wonderful. While many RPAs have their own communities, none compare to UiPath's. The community edition of UiPath boasts a substantial user base, with expansive groups across various social media platforms. When I first started using UiPath, I would always turn to the user community whenever I encountered an issue. I noticed that others had already asked the same questions and received answers, which was quite convenient for me.

Everyone associated with UiPath usually completes at least their first year of Academy courses to acquire a fundamental understanding of RPA and the platform's functioning. This knowledge is crucial for facilitating the easiest possible approach to automation. I genuinely appreciate all the videos from each course. Every video contains valuable information, and I never skip any of them. In the beginning, the Academy was a great help to me.

UiPath helps reduce the cost of our digital transformation. One of our large financial industry clients mentioned that where they used to require 13,000 employees, they are now only using 6,000 to complete the same work through digital transformation.

UiPath assists in eliminating human errors. Numerous tasks performed by humans each day involve typing in information. Humans can make mistakes due to factors such as fatigue, mood, or feeling unwell. However, automated processes are not susceptible to these issues.

UiPath can contribute to cost savings for an organization, contingent upon the organization's size and the quantity of tasks being automated relative to the number of employees presently engaged in performing those tasks. On average, UiPath has the potential to reduce costs by approximately 30 percent.

The most valuable feature is the ability to view my own activity and customize it on the platform.

We cannot utilize the UiPath community edition license to operate any bots that we have created using that version in an enterprise environment. This is because we are obligated to employ UiPath Studio, which necessitates a distinct license for professional use.

I have been using UiPath for two years.

UiPath is the most stable platform.

UiPath is scalable.

I previously used Power Automate before switching to UiPath which is an out-of-the-box solution.

The initial setup is straightforward. We just need to run the orchestrator and the packet. I can complete the deployments myself based on the documents.

I would rate UiPath nine out of ten.

UiPath requires proper maintenance which is outlined in the user manual.

We're in the supply chain industry and we use UiPath for automations for purchasing and selling and to make people's lives easier within the organization. We have 20,000 users in our organization. 

We do not currently use the AI functionality in our automation program but we have in the past. I've found Document Understanding in the AI Center valuable. In the past, the action center was slow compared to some competitors in the IDP sphere, which can be detrimental if you're dealing with millions of documents but this has since been improved.

We use unattended robot processes almost exclusively and this includes approximately 130 to 140 processes. We do have plans to increase this usage and create more core automations. Certain automations have a shelf life and need to be retired at a certain point. A lot of times we're working with systems that are eventually going to be replaced. The reason why we use UiPath over strictly APIs or something programmatic is that we don't have access to something programmatic. 

UiPath has improved our organization in the sense that it has reduced our manual hours by 200,000 hours per year. This is substantial especially given the size of the COE. We don't necessarily realize these benefits from a head count decrease perspective but we definitely realize it from a time-saving perspective. 

The automations that UiPath provide free up our team members for tasks and projects that they have always wanted to do but have not had time for. There has been a shift to more meaningful work and doing work that hasn't been done before.

The Orchestration feature has been valuable as well as Studio because it makes it easier for people to develop who don't necessarily have a coding background. The UI automation when using UiPath is the best in the field, as far as RPA goes.

UiPath will introduce new features and it appears as though there is an unspoken rule that what they have released is not where it needs to be, but it'll be there eventually. To improve this solution, there could be increased transparency over licensing and consistency regarding what it costs for on-prem and what it costs for the cloud. This would make it more enticing for people to switch from one to another. 

We have also experienced some difficulty with updates and making sure that everything runs consistently. Many times, new releases are not communicated and then are released. This is included in documentation but this documentation is not always stored in the same place. Having some clarity or upgrade assistance to highlight what we need to look out for would help a great deal. 

We have been using this solution for two years. 

This is a stable solution but stability is dependent on your configuration. If you configure your robots in such a way that every VDI that runs or every virtual machine that's able to run a bot has a backup, then it will be stable.

UiPath's support is quite good. Whenever I've submitted a ticket, I have gotten relatively good responses within a couple of days. If you say that something is urgent and critical, they do get back to you sooner. Sometimes you get stuck between L1 and L2 support, which can be frustrating. 

I would rate the support for this solution an eight out of ten. 

Positive

The complexity of the setup depends on what you're trying to deploy. If you're deploying only the orchestrator and setting up robots, it is pretty straightforward. If 10 is difficult and one is easy, I would rate the setup a three or four. 

The certificates needed to set up the orchestrator can be confusing and frustrating during setup. For the most part, what you need to do is straightforward. When it comes to installations that require a Linux virtual machine, Docker configuration, or Kubernetes, the setup is more complex. It is more complex to set up an on-premises configuration compared to a cloud configuration.

From what I've seen, organizations will have vastly different numbers as to how hours correspond to dollars. Our return on investment has been good, even from a conservative perspective.

The way that the licensing is structured is confusing for some because there is different licensing if you're on the cloud versus if you're on-prem. There are unattended licenses and then there are non-production licenses and people get confused by that.

There's a level of buy-in that's required that makes it difficult for people to get started. For example, "If we do this, we need to get this whole package" as opposed to, "Let's get a couple of licenses and see how it works for us." There's the community for these questions but if you want to do an on-premise installation, you can't really use the community in the same way to get clarity.

As far as strictly RPA and UI-based automation solutions are concerned, UiPath really shines over its competition. The most similar comparisons would be Automation Anywhere and Blue Prism, and I don't think that they have the same level of ease when learning how to use their solutions. Not as many users in the market know how to use those solutions and they don't have the same level of orchestration which makes them more difficult to manage compared to UiPath. 

The UiPath's user community, in terms of the value that you gain by being a part of it, is hit or miss. A lot of times there aren't responses to the high-level questions. There are a lot of responses to people who are just learning how to use it, but for more complex questions, there are no experts to field responses. It is possible to find these answers but they are not necessarily contained on UiPath's platforms. That being said, I did find the user community and academy very useful when I first started using this solution.  

I have done 16 courses from the academy and continue to review what is released to see if it would add value to me to stay up to date with the latest features. The academy provides the ability for more people to learn UiPath and learn RPA and this makes it easier to hire new team members as they can easily gain the necessary skillsets. They still do have to learn on the job to some extent, but there's a basic skillset that's pretty well established and there are certifications that are associated with that. 

I would advise others considering UiPath to start with some use cases in mind. I don't necessarily think that you're going to get value out of evaluating the solution if you don't have at least a few things to get you started. I would advise having someone with a technical skillset to assist in this regard. 

I would rate UiPath a nine out of ten.