UiPath Reviews

We primarily use UiPath for automation processes. One of the major use cases is the approval system that we have. Our system goes through a lot of approval and workflow steps, and we have automated the entire process using UiPath.

We are using UiPath for most of the automation processes. We have reduced a lot of resources that we previously had, and it has improved the efficiency of the operating model that we have. Earlier, if it took around a week, we are now able to achieve the same process within three days or so. It has basically cut the time in half.

It helps us to achieve end-to-end automation. If something involves manual intervention, it's always prone to human error. End-to-end automation completely removes all human errors and also saves a lot of time and manpower for a specific process or task. So, overall, we improve the efficiency of the processes that we implement.

It has reduced the time taken to develop something, as well as the error rate. Earlier, we used to have a lot of human errors because there was a manual intervention, but now, there are no errors, and everything operates smoothly.

We automated the complete approval workflow system. Every operation has a different set of child operations that occurs as a change reaction. UiPath helped a lot in implementing this in a completely automated way. With the flow chart wizard available within UiPath, we are able to achieve this pretty easily with less effort. It gives us more results with less effort.

It definitely reduced the costs of digital transformation because we have cut down a lot of resources that we had earlier. We were able to cut down the cost by half. There is definitely a reduction in price. Doing digital transformation didn't require expensive or complex application upgrades or IT application support.

It has reduced human error a lot. Previously, with our approval workflow, at every step, a human had to come, approve the request, and perform a lot of manual steps after the approval. All those steps are now automated, and everything happens within the expected time period. There is totally no human error because it follows a set of rules, and it always knows what to do during an approval operation. There is a 40% reduction in the errors that we had.

It has definitely freed up a lot of employee time. It has saved us 12 hours per week. There are cost savings and time savings. It has reduced the human resources required as well as the time consumption. We are now able to invest our time in other areas, and let UiPath take care of the heavy lifting.

The Orchestrator and the Studio are the features that I personally enjoy using.

It's pretty easy to build automations. Earlier, we had to do a lot of manual work, but with the introduction of UiPath, everything became very easy. The drag-and-drop components have made our lives much easier. Even non-technical teams are able to build an automation workflow within hours.

Their user community has been very good. For any questions that I post, I get the answers pretty quickly. They're friendly as well.

UiPath can probably work on improving the AI features. We tried UiPath's AI functionality in our automation program. We did some research on that, but right now, nothing is in production. When we did some research, we weren't getting the expected results. We weren't completely satisfied with the results, so we put it aside. It could be a drawback on our side in terms of learning the tool.

In terms of additional features, UiPath already has a plethora of options. All our needs are fulfilled by the features that are currently available.

It has been 15 to 16 months.

So far, we haven't faced any downtime in terms of using UiPath. It has always been up. It also has a plan for exposing multiple endpoints so that if one goes down, we're able to use the other one. So, the stability has definitely been great, and we haven't seen any downtime until now.

We use it as an internal application. There are around 500 to 800 members who use the tool in terms of the automation process. It has been good for our use case.

We have deployed everything in the cloud, and we also have the ability to integrate it with other AWS services. For the environment basically, we have different stages. One is the beta stage and the other is the production stage. In the beta stage, we do internal testing, and once it's ready, we deploy to the production environment where it communicates with other services like AWS.

We don't have any plans to increase the usage of UiPath at this time. If we need to expose anything to public-facing customers, we might think about it.

Their technical support has been great. For any doubts we have, we reach out to them via email or via a personal contact for our organization. Whenever we need support, they are totally willing to help us out. I would rate their support a nine out of ten.

Positive

We had an in-house solution that we developed, but it was not scalable, and there was a lot of maintenance work that we had to do to make it work. So, we migrated to UiPath. That was the only solution that we worked on. We did the research, and we found out that UiPath is a leading tool in the industry for RPA, so we hopped onto it.

I was not involved in its setup. I was more involved in the development once it was set up.

We are using the UiPath's cloud version. We don't have any on-premise setup. If we had an on-premise setup, we would've had to maintain all the servers and make sure it's running all the time. Because we completely migrated to the cloud, the maintenance is not on us. UiPath takes care of that. It's definitely a big win for us because we migrated from the on-premise system to the cloud system.

It requires very minimal maintenance in comparison to the on-premise setup. In an on-premise setup, we have to maintain all the servers and make sure it's always running up, but with the cloud version, there is very less maintenance on our side. There is an IT team of around two to three people who maintain the systems.

We could see an ROI within a month. We were able to see the benefits of the automation processes within a month. There was a 25% increase after implementing UiPath. There is an increment on a year-by-year basis.

We are using its enterprise version. Its price seems okay, but I'm not sure because I'm not involved with the finance side. I'm more on the development side.

We didn't evaluate other options. We did some research, and we found UiPath to be a leader in the industry, and it also fitted our budget. So, we went for it and started using it.

I would definitely recommend it to others. Automation is going to be a part of everything in the future. So, every company should start adopting UiPath for any internal or external needs. Automation is the best way to go ahead.

We used to do the entire process manually, and we found a lot of errors. It was a time-consuming process on the whole. With the introduction of UiPath, we definitely saw the benefits of automation and a smooth process with fewer errors.

I would rate it a nine out of ten. It's one of the best RPA solutions out there. I'm reducing one point for the AI features. Apart from that, I find it great.

We automate the entire revenue and order to cash and then process it to payables. It is used for processes, from generating customer invoices to ensuring that all our vendors are getting paid timely. We also use it for data reporting, audit requirements, or whatever information gathering that the company may need.

We've automated about 30-ish processes, and that's just the tip of the iceberg of where it's going.

All of the processes are attended to right now. We're still getting the backend set up to move some of them to unattended.

