UiPath Platform Reviews

My main use case for this product is process automation. For example, we use UiPath to make quick and easy applications for our internal office use.

It has reduced repetitive tasks. We now have more efficient processes. Manual testing was one of the time-consuming tasks that we used to do. Our testing team used to spend days and nights testing. UiPath has completely boosted the process. For example, previously, if we needed three employees to do a particular manual test, now, because of the automation that is available, we require just one employee. It has saved a lot of time, and it has also enabled us to deliver better-quality products. With automation, less manual work is involved, and the quality of the product that we deliver is very good. We have also been able to automate a lot of tasks, such as compliance tracking.

It's very easy to build automations using UiPath. Most of the things are just drag-and-drop. People with zero to minimal coding knowledge can build applications using UiPath. It's straightforward. One thing that facilitates this is that a lot of in-app guides or inbuilt tutorials are available, which makes UiPath very easy for a beginner who is starting out with UiPath. With such a good knowledge base, it becomes very easy for them to get a grasp of everything and start building applications.

It enables us to implement end-to-end automation. It also improves the employee experience. In software development, especially in the field of testing, there are many repetitive tasks, and they are prone to many manual errors as well. Automation through UiPath boosted employee morale, and it also improved the customer experience. We have been able to deliver better products on time to customers with UiPath.

It's a cloud-based solution, and it has helped to minimize our on-premises footprint.

With the AI functionality, we have been able to identify areas where automation can be implemented. We are trying to identify where process automation can be brought in and efficiency can be improved. The AI functionality is good, but there's a lot of initial work that needs to be done for this. It has enabled us to automate more processes. Within a month, we have been able to automate around 40 to 45 processes that were pending for a long time. It has definitely speeded up the entire process.

It speeds up digital transformation and also reduces the cost of digital transformation. Less manual intervention is needed, and less manpower is needed. It definitely reduces the overall cost for the company. Also, when something is automated, it's very quick. Redundant or repetitive tasks are completely reduced, and a lot of time is saved. So, it definitely saves time and cost.

This digital transformation didn't require expensive or complex application upgrades, or IT application support. Everything was inside UiPath. We just took some additional training from UiPath to get it implemented. Other than that, we did not use anything.

It has reduced a lot of human error. With manual testing, there were a lot of errors. With automation, that has been completely eradicated, and a lot of time and effort has been saved. It has reduced human errors by 100%.

It has improved our customer experience as well. We provide services to our clients or customers. Any human error leads to a delay in delivering the application. With automation, we have completely removed human errors, and we are able to satisfy our customers. It has impacted the retention of our customers.

It has freed up employees' time as well. A task that previously required three or four employees just requires one employee now. We do not spend all our time on a process. Once we implement and start an automation process, everything happens automatically. We can concentrate on other aspects of software development. It has saved 20 hours per week or 4 hours per day. 

It has saved a lot of costs for us in terms of employee reduction. We now need just one employee for a task rather than four employees. So, there are savings in terms of employee salary. We are also able to retain customers better, which has improved our revenue. Overall, about 25% of our cost has been saved. We were losing revenue and customers because they were not satisfied. With UiPath, our efficiency has improved, and the time to market has reduced. 

There are two features that I like a lot in UiPath: one is the Orchestrator option, and the other one is the Studio option. I especially like Orchestrator because it's very insightful for us. It's like a centralized hub to manage and maintain all of our process automation and task-mining. It systematically organizes each and every folder so that it's easy for us whenever we need to know, set, or take something. Studio is where we primarily do most of our designing. It's a very good tool. Most of it is drag-and-drop. These are the two main useful features for us.

The dashboard view could be more visually appealing. Dashboards in any software should stand out with colors, numbers, and other things, but in UiPath, the dashboard is not that visually appealing. The UiPath team could make it more visually appealing for us to get more insights.

Another improvement area is related to product updates. Earlier, we used to get monthly updates about the product, but that has stopped now. If they could bring that back, it'll be very good.

We have recently tried the AI functionality. There is a lot of learning that we need to do with regard to AI. It's good, but it's not as smooth as Orchestrator or Studio. The AI aspect of the product could be better. We're currently working on allowing the AI to automatically detect areas where automation can be brought in and efficiency can be improved. That needs some more refinement. It's currently not straightforward. Sometimes, it just repeats whatever it said previously, so nothing new comes out of it. The AI aspect of the product can be much more refined. Apart from that, I don't have anything else. It's a well-thought-out and complete product. It's very easy to use and easy to understand.

