UiPath Platform Reviews

We are using UiPath as an RPA solution, utilizing its capabilities for document extraction, intelligent OCR, and intelligent automation. Once it became available in-house along with the robot environment, we started using it.

UiPath enables us to implement end-to-end automation.

UiPath has freed up employee time because most accounting staff are now monitoring rather than performing tasks manually.

The robots are valuable, and UiPath is becoming stronger in the intelligent automation space, which is a good step forward. Also, Document Understanding integrated with Agentic AI is working well. The automation cloud is also good.

Their community is good. UiPath Academy is also good. You can get familiarized with the products. Whenever they release a product, they also release a course in UiPath Academy. So, you can get familiarized with the product and understand the new capabilities.

I do not like the Orchestrator setup and the licensing model. Its price is higher than others, and the licensing model is quite confusing. 

UiPath should develop models for situations when other applications disrupt automation and provide a mechanism to override that. Efficiency issues are present and should be addressed.

I have used this solution for almost seven years.

The solution is not very stable. Sometimes there are issues, for example, selectors may not work properly. 

The solution is scalable enough, but since the license cost is high and most of our solutions are deployed in Azure VMs, which is expensive, customers are hesitant to invest in more bots or solutions. If the licensing costs were to decrease, more bots could be deployed.

We have 20 to 30 people using UiPath.

Their technical support is average. Their community is good. For almost all the questions, we get answers. Initially, it was very difficult to get support, but nowadays, we do not have to go for support because most things get solved in the community itself.

I was a .NET developer before using UiPath, so it was more of a generic transition for me. I have worked with ABBYY FlexiCapture. My experience was good because the automation has been running fine. The document is in proper format. It works fine.

For me, UiPath is much easier to use than Power Automate or any other tool because I have the most experience with UiPath. They tried to fine-tune the automation experience over time, so it is much easier compared to other tools.

The initial setup is straightforward and does not require much effort, just a bit.

We were using the on-premises version of UiPath, but we have now migrated to the cloud. The migration process itself was very easy because they have a cloud migration tool. We started using the cloud. It has more capabilities, and it is much easier for us to maintain. We do not have to update the Orchestrator after every release. So, it is good.

The deployment is done in-house.

Most RPA solutions are cost-effective. For accounting, we automated tasks in our old organization, and now, most accounting staff are monitoring rather than performing tasks manually. They are simply doing validations.

UiPath has reduced human error and saved employee time.

Its cost is a bit on the higher side. We are not very happy with their pricing. Most of the UiPath products are priced higher than competitors.

UiPath is evolving with current trends, particularly in AI, and is now focusing on Agentic AI. The future looks promising for UiPath. 

Overall, I would rate it a seven out of ten. It is a good product.

I have automated a few basic business workflows. They were simple automations.

In terms of complex workflows, generally, we have some kind of system to interact with over a browser. There are specific sites such as SAP or other HR applications that usually have browser UIs. Browser interactions are the best I have found with RPA solutions. 

We have tested the Document Understanding feature, which seems promising. Although I haven't developed a proper workflow for that use case, it looks useful. The framework seems to help set up the development process without needing extensive programming knowledge. 

We also use UiPath in our Microsoft environment, particularly for core applications such as Excel, Word, and Outlook. Excel activities are very useful, so it has become a core element of our workflows. As a developer, I enjoy using Visual Studio to create custom activities based on specific business workflow requirements.

There are also a few use cases for agentic automation. A core element is processing the source document, whether it's Microsoft Word, PDF, JSON, or XML. It parses the documents, retrieves required data, and pushes the data into a target system, such as a database or Excel table. The automation acts as an automated interface, moving data from a source system to a target system.

UiPath helps speed up digital transformation and ideally reduces associated costs. Though there are instances where the frequency of automation has decreased, impacting overall effectiveness, generally, our automations operate ten to hundreds of times faster than manual processing.

There's a notable reduction in human error. Partners are often surprised that the automated process doesn't make mistakes. While we can't predict all unexpected issues, business-related errors are virtually non-existent once a process is automated.

