UiPath Reviews

RPA overall is about routine, mundane, structured tasks. We use a number of them at my client's work in terms of how do we do back office reporting for general deliverables, contract compliance, etc. 

We had a few different reports that we had to do every month. We have to hand-jam them into a very poorly-formatted database which had weird drop-downs. Instead of entering them manually, and spending a day or month just punching in titles and numbers, we compile it onto an Excel sheet and have a bot run and dump all that information. 

All I have to do is tweak what information has changed from month to month. This has made my life a lot easier.

When I was first introduced to UiPath, I stated that I am very adamantly not a coder. I hate code, lines, and missing that semicolon somewhere in there. Being able to understand that your path is structured as a process flow, you are still able to declare variables, and ensure the background logic is sound. You are also able to really visualize what the process needs to do and the paths that it needs to take: true, false, etc. So, it has been very useful in terms of crafting it.

To exceed the expectations, it needs to be easy to debug, not only easy to craft. You need to be able to make it truly do what you want it to do. As a user, you have an idea of what you want it to do. However, when you hit run, it doesn't always do it, then you have to figure out why. That ends up being the majority of your development time. UiPath does pose a bit of a challenge in terms of easy to understand errors, where it's getting stuck, or what was the logic behind the process that we were trying to do from a UiPath standpoint. Making improvements to these would help out a more in terms of being able to make it more user-friendly.

Looking to go from structured to unstructured data, then UiPath needs to be able to handle understanding natural language and scanning of documents which are not well-written or visible, in terms scanning quality. These are probably the easiest target areas to improve on first.

If I'm using it as an attended bot, it's pretty stable. When you discussing unattended bots, anything could go wrong in the entire stack. We have found times, if I run UiPath for a week, and it needs to simply loop a PowerPoint presentation, come back in a week, then sometimes the PowerPoint will be dead. It is harder to understand if it was UiPath's fault or if it was because the device decided to do a random Windows update and restart itself. It could be a litany reasons, but even then, I can't be 100% confident that the unattended bot is going to run forever.

It would have been hard to set up without some basic training and basic use cases to practice through first. After some familiarity with the product, it is not hard to set up.

We have seen ROI across the board.

It has limited human errors within the confines of how bots were constructed on what we needed them to do.

My specific process that I use it on went from a day to about 15 minutes (time savings).

All the RPA tools are good for different things. For my very simple process, I didn't go with Automation Anywhere because setting up the Orchestrator and turning on the server is a pain. I have had any experience dealing with Blue Prism.

The primary use case of UiPath, with every organization that I've worked with as a consultant, has been to make business processes more efficient and the work of their employees more enjoyable. 

By utilizing this technology, you're able to get value through your value streams quicker. When you realize value, that means you can work with your customers more quickly, as well as build customer loyalty and employer loyalty. These have definitely been some of the byproducts of using the software.

When I was working as an RPA manager, managing a program for an insurance company which supported insurance lifecycle processing, one of the components was that they had to review insurance policies annually. It was very cumbersome. We were talking anywhere from 10,000 to 40,000 daily. It was almost a 20-FTE process. We were able to automate that completely.

However, the real value came when the organization understood how to apply RPA and it actually began creating brand-new business processes specifically for RPA. So instead of hiring new people, they said, "Hey, we've always wanted to do this, we don't have the budget to bring on and train people, so let's build bots to do it from day zero." Once they were able to understand that I could do more than just automate processes, that I could build new business lines with bots, that was an incredibly valuable result of using this software.

The benefits are very high when you automate business processes. Before using RPA, I was working in technology, building macros and things of that nature. But the way we're able to build sustainable, functional bots that really work well in the long-term makes the benefit a ten out of ten.

This is going to be an interesting answer, but the most valuable feature of the software is not the software itself, but the community that supports it. When I first started learning the software to support a program, I had to self-teach; there wasn't a budget for training. But going through their learning platform and then connecting with the community when I didn't understand how to utilize some of the functionality, that was far more powerful than the product itself. The network around the product is amazing.

The great thing about the UiPath RPA Academy is that it's not stagnant. Even though my first go at getting certified as a developer was three years ago, I literally have to go back the Academy and learn it every year because there are new features and new functionality. An example is the RE Framework they've incorporated. The living nature of the Academy gives a lot of value. But hands-down, the way that they give practical exercises, the fact that they give you applications you can download to learn how to interact with bots by simulating an actual operational environment, makes it a very impactful learning experience.