The solution has improved the organization by providing time savings. That's one of the most fundamental things. We recently had a project that would take a human who's actually navigating through the screens and clicking all the buttons roughly a month's worth of work, if that was their primary focus all day long. We were able to get that completed within two days using UiPath. Therefore, the time savings are phenomenal. 

Also, when you're dealing with all that data, there's a lot less likelihood of human error and missteps. With the bot, we know for sure that the line is the line, and that's it. It's error-free for the most part.

The low to no-code is by far the most valuable feature. Developing a bot in under a minute that saves you an hour a day is phenomenal.

The user community is great. Looking at the forums, when a question is posted, the responses are fairly quick, either from UiPath or the community itself. In my past role, I posted to the community before, and I had been able to answer some questions as well. Then, it's nice to know people are having the same problems you're having and finding solutions.

I've taken UiPath Academy courses. I've taken mostly the developer ones, and then I'm looking into more of the admin side, with the Orchestrator and project management side of it. The biggest value is that it walks you through step by step and you're doing it alongside the course. It's hands-on learning. It's one thing to watch a video. It's a different thing actually to play with it and have something start working.

Overall the training and documentation could be better. There's just so much of it, so a streamlined way to get to the information I need would be ideal.

I've used the solution for about two years. 

It's very stable. Performance-wise and stability-wise, it's great. We're able to access it from anywhere. I have the Orchestrator app on my phone, so I can always keep track of the bots that we've developed and see how they're doing and everything.

Scalability is something we're still looking into. We just started, so we're still in the groundwork. However, in terms of being able to scale, the potential's there. We just need more time to play with it.

I've had one instance with them, and it was great. They knew their stuff, they walked me through everything.

Positive

Before UiPath, we used Nintex RPA, and then an SAP RPA tool as well. We used to UiPath to get more usability and scalability. The user-friendliness of the product and just the engine and the innovations that they're making behind it really placed them as a leader in the sector.

I was involved in the implementation since proposing the idea to start developing and starting a road show to be able to expand.

The process was straightforward. I had no qualms about it.

We started small. We essentially had two developer licenses, a couple unattended, and then a couple attended. We had already identified who would the attended bots go to, and did all that legwork in the forefront. Once we got the license enabled, we could activate it, work in the Orchestrator to assign the specific roles, and then have them start running. Within a week, we were able to get bots out the door and have people actually using them.

Everything has been done in-house. We've been building everything ourselves. 

We've definitely seen an ROI. For example, in one project, we were able to take a month's worth of human effort and completed it in two days with UiPath. We've had several others of a similar nature.

The pricing is a bit high compared to other products. That said, it does offer more. From working with other ones, it is definitely a more powerful tool and well worth the pricing.

We did evaluate other options. We had the ones we used before. We also looked at Blue Prism, Automation Anywhere, and a couple of others. 

The difference was a sense of familiarity. I had previous experience with UiPath. Mainly the innovations and the fact that since 2019 on the Magic Quadrant, they've been the leader consistently, and they will continue to be, were the reason we chose UiPath.

We do not use the AI functionality in our automation as of right now. It is something I'm interested in, however.

Our company will be involved in an environmental initiative using UiPath. We have an environmental group. As of right now, we haven't thought about taking it that far. We've only had it for about a month or two. It's something we're considering for the future. 

The most important part is going to be the user interface. The people who are developing it, the people who are using it, they're the ones who are going to have the most to say about it. Your business end-user has the most to say about it; if they don't like it, that's all you'll hear. By focusing on that user interface, which UiPath has done, you really get a solid project that people get excited about rather than leaving a bad taste in their mouths.

I'd rate the solution a nine out of ten. I love the product.

We have very restricted usage, primarily around integration situations where we don't have any APIs. We primarily want to do just unattended automation. We discourage attended automation at this time. We have ten to twenty processes happening right now.

The improvements we've seen are primarily around the time and cost savings that surround someone sitting and manually syncing data between SaaS platforms. Although we use the latest and greatest SaaS platforms, they still don't have to interact with each other. There are no APIs in most cases. In those situations, rather than having someone manually sit and do it or have the product vendor customize it, we use UiPath.

For example, a couple of automations save us at least a year's worth of manual effort. Day in and day out, there is a SaaS platform that creates new data, and that needs to go through the different SaaS platforms. And that's the major statement we have. Then there are a few legacy applications we have that are near end of life. We don't intend to bring new APIs to them. Instead, we use UiPath.

I personally use the Academy often, and I have encouraged a couple of .NET developers within the organization to take up the certification. We have system integrators and local offshore vendors. They don't have certification right now. However, I am encouraging them to get certified. They're using UiPath Academy.

For me, the biggest win for the Academy was around the infrastructure and the sales switch around it. In my role, I'm required to go and talk to business functions and technology leaders. I have to tell them what the product can do, how it is deployed, etc., at the level of ownership. Plus, thought leadership needs to come from me, and those academic courses help me a lot.

The user community is definitely robust. I see lots of contributions, and people are willing to come and respond to any posted queries. 

The key reason we are not able to adopt it fully compared to other customers is the security model. Usually, what happens is whenever we talk to a business stakeholder, the first concern is data security. The moment that you talk about a bot in an unattended fashion going and reading the data source, concerns arise since there's not much control at a certain point.

Security remains a concern. We have completed all our security assessments. However, that continues to be a key question. There are use cases that are based out of Europe. If we have an instance in North America, again, the question of GDPR and all those questions arise. For example, does that mean that we have to have multiple tenants in different geographies? We are still trying to solve those kinds of questions.

There are situations in the community where, due to the fact that the product is so rapidly evolving, lots of the content out there is outdated. It leads to that lost effort when you try to do what they're saying, and it doesn't work due to it being a different version. That's probably one problem that I have noticed so far.

