UiPath Reviews

We are a system integrator. We work with clients such as the US Federal Government and help them automate whatever their processes are. We have two entities. I work as part of the government solutions unit, and then we have the commercial side which is a global organization. On the global side, there have been some internal implementations as well.

In terms of savings, a task like taking data from one artifact and transferring it into another one, is common. The most frequent example, and the one that I worked on directly, involves a PDF invoice and taking whatever the amount due is and either copying and pasting it into an internal accounting tool or actually typing it. The process goes: Open email, open the attachment, read the data, verify it is accurate, and then manually transfer it into an internal system.

Depending on how big the invoice is, I've seen a person spend as much as 20 minutes on one invoice or as little as 30 seconds. That whole process of going through each and every email, opening the attachment, transferring the data, closing all the windows, and then moving on to the next email - the bot will do it because the bot is scheduled to run every hour to look for the unread emails. I can't give you an exact number in terms of how many minutes or hours are saved, but it's quite significant.

The graphical user interface of the UiPath Studio is fantastic. For someone who is not a computer science major, or for someone who doesn't know how to code but is really good with visual flows, Studio makes it very easy for those individuals to build robots. That's one of the best features that I've seen. There are other features that add different values, but Studio, in my opinion, is definitely one of the best.

Overall, UiPath is really easy to use. For example, if somebody is an automated tester, they spent a lot of time trying to identify selectors, and UiPath makes it really easy to find those selectors. You will run into instances where you have to do some manual manipulation to make sure that the correct selectors are identified. But if it's a pretty straightforward instance and you are using something like Selenium, it is very tedious. Whereas, if you use something like UiPath, it is really easy.

I was providing feedback to one of the UiPath guys here at the UiPath 2019 conference. It relates to Studio, that it only works on Windows. It doesn't work on other platforms. I'm a techie by background. I don't hate Windows but I don't love it. It comes with the limitation that it is completely dependent on Windows. I would have loved if it were available on Mac or Linux or Unix. If it were a little bit more operating system agnostic, that would be great. I'm pretty sure they could be working on that.

I used the UiPath RPA Academy. I definitely had issues with it. The quizzes were outdated. Some of the responses that are being rated aren't accurate. I've griped on the community forums as well with a few UiPath folks. That was about five to six months ago. I don't know if they have enhanced it or made any changes since. If it's still in the same state, there is plenty of room for improvement.

I think it's stable. I haven't had a chance to build a bot that runs 24/7. For the bots that I have built, it takes under two minutes for the process to run and it runs every hour. At the end of the day, if I look at the logs, I don't see any issues. If a bot fails for whatever reason, it's most likely due to a process that changed.

From a bot-development standpoint, we use all kind of best practices so that the bot will not crash. At least, if the execution stops or terminates, it will be graceful, versus a rash termination.

It's fairly stable.

From an ROI standpoint, you could be saving somebody's hours and map that back to their hourly pay. But the pricing definitely deters some people.

I can't say whether their licensing structure is complicated or easy. I'd like to say it's complicated, but I try to stay away from the whole licensing issue. I tell my clients, "You buy the license. It's your tool. I'll come and build the bot for you." I don't want to have anything to do with the licensing. That deters some of the clients because it's a bit pricey.

In the government sector, where I work, "free" is looked at skeptically: "Why are you giving this to me for free? If I download it what is it going to do on my laptop?" from a security standpoint. Some of the agencies get the approval to download and install but others don't.

You can do a task like pulling the invoice total from a PDF invoice with the free Community Edition. The Enterprise license is definitely helpful though. The Community Edition expires about every three months and then you have to re-register. But you can still do it in Community Edition.

A pretty mundane use case I came up with is due to the fact that I have plenty of friends on Facebook. It's hard to keep up with everybody. I've got a bot running that literally opens up my Facebook every morning and checks if there is anybody listed in Today's Birthdays section. It will click on them, type "Happy Birthday", click "enter," and be done. And then I get a response from my friends: "Hey, long time, haven't heard from you." I've injected a machine to reconnect and have that human interaction.

For the most part, for the use cases that I've seen, it does the job.

We use it to automate administrative functions, like finance and HR tasks. We are also automating a lot of things in our SAP systems, e.g. updating prices. 

We use it for a lot of small tasks, like downloading something from an particular internal website (e.g., SharePoint in Office 365) and uploading it back, or for doing modifications, then loading them back.

