UiPath Platform Reviews

One of the use cases is related to material billing. For the material billing process, previously, when a vendor invoice came into our SAP system, our staff had to write invoice data and process the invoice. We transferred this process to RPA. We now have only one robot focusing on this project. It handles about 120 invoices in a month.

We have not yet used UiPath's AI functionality in our automation program. We are always thinking about using AI and machine learning in our development, but we have not had a project in which we could use AI. We might use it in the near future.

It is deployed on-prem, but we are thinking about changing it to the cloud.

It is easy to build automations by using UiPath. One of the projects was related to reporting or getting some information from the websites. To do our purchasing, the department needs a summarized report containing prices in email. We converted that into an RPA project where the robot accesses the website, reads the specific numbers, creates a small report in Excel format, and sends it as an email to our department. It took us three days or so to implement this automation. It was an easy project.

UiPath enables us to implement end-to-end automation. One advantage is that robots can work 24 hours. It enables people to add some value to the company. They can think about some places where they can improve or they can reduce costs. They have enough time to think about it. Before RPA, they used to take a lot of time to do the same work.

Our on-premises footprint has been reduced. For our invoice use case, our staff used to print out the invoice to check the numbers and enter the data. We eliminated that and reduced our paper usage by approximately 20%.

UiPath reduces the cost of digital transformation. We are using the SAP system, and there is a cost if we want to implement any automation. There are consulting companies that can write the code, but they are very expensive. With UiPath, we can automate our processes and eliminate or reduce that cost.

It has reduced human error. If the invoice is correct and the data is correct, what the robot writes into SAP is also correct. It has reduced risks and errors.

Employee time has been freed up. It saved us the time of one staff member. We were able to shift that person to another department because of the time savings.

UiPath has saved us costs. We could shift one staff member to another department. We did not have to hire one more staff member, so it has saved that cost.

The development part is very simple. It is easy to use. Our development time for a project is approximately two weeks now. It is good because even though you can develop the code in SAP, it takes a lot of time. When the demand is high, we can deliver in two weeks. It has helped us to tell our organization that RPA is easier and faster than the usual code route.

We have used UiPath Academy courses for process mining. For RPA, we have some KPIs for developers to complete their education. In UiPath Academy courses, they have an option for the Turkish language for videos, but they are always in English. They should correct that.

UiPath should integrate more machine learning and have more machine learning processes. In their development system, they have some machine learning tools, but they should increase them. With robots and structured data, in my opinion, we can use machine learning. The robots should also use machine learning to create some AI models.

Its price should be reduced.

We have been using UiPath for two years.

At the beginning of the project, there were some issues, but now, it is stable.

It is scalable. For the RPA part, we have 5 robots, and we have 40 projects that are live. We have about 100 projects that are to be implemented.

I would rate them an eight out of ten.

We did not use any other solution.

In our department, we have three employees for implementation. We do not take the help of any consulting company.

Its price could be better. They should reduce its price.

The insights module, process mining, document understanding, and other modules should come as one package because when you buy a module, it usually is not enough for a project, and then you have to buy another module. They might already have bundled these. I have not checked it recently.

To those evaluating this solution, I would recommend seeing it as one package. Before implementing it, the organization should also be ready for it because, with automation, people have concerns about losing their jobs. Organizations should have a clear understanding that robots are coming to save time.

Overall, I would rate UiPath an eight out of ten.

We use it for handling processes that involve human effort savings. We are currently focusing on processes and problems that our users are facing in their day-to-day activities. It is used for the automation of business problems that are repetitive and error-oriented with a huge number of users working on them. We list down a set of processes where users are spending a lot of time, then we verify whether the use case is valid for automation using RPA. Once that is complete, we start programming the bot based on the requirements given by the user. We try to mimic each and every action performed by a human being by using UiPath Studio. It replicates what a human being does.

In terms of setup, the development happens in Studio that's on-premise, but the deployment of the robots is done on the cloud. They have their own cloud service called Orchestrator. UiPath hosts that, and it is available at cloud.uipath.com. It is basically the UiPath Cloud. The interface is completely handled by UiPath.

The biggest benefit is that before implementing automation, the users were spending a lot of time doing mundane and manual activities. Implementing the robotic process automation for processes that they were involved in helped them to avoid doing these manual activities and focus on more value-added processes. On the whole, it has helped the users to spend their time more wisely and also get more benefits for the same time spent. It helps us to improve user satisfaction by improving their working methodology because they are only doing things that are value-adding.