I've used the solution for a little over three years.

The stability of the product is very good. 

If you look at the key components and the visuals, I mean the Studio, the Bot, and the Orchestrator, the Bot and the Studio are within our environment. We haven't experienced any issues. What is left is the Orchestrator, and we haven't seen any outages so far.

I don't have any concerns with scaling.

I haven't created too many support requests. That said, the most recent one did not go well. The engineer had some trouble understanding, and the issue is still ongoing.

It wouldn't be fair for me to judge their support just based on those one or two tickets I worked on. I'm sure they have a good team. It was just that one ticket did not work out.

This was our first RPA tool. 

I was involved in the development and deployment. 

The virtual machine setup and the Robot and Orchestrator connection definitely were a little challenging. However, in the current version of the application, Orchestrator, it's far more seamless. Three years ago, it definitely was not that straightforward. Everything has gotten easier. 

The first automation took between three to six months, from initial procurement and development to deployment.

I did the deployment myself. 

In terms of ROI, we are getting there. It's not like as good as I anticipated. That said, we are getting there.

The pricing is fairly decent. It was not crazy expensive. Their cloud deployment gives you that sweet spot in pricing. You don't have to spend $20,000 for the Orchestrator, for example.

We assessed all the market leaders and did a couple of proofs of concept. It turned out that UiPath checked all the boxes from a capability standpoint and user-friendly developer experience, plus the deployment experience. UiPath was a clear leader.

We do not use UiPath AI functionality in our automation program. At this time, it is limited to OCR capabilities.

We currently are unable to automate more complex or involved processes. It is still in the conceptualization phase. We haven't put it into production yet. However, we are exploring their invoice management capabilities and more.

We have yet to develop some sort of social responsibility initiative using UiPath. However, we might in the future. 

I would invite potential users to look at the library of activities that are there. Make sure that the kind of use cases that they're looking at are present, and the level of security that they are looking for in terms of data. If you have less intensive security challenges, it's a no-brainer to use UiPath in the cloud. However, it might get a little tricky if it turns out to be healthcare or anything of that sort. You'll have to work with your data protection team.

I'd rate the solution a nine out of ten. 

When I started at my company, they were building their RPA journey. I was the first person to help them do that. As no one in my company was aware of what RPA is, we needed to showcase and publicize what UiPath is and what RPA is.

I work for an insurance company and there are handwritten scripts that need to be scanned in, and this was the first use case that I had to work on. We used the OCR technology to scan handwritten documents and its capabilities are evolving day by day. When I initially started, it was not as robust as it is today. We had some challenges with the OCR technology, but today we are able to do it successfully with validations.

Right now, there are 24 automations of which 22 are in production and two are being built. These are all unattended bots. I also use this solution in a personal capacity to delete all the junk emails I receive as I usually get 20,000 junk emails a week. This saves me a lot of time. 

The UiPath's user community, in terms of the value that we gain by being part of it, is very helpful. If I'm stuck with coding, that is the place I go to get assistance. The ideas and the solutions that they provide are very helpful. There are a few people in the community who are very accurate and their solutions always work.

I have also made use of the academy. Currently, I'm taking the certification training and planning to get my certification done by the end of this year. It has taught me new ways of doing things including dynamic selectors. Previously, the bots used to break because of a selectors issue, but the dynamic selectors solved this. 

We have an internal process that is manual and takes three days. The first day involves pulling in the data, the second day involves validation and the third day involves delivering it to the relevant system. We automated this process using UiPath.

The errors have been minimized. Whenever something goes wrong, we immediately get an Outlook notification. This is when our business customers get to know that there's something wrong with the input data that they're getting. They can directly deal with the input information data team and get that information corrected and this usually happens within three hours. 

The OCR technology within this solution has been most valuable. We are able to scan handwritten documents and scrape their contents to be captured within the system. 

When I first started using this solution, the OCR technology was not that good, but it has since improved. Most of the handwritten documents are easily read by the OCR technology. 

I have been using this solution for three years. 

The stability does depend upon the applications we are using but overall the stability is good. 

This is definitely a scalable solution. 

The first time we had issues was during the setup and we haven't needed to contact the support team since then. Their support is really good and the solutions that they provided really worked from our side. They provided step-by-step instructions that really helped us a lot and saved a lot of time. Our initial estimate to get that UiPath deployment was two and a half weeks, but we finished that in three days. This was made possible by the support and the instructions received from the support team. 

I would rate the support for this solution an eight out of ten. 

Positive

I was the one who did the deployment. During the deployment, we had some challenges but received assistance from UiPath support. Even though we had some hiccups in the initial days, we were able to still overcome those with the help of UiPath support. The deployment took two to three days for an on-premises installation. 

Our business has been highly satisfied with the RPA solutions that we are providing thanks to UiPath.

The pricing for this solution is reasonable. 

We evaluated Blue Prism but felt UiPath is easier to use and offers better performance.

I would rate this solution an eight out of ten. I would rate it a ten out of ten if this solution worked better with our other applications. 

I would definitely advise others to consider UiPath because it is easy to learn how to use. A lot of documentation is available and accessible to facilitate learning including YouTube videos. 

When I was evaluating Blue Prism versus UiPath, the training materials were not the same for Blue Prism. Coding using UiPath is really easy and is mostly drag and drop. 

We're a consultancy and I am the strategic architect. I have implemented the product at 25 different client locations spanning multiple industries. Their RPA requirements range from pretty standard, bread-and-butter workflows that navigate an application and follow some business rules, to more sophisticated ones that are integrating Document Understanding and a little bit of chatbot.

I have deployed it on multiple application stacks, including out-of-the-box SAP, Oracle, Microsoft, and some specialty, third-party products like DNA, Encompass, LendingQB, and others.

