UiPath Platform Reviews

I use this solution for automating customer processes. I have been working with this for almost seven years and am responsible for automating various business processes across different industries such as finance, telecommunications, and airlines. I have experience working with numerous sectors and do not use it for personal reasons.

Document Understanding allows me to track information not only from structured documents but also from unstructured documents through artificial intelligence and machine learning techniques. These are excellent tools. Additionally, the process understanding enables me to track and manage document processing effectively. Ease of building automation includes utilizing tools to record the process and generate the initial process design document.

I have just generated the default pilot. I believe another option for the tool could be voice interaction. For example, similar to using assistants like Alexa, it would be beneficial to integrate voice commands with the UI to create an Excel spreadsheet and populate a data table.

I have been using the solution for seven years.

I have experienced stability issues.

I have experienced scalability issues.

I would rate customer service a ten out of ten.

The number of solutions we select depends on client needs. My company uses various software platforms without preference, and it depends on client requirements and objectives.

The initial setup is efficient if all infrastructure requirements are met, faster than Azure's requirement. It could take about an hour.

We have our checklist that describes every document. We ensure everything is checked. We are a consulting company, and we have expertise in this field.

If you lose higher Wi-Fi parameters, it saves additional time. The license cost is slightly higher compared to other providers, yet the benefits are justifiable.

The developers are very client-focused, always looking for feedback and adding additional value in every version. I was one of the first UiPath MDPs, and it enables a lot of learning opportunities. If you're keen on learning, you can benefit greatly.

UiPath is accessible with various language options, breaking down communication barriers. Many developers benefit from this, especially since it's free. Fatigue can lead to errors, but automation helps reduce such issues, particularly in financial processes. In terms of digital transformation, UiPath accelerates the process and reduces costs. 

Overall, I believe UiPath is the best tool available. I rate the overall solution ten out of ten.

We currently use UiPath to process birth certificates. One of my tasks was to apply OCR to the birth certificates and use a named entity recognition model to extract details like the names of the individuals, parents, and the place of birth. The project requires us to handle certificates from all 50 states, and every state uses a different format. 

We're supposed to be doing intelligent automation, but we're not there yet. I work in the applied analytics and statistics section, and we're supposed to find ways to inject more advanced analytical methods into some of these places where we can automate. Our IT department has a CoE that conducts intake processes. They use Automation Hub to review each process, and the executive governance board votes on it. I don't know how they decide internally because I'm not part of that. 

Automation through UiPath provided a framework and a low-code solution, which generally improved the process. It reduced the burden on the workers, freeing them to do what they wanted. 

It is also utilized in identity governance, especially within IT environments. For example, say I want to install a particular piece of software on my computer. There's a process to request access, and it goes through an approval chain. Ultimately, it gets to someone who has to click a button or provision an account. Someone will get an email and copy-paste the stuff from the email into another system and click "provision." 

And when an employee leaves or switches job roles, they no longer need access to a particular system anymore, so you must remove that access as soon as possible. Automation helps. Governance is one area that we would like to use it in more.

UI automation is helpful for interacting with legacy systems, mainframe systems, and various web applications. Someone might use all those things during their jobs, and many of them don't necessarily have APIs, either.

Although improvements have been made, such as auto-healing, there is room for improvement. Changes in the UI can break automations. If you upgrade from Windows 10 to 11, you may need to rewrite some of those UI selectors completely. That is probably the biggest weakness that I can think of.

I have been using UiPath for four or five years.

The solution can be fragile, but there have been significant improvements over the years. The unified target framework, which considers strict, fuzzy, and image matching, helps to stabilize the application somewhat.

UiPath has been able to perform as our organization grows or as the demands on UiPath increase.

In my previous job, I interacted directly with UiPath support, and they were always effective. Currently, support is accessed through IT, which escalates issues if needed, so I have less direct interaction with customer support.

Positive

I've used Python and VBA and experimented minimally with Selenium, but they're not as strong when it comes to UI automation. I've also used Power Automate for Microsoft products. Sometimes, I want to automate Outlook, but I don't want to ask the security to enable the UiPath activity to pull emails. 

We've saved time and reduced human error. 

I rate UiPath eight out of 10.

Our primary use case for UiPath revolves around document imaging, specifically scraping data off documents and digitizing them. We only use it in our accounting department and haven't expanded it to the rest of the company. We've seen some success with the projects on the financial team, but we might be resource-constrained to get other departments involved. It's hard for them to adapt to new technologies. 

UiPath has improved the accuracy of data entry from our invoices. Processing thousands of invoices is time-consuming. One outcome we've achieved is expanding the data collection from the invoices. They were only capturing dollar amounts, but these invoices have tons of other information that was just going to waste and could be analyzed. Now, we're capturing the data and analyzing it. It will be a significant benefit, considering how we do business.

We've advanced our green initiatives by recycling invoice paper after digitizing it and reduced the costs of pulling this information into our system.

The most valuable feature is the general automation that UiPath offers, especially in improving data collection which allows for a more comprehensive analysis of information on invoices.

There is a need for better autopilot features to enhance the functionality of UiPath.

I have been using UiPath for about a year.

UiPath is stable so far.

UiPath can scale as our business grows.

Customer service and support have been excellent. I would rate it highly for their responsiveness and supportiveness.