We use it in a very large way across the company. Last year, we implemented approximately 22 processes and saved close to 80,000 hours total. This year, we have already saved close to 6000 hours. 

You don't need to know coding, as it's pretty straightforward. The graphical user interface is easy to use. It is drag and drop. You do need to understand the basics of what's happening, what you're doing, and how the technical things work. However, after a short bit of training, you can start doing stuff, and the more you learn, the better you become. 

There are so many workarounds. It allows you to do complicated things in such an easy way. UiPath has provided so many APIs that make it easy to interact with other databases or applications without even going into them. If I want to download something from a website, then I don't need to necessarily go into it, I can use the API function, which is very cool.

With Excel applications, it is not able to handle a lot of pop ups. It should be able to do this automatically. We just change the format of the file from XLSX to XLS, but it should be able to handle this automatically. Instead, when something pops up, it gets stuck there. This type of thing are small, but still the process gets stuck. I would like to see better integration of applications to avoid these issues.

We are also making a lot of manual changes in SAP. We are looking for a solution where we don't have to make manual corrections every time, similar to what UiPath did with some SharePoint websites.

Less than one year.

The product is definitely reliable. It gets the job done. The difference is in how you design it. When you start as a developer, you tend to always take the longest route as part of the learning process. Once you get used to the product, you realize something can be done in two steps instead of five.

A lot of people rely on what I design, so if it doesn't work, I immediately get a call that 50 people are waiting for something. This happens, but rarely, as it works perfectly.

Whenever we get stuck on something and are not able to proceed, then we get in touch with UiPath, who will help us out. Their technical support staff is pretty good. These things really help the user out.

Initially, I used the UiPath Academy when I didn't know anything. At that time, I went through the basic training, then I had to leave the academy to focus on automating our company standard products, like SAP.

I have been working with this solution for 11 months. I did not know about this solution before working as an RPA Developer. Now, you can challenge me on anything UiPath related, and I will find a solution. It is so easy to learn new things. It has good usability.

We are using UiPath to automate our cache application and to download documents to help our finance team.

We're saving a lot of time for all our associates in our company. As far as metrics go, each project that we complete is saving us on the order of 40 hours a month, so it's saving a lot of time.

It also allows our associates to do things that are more interesting, instead of having so much repetition in their jobs.

In addition, we've seen performance benefits because it removes the human error portion of running a process. It makes it easier for the owners of the process because they don't have to worry if they've made a mistake. They also don't have to look something up because the RPA would have everything for them, ready to go. Performance has improved a lot, as well.

I like that it's very flexible, so we can design our automation the way we need to. Some other RPA tools don't really allow us to use all the applications that for our team.

It's also very easy to use. There is a lot of drag-and-drop. There are many different ways to complete a solution. For example, if we're trying to manipulate Excel data, sometimes one solution will be really slow and ineffective, but UiPath gives us the ability to find multiple ways to do the same thing and complete the same solution much more quickly.

There are a lot of solutions in UiPath where we have to know some programming languages. I'd like to cut some of that out, with features that perform those tasks without having to know programming languages. I work a lot with my team members who don't really know programming that well, and I have to walk them through how to do different coding things to effectively develop their RPA.

It can be complicated to get a stable solution, but once you're over that learning curve, it's very easy. At first, it's complicated to figure out how to get a stable solution using UiPath.

We're constantly having to use our solutions on multiple servers and expand to multiple teams, so we need to work a lot with IT. They support the servers and make sure the servers are a mirror of each other. If they're not a mirror, then it can be difficult using UiPath. But once they're a mirror, it's very simple to finish a solution and move it onto a different server or to a different machine, where someone else is using UiPath.

From my experience, technical support is very fast in responding. I will submit a ticket and, by the next day, they're already working the ticket and helping to find a solution, so it's been a very good experience.

We were using another tool before UiPath. The one we were using was Kofax Kapow and it uses a different style. It was very restrictive and they had to update a lot of features for us. There was a large learning curve, as well. When we started using UiPath, I felt the learning curve was smaller and we could get into it a lot easier. It was less restrictive and more versatile in what we could do with it.

When we first started learning UiPath, they gave me the project to install Orchestrator and Studio into our server environments, so that was another learning curve for me because initially, the installation of UiPath was very difficult to figure out. But they've upgraded it since then and it's much easier now. We've now sent that function to our IT teams to do.