We are automating all the manual activities that can be successfully handled by the robots. So, the users are really happy, and we are getting good feedback from the users in terms of time savings. We are also achieving 100% accuracy in the output, which was not the case when the users were performing these actions. When they were performing the actions, the users had to validate the outputs, and the outputs were not as per the requirement. There used to be an error rate of at least 10% to 15%, but with automation, the error rate has been reduced to zero. So, the removal of manual activity and the reduction of the error rate to zero are two of the main benefits.

We are using it in our finance operations for our accounts payable process to process invoices. For this process, we were receiving invoices at a rate of more than 50 per day, and having humans perform those actions was not sustainable in the long run. So, we developed a robot that would automatically process invoices that we received through email. It extracts and updates the data into our ERP, and then, it sends an email to the users telling them that the invoice has been received, verified, and uploaded into our ERP. Now, we have a process that saves approximately two hours for five or more users on a daily basis. At an annual rate, we can save approximately 10,000 hours. We develop the bot in UiPath Studio and then deploy it in cloud Orchestrator via an unattended bot, which is a bot that runs on a predefined schedule. We have a particular time when invoices arrive in our inboxes. We set the robot to run at that particular time, and then the robot is able to process those invoices and proceed to the next action.

We focus only on processes that can be automated end-to-end, completely eliminating human activity. UiPath is flexible, and it allows us to build robots that prevent human intervention right from the start and all the way to the end. Then, we are able to deploy it on the cloud by using the Orchestrator solution. From start to finish, we have completely eliminated human effort, supporting our mission of end-to-end automation. For process analysis, we use a UiPath tool called Task Capture to understand the business case and draw a flow diagram for the steps involved in a process. UiPath has all the solutions required to implement end-to-end automation, and we are successfully using them for all our business problems.

This end-to-end coverage is important. Basically, we select processes where we can avoid human intervention. End-to-end automation is one of the key KPIs that we check before we even start automating a process. It is the first thing that we look for because we prefer no human intervention at all, be it for any kind of input, validating the output, or checking the logs of a process. All of these are predetermined and handled by the robot.

It is cloud-based. So, we do not have any infrastructure costs for maintaining the servers, etc. That is a big advantage. Also, Studio updates for development are pushed automatically. We receive the updates and just click on them, and Studio is updated. Overall, it saves a lot of time for the IT team because there isn't any involvement from IT resources after we deploy or install Studio on our system. From there on, there is literally no involvement of the IT department. That is how beautifully they have designed the tool for the updates as well as overall maintenance.

We went for the cloud to avoid any on-premises server costs that we might need to take care of on a recurring basis. The cloud was a big advantage for us. We are able to save approximately 15 lakh Indian Rupees, which would be $10,000 to $15,000, by not going for the on-premises setup. We were able to save that sort of investment in server costs by going for a cloud-based tool.

We were able to synthesize the value of this solution right from the inception. As soon as we deployed the bots, we were getting actual analytics for the run rate of the process and the total time of bot execution. Indirectly, the time during which the bot executes is literally the time that is saved from human effort. We get proper metrics of the time being saved by using Orchestrator. The other important thing is logs. In case a process fails, from the logs, we are able to derive insights about when exactly a process is failing. We are then able to develop a solution to handle these failures and re-implement them. So, overall the cloud solution gives us insights. It adds value to even developers' time by giving us an overall metric of the time saved as well as utilizing the logs for insights about the process runtime, et cetera. Overall, the cloud functionality is a great value addition.

It affects our ability to scale up automation. When we develop and deploy a process, other users in different departments take a look at the processes, and they are getting confident about the fact that this can solve their problems. We have been receiving requirements, and in that way, we are able to scale up the automation. On top of that, we develop the robots in a way that is modular in nature so that when we implement a process, we have reusable components that can be plugged and played into the new process. This improves the speed at which we can automate processes.

It has indirectly brought innovation from the users' perspective and developers' perspective. The users are saving time, and they are getting innovative in their day-to-day activities. In terms of development, we are on a constant learning path. When the vendor releases new software updates, we are able to effectively utilize those and implement them into our processes on an immediate basis, which improves the speed of delivering a process and the quality of output.

We can scale automation without having to pay attention to the infrastructure for doing so. We don't have to be worried about the cost involved with the on-premises setup. It is a cloud-based solution. So, when a requirement comes up and a bot is developed, only then we need to apply for the license and procure a bot. It has been beneficial because we don't need to pay any upfront cost until the bot is developed and ready to be deployed, and because the bots are delivered completely through the software service, that also indirectly proved very beneficial for global deployments and scaling of processes.