When considering specific features of UiPath that streamline operations, the management part of UiPath Orchestrator for unattended automation is helpful. The scheduling is very nice, easy, and simple to manage, allowing me to oversee workflows and their schedules effortlessly.

It saves time for the development team. The agentic automation from UiPath is user-friendly. It's definitely one of the stronger points. It's really easy to handle, even for someone who has never heard about RPA. It's generally simple. Once I install the system, I show them how to start and stop the processes, and that's basically all there is to it.

What I appreciate about UiPath is that, compared to the competitors, it has pretty much everything. There are so many out-of-the-box solutions that it's difficult to find a match. I have tried to compare it to free alternatives, and the difference is night and day.

It's simple to develop and use for developers and end-users as well, so I would say that's probably the most important aspect for us. The development time is very fast once a UiPath developer learns the basics of development. It usually takes a few days to automate a business process, which is mind-blowing compared to other options.

There is one major feature I feel is missing from UiPath. When someone starts an automation, there should be some notification window on the screen to provide information about the flow's status and progress. Currently, users can see if the flow is running and some basic information, but there's no core notification window that fully informs users. Incorporating such a feature would greatly enhance user experience.

I faced one issue with UiPath Studio where when automating a workflow takes several hours and the application remains open, it can consume an immense amount of memory, sometimes up to six gigabytes of RAM. Restarting UiPath Studio usually resolves this. I'm uncertain if this is a common issue or specific to my environment.

I usually use the UiPath Community, which is pretty much my primary resource. I occasionally explore the marketplace for specific activities that may already exist. However, I primarily rely on forums. Most of the time when I have a specific question, I find the proper answer there. About 90% of the time, I find relevant forum threads where someone has encountered the same issue or question.

I utilized the UiPath Academy heavily in the first two years, completing most developer-related lessons. It's challenging to keep track of all the lessons nowadays, so in recent times, my learning has shifted more towards forums and YouTube videos rather than strictly relying on the academy.

Neutral

I haven't worked with any RPA product before UiPath. We did explore other options back in 2019 and compared various competitors when we had a project in 2023. However, my development experience has solely been with UiPath.

If our partner requires an on-prem RPA solution, we create a compact UiPath architecture. We have several partners with on-prem orchestrators and associated servers. It's really simple to assemble. I know because it took just a weekend to set up all the servers. If someone prefers cloud solutions, it's even easier since much of the configuration is pre-set. Overall, I would say that it's not difficult to develop an on-prem architecture.

On paper, I believe there are cost savings thanks to UiPath. However, I don't have access to exact conversion numbers. I can see saved time and reduced FTEs, but I can't specify how that translates into actual money. Some workflows don't pay off the license due to infrequency, but overall, I believe it does contribute positively.

I would definitely recommend UiPath, although the major concern is that it's not super cheap. Despite its higher price, I understand the complexity behind it since it's the most comprehensive RPA solution. 

The cost can be a barrier in Hungary, making it difficult for me to persuade others to invest, especially when unattended robots come at a significant price point.

When we were trying to implement UiPath in our environment about four or five years ago, things were totally different than they are today. Many automation solutions didn't exist back then, making it challenging to get familiar with the product and its capabilities initially. Since then, the RPA ecosystem has expanded significantly. Document Understanding wasn't a feature in 2019 or 2020, but now, it is much improved.

We haven't really used the communication mining feature. I've checked it a few times, but we usually handle manual interviews with key users. As for task mining, I used it for documentation purposes when creating workflow documentation. It supports generating document templates, which is very useful for us, but we haven't used it for deeper automated workflow steps.

I would rate UiPath an eight out of ten.

I am in consulting, and I implement UiPath for my clients across various use cases.

Immediate benefits include faster operation and the ability to run overnight, which clients value since the work is already completed when they start their day.

From my point of view, it is visual, making it easy to learn. It is super easy for me to learn and handle the automation, then replicate it, rather than using traditional code.

Everything is embedded. It is not only automation. It also includes document understanding and communications mining, with all add-ons in the same organization. 