I believe Blue Prism was also under consideration, but I was not part of that decision.

Use the forums and surround yourself with people who are technical. Use UiPath Support a lot because, if you don't have a programming background, it can be difficult to figure out how to organize your development in a stable way. If it's not stable, it's going to give you a lot of headaches trying to constantly maintain it.

For UiPath, we have about three different teams of developers in my department. Each team supports a different group in that department and each team consists of about three developers. In terms of maintenance, we're maintaining our jobs. Once we deploy a solution, we're currently maintaining it ourselves. Whoever develops the project makes sure that it's working, but we're also looking at other solutions for maintenance where we would give it to another team. All they would do is make sure the robots are running.

We've used UiPath RPA Academy training and it's a very good tool to figure out how well you know UiPath. I wouldn't use it as something to learn the tool, because there is a lot more in UiPath than is in Academy. But I like Academy because it confirms what I've learned is the way it's supposed to work. It gives you a good basic foundation.

I would rate UiPath as a ten out of ten. I think it's the best RPA tool out there, although I have not used the other one that people talk about, which is Blue Prism. From what I can tell, they're about equal, but my experience is with UiPath and I like it a lot.

I currently work for a data center company serving real estate clients. Our primary use case for UiPath involves large-scale automation using Document Understanding to process invoices. 

I have two models running. One is for our general invoices, including everything we pay for people coming on-site at all data centers worldwide. There's a separate model for utilities. Accuracy in our utilities spending is crucial for our data center business, where power costs are passed on to customers. 

Currently, we still use traditional machine learning from when we initially developed these models three years ago. However, we are creating a company strategy to implement GenAI and deal with the legal implications. GenAI is something we're considering as an enhancement to our document processing and data collection. We're still trying to figure out how that happened. We're figuring out which documents and data to include in an internal model and draw conclusions from. 

When working with data, our top priority is ensuring that the data is updated, accurate, and well-maintained. There's a structure involved because a ton of our information is in SharePoint, which is a mess. We have two SharePoint sites for every employee.

Some large-scale invoice-related tasks were overwhelming our existing processes and attempts to handle them manually. We are in the data center industry and dealing with all these technology companies, but many processes in the real estate business are a bit more outdated. Many of our people are comfortable working in Excel, and some teams are highly siloed.  One significant challenge I've faced as a UiPath developer is acting as an evangelist within the company.  We want to demonstrate the platform's capabilities and get buy-in from these different teams across the enterprise to raise the level of what we're trying to do. 

UiPath has been helpful with that first step of getting the information off the invoice. I've been learning and expanding my skill set on the workflow side. Many of our automations have a workflow with a human in the loop doing manual review. I look forward to automating between different departments, and that's one thing I want to develop at this conference.

We used to bring on seasonal contractors during peak seasons, and now we no longer need to do that because the existing staff have more capability. That was a big thing when we started. Our accounting team was so busy for the two weeks before and the one week after closing. There was a tiny window when they could engage with any process improvement or look ahead at what we could change because they were so busy keeping up with how things work. We've freed up these people who are intimately familiar with our business and give them more time to apply that knowledge instead of filling out forms. 

We were processing about 2,000 invoices a month when I started. Now we're up to about three thousand. It took about 15 minutes per invoice to process because there were so many different elements. Working with Yardi is challenging. There was a big issue with getting these into Yardi and uploading them in batches. If one invoice in the batch failed, it would kick them all out. We spent all this extra effort troubleshooting and doing all of this. 

Now, the bot can execute this work and upload them individually. If there's a single error, it can be isolated and kicked out as an exception. Someone can manually review it, and the bot can keep putting the rest of the invoices into the system. We've also had a great ROI on the monthly reporting. We generated reports from around 50 sites every week and then distributed them to a long list of different people on different projects. It's straightforward to do and only requires 10 clicks for each report, but it saves massive amounts of time for people. Now, all I need to do is maintain a list of who should get the emails and what projects need reports to run. 

I love developing automations. I often directly help people by improving the part of their job that is time-consuming and dull. In addition to saving time, we reduce errors caused by manually typing things in. I've demonstrated that in different departments at our company.