Positive

Previously, we used a service that scanned documents and sent them back in EDI format. We switched to UiPath because the previous solution couldn't handle certain document images unless they were in native PDF form.

The initial setup seemed straightforward.

We used corporate for the setup. Corporate used UiPath as a partner for support.

While there hasn't been a financial return on investment yet, the team is happier not having to manually enter invoices, which is a qualitative benefit. However, I foresee a financial return in the future.

UiPath's licensing seems straightforward, and the pricing is comfortable for the corporate leadership. They made an outright purchase, knowing the full cost and expectations.

I rate UiPath 10 out of 10.

We primarily use UiPath to move data and consolidate data formats efficiently. We are involved in claims management within healthcare. We are also exploring DevOps tooling and CI/CD pipelines, and automated testing.

UiPath has significantly improved how we claims. We provide this product for our customers directly, so we want to ensure they reap the benefits of the automation program. We serve as a product team and make sure that our products are directly open to the customers. Although we are not extensively using AI yet, there is significant interest in the org. We aim to recommend automations to users and intend to develop AI capabilities down the line.

Our teams are heavily using integration service, especially following our cloud migration. Having further insights and program visibility is crucial for longevity.

It would be helpful to be able to double-click and drill down into the data we see in the APIs and get a little more interactivity, especially in the Studio and Studio Web. I want to be able to pull in fields dynamically.

I have used UiPath since 2021, so it has been about three years.

UiPath is relatively stable. I've seen a few bugs in some of their newer tools and Integration Service. There are some issues with feature clarity across platforms, but it's not necessarily a stability problem. Occasionally, cloud may experience downtime, but stability is always reliable. 

Most of the scalability issues from an implementation fall on the customer's side because they don't understand how to scale out their VM presence or set up systems in a way that relies on siloed teams. They're using it on-premises and have to manage the instance with teams outside of their automation team. I haven't had any scalability issues in the cloud. The cloud might go down once a year, but I haven't had issues scaling it, and if it has an outage it's normally not long enough to make a dent.

I rate UiPath support seven out of 10. UiPath's support is quite reliable and significantly better than most alternatives. Some competitors don't get back to you or have meaningful solutions.  

There's room for improvement. They could make their online support pages easier to navigate. They're integrating support with Automation Cloud, which will make raising a ticket more seamless. When you open the ticket, it should automatically provide them information about your deployment.  They're good about following up with you, but getting solutions for some products takes time. 

Neutral

I have always worked with UiPath, sometimes using other platforms such as Salesforce and Power Platform when they better fit specific needs. However, they are not as suitable for making enterprise scale automation.

The on-premises deployment when we started in 2019 was somewhat complex. It's different for every customer, whereas the cloud is consistently distributed the same way, and you can customize it for your business.  

We work with an implementation partner for staff augmentation and architectural support, with a proactive offshore development team experienced in best practices. 

I rate UiPath eight out of 10.

I have hundreds of use cases for UiPath. Mainly, it's used for AP and AR automation, outboarding, HR, and for vendors and customers. 

It's helped us reduce manual work for our employees and customers.

Having expertise in IPaaS has allowed us to create a lot of automation for our clients that they normally couldn't automate. It's a profitable solution in that sense. Also, it automates many steps that normally would require a lot of FTEs to do that work. You can ensure it's being done on time without any human errors.

The UI automation is excellent. Being able to automate clicks on desktop applications and browsers is very helpful. A lot of the other tools are very good at automating online system processes and similar things. However, when it comes to desktop UI automation, they are by far the leader.

They're just starting to add a lot of AI functionality, so there's definitely room for improvements in leveraging the latest AI technologies - like GPT, et cetera.

I've used the solution for about eight years. 

The solution is very stable. I'd rate its reliability nine out of ten.

It's extremely scalable. I'd rate scalability ten out of ten. 

Most of our technical responses are related to third-party websites changing their designs. You have to deal with those changes. The modern selectors are smarter and can adapt to change. However, if the developer changes a lot of things in the background. 

UiPath support is quite good. Sometimes they take a bit to get back to us, however, most of the time, they are pretty responsive. 

They do have a higher tier of service that costs more, and they are quite excellent. 

Positive

I use both UiPath and Power Automate. We used to use a tool called Win Automation. We switched from then due to the fact that they were prone to failure and did not have enough tools to meet expectations. They have since been acquired by Microsoft, and Microsoft Power Automate is based on that.

I'd rate the initial setup eight out of ten. It's pretty easy to implement. 

We use Azure Virtual Machines to deploy the robots and usually use a lot of the Azure services in conjunction with the robots. The cloud is on UiPath's automation cloud. That's where we have our servers - to manage the robust deployed data on multiple virtual machines.

In terms of maintenance, there are always releases and updates, and then you can usually design your own robots to watch over the other robots, which is really interesting. You have the flexibility to make your own monitoring; if it sees something wrong, you can enter a ticket and then dispatch it to the support team to respond to it. 

My whole developer team is involved in maintenance; however, I have specific support team members. There's 28 developers and seven support team members in that group.

