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.

Neutral

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 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.

I use this solution to automate processes and do screen scraping, image recognition, and other tasks.

UiPath Platform helps significantly in automating manual tasks. It reduces the workforce and the execution time required for operational tasks, so it provides good support.

The best feature about UiPath Platform is the role-based control access, which I have appreciated the most because whenever we want to implement securities and compliances, we can control the access for the solution.

AI-powered automation, combined RPA with AI, is the second best part, and the prebuilt automation concepts reduce the development time, which is the third best feature I appreciate. 

The UI is very user-friendly; if you are not a techie person, you can normally use drag-and-drop flows for a designer in UiPath Platform Studio, which is phenomenal, and when a non-technical person is going to use it, they can learn this particular process in a smooth manner.

Sometimes, regarding the limitations, heavy-level architectures and structures are needed, such as architectural setup required to boost IT support for long-scale automation. The learning curve, while low-code advanced automation is related to AI and ML, requires substantial technical knowledge. There could be some performance issues, such as automation breaking when UI elements change frequently, so these are limitations which I face, and these are the areas where UiPath Platform can improve.

The license pricing is very high, so compared to other competitors such as Automation Anywhere or Power Automate, it could be more competitive if these things were matched with the competitors.

I have been using UiPath Platform for the past three years.

The stability rates at eight out of ten. 

The scalability is impressive. Enterprise automation for small and large projects is easy, which is phenomenal.

We have 500 users using the solution.

I would rate their technical support a nine out of ten. Logistic support and integration is quite smooth; every time I required support, the support team was available and provided me with whatever assistance was required.

Positive

Blue Prism is one of the solutions that I have used, but it is less flexible for citizen users. The second solution I have used besides UiPath Platform is Microsoft Power Automate.

The deployment was easy. It doesn't require any maintenance.

It has reduced operational times and costs, particularly concerning manpower and the repetitive time needed to establish any process. It has positively impacted us and provided us with excellent solutions with phenomenal processing time. This was precisely what I needed.

It is expensive and not competitive compared to other competitor tools.

I have been using UiPath Platform for the past three years, and my experience is quite good with these process automation tools; I highly recommend this.

Users can utilize it because the UI is very simple and easy to use for non-technical persons. It helps overcome all the limitations, and the stability is very high, so it is reusable for multiple processes and purposes. I recommend all users to use it.

My overall rating for UiPath Platform is 8 out of 10.

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.

Clients usually use UiPath Platform for the automation of use cases in departments like HR, Finance, and IT support.

UiPath Platform can handle very complex processes. We have implemented various complex use cases using UiPath, and they are performing very well.

UiPath Platform integrates with several systems, whether they are ERP systems such as Oracle or SAP, as well as other systems.

UiPath Platform utilizes AI features. They recently released a new platform called Agentic Automation, which exposes AI and RPA in one platform, making it something fresh and new.

The most important features of the UiPath Platform are the UI automation capabilities and Document Understanding.

UiPath Platform is doing a good job with enhancements; they are releasing new features almost every six months. However, I would recommend that they improve their ability to be a low-code, no-code platform, as this would be a great feature for their platform.

I have been working with UiPath Platform for about six years.

I would rate UiPath Platform's support a seven out of ten. They need to work on improving their response time for open tickets and handling complex support cases, as I have seen some cases take a very long time to troubleshoot and get to the source of the problems. Therefore, they need to improve their response time as well as increase the teams in their support team, especially when handling complex support cases.

Neutral

Deploying UiPath Platform takes a couple of weeks.

The price of UiPath Platform in the Middle East region is a little bit high; having a lower price for the Middle East region would make it more attractive.

It suits big enterprise customers. However, if the customer is of medium to smaller size, UiPath Platform may not be a suitable choice.

It is an expensive tool. When compared to competition, such as Microsoft's Power Automate platform or IBM Cloud Pak, UiPath is expensive. Both of them are much lower in terms of pricing than the UiPath Platform, so they need to consider this in the enterprise scheme.

I would rate UiPath Platform a nine out of ten.

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.

We started using AI in Document Understanding by leveraging it against our models for different documents from our customers, primarily in the finance space. We have also used AI to train models for land management documents, helping them learn as we receive new document types. 

Recently, we've used it to analyze documents and articles online to understand sentiment toward our company. We analyze and summarize things people say in articles or posts elsewhere, which allows us to collect industry trend data. We are considering using Clipboard AI for smaller, ad-hoc data processing tasks because it can sometimes be more effective than Document Understanding.

We get a lot of projects that are on relatively short notice for the workload that comes with them. Historically, we would rely on leveraged services or contractors to do that work manually, which is costly. You can save tons of money by automating data entry, transcription, etc. Nowadays, as we get busier and busier, the work seems to bog people down more and more with tasks. UiPath gives them opportunities to free themselves up and focus on themselves.

We initially focused on time savings and how we could free people up more. We achieved that over time, but it took a while to get there in the first few years. We came in with some use cases that we later learned were not great fits for automation. We learned through trial and error and got better at identifying better use cases for automation. We've succeeded, and it's worked out for the better. 

But aside from saving people time, we also wanted to ensure that we brought in new technology to leverage some of those processes. UiPath forces you to look at the process from a high level and take a step back. You might have had the same person doing the same process for 10 years or more without thinking about how you can use new technologies to eliminate the process or make it more efficient. UiPath forces you to look at the process as a whole and the systems it's tied to. When you step back and look at it, especially with new people coming in, they start offering suggestions, like "Wait. You've been sending this email every time? That's something we can automate now. Oh, you've been trying to pull this information from a document and copy and paste it? That's something we can automate, too." 

