UiPath Platform Reviews

We use multiple types of applications, including SAP. I work on contract documents with UiPath mostly. I work with different clients in different companies. We use the solution to automate processes. It helps by reading contract documents and updating details in SAP applications. 

We use a lot of document understanding. It reads the documents for us. I had a document understanding from UiPAth about two years ago. They helped us understand how it would work. With it, we were able to build a solution for invoices and purchase orders.

I like that we can work with different types of classifications. Whenever you classify a document using an ML model, there is a license associated with it. However, the intelligent classifier doesn't consume any of the licenses unless there is a specific amount of usage on the respective document. We process around a thousand documents per day and the classification is free. It helped us process all of these documents. We were able to train our ML models easily. 

Building automation with UiPath is very easy compared to others. The UI is easy. There's a community forum where you can request help. They also have a marketplace to help you find customized solutions. 

Previously, a turnaround time for a particular process was two to three days. Once we automate the process, we can handle the process in three hours. The turnaround times have improved a lot. We've drastically reduced our turnaround time on each transaction we handle. That's reduced our costs by quite a lot. That said, I don't have an exact figure off the top of my head. 

The user community and forums are great. They are really impressive. When I started in RPA, it was difficult to find help or to help others. The forum gives us the platform we need to help each other and source solutions to problems. It's now easy to find answers. It helps a lot. 

We use the AI functionality. I've used it for 1.5 years. It offers good functionality. However, you need to have a good understanding of how to use the resource effectively. 

We've achieved 80% to 90% now using AI.

We can automate more processes now. We need to do a proper assessment first to see what we can get from AI. However, there's functionality beyond document understanding. That said, finding the right use cases can be difficult.

We've sped up digital transformation and the cost surrounding it. It also wasn't expensive to do so. We can go ahead with minimal cost. We just need to align the solution with the right resources.

It's reduced human error. We have the functionality to capture business exceptions. If we need human confirmation, it will get sent to the action center. However, by automating, we've reduced the need for humans. We've reduced human error by 20% to 30%. The bot will capture data in areas where in the past humans may have made mistakes.

The bot has freed up employee time. We do have attended automation. If there are tasks needed for humans, we've created the process in such a way that they can do these tasks and then spend the rest of their time on other activities. It's likely freed up human time by 10% or more. We'd only work on processes where there is a minimum of 10% reduction in human time. 

There are a few bugs and a few things on the technical side where certain features are not available.

There are some functionality limitations on UiPath that we could have access to on different platforms.

If we have to move the model to production, we have to download it and upload it again.  

I've used the solution for seven years. 

The solution is stable as long as you maintain it in a proper way. You need an admin and support team to take care of performance. 

We work mostly with enterprise-level organizations. 

The solution is scalable. 

Technical support is good. If I have questions, they help me. However, I've had colleagues who have raised tickets and had trouble resolving issues. I personally have never had issues. 

We did not use other solution other than UiPath. However, I have done some small POCs in others. I've used Automation Anywhere, for example. There are different commands in AA and a few different features, however, they are both accurate and efficient.

I've set up the solution. The deployment takes a few hours. There may be software and hardware requirements If everything is there, it might take one or two days to get everything up and running. 

You may need to maintain your production servers after setup to make sure the bots keep running. We might have other weekly or monthly maintenance tasks to ensure everything is performing as expected. 

The solution is growing in price. It's getting to be too expensive. While I like the solutions they are providing, they need to balance the cost so that they can stay competitive in the market. 

I'm a customer.

I would recommend the solution, however, new users need to be mindful of the cost. If they have the budget, they should go with UiPath. 

I'd rate the solution nine out of ten. 

We use UiPath for robot authentication. We primarily use the software for accounting, particularly in our financial department, where we place some details from the client site, put them on a particular website, download the details, and then send those to a specific client.

I work for a big organization with many team members who access UiPath. On the client side, mostly enterprise clients, UiPath also has many users.

We've seen many benefits from UiPath, particularly from the client side.

The first benefit is manpower reduction, or reducing the number of people required to do the work.

Another benefit of UiPath is the reduction of errors. Sometimes, you'll notice errors from human intervention, but when the work is done via UiPath, you won't see any errors, so the solution has improved the success rate.

What I like most about UiPath is that it significantly reduced the amount of human intervention, which means that what usually takes people to do in ten to fifteen minutes would only take the robot one to two minutes.

I also like that UiPath runs 24/7.