In addition, I find the solution easy to use. I have personal experience using all three of the major software vendors that are in this space right now, including Automation Anywhere and Blue Prism, and I would put UiPath as number-one, specifically from a learning perspective. I've been able to take people with absolutely zero technical background and quickly scale them up in a matter of weeks so they're building bots. I haven't been able to accomplish that same feat with the other platforms.

Being a person who has held every RPA role from developer to analyst, architect, and executive, one feature I think it needs - from a documentation perspective - is the ability to easily extract variable details and data. They do have a Variables panel that you frequently interact with, but I constantly have situations where those need to be adjusted or I want to be able to present those to a business. Sometimes it's difficult to extract those, and if you're not tracking them while you build, you can quickly get into 200 to 300 variables in use, especially using the RE Framework where you're passing workflow arguments in and out. I would like to see something like that.

In addition - and obviously UiPath is aware of this - we have to continue to improve the OCR capability. Computer Vision is excellent. I've used it on Azure. I've created PeopleSoft environments and worked through the Computer Vision feature. It works amazingly in a Citrix environment. But I speak with multiple organizations and a lot of them have the same problem of processing documentation from the mail room or from vendors, etc. That's a huge component. If we can get that embedded in UiPath, so we don't have to rely solely on OCR vendors like Captiva or ABBYY, that would be a huge step forward in being able to service all organizations.

There could be improved logging and functionality. But if you truly understand the software, adding logging to what the bot is already doing is as simple as typing on the right line. It's incredibly easy and you can embed it. Even though what it currently logs is limited, it's easy enough to create logs or reporting without a lot of effort.

Outside of that, it's really hard to come up with other recommendations. The software is solid.

I was recently reading about the document processing framework that they just implemented. I gave a demo two weeks ago on the Computer Vision functionality that was in beta. So the sustainability is there. They're focused not on just how good RPA is and on making it better, but they're also integrating it with future-tech. That is where the stability comes in.

UiPath's scalability and stability are exceptional. They are constantly releasing new versions.

Scalability is all in the delivery. I've definitely run into multiple organizational roadblocks with my clients because they get six months down their delivery timeline and they're not meeting their OI, they're not scaling. That generally comes down to how it's being delivered. If you have experience, you're working with a partner, you're working with people who have used this solution at scale, you can generally bypass a lot of those roadblocks. It's definitely scalable if you have the right expertise.

I have used both technical and customer support. When I was going through training, trying to learn some of the software, I had issues when I finally purchased licenses. The issues were related to putting them in Orchestrator and installing them. Support was definitely very supportive, very responsive when trying to get feedback.

Even when it comes to the community, as well, if you're just trying to learn the software, to learn the features and functionality, the community network is there to quickly respond and support you so you can get back to getting value, instead of getting hung up on one piece of functionality.

I have seen cases where an organization moves from a different automation solution to UiPath. At one point, we were transitioning from Automation Anywhere. There were very basic bots, these weren't complex processes, but we built a bot in UiPath that read the XAML of the Automation Anywhere script, converted it into activities in UiPath, and built a bot. We had a bot that builds a bot.

An example of why people move to UiPath is that when I was the director of RPA for a finance company, when I set up the program I had to go to EVP and pitch the prices and the costs. When I gave him the cost for all the software, to bring a vendor on, he told me "no." It was way too expensive. But UiPath has this amazing option called the Community Edition. What I was able to do was download the software, teach myself how to use it in about 45 days and, within two months, I had automated a pilot process, completely on my own. I was able to walk it into the EVP and say, "Look what I was able to complete. You told me no money, no funding, but now can I get funding?" Then I got funding and was able to bring on a team. That's one perfect example. They said "no," so I got a free version that cost me nothing.

In terms of how companies know that they need to invest in automation, in this day and age, with the speed at which information and technology move, it's at the point where this is not a new topic. A lot of organizations, through word-of-mouth, internet searches, or conferences, or events such UiPath 2019 here in DC, realize it as soon as they hear the success stories. It's impossible to ignore. Most organizations are like that. They hear about it, they realize that it's something they should consider, it's something they have to do, and they take the next step.

The initial setup is absolutely straightforward; it provides a quick and easy installation. Given that you may have to go through some technical hurdles to get permission to download it, I'm not talking about that. But if you have all the permissions and you're allowed to download and install it, it's absolutely simple. It shouldn't take more than ten minutes.

Technical prerequisites are not needed to use the software, but technical resources can speed up the ease with which you deploy. Given that you're generally not interacting with UiPath in isolation but with other business applications as well, you want to make sure that there's technical support in case you have some issues. Or, if there's something that you didn't experience in UAT but that comes up once you get into production, it's good to have some additional support. It's not a requirement but I would recommend it.