We have helped companies reshape their resources. That's a part of the benefits. They want to put automation in place because they want to change their headcount and not have to do those rote, mundane business processes.

We have been able to show enhancements in resourcing. A very good example is that we built a process for a client who had to spend three or four days a month doing a really lousy process involving 3,000 payment transactions, every month. The robot is able to execute that workflow in a half day, so we freed up two and a half to three and a half days where he does not have to do it. To him, this was a huge lifesaver.

It has also reduced human error, for sure. That's a positive selling point. When we build workflows for our customers we include business reports and audit logs. We typically add a status flag for a record so that every record that is transacted has traceability through the audit log. We also have a status report, and that shows how many records the workflow executed, how many were successful, and how many failed. We see a range where between 65 and 90 percent of the records go straight through. That means all the business rules were met and the process was completed for those records. That shows that they're identifying a much smaller subset of errors and that they can rely on the robot to successfully complete the end-to-end transaction. And whatever is leftover requires human touch.

That changes the dynamic in operations. They don't have to concentrate on every single record, but only somewhere between 10 and 35 percent of all records may have to be handled manually. It shows them which ones had errors, the ones that did not meet the business rules, and they know which ones to concentrate on. That's a feedback loop that helps them decide if they need to add a business rule or change a business rule to get to a higher percentage of throughput.

In terms of employee time, I have documented situations where clients might have had 10 people working on half a dozen business processes. We've implemented IPA—intelligent process automation—and then they only need three or four people, so they can redeploy those other folks to other places. It saves them money because they don't have the FTE costs they had before for those processes.

From a development point of view, the Studio tool as the basis of componentized architecture has been a really critical part. You get out-of-the-box, componentized architecture to jumpstart or accelerate development and that's a very key feature. 

When talking about deployment, you have a very robust infrastructure to manage your automations, the robots, and how they can be configured, deployed, executed, monitored, and maintained. 

When it comes to process discovery, it has excellent front-end tools and capabilities vis-à-vis Task Capture and Automation Hub. 

And at the back end, the notion of botting sites to monitor and manage your robotic infrastructure and reporting on it is pretty great. These are all pretty good tools.

The ease of use is because of the UI's capabilities. The fact that it has a .NET Framework, from a developer's point of view, makes it a very easy product to jumpstart into. But what is key is the ability to do really fine development activities. You really can get to a nuanced level of development for complicated and robust workflows. The tools are definitely well constructed to allow you that kind of flexibility. 

A really good example would be if you are doing something with OCR to read a PDF. You can vary the OCR engines and test them out to determine which OCR engine will give you the best results. That's pretty good because you do get into situations where one engine may work better than another.

We can also implement end-to-end automation and that is critically important. We always strive for what I call "straight-through" processing, where we're trying to handle all the use cases based on business rules. We're not always successful, but that's not a bad thing. If we can take 60 percent of your processes and automate them with straight-through processing, where everything works, your exceptions are a much smaller work set. That has had a significant impact on clients. For one of my clients, where we have worked very hard, they have better than 90 percent "throughput," meaning that 90 percent of their transactions go completely through the automated workflows. The client has been incredibly pleased with that.

We also use the UiPath Academy all the time, in two ways. Internally, we avail ourselves of all the courses. It's especially important to understand new updates and releases. It's a great place to go to understand what those new features are. That is of real value. 

But the Academy is also a good starting point when I want my engineers to be certified. They can jumpstart that process by going to the Academy and making sure they know how the product works. They follow through on that program and complete the training. Once they finish that, we try to get a project or two under their belts, and then have them take the certification exams.

One of the chief problems in all of our implementations is "application sensitivity." If an automation involves a webpage or Outlook, every item on that screen—the menu bar, the actual document, an attachment, a field—has a selector so that workflow can work correctly. UiPath does a very good job, whether for legacy systems or newer systems, of using selectors so that you can build applications that have discrete functionality. 

But what happens when a selector breaks? That means that something has changed in the application. This is especially true with SaaS or third-party applications. They make one change to a field and the selector breaks and that means it has to be touched and fixed. 

UiPath could do a better job of enveloping selectors to make them less fragile. There are techniques that can be used to achieve that, even without a system-related improvement, but they are not out-of-the-box. That is the one area that is the biggest pain point. It happens all the time.

They should reduce selector sensitivity and improve remediation when one does break. 

I don't know how they would do it, but if the change that caused the break were a relatively minor thing, they should somehow have it automatically recalibrated. I'm sure it's a tough problem, but clients complain to me about that all the time. I have to explain to them, "Well, the application changed." They'll say, "Well, we're looking at it, we don't see anything." It's often true that you can't see it, but the selector underneath broke and that means something was done but, visually, an end user would not see it if it was a minor change. So I'd like UiPath to find a way to "desensitize" selectors.

I have been using UiPath for four years.

It is very stable. There are no questions about that.

There are absolutely no issues with scalability. We're using this with multiple clients.

The new robot polling is very helpful. We are using it effectively for clients and that technical capability is a great enhancement. The modern folder profile gets us there as well. 

We're very pleased with the cloud-enabled product sets. I push that with as many clients as I can because it's the easiest to implement. On the cloud side, there were issues at one point with their licensing management, but that has finally been smoothed out and that makes life easier. If you want to add another product, as long as it gets licensed, boom, it's there. I don't have to think about it. Overall, the scalability is great.

The environments that we work in are client-driven, but they can have multiple locations and geographies. We have a couple of clients where the implementation is in the US but it is supporting Europe. And we now have a client that needs to be supported in South America. We are cloud-enabled for them and the product works great. And while it has nothing to do with UiPath, there are some latency issues over the network, so we may have to rethink how we deploy in different hemispheres. But we know that UiPath tech can support that.