I find the ease of building automation in UiPath valuable. It's easier to do that in UiPath versus other platforms, such as Blue Prism and Automation Anywhere. My organization has a lot of activities and needs to give specific details and accesses, and I found that UiPath works in the final product.

UiPath enables my organization to implement end-to-end automation. Sometimes, it's required for the user interface, but implementing end-to-end automation still depends on the product and agenda.

The solution helped minimize the on-premises footprint of my organization, mainly because it allows you to do a significant amount of work remotely, so UiPath is the best way to minimize your on-premises footprint.

My team has utilized UiPath Academy, precisely the basic course, then the development course, and then the advanced certification. You have to start with the basic course that shows you how the platform works, then move on to the development course, and then the advanced course or certification.

What I like best about UiPath Academy courses is that you see several maintenance scenarios you don't get to observe daily. You'll see perfect examples of different scenarios in the videos plus the instructor has a good teaching style, so my team was able to understand the lessons easily.

I also found that UiPath has helped in significantly reducing the cost of digital transformation.

In terms of reducing human error, UiPath has helped decrease it by twelve to fifteen percent. Sometimes, humans working for five to ten hours become tired, while the robot can work twenty-four by seven without getting tired, complete the work on time, and ensure that all details it encodes are correct.

Because of UiPath, my organization doesn't need so many people, but you still need to manage the robot, monitor it, and ensure that reporting works fine. It's not like my team has to do another project after utilizing UiPath. Still, the solution requires managing routers, which now requires one person with UiPath versus ten people without UiPath, so that's one example of what the solution has helped reduce. UiPath helped free up about thirty percent of employee time.

I like the most recent update that was completed for UiPath because it helped solve the clustering case, and then the modern authentication is good.

What needs some improvement in UiPath is its Document Understanding functionality. It should be simplified because, right now, it's a little complicated to use, as you have to give it data or details, so in the future, I hope that could be improved.

I have been using UiPath for more than four years now.

UiPath is a stable solution.

Currently, we find UiPath scalable, but we still need to observe and monitor it for an extended period to check its scalability.

We have not had any issues with UiPath technical support. They've helped us a lot and have provided a lot of input, and we are satisfied with how they've handled different types of issues.

Our rating for them would be seven out of ten.

Neutral

I've used Blue Prism and Automation Anywhere.

In my organization, my team previously used Excel Automation, which means the team uses scripts and macros to automate tasks. However, there was a lot of limitation, while in UiPath, there was none, so my organization switched to UiPath.

Deploying UiPath wasn't as complex. My organization has a lot of members who can access everything. There wasn't any issue with deploying the solution.

At the moment, I haven't seen ROI from UiPath, but maybe in the future, I will.

I find UiPath a reasonably priced solution.

My organization currently doesn't use UiPath to automate processes that deal with good causes, but there is a possibility in the future.

The organization I belong to has not implemented the AI functionality of UiPath in its automation program.

UiPath is currently deployed on-premises, but the team is considering moving it to the cloud.

Sometimes, the solution requires maintenance, specifically on the server side, as that runs 24/7, so you need to integrate and do some checks to maintain UiPath.

I recommend UiPath versus Blue Prism and Automation Anywhere. If you are using other platforms, I suggest moving to UiPath.

My rating for UiPath as a solution is eight out of ten.

My organization is not a UiPath customer. My organization is an integrator that creates the robots and recommends UiPath to businesses.

We use a feature called Document Understanding to extract data from invoices and generate reports. It uses the invoice number, amount, line amount, description, addresses, remit address, and other fields. This is the current project I'm working on. I'm using all the features available in UiPath to train the invoices to identify all the fields. Then, I deploy the training, create a pipeline, and use that ML skill in my coding while developing a project.

We are doing this for our team talent payments team. They usually receive different invoices from vendors for various reasons. My company currently has 700 vendors listed. These vendors send invoices for their services, and the talent payment team used to fetch and extract the data manually before we started working on this project. Whenever they received an invoice, they would open it and write down the data.

We have now completed phase one of the project and are in phase two. For this process, the bot will receive all the invoices and extract all the data needed by the team. We will then create a consolidated report in Excel for each vendor and present it to the talent team. This automation saves the talent team time. In addition, I have used email automation, Excel automation, API calls, and UI automation in this project.

We deploy UiPath on-premises, cloud, and hybrid environments depending on the organization's requirements.

Building automation using UiPath is really easy. Studio is a drag-and-drop environment with different palettes, search options, and simple properties, inputs, and outputs. It doesn't take much effort to develop a workflow in UiPath, even complex ones. UiPath also has recorders, so we can perform our actions and start recording before we perform them. UiPath will then develop the workflow for us based on our screen actions.