Its AI functionality is helpful to learn from the existing use cases and then implement the learnings on the new and upcoming test cases. As a developer, we need not spend any time developing templates for the extraction, etc. The AI module in itself has the capability to understand new forms of data. It can then accordingly extract and plug in the data to our templates without much effort. So, AI functionality has saved a lot of our time in developing a solution as compared to doing it the manual way.

We had one process where we had to use AI functionality, and we were able to eliminate any manual efforts. Previously, we had somebody who was verifying the output of the bot and after that only processing went to the next step, but with AI, we got the confidence that the bot has the ability to complete the action without manual intervention. That is one great example where AI helped to eliminate manual effort and improve the quality of the output.

It has significantly reduced human errors. Bots have quite a high performance rate with minimal or zero errors. The errors only occur because we haven't updated the business case in the bot. Once the business cases are updated in the robot, we do not see any errors. The bots follow all the steps as programmed and do not deviate from the set of rules defined while developing them. This reduction in human error has had a positive impact on users. The users had been feeling more comfortable using the robot output rather than relying on their own output, which sometimes had errors. So, overall the confidence level has improved and the lead time in delivering the output has also improved. The time they were earlier spending on the validation of their output has reduced. 

It has freed a lot of time. We only automate processes where we find huge time savings. We count it as full-time (FT) employee benefits. We only pick processes that have three or four cumulated FT benefits. With automation, we are saving at least three or four hours on a daily basis. This time is being utilized by business users in completing any other backlog work, focusing on other important things, improving their own work skills, etc.

Excel automation is extremely reliable. Excel integration is one of the top features that I have been using. We also have a feature called Document Understanding for processing the PDF format of an invoice by a bot. It has the capability to scan an invoice and then pick out the required fields, such as the name of the vendor, the details of the products being sent, or the cost of the product. There is an AI functionality that allows a user to program the required fields to be extracted, and the bot automatically follows those rules and extracts the data. Therefore, the AI functionality of Document Understanding is another important attribute that I personally like about UiPath.

I also like the Computer Vision functionality, where UiPath provides image processing abilities for robotic process automation. This provides a big advantage because images can be automatically processed without involving any additional tools. With an API, we can automatically link the Computer Vision engine and start extracting and processing images at a quick rate.

UiPath is a low-code platform, or mostly no-code platform, where coding is minimal. We can drag and drop all the required steps and then develop a bot in very less time. I am good at programming, but even a user who doesn't know programming can easily pick up the tool. The ease at which anybody can learn it is quite high. Overall, it is a 10 out of 10 in terms of usability. It is really easy to use with the tutorials that they have in place. Everything about it is quite simple.

We use Orchestrator to keep a track of all the robots that are deployed, monitor the logs, and deploy the robots on the runner machines. We use Orchestrator to upload the bots from Studio to the cloud and then deploy them to runner machines across our virtual machines. Once a bot executes, we get the logs, and if needed, we can monitor them to check that the processes are coming in smoothly. In case of any failures, Orchestrator also has the functionality to re-execute the process. So, we are utilizing the cloud to a greater extent for managing our robots.

The UiPath community is wonderful. It is one of the best communities where we can get a solution for any question that we post in a matter of minutes or hours. Whenever we post a question about any doubt or a bug, someone from the UiPath support team or community replies. Their knowledge is useful for other users who might face the same problem in the future. They have an MVP promotion where if I answer more than 100 questions, they provide us freebies or maybe certification vouchers. That's a good thing that they're doing to grow the community. I'm really enjoying the community members' involvement as well as their support shown during any problems that we face. I have also used Power Automate, and the community support of Power Automate is not that great, but the community of UiPath is very responsive.

It is expensive. Its licensing structure should be improved. They can introduce a license structure where they charge you on a per-minute basis rather than a full upfront payment. 

In UiPath Academy, the certification that they provide at the end of every course can serve as a good motivating factor for somebody who's learning it. That is a good thing, but one of the negatives is that previously, the certification program was free of cost, which helped a lot of developers to become certified developers, but recently, they introduced a paid certification course. I wasn't expecting that move from them. I would like them to go back to their initial certification method which was free of cost.

