UiPath Platform Reviews

We are primarily automating business processes from SAP applications and a few from a web-based application. 

UiPath reduces the number of human employees needed to do repetitive tasks. A person can only work during normal business hours, whereas a bot can work 24/7 without making mistakes.

UiPath is user-friendly. Building automations isn't complex, and it doesn't take many days to learn. If you have basic knowledge of any programming language, you can start building small projects in 30 to 45 days. 

If it is a fixed process instead of a dynamic process, we can do end-to-end automation. Automating this kind of process is easier. If it's a dynamic process, we need some kind of external integration. 

UiPath's community forums were helpful in my early stages, when I was learning the product. When I got errors, I was sometimes unsure what they meant, so I could go onto the forum and find answers easily. 

They also have these UiPath Academy courses. I've taken the foundational course and the advanced courses on Document Understanding and data manipulation. I still haven't had a chance to work on Document Understanding, but the data manipulation course has been helpful. I learned to do some queries that simplify the workflow and make it faster. 

I have fewer issues with the user interface when I'm using Blue Prism or Automation Anywhere. For example, if you want to perform an action in  UiPath, it's a little tricky because you must click on a particular icon. When you click on that, some selectors are generated. That will change whenever the application updates, so you must change the selector again after the update. When we are dealing with Automation Anywhere, we'll not get any selectors if we are using that action once. 

I have used UiPath for more than two years. 

I had an activity crash once when the permissions failed. When we were using that activity, it automatically created multiple activities. Even though we dragged it and used it only once, it created multiple activities. That only happened once.

I have tried Blue Prism and Automation Anywhere. 

UiPath is deployed on-premises. We only needed to download UiPath Studio off the website and install it. It took about 30 minutes. 

I rate UiPath eight out of ten. I recommend taking the UiPath Academy courses first. Take the foundational course. It has some hands-on exercises with small automation processes. Later, they can complete the advanced course. 

We're a tech consulting company that works for insurance companies. We use UiPath for tasks related to payment processing, deductibles, and denial of coverage. We check each part of the process to ensure that the patient has met a set of criteria. We're checking the deductible to see if it has been met, and we update the notes on the platform. UiPath is useful for all of our clients regardless of the industry. For example, we have used it for payroll and payment processing at Citibank and Doshi Bank. 

A bot can run 24/7, reducing the human labor required. That is UiPath's major advantage. It reduces the number of manual tasks while also improving and enhancing human labor. A manual task that took 10 minutes in the past can be completed in two or three. We are saving a lot of time. 

Let's say we have eight people doing a particular task eight hours a day on a five-day work schedule. Once we automate that task, we can run the bot 24 hours a day Monday to Sunday. Automation reduces our costs and human error. The accuracy and data security are high. It's beneficial all around.

Uipath facilitates data sharing between systems. We have some shared folder packs that enable us to share the data from one system to another. This functionality can be important, depending on the project and type of data. We use some encrypted features. If we want to share data in encrypted mode, we can put it in an Orchestrator folder on-premises so only those with access can see the data. 

The business will share the data, including employee and patient records. All the data is shared within the database.  Either the employees can send data over, or they can access the data from that particular folder. UiPath offers a central portal for managing patient information. We've done a lot of things to extract and utilize patient information, ensuring that it can be accessed by the appropriate teams. We have to train our bots to capture the right information, like the patient's name, address, ID, location, etc.

UiPath is good for data scraping and extracting information from websites. UiPath is approachable, and it makes life much easier by automating repetitive tasks with the help of drag-and-drop flexibility, eliminating human interaction. The drag-and-drop APIs make it easy to get data from the API quickly.

I also like UiPath's security features because it gives us lots of tools to secure sensitive information. We can encrypt the customer data and store it in UiPath on-premises. We can also control access so that only authenticated users can obtain the data. 

Citrix and email automation could be improved. We can use the features, but the accuracy isn't 100 percent. 

I have used UiPath for the past five years. 