UiPath enables us to implement end-to-end automation, which is important to me from an analytics perspective. It makes it easier for us to provide solutions to businesses, regardless of their requirements. With UiPath, we can keep manual interaction to a minimum, from providing input to getting output. UiPath apps and interactions also make it easier to automate processes. In the past, people would develop scripts to automate tasks, but they had to keep in mind that there would still be some manual work involved, such as preparing an input file. With UiPath, we can minimize this manual intervention and prerequisites. This is a significant advantage.

Everyone on our team uses the Academy Courses when they start using UiPath, and whenever a new feature is added, we search the course list for the updated courses. The biggest benefit is being able to learn UiPath directly from the developers, rather than from a third party. When we learn from a third party, they have to learn UiPath first, and then try to explain it to us based on their own understanding. But when we learn from UiPath, it's like a personal experience, because they developed the product and know how it's supposed to be used. The other great thing about the Academy is that it's very interactive, with question-and-answer sections and plenty of resources. For example, they provide input files so we can try out new features. All in all, the Academy makes it really easy to learn UiPath. We just have to take the startup course, and they explain everything through videos, interactive sections, questions, tests, and data flows.

UiPath helps speed up and reduce the cost of our digital transformation.

It also helps reduce human errors in the normal processes that we develop.

UiPath has freed up our employee time. For example, in the onboarding and interview processes, our organization may have many people applying on any given day. Sorting through applications was done manually, but with UiPath, the process has been significantly sped up. UiPath now performs all of the tasks, such as getting candidate details and making consolidation reports for the hiring team. Overall, UiPath has saved us a lot of time and effort, and it has been a great return on investment.

The most valuable feature is the document understanding feature of this current project, which is better than ABBYY FlexiCapture or Automation Anywhere. It can learn on its own, given enough instructions and data. With training, we can actually train it to recognize the specific fields on invoices that we want. For example, UiPath can still provide information from a few of the invoice fields without training, such as the invoice number and date, which are present on every invoice. However, some vendors have specific fields on their invoices, such as the candidate name, job location, or start date, which we can train UiPath to recognize. This gives us the ability to train UiPath beyond the common things, if we are looking for any specific information or if we want to personalize it for a vendor. We are then able to use this trained model in our code, which is very helpful.

I also like the Excel automation feature. UiPath has recently updated the Excel activities package, which gives us more options with a more modern look and feel.

I find the features UiPath provides to be excellent, but the documentation is difficult to maintain. I have noticed that it can be difficult to find information on some features in the UiPath documentation portal. The document portal needs to be kept more up-to-date. UiPath will release the new feature, but the document portal will still have the older version information. The documentation portal could be easier to navigate if it were redesigned to make it easier to find information about a particular feature. It would be great if the portal were updated as soon as new features are released.

I have been using UiPath for almost three years.

We have occasionally observed some abnormalities, but we have not yet found the cause. For one of the processes, we are running macros and triggering them with UiPath. These macros can take ten to eleven hours to run. Sometimes, UiPath stops while a macro is still running. Once the macro is completed, UiPath is supposed to perform another task, but the macro takes so long to run that this does not happen. I believe this is a problem with our program, as it is taking too long to complete. These kinds of delays can occur, and that is understandable.

There are many areas where support can improve. However, it is not that bad. In terms of sticking to schedules, they are available quickly and listen to all of the problems. Sometimes, we have hit roadblocks because the people assigned to solve a particular support ticket did not have any idea about the feature. This has caused problems for us, as we have had to spend time filling in another person who actually had the knowledge about that feature. We have run into this problem a few times. 

Neutral

Our organization previously used Automation Anywhere, a script-based RPA tool. The fact that we moved to UiPath suggests that we wanted to change products for a reason. We must have heard that UiPath is better than Automation Anywhere in some way, which is why we made the switch.

We have seen a good return on investment.

I would rate UiPath seven out of ten. UiPath has a lot of features they are working on but they take a long time to enter production.

Maintenance for UiPath is minimal. Small things such as changing the passwords because of the password rotation policy. We maintain our bots through VMs that run on AWS.

I recommend UiPath because it is a low-code/no-code solution that can be used by non-technical people. The Academy courses, which train users specifically on how to use the tool, make it easy to develop and automate processes. UiPath also offers a community version that includes most of the features of the paid version. Earlier in my career, I learned to use Blue Prism, which is a closed-source solution that only had basic courses available in its academy. It was difficult to use compared to UiPath, and it was hard to get any information on any forum or from its academy on how to use the tool and update it. In terms of learning, use, and understanding, UiPath is much easier than other solutions.

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

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

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

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

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

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

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

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

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

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

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