I've been using UiPath for around a year.

It's a cloud-based solution. It's very stable, and we just need to make sure that it's up to date. Personally, I have not seen any bugs, errors, or performance issues with this. We are not using an on-premise model. It's cloud-based. So, the service is always available, and it's always quick. It's very stable, and I have no complaints.

The applications that we develop with UiPath are also very reliable. They don't crash or have any performance issues. They are very stable and reliable.

When we started with UiPath, our main use case was to be able to quickly and easily make applications for internal purposes, but now, we are doing a lot more with UiPath. We are doing compliance, and we are doing AI-related process automation. It's definitely a scalable solution.

It's deployed across multiple departments. Each department has its own RPA functionality and RPA usage. In my department, 20 of us use UiPath, but I'm not sure about its users in other departments. 

Their support team is very knowledgeable. Whatever issues we have, they try to explain them to us in a better way. The SLA or response time is pretty quick. It's 24 hours for us. I have no complaints. I would rate them a nine out of ten.

In addition to the support team that UiPath has, I depend on the user community for all my queries. I see the UiPath Community as the main support tool. It's my go-to space for anything related to UiPath, and I am very satisfied with the quality of the community.

Positive

I am not aware of any other solution that we used to use.

It didn't take a lot of time to implement, which is a very good thing about UiPath. In about two to three weeks, we got the entire setup done. That was very quick.

It's a cloud solution. We have deployed it on AWS. Being a cloud solution, it requires very less maintenance from our side. That's one of the very good things about UiPath. We just need to make sure it's up to date.

We have definitely seen an ROI. Customer satisfaction has improved a lot. We have been able to retain customers better, and we have been able to reduce manual errors by 100%. 

Its pricing is straightforward. There are two editions: one is the community edition and one is the enterprise edition, which is a paid one. The paid edition is priced reasonably.

They charge extra for additional training and implementation, but that should be bundled up with the enterprise edition itself. All in all, it's reasonably priced.

To anyone considering UiPath, I would advise checking out the trial version of UiPath before going on to the actual version. Before you start using UiPath, there are a lot of things you need to get your head around. People who generally use UiPath have zero or minimal coding skills. This is something that you definitely need to know.

You can try out the UiPath Academy as well. They provide certification courses. I have not used UiPath Academy, but I have seen my team using it for the certification program they offer. I have heard that it's very good.

I would rate it a nine out of ten because I have not faced any issues with the product. Whatever we wanted to achieve with this product, we have been able to achieve.

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.

We are using UiPath Platform to automate end-user testing for the QA team. We're not fully up and running yet, but we've been working on an end-to-end testing method with UiPath Platform that will take new hires, people that come in, we enter them in SAP, and then we can kick off testing for all the downstream applications to make sure that user makes it there and has all the proper information. It's nice to be able to have all of that in one place and have it automated to where we can just run one process and have it kick off all those different jobs to check the different applications.

The Orchestrator feature of UiPath Platform is really nice, being able to set up multiple robots and have Orchestrator control those, send jobs when they're available, and so on. It makes it really easy to have processes running. The biggest benefit is having one place where the different developers and users can go to look for how to do a specific thing or how something should be, the best use case for an activity or a type of process. It is helpful to have all that in one place.

The UiPath user community is helpful; there have been a few times where I've needed an answer for something and I found it on the forum or in the community section. Having other people working on similar things and sharing tips and techniques is always useful.

I'm not sure how UiPath Platform can be improved, as I don't have specific features that should be included in the next release.

I have been using UiPath Platform since October.

I haven't experienced any downtime, crashes, or performance issues with UiPath Platform, so I assess its stability and reliability positively.

For what we're doing with UiPath Platform, I think it scales fine; I'm not sure about the other team that's using it, as I think they're more end-user focused and we're testing, so I believe it scales well. I haven't heard any complaints from them. It's been fairly smooth for us to expand usage of UiPath Platform; we've added a couple of people to our team, and as for the finances team, I don't think they've had any issues with adding automation users.

The few times that we've had to reach out for customer service and technical support, we got a response within a few hours, so I think for a third-party vendor, it seemed in line with all of our others, which is good. I would rate our customer service and technical support an eight or nine on a scale from one to ten.

Positive

UiPath Platform had already been selected when I joined the QA team, so I don't know what other solutions were considered.