We won an award for our ESG efforts. I developed an automation to help us report our ESG metrics because all of these customers want reports to give their shareholders about green initiatives. We wanted to take all the data on energy reductions in data centers and distribute it to each of our customers. We had a very complex template that we wanted to iterate on until we delivered the report. I developed a bot that could generate the source data and template of these files for our customers by data center and aggregate them. 

Before I joined the company, they had no automation solution. They tried to do this with mail merge, which struggled because of the variability across our sites. We wanted to achieve greater complexity and offer this table of information when it's available or update it when the final file we're generating varies significantly. We wanted to be able to convert a Word doc into PDF format and aggregate all of those different PDFs at the site level and aggregate those per customer. 

UiPath's Object Repository was huge. I could build these libraries because our industry works with many of the same systems. It's hard to integrate with Yardi's core CRM, and many of our automation efforts focus on getting information in and out of that system. The ability to build these libraries of reusable selectors has dramatically benefited me over the past couple of years. 

I'm excited about all the new stuff around document understanding because I think that is a large area. We can continue expanding and delivering large-scale automations.

The messages and alerts that Orchestrator generates are a little overwhelming. I'd like them to be filtered down to the most actionable things I need to look at. For many things, we set up an automation that will send an email summarizing things to the stakeholders for the automation. With any of these types of things, you're generating notices, emails, and things, so you want to focus on some things that need your attention. 

I started using UiPath while interning and pursuing an MBA. I've always been a huge fan of Excel, Visual Basic, and automation in general. I've been in my current role for about three and a half years, but I began tinkering with UiPath for a couple of years before that. 

I have not experienced any performance or uptime issues with UiPath.

In my current role, it's been challenging to demonstrate the need to grow and bring on more developers. We're processing a high volume of invoices, but the rest of the business has around 200 employees. We have large capital expenditures building these data centers but not a high volume of back office processes. 

I have not necessarily been able to evaluate what it would look like to grow with 20 automations. We could keep a steady pace of new smaller-scale processes and look for new large-scale opportunities, especially with some of these new technologies. However, I don't think we'll be a large enough business to need these massive deployments.

I rate UiPath support 10 out of 10. I have submitted tickets periodically for a specific issue, or when I'm trying to solve a new problem, I haven't faced before. I am the only UiPath-focused employee at my company. I can work on iterating, researching, and troubleshooting. 

 I've always been able to put in a ticket and get on a call with some people. They're able to connect me with someone and help me understand either the problem I'm facing or the fact that we've been able to have more calls recently about new potential. The online community is also an excellent resource for finding ways to approach and solve problems. Their support has been great.

Positive

Prior to UiPath, there was no different solution implemented at my current company. At a previous company, we conducted a comparison between Automation Anywhere and UiPath and opted for UiPath due to its greater flexibility, capabilities, and entry offerings. At the start of my career, UiPath was one of the first to offer free online training and a lower entry point for businesses just starting out.

Automation Anywhere followed suit. While reviewing them, I built the same process in both systems and presented it to our executives. Automation Anywhere seemed focused on the financial industry. It had some excellent features if that's what you were what you cared about, but I greatly preferred the UiPath's general flexibility, capabilities, and breadth of integration. I've done some small-scale things with Microsoft Power Automate. That tool is hard to work with. They try to make it easy for non-technical people, but it means that I have a hell of a time trying to get it to do what I want.

The initial setup was straightforward, and it was conducted in-house. We host our own virtual machines for running automations and we are a cloud customer.

The implementation was done in-house.

We've seen the greatest ROI from large-scale invoice processing, but small-scale operations have had great returns. Before automation, we were processing 3,000 invoices monthly, which took 15 minutes each. It still requires time to review them in the Action Center manually. 

UiPath's pricing and licensing have been reasonable and manageable for us. Despite challenges in constantly monitoring SharePoint folders, UiPath has worked well within our resources. We have a fully dedicated, unattended license for our invoice processing, which needs to be a top priority and is always running throughout the day. We have another one for all of our other scheduled automations, and we've been pleased with that so far.

I rate UiPath 10 out of 10. I'm incredibly impressed with the pace of new features that have come out. I have been working with UiPath for six years since I graduated college, and I'm blown away by what's coming out every year.

Our primary use case involves the democratization of software through the Sysen Lever and Power User Program. Essentially, we are trying to automate complex processes that can be easily rules-based, eliminating the need for repetitive motions.

UiPath helped relieve some of the burden related to paperwork and regulation, making people happy and excited about new opportunities.