I've been using the solution for one year. 

The product has been stable.

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

I haven't worked with technical support.

I did not previously use a different solution. 

We're using the 2023 version of the solution. 

I was involved in the implementation. 

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

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

We deployed the product ourselves. 

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

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

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

We are UiPath partners. 

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

I'd rate the solution eight out of ten. 

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

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

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

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

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

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

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

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

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

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

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

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

I have used UiPath for approximately two years.

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

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

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

Positive

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

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

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

I rate UiPath eight out of 10. 

We use UiPath to automate daily repetitive tasks.

I would rate the ease of building automation with UiPath a nine out of ten. It saves us a lot of development time, and the drag-and-drop feature is very useful. The cloud version's orchestrator is also amazing, as it can host our robots.

UiPath enables us to implement end-to-end automation, which is one of the most crucial parts for our customers. Most of our users are not technically proficient and do not know how to deal with these things. They want the automation to be complete without any manual intervention.

The UiPath User Community is really helpful and has helped solve a lot of problems.

The biggest advantage of UiPath is that a lot of time is saved, which can be used for other projects.

UiPath Academy courses are helpful. They help us gain a deeper understanding of the product.

UiPath's AI helps us perform more complex processes in automation.

It has helped us speed up our digital transformation by removing a lot of manual work.

Speeding up the digital transformation process does not require any expensive upgrades or much IT support to keep UiPath up to date.

UiPath has helped to reduce human error. This indirectly allows our customers to focus their employees' time on more productive projects.

It has helped us save time.

UiPath helps reduce costs, especially for accounting companies. They are able to automate basic tasks reducing the number of people required for daily tasks and can also have those tasks running twenty-four hours a day seven days a week.

UiPath is a no-code automation tool that saves me a lot of time when developing workflows.

UiPath is very slow for scraping. If they could make it faster, that would be great. We are currently using custom robots to scrape data, which is faster.

The initial setup of UiPath can be complicated. It would be helpful to have an executable file to simplify the deployment.

Integrating UiPath can be a complex and error-prone process, especially when it comes to calculations. A helpful feature would be the ability to add simple workflows using executables, which would be especially beneficial for small projects.

UiPath needs to be more compatible with MacBooks.

I have been using UiPath for three and a half years.

The UiPath software is generally stable, but some of the packages within it can sometimes be unstable. For example, we have had to switch to older versions of some packages in order to get them to work properly.

I would give the scalability a rating of seven out of ten. As we scale, we involve more users and machines, which means ensuring compatibility.

To deploy, UiPath needs to be installed on the production machine and the extensions need to be ready. One person is enough for the deployment.

The initial setup of UiPath can be complex, as we sometimes need to explain to customers that it is not as simple as copying and pasting an executable file. UiPath requires some setup and configuration in order to work properly. 

I would rate UiPath an eight out of ten.

The decision of whether or not to use UiPath depends on the customer. If the customer is a Windows user, then UiPath is a good choice because there are many third-party packages available that make tasks easier. The orchestrator cloud functionality is also very helpful.

UiPath is easy to maintain because it integrates with other applications.

I recommend UiPath for Microsoft Windows users.

We use UiPath to automate the repetitive reporting tasks in our organization. I am currently using UiPath for five Oracle-based projects.

UiPath has increased our organization's productivity and efficiency and saved us money. 

There is a short learning curve. We can learn to use it in one month, compared to other RPA solutions that take three months.

Building automation using UiPath is simple.

UiPath enables us to implement end-to-end automation. First, I build the code based on the customer's requirements and run the code in UiPath. Then, I run the code using an orchestrator on our VM when it is put into production.

The UiPath Community is a great place to find information without having to contact the technical support team.

I am a big fan of the UiPath Academy courses. When I first started using UiPath, I took all of the courses, which helped me immensely. Whenever I need to learn a new UiPath task, I simply go to the Academy courses.

UiPath helps speed up digital transformation and reduce costs.

If we input data into UiPath correctly, it can help reduce human error by 95 percent.

UiPath has helped to free up 25 percent of our employees' time by automating recurring tasks, allowing them to focus on other tasks.

It has helped our organization save around 30 percent of our organizational costs.

UiPath is user-friendly. Compared to other RPA tools that require knowledge of a programming language, UiPath requires less coding.