I think my experience with deploying UiPath Platform has gone well; there are aspects that are complicated to set up, such as getting the robots configured. Although that's more our environment, getting permissions and users set up and SQL coordinated, it's not really the platform itself, but it's been fairly easy to implement and it's not been onerous.

We have used UiPath Academy courses and we also had a web or a Zoom-based training program. I don't recall if that was with UiPath itself or a third-party vendor, but the learning courses are helpful.

I believe we have seen a return on investment with UiPath Platform; I can't really speak to hard numbers, but being able to automate our testing cuts down on our hours spent testing and helps us to do more with a smaller team.

I would rate UiPath Platform a nine out of ten.

I use UiPath to automate repetitive tasks within our organization. It helps us deploy processes without human intervention for some tasks.

UiPath has helped my organization, especially in the banking industry, by automating processes, reducing manual work, and saving costs. These improvements enhance process efficiency, reduce stress, and improve end-to-end efficiency.

The Studio is a valuable feature because it allows us to automate processes independently. It enables us to configure and manage everything through a web application called Orchestrator, which is particularly helpful for large organizations.

The documentation related to new releases needs improvement. It should provide a clear understanding of what was present in the old release, what's new, and how it affects users.

I have been using UiPath for around three years.

UiPath's stability is satisfactory. No product offers one hundred percent accuracy, but UiPath performs well overall.

The solution is very scalable. I would rate it eight out of ten for scalability.

Technical support comes primarily from engaging in UiPath's forum, where people share insights. I find the community engagement to be more helpful than direct product support.

Neutral

The initial setup was straightforward. Deployment doesn't take much time once the development and testing phases are completed.

The implementation of UiPath saves a significant amount of money and reduces manual errors, improving overall performance.

The pricing and licensing of UiPath are expensive. I rate it ten out of ten in terms of expense.

I recommend using this automation tool based on the specific needs of the industry or organization.

I'd rate the solution seven out of ten.

The use cases for UiPath depend on the specific requirements of each department within an organization. We typically meet with small groups of employees to identify potential automation opportunities within their departments. If a use case is suitable for automation, we develop the feature and build the bot for the customer.

UiPath integrates seamlessly with our existing products. Leveraging its AI capabilities, we're identifying new use cases. Additionally, UiPath offers a "bring your own model" approach, allowing us to utilize machine learning models from other vendors if needed.

UiPath enables end-to-end automation.

As a team of six developers, we rely heavily on the UiPath user community for answers to our questions.

UiPath helps us significantly reduce our on-premises footprint. It provides an automated touchless environment that we use in the administration and finance departments to automate a portion of our business processes.

We incorporate UiPath Academy courses into our developer training program to ensure they achieve specific certifications. For instance, all developers must obtain the professional UiPath certification. Each year, we prioritize which modules to target based on relevant use cases.

We use AI functionality in our automation. Communication mining and task mining are AI components of UiPath.

UiPath helps speed up and reduce the cost of digital transformation.

It helps reduce human error and frees  up our staff time to focus on other tasks.

UiPath has helped save us costs overall.

The biggest advantage of UiPath is its user-friendly environment. Unlike Azure and Blue Prism, UiPath offers a robust orchestration platform that allows central management of our entire RPA ecosystem from a single orchestrator. Additionally, UiPath excels in automating web applications.

UiPath provides a comprehensive suite of solutions for robotic process automation. Beyond the core UiPath Studio for building robots, they offer a range of AI-powered products such as communication mining, task mining, and the Automation Cloud. These solutions seamlessly integrate within a unified environment.

The pricing is high and has room for improvement.

I find UiPath's development environment to be challenging. Ideally, I'd prefer a more user-friendly approach like Blue Prism's, which utilizes a building block concept.

I have been using UiPath for 4 years.

I would rate the stability of UiPath 8  out of 10.

I would rate the scalability of UiPath 9 out of 10.

The technical support is good.

Positive

I have used Kofax but UiPath is far ahead of it.

The initial deployment is straightforward. Deploying bots using UiPath is easy.

We used external consultants.

UiPath is priced high.

I would rate UiPath 8 out of 10.

I recommend UiPath to others.

The use cases are quite broad.  UiPath is used in customer contact centers, supply chain management, operations, etc. It is useful for the intelligent automation of task-oriented processes.

It's easy to sell clients on a cloud-based solution like UiPath because it's the easiest to maintain and run. Some of the customers have already adopted a cloud-first strategy, so it's crucial for them not to have to operate their own data center. Others need to have a data center for privacy reasons. 