I rate UiPath support eight out of 10. They provide us with assistance while we are developing bots. We can send the Orchestrator logs to UiPath to find out where a process is failing. For example, a web-based process might be using an old particular password. The support team will notify us that we need to update the password in the production environment. 

Positive

Before we implemented UiPath, we tried Automation Anywhere. I like UiPath the best because it has capabilities like Document Understanding, AI, fabric, etc. UiPath has more features than Automation Anywhere. When we did a POC of Automation Anywhere, we found that the data scraping wasn't as accurate when working with PDFs. 

The deployment may be straightforward or complex, depending on the project. Before each project, we have a testing phase of about seven to eight days. We have a 10-day monitoring period. In that 10-day period, the developer is also involved with the support. We have a different support team that takes care of most of these things, like deployment and monitoring the processes. If something goes wrong, they have to open a ticket and reach out to the developers. 

Our implementation process involves checking all the business requirements. We look at the software and machines our clients use and the steps involved. Once we know the business requirements, we start working on the modules. We determine how many modules we need and the amount of time it will take to develop them. 

After that, we have a daily scrum call. If we have issues, we reach out to the business, and they will come back with a solution. We need to undergo this initial development phase before starting anything. Once the development is completed, we have multiple process design documents detailing the processes and steps. We also work with third-party integrators. About seven or eight staff members are involved. 

This solution does not require much maintenance once it is deployed and we've granted the access required. Once we've ensured the process is running and done the initial updates, we don't need to maintain it.

I haven't calculated the ROI, but I've heard that other people have seen 60 to 70 percent return on what they invested.

The pricing depends on the project and how many hours we will charge. 

I rate UiPath nine out of 10. There are still a few areas that require improvement. Before implementing, I suggest doing a POC so you can evaluate other tools side by side to see which one is best. 

We are a partner of UiPath and a system integrator for our clients.

For most clients, we tend to begin by focusing on areas with the highest potential for automation. This typically includes finance, procurement, or HR functions, with the first two being the most common choices. These areas are chosen because their processes are generally stable and repetitive, making them ideal starting points for RPA implementation.

However, our experience doesn't end with just one client. We've had numerous engagements, including with large, multi-company groups. Once one division like the "glass division" successfully implemented RPA, it often sparked interest in other divisions like the pharmaceutical division. Demonstrating a solid proof of concept makes it easier to scale the technology to diverse use cases across the organization.

Ultimately, overcoming the initial hesitation and showcasing the tool's benefits is crucial. Once the value becomes apparent, a shift often occurs, transitioning from a client-driven demand to a proactive push from various departments eager to eliminate tedious manual tasks.

While we haven't encountered any major technical roadblocks, understanding the potential for automation has been the primary challenge for users. Initially, we also faced some learning curve hurdles during the first few projects. However, as our internal expertise matured, approximately 80 to 90 percent of use cases have been implemented smoothly with minimal or no support from UiPath. It's clear that effectively identifying tasks suitable for automation versus those requiring human intervention has been the key hurdle. From a purely technical standpoint, the capabilities have been readily achievable.

While UiPath facilitates end-to-end automation, its feasibility heavily relies on the specific use case and associated tuning costs. The decision to automate isn't solely driven by cost reduction, but also by the number of tedious tasks it can alleviate for employees. Clients are often eager to free their workforce from such repetitive drudgery, especially if the task is long-standing and well-defined. In these scenarios, full automation often presents a compelling value proposition.

The UiPath user community exists on two levels. First, there's the general UiPath user community, managed by UiPath itself. This broader community offers a valuable resource for learning, sharing experiences, and finding solutions. Second, once a UiPath instance is set up within a specific client's environment, a smaller user community emerges within that client's organization. While this internal community may seem less significant, its role in supporting individual users in tackling automation challenges is crucial. By sharing their experiences and overcoming difficulties, these internal user communities can act as "roll cages" for individual functions, providing guidance and support regardless of the specific challenges encountered.