Occasionally, we receive an error message stating that a UiPath element is invalid, even though it should be working. This is frustrating and needs to be addressed.

UiPath needs to improve the selector and offer better integration for Python.

I have been using UiPath for two years.

I would rate the stability a seven out of ten because we sometimes encounter errors.

I would rate the scalability an eight out of ten.

The technical support is good but I usually find my answers using the UiPath Community forum.

Neutral

The deployment is not complex compared to other RPAs that require knowledge of Python or Java.

Deployment time varies depending on the use case but averages two to three days.

One person can complete the deployment.

UiPath offers two versions of its solution: a free Community edition and a licensed Enterprise edition. The Enterprise edition includes all features and automatic updates, which are not available in the Community edition.

The cost for UiPath is affordable.

I would rate UiPath a nine out of ten.

Basic maintenance is required for UiPath.

We have UiPath deployed in four of our departments including sales, booking, comp, and operations. In my department, we have five UiPath licenses.

I've worked in two organizations where I have used UiPath. The first organization was in banking and we used UiPath to help automate banking and financial forms. The second organization, the one I am currently working for, is a technology company with several sub-companies that include banking/financial, the hotel sector, and some overseas organizations. In this organization, we automate tasks that are repetitive, as well as reconciliations.

The main advantage is that we've synchronized our process across 70 sub-branches covering the entire island of Sri Lanka. Previously, we had three or four employees manually inputting the user entries for the various branches. We eliminated those positions so that data entry is now done by robots and performed in the head office.

We have multiple robots directing all of the data to the robot platform in the head office. We saw value within six months. That's how long it took to eliminate the positions. We stopped recruiting people who had previously done that task. More tasks remain, but the main use case was realized within six months.

The APIs are helpful in our workflow. We have a separate application for the government sector, and the Sri Lankan government provides that API. It's a matter of due diligence because we get the customer information, like the national identity card number. We use the API to exchange that information.

We get quick information about existing loans, including how they perform and whether the borrower is paying on time. If they are red, it means that the payments aren't being made in that period of time. That is the kind of information that is exchanged with the API. We can process 20 or 30 users every minute through the API on average.

Previously, our staff onboarding involved a large number of hard-copy documents—around 50. We have automated what was a long manual process, using automation to go through the documents to create a customized onboarding process, one that includes the government regulatory platforms that we are required to use. We used to have to store those documents in an archive, taking up our storage capacity. With UiPath's OCR platform, we get the information we need to do the task. That has resulted in huge savings for the organization, including environmental savings in terms of trees used for paper. It has also saved a lot of the human effort involved in verifying data in those documents.

In our previous process, the documentation was written entirely by humans, including data entry. That data entry was a critical point but there was a lot of human error. That has been reduced by 85 to 90 percent. In my current organization, we have automated about 70 processes and the amount of employee time saved depends on the process. For example, one of our automated processes has saved eight hours for one FTE, while another has saved 10 FTEs two hours each.

And we have done an end-to-end automation for an insurance platform, for renewals. There is no human touch at all.

UiPath has also helped us to reduce our on-prem footprint, compared to our previous platform. In our previous model, we worried a lot about our data. But with UiPath in the cloud, could our entire database be somewhere else, meaning not in our custody? A few years back, UiPath introduced governance and audit platforms, and that's when we felt that it was okay and that we didn't need on-prem platforms anymore. It was okay, at that point, to go for a cloud platform. We are migrating our on-prem platform to the cloud now.

UiPath Orchestrator is incredibly useful. It's the main dashboard platform we use. Orchestrator provides a single platform where we can connect with legacy systems and manage all the bots. 

Orchestrator lets us see the entire process across various department units so that they can see the separate tenants and units. The application can multi-task to handle processes even when we have a long queue. If the queue is piling up, we can assign multiple robots to clear the queue quickly. We can find the ETA for the queues and everything inside Orchestrator.

The Studio and development boards are also helpful.

The UiPath community staff is the best I have ever seen. I have worked in several communities, not only in RPA platforms but for other tools, but the UiPath community is the best. I am an active member of the community. If someone has a question, we always look after it there and are very happy to help them.

The UiPath Academy is very useful as well. My colleagues and I are always going through the new features that are available for our automation and new developments. We always keep in touch with the Academy.

Previous Orchestrator versions were very user-friendly for the admins and the users, but the new Orchestrator is a bit advanced. If they could reduce its complexity, to something more like what it used to be like, it would be better.

Also, if they can improve the performance of robots, that would be good. 

I have been using UiPath for more than five years.

There are no issues with the stability.