The drag-and-drop features are useful, and having the ability to integrate technical scripting is beneficial. It speeds up development while offering additional flexibility.

Scaling efficiently and supporting people with technical information has been challenging.

We have encountered scalability issues trying to figure out how to make the operations work with different setups. My particular employee group is all remote.

I did not evaluate other options before choosing iMac.

I rate UiPath an eight out of ten.

We use the tool for robotic process automation to automate mundane business processes prone to human error.

Some of UiPath's best features are its ability to interact well with applications and its less proneness to errors. It allows us to implement end-to-end automation, which is very important for our organization since we have many time-consuming job runs.

The tool has improved our organization by reducing operational costs through process automation and cutting FTEs. We can do more regression testing for test automation, leading to better products. It's helped minimize our on-premises footprint to some extent and aided organizational restructuring.

We've used the academy courses, which are good for beginners and advanced users. UiPath has sped up digital transformation, allowing quick fixes without building entire new solutions. It reduces human errors by 60-70 percent and saves us around 2500 hours.

UiPath is pretty easy to use for small—and medium-scale automation. However, maintaining the code becomes a bit more difficult when building large-scale, enterprise-level automation. Areas for improvement include versioning for collaborative projects and reporting features currently lacking.

I have been using the product for six years. 

As for stability, I'd rate it as six out of ten. Once a project is built, we face many issues, and we often have to go back to UiPath. So, in my opinion, stability could be improved.

My company has 10-15 users. Based on my experience, I would say UiPath is a scalable solution. I'd rate its scalability around seven or eight out of ten.

The user community for UiPath is great. We can ask about any issues we have on the community forum and usually get them resolved. Regarding technical support, it's amazing that they respond quickly. However, their level one engineer could be better educated on the tool before moving to level two support.

Neutral

We previously used an open-source Java Selenium solution but switched to UiPath for better security and platform capabilities.

We have the tool deployed in the cloud version. The deployment process was straightforward—it was pretty easy, mostly just drag and drop. Because of the number of projects we have, the initial deployment took days to months.

We use UiPath in multiple locations globally, including the US and India. The solution requires maintenance, particularly from a coding perspective.

I'd estimate UiPath has helped us save around 10-15 percent in costs.

UiPath is a pretty expensive tool compared to what the market offers, including open-source alternatives that can do similar things.

Overall, I would recommend UiPath to other users. The main reasons I like it and would recommend it are that it's very user-interactive and its capabilities are really good.

On a scale from one to ten, I'd rate it overall around eight.

I have worked on multiple use cases with UiPath dealing with SAP, SharePoint, or a web application. We had to extract the data and do some automation of data processing. We were taking data from one environment, such as from an Excel sheet, and processing it. These were the use cases for which we used UiPath extensively.

In addition to app integration, there were use cases related to various frameworks such as REframework and State Machines. We used the REframework at the enterprise level to be able to handle exceptions and bot failures and make automation healthy, robust, and steady.

We have also done automation for a healthcare department for claim processing.

UiPath saves the execution time of processes running in the production. If a process was taking three to four hours previously, with UiPath automation, it can be completed within an hour with better exception handling capability and less dependency. It saves 50% time.

UiPath is capable of handling the complexities involved in taking data from different environments. It is also capable of exception handling. If any application has limited functionality, we can use UiPath for automation with that particular application. With advanced selectors and linked queries, we can get the data from the application or interact with the application.

UiPath Document Understanding has helped to reduce the data entry work and physical copies of documents.

UiPath enables us to implement end-to-end automation. For every organization, it is very important that automation is robust enough.

UiPath can help minimize your on-premises footprint. It depends on whether you plan to deploy your automation on the cloud or on-prem. On-prem has various challenges and restrictions, but it also has benefits.

UiPath speeds up digital transformation without requiring expensive or complex application upgrades, or IT application support. App integrations are advanced and robust. It is plug-and-play. You can integrate with Excel, Outlook, SharePoint, SAP, and various databases. There are pre-loaded activities. You can integrate with GitLab or GitHub. It has inbuilt activities for enterprise-level applications.

UiPath reduces human errors, but it also depends upon the process. It depends on how much interaction is required and what exception rates are there. When everything has been identified, it can reduce errors by more than 70%.