We use Agentic automation. It's very good at automating processes. We're still at an early stage. We have access to the alpha version. I like what it is doing, however, it is not production-ready yet. I see its potential. Initially, I started playing with it via demos only. I've built a few things I have shown to clients, although I have yet to use it. 

We had a few use cases for Agentic. One use case was as an HR assistant, including providing invitations to candidates to say they are a fit for "x" roles and to set up interview times. Another use case was as a document extractor. I created an agent that could extract information from documents and provide a stable output and learn for itself. The third use case was for account payables, which is the one I've been demoing. I've created an agent that can read an invoice and provide recommendations, such as approving payments.

I have experience with UiPath's communication mining features. It can be used in real-time if you link it to a mailbox, for example. I don't see the power of linking to a mailbox. However, I see the power of using them to send an email and then get in return what the tool understands. I'm able to automate actions and responses. I have a demo on that. For example, I have an automation that scans the email, and it can tell what documentation the email is about. I can understand, for example, if the email or document is about a policy claim and then ask further questions or make further recommendations based on that.

It's fairly easy to build automation. I'd rate it overall a seven out of ten. It can get super-complex, however, it's fairly easy.

We can handle end-to-end automation for the most part. Now, with Agentic, it's easier, since you can connect automation. You just need to keep in mind there's a different approach.

I do use the UiPath forum. If I don't know something or if I'm facing an issue. Maybe someone has already faced it. 90% of the time, someone already has. I can ask questions and try to solve problems.

UiPath helps the team have less work. People, initially, when they use automation, fear they will lose their jobs. However, that's not the case. Now, people see that they can properly focus on other stuff. Their job isn't taken. They can focus elsewhere. Depending on the use case, UiPath has freed up 50% to 90% of a person's time.

The Academy is free, and there is a lot of content. For new joiners, they have to be certified, so for the first two to three weeks, we put them in full training mode. 

Licensing needs improvement. Licensing in UiPath is a bit confusing. They are already working on that, however, from my perspective, it is what I feel least safe discussing because the product changes two or three times a year. 

Additionally, it is confusing to understand the packages available, the number of packages, and updates with new versions. Therefore, from my perspective, licensing is an area for improvement.

The Agentic tool has a lot of noise. However, we have to get hands on to understand what the tool is capable of and what the tool is not capable of. That's one of the things that I am spending time with.

I have used all the platforms for five and a half years overall.

I have personally never experienced downtime. I'd rate stability nine out of ten.

Sclability is quite good, perhaps an eight out of ten. It depends on how the development is executed. If done properly, scaling is straightforward; otherwise, it can be challenging. However, the issue lies with the implementation, not the platform.

Every time I work with the official UiPath support, they are slow and might not have read my request thoroughly before responding, leading to incorrect answers.

If you know the right person, partner support can be good. I tend to not ask anything when I am trouble. The support in Australia is better for partners. 

Neutral

I have used Blue Prism at a beginner level and Automation Anywhere at a beginner level. As of now, I would not consider them competition. Blue Prism, for example, has not kept up with changes, and Automation Anywhere is making efforts, however, I am biased and would naturally choose UiPath. The main competitor would be Microsoft Power Automate.

Cloud deployment took me 15 minutes. A few years ago, most deployments were on-prem. Overall, the safe answer to fully deploy would be weeks, however, depending on the use case, it could be longer. The largest deployments I have done took four months due to complex automation. Typically, it takes three to four weeks, maximum.

We have around 500 UiPath specialists. Our clients are medium to enterprise.

The solution absolutely needs maintenance. If the applications change of something becomes unstable, you need to have maintenance to make changes. The same is true if a website updates, for example. It can affect an automation. 

We are already undertaking this at the regional level, so if UiPath has any activity in Australia, they will reach out to me.

I do not have the numbers at hand, however, there is clearly a return on investment when the automations are done properly, which is hopefully every time we develop anything for production.