It is scalable and very easy to scale but, again, that comes back to the pricing.

UiPath scales easily, but scaling for the cloud and on-premises versions is different. For the on-premises solution, we need to add new licenses to scale up. But it's easy in terms of scalability on our end.

Support can be divided into two tiers: enterprise users and community users. Enterprise users like us get high priority because we are dealing with live operations and customers. When we raise a ticket, we have options like critical and onsite support. They reply in one or two hours, or in less than 30 minutes if it's critical. Their technical support is very helpful and the ticketing platform is very good.

We also get a fast response for non-technical customer service issues.

I hope their support can be developed because when there is a difficult case, sometimes it seems that it's a new issue for them as well. I have experienced that. That should be improved a bit. Overall, support is very good, but there is room for a bit of improvement.

Positive

We didn't have an automation solution previously. As a developer, there are lots of costs in our country associated with switching to automation. There weren't other solutions that could integrate our entire operation like UiPath. I don't think it was possible to select another one.

As a user and an administrator, I can manage the entire server from the main controller. I know everything that UiPath is doing. I also can't think of another solution that has the same broad user community.

UiPath runs Orchestrator and the application in the cloud, but our robots work on-prem in our data center.

In my previous organization, I deployed UiPath, but when I got there I didn't even know what UiPath was. Fortunately, they have nice documentation on the UiPath website, step-by-step. I followed that and was able to deploy things. Since then, I have helped several organizations, via the UiPath community, to deploy Orchestrator within two or three hours. If they have completed the relevant prerequisites, it can be done in that amount of time for a standard installation.

We had a detailed plan in place that progressed in phases. In phase one, we eliminated the data entry function in the main office and the branches. In phase two we would optimize our existing processes. Once all the automation is finished in the head office, we optimize those head office processes.

We have seen significant cost savings throughout the company. Before we started to use UiPath in 2019, we had three or four people doing data entry in every branch. It has eliminated human data entry and also frees up our cashiers because the cashier cannot go anywhere when the queue is long.

We calculated what we have spent for our entire RPA platform and what our ROI is. Our calculations showed that after one and a half years, we had recouped our entire spend on the RPA platform. That included the entire robot cost, servers, the software license, et cetera. That means we had ROI after 18 months.

When it comes to unattended robots, the cost for us in Sri Lanka is huge. It's tricky for us to convince management when they think about the price. We have to prove the value with evidence. We explain that we will save this or that amount, so please help us with this tool. 

Maybe for Middle Eastern or other countries, the price of that robot is not a big deal, but roughly $10,000 for an unattended robot is a very big deal for us. 

They are switching their licensing from a legacy mode to flex licensing. With that kind of license, they have given up a certain fee, which is okay, but the robot cost is high. Orchestrator is now free on the cloud platform, but we need UiPath Studio, the developer platform, as well as attended and unattended robots, and those are the things we pay for. The unattended robots are the highest priced. On a scale where one represents the most expensive and 10 is cheapest, I would rate UiPath at about two.

We have looked at several automation platforms. We have done several demos and looked at the price of Automation Anywhere and Blue Prism. But they are more complex than UiPath.

If you consider other applications, like Blue Prism and Automation Anywhere, the UiPath platform is better because it's user-friendly, making it easy to get tasks done. Even for a beginning developer, it's easy to catch up with all the stuff in UiPath.

UiPath has noticed that I'm an active contributor, so they contacted me to get feedback and invite me to build the community. If I check my LinkedIn profile, I can see all the things I've done in the UiPath community. I don't see that with the Automation Anywhere platform.

If I don't know how to do something, I can watch one video and learn everything I need to know. If we post a question on the forum, we get an answer in one or two minutes from another user.

My main use case for this product is process automation. For example, we use UiPath to make quick and easy applications for our internal office use.

It has reduced repetitive tasks. We now have more efficient processes. Manual testing was one of the time-consuming tasks that we used to do. Our testing team used to spend days and nights testing. UiPath has completely boosted the process. For example, previously, if we needed three employees to do a particular manual test, now, because of the automation that is available, we require just one employee. It has saved a lot of time, and it has also enabled us to deliver better-quality products. With automation, less manual work is involved, and the quality of the product that we deliver is very good. We have also been able to automate a lot of tasks, such as compliance tracking.

It's very easy to build automations using UiPath. Most of the things are just drag-and-drop. People with zero to minimal coding knowledge can build applications using UiPath. It's straightforward. One thing that facilitates this is that a lot of in-app guides or inbuilt tutorials are available, which makes UiPath very easy for a beginner who is starting out with UiPath. With such a good knowledge base, it becomes very easy for them to get a grasp of everything and start building applications.