Initially, our focus was solely on on-premise solutions. In fact, up until last year, I hadn't encountered a single client who had implemented their RPA solution on the cloud. This was primarily because we catered to a mainly small business clientele. However, the landscape has shifted significantly, with more and more cloud-native solutions emerging. This shift has been driven, in part, by the cost-effectiveness of cloud-based options. One of the major roadblocks to cloud adoption in the past was the pricing of the orchestrator. While it might be suitable for supporting large client bases with thousands of users, it wasn't cost-effective for smaller businesses with only 100-200 users. Fortunately, UiPath has introduced a new approach, allowing us to purchase orchestrator instances tailored to specific user base needs. This, combined with the inherent benefits of a cloud-based platform, has made the cloud a much more attractive option compared to 2019. In conclusion, cloud computing is now a critical factor in the RPA landscape, and the adoption of cloud-based solutions has become significantly easier. This shift has opened up new opportunities for businesses of all sizes to leverage the benefits of RPA technology.

We started with five or six people trained online by UiPath and the different certification programs available in the UiPath Academy courses were helpful.

UiPath has helped to drastically reduce human error to almost zero by automating all the structured data that used to be done manually by people. This has improved the quality of work for our clients.

UiPath has helped free up employee time. Previously, we analyzed each potential use case to determine its priority. Before committing to a specific case, we built a business case to assess its potential benefits. This involved analyzing how much time automation could save, the associated cost savings, and the number of transactions it could automate. We performed this analysis during the design and assessment phases of our workflow. Following this process, we would gather the data and present it to management for approval before moving forward with automation. The amount of time saved depends on the individual use cases but they are significant. What used to take hours now takes seconds.

UiPath has delivered cost savings for our clients' organizations, not through mere implementation, but through thorough assessment. We start by demonstrating the technology's value through small-scale projects, then scale up. At this point, we gather a list of potential use cases, identify the number of users who could benefit, and pinpoint the manual tasks ripe for automation. Only then, with a business case in hand, do we proceed with full implementation. This careful approach ensures that when use cases are deployed, they translate into meaningful time savings and reduced manual workload. As a result, our clients typically see cost savings in staff reductions of at least 30 percent.

UiPath is an efficient and user-friendly tool. It allows us to record and capture actions, which it then translates into underlying code. This makes development incredibly fast. The centralized orchestration feature is also a major advantage.

Clients are often convinced by its features and marketing. In some cases, when competing with Blue Prism and Automation Anywhere, UiPath has won out due to its faster time to market. This was especially true during the early days of RPA when clients were still experimenting and wanted to try multiple vendors. UiPath's flexibility and strong support, both during evaluation and implementation, were also key factors in its success.

We sometimes use the AI functionality mainly for document scanning but at the time it was poor and had room for improvement.

The operation costs have room for improvement. 

I have been using UiPath for over four years.

UiPath is a stable solution.

We haven't encountered any scaling issues, and UiPath is theoretically scalable for up to 10,000 bots. We've successfully implemented over 100 use cases for a large client with multiple subsidiaries, receiving no complaints.

The technical support is good.

Positive

The initial setup is straightforward and UiPath worked with us for every deployment.

We implemented UiPath for our clients in-house.

We evaluated Blue Prism and Automation Anywhere. Blue Prism and Automation Anywhere are not as user-friendly as UiPath and they don't have the same user community.

I would rate UiPath a nine out of ten.

Previously, we distinguished between Automation Anywhere and UiPath based on their bundled offerings. Automation Anywhere included category two AI capabilities with their RPA solution, while UiPath focused solely on RPA and didn't have much presence in the AI space at the time. Although UiPath could integrate with other AI vendors, this wasn't a significant interest for our clients.

Most deployments we completed for our clients were central.

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

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

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

UiPath has helped to minimize our on-prem footprint.

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

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

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

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

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

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

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

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

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

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

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

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

Positive

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

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

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

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

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

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

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

I would rate UiPath a nine out of ten.

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

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

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

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

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

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

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

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

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

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

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