From my discussions with clients, they normally find it expensive. This expense is generally not in terms of the bot or developer license. It's rather when it comes to AI units. Enabling document understanding, communications mining, or agents is considered expensive.

I'd rate pricing seven out of ten, with ten being the most expensive. 

We are UiPath partners.

The tool is already proven, so starting a proof of concept is a good idea. Users should create a POC that can scale. Automate steps one and two, for instance, so that you trust the tool and see what it can do. Then, quickly transition to phase one if phase zero was the initial step to see its scalability and impact on previously good information. 

I'd provide an overall product rating of seven out of ten.

From time to time, I have been using UiPath Platform only for merging, filtering, and getting what I want from data tables, basically every now and then, only when I need to do small tasks, such as filter tables or do a quick win.

I used to be basically an integrator where I worked for a consultancy company where some other company would hire us to develop UiPath Platform products into their environments. When I'm using UiPath Platform, it's for my personal use, just to save me some time doing what I told you about tables and just easing my job.

From UiPath Platform, the positive side is it was easy to integrate. Now, they have been changing lots of things that I don't really prefer, and basically, it was easy. The Orchestrator and having the logs whenever an automation is running allows you to see the logs right away, even though it can be on debug or even in production.

The Orchestrator is one of the main things that UiPath Platform has. A disadvantage against Power Automate is that with Power Automate, you have the cloud flows that you can trigger based on a cloud flow connected to whatever you want, which is pretty nice. You can also run most of your automations depending on if you are using UI or not; if you are not, you can do everything cloud-based instead of actually needing a machine to do that, whereas with UiPath Platform, you always needed a machine before.

The installation procedure for UiPath Platform was straightforward.

I think they are turning too much into a business standpoint with UiPath Platform, meaning that the new stuff that they have been developing and operating has the most focus on business, so business can actually develop it within UiPath Platform, which they kind of never will. They have been disregarding the developer side of things by not keeping it simple and easy to use. I think they have been developing too much into the idea that anyone can build in UiPath Platform, but it's making things harder for people who actually understand UiPath Platform and how it should run. It's not about being too simplistic; it's about making things that for us don't make sense. Some changes even in the Excel activities have been making things harder and pointless in some regard.

I think UiPath Platform should focus more on developers and not on business because, in reality, business will never be doing automations. If they do, they will always need a developer to fix it because they messed up somewhere, and for the price, it went up too high.

I did use UiPath Platform. I haven't been using it lately. The last time I used UiPath Platform was a few months ago, but it's only to do small tasks, and I don't even use it in production that much because it's too expensive right now.

If I count every day use of UiPath Platform, I worked for two and a half years using it every day.

I have only used UiPath Platform. Automation Anywhere, I never used it, but I wanted to compare between automation tools. I have been mostly using Power Automate.

The installation procedure for UiPath Platform was straightforward.

Regarding ROI with UiPath Platform, it depends on how companies are actually using the automation and what use cases they have. But for it to be right now viable in terms of cost and everything, they must be using UiPath Platform almost all the time; otherwise, it won't be that good because it's too expensive. The good part is that you reduce human error, you don't give access to passwords, and you keep them safe in that regard, but then, I don't have a definitive answer because I haven't been touching UiPath Platform for too long and not dealing with customers with UiPath Platform for a long time.

Nowadays regarding UiPath Platform, there are both advantages and disadvantages because nowadays you can just go into an AI tool such as GPT, Claude, or whatever and ask it to do whatever you need, and it will be faster. UiPath Platform has the upside of the automation if you actually develop that into a customer, which will be time-saving for them. I used to have runtime for UiPath Platform.

My main use cases for UiPath Platform include bot automation, Agentic agents, and AI, with specific use cases that are healthcare-centric, while also leveraging technologies that the platform brings, such as RPA bots and agent orchestration.

Implementing these features from UiPath Platform has benefited my organization as we reduced DSO and improved clinical effectiveness and timeliness, leading to improved employee efficiency and accuracy.

The feature of UiPath Platform that I appreciate the most is the orchestration. 