It enables us to implement end-to-end automation. It also improves the employee experience. In software development, especially in the field of testing, there are many repetitive tasks, and they are prone to many manual errors as well. Automation through UiPath boosted employee morale, and it also improved the customer experience. We have been able to deliver better products on time to customers with UiPath.

It's a cloud-based solution, and it has helped to minimize our on-premises footprint.

With the AI functionality, we have been able to identify areas where automation can be implemented. We are trying to identify where process automation can be brought in and efficiency can be improved. The AI functionality is good, but there's a lot of initial work that needs to be done for this. It has enabled us to automate more processes. Within a month, we have been able to automate around 40 to 45 processes that were pending for a long time. It has definitely speeded up the entire process.

It speeds up digital transformation and also reduces the cost of digital transformation. Less manual intervention is needed, and less manpower is needed. It definitely reduces the overall cost for the company. Also, when something is automated, it's very quick. Redundant or repetitive tasks are completely reduced, and a lot of time is saved. So, it definitely saves time and cost.

This digital transformation didn't require expensive or complex application upgrades, or IT application support. Everything was inside UiPath. We just took some additional training from UiPath to get it implemented. Other than that, we did not use anything.

It has reduced a lot of human error. With manual testing, there were a lot of errors. With automation, that has been completely eradicated, and a lot of time and effort has been saved. It has reduced human errors by 100%.

It has improved our customer experience as well. We provide services to our clients or customers. Any human error leads to a delay in delivering the application. With automation, we have completely removed human errors, and we are able to satisfy our customers. It has impacted the retention of our customers.

It has freed up employees' time as well. A task that previously required three or four employees just requires one employee now. We do not spend all our time on a process. Once we implement and start an automation process, everything happens automatically. We can concentrate on other aspects of software development. It has saved 20 hours per week or 4 hours per day. 

It has saved a lot of costs for us in terms of employee reduction. We now need just one employee for a task rather than four employees. So, there are savings in terms of employee salary. We are also able to retain customers better, which has improved our revenue. Overall, about 25% of our cost has been saved. We were losing revenue and customers because they were not satisfied. With UiPath, our efficiency has improved, and the time to market has reduced. 

There are two features that I like a lot in UiPath: one is the Orchestrator option, and the other one is the Studio option. I especially like Orchestrator because it's very insightful for us. It's like a centralized hub to manage and maintain all of our process automation and task-mining. It systematically organizes each and every folder so that it's easy for us whenever we need to know, set, or take something. Studio is where we primarily do most of our designing. It's a very good tool. Most of it is drag-and-drop. These are the two main useful features for us.

The dashboard view could be more visually appealing. Dashboards in any software should stand out with colors, numbers, and other things, but in UiPath, the dashboard is not that visually appealing. The UiPath team could make it more visually appealing for us to get more insights.

Another improvement area is related to product updates. Earlier, we used to get monthly updates about the product, but that has stopped now. If they could bring that back, it'll be very good.

We have recently tried the AI functionality. There is a lot of learning that we need to do with regard to AI. It's good, but it's not as smooth as Orchestrator or Studio. The AI aspect of the product could be better. We're currently working on allowing the AI to automatically detect areas where automation can be brought in and efficiency can be improved. That needs some more refinement. It's currently not straightforward. Sometimes, it just repeats whatever it said previously, so nothing new comes out of it. The AI aspect of the product can be much more refined. Apart from that, I don't have anything else. It's a well-thought-out and complete product. It's very easy to use and easy to understand.

I've been using UiPath for around a year.

It's a cloud-based solution. It's very stable, and we just need to make sure that it's up to date. Personally, I have not seen any bugs, errors, or performance issues with this. We are not using an on-premise model. It's cloud-based. So, the service is always available, and it's always quick. It's very stable, and I have no complaints.

The applications that we develop with UiPath are also very reliable. They don't crash or have any performance issues. They are very stable and reliable.

When we started with UiPath, our main use case was to be able to quickly and easily make applications for internal purposes, but now, we are doing a lot more with UiPath. We are doing compliance, and we are doing AI-related process automation. It's definitely a scalable solution.

It's deployed across multiple departments. Each department has its own RPA functionality and RPA usage. In my department, 20 of us use UiPath, but I'm not sure about its users in other departments. 

Their support team is very knowledgeable. Whatever issues we have, they try to explain them to us in a better way. The SLA or response time is pretty quick. It's 24 hours for us. I have no complaints. I would rate them a nine out of ten.