I have been using this solution for three years.

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

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

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

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

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

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

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

Positive

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

I have been using UiPath for almost six years.

The stability is an eight out of 10.

The scalability is a nine out of 10.

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

Positive

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

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

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

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

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

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

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

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

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 use UiPath across a diverse range of functions and departments, encompassing accounting, human resources, loan servicing, employee progress tracking, and loan origination.

Our primary objective has always been to navigate the cycles effectively, ensuring that we can manage fluctuations without the need for constant hiring and downsizing. It's all about maintaining a consistent workforce over time.

The most valuable component is Studio—it's the cornerstone of our automation efforts. Recently, we've delved deeply into Insights, which has proven to be incredibly beneficial. Our key focus is on eliminating time-consuming tasks and enhancing reliability, especially in repetitive processes, which is where automation has proven to be a significant asset.

Simplification and adaptability for smaller businesses would be a welcome enhancement.

I have been using UiPath for approximately six years.

It is highly reliable, and we didn't have any issues with it.

When it comes to scalability, one aspect to consider is understanding the licensing for on-demand bots and related components. There have been some challenges, mostly on our side, particularly concerning high-density servers. 

The ideal scaling strategy involves adding more instances to these servers. We have opted for standalone virtual machines for each partner, and while this approach offers scalability, it does require the manual setup of additional machines, which can be a slower process for a small IT team like ours.

I contacted customer support only once when we encountered an issue related to changing the institution name within an application. Fortunately, the support team was able to resolve the matter successfully. I would rate them ten out of ten.

Positive

We were using a software called Winautomation, which wasn't very robust. So, we made the decision to switch it, which has been a beneficial change.

The initial setup was relatively straightforward. The main challenge we encountered was obtaining security approvals when transitioning to on-cloud.

Initially, there was just one automation tool in place. Our first step was to rebuild that process using UiPath and then we engaged with various business teams to explain the concept of RPA and gather input to create an initial backlog. Afterward, we collaborated with management to prioritize the tasks and determine the order in which we should proceed.

I find the licensing structure to be perplexing, and it frequently changes. The inclusion of AI units, raw document units, and Cloudmont licensing, along with various sub-licensing options, can be quite complex and non-intuitive.

We were considering a few alternatives, such as Blue Prism and Automation Anywhere. The primary goal was to find a solution that we could commit to for the long term. Ultimately, it appeared that UiPath, which is an industry standard, was the best choice. I also had previous experience with it at a previous company, which made the transition more comfortable for me.

Overall, I would rate UiPath ten out of ten.

I use UiPath for a variety of tasks, including automating user interfaces, processing documents, utilizing process mining, performing test automation, and even handling natural language processing.

It contributed to revenue growth by enabling us to maintain a consistent headcount and resource level while expanding our business.

Unattended automation, particularly in the realm of UI automation, is the most valuable aspect. 

Its ability to swiftly create automation in UiPath Studio is highly beneficial. It's highly effective in pinpointing areas within the organization where assistance is required.

There are several areas where I see room for improvement in the tool. One of these areas would be a more solutions-oriented pricing structure. This is because the platform requires a multitude of building blocks even for the simplest use cases and when dealing with newer clients, this can be challenging. One area where I'd appreciate additional or new features is in the realm of insights.

I have been using UiPath for seven years.

It offers good stability features with minor bugs from time to time.

When it comes to scalability, UiPath exhibits a high degree of proficiency.

The customer support is quite commendable and we often make use of TAM when needed. I would rate it around an eight out of ten because there is room for improvement.

Positive

I've previously used a variety of automation tools, including Blue Prism, OpenSpan, Automation Anywhere, WorkFusion, and Microsoft Power Automate.

The initial setup was straightforward.

I collaborated with my IT teams to establish high-availability virtual machines in Azure, whether on-premises or in a semi-private environment. I also partnered with my security team to formulate our digital worker strategy, which essentially involved managing identities, and I integrated all these components into a cohesive system.