Sometimes, we do find that the bots misbehave or there are bugs that prevent the bot from executing even when the business cases are completely listed out. It could be that the cloud Orchestrator doesn't send the trigger to the runner systems to start the process because of small internet fluctuation. Sometimes, we find that the processes are killing the execution themselves and going into a halt state without any errors in the program. So, we do see some reliability issues, but these happen once in 20 or 30 instances. They are not on a regular basis. However, when that happens, it does create panic, and we have to immediately rectify it. If they can focus on that, it would be good.

I have been using UiPath for three years.

It is great. We are able to scale at a rate faster than what we had thought of because of the way we are able to develop our processes. UiPath literally automates most of the processes that business users are doing. So far, we haven't had any use cases that cannot be handled with UiPath, which helps in scaling implementation at a faster pace.

We have about a four-member team with analysts as well as developers who work with it, but the developers basically handle all the IT-related tasks. 

We are a manufacturing company, and we have deployed our solutions in almost every department. We have finance, planning, control, human resources, sales, and supply chain. We have 15 to 20 in each of the departments, and they are saving close to three hours individually. Overall, our estimated time savings are upwards of 100,000 hours annually. 

Our current usage of it is 30% to 40%. We still have a lot more potential to tap. We are still on the journey to reach 100% of user involvement where everybody is aware of the process. We are yet to hold the discovery workshops with all the users so that they're aware of the process. Right now, it is limited to a few people within the departments, but its usage will increase with time as we continue to automate processes at this rate.

We use UiPath Academy for the certification or onboarding of new members. When we onboard new members, we tell them to go through the UiPath Academy to get an understanding of the tool. It is free of cost, and it covers all the required modules for becoming an RPA developer. We use it extensively during the initial days as a developer, and over time and with experience, we learn directly from the tool.

They have a very responsive community. Sometimes, within minutes, we get a response to our query. We are quickly able to understand the solution that they provided and implement it. If it is a complicated problem, sometimes, the UiPath moderator from the UiPath company responds to the query and resolves it. If it is not resolved, we can directly contact their customer support. We are enterprise users, and we get quick responses to the queries that we raise. I would rate their support a 9 out of 10.

Positive

In between, we used Power Automate just to see the functionality, but we did not find it as intuitive as UiPath. We gave up on Power Automate, and we are now full-time users of UiPath.

I was around when it was set up. I had personally taken care of the installation. I found it easy and not at all time-consuming. I was done with the process in a couple of hours. In about four or five hours, I was done with the installation and setup of Studio and Orchestrator, listing the licensed accounts, and deployment of the random bots. Everything was completed in a matter of no time. I am not directly related to the IT department. I am just a developer, but I was able to handle it with no external support.

We did it in-house. We only contacted UiPath. They delivered the license keys, and we just keyed in the license keys, and it started working. That's it. Nothing else.

It is lightweight in terms of maintenance. There's no maintenance at all. It automatically handles all the upgrades via the cloud. There are no issues. It requires zero effort from IT.

Overall, you don't have a lot of savings because of expensive licenses. The licenses are quite expensive, and they are not cheap. It saves money but not significantly. However, we are not focusing so much on the monetary benefits. We are focusing more on the quality of output and time savings.

It does reduce the cost of digital transformation, but that happens after a year or two from deployment. Immediate benefits are not evident, but within a period of one to three years, we are able to make a huge amount of savings in terms of time. 

This digital transformation doesn't require expensive or complex application upgrades or IT application support. We didn't have any issues, and we never needed IT to support the UiPath tool. We have been directly using it as it is without making any changes. The impact of this digital transformation on our infrastructure was zero. There were no costs involved. It was used as it is without any changes in the infrastructure.

During the initial two years, we hadn't reached a breakeven point. When the development was going on, we had both costs. On one side, the manual effort was going on, and on the other, there was the licensing cost. So, we didn't have cost savings. After the bot was implemented or after about one and a half years, we were able to receive proper monetary benefits or what we call a breakeven point. So, when we started eliminating human activity, that got converted to cost savings. The accuracy of the process also indirectly improved our customer satisfaction. All in all, we were at a breakeven point, after a two-year period. That would be the general thumb rule for most organizations. So, at an immediate level, we did not receive monetary benefits, but after a period of about two years, we received monetary benefits or savings.

We rely on UiPath Academy for knowledge during the initial days, and it saves a lot of time. We don't have any monetary spending for setting up training because it is available for free. So, we have made some savings. It has saved us time and money, and it has been helpful in getting employees up to speed on the solution.