We witnessed an ROI fairly quickly. For the cost of one developer license, you can produce a lot of automation. The robot license is a 24/7 one-year license. If you can run bots 24 hours nonstop on it when you can run many different processes, each process can save hours, hundreds of hours of time for employees. There's also a lot of savings from your customer side on being able to service things quicker as well. That you can't fully quantify; however, you find you can offer better customer service in terms of speed of transaction, et cetera. Even if you spend $10,000 to $15,000 on a robot license, you quickly recover your costs. 

The pricing is very competitive. There are some parts of the solution that are considered consumable, and as you consume more, you increase the cost. However, that's similar to other products out there. There might be extra costs for AI units, robot units, and data services. That said, what they give you out of the box for every license is usually sufficient for most enterprises.

I'm a customer, reseller, and partner.

I'd rate UiPath ten out of ten. 

I would advise new users that the biggest part is to always sync in reusable components. That will drive your ROI much quicker. If you can reuse pieces or design them in a way that they're reusable, then you can use them across multiple processes instead of redoing the work over and over. Thinking modular from the beginning is going to go a long way.

We have a lot of SAP Extract, transform, and load (ETL). We have human resources and time management. We have a very diverse tool landscape due to natural growth. We are in a very early stage of transformation, so we use it to bring information into multiple systems at the same time.

We also have a good few financial use cases related to tax. We work in Europe. Within the EU, there are different regulations, and sometimes, we have very short deadlines. On the third or first business day, we have to get information out of 16 or 17 SAP systems and format them. We have to get them out to Italy and Spain for government stuff.

The objective that we were trying to achieve by implementing UiPath was hard cost savings, but I changed that a little bit. It is not the right technology for hard cost savings. We have now changed it to quality and efficiency, and what they do with quality and efficiency is up to them.

Currently, we only use the core RPA. We joined the company only eight months ago. We worked for another company before, and that company is at a very early stage. We are setting up our CVs and our citizen development program, so currently, we only use core RPA and core automation services.

We are not using AI yet, but we are about to change that with Document Understanding. In the company where I worked before, we used Document Understanding, and it helped us a lot.

UiPath automations have increased the accuracy of our operations. We have a lot of peak sessions with finance and techs. There are quite high penalties if we get something wrong. For example, if we calculate our tax incorrectly and we pay too much, that does not mean we get the money back. If we pay too little, we also have to pay a penalty fee. We have reduced the error rate by over 25%. We saved 1.24 million last year. That is one aspect. The other aspect is the peak time work. We had a team of people coming in on the third business day at 5 am. I had to download all the reports and things like that because they had to get the report out by 12 pm. If they were not out by 12 pm, we had to pay a penalty. After automation, people came in at 8 am, and the reports went out by 10 am. 

I like the low-code/no-code approach and the graphical interface. Among all the RPA tools, UiPath is the one with the easiest interface.

Orchestrator needs an overhaul. They have added so many functions that it is sometimes quite hard to find the right settings. They have a tree hierarchy with the host and the tenant. Some settings you do on the host, and some settings you do on the tenant. You need to know at which level you are to find what you need. It all looks very same.

The other thing that I have been telling them for years is the width of the activity. You cannot change the width. I do a lot of training to show something, and I constantly have to go into the advanced editor to show what is in there, but the big thing right now is Orchestrator.

I have been using UiPath for 12 or 13 years.

I have not had any issues. If something happened, it happened because of the human network.

It is very scalable.

The USA support is okay. I would rate them a seven out of ten.

Their support in Europe is good or very good if you get the right people. I would rate them between six to nine out of ten.

Their support in Asia needs improvement. I would rate them a four out of ten.

I have worked with Blue Prism. I have worked with Automation Anywhere. I have worked with what I call the Microsoft suite, which includes Power Apps, Power Automate, and Azure Logic. I worked very shortly with OpenSpan, later known as Pega. I trained at a university. I trained others in automation as part of the robotics lab at the University of Hanover. We looked at several tools there. 

In terms of comparison between UiPath and Microsoft Power Automate, given the use cases for which I normally use them, they both have areas where they are good. If Microsoft could get their documentation right, the attended series of UiPath would be in a lot of trouble. Given the whole unattended and hyper automation or intelligent automation, which is the main focus of UiPath, you need orchestration. That is where the big bucks and the big savings are, but to get the technology out with the attended bots or shadow IT, Microsoft Power Apps and Power Automate are important because they help people understand what technology can do. What we see very often is that people start with Power Apps, sometimes even with a macro, and then they realize that they have hit a certain barrier very quickly. They come to us. Initially, we take what they have and just enhance it with UiPath, and then over time, we bring the functionality from the macro, Power Apps, or Selenium and migrate them into our things.

Currently, we are on-prem, but we are migrating to the cloud in November. We are currently not using the latest version, but with the migration, we will be.

I was involved in its setup. The Orchestrator setup could be easier. There are a few loopholes that you need to understand. UiPath Studio is straightforward, but the setup of Orchestrator has become a little bit more complicated over time. You need to connect them to bots, and you need to know what type of user you need for what type of robot, which has become more tricky. Overall, the setup of Orchestrator and certificates can be a bit challenging.

In terms of the implementation strategy, we took a test server and put it on. We did some testing with our network and information security team, and once they were happy, we moved it out to production.

For the current implementation, we did not take any help. The first one was done by a partner, but they did not do a good job. I did the second installation on my own because I knew how to do it.

In the previous company, they had a partner system. 