ROI is one of the most frequent questions I get from organizations. You should be seeing ROI in less than six months. If you're not returning your cost and more, from a licensing and personnel standpoint, in the first six months, then it is not a software issue and it is not a delivery issue. In that case, it is a scoping issue. You're probably looking at processes that shouldn't have been automated in the first place.

Every organization that is successful with the software is reaching their ROI in six months or under.

The amount of time saved with bots is an interesting question but it's hard to answer with a pinpoint response because it depends on an organization's strategy. I've seen multiple organizations that use attended bots, so they're just saving a fraction of the time. But then I've been in organizations where they've automated a process end-to-end. A process that previously required 20 FTEs went from having 40,000 hours of manual work to zero.

For pricing there is a variable at play, and that's scale. Depending on how you want to scale - whether working with a partner or directly with UiPath - there's a specific cost per license. But then it's all about optimizing a process, and what we call "license utilization." We try to maximize each license, and we'll have it running three or four processes.

The cost is nothing, it's peanuts, when you see the capabilities. When you're talking about one license supporting what was previously done by 14 people, what is $1,500, or whatever the licensing cost is for unattended bots?

Even more importantly, as a technology expert, I know that I could do some additional coding and automate the running of the bots. But why would I spend that extra time when they have Orchestrator. I could have a person running them as well, but the Orchestrator license is far cheaper than a resource; just click "run." When you compare the results that you get, the price is a moot point.

If I was going to give any advice to someone who was just about to utilize the software, I would say that the most successful organizations that apply this technology make it an entire team effort. It's not started in one business unit. And if it is, it's socialized across the enterprise. That's the quickest way to scale: getting everybody onboard. The second-biggest thing is that the most impactful projects you will get will come from your people, your internal workers. And until you get them to understand what the software can do and its capabilities, it's going to take you longer to scale your program. So make sure everybody's socialized, and make sure everybody truly understands what the software can truly do. They're going to give you the best opportunities to benefit from it.

Deployment should definitely be done using the support of experts. Even when I owned my own RPA program, and I wasn't in a consulting capacity, I still reached out to a third-party to get support. While setting it up is something that you can do internally, given that most objectives include speed-to-market and quick scaling - wanting to see results in 60 days instead of six months - it's going to be very difficult to do alone, especially if your goal is to have 100 bots in a year. If your goal is ten, you can probably manage it. It's important to use experts if you are looking to rapidly scale.

I have implemented UiPath in virtual environments, including on-prem, Azure VMs and servers, SQL-based data storage, as well as AWS. I've never had any issues with the responsiveness or the application having any problems operating. The biggest consideration that you have when trying to deploy robots in a virtual environment is making sure that your architecture is sound. You have to integrate through severs and you have to take into consideration firewall updates. And then there's interacting from the cloud if your applications are on-prem. You have to make sure that the bot doesn't have any issues. But if your architecture is solid and your infrastructure is set to support the applications in a cloud environment, there shouldn't be any issues. You wouldn't notice any difference compared to having them on a desktop on-premise.

I would agree that UiPath eliminates human error, but I would add the caveat that good code eliminates human error. I've been doing this for a while and I've seen bots that mess up. It's in your delivery methodology. If you have a sound delivery methodology - you're going through a rigorous UAT cycle and are having outputs audited by the subject matter experts - you should literally get to zero errors. Maybe you will have five percent exception cases, but your error percentage should be zero.

Having worked with all the tools, they all have little niche components. As long as UiPath continues to focus on knowing what the next wave of technology is that businesses really need to use to be efficient, and they start embedding that skillset in their software, that's all you could ask for. They need to stay in front of the power curve of technology, which is impossible, but they're trying.

I've never had a bad issue with UiPath. My experience with them has always been pleasant and engaging. They're never stuck at just giving you software, showing you how to use it, and then walking out. They're always focused on improving your business. If you focus on that, and focus on generating value, you can't lose.

Automation technology is the number-one driver across an organization now. Trying to find ways to do more with less has been the going mantra for organizations for years now. It's no longer feasible to simply run operational efficiency or Six Sigma projects to try to get gains. The only way that you're going to get significant gains is going with an automation-first approach. That's where I see a lot of organizations headed, even spending more on RPA software than on cloud implementation. It's a very big focus, and I don't see that slowing down any time soon.

On a scale from one to ten, I would you rate UiPath as an eleven. It's excellent software.

When it comes to finance and HR services the product has great potential. Our company is big, so there are a lot of opportunities.

We are doing automation internally for financial processes.

Externally, for our customers, we are developing a shared service center. This is not restrained to any one specific area, like HR or finance. Anything that is manually or taking a lot of human effort, we try to automate (by selling it to our customers).