It is expensive. Every product or component is built separately. All the components have a separate fee. UiPath Studio has a license cost. The cloud has a license cost, and bots have a license cost. These costs are recurring on a yearly basis. So, every product or component has to be licensed for a year, and on expiry, you have to renew it.

Their licensing structure should be improved. The cost of a bot is a lot. It is more expensive as compared to some of the competitors. It is probably $8,000 for an unattended bot. When I did a search on the internet, I found that other vendors offer much better plans. I would like UiPath to introduce some flexibility in the licenses. Instead of a full license, they can maybe introduce a license structure where they charge you on a per-minute basis rather than a full $8,000 upfront payment. If I'm just spending eight hours on the bot, the bot should only be charged for that time. There could be a per-hour rate. A plan like that would be beneficial.

Initially, it will be expensive, and it also won't be as per the initial thoughts that it is going to be a quick solution that saves a lot of time. With time, you can achieve cost savings but not immediately.

We had our eyes on UiPath from the beginning. We did not focus on others.

My advice would be to not use RPA as the only solution. You also have to use other complementing features, such as optical character recognition, so that the overall solution is usable. Just RPA can't solve all the problems.

There should be proper change management to bring awareness about the impact of RPA. A lot of time, people misunderstand and take it in the wrong sense that they might lose their jobs. The fact is that RPA can't automate everything, and skilled people will still be required for doing activities. We can only automate a certain set of manual activities.

I would also advise taking one step at a time. Automate a few solutions, check the user feedback, and then start scaling up rather than immediately scaling up without getting the user feedback.

I would rate UiPath an 8 out of 10. Overall, I have no complaints. Studio, Orchestrator, and all the other tools are top-notch. They are being updated with new features on a daily basis. The product is extremely good, and I have no complaints regarding that, but the license is something they can focus on. They can introduce some innovative plans for procuring the license.

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

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

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

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

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

I have been using the product for six years. 

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

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

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

Neutral

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

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

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

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

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

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

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

We have an online report, and our management tasked me with recreating it, but they don't allow bots to create things on the website. I'm responsible for the automation and engineering work, and they wanted me to evaluate the performance of our systems and solar panels. I need to go to the manufacturer's website and download the monthly report corresponding to our factory site. 

Each month, I need to go to the site, get their readings, and create a report. It's a repetitive task that takes about four or five hours. UiPath enables me to automate the finance side of the report.

Generating all these market analyses and data reports from various websites can be time-consuming. It might require a whole team with its own manager to check and update the docs. However, when UiPath came into play, we could automate a lot of that work from different platforms. That was the start of a digital transformation at our company. It saves about eight hours per report. 

UiPath decreases human error. A lot of the reporting on product quality was done through manual data entry into the database system. There is potential for human error. Now, we can a lot of that information automatically and perform the data analysis with UiPath. Since we no longer need a designated person to do the data analysis, we can save around $200 to $300 monthly.

UiPath is easy to use and learn. With some experience in automation, I could learn the solution in three or four hours. It's easier to build automations in UiPath compared to other tools. UiPath has a feature that allows you to build automations quickly. You can build your workflow in under 10 minutes. In UiPath Studio, you can do browser automation by recording it. You can set up flows where you click through the buttons on a website. For example, there's a button where you have to click to verify that you're human. That's something you can add to the flow. 

Having a workflow is beneficial. At our monthly meetings, we rectified the revenue generation, etc. We analyzed all these systems' performance and costs to create a plan and saved a lot of money doing that.

We're developing a use case for automated communications mining using Salesforce for one of our teams. It will be helpful, but we haven't implemented it yet. We have several reports and a script to perform this automatically. We will rate the responses from our team members and the outside groups we are using. 

The UiPath community is very helpful. When I started using UiPath, I had no clue about it, so I watched a few videos and learned how to do most of the integrations. I also reached out to some colleagues on LinkedIn who directed me to the Sri Lankan user community. They were amazing.

I would love to see UiPath create a reporting application that you could deploy on the side and feed data directly into it. That would be an amazing tool to have. Microsoft has this data migration interface, so if you create an automation, it checks everything going into it. 

I tried UiPath a couple of years back for another project and worked with it for about a year and a half. I also worked with it more recently, and the experience is different.

We had some performance issues in the first few weeks. Apart from that, UiPath has been running okay.

The cloud component of UiPath makes it scalable.

I rate UiPath support seven out of 10. You can contact enterprise support. They're always ready to receive our calls and provide recommendations. 

Neutral