I do not like the enormous jumps that they have had in the past. The ROI has become a lot harder because of the pricing changes. When you have time to plan for it, the ROI is there. If it was cheaper, it would make my life easier, but on the other hand, it is worth it. These jumps year after year are a problem for me because then I have to go back and say that prices have increased by 30% percent, and I get asked, "For what?" It takes a lot of time.

In this company, UiPath was already chosen. In the company before, I looked at all the big ones. I chose UiPath for the ease of use. 

I would advise finishing UiPath Academy courses. After you have finished them the first time, finish them the second time.

I would rate UiPath a strong eight out of ten.

In the past, we have used UiPath to automate repetitive manual processes for companies in the finance and banking sectors, but healthcare is our current focus. This industry involves processing tons of data from patients, customers, and doctors, so it's a huge field. 

Previously, I developed bots for compliance at financial companies. I've also created processes for reading PDFs, sending emails, Excel automation, logging, and exception handling. We have also contracted with insurance companies that need to pull data from emails into their main enterprise application.

The healthcare companies cannot provide us with direct access to their systems for security reasons. We are currently accessing their network through a middleware system so it doesn't compromise their security. UiPath doesn't work on that third machine and cannot retrieve the values as it should. If we scrape data from the web, it will get to the HTML that is behind the site. 

When we are accessing the third PC, we cannot get to it because it is a desktop machine. We are using the completed version activity, which is working mainly on the image image-based activity. This capability is available in UiPath, but I don't think Power Automate or Automation Anywhere can do this. It helps because we don't need to do any coding. 

UiPath tends to be deployed on the cloud, so clients can minimize their on-premise footprint. We deploy on-premise and cloud-based UiPath depending on what our clients want. For some companies, uploading data to the Orchestrator on the cloud is potentially a security concern that hasn't been resolved by the UiPath developers. Power Automate has an advantage in that regard. 

Our employees use the company's credentials to get training from the UiPath Academy and obtain certifications. I have a personal account on UiPath Academy, but it has some license issues. The academy is helpful because UiPath is implementing new features every three months or so. It's all about the documentation. We can learn about new features and do more. With more knowledge, we can develop something bigger.

UiPath reduces costs by eliminating human labor. Let's use an insurance company as an example. Let's say they have employees who are responsible for reading emails. Every day, they receive information via email from the customers, and their job is to retrieve the details and enter them into the main database. The average insurance company receives 400-500 emails daily. These people will spend the whole day completing the task of manually transferring data to their main application. 

We have a bot in pre-production that can handle 1,100 emails daily for the company. It has a significant impact on the efficiency of the operation because the bot can input the details into the database quickly and without any errors. The employees who were responsible for this work are now monitoring it and also learning about UiPath at the same time. It is a great tool for increasing productivity, thereby proportionally increasing the company's profits.

The first company I worked with had 20 employees in their compliance department working on some PDFs. The company had to send emails to around 6 million customers. We deployed the bots, and five bots could do the work of 10 employees. The company kept the other 10 employees but reassigned them to monitor the bots and fix errors. They also learned to develop their own bots. They could cut 10 positions and save money while improving productivity. Those employees weren't working as fast as the bots and cost more money.

The solution also greatly reduces human error. In the financial compliance use case, they were dealing with upwards of a million rows. That was labor-intensive work, and no human could complete the task in under three days manually. Sometimes, we would have some errors in which the values were reversed by accident because humans make mistakes when they are tired. In this kind of work, we're working with digital amounts and currencies, and we are applying mathematical formulas to the amounts, like credit, debit, or some business calculations. 

UiPath doesn't have large hardware or software requirements. We only need one physical PC on the client's premises. That computer requires some minimum specifications, such as a 1 terabyte hard drive and an i5 processor. We need that computer hardware and a license for the client. 

If the client doesn't want to purchase an enterprise license, UiPath offers a community version. There are no restrictions on the features, but it can only run one bot at a time. The enterprise version can run multiple bots. If our client only needs one process, we can provide them with the community version and deploy it on their PC. 

UiPath can free up employees to work on more important things. One of my colleagues was doing some tedious work manually, but once the bot was in place, he only needed to click one button to run UiPath, which extracts all the data and updates the Excel spreadsheet in 10 or 15 minutes. Previously, he spent up to six hours preparing the data before he could complete the other tasks. The important work was being delayed every time. It increases productivity, which benefits the company. 

UiPath's most valuable features are its UI automation activities like scraping and manipulating data. We need to scrape the data before we can manipulate it or save it in another application. I think that part is very valuable and important.

Having worked with other tools like Microsoft Power Automate and Automation Anywhere, I find UiPath to be the most user-friendly because it provides all the actions on the side, and we can just drag and drop them. It's a simple interface that we can easily understand. Automation Anywhere has a more complex interface. UiPath is straightforward enough that our junior employees can easily pick it up. 

UiPath's ability to offer end-to-end automation is critical. We typically provide our clients with a simple demo of what UiPath can do. After that, they provide us with details about their end-to-end processes, which we use to determine what can be implemented through UiPath.

For our healthcare client, the initial assignment was to scrape the data from the website and put it into Excel. Later, they decided that they wanted the data in another application, so it could be stored in the main database. We constructed an end-to-end process for maintaining a million records in their primary database.