UiPath Platform can be improved by being able to leverage what we have, and from an AI capability perspective, having a chat or voice capability on the platform would be beneficial. With Maestro and the concept of being able to orchestrate across other solutions is phenomenal and great, but I would also appreciate being able to just stick with one solution.

I have been using UiPath Platform for six years.

I have not experienced any downtime or performance issues.

UiPath Platform scales with the growing needs of our organization extremely efficiently.

I evaluate my customer service and technical support as top-notch. On a scale of one to ten, I rate my customer service/technical support as a ten. 

They have been highly responsive. In every cab meeting or conversation with senior leadership at UiPath, they have made things happen, and my account executive and solutions executive have also made things happen. I cannot say enough about how great the team that supports us is.

Positive

Before selecting UiPath Platform, we looked at some other vendors, and I have a background beyond the current relationship, as I have used UiPath Platform in other companies, which helped accelerate our decision-making.

My experience with deploying UiPath Platform is very positive.

We are seeing a return on investment with UiPath Platform.

My experience with the pricing, setup cost, and licensing of UiPath Platform is positive.

Prior to adopting UiPath Platform, we were considering other solutions, including purpose-built solutions from companies such as Tenor and also Blue Prism and OpenAI's ChatGPT.

My advice to another organization that's considering UiPath Platform is to understand your journey and what you're trying to accomplish. UiPath Platform can do it, and I don't have any concerns or questions around the technology or the capability or the organization to support. Another customer would need to be prepared and understand what they are doing and why. 

I rate UiPath Platform ten out of ten.

We use UiPath Platform for automation. We implemented automation across departments with this solution. We use robots to automate a process. 

We handle both attended and unattended automation with UiPath Platform. We do not use any AI integration features in UiPath Platform.

UiPath Platform is easy to use, and the user interaction is good.

UiPath Platform allows for code-free use, but I mostly write code.

The support process of UiPath Platform can be improved. When we get stuck somewhere and need help from UiPath people, it takes considerable time to receive assistance.

I have worked with UiPath Platform for around two years.

I have not experienced any stability issues with UiPath Platform.

The scalability of UiPath Platform is good. We deployed the automation in departments, which helped us save resources, money, and improve quality.

The support needs improvement. 

I also worked with Blue Prism. When comparing UiPath Platform to Blue Prism, the main difference is the user-friendly aspect. UiPath Platform is easier to use.

UiPath Platform helps save time, increase performance, and decrease human errors. While quality is not always accurate, time and money savings are significant.

UiPath Platform is a cost-effective tool.

In terms of the learning curve, it was initially difficult but became manageable once we learned the tool and started working with it. It takes some time and effort in the beginning, and then you get the results. It saves a lot of time and also reduces costs.

I would rate UiPath Platform an eight out of ten.

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.

In Brazil, we have some standard processes. Some companies operate in similar ways. I cannot give all the details, but there is a process for financial invoices. We normally use UiPath to automate this process.

Using UiPath is very easy. Even for new users or developers who are just starting, it is easy to use. You just need to drag and drop the activity, so it is very easy to start using. We have UiPath Academy, which is very helpful when you need to learn something. When anyone is starting to use UiPath here in my company, we recommend starting with UiPath Academy. It helps a lot in every project that we have here. 

Also, there is the community, which is very helpful. We have lots of users, and for every question that we have, we can just Google it, and then we can find the answers in the community. Almost all the questions that we have can be found in the community, which is very helpful. We also have different integrations with different services, and this is very helpful as well.

I do not have any complaints about the tools themselves. They work very well. The only problem is the cost. It was more accessible initially, and we could have more resources with the same license. Now, the license is different, and we need a license for each tool that we have, so it is not very accessible to have all of the tools for installation.

I have used it for about six years.

The stability is very good. In the beginning, we depended on our infrastructure. However, now that we have services on the cloud, it is very stable.

Scalability depends on how you are automating and using resources like queue triggers. If you use queues, it is easy to scale. You just need to change the number of robots for the process, and then it works very fast.