We previously used Microsoft Power Automate. Since we are using Microsoft ERP and CRM systems, all of our automation systems need to be compatible with Microsoft. We could use Power Automate for free, so it made sense to stick with one vendor. 

UiPath is easier to understand and use because we can record actions, and it has an amazing support community. It is also competitive in terms of cost. If you are sending information to databases with Power Automate, you need some subscriptions to PowerApps and Power BI. It costs you about a hundred dollars to get started. You can download and use UiPath Studio for free. 

Compared to our older platforms, UiPath is easy to install and integrate. On day one, you can deploy it to your system in a few minutes. Our previous solution required more infrastructure to do the automation. UiPath has UiPath Studio, so you can play the flow and record all your inputs. The main advantage is that you can build a solution in minutes. It's effortless to get started. 

UiPath is reasonably priced. 

I rate UiPath eight out of 10. 

We are using it to automate business processes in the organization.

UiPath has impacted our operational efficiency quite a lot. There are a lot of scenarios where it has helped the end users. We also have benefited financially from it. We have streamlined the processes to an extent. We initially started with a basic data migration process, and now, we have our own intelligent automation and hyper-automation framework. We just get the requirement, put it in the framework, and start automating. We have progressed a lot.

UiPath enables us to implement end-to-end automation. There are certain instances where we do not get end-to-end automation, but those are the things that are out of RPA's capabilities.

End-to-end automation is important because we can showcase our capability more efficiently in front of our management and the client. We can show that something can be 100% automated if there is a use of 100% automation.

They have UiPath Academy. When UiPath was new, we did not have any online resources to go and learn. The YouTube community was small. There were no courses on Udemy or any of the online platforms. The offline platforms were also minimal. UiPath Academy was one place where we could go and learn and prepare for the exam. I got certified when UiPath certifications were free. I have done all the learning from UiPath Academy. As I move up in my role and responsibilities, if I want to learn a few more things, UiPath Academy is still the best place. You get a very crisp and clear understanding of everything.

We use UiPath’s artificial intelligence and machine learning capabilities for hyper-automation. In my understanding, RPA in the initial days was limited to redundant process automation, whereas now, the use of AI Fabric and other components makes the automation more intelligent. We can add decision-making to existing automation. There were many processes where we had stalled the process just because the next step was a decision-making step, and someone had to come and make a decision to move forward. Now, we have our own AI team to build the code that can make decisions on behalf of a person and also learn from the existing behaviors. That helps quite a lot.

UiPath saves time. It saves about 50% of the time. It never saves 100% of the time because we also spend a lot of time maintaining and doing enhancements to the process. Processes are never stable.

We have integrated it with multiple tools. The outcome has been very good. There have been challenges at times with the development, but the integration has been smooth so far.

Computer Vision is one good feature. AI Fabric is another good feature. The holistic Orchestrator platform is another feature that is very useful.

The RE Framework provided by UiPath is quite extensive. It solves a lot of problems and gives us a lot of time back. We do not have to create our own framework.

UiPath is more user-friendly than other RPA solutions that I have used. UiPath also has the biggest community.

Automation Hub needs to improve a lot. About two years back, it kept on crashing. It has improved a lot. We use it but not to a great extent. We try to build our own dashboards by using any of the data analytics tools.

It should give real-time data, and the integration with the servers is not that great. It can be because of the infrastructure that we have.

They can also consider integration with other automation tools because nowadays, a company does not have one automation tool or RPA tool. A company has multiple RPA tools. They can think of integrating the data from other automation tools in one automation hub so that it becomes centralized.

I have been using UiPath for close to seven years.

UiPath is quite stable. I would rate it a nine out of ten for scalability. It does crash sometimes. That could be because of the infrastructure we are using.

The reliability of any process that goes to the end user is tested with a set of data. We do rigorous testing because, at the end of the day, any error in production ends up in a financial loss, so we test the automation that has been built to quite an extent.

I would rate UiPath a seven out of ten for scalability. No technology is 100% scalable. As technology evolves, new features, such as GenAI features, need to be added. Scalability-wise, it can never go to a ten. Another reason why I rated it a seven is that I want Automation Hub to be scaled to its full potential. It has not been scaled up properly. I have got this feedback from different people across the organization.

The organization I belong to works on the use cases for building automation for given processes. We have around 15 developers doing this work.

I would rate UiPath support a ten out of ten. They have been quite supportive when we have raised any query with them.