I also like the UiPath Community forum. I go there when I get stuck with anything. When I run into an error, it's easy to find the answer. The community is highly active. If I post a question, I can usually get a response from community members in an hour or two. 

I have tried a bot that uses UiPath's AI capabilities, but I didn't develop it. It's a portal for patients to make appointments and check into reception at the hospital. We implemented ChatGPT on an Android device, so customers can ask questions and get information. 

We also developed a bot that can derive the same types of data from PDFs with different structures and formats. For example, let's say the patient's name is on the first row on one form, but on the third row on another. We can configure a bot to extract the name regardless of where it is. We can train our ML module by telling it when the data is wrong and running it again. Now, it's mostly accurate.

I would like UiPath to improve its screenshot feature. It should have the option not to take screenshots unless the user specifically allows it. Sometimes, it is a security issue for companies that do not want to share screenshots of the main application. Another thing I want to see is a standalone mobile application that we can run anywhere. I would like more cross-platform application support.

UiPath can get unwieldy if the process becomes too big and complex. I had one client based in Saudi Arabia that had an application with 1,500 pages. Once the bot we were developing got much bigger, the application started having stability issues. It performs well in typical cases, but once we exceed that average, the application starts to crash or behave abnormally. 

I have used UiPath for four years.

Overall, UiPath is stable for most processes, but Power Automate is better at handling large, complex projects.

I have worked with Microsoft Power Automate and Automation Anywhere. The primary advantage of UiPath is that it's more accessible than the other solutions. You can learn UiPath without any knowledge of programming or computer science. It takes only about a month to learn the tool, even if you have no skills. For example, if you're a blogger and you want to automate posting to the website, you can do that through UiPath, so it is beneficial for personal use and commercial use. 

The other advantage is cost savings. UiPath saves organizations some money, and it's more accurate than Power Automate or Automation Anywhere. Automation Anywhere is my third choice. Power Automate comes in second place because It was developed by Microsoft, and most enterprise companies have a Microsoft subscription. If their license includes Power Automate, they prefer to use that instead of buying a separate subscription for UiPath. 

Many companies are switching to Power Automate because of this bundled licensing. The UiPath enterprise subscription is somewhat expensive. Microsoft can provide the same functionality, and it integrates with tools like Excel and Outlook. Companies can get all those tools within the same license, so that's an advantage Power Automate offers over UiPath.

Another advantage of UiPath is that you can also work with image-based processes. If we cannot get any selectors or access the HTML code behind the application, we can use image-based processes. This feature isn't available in Automation Anywhere. UiPath has the AI center, and Microsoft also implements AI in Power Automate processes.  However, Automation Anywhere cannot use AI in their product.

My current company is smaller, so I'm responsible for multiple tasks. I am the requirement gatherer, developer, and deployer. At my previous company, they had a business analyst who talked to the client and made an inventory of their requirements that he provided to us. Then, my only task was to develop the bot. It was the other team's duty to deploy the bot on the client's physical machine. 

The process involves three steps. We need to connect UiPath and provide the logs. Our client can access the Orchestrator to see logs of what the bot is doing online. He doesn't need to physically access the machine. There is also middleware called the UiPath Assistant that we use to connect UiPath to the Orchestrator. 

The number of staff needed for deployment depends on the complexity of the processes. If it is a single process, we don't need a deployment person or team. The developers can deploy the bots. My company has five developers, so everyone is developing their own bots and handing them over to the deployment team. For every five developers, we have two deployers. If the five developers are developing automated bots daily, we need only two deployers to deploy them on the machine. Also, if we want to have a backup version, we can deploy it on GitHub to make the repository and organize everything.

The maintenance aspect can sometimes be difficult. Exceptional cases can arise during the process. When we initiate some processes, we need to monitor them for about 30 days. We don't monitor some processes because we're not seeing any errors or exceptions. We have to monitor other bots, stop them as needed, handle the exception, and run them again. After 30 days, the bot should be mature enough to handle the exceptions without intervention. 

UiPath offers an excellent return. For example, a recent client in Pakistan was scraping data from a website with 349 products. His job was to scrape the title, price, and variants and place the data in an Excel spreadsheet. He was working all week alone, so I proposed UiPath. I told him UiPath has a function called "Extract Data Table" that can scrape all the details of the products and just dump it into Excel in five or ten minutes. He was impressed, and I developed the bot in front of him. 

Now, he's running my bot and dumping all the results in his Excel sheet. He's also working on other projects, and his routine has become very stable. He has more time to spend with his family. It has surely made an impact and yielded a positive ROI.

I don't know the exact cost, but UiPath is more expensive than Power Automate and Automation Anywhere. 

I rate UiPath seven out of 10. Learning a little JavaScript coding is helpful because there are some scenarios in which UiPath doesn't help you. In some cases, you may need to write a little code to perform some actions or call some functions. I would also take advantage of the UiPath Academy so you can stay up to date on the latest news and features. 

We leverage UiPath for customer service use cases and process automation to improve employee productivity and reduce time spent on repetitive work. UiPath is mainly used for financial processes like automated invoicing, but we also use the solution for IT processes. 

UiPath is deployed on-prem on a private cloud, and all our BFSI customers are on-prem. BFSI customers tend to use fully on-prem environments. UiPath offers cloud and on-prem versions, but the functionality is the same. A few technical aspects are a little different. 