It comes with a high cost, but the value it delivers justifies the expense.

We conducted evaluations of various automation platforms, including Automation Anywhere, Kofax, Pega, and Blue Prism. There were several notable distinctions. Firstly, UiPath stood out because it offered a free starting point, which was not the case with the others. Secondly, UiPath's integration with Visual Studio was more seamless compared to the other platforms. Their open and free-for-all community is an enormous advantage.

My advice would be to keep your problem-solving approach simple and avoid the urge to plan every detail. One common issue I've observed is people tend to overcomplicate the deployment, strategy, and overall decision-making process when adopting a new software platform. Instead, I'd recommend that if you can identify one or two use cases where the tool's benefits outweigh its costs, you have a solid starting point. Keep it straightforward, and you'll be on the right track. 

Overall, I would rate it ten out of ten.

I develop RPA processes at a financial services company. We use UiPath for tasks like data entry, image processing, and reporting. 

The biggest benefits of UiPath are fast implementation and the ability to run unattended bots. When they implemented UiPath, my manager was kind of shocked. 

We could run a process to extract every file from the portal each employee needs, which saves almost two hours per employee daily. You could see the benefits immediately. The hardest part of RPA is often convincing management that the expense is justified. The company can hire fewer employees because it's automating repetitive tasks. However, some of that savings is offset by the cost of licenses and hiring developers. 

I completed the UiPath Academy course, but I haven't received a certification. It helped me to understand how to implement UiPath processes. The main benefit is that it contains complete information about the tool. I know enough about using UiPath that I don't need to search the knowledge base when I get a new requirement.

Another advantage of implementing robotic process automation is that you can greatly reduce human errors. The RPA process almost never makes mistakes. It increases productivity and frees up employee time. For example, we have a guy who is responsible for creating memos for the checks. It involves 200 checks, but he was reassigned to something else, and now all those checks have been automated. The organization saved the equivalent of about 60 FTEs. 

The most valuable feature is image processing. It's something I use daily when I need to do some work on a VM remotely. Image processing enables me to locate the connectors and click to perform my job or task. It's easier for me to develop a process using UiPath compared to Power Automate.

UiPath enables us to set up end-to-end processes. For example, I have a process for taxes that gets a statement from the bank, checks incoming and outgoing transactions, calculates the withholding and exemptions, and files it on the income tax site. If I get stuck when I'm working on any process, I can easily ask the UiPath Community forum, and the public can respond to it. 

UiPath's OCR features could be improved. It has to do complex OCR captures with UiPath. I would also like improvements in the dashboard for executing processes. 

I have used UiPath for a year and a half. 

UiPath is stable, but you need to adjust the process when a web application changes its interface. 

UiPath is quite scalable, in my experience. We have a large environment and 150-160 processes. 

I rate UiPath technical support nine out of 10. They're always on our level when we contact them about any errors or limitations we face. They respond consistently, and they're available when we need a meeting to discuss something.

Positive

I have also worked with Power Automate. UiPath is more flexible and dynamic, whereas Power Automate is a little harder to handle.

The initial installation is straightforward. You install the UiPath enterprise license and apply the license key after completing the task. For unattended bots, you need to deploy the Orchestrator on-premises, which is somewhat complicated, but the overall experience is straightforward.

When we implement it on-premises, we need to take some steps for security. We have to configure some ports and connect all the PCs, but everything is under the control of an enterprise security security solution. During the initial installation, we needed five people, but once it's deployed, a single person can administer the platform. 

The pricing depends on whether you're running attended or unattended bots. Unattended processes cost a lot more, and you have to pay cloud costs, too. It's costly. The licensing for the tenant dashboard, developer's toolkit, etc. was reasonable, but unattended bots are quite expensive.  

I rate UiPath nine out of 10. I suggest new users study the knowledge base on the UiPath website. Many people get information from YouTube or another source that doesn't cover all the steps of this tool. However, if you study using UiPath Academy, you can gain complete knowledge of the tool.