I have been in the automation field for the last 12 years. I started with RPA with Blue Prism. I have worked with almost all main RPA tools such as Power Automate, Automation Anywhere, etc. I find UiPath to be the most user-friendly. There is the ease of having all the activities in the same panel. You can have the Studio setup and you can review the code as well with the analyzer. It gives a lot of flexibility when you are developing.

The one feature that is very good is that the marketplace is open. People can build their own set of activities and post them there, which is very useful. I myself have built a lot of activities. I have also used activities by other developers to complete my work. The marketplace is very helpful.

UiPath has the biggest user community. Its community is bigger than Power Automate, Automation Anywhere, and Blue Prism. Other than the community, there are also several groups. There are a lot of developers. If you are stuck with any issue, which is quite common, someone will have a solution for it.

Developing automation with UiPath is much easier compared to Power Automate, Automation Anywhere, and Blue Prism.

The deployment is handled by another team. I do not handle the deployment because the infrastructure team handles it. It should be a one-man job. It is not that difficult.

The deployment duration of a process depends on how big the process is and how much time and resources it requires for development. Usually, it takes two to three weeks. It can also take ten weeks depending on the process. 

All tools require maintenance in terms of upgrades, but that is probably handled by UiPath. We only maintain our own processes. If there are some changes to the selectors or any of the UI components, we have to update the project.

With RPA, it takes one or two years to see an ROI. It is not cost-efficient till then. When you start building hundreds of processes and utilizing the full capacity of the bots to work 24 hours, you get a good return on investment. Initially, it was expensive, but as we scaled up, we could see an ROI. We have seen a good profit.

Initially, the ROI is less. It is about 5% to 6% per year, but as the processes mature, the headcount reduces, and the human intervention also reduces. It eventually moves to 30% to 40% ROI.

It is the most user-friendly RPA platform, but it is also the most expensive RPA platform.

I would recommend UiPath to others because it is the most user-friendly. It is also developer-friendly because of the community. It also works across systems. These are the three reasons for recommending it.

We run a roadshow across the organization to understand which processes are redundant. We try to understand which part of a process can be automated by using the general RPA automation and only one tool. We also categorize them in terms of what can go under intelligent automation where a certain amount of decision-making is required. Another category is hyper-automation where we try to understand how to include different tools, such as machine learning code, AI code, NLP data set, or data mining set. If we have an existing tool for data mining and process mining, the final steps can be automated. These are three major criteria. For basic automation, we try to assess the type of automation. Is it desktop automation? What kind of resources are required? Do we need an attended automation or an unattended automation? Based on my experience, almost all of them are unattended automation. We then try to pull in the use cases, prioritize them, and start automating.

UiPath keeps on enhancing its product. Four years ago, there was no AI Fabric or Automation Hub, and now, we have all those things. They help a lot in delivering the project and having a prototype view for all the projects that are running.

Overall, I would rate UiPath an eight out of ten.

We have a lot of use cases for UiPath including automation of processes and reconciliation.

Building automation using UiPath is easy.

It helps our operational efficiency by saving time and reducing costs. Manually processes that take an hour can be done in five minutes using UiPath.

The most beneficial feature of UiPath for our workflows is the seamless database connectivity.

UiPath facilitates end-to-end automation for well-defined processes. This eliminates interruptions caused by manual steps within the workflow.

The UiPath User Community is large. There is a lot of interaction and sharing making it easy for us to find answers to any issues we may have.

The biggest benefits we have seen using UiPath are the cost and time savings.

It has helped save around ten percent of costs.

The UiPath Academy courses are great. They have a lot of helpful courses.

UiPath has reduced human error by 70 percent.

UiPath excels at integrating with a wide variety of systems, including on-premises systems, legacy systems, and web pages.

The high cost of UiPath licensing significantly reduces the value we get from the solution. A large portion of the cost savings we achieve are negated by the licensing fees.

I have been using UiPath for four years.

I would rate the stability of Uipath eight out of ten.

I would rate the scalability of Uipath eight out of ten.

The technical support is great with the premium service for enterprise-level clients.

Positive

I'm certified in Automation Anywhere and currently use Microsoft Power Automate. However, UiPath seems better suited for enterprise-level automation. Unlike Power Automate, UiPath is system-agnostic. It can connect to any system, regardless of platform, making it highly versatile. On the other hand, Microsoft Power Automate prioritizes integration with other Microsoft products. Connecting legacy systems with Power Automate often requires purchasing premium connectors and potentially hiring an expert for configuration.

The deployment took around two weeks to complete.