Every time we need support, most questions can be answered by searching on the Internet or finding solutions in the community. When we require technical support, we contact UiPath. For instance, we had trouble with the database while using UiPath on-premise and connected to support. They were very helpful, addressing the issue in three hours. Therefore, I would rate customer service a ten. It's a very easy tool to use, so normally, we do not encounter many troubles. But when we do, the answers are either in the community, or we contact support.

Positive

It depends on the customer and project. Sometimes, I am involved in the deployment process. I might be a developer, and sometimes I need to deploy in a development tenant. Another team analyzes and deploys it to production, or we deploy it to a tenant for deployment. A global team, for example, analyzes, publishes to production, and ensures they have all the documents before publishing to production. We use the process to run through.

In the beginning, the return on investment is quick. As automation scales, requiring more licenses, it becomes more expensive. At first, processes save money, but eventually, automation without cost savings occurs due to licensing costs.

Besides using UiPath Academy, having expertise in the automation process is crucial because it is not just about setting up automation. Governance becomes critical as automation scales. Planning is essential before starting the process to avoid chaos as automated processes increase. For example, restricting developer access to production is crucial. Overall, I would rate UiPath an eight out of ten because, while it is the best tool regarding resources and integration, pricing is problematic.

I initially used UiPath for repetitive and structured or mechanical types of automation. I was a software engineer, and I handled maintenance processes for applications, whether it involved starting up servers, generating reports, or conducting health checks. These repetitive operational maintenance tasks were handled with UiPath. It was a tool for creating workflows to handle such menial tasks. 

Automation must be present in an organization. Without it, you are stuck with manual processes that require lots of manpower for menial tasks. Automation allows large companies to scale their services efficiently, focus on more strategic tasks, and serve their customers efficiently. Its benefits can be seen immediately after the deployment. Your staff does not have to do repetitive tasks anymore.

Communications mining happens at the intake part of an internal process. It helps to classify information coming from various channels, such as an email or a ticketing system. It is useful for triaging and actionable insights. You can action that using a downstream automation. It can help with any process, whether it is a finance, IT, HR, logistics, or healthcare process. They also have IXP which combines Communications Mining with Generative Extraction. Tone or sentiment analysis in documents helps with better redirection or triaging. It goes hand in hand with the capability to classify documents.

Communications mining can help save time for your resources. If about 80% of your incoming communication is related to order management, with automation, the return will be direct. There will be hard savings in terms of people needed to work on the order entry processes. Instead of ten resources, you might need just three resources. The savings depend on the use case or the volume of a particular use case.

A key strength of UiPath is that you can easily and quickly build automation. If you are familiar with UiPath, you can automate simple to medium processes in a few hours. If you do not have any technical background, you can get started with UiPath and be up and running in one week with the help of a foundational course. I had a colleague with a background in political science. He did the foundational course and was able to build a project on his own in just one to two weeks. He is now a successful technical project manager working with UiPath.

UiPath helps to reduce human errors if the process, requirements, and exceptions are properly defined and the process is fully optimized before being automated. The ideal target is 100% accuracy, but that is usually not possible for most processes. About 90% or more accuracy is more realistic. 

We have started to gather use cases where we can leverage agenting automation. It opens up more capabilities or coverage on the existing use cases as compared to before where we could only automate an end-to-end process to a limit. For example, we could only automate entering an invoice into a system using UI or API automation and downloading a report. With Intelligent Automation, they have added the capability to read from structured and unstructured documents and then classify the content. 

Agentic automation now allows us to handle complex tasks like invoice dispute investigations, which wasn't possible with traditional RPA. Using UiPath Agent Builder and Agentic Orchestration, we can automate and manage end-to-end processes across applications and provide meaningful resolutions. This makes workflows more dynamic and flexible compared to rigid, structured automation.

From the early days, UiPath stood out because of its intuitive interface and ease of use, enabling the automation of complex processes without requiring technical knowledge related to development. UiPath has since expanded from simple automation to Intelligent Automation and Agentic Automation. The coverage of more complex use cases has increased, making it more robust. Processes not capable of automation five or six years back can now be automated easily. We can read from documents using Document Understanding or create complex workflows that require many decisions using agents. They are moving towards Agentic Automation.