The Unattended Robots are good and handy. If you have the proper team and environment available, especially a team who is experienced and knows how to develop with a sense of excellence, then a lot of tasks can be done outside office hours. Then, the next day, teams can come in and have the information that they need readily available.

UiPath needs to improve Orchestrator and its back office licenses. For example, three or four people logging in on a license should be able to get in, but they can't, even though its Unattended.

Why can't we just increase the capacity of the VDIs, so we can use capacity that is there?

Stability depends on the type of structure that you are putting in place. I think it is important that you run 16GB, with not more than three or four processors in parallel.

If I need something, I go to my account managers, who are nice people. They respond back quickly and get back with a lot good options, which I like. 

My development team does connect with the technical teams. The feedback, which I receive from them, is very good. There have been instances, which we have highlighted and identified something, then the UiPath technical team accepted it, said whether they would fix it in the next release, then fixed it if needed.

The UiPath Academy is fantastic and amazing. I'm a big promoter of it in my discussions with customers.

When it comes to Studio, it is an easy solution to install. Anyone can go download and install it. Though, I'm not sure if just any company can install it, because you need to have permissions from IT in order to install it on your computer.

When it comes to Orchestrator, you need an approved structure from IT security. There are associated firewalls that have to be installed with your IT partner's help. Then, it is quite straightforward.

UiPath helped us with the installation.

It is not easy to see ROI quickly. 

It is not a cheap solution. There is an annual licensing cost for all the components.

When it comes to back office licenses, why can't we have parallel processors running on one back office license? I understand the commercial aspect, but when you have servers and a node locked license, you should be able to use the license from different instances.

UiPath is quite a customer-centric company.

Most of the time, I am a developer. I also have to develop some best practices, but a lot of the time, I'm working on the application and creating Unattended Robots. We have a large amount of old school manual processes which we need to automate, because we have a lot of full-time employees just doing boring stuff. 

I started last year, so I am a bit fresh in the organization. We have two people: One who analyzes and other develops.

I am using version 2018.4, which I find easy to use. We can see some major changes with each version. The IT department sort of hates that I come by every quarter of a year and want an upgrade, but it is very much worth it. There is a lot of stuff happening out there, and it's dangerous to be left behind by a few versions. 

We have a few people who are very happy to be relieved of their (almost) full-time job of processing customer applications, then processing those applications further along into the company and having that be their full time job. Now, these employees are able to do some more enlightening stuff.

The automation technology is mainly in the financial involvement. We also supply a lot of the power for users. We have a lot of documents which have to be signed and processed, and in those areas, it's nice to have automation and easy to see the benefits.

The seamless integration with programming underneath, so if you choose to, you can get a bit technical with stuff. If there is something missing, you can make it yourself. 

The increasing amount of possibilities in Orchestrator to control robots and schedule them, with the possibly of a dynamic schedule in the future. In addition, there is API access to Orchestrator.

I've seen the roadmap. It looks like some of my wishes are in there, such as the debugging of the last X amount of savings before the robot fails. 

I would also like more script access to the flow of activity, so we can try to see a text version of what we have in the user interface.

Most of the time, the product boils down to making something that works by itself. 

I haven't encountered any real issues with the stability of the product. It is hard to evaluate since it works through so many systems.

We haven't had that many scalability questions arise yet, because we are still in the process of getting people to adopt this new technology. I have looked at the features, and it looks promising.

We have a plan for licensed upgrades, which is a straightforward, easy procedure. This is based on our knowledge from migrations of earlier versions.

We started out by going through the few basic certifications which were in the UiPath Academy a year ago, though there are more now. Even though my coworker is not a developer, he just wanted to have insight into how you use software, so we both did it. 

The UiPath Academy was very good. It tries to help and provides a sort of education not from where somebody is attempting to sell you something. While you are sold product, you push yourself to pass the courses to get to the juicy stuff, and it is on your own accord.

This was a new product for the company. Leadership though this was a good place to start.

The initial setup was complex, which was done by the consultants. After that, we adapted the product a bit, and it has been pretty easy.

The initial setup for our virtual environment was straightforward, as was the installation with it. Afterwards, we were up and running with our virtual machines.

We originally used a consulting company, Deloitte, but then decided that we wanted the knowledge to be in-house.

It has helped eliminate human error. Data quality is a concern, and it helps to alleviate some of our data quality issues.

It has saved the company time.

We use the performance benefits of it to make a case for future hiring of people, so I have great expectations from it. I would rate the current ROI and performance benefits as an eight out of ten.