UiPath makes our employees' jobs easier by eliminating repetitive tasks. The solution has reduced the time spent on these tasks by around 35 to 40 percent. They can use bots and spend more time on more productive work. We've improved process efficiency and employee productivity using automation. 

It's helped us discover better ways to make each process more stable. Our productivity has increased from 20 percent to almost 45 percent. That's what the change we have seen using you about. Using UiPath has reduced human error by 99 percent. I can't say 100 percent because nothing is fully automated. 

UiPath's automation features are all equally valuable, but we use the unattended bots the most. UiPath is easier to handle than most RPA technologies, and it's easy to install, so it's a competitive solution. 

The UiPath community has helped us troubleshoot issues. For example, if a bot isn't working properly, we can go to the forums to find the root cause of the problem. My technical team uses the UiPath Academy to get certifications and gain a better understanding of the product, but I haven't used it. 

We use some of UiPath's AI functionality, which makes it easy for us. Predictive analysis suggests the next logical step and what could be the possible solution for that. It tells you the possibilities and the pros and cons of each step.

The OCR technology has room for improvement. UiPath accurately reads about 85 percent of the fields in a scanned document, but that needs to be somewhere around 90 to 95 percent.

I have worked with UiPath for nearly three to four years.

The uptime for our bots is almost 99.9 percent.

UiPath is highly scalable. We plan to increase our usage because we aren't using it internally. It's something we deploy for our customers, so the usage will increase as our business grows. 

I rate UiPath support 10 out of 10. There are many ways to get support, including the knowledge base, live assistance, UiPath Academy, and UiPath support center. 

Positive

I was not involved with the setup. I sell the licenses, and the technical team handles the deployment. UiPath requires some maintenance, such as platform updates, updating the bots, and adding workloads. 

UiPath has reduced our employees' processing time and our expenses. UiPath has cut costs by about 18 to 20 percent. You can start realizing the ROI within six months to a year.

UiPath is affordable compared to Blue Prism or AutomationEdge. A basic license covers the cost of implementation and recurring fees that depend on the complexity of the processes and workflows. 

I looked at Automation Anywhere and AutomationEdge. UiPath is easier to implement and use. Cost is the primary factor. Indian customers tend to consider the cost of a solution more than the features.

I rate UiPath 10 out of 10. The solution can't give you 100 percent automation for complex processes, but it gives you up to 90 percent. However, once you optimize a bot, you can reuse it for other processes.

I have worked with most of the UiPath use cases. From 2017 to now, I have delivered more than 400 bots. I have worked in healthcare, energy, shipping, and other industries.

When it comes to manual processes, especially IDP and the combination of IDP and automation, the journey has been a bit difficult and challenging, but it has been worth it. Most other automation is straightforward. We take input from multiple platforms, put it into another platform, and so on. But with IDP, we have to read the document, validate the data, and then integrate it with the automation tool in UiPath.

I started integrating IDP and automation before UiPath Document Understanding and the Action Center were available. What I used to do was automate the process and then create a layout in ABBYY. I would then integrate the ABBYY layout into UiPath, evaluate the data, and then automate the rest. I did this in 2018 and 2019.

Now that we have our own Document Understanding and Action Center platform, I don't have to rely on any third-party tools for IDP. The combination of automation and IDP within a single platform has made a big impact on many businesses. It has helped them to reduce their annual efforts in data entry, reading documents, and correcting small errors in data extraction and copy-pasting.

I have seen the best results when IDP is combined with automation. It has reduced manual efforts by at least 80 percent. Automation is always helpful, but the combination of IDP and automation is even more effective.

In one example, we were able to deploy more than 700 bots for a single organization in the manufacturing industry. They had around 25 servers just to run the bots, but now they are running multiple bots on a single server. They are saving millions of dollars per month by using UiPath.

Overall, I think the combination of IDP and automation is a huge game-changer for businesses. It is helping them to save time, money, and resources.

Most of the elements we have right now as activities with this do not require us to work with the norm of 100 lines of code or anything like that. It is just drag and drop, so anyone can use UiPath from scratch and be approved within a couple of months. The platform itself is very easy to learn and use. I don't think there were any challenges at any point with respect to this.

UiPath enables us to implement end-to-end automation. We have many back-end processes that run without any manual intervention. We simply schedule the bots, and they run flawlessly. We also have a bot that generates reports for us. As a result, we have had end-to-end automation in place for almost a year now. We are very pleased with how it is working, and we believe it is a valuable feature.

The UiPath User Community is great. I am proud to be a part of the community, where I have earned the Community Moderator badge, the Bylaw badge, and the MM VPA badge. I have witnessed the incredible journey of the community, from a group of people who didn't know each other to a community that meets in person at least once a month. The quality of the answers in the forum is amazing. I have seen a few companies create internal competitions to see who can answer the most questions in the forums and receive prizes. These small gestures from the community make a big impact. I would say that the community has played a major role in the growth and deployment of UiPath. UiPath has never failed to surprise and value the community members. The company has never disappointed us, and it continues to support our efforts.