The UiPath community offers a lot of value for sharing knowledge and networking. It helps you build knowledge and grow professionally within the same company or land your dream job in this space. Many large companies are using UiPath as the main automation tool.

UiPath Academy was my first point of entry when I started using UiPath. With its help, I was able to build my first robot. It has also helped me to be up to date with the latest and greatest features of UiPath.

Now that UiPath is moving towards BPMN as part of agentic orchestration on Maestro, there is a need to make it easier for newcomers in the BPMN space to understand the components of a BPMN workflow. More awareness is needed since even technically inclined individuals are not very familiar with BPMN.

I have probably used UiPath since 2017.

Our clients are large enterprises and small to medium businesses. We are both a partner and a customer. About 90% of our resources are working with UiPath. We are a small company with 200 to 300 employees.

Sometimes the technical support team gets repetitive with the questions they ask, and for complex issues, it drags on too long.

Neutral

Some of our customers are on-prem, and some of them are on the cloud.

If you are on the cloud, you do not need to worry about deployment. On-premise, it is similar to other software where you need to provision an infrastructure, either AWS or any of the hyperscalers. It might require more steps and effort, but it is doable.

For complex cases, it could take an average of three months. Simple ones can take less than a month.

In terms of maintenance, any solution requires some sort of support and maintenance.

UiPath Autopilot saves 20% of my time. Most of my time goes into building projects for customers and not for personal productivity. The only automations that I leverage are the prebuilt ones for my personal use, such as UiPath Autopilot.

There is always an opportunity to improve. They have been trying to improve pricing by consolidating some of these SKUs together. They are trying to bundle more capabilities with the same set of licenses, which is good. However, because things are always changing, it leads to some confusion. They can make it more streamlined and consistent.

Compared to Blue Prism and Automation Anywhere, UiPath is more user-friendly and constantly innovating to lead in agentic capabilities.

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

Currently, we do not have any AI use cases. I work for a healthcare system. Our main use case is using UiPath to replicate what medical coders do. We input codes from certain medical systems into another, and it automates our billing cycle. This allows us to input the codes directly into the insurance billing cycle, speeding up our payment process.

Our hospital does not get paid if we are slow to get the codes to the payers. By automating this process with UiPath, we wanted to speed up the process of getting paid by the insurance companies. It has been amazing. Just this year, we probably saved 45 million dollars, and the next year, it will be upwards of 80 million.

In health care in America, many processes are still paper-based. Document processing is valuable as it allows doctors to have documents processed in advance, making it easier to access and ask questions. Additionally, UiPath has freed up staff time significantly, to the point where some staff had to be laid off. Our use of automation sped up the process of getting paid from insurance companies, saving us substantial amounts of money.

We're looking to add AI, specifically generative AI, but it's a matter of our organization implementing it. With autopilot features like Microsoft's Copilot or ChatGPT, users can start chatting immediately. However, with UiPath, one needs the UiPath Assistant installed on every machine, which is unrealistic as many people use the same machine in the hospital.

My enterprise has been using UiPath since 2021. My team inherited it in 2023, so it has been about 11 years.

The solution just went live yesterday, so I don't have feedback on its stability yet.

The solution is scalable. We previously had an older solution, and UiPath helped us revamp and upgrade our systems, making them more scalable.

The customer support from UiPath is amazing. We are part of the hypercare, and I would rate it as a nine out of ten.

Positive

We use Power Automate a lot and still incorporate it alongside UiPath. Some hospital systems require us to be all on-premises, so we use both UiPath and Power Automate to get our systems working as needed.

Some automations were built in-house by our team of developers. We also worked with an external partner and UiPath to implement some other solutions.

We have seen a 100% return on investment. The process is night and day when compared to paying employees over time for the same work.

It is more expensive than other automation services, but I don't deal with the financial details much.

As automation software, I would rate UiPath a ten out of ten.