I heard that they also evaluated Blue Prism. The leadership went with UiPath because it had more transparency, had a better cost, and was more risk-free. They decided to give UiPath a shot before deciding on a long-term solution.

Get buy-in from your leadership early on, because it's very hard to get stuff done without it.

We are only using Unattended Robots at the moment. However, we are very excited about Attended Robots getting a foothold. It is something that we want to investigate more, since Attended Robots are feasible in our organization.

We use the solution to pull documents from audit systems, download documents from document management systems, and grab data from financial management systems. 

I like UiPath's framework. It offers a modern design experience, which makes it easy to do different activities. 

The solution is expensive. 

I have been using the product for four years. 

The product is stable. 

UiPath is scalable. 

UiPath's support is great. 

Positive

UiPath's deployment within our environment is complex. However, we have online resources available. 

We have seen ROI with the tool's use. 

The tool's pricing depends on its use. It is expensive. 

Our business objective was to improve manual processes and increase efficiency. 

Task Capture helps to build documentation. 

UiPath has freed up our resources' time. 

I rate it a ten out of ten. 

I use UiPath to reduce any data entry, report generation, or anything where UiPath can help avoid human errors.

The solution is very user-friendly and easy to use. It comes with pre-built automation. The tutorials are very helpful. 

I have been working with the product for six months. 

The tool is stable. 

UiPath is scalable. 

The tool's support is helpful. 

I use UiPath to reduce human errors during report generation or data entry. Simple errors can cause delays down the stream. 

The product has helped us save hours, which can range from a few hours to tens of thousands of hours. 

UiPath has helped us increase accuracy. It is helpful in data validation. 

I rate it a ten out of ten. 

I'm using the solution for web applications and for integration.

The solution has improved our organization by improving processes, including documentation processes. We're able to increase our capabilities. We can use it to help us with large projects. Over the years, it's helped put less pressure on the server.

The integration services are quite effective. There are so many integration partners available. For example, we can use the solution with Jira.

It is easy to build automations. We use it to automate processes. We can use the product to automate good causes like sustainable production. However, we work more with web processes as opposed to good causes.

We do use it for end-to-end automation. We can ingest documentation, do a development phase and make our application. It's important to have this end-to-end capability. It helps us gain more knowledge and control.

The user community is definitely useful. If you have any issues or need something explained, you can use the community and gain more knowledge. We can share our knowledge as well. It helps clarify. It helps us interact with other humans to gain insights. 

It's helped lower our on-premises footprint. It's important to us to be able to reduce the on-prem footprint. It saves us space. It's helping us future-proof. It helps reduce limitations.

I've used the UiPath Academy courses. We can learn from ourselves, however, it does help. While we don't completely gain knowledge from the Academy, the solution requires users to go through a learning curve. It can show you the basics, and you need to go further by experimenting. I haven't used Academy courses in the last few weeks. It really does help with integrating services and understanding that aspect of the solution, however.

We plan on leveraging AI functionality. We haven't used it yet. 

It is helping with digital transformation. We can leverage architecture and different platforms much more efficiently. There are a lot of tools and upgrade versions that we need to go through right now. As we continue digital transformation, it will help make our processes more convenient and make tools easier to use.

It's reduced human error. However, the way our documentation is created, we won't be able to completely remove human interactions in the documents and can't remove human error completely.

The product has been able to free up employee time. We can build and complete a process very fast. 

We've noted cost savings when using the solution. We've been able to reduce licenses or move to community licensing.

A lot of implementation is done by UiPath, however, there are parts of the studio we've had issues with. We'd like the upgrades to be a bit easier and more flexible.

I've been using the solution for three years. 

The solution is stable. 

We have three people using the solution in our organization. 

The solution is scalable. We have a lot of applications and different scenarios. We can definitely scale as needed. 

If we have a lot of complications we can get support to troubleshoot. They have been helpful overall. 

Positive

We've also used Blue Prism and Power Automate. 

We find UiPath is easier to build on with drag-and-drop functionality.

Implementing the cloud version of the product is easy. Deployment is simple. However, it depends on your environment.

It's helpful to have some knowledge of UiPath. You only need two to three people to maintain the solution. If it's the first time setting it up, it may require more people.   

We do the deployment ourselves. 

I have witnessed an ROI. We've noted cost savings after implementations. 

The pricing can be a bit high. For single attempts at automation, it may be too pricey for a normal person. If you are doing a lot of automation, it's more affordable. 

I'm an end-user.

I'd recommend that users implement the solution. It's important to implement it correctly in the organization, however. The technology is far easier to use than other technologies in terms of reducing manual interventions in processes.

I would rate the solution ten out of ten.

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.