The solution helps customers reduce costs by about 20 percent. UiPath doesn't require any expensive or complex application upgrades. It has reduced human error. UiPath has improved outcomes like SLAs and customer satisfaction scores while reducing wasted time. 

UiPath frees up employee time, but the exact amount varies from client to client. It depends on your scope and your use case. You can obviously save time. It depends on how you design the process or whether you're automating one process or 10. 

I appreciate the stability of the UI automation, the studio, and the development environment. I also like the platform's rich capabilities. Stability and performance are always essential when automating through the user interface. This is what they definitely bring to the table. 

Regarding the ease of building automations, I would rate UiPath nine out of 10. It's the best tool in the marketplace. It's easy to build automations, and the interface is easy to use. I like how it integrates with the Orchestrator and everything works together. There are so many different use cases that we can easily connect through APIs, databases, and user interfaces to automate all kinds of applications. 

UiPath's end-to-end automation is critical. It's the most efficient way to automate. You automate mundane tasks so that people can focus on everything that requires expert skills or knowledge. 

The solution's user community is amazing. There's a lot of knowledge and experience, and it's easy to access that information. It's a highly active community. The UiPath Academy also has some attractive content that gives you hands-on experience with the product. The courses are easy to follow. 

I have been using UiPath for about three years. 

Excellent stability.

UiPath's scalability is excellent. 

I have had limited contact with UiPath support, which says something about the product. 

I have used Automation Anywhere and UiPath. I've looked at other options, but UiPath is at the high end.

Deploying UiPath is straightforward. It's fast. You can deploy UiPath in five minutes depending on what you need and how everything is configured up front. You need to get a platform account and set up the machines that will be part of the solution. You also need to set up users and assign them licenses. UiPath requires some maintenance based on the types of packages you're running. One person can do it. It isn't too complex. 

UiPath is relatively expensive. However, it's the leading product because it has so many capabilities. 

I rate UiPath 9 out of 10. When implementing, I recommend sketching out your costs over multiple use cases and comparing them to an alternative solution. 

There are multiple use cases. We have use cases for the ticketing system for assigning the ticket, resolving or maybe closing the ticket, and opening a new ticket. We also have a business use case related to insurance. I worked for an insurance client, and by using automation, we could create a policy that is used for testing purposes. If they had a new enhancement or an issue, they wanted to test whether it was working properly or not. They provided us with some raw data, and we tested that.

UiPath enables us to implement end-to-end automation. It is very important for us.

We use the AI functionality in our automation program. It helps us with decision-making. The AI functionality has enabled us to automate more processes overall.

UiPath speeds up digital transformation and reduces the cost of digital transformation.

UiPath definitely minimizes the operational expenses. By automating the static tasks that people are doing on a daily basis, there is a reduction.

UiPath reduces human errors. With static tasks, such as data entry, there are more chances of human error. With robots, there is less chance for error.

UiPath frees up employee time for other tasks. By automating static processes, we can save time and utilize it for other tasks.

UiPath definitely saves costs, but we cannot fully replace humans with robots. A human is required in certain cases. We can reduce at least 70% of manual tasks and for maybe 20% to 30% of tasks, we need human intervention.

The IDP feature is most valuable in UiPath because there are a lot of invoices and bills in every company. If they want to extract from a scanned document, it is very useful.

UiPath is very easy. We can build very complex processes within a few days.

UiPath has a very good community. If I am facing some issues, it is very easy to get the help of the community. They provide a solution very fast if I post an issue there.

UiPath Academy is good for learning purposes and certifications. They have beginner courses and advanced courses. By using them, it is easy to implement UiPath in a real-life project or process.

When it comes to decision-making, the robot will work based on what we feed it. It will not take any decision at runtime the way a human can. If they can put more intelligence in the robot for decision-making, it will definitely be beneficial for us. For example, if something is not working and it can dynamically decide at runtime what would be the next step, it will be beneficial.

Additional features such as chatbots and AI should be included in the UiPath itself. UI development is another thing. It could be improved for web development and app development.

I have more than six years of experience with UiPath. I have also worked with Automation Anywhere for a year, but I am more familiar with UiPath.

It is scalable. They have ML and also Python. They are adding a few more features.

We have around 1,000 people using UiPath. We have different groups in our company. We have separate teams. There are multiple different tools. UiPath is in one vertical. Automation Anywhere is in a separate vertical. 