We will lean on their technical support when we have exhausted our capabilities. Most of our issues have been in the Document Understanding sphere, especially in custom model development, although sometimes there have been issues with it in out-of-the-box systems. For all of my IPA projects that include Document Understanding, I try to convince the customer to buy Premium Support, because regular support could take two to three days to finally get to the right answer. With Premium Support, I'll get it in a day or a day and a half, and that can make a big difference.

I rate their support at seven out of 10 because the initial triaging takes the longest time, and that's one of the greatest concerns for me. If you have regular support, as part of the triage process they will tell you to look at frequently asked questions, but of course, we've already done that. Overall, the FAQs are one of the weak points in the fabric of available resources. We're putting in a support ticket because we haven't found what we need. That level of support is very generic and you really have to knock hard on their door hard and say, "We've done that already. We haven't found our answer. We need to talk to an engineer." Level-one support is usually too junior, but when we get to the next level, we finally start to get better answers. Level two is good, but level one and that triaging can be painful.

We rely on the partner network, and UiPath has been an excellent partner. We do use the community as a reference point, but we don't get a lot of value from using the FAQs.

On the flip side, I have used the Community editions of all the products. That's a big plus, especially when a client doesn't want to put any money into it upfront because they're very nervous. We use the Community edition to prove the point. In that respect, the Community edition and the forums do become helpful.

Neutral

I started with Automation Anywhere in a previous job. I like both products. Both it and UiPath are excellent. Going with UiPath really had nothing to do with a problem with Automation Anywhere. When I came to my current company, they had already decided to go with UiPath. They had done a few projects with UiPath and that set the tone going forward.

As a consultant in a global practice, I do have a couple of Automation Anywhere projects going on. I also have a project that is using Power Automate. 

Our preferred IPA solution is UiPath, but clients drive that decision. I had one client who said, out of the gate, "No. We're using Automation Anywhere. No questions asked." And I said, "Alright. It's a good product." 

But as a company, we lean toward UiPath as a starting point and they've been an excellent partner, and I say that wholeheartedly.

Deploying the solution is straightforward. It involves a low level of complexity and less effort.

I have a separate DevOps team that actually does the build-out of the environment. They're separate from the developer team. DevOps does the implementation. They'll talk to the client's IT department directly and work on all the details of setting up the infrastructure and they'll get it ready for us. Then the developers take over.

We do lean on UiPath support in some niche issues areas, but for the most part, my engineers are pretty well qualified.

In terms of the solution's AI functionality, such as Document Understanding and chatbots, we no longer advertise ourselves as doing RPA. We advertise ourselves as an IPA shop—intelligent process automation. The focal point of that is Document Understanding and the DRUID AI Chatbot capabilities. We're getting an awful lot of Document Understanding projects and we use our sandbox to pump our clients' data into the Document Understanding frameworks and intelligent form factors to prove that the solution works. We really want to go for the bigger ticket items that require Document Understanding.

When dealing with Document Understanding, we are introducing a new capability to the client. We train them on how to use the tool. That is a definite change in the client's skill sets and it does pay for itself in the long run. There is a delicate balance. The investment cost is always the tricky part, but once clients start seeing their data coming through automatically, the light bulb comes on.

Since UiPath became a publicly traded company, the flexibility and variability on pricing have really gone down a lot. It's tougher to get a better deal out of them. I'm not saying it can't happen, but as a publicly traded company, they're not the same company that they were when they were private and first growing. It's understandable. They have stockholders to answer to.

The top vendors are