When we join the UiPath Community and become an MVP, we gain direct access to the company's product engineers. We can provide our feedback and reviews for every product and release, and we also have beta access to all products when we are eligible as an MVP. Every review, opinion, and idea that we provide to the product managers is taken seriously and reviewed. If it is valid, the product managers implement it. I think this is the best thing about being a part of the UiPath team, both as a team member and as an individual. I really like the core UiPath team very much.

We have UiPath both on-premises and in the cloud. I think we were able to make significant savings when we upgraded to the cloud, especially in terms of infrastructure costs, deployment, and upgrades. The dynamic nature of cloud computing has helped us to reduce costs and save time.

We often use the UiPath Academy courses. I believe that 80 to 90 percent of my team uses the Academy, and it is the main platform where we have learned to use UiPath. I recommend that everyone take the Academy courses. For anyone who wants to learn UiPath, the Academy is the best place because it has everything we need to know.

UiPath accelerates our digital transformation and reduces costs. We did not need to upgrade to expensive or complex applications to accelerate our digital transformation.

UiPath has reduced up to 70 percent of the human errors.

UiPath has helped free up staff time. We have citizen developers from UiPath who are using UiPath Studio X to save almost 70 percent of their daily time on email automation. Especially when it comes to process mining, they don't have to do the same update task; the processing is ready, and everything is ready to be given to the developers. Even the developers are saving time when using the RA framework for SAP or ERP applications, such as by creating and using libraries of common screens, selectors, and steps. This saves them at least 50 percent of their time, so they can focus more on research and development and new features.

Document Understanding and Action Center have added significant value to UiPath, especially for the IDP process.

There are a few businesses that are failing to generate their ROI. I think that's where UiPath needs to educate businesses so that they can choose the right product for them, whether that's the entire automation solution suite or just the individual products that they need. I think that educating businesses about this will help them a lot and make it easier for them to succeed.

When integrating with third-party tools, UiPath gives us the freedom to write our own code and integrate it. However, if we could get a repository of at least a few of the layouts for the GUI or AI Center, where we would only need to make minor changes, that would be helpful. For example, the files have a template that extracts all the information. I would just like to change a few things, but I don't want all of that. I know we can just hide it, but that won't help because processing the whole document extraction will still take the same amount of time. If we could get those codes in any of the repositories where we could make small changes to the existing code and then import them into our processes, that would be helpful. We do have all the code. We do have all the activities, but none of them are accessible or modifiable. We have to use them as is, or we have to create our own. Those are the only two options we have. If we could get the codes in the report that we want, and then we could make the changes and use them in our own code, I think that would help us more.

I have been using UiPath for seven years. I started my journey in December 2016 and we started delivering projects to clients in 2017. I have been impressed with the evaluation of the UiPath products from 2017 to 2023. The features that we have been receiving in recent years are very good.

When I started as an automation engineer in 2017, people at companies like Sony and other networks and large companies were scared to share their processes and credentials due to security concerns. I have seen this challenge firsthand. However, now, companies of all sizes, including national banks, are looking at automation.

I have seen an incredible journey from 2017 to 2023. I am happy to have been a part of it.

UiPath is stable.

UiPath is scalable. We are able to upgrade anything.

Whenever we have a challenge or similar issue, in rare cases, such as when there are multiple questions assigned to a support ticket, there may be a slight delay in technical support responding.

Positive

The initial deployment is straightforward.

The deployment time depends on the complexity of the project, ranging from six weeks to four months. For a very simple UiPath automation project with multiple applications, we can complete the development, UAT, and deployment within six weeks. However, if the project involves IDP, validation, and other complex features, it may take three to four months to complete.

The number of people required for deployment depends on the complexity. I always suggest having proper planning. I would not let any of the junior developers deploy to production at any time. I would always have two different teams. This is my preference. Instead of having junior developers deploy to production with only one person, even if they are capable of doing it, I would suggest not giving access to everyone to deploy to production. Instead, they should reach out to the production support team, and the production support team should do a code review before the deployment. Once the code is reviewed, the production support team can publish the package to production.

I have seen organizations that have been able to generate an ROI of almost 100 percent, as well as organizations that have struggled to generate even a 10 percent ROI. Some companies are very good at knowing what licenses they have bought and how to use them, but I have also seen companies that have a whole suite of automation tools that they are not using, including process mining and test suites. They are still paying for all of these tools, but they are struggling to generate an ROI.

The main complaint I receive about UiPath is the pricing. Many people purchase the entire suite, which can be expensive, even though they don't need all of the features. The pricing is also somewhat opaque for businesses of all sizes. Unless a company is a UiPath partner, it is difficult to customize the solution to pay only for the features that are needed.

I would rate UiPath eight out of ten. We have experienced some automation processes that did not turn out as expected, especially with legacy applications, which can be challenging.

I have not seen any challenges with UiPath upgrades, but there are a few things to keep in mind. Consider a client with an on-premise deployment. The developers have returned their code, which is very old. After two or three years, the client is finally upgrading. During this time, a few activities may have changed drastically or been removed from UiPath because they have been merged into other activities. In these cases, we need to do some maintenance to ensure that the upgrade is successful. We need to check that everything is ready and that the upgrade looks good. This may take some time, but it is the only maintenance that is required.

Our team manages RPA licensing, including evaluating other tools besides UiPath. We consider factors like upcoming automation reports and license renewal costs when deciding between UiPath, Power Automate, or other options. By comparing features and licensing expenses, we make informed choices about which RPA tool best suits our needs.