The first feature that I like is the exception-handling capability. The second feature is the REframework provided by them, and the third feature would be the Orchestrator functions. There is also the feasibility provided to monitor the ports and deploy the code. There is monitoring, retrieving, and all those things. We can use the web or mobile application. These are the key features of UiPath.

For handling complex scenarios, REframework is good. It has good exception handling and in-built mechanisms.

The certification can be made more affordable.

In terms of features, we get regular updates, and AI has recently been integrated. As of now, I do not have an area of improvement. They have already improved the functionality of Orchestrator. As compared to two or three years ago, Orchestrator now offers different functionalities and services. There is a difference, and it has improved.

I have been using UiPath for more than three years.

It is stable. Our organization has licenses because we cannot upgrade the application in sync with the Community version. The enterprise has to stick to one version for a certain period or whatever tenure has been mentioned in the license. The Community version is the playground for UiPath. They upgrade it, and all the beta version updates are there. They come to know how things are going and what are the responses and challenges.

It is scalable. It is used in multiple departments. The size of the organizations that use UiPath varies. They could be MNCs or startups.

Their support is good. After procuring the licenses, when there is an issue, there is a dedicated support team. They respond well.

The UiPath Community is vast. It provides an opportunity to get help from others. They provide good support, and the MVPs are actively engaged in responding to the queries that people are posting when facing any challenge. We can find relevant information by searching with keywords. It is good.

UiPath Academy has been useful in learning about new topics and new versions.

Neutral

I am quite new to Automation Anywhere, but a better exception-handling mechanism and the ability to interact with various applications make UiPath more unique. The drag-and-drop interface is attractive to people who are not very technical. The user experience is more intuitive.

We have on-premises and cloud deployments. The deployment part takes about a week because we have to prepare the production environment. A week is good enough for the deployment.

The number of people involved in the deployment varies. Support teams are there. Developers are also there. There are also people from the change management team.

Like any other software, it requires maintenance.

I would recommend UiPath to others. Overall, I would rate UiPath a nine out of ten. It is robust and scalable, but there is always scope for improvement.

The use cases are quite broad.  UiPath is used in customer contact centers, supply chain management, operations, etc. It is useful for the intelligent automation of task-oriented processes.

It's easy to sell clients on a cloud-based solution like UiPath because it's the easiest to maintain and run. Some of the customers have already adopted a cloud-first strategy, so it's crucial for them not to have to operate their own data center. Others need to have a data center for privacy reasons. 

The solution helps customers reduce costs by about 20 percent. UiPath doesn't require any expensive or complex application upgrades. It has reduced human error. UiPath has improved outcomes like SLAs and customer satisfaction scores while reducing wasted time. 

UiPath frees up employee time, but the exact amount varies from client to client. It depends on your scope and your use case. You can obviously save time. It depends on how you design the process or whether you're automating one process or 10. 

I appreciate the stability of the UI automation, the studio, and the development environment. I also like the platform's rich capabilities. Stability and performance are always essential when automating through the user interface. This is what they definitely bring to the table. 

Regarding the ease of building automations, I would rate UiPath nine out of 10. It's the best tool in the marketplace. It's easy to build automations, and the interface is easy to use. I like how it integrates with the Orchestrator and everything works together. There are so many different use cases that we can easily connect through APIs, databases, and user interfaces to automate all kinds of applications. 

UiPath's end-to-end automation is critical. It's the most efficient way to automate. You automate mundane tasks so that people can focus on everything that requires expert skills or knowledge. 

The solution's user community is amazing. There's a lot of knowledge and experience, and it's easy to access that information. It's a highly active community. The UiPath Academy also has some attractive content that gives you hands-on experience with the product. The courses are easy to follow. 

I have been using UiPath for about three years. 

Excellent stability.

UiPath's scalability is excellent. 

I have had limited contact with UiPath support, which says something about the product. 

I have used Automation Anywhere and UiPath. I've looked at other options, but UiPath is at the high end.

Deploying UiPath is straightforward. It's fast. You can deploy UiPath in five minutes depending on what you need and how everything is configured up front. You need to get a platform account and set up the machines that will be part of the solution. You also need to set up users and assign them licenses. UiPath requires some maintenance based on the types of packages you're running. One person can do it. It isn't too complex. 

UiPath is relatively expensive. However, it's the leading product because it has so many capabilities. 

I rate UiPath 9 out of 10. When implementing, I recommend sketching out your costs over multiple use cases and comparing them to an alternative solution.