In addition to the support team that UiPath has, I depend on the user community for all my queries. I see the UiPath Community as the main support tool. It's my go-to space for anything related to UiPath, and I am very satisfied with the quality of the community.

Positive

I am not aware of any other solution that we used to use.

It didn't take a lot of time to implement, which is a very good thing about UiPath. In about two to three weeks, we got the entire setup done. That was very quick.

It's a cloud solution. We have deployed it on AWS. Being a cloud solution, it requires very less maintenance from our side. That's one of the very good things about UiPath. We just need to make sure it's up to date.

We have definitely seen an ROI. Customer satisfaction has improved a lot. We have been able to retain customers better, and we have been able to reduce manual errors by 100%. 

Its pricing is straightforward. There are two editions: one is the community edition and one is the enterprise edition, which is a paid one. The paid edition is priced reasonably.

They charge extra for additional training and implementation, but that should be bundled up with the enterprise edition itself. All in all, it's reasonably priced.

To anyone considering UiPath, I would advise checking out the trial version of UiPath before going on to the actual version. Before you start using UiPath, there are a lot of things you need to get your head around. People who generally use UiPath have zero or minimal coding skills. This is something that you definitely need to know.

You can try out the UiPath Academy as well. They provide certification courses. I have not used UiPath Academy, but I have seen my team using it for the certification program they offer. I have heard that it's very good.

I would rate it a nine out of ten because I have not faced any issues with the product. Whatever we wanted to achieve with this product, we have been able to achieve.

I developed several use cases using UiPath. One involved website scraping, where I extracted data like temperature, humidity, and pressure for various cities from a specific website and displayed it in an Excel sheet. This was a small project, but my main focus was a prototype for a client: digital marketing automation. Using UiPath, I created an automation to automatically post articles on different social media platforms.

UiPath has certainly improved our operational efficiency. My prototype adheres to its principles.  UiPath has a sheer number of functionalities and features in UiPath. While these are beneficial, considering operational efficiency, UiPath excels thanks to its modularity. It's comprised of distinct components like Orchestrate, robots, and studios. This breakdown allows each component to function independently, increasing work flexibility and ease of use.

I would rate the ease of building automation using UiPath an eight out of ten with ten being the easiest.

I would rate the UiPath User Community ten out of ten. It is the best community I have used.

I'm taking advantage of the UiPath Academy courses and find them helpful.

UiPath helps to speed up our digital transformation and reduce costs.

Automation through UiPath helps reduce 80 to 90 percent of human errors.

The UiPath User Community is the best feature. We can find a solution to all of our issues there.

UiPath's interface element identification is arguably more reliable than Automation Anywhere's. This is because it utilizes an element descriptor method, which essentially locates "anchors" within the target element, not just relying on its absolute position. In simpler terms, it seeks a stable reference point within the element itself, even if its overall position on the screen shifts. As a result, changes to the website's UI are less likely to break our automation, as the code doesn't depend solely on the element's position. Additionally, UiPath offers a wider range of app integrations and features compared to Automation Anywhere or Blue Prism, making it more versatile for different automation needs.

Logging is also valuable. We can see any system, business, or technical errors.

One area that could be improved is how we access the UiPath Academy courses. While it's fantastic that each course provides an assignment, it would be more convenient if we could view the solutions directly within the platform rather than downloading them each time and opening them in our individual UiPath Studio applications. Ideally, there would be an interface integrated into the course platform itself where we could access and review the solutions directly within the browser. This would save time and streamline the learning process.

In Automation Anywhere, each line of code is displayed in a list view, offering clearer visibility. In contrast, UiPath condenses everything into a boxed view or flowchart, which can become cumbersome when dealing with numerous intricate conditions. Pinpointing specific segments for modification within such a condensed format proves challenging. Therefore, UiPath's UI design could benefit from an overhaul to enhance clarity and ease of navigation, especially for managing complex workflows.

I have been using UiPath for more than a year.

I rate the stability of UiPath an eight out of ten.

I rate the scalability of UiPath a nine out of ten.

I find Automation Anywhere to be more user-friendly for newcomers.

While I have more experience with Automation Anywhere, and it's where I've worked more extensively, UiPath is currently the market leader in the field. This prompts me to explore what's behind its success and delve deeper into learning UiPath. There must be compelling reasons why it holds the top position.

UiPath is more expensive than Automation Anywhere.

I would rate UiPath nine out of ten.

I recommend UiPath as the leading RPA technology, considering the current market trends.