We engaged Deloitte as our consulting firm for the UiPath implementation. While we handled a significant portion of the on-premises work ourselves, their team provided some technical assistance. Overall, I would rate their services a six out of ten.

UiPath promises a 50 percent reduction in operational costs, but the high licensing fees may consume most of those savings.

I would rate the cost of UiPath eight out of ten with ten being the most expensive.

I would rate UiPath eight out of ten.

We have around 15 users that work with UiPath for the attended bots.

UiPath Orchestrator requires regular maintenance and updates.

I recommend UiPath. The only negative area of UiPath is the licensing fees. 

I use UiPath for work projects that involve various applications, including license rebate processing and healthcare licensing. I develop reusable components for these projects.

Specifically, the process involves launching different licensing websites and extracting essential information such as license number, status, effective date, expiration date, and any disciplinary actions. This data is collected from providers like physicians, dietitians, opticians, and speech therapists. We validate the extracted information against existing databases or applications, updating records where necessary.

This validated information is crucial for determining the approval or denial of applications, such as those related to provider enrollment. Essentially, my work centers around creating processes with defined inputs and desired outputs.

Currently, I'm focused on a project within the manufacturing sector, specifically a constant bidding branch. Here, we gather order information for stakeholders, including tracking numbers, tracking statuses, and approximate order values. We store this data in an Oracle database, generate a CSV file from it, and distribute this file to stakeholders via email.

Building automation using UiPath is easy for developers. It is easy for them to manage and start building with the automation.

UiPath empowers organizations to improve their staff's time management and become more cost-effective. By automating routine tasks, it frees up employees' valuable time to focus on higher-priority work. 

UiPath enables end-to-end automation. Our process begins with meeting stakeholders to determine which processes are suitable for automation. We assess if existing tools are sufficient or if new ones need to be implemented. We also identify applications that automation could potentially replace. If all requirements are met, we obtain sign-off for automation and prepare process documentation, such as Process Definition Documents. We then consult with business stakeholders and obtain managerial approval on the Solution Design Document. This phase can take several weeks and involves outlining the specific solutions and applications required for the automation. Next, we create a video demonstrating the automation workflow and explain the process to stakeholders. After securing sign-off from management and SMEs, we begin the development phase. The completed development is sent for UAT and then moved into production. We typically monitor the automation in production for one to two months. Any errors trigger email notifications, allowing us to promptly address issues within UiPath Studio and re-deploy to the live production environment.

The UiPath User Community is a valuable resource for developers. It allows us to share knowledge and find answers to questions or issues we encounter, without needing to submit a support ticket.

It has significantly improved our efficiency by automating many manual tasks, leading to a noticeable benefit for patients. Now, thanks to automated benefit processing, patients receive instant approvals or denials from their insurance providers.

Our company encourages us to complete UiPath Academy courses to further our understanding of Robotic Process Automation. These courses equip us with the skills and knowledge necessary to solve complex problems encountered in real-world scenarios. Completing the Academy courses and obtaining certifications can be beneficial not only for career advancement within our company but also for understanding new features and process flows implemented in future updates. Additionally, these certifications can be valuable when transitioning to other companies as they demonstrate our expertise in UiPath products.

Human error is minimized by utilizing exception handling.

UiPath helps free up our time.

The most valuable feature is the easily accessible tool, such as the ARI framework, which I have used extensively. My interest in the ARI framework has grown significantly because the templates are built directly into UiPath, making it possible to automate more complex processes, while also simplifying the development and understanding for developers.

The UiPath Community Edition lacks some key features that developers find essential for learning and building their knowledge base before transitioning to the paid Enterprise Edition. To provide developers with a more comprehensive evaluation experience, UiPath could consider including all features in the Community Edition for a limited trial period. This would allow developers to fully test the solution's capabilities before making a purchase decision.

I have been using UiPath for four years.

UiPath operates reliably around 80 percent of the time. However, automation speed can sometimes be hindered by internal applications.

I had to contact their support once and they were extremely helpful in resolving my issue.

Positive

While I have experience with Automation Anywhere, I find UiPath to be more user-friendly and offer a more robust orchestration tool. Although Automation Anywhere offers child bots and AI IQ bots, it is not as well-suited for handling complex automation scenarios.

The initial deployment is straightforward. We can sign up with UiPath and set it up on our local desktop, or we can deploy it from our cloud cluster.

I would rate UiPath eight out of ten.

The amount of maintenance required depends on the project and the bots being used. On average maintenance is done monthly.

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.