Most of the time, if we raise a ticket, they help us to resolve the issue. I would rate their support a seven out of ten. The response time is as per the issue. Sometimes, it is very fast, and at other times, I have to wait for a day or two to get help from UiPath, so I have had both good and bad experiences with their support.

Neutral

I have worked with Automation Anywhere. I have also done scripting, but I had to write a lot of code to automate, whereas, with UiPath, it is simple. It is drag and drop.

It is deployed on-premises. There was no issue at all in deploying it.

For the deployment of bots, we have different VM servers. They are unattended ones. The deployment of bots is a very simple task. 

I can do the deployment myself. It is not a big task.

It saves six to seven hours for one person in a day. It saves the cost of one FTE, which is very high in US dollars. It is more than the cost of a robot. There are definitely savings. If the utilization is more, the savings would be more.

When I started with UiPath, there was a desktop model, and we did not have to purchase Orchestrator. Now, there is a bundle or package of Orchestrator with attended or unattended robots, so the cost is a little bit on the higher end. They are selling the Orchestrator model or the admin model. If someone wants to purchase the standalone or desktop model, they cannot do that, so the cost is on the higher side, but if we purchase more licenses, it gets reduced. If we purchase fewer licenses, it will be high.

If you have good use cases, I would advise using UiPath. Compared to other tools, UiPath is very easy to learn. A trial version of UiPath is easily available, whereas the trial version of Automation Anywhere and Blue Prism is not easily available. Automation Anywhere provides a trial version nowadays, but previously, it was very difficult to train people on that. That is the reason UiPath is the market leader at this time.

I would rate UiPath an eight out of ten.

I have worked on use cases for three domains, which include the banking, health care, and insurance domains, and designed bots for automating processes.

UiPath enables us to implement end-to-end automation. In my three years of experience, I have developed bots for banking, insurance, and healthcare domains.

UiPath is very easy to use. We are able to automate manual processes with bots, so the work gets done in a very short time. Manual work that takes months can be done in two or three weeks.

UiPath helps to speed up digital transformation. It is easy to use. It completely removes human intervention. We can develop unattended bots. It brings efficiency and also helps in reducing human headcount. After UiPath was launched in our organization, there was a reduction of 800 employees.

UiPath Studio and Orchestrator have been useful in designing the bots. I know about Document Understanding, but I am not working on integration services such as app integration. For building automation, a lot of activities are there. There is load taxonomy or taxonomy creation. After that, there is digitization, classification, and extraction. The validation part is also there. These are the steps for designing a bot using Document Understanding.

I have used UiPath Academy courses. I have done two courses. I did the UiPath Associate certification in 2021, and UiPath Advanced RPA Developer v1.0 certification in January 2023. I am currently preparing for the advanced UiARD certification. Through the UiPath Academy courses, I have learned a lot of things about queues, Orchestrator, advanced methods, etc. It is very good for learners.

On my organization laptop, while doing database activities, such as database connect activity, UiPath Studio hangs. We click on the screen, but there is no response. The only option that works at that time is to open the task manager and forcefully stop the services of UiPath. UiPath gets closed, and we again have to run UiPath Studio. 

UiPath Studio is also slow during web scraping and screen scraping.

In terms of new features, UiPath already has many features, but its pricing can be better for small businesses.

I have been working with UiPath since December 2020. It has been three years since I have been working as an RPA developer.

We are an organization with about 1,300 employees, and we have 20 people working with UiPath.

I have not used their support. When I have a problem in developing a bot, we use the UiPath community, and they provide me with a solution for the same.

I have also used Blue Prism. UiPath is easy to understand. It is easier to develop and deploy bots in UiPath. In Blue Prism, there are some challenges related to how to create processes. In UiPath, there are many sections such as Control Panel, activity properties, or object repository. They provide a modern experience to the developers. It is better than Blue Prism.

To deploy three projects, I had to install UiPath on the client's machine, and it took only one and a half days. 

We have two or three people for the deployment of projects. We have one person to deploy the code on a client machine. We also have a solution architect and a support team. The deployment requires only two or three days.

Small businesses do not have the budget to purchase the UiPath license. They should provide a cheaper license option for small businesses.

It is a very good solution. There are various RPA solutions, but UiPath is currently the number one solution in India as well as outside of India.

I would rate UiPath a ten out of ten. I love this tool. It works very efficiently.