UiPath handles our invoice processing and a variety of ERP tasks, including automating processes in SAP and Oracle. We also leverage it for some portal interactions and other invoice-related functionalities.

Now we are evaluating UiPath Agentic Maestro capabilities, what we felt like it's a good platform for orchestrating the Agentic AI + RPA for touchless intelligent automation. Currently we are working on a POC.

We recently migrated to UiPath's cloud-based Orchestrator, and the benefits have been tremendous. We receive frequent updates without any maintenance on our end thanks to UiPath managing everything. This ensures no downtime and access to all the latest features, which UiPath releases regularly throughout the year in response to user feedback. Additionally, our investment in premium support, including a dedicated Partner Account Manager and UiPath Advantage benefits, provides us with immediate assistance whenever needed.

Although UiPath is not as user-friendly as Microsoft Power Automate, it boasts a wider range of features. UiPath does require some coding knowledge for developers due to its drag-and-drop interface, but it provides a strong framework that simplifies development. Projects can often be completed within one to two months thanks to this ease of use, and the platform itself is constantly being improved.

UiPath offers end-to-end automation, replacing the need for multiple tools. It supports DLC and provides sample documents and maintenance guidance. Additionally, UiPath's built-in flowcharts eliminate the need for Visio, reducing costs. Furthermore, integration with Azure and pre-built templates minimizes the need for PowerShell scripting, streamlining the development process. Overall, UiPath simplifies automation by offering a comprehensive and user-friendly platform.

The UiPath User Community is a fantastic resource, offering a one-stop shop for all our UiPath inquiries where we can find answers and connect with other users.

UiPath has been a game-changer for us. Productivity has soared, security has been significantly bolstered, and the new features are proving incredibly versatile. We've even been able to reduce outsourcing by implementing UiPath automation, which have greatly simplified our monitoring processes.

Its ability to minimize on-premises infrastructure aligns perfectly with the current trend of companies prioritizing digitization to reduce their physical footprint. In other words, UiPath is a key tool for achieving this modern business goal.

Our vendors initially struggled to adapt to the cloud-based platform after migrating from on-premise software. To bridge this knowledge gap, we directed them to the UiPath Academy courses, which proved to be a valuable resource. However, the extensive course library made navigating and finding the most relevant content challenging. Fortunately, UiPath's supportive team provided us with the necessary links, allowing our team to get up to speed quickly.

It has helped speed up our digital transformation.

UiPath has significantly reduced human error in our finance department. Previously, manual processes resulted in numerous errors that often went unnoticed until the quarter's end. Now, automation minimizes errors and frees the finance team to handle any remaining manual tasks with greater ease.

UiPath has helped free up around 30 percent of our staff time and has significantly reduced our costs, and the KPI data we're maintaining confirms these substantial savings.

UiPath stands out for its robust SAP integration capabilities and a growing library of connectors that simplify connecting to various applications. Document Understanding has also seen significant improvement, making data extraction more accurate. Additionally, UiPath offers valuable process insights, providing a clear picture of automation utilization across machines, and giving us a powerful tool to optimize our workflows.

UiPath's cost can be prohibitive, and the sheer number of licensing options they offer makes it difficult to choose the right one, creating a confusing selection process.

Currently, UiPath doesn't provide automatic notifications for known bugs in new releases. This means we're left to discover and report them ourselves. Ideally, I'd like to receive updates on these known issues from UiPath to streamline the automation process.

UiPath implementing a feature like Microsoft's CoPilot would significantly enhance our development experience by offering assistance in building automation.

I have been using UiPath for seven years.

UiPath is stable.

UiPath is easy to scale up.

Regular support is pathetic, back to back email conversation even though it is a production issue, so resolution time is quite high. the other option is we need to choose  paid support plans for quick resolution .

We also have a signed license agreement with Microsoft because of UiPath's high cost.

UiPath offers a pre-built framework that tailors to our specific needs, along with a powerful orchestrator for centralized control. While Microsoft's automation platform is still evolving and lacks features like UiPath's orchestrator, it excels in native integrations with Microsoft products like Outlook and SharePoint. However, for SAP integrations, UiPath provides exclusive activities that are crucial for automating tasks within our system.

In 2018 when I first deployed UiPath I found it to be complex but now that I have more experience, the deployment is straightforward.

Our team created three AWS accounts, designating one of them. We then set up, launched, and deployed the orchestration tool on the first account. After performing a POC and gaining leadership approval, we spun up two additional accounts for QA with UiPath's ongoing support throughout the year. Finally, we deployed additional machines and established a Cloud Operating Validation environment.

In-house we required eight people for the deployment.

We initially developed the proof of concept ourselves, but after launching into production, we leveraged the expertise of multiple vendors to ensure successful implementation.

UiPath is expensive compared to other RPA tools.

I would rate UiPath eight out of ten.

We currently have around 130 active bots, though, in the past few years, we decommissioned a larger force of 300. We also boast a user base of over 80.

The maintenance is handled by UiPath.

For a successful RPA implementation, establish a strong framework and conduct a thorough analysis to guarantee the stability of your bots. In the long term, a well-run COE is invaluable. Additionally, explore the range of tools available to enhance your RPA capabilities.