1. UiPath
2. Automation Anywhere
3. Blue Prism (which we don't do a lot of work in)
4. Power Automate, only because it's Microsoft.

I encourage people to look at the review and evaluation sites to help them start getting an idea of what is available. Then I say, "Here is some actual work we've done with UiPath. This is our actual experience. Check the marketplace data that's out there," because there's a lot of information they can avail themselves of. That way, they can be satisfied that what our company is recommending is valid.

I may point out some of the key questions for them to look into. If they're trying to scale, what are the business problems they're trying to solve? If they're thinking about a Document Understanding requirement, they should compare what's going out there with other intelligent document processing capabilities and take it from there.

As a partner, what has been helpful is that UiPath offers a not-for-resale (NFR) license. These are fully loaded licenses and ours is cloud-enabled. We're using them for PoCs very effectively. There is a lot of great value in them. I have a couple of projects now where we've asked clients to send us their sample data, their documents. We have our sandbox ready and I have one or two developers knock that process out with a turnaround of one or two days. We can bring it back to the client and say, "Here's your data and this is what we were able to do with it." That is very effective.

I really appreciate the way the product has been architected. It's a robust product set. We have built custom models with the UiPath toolset. We've had several use cases where we had to do so because there was no out-of-the-box solution, and the tools are great.

The AI functionality has enabled us to automate more processes overall. They are the more difficult projects to do because Document Understanding is not a pure, out-of-the-box solution. There is work involved in it but we've been successful at it. Once we get the models well-trained, the client starts to really see real value. They're seeing the straight-through processing that they're trying to achieve.

The client I mentioned earlier, the one with the 90 percent "throughput," is an example. That automation is the result of custom models. We worked hard on that and we were very successful. The client has been very happy.

Overall, the way I would rate UiPath depends on the support level I have to use. If it's Standard Support, it's a five or six out of 10. If I have Premium Support, it's a seven or eight.

My primary use case with UiPath is to automate workflows for processes in web-based applications, such as email and Excel automation. We also use it as a task or workflow management tool, capable of assigning tasks, checking on the status of tasks, and more.

Another thing that I have been doing with UiPath is replacing repetitive tasks performed within the organization. Automating such tasks makes the related process smoother and faster. 

We are using the UiPath automation cloud offering, which is a SaaS solution. One advantage to this type of environment is that we can get updates instantly. If it were an on-premises or hybrid model then the setup and maintenance take time, but this isn't the case with a SaaS model. This instant setup is what we needed because it made for a smooth transition from manual processes to automation. 

With respect to building automations, UiPath is a pretty straightforward platform. The major reason that we choose to implement UiPath is the interface that it provides, which boosts the usefulness of the entire platform. If we need assistance then there are many knowledge base documents available. There is also in-app help, which makes it very easy to understand and start using it.

I was able to learn how to use it within a week, which shows how easy it is. For example, it does not require a lot of coding. It's more of a drag-and-drop interface, making it easier to develop programs and automate processes.

UiPath enables us to implement end-to-end automation, and it has completely replaced the manual processes that we were using. This includes analyzing the process and implementing automation to collect the data. Data fetching is done using the robots that we create.

Since implementing UiPath, we have experienced better retention of our users. This is because we have been able to make our process much smoother, as well as quicker. Consequently, we have been able to deliver at a much faster pace. This has enhanced the customer experience and in turn, has improved customer satisfaction. Overall, we have seen an increase of about 30% in terms of user retention. This has translated to increasing revenue.

With respect to automating our processes, automation has reduced our manual efforts by more than 70%. This means that we are able to concentrate more on other aspects of our business. The business is growing because we are able to do things like work on our website, customer engagement, and customer relations.

UiPath has taken care of most of the backend work for us, which is a good bonus. It has reduced our investment in manpower by about 50% and decreased our overall output time by more than 70%.

Automation has definitely reduced the rate of human error when compared to our previous, manual processes. At this point, there is minimal to zero human error. I estimate that approximately one hundred percent of human error has been eliminated.

Implementing this product definitely helps speed the process of digital transformation, and reduces its cost as well. One of the goals of our organization is to completely digitize. We want to optimize everything so that employees can focus more on the customer relationship aspect, building more value for our brand. UiPath has definitely helped in improving the overall process.

Our digital transformation did not require any external support for third-party application software. It's an in-built process and we did not need anything extra.

The specific feature I like is folder organization, and it is in the Orchestrator tenant. This is very useful because it keeps all of my folders and data in a centralized tenant.

The menu options are easily accessible in the Orchestrator tenant, which is something that I like very much.

The UiPath Academy was pretty helpful for us in the initial stages. We were able to learn more about the software and what is there. They also provide courses and certifications, which assist with learning and getting employees up to speed.

It took only a week for me to completely get a handle on the software. Taking the initial training and certification courses is a hassle-free process. It is not difficult to induct somebody and have them start using the product.

The courses that they offer provide hands-on experience, and I think that it's a good initiative that they are taking on by doing so. It helps to ease the learning curve and allowed us to learn more about the world of automation.

UiPath has a user community that is very knowledgeable and friendly. Our peers in the UiPath community are able to dumb down responses to a beginner's level of experience, regardless of what queries we have put forth. Whatever we have wanted to do with RPA, they have been able to help. We now have a good level of comfort in terms of interacting with our peers in the community.

We have experience with other communities and have found that the discussions are generally at a higher level, which may be too difficult for a new person that is just starting out with the product.

Generally speaking, I like the features that I am using and I could not really say where improvement is needed in that respect.

The product could be made a little less glitchy. Specifically, when too many users are working at the same time, it hangs a little bit here and there.

In a future release, I would like to see drag-and-drop functionality in the robot creation process within Orchestrator. As of now, it is not available there. It would be helpful because from there, it is easy to create a process flow. Instead of switching between multiple menus and multiple tabs, we can do it from the Orchestrator or the main menu.

I have been using UiPath for approximately a year and a half.

I would rate the stability an eight out of ten. Sometimes, when the load is high or there are many users working at the same time, or when I'm working on different parts at the same time, it lags a little bit. There is a slight drop in performance.

Otherwise, it's very stable and secure software.

Using the automation cloud offering has meant that scaling up automations has been very smooth for us. We started out with between 40 and 50 users working on this particular tool, and now it's between 150 and 170 users.

There are two levels of roles; admin roles and user roles. The admin role is able to assign and approve tasks, using the task management module. Regular users are able to perform all of the other functions.

It is definitely a scalable solution, being cloud-based and SaaS. It is also very customizable. Customizability is the unique selling point (USP) for this particular product, given the number of customizations that are available and the number of features that can be added.

The technical support staff is brilliant. They are very knowledgeable and very quick when it comes to addressing our queries. They don't ask us to wait for long when we have a problem, and we normally have a resolution within hours.

There is also a community forum that helps us to deal with problems ourselves, without the dependence on the technical support team.

I would rate the technical support a ten out of ten.

Positive

We did not use another RPA solution prior to UiPath. Before this, we were doing everything manually.

I was not involved in the initial setup and deployment.

As we opted to implement the cloud-based model, the maintenance on our part is minimal. We just have to update the software from time to time. The amount of maintenance that we perform is not only easy but saves a lot of time for our IT team.

The team of people for maintenance consists of six or seven junior IT staff. They perform the updates and nothing more.

Using the automation cloud offering has helped to decrease our time to value. An example of where we saw the benefits of this solution was with an Excel automation that we created. This process involves an Excel worksheet that contains between 20,000 and 30,000 records. We had to manually search for particular records, and the process to approximately a week to complete. Now, with UiPath, the same process is completed within a couple of minutes. 

Once we signed up with UiPath, we instantly saw growth in our entire business. It was a win-win situation. 

The additional time has enabled our employees to focus on higher-value work, such as R&D, customer engagement, and improving our brand. It also has an effect on employees' satisfaction, specifically, mine.

A lot of time spent doing repetitive and redundant work is something that was irritating me a lot. Now that the automation is in place, I just have to set up the workflow. It has definitely increased my overall morale and satisfaction. 

One of the downsides to UiPath is the cost of the enterprise version. It is a little bit on the higher side.

UiPath's cloud offering is a centralized, all-in-one platform. It saves money because you don't have to invest as much in other software, and it's cheaper than some solutions because you don't have to maintain the platform or the database. However, because it's not cheap, the overall cost reduction is not drastic at first. Taking a holistic view, it does because overall, it will reduce costs.

There is also a Community Edition that can be used free of charge. This is an option for users that find the price to be high. One main differentiating factor with the Community Edition is the number of updates. There are fewer in the Community Edition.

Also, the support offered for the Community Edition is not as quick. People will not have a great user experience. However, it is important to remember that in terms of cost, the Enterprise Edition is a little bit pricey for small and medium-scale enterprises. 

About a month ago, we started using the AI functionality of the software to design robots and processes. At this point, we are looking to use AI for our internal applications.

One example is that we are working on security-related automation that triggers an alert when somebody inserts or removes an external hard disk from a system. Taking advantage of the AI capabilities has helped us to maintain a much safer work environment, in terms of data security.

The AI functionality has definitely enabled us to automate more processes. A lot of manual work and redundant work has been reduced. Also, the number of errors that we had occurring during our manual processes has been greatly reduced.

This solution has definitely helped to free up employee time. Tasks that used to take approximately a week, now take just 30 or 40 minutes. This is a lot of time saved, which allows us to concentrate more on other aspects of the business. For example, improved customer engagement has resulted in gathering more leads. Also, we have more time for R&D.

I estimate that we are saving approximately five hours per day, so 20 hours per week, per employee. In addition to the areas that we have more time to concentrate on, it has helped improve the value of our brand overall.

My advice for anybody who is looking into implementing this product is that it's a must. This is the go-to software that I would recommend for anybody looking to automate their business in a smooth and efficient manner.

Cost, of course, is something that has to be considered but if they can afford this solution then they should implement it. It has a wide variety of features and functionalities, which are market fit and market ready. 

I would rate this solution a nine out of ten.

We have a web application, and we also have iOS and Android applications. We are automating the regression testing part for these applications. Mainly, we are navigating and interacting with UI elements, and we are verifying certain buttons. We are also verifying certain data with RDBMS outputs.

UiPath enables us to implement end-to-end automation, starting with process analysis, then robot building, and finally monitoring of automations. UiPath has been doing well in terms of Orchestrator and how we can see the execution and the reports and results of our test cases. It is doing well in these aspects, which is very important for us. We are doing end-to-end automation and monitoring using Orchestrator, and it is quite useful. This is something that we were looking for while deciding on the automation tool that we would like to go with, and that's why we decided to go with UiPath.

It has been helpful for regression testing. We are developing a big web application, and we are expecting changes every quarter. The development and deployment have been going on every quarter for the past two years. Previously, we had a team of seven or eight people who were doing the manual testing. By automating the testing, we have reduced the team's size to half. The remaining team members are not just analyzing the executions that we are doing with UiPath; they are also providing support. It has increased employee satisfaction because they don't have to do repetitive work again and again. It has been quite good.

It has been useful for unattended automation, and it has also reduced human errors in our organization. Reduction in human errors is the best benefit that we have got from the UiPath implementation.

Automation is most valuable. When it comes to web automation, data scraping and UI-related activities, such as the Find Element activity, are quite useful.

UiPath Academy courses have also been very useful. Whenever we have to work on something new, I go to UiPath Academy and browse all the resources that they have provided. When I started working with OCR about two or three months back, I used UiPath Academy courses. They are very helpful, especially for new people who join the team. New associates need exposure to the tools that we are using, and the content that is present in UiPath Academy is quite good. It gives them an idea about the tool and the things that they can do with it. UiPath Academy has been quite helpful in training new associates.

UiPath is developing day by day, and there are certain products, such as AI Fabric, that UiPath has launched lately. These products are quite new to most of us in the RPA industry. Because there are courses available for these products in UiPath Academy, we are able to get an idea about a tool, its capabilities, and how to use it.

There is a big room for improvement when it comes to mobile automation. The Find Element activity is not present in mobile automation. There are activities to extract data, but we don't have data scraping in mobile automation. These activities are available for UI automation of web applications, but they are not available for mobile automation, which is a drawback when working on mobile automation with UiPath.

There are also so many bugs in mobile automation. I've been working with mobile automation for the past six months, and in the past six months, I have found so many bugs. We have reported them to UiPath. Some of them are posted on the forum, and I haven't seen any positive feedback in terms of whether a bug has been created or they are working on improvement. So far, there is nothing like that. 

There is also a bug related to the Pick Branch activity, and we can't really work with the UI elements in this particular activity. This issue was first reported by someone in 2019, and this post is available in the forum. It has been more than two years, and this bug has not been fixed. 

For mobile automation, there is a tool provided by UiPath called Mobile Device Management (MDM). We do the automation using that tool. In our project, we are using cloud APM services. UiPath Studio communicates with MDM, and MDM communicates with Sauce Labs, which is the cloud APM service provider for us. There is a huge gap in the synchronization of both of them. I have observed a visible difference. When I execute an app activity, it gets executed at Sauce Labs very fast. The final output that we should be getting first comes to MDM and then UiPath takes that output from the MDM, but there is a synchronization gap. There is a visible difference, and UiPath is lacking in this part. So, mobile automation is the part where UiPath can improve a lot.

I've been working with UiPath for almost two years. I'm into development, and I have worked on Excel automation, mobile automation, and web automation.

I don't have any opinion on its scalability at this time. In terms of its usage, we have to create 2,000 automations for our client, and we have already implemented more than 1,000. We don't run those automations every day. We run them as per the requirements, so there would be 200 to 400 processes once a week.

In my project, there are five people who are working with UiPath, but in my company, there are many more people. One of them is the manager, and four of them are working on development. 

There have been some bugs for which we connected with UiPath support. It was a mixed experience. There were some technical support experts with whom we connected, and they tried to get to the root of the trouble. They did their best to provide us with the best solution possible. We have also had other scenarios where there was no answer or explanation for the issue. We didn't get any positive feedback from them.

I had posted a few queries related to mobile automation on the UiPath community, but there was no instant solution. I was expecting a reply within one or two days, but there was no reply. Because this is a niche field, there are not many people working in this domain, but I got replies from the UiPath team on some of the queries. So, overall, the experience was good. I would rate them a six out of 10.

I was not involved in its setup.

It reduces the cost of digital transformation in a way. When it comes to the scenario of our automation, UiPath isn't so fast, and there is the speed issue that UiPath can fix, but because a bot has the capability of working 24/7, there is a reduction in the cost of digital transformation.

We evaluated Blue Prism. We didn't explore Automation Anywhere. After comparing it with Blue Prism, we decided to go with UiPath. As per our client's requirement, there were three applications to be automated, and because UiPath supported web automation and mobile automation for iOS and Android, we went for UiPath. We just had to buy the license for one, and we could automate all three applications.

Rather than implementing RPA on a big scale, I would advise starting at a small scale and doing good process task mining. It is very important to identify the right process to automate.

UiPath is quite an impressive tool. It was the first tool that I started learning when I got into RPA. Recently, I got familiarized with Automation Anywhere. I used to think that Automation Anywhere is better because it is on the cloud, but now that I know that UiPath also has a cloud option, I'm going to explore that option. It is a good solution, and UiPath is doing well when it comes to the improvement of the product. My experience is good overall.

We have not used AI-enhanced Document Understanding in our automation program. We are planning to implement it, but it may take a while.

I would rate it an eight out of 10.

We are on-prem within the insurance industry. Our use cases are in auto reports and micro use cases within that.

The biggest benefit we see from UiPath is the overall platform. It's not only the functionalities. As we started tying that all together in the platform view, with the orchestration forms and the workflow function, it'll be key, because it's been around in the industry for 20 years, but hasn't been tied to everything. 

It saves us costs but that's only one part of it. We are looking at it in terms of employee centricity, customer centricity, reducing the risk, and improving the accuracy. There's a multitude of factors that we are looking at.

We have seen a reduction in human error using UiPath. We are an audit firm at heart. We do a lot of audit and tax work, which is all related. Within use cases in those spaces, we see a change in terms of accuracy. It eliminates manual errors. Instead of just looking at 20% or 30% of the big picture, you can look at 100 of it because it's automated. 

The most valuable feature is the fluidity of the products. When I want to use RPA, I can use RPA. When I want to do process mining, I can do process mining. Those are the two top that I typically use it for. 

Building automations is easy. It's drag and drop. If you are a developer and want the full functionality, you can actually dive into it at a little bit more of an API level.

We use the Academy. I am the training and certification lead for our UI group of 200 practitioners. It's probably the only group in your partner community that's 100% certified. We are tied in into your training and certification piece and we are using and reusing the licenses to make sure that we are pushing out the updates from the platform through the training store.

Our training and certification programs are still gaining maturity. We recently signed the USN Certification with UiPath, which gives us access to brochures and AP credits. It makes it a little bit more formal because the process was there, but it was very informal. We were exchanging emails, but now it's tied together with the workflow. It's getting there. 

The breadth of the courses is the most valuable aspect of the Academy. This is my third year doing this. There has been an increase in courses being offered. 

The path forward is probably to tie this all together in a platform and look at the workflow automation. At this point, we are doing snapshot automation, point solution, and staff automations. The term RPA itself is a misnomer, it never was a robotic process, it was robotic task automation. We are automating tasks and the way to get away from that is to look at process level automation end-to-end. That won't be done with RPA tools, it has to be with the workflow tools. How do we tie in and how do we tie into, either the orchestration function or decisioning functions? They will tie into a broader transformation initiative. It'll be dual-edged.

I have been using UiPath for two years. 

The stability has improved in the last two years. As they push more functionality on that and go more cloud-centric, I think it will be much more stable. We just got through an issue yesterday, but it was resolved quickly. We knew what to do. We could figure out the root cause. 

Scalability has come a long way. UiPath is probably the leader in this, but as we look at broader solutions and a process-centric automation suite, we also have a long way to go forward. We are at a midpoint in the journey. It's on UiPath and the department of community to try to hook that together.

UiPath is our biggest alliance in the automation side for my company and the plan is to increase the usage. There's a commitment from the very top on both sides. We have stepped away from past automation and stepped into the broader use of it and the transformation journey. There have been micro transformation journeys in all sectors, whether it's financial services or outside of that and commercial, national accounts, and the public sector. That's how we're looking to scale and become even bigger in the next few years.

We use Automation Anywhere, Blue Prism, and Pega Robotic Process. Some of it is just down to the differences between what the tools offer. I've used all four of them.

Each solution has its pros, but in terms of speed to market, and improving the quality, the partner network, the product suite, and the product roadmap itself, UiPath is a few years ahead of the rest. That's reflected in the analyst reports.

UiPath is something that people can dive into. My advice would be to take a few courses, everything is available online. It really comes down to people's aptitude and whether they want to get into this. I don't think it's very difficult.

I would rate it a seven out of ten. Purely because there is always room for improvement, but it's on the right track. Product roadmaps and positioning are in the right space.