If it's not automation, it's something else. We can look at other tools and applications our company brought in. There's usually some other solution they can use, automation or not. The natural way to work with it is by lining out a process and laying out all the steps on a workflow diagram. It allows you to rethink your process as you're doing it. 

Instead of just following step-by-step documentation or the way you've done it all the time, it gives you a chance to see it from a new perspective, and that's just part of working with the tool. As you build that out in UiPath using task capture or anything else, you will see that naturally and start thinking about ways to handle it better.  

Automation has freed up employees for other tasks. That's something that they like about it. The other thing it's done is build some excitement about IT and solutions in general. They're always looking at the new function that's coming out. They want to see what else we can do for them. Automation isn't always the answer, but we can get them to engage and talk to us during office hours to attempt to solve their problem with UiPath. We can also learn more about what they do. 

We're getting closer to our customers, talking more about their work, and they're feeling a closer bond with us. They're feeling like they trust us more in IT and are starting to see what other tools we have. Maybe automation wasn't the right fit, but we will always find better opportunities by building a report that sends an automatic email and an application for them in low-code software. UiPath has helped create a much better and fluid engagement process for us and our customers. 

Since it's a low-code tool that's easier for them to approach and understand, they're also more involved in the design process. The learning curve is shorter. When Studio first came out, it wasn't as user-friendly as they had hoped, but StudioX came out in 2020 and was approachable for most of our users. That's what our citizen developers use most of the time now. We have far more citizen developers with StudioX than unattended developers with Studio.

Within UiPath Cloud itself, UiPath Insights has been excellent. Insights is one of the newer features we were excited about because we built custom reports, captured all that data in one place, and leveraged it in different areas. That was a challenge for us and created a support burden. We're automation developers, not report developers. When leadership wanted a new metric or anything, figuring it out was always a pain. 

Insights has built-in mechanisms for tracking time savings, usage reports, and the overall health of your automation program. Having that functionality built in by default is critical. I click it and tell it the report that I want to generate. It'll build it for me automatically, and I can share it with people who need it. It has made a huge difference for people administrating the platform and reporting success to leadership over time. 

UiPath needs work on the governance side. For example, they released Studio Web this year and have started work on its governance, but it initially lacked control from an administration standpoint. You could not lock down third-party libraries or other applications and integrations it had built in.

For example, people could use a Google account, but we might have concerns about that from a security standpoint. Cybersecurity is taking a more significant place in IT, and we're mindful of that. Having explicit governance over what our users can do inside those technologies is essential. We hope to see that more over the next few years. We've given a lot of that feedback as customers to UiPath, and they've been working hard to get that into the pipeline and implement those changes.

I have been using UiPath for about six years now.

UiPath can grow with us, especially since they developed a cloud environment. When we started, we had to make many changes in Orchestrator and other areas as we scaled up. We scaled up fast and automated dozens of automations in the first few years. 

However, we found that the default setup for the UiPath Orchestrator in 2018 didn't have all the features we needed to administer it to our customers. We had to build custom solutions in-house, but they've released many new features in UiPath Cloud that simplify management. 

I rate UiPath 10 out of 10. The executive support team and customer success team have been great. All of them play a role, and they're super knowledgeable. If they can't solve your problem, they know who can and connect you with them quickly. We've leveraged them extensively and will use them more over the next couple of years as we finish our cloud implementation. 

There are still many features we don't use, and we constantly go to them for guidance and help on how to use them best and what they've done with other customers. They provide tons of great insight and have a solid network. 

Positive

We didn't have a low-code automation platform. We developed most of our automations using PowerShell. We didn't have citizen developers, but most business users would use Power Automate. Back then, it was known as Flow on the Power Platform. 

Our corporate leadership decided to bring in UiPath. It wasn't an IT decision.  They wanted something they could start using for their daily tasks. They didn't think we had something that could automate things well, and PowerShell is limited from a scripting and API standpoint. They wanted to automate things in SAP, and the APIs and other things are locked down in a custom shop like ours. We can't integrate with our environment in any way we want, so we need something that can interact through the interface. UiPath does that. It can click and type everything through the interface. 

The leadership started the process. IT got involved and supported it. Since then, we've helped it grow throughout the company. It's not just finance anymore. 

The initial setup was complex because UiPath didn't have many pipelines built in. We had to build custom pipelines for the technology we use. It was TFS at the time, and now we use Azure DevOps. I helped with the VDI setup. For unattended automations, you must have a platform or system they can run on. We had looked at doing HDRs—high-density robots—that UiPath. 

Due to applications such as SAP, it couldn't run on a server-side setup. It had to be on a desktop, so we used a VDI for every bot we created, and I helped create the user policies for our accounts and device policies for each VDI. I also set up all the installations and the presets. I helped set up a framework for that over the first year, from 2018 to 2019. We smoothed out the process from there. That was something we had to do on our side. It will be unique for a customer depending on their environment.

We used a partner during the initial setup.

The leadership is pleased with the outcomes. With Insights, we can show them how much time we're saving with each process.  We document savings in hours rather than monetary terms.

I rate UiPath 10 out of 10.