UiPath Reviews

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

UiPath is stable.

UiPath is scalable. We are able to upgrade anything.

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

Positive

The initial deployment is straightforward.

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

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

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

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

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

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

Most of my use cases are spread across all the business units. It's used in accounts payable or for receiving reconciliations. It is also used in directory management and the banking finance sector. 

UiPath has a lot of features and they have added a lot of things. The apps and document understanding are good. We use document understanding a lot, even though they may not be common for day-to-day processes.

The Orchestrator is amazing. It provides a huge benefit including data security and data storage.

We can add a huge number of activities and can input code right into the platform.

While there might be companies that use the product to do automation for good cause, however, so far, in my experience, I have yet to do much of those use cases. I’m more on the business process side.

The product enables us to implement end-to-end automation. When they first launched, people used to have some sort of hiccups, however, now you don’t need different tools to manage your entire automation journey. With UiPath, from the discovery phase on, you have everything you need. We can understand the ROI clearly and can see what we’ve invested and what we’ve received.

The user community is valuable. It has the biggest community. Everyone knows it. One of the reasons UiPath is so successful is the UiPath community. We have tremendous people in the community supporting each other in terms of development or community events. People from different organizations can explain different pain point areas or explain good use cases and share learning and feedback.

We use both cloud and on-prem services. Most companies prefer on-prem over the cloud. From our perspective, we’re working to convert users to the cloud to reduce the footprint. Still, many want to maintain that on-prem segment.

We use the UiPath Academy courses. Since the beginning of my career, I’ve used it. Whenever there are new products that are launched, they will release certain courses for training purposes. I've gone through training at the Academy. I found a certified trainer also to provide training. Overall, having the training available really helps new people who want to kick-start their careers using the app.

They've also implemented community collaboration. If someone from the community has developed something, they will add training based on the community. The user has larger visual data now, compared to what happened previously.

The solution has allowed us to manage digital transformation and reduce the cost around it. Automation really helps boost digital transformation. We've seen cost reduction around resource use and the cost of operations as well. 

We've been able to reduce human error using UiPath. Of course, it depends on the people developing it. However, as long as the people have good implementation experience, we can really minimize errors.

It's helped free up employee time. However, it is not a major amount across every project. Comparatively, it can save a number of hours versus manual labor. 

We have saved money and that's calculated on the number of hours saved in terms of man hours. We haven't cut staff; they are now working on different tasks instead.  

We've used AI functionality. On a real-time basis, we haven't seen many benefits from the AI center. It's not cost-effective to run models on it as of now. We haven't been able to automate more processes. Some projects don't require AI at all. If it gets more cost-effective and has more use cases, that might change. 

The tool continuously redefines itself. They release three major versions every year and target one major feature once a year, like AI, et cetera. However, there are a few features at an early stage and not quite mature yet.

The initial tools are good enough compared to other vendors, however, they are still refining and need to change a lot of things, especially in the AI center, which is not that flexible when it comes to deployment. This is the same for UiPath apps. In most cases, nobody wants to invest a lot of money in attended bots. They need to work on that.

We'd like to see them work towards more stable outcomes to minimize hiccups. 

I've been using the solution for more than six years. I started in 2017.

Previously, we haven't noticed stability issues. In the past year, we have noted issues with stability. There have been some hiccups. 

The scalability depends on the way a company implements it. From a cloud perspective, the scalability is good. That said, the flexibility is there to scale.

We've had issues in the past where products were not working as expected and we've reached out to support. The experience has been mixed. Sometimes it is good. Sometimes solutions are delayed. 

Neutral

I did not use a different solution previously. However, I have used Automation Anywhere, Power Automate, recently, and also Intellibot and Blue Prism.

Power Automate is still quite young. There are still items missing as it's new. 

UiPath excels in the Orchestrator. The flexibility is great as well.

We've worked with both cloud and on-prem deployments. However, people seem to prefer on-prem. Almost all of our clients are maintaining their own cloud and then running UiPath into the cloud from on-prem.

I was involved with the deployment. The setup is straightforward. For the governance and audit security principles, we do need to add in a bit more. We might add, for example, a CI/CD pipeline. 

We tend to have three to five people, part of the support team, to help with the deployment.

There is some maintenance required. We need to monitor our VMs and understand if the robot is failing and if so what is the root cause. We have an interior support team for maintenance services.  

We did not use an outside vendor for the setup. Only people in the department are allowed to handle the deployments due to compliance. 

We cannot calculate an overall ROI. However, if something isn't getting 150% or more, people tend to not want to implement it. So far, we've seen a very good ROI. 

The costs have gone up recently. The pricing seems to be a bit higher for the end user. 

We are UiPath partners. 

I'd rate the solution seven out of ten. The most recent tools are not as impressive compared to what is happening in the market. 

As long as others don't need additional tools like Apps or document understanding, I'd recommend it. There are a lot of features and functionality to try. However, if you need document understanding and apps, I'd advise users to look at their use case, do a POC, and figure out if it's a perfect fit. 

From the perspective of pure automation, UiPath is excellent. However, if a company is looking for AI functionality, they really need to see what else is out there and what is best for them. 

For a current client, we have around 22 to 25 use cases, and it's all based on the financial side of things. The client is in finance, and we have use cases all of which are comprised of different tools, including SAP and their in-house CRMs. It's about automating the process where we take some data from the CRM tool and upload it to SAP. It also involves uploading the files to the FTP server. 

For example, one use case is where the applications used are Oracle, and SAP, and STP. We just download the data from Oracle. There are different files that we download from Oracle and upload to the FTP server. From that FTP server, there is a different team that takes those files and creates a Tableau dashboard. 

UiPath Studio helped us automate many processes that have helped us save money. Even though the tool price is there and the license costs are there, it has given good ROI. For example, automating a process can reduce the work to half or maybe 60%. We divert efforts to different work. Therefore, it has been pretty useful in terms of savings and quality control.

For example, one client had a focus on quality control. There are instances where employees make some minor errors that could lead to major losses to the organization from the department's point of view. We automated that process and it gave us more return in terms of quality control. Fewer errors ultimately were made which saved the company from losses.

UiPath has a full suite of capabilities. It has, for example, an end-to-end automation suite. From a development point of view, it is pretty helpful to have access to all of the activities on offer that anyone can understand. 

The Studio as well as the process mining are great. Document understanding is another useful feature. It has eliminated the business analyst side where you have to go through each department and find out which processes are there, and take a different tool to get those all processes in one place and create a process workflow. All of this can be done with process mining. 

With document understanding, we have the capabilities of having UiPath understand and create documents, which previously was quite a lengthy endeavor. You just have to install it and follow the steps. It will automatically take a screenshot and create a document for you and then create a brief description of it. 

It’s easy to build automation using UiPath Studio. From a developer's point of view, it is easy due to the fact that you don't need much of a coding language or coding background. You just should have a clear logic behind it. If you're clear with the logic, a layman can handle the task. They do have Studio X features, which is for the layman who doesn't have any background, who doesn't have any coding or developer's background. They can automate their own work. Even an SME who doesn't know anything about automation could automate small tasks.

It’s great that we can scale automation without having to pay attention to infrastructure. That is very important actually. For example, scaling automation plus giving attention to the infrastructure can be a little hectic and time-consuming. If there is any way where we could reduce this work or optimize it, it would be great from the implementation point of view.

UiPath enables us to implement end-to-end automation. Right from the start, you have document understanding and process mining as well as the Orchestrator, which helps you with getting an overall view of the bots in our organization.

End-to-end coverage is the most important thing, due to the fact that, if it is end-to-end, we don't need to go to the market and look for any other application. If you can get end-to-end, you don't need to go for other products which simplifies everything. It's easy for us to maintain and work with it instead of having to integrate and manage multiple systems, multiple products, and multiple applications.

UiPath has helped minimize our on-premise footprint. It has helped us with quality control savings. We have saved many efforts previously requiring full-time employees. It’s one of the most important factors when we work for clients. If a client is hiring us to automate many processes, there are different intentions of doing it. If we are able to help them reduce cost, reduce and do some quality control, it is important for them. For example, previously, if work required ten employees, we have been able to reduce that down to six or sometimes four personnel maybe.

The UiPath Studio has reduced human error. It has helped us with quality control very often. In the past, mistakes have cost us. It has saved costs as well as saving us money related to fines or penalties.

The solution has freed up employee time. Instead of doing the same mundane work every day, we have just automated that part and now the employees have more free time to do more meaningful work. In terms of hours, from a department's point of view, we have saved around half, that is four hours per day, maybe about 80 hours per month. The additional time enabled employees to focus on more important work.

We have found that the product has reduced the costs of our client’s automation operations. With my previous client, we calculated an average of 40% in reduction of personnel and 40% in cost savings. UiPath has saved us money across the organization. The average saving is likely around 40% to 45%.

I'm pretty much happy with all of those tools. I don't have anything in mind that I could see improvement.

While UiPath Studio helps speed up the cost of digital transformation, in a way, it requires expensive or complex application upgrades or IT support, as it needs an entire setup. That setup requires support from different departments, and that comes with a cost.

I came across one problem while upgrading. We were upgrading from the 2019 version to the 2020. There was one thing that was not mentioned either on the website or documentation, and we had to take support from UiPath. The documentation needs to contain each of the scenarios which could occur while upgrading the solutions. As it is now, this is not the case. That said, when we ran into issues, UiPath Support helped us through it.

I've been using UiPath for five years now.

We've had outages once or twice. For that, they have a workaround. If a server goes down, we should have a backup server for it. If that's the case, it is just a few steps needed to migrate or we can take the setup from another server. That's it. It's pretty good in general. 

The scalability is fine. For example, if the bot count is about zero to 100, we have the capacity. And if it goes beyond that, then we have to increase the features of the systems and servers. It could take time if we scale beyond the limits, however, it's still possible. It just requires an upgrade. 

What's required is managing all the infrastructure and getting all the permissions from the client which is what could take time. Scalability can be an issue when it goes beyond the mentioned limit.

In the current organization we're working with, it's totally unattended bots where no user is actually using this tool. That said, the bots are in production, which works 24/7. No user is having this access to the tool. It is all unattended bots.

In the previous organization, there were 58 to 70 users as we had attended bots. They were using bots in their daily routine.

It's a routine for us to use this product every day and deploy this solution. We are definitely looking at increasing it and scaling. We have a lot of work in the pipeline.

I've contacted technical support many times and they are very helpful. Based on the severity and priority, they do help us on priority and they are very helpful in terms of responding, supporting, and maintaining. If they can't help us by email, even after giving clear instructions, they'll bump you to a different level and help. It can be just like spoon-feeding us. They are very patient and try to be very clear.

We were doing automation, however, it was just .com and .net. We used to write five lines of code just to click on one button, which is just an activity right now we have in UiPath. We switched to UiPath to do end-to-end processes which would require large amounts of code if we kept doing what we were doing.  

I've implemented UiPath from scratch many times. 

The process is quite straightforward. You just have to have the installer and just click install, and then after a few steps, it is done.

Setting up just UiPath Studio hardly takes ten to 20 minutes or maybe one hour if you're facing some complexity. Setting up an Orchestrator with all the robots could take a while.

Our implementation strategy is based on whatever the customer's requirements are. Different clients have different requirements. My previous client, for example, didn't want the cloud as they were pretty concerned about the security as they deal with financial data and they don't want the data to go to the cloud at all.

Clients have the option of on-premises or cloud. Based on that, we just go with the requirements. Some clients want attended bots due to the cost, and some want unattended bots due to the features. 

In terms of maintenance and deployment, how many people you need depends on how many processes you have with the client. Right now, with the current client, we have 22 to 25 processes that we have automated. We are just three users who are developing, testing, maintaining, and supporting this project. However, it varies and often depends on the process and client and how many bots.

For maintenance and support, you don't need many people. For development, if they're at 10 people, five or four could do the work in terms of support and maintenance.

We handle the deployments for our clients. 

While the clients might have released some reports, I don't have much knowledge about ROI. 

I do know about the prices of attended and unattended bots as well as Orchestrator. 

There are costs related to Orchestrator, Studio, and attended bots. There are also infrastructure costs, and, while implementing this tool in any organization, there are different costs attached to it.

The price for the attended bot is between $1,800 and $3,000. The unattended bot was $8,000 last year.

Orchestrator is around $20,000.

We looked at Automation Anywhere and Blue Prism, however, about five years back, where UiPath, Blue Prism, and Automation Anywhere were the leaders in the market, at that time, just UiPath had the free training and Intuit training for their tool. The other tools didn't have any training, or if they had, it was paid. That's why we chose UiPath, which ended up being the best out of the three anyway.

The company I work for is a UiPath partner.

There have been multiple companies that I've been working with. Two remain the same. I've been using different tools as well. It's been on and off with UiPath.

We are not using the latest version of UiPath. The latest version is 2021. We are using 2020. This is due to the fact that the client that I'm working with has a stated policy as to using a minus one version. They believe it could not be a more stable version for any product. 

At this time, we don't use the SaaS solution or the AI functionality. However, I have enrolled in AI training to better understand it. We do not yet use the automation cloud or UiPath apps either.

In terms of employee satisfaction, from the experience I had from interacting with the client and different users, they are happy as well as sad. They are happy in terms of moving away from the mundane work that has been taken off from their hands. They are, however, both sad and afraid that they could lose their job.

I'd advise users, if they're a layman, to go with the training. Just start with the training from the UiPath website itself, in the RPA Academy. That is sufficient for anyone to start with. They have all the courses that start right from scratch for every role, be it business analyst, solution or product developer, et cetera. In six months, even starting from scratch, you can excel on this product.

With UiPath, it really is possible to optimize so many things. 

I'd rate the solution at an eight out of ten.

We managed over 500 global tasks worldwide, leveraging UiPath to automate procurement, financial accounting, customer service processes, and customer relations.

We evaluate resumes through the RPA and ChatGPT four. We also arrange service for customers who need repairs to their devices through automation we developed using UiPath.

UiPath enables end-to-end automation. The end-to-end automation is important because it allows us to reduce our testing and reporting time from 28 hours down to 15.

UiPath has helped us shorten the time for our supply chain and revenue report generation. By using UiPath Document Understanding the OCR can read the PDF documents and automatically drop the file into the ERP system significantly reducing our time.

UiPath has streamlined our operations by digitizing our documentation and converting it to easily accessible PDF files. This has significantly reduced our physical footprint, eliminating the need for paper storage and manual document handling.

As a partner of UiPath in our region we are required to take all the Academy courses so we can better service our clients and share our use cases.

We have 1,000 clients around the world, each with unique invoice formatting preferences. Our AI system efficiently sorts these invoices based on their specific formats. By automating more processes through AI, we've significantly improved efficiency. For example, while standard OCR takes a minute to process a PDF invoice, our AI system does it in just two seconds.

UiPath has helped speed up our digital transformation. We have created a large data lake to help with analytics.

We require human verification for the final invoice numbers. Using UiPath the number of human errors has been reduced to one percent.

UiPath has saved ten percent of our employees' time by automating the invoicing process, translating the invoice language, and emailing it to the original user.

UiPath helps save costs. We can keep the license costs down by using one API license to convert all our PDF files into Word.

UiPath is well-suited for automating tasks within Oracle applications and can be deployed on-premises or in the cloud. This flexibility is particularly advantageous when dealing with sensitive data that cannot be migrated to the cloud for security reasons.

UiPath needs to improve its integration with Microsoft products such as Office, SharePoint, and PowerPoint.

I have been using UiPath for two years.

UiPath is stable.

UiPath can scale to our needs.

The technical support is good. We rarely have to use them.

Positive

For general automation needs, we choose Microsoft Power Automate due to its cost-effectiveness compared to UiPath. However, for Oracle-centric automation, where stability is paramount, we rely on UiPath.

The initial deployment was complex. Many settings within the orchestrator need to be set before running a job. Once we implemented UiPath we had our user team keep an eye on it for one month to ensure it was stable, scheduling only attendee jobs before moving onto more complex automation.

In our region, we have a team of 15 to 25 people for the deployments and a smaller team of five in North America.

We implement UiPath in-house.

UiPath is expensive compared to the competition. We pay a license fee that is over 20,000 USD.

We evaluated Automation Anywhere, Power Automate, and UiPath. Automation Anywhere and UiPath are more expensive than Power Automate.

I would rate UiPath a nine out of ten.

We do require the assistance of IT to help increase our digital transformation.

Maintenance is required when updates are made to a process or component. Our team of 25 is responsible for the maintenance as well.

We use the solution for robotic process automation. We use it across the value chain for our business. We've used it in accounts, including cash management, and in HR for management tasks and IT for password resetting. 

The automation has been quite useful. It's been helpful in our journey towards transformation. 

I've used this solution for a while and I utilize the whole tool and get a lot of benefits out of it. 

It helps save time. We've had efforts that would take more than four hours a day, yet, when done through UiPath, it takes less than a minute.

The useability is very good - even for non-technical people. I'm an accountant by education and now I'm also an automation expert by profession. Its interface is user-friendly to those of us who are non-technical.

Anyone who wants to automate any task that is rule-based and repetitive can do it through UiPath.   

We can use the solution for automation emails or notifications.

It enables end-to-end automation. We developed a use case where people from different business units have large amounts of data, Excel files, we've made it so that we can combine it and enter it into the ERP system. Everything can be checked via the rule book and can create the report and send back the information to the customer. It simplifies the data and organizes and compiles it for them. Users have gotten the benefit of five FTEs by using UiPath. It saved many man-hours. 

I haven't used the UiPath Community too much. I often Google questions to find answers. It is a good place to go for development work, though. 

It reduces our footprint. We historically did have many items on-prem. I like it on-prem and on the desktop.

It can reduce the cost of digital transformation. Where processes can have faster response times, UiPath helps with efficiency. However, if the response time of the application is slow, and we need to provide workarounds, it isn't helpful in that it hasn't efficiently helped us save time.

UiPath reduces human error by 100%. Whatever you give to the robot, it will do it correctly. That said, it needs to be programmed correctly - if it's programmed wrong, it will do it 100% wrong. If it's programmed right, it does it 100% right. 

It's freed up human time. It's not well-utilized in that sense. It should be available to everyone so that they can find ways to save time by creating their own automation according to what they need.

There are a few shortcomings. For example, even in their latest version, there are still older features even though they've introduced new ones in parallel. They should do something where they update the solution and then close off the older version after a year or something like that. That might help with standardization. 

Sometimes it is very useful for automation. However, sometimes it is really, really frustrating when it is unable to manage the more dynamic items. When an element is stable, it's great. When it comes to changes to IDs or the dynamics of the website, it lets us down in front of our customers. It needs to be better at handling volumes of data. 

Automation on the cloud has had issues. It can be slower. 

The Academy classes could be improved. There should be a portal for use cases. There should be more business examples.

They should offer different licensing tiers, especially for daily individual users. 

I've been using the solution since 2016, more than five years. 

It is a stable product. There were some issues while interacting with different applications. For example, with Microsoft, we have issues with One Drive. When UiPath is working on a file, it cannot quickly get to the file. We need to move the file to a local drive before processing the data. Microsoft applications seem to give it trouble. 

We have multinational business units. Company-wide, maybe 500 people are using it. Where I am, there may be a team of ten people working with it and 50 to 60 automations. The solution is in multiple locations and departments. 

The solution is scalable. It depends on how an organization wants to utilize it. 

Technical support is very flexible, however, they do not respond quickly. Sometimes they just tell us "this is how it works" and we have to try to explain our framework.

Neutral

I have also tried Blue Prism. I didn't work with it much; I just studied it theoretically. 

I also tried to work with Power Automate. Initially, it wasn't very good, however, later, it began to echo the style and functionality of UiPath.

UiPath is easy to use and easy to get started with. 

The deployment was a long journey. I was one of the first people in Pakistan to use it. Now, once you get a license, you can deploy it in two weeks. However, it depends on the complexity of the processes in terms of deploying automation.

We have around ten people maintaining the solution. It requires a lot of maintenance. If anything needs to be changed in the target application, it needs to be incorporated into the robot. 

Someone told us you do need three to five years before you get an ROI. However, in our first year, we were able to save more than 8,000 hours. 

The solution is on the expensive side. 

There should be standardized packages. If an organization already has a license with UiPath, UiPath should offer special licenses to each employee so that each employee has their own UiPath automation capabilities for each of their individual tasks.

There should be regional packages and costs. Different regions cannot necessarily afford UiPath. What is affordable in Europe may not be affordable somewhere else. 

We're a UiPath customer. We serve internal customers with robots.

We do not use the UiPath AI functionality, however, we are on a journey towards building our own internal solution. 

I'd like to see UiPath cut the cost of their license. For end-to-end automation, for developers, I understand why it needs to be expensive, however, for day-to-day users, it should be cheap. 

I'd recommend the solution to new users. 

I'd rate the solution eight out of ten. It's still the best out of all related products.

We are an auditing firm who has a certain level of tasks that are open for automating. These are complete steps, which can be performed by anyone, standardized, and do not involve any human intelligence. These are just basic human tasks. It is a long process, where in-between there are certain validation and verification steps as well as certain steps that involve a lot of documentation to go through. The organization is targeting all these tasks, which are completely static and can be automated, so they can get rid of them. Then, employees can work on something more useful as well as more productivity-oriented tasks.

Currently, I am dealing with our internal COE, providing RPA solutions to internal and external clients. UiPath is a driving force in our COE.

It is on-prem. There are a couple of discussions going around upgrading UiPath because there has been so much advancement with the solution.

Document Understanding was a game-changer. One of our clients has manual billing that needs to be processed. With the help of Document Understanding and UiPath Action Center, we created an excellent workflow for our client. It also gives us better accuracy. Now, there are hardly any exceptions in the client's billing documents that are being processed.

In my previous role, I presented some clients the end-to-end installation design of UiPath, e.g., building a PDD using Task Capture, going to UiPath Studio to build the actual solution, and then later going to post-production Insights. 

UiPath has helped to minimize our on-prem footprint. Most organizations prefer on-prem because it reduces the risk of compliance issues.

Attended robots have been very beneficial for our users. UiPath saves one robot for every user. We have a couple of clients who are using attended automation for their day-to-day tasks.

From an organizational point of view, the most used feature is Orchestrator because that is how we manage more than 100 users. When there are more than 100 users, it is important, and probably better, to have some place to manage them. Orchestrator is doing that for us very well. 

The most exciting new feature is UiPath Apps. I have explored it in-depth to get a better understanding. I think this product will be a game-changer for my organization as well as for my clients. It will revolutionize the way that we are providing licensing and proper access to a user. It also revolutionizes the way people are using it. Everything will be on the cloud, which I think is the most interesting feature of UiPath Apps.

UiPath Apps will definitely help to reduce the workload of our IT department by enabling end users to create apps. If you are creating an app and sharing it over the cloud, that removes the dependency of having UiPath installed with the correct version as well as Internet connectivity. Or, you might have a global server in the background that is not functioning very well. There are multiple issues related to connectivity of the UiPath robot when deploying it on a user's machine. 

If you are giving access to a group of users and adding Azure container or any other container provided by UiPath, then this reduces 10 to 15 hours of work from the IT or support guys who are manually doing all these things by themselves. Not every user must have the new step of getting the UiPath license and software installed, it is really static. You are eliminating that task completely by having UiPath Apps on the cloud. This is definitely convenient for users to use.

We are not using UiPath Apps in my current organization. About two to three months ago, I created UiPath when I was at TCS. It was there that we demonstrated the power of UiPath Apps versus normal, conventional methods. It reduced our work through scalability. It helped us to easily scale and was more convenient, because giving new or temporary access can be a pain. 

It is very easy to share UiPath Apps. When you want to start or remove it, you can do it with a simple click within the cloud. It is not that complicated. Also, the usage is better in UiPath Apps compared to the conventional UiPath robot. In UiPath Assistant, you can access the portal and simply run it over there. Therefore, you will not have a problem with the background functioning of the UiPath robot or even connectivity issues. Scalability and ease of use are favorable for users when they are using UiPath Apps.

Recently, I have been exploring Automation Hub. Its idea to pipeline a feature will be very useful for our guys managing RPA products on a large scale. 

When it comes to debugging, there is some improvement needed for UiPath compared to other RPA tools. There are features to edit the workflow or content of the automation file while we are debugging. For example, we have 10,000 lines of code that we have integrated by 10 different users. So, there is one integrated code and you are debugging it. After some time, you might find a line which is not an error. You may have forgotten to remove it or change the value to your desired criteria. It is really a pain to stop the entire debug session and just edit it, then start again at zero. It will do the same steps again just to reach that level or step where you were actually stuck previously. Whereas, in different automation tools, whether you are on the findings step or in-between a debug session, you can actually edit that information. This is good because sometimes the developer also forgets to add or remove certain values in-between a long code. I think this should be improved in UiPath. This should already be in consideration because I have been in touch with UiPath a couple of times because of this.

My current company is currently looking at the end-to-end solution. However, Insights and Task Capture are major concerns. Task Capture will give you a skeleton of the PDD, then you have to edit it. The skeleton is only there for simple automation, and we have complex scenarios. It is so complicated that the PDD generation using Task Capture will not give you even 20% of the output. While Task Capture is something promising, people are looking at it with greater expectations than it provides. People are not using Task Capture or Insight because of their limitations. These features could use improvements and enhancements.

I have been using UiPath for three years. I recently switched companies. I worked with Capgemini and TCS prior to this company, where I was in their COEs and providing solutions to clients. This is the first time that I have been on a project for PwC. Since the start of 2018, I have worked mainly in COEs and have interacted with around 30 clients up until now.

PwC, as a firm, has been using this technology for four to five years.

I have been using UiPath on a different powerful system that has high-end RAM. Sometimes, it crashes due to the use of multiple components at once. For example, when I was using Druid with data service and another UiPath product. Developing was quite easy. However, when debugging, sometimes it would freeze. I don't know whether it was because of my system and its compatibility, my system's configuration, or the fact that we were using so many high-end tools and products at once. 

The robustness of the tool, when it comes to using high-end products, is something that I am currently exploring. This is something that is currently a bit of concern for other developers as well. I have been interacting with a lot of developers around the globe. As a part of that, I tend to share my experiences. They have shared that it will sometimes freeze, even with simple automation. Because we are using new features or products all at once, it freezes. I think this should not be the case. If you are using long, heavy code, and it gets frozen at one point, I can understand that. However, 10 simple lines of code, while using three or four products at once, is getting frozen. That should be taken care of or improved.

To troubleshoot the system crashing, we contacted UiPath. They were kind enough to reply and have a discussion. They are working on this and trying to make it more convenient so future releases will solve this problem.

As a part of a COE, we get clients who expect us to present the entire proof of concept as well as a PPT or presentation. For example, why they need to go with UiPath, what are the advantages/disadvantages, if any, and why we should not go with another tool or solution as a whole, not just RPA. The main point for us when presenting UiPath is the ease of usability and scalability. We don't need major infrastructure changes, just two or three URLs to be widely fitted. Then, they need to decide if they want unattended or attended robots. The scalability is the major driving force which excites our clients and us, because there isn't a need to have media-heavy software or heavy processes changes.

Clients don't want every user in their organization who joins to have a long process to get through the start up. Automation Cloud is something they were very much interested in exploring because of the scalability. They find it very easy to use and scale, because not all the clients have a certain set of users using robots. 

I have seen user usage explode from zero to a bigger audience of 22 users.

UiPath is used extensively in my current organization on a large scale. There is also a plan to scale it to more users.

PwC has their internal teams providing a "help center" sort of infrastructure to them. If there was a need for any help, or some basic doubt, it is solved internally. PwC's internal help center exists already. However, for major issues, we reach out to UiPath, as a customer, so that we can receive a response and clarity on issues.

The technical support is really great. I have been in touch with all sorts of UiPath support because I was in the COE and our clients were completely global until my latest assignment. I think UiPath India, France, Belgium, and Canada are timely. They provide a very precise support experience. They were kind enough to let us know the actual reason, because just saying that it is a bug is not something that we can comfortably accept or digest. Also, they have been kind enough to follow back up on updates and bugs that we have reported.

As a whole, I have reported more than 25 bugs across all their products. They were kind enough to reach out to the same forum where we raised the ticket. They were kind enough to reply that these are the updates that they will roll out in the next version. It is good to have this interaction as well as a heads-up regarding your bug reports. I think the technical support is on the mark and doing their job really well.

The learning tools and support are really great. They have the most engaging forum across the globe, compared to other RPA tools. The learning and engagement are really up to the mark. That also brings confidence to our clients and us. We are a part of their global community forum, which is a benefit for us. 

Their marketplace has grown tenfold in the last year. It is because of the developer's involvement as well as involvement from people in the community. UiPath is creating their own statements and usable components, which adds value to our presentation. The tool is growing, and developers and community members are growing with them. 

My previous companies migrated from other RPA solutions, like Automation Anywhere, Blue Prism, and NICE Robotic Automation, to UiPath because of the value of its features and the quality of the overall solution. I migrated my clients from those companies so they could have a better ROI and reduce the cost of maintenance. We also migrated from scheduling tools, like AutoSys, to provide better accuracy and ease of use.

My current company was not previously using an RPA solution.

The initial setup and implementation are standard, simple, and user-friendly. UiPath just requires basic adjustment, then it is plug and play. It is very easy for everyone to understand, e.g., non-technical clients can understand what has been changed.

If the deployment is done properly, you will see better data accuracy with UiPath than manual entry. If the deployment is done by someone without much experience, it will affect the quality of the solution due to bad coding. You can't just leave it to the tool.

Using Automation Cloud makes it easier to deploy.

It takes almost two weeks for us to implement from scratch because we must understand the client's infrastructure, create a solution design, and then present it to them.

We present our clients with a PoC, including a document that justifies the work and costs. We also give them a standard robot that we created for demo purposes. This way, they can visualize how it will be implemented and mapped in their organization.

For deployment, one or two people are sufficient: one from an infrastructure background and another from a technical background. Sometimes, it is complex or hard to understand the client's needs when it comes to the deployment of Azure, Nvidia, or AWS servers on their VPN connection.

The amount of staff needed for maintenance depends on the size of the solution, e.g., the bigger solutions will need more people. However, the maintenance and support activities can also be automated and that reduces the need for support and maintenance. Three or four support team members are enough with the help of a robot.

The last ROI calculation that we did for a client showed that they saved 25% of their time by automating a manual task with an unattended robot for a single machine.

Overall, the cost remains the same to the client and us, when using Automation Cloud, because of the amount of money spent on the cloud migration and cloud usage.

At my previous company, in the best scenario, we removed almost 200 hours per month of client usage, making it automated with almost zero errors. So, about 32 employees were freed up from their work per month, and now there are only two. This has enabled employees to focus on higher-value work that involves human-base interaction. This saved the client money and provided a recruitment benefit.

UiPath has been useful for improving employee satisfaction. Employees are now spending time on more value-add work instead of something static, whether it is boring or hectic, that they have been working on for ages. This gives employees a sense of advancement.

I would rate the pricing as seven out of 10, where 10 is the most expensive. The pricing increased with the latest release. It used to be cheap. Now, it is expensive. However, it does come with supported features, which almost justify its cost.

Building automations is very easy. I have used multiple RPA tools. Developing automation with UiPath is very convenient compared to other tools. 

Development is very easy. I have been exploring certain markets based on the marketplace component and its native integrations with ServicesNow for the chatbot. I think development is where UiPath stands out as a winner compared to other tools because starting to automate is very easy.

Compared to other RPA tools, UiPath is leading with new feature additions every quarter. Obviously, all the new features will not be incorporated into the solution or be helpful for the client. We see the organization putting in efforts to grow at a rapid pace, including ML, scaling, and everything on the cloud, like data servers. UiPath gives us the confidence to present a tool that can be relied on because it is constantly growing. It constantly has certain new features added which can be beneficial.

With UiPath, not everyone needs to understand the code, which is great. This makes it superior over other tools because it is easy to understand. This contributes to profits because clients prefer UiPath over something else because they have more confidence using it.

Blue Prism has the ability to edit in the middle of a debug. As far as I have explored, Blue Prism is leading on the debugging front and stands out against UiPath. Debugging in Blue Prism gives users a lot of usability to edit the workflow. This makes it easier for developers to run things once and get things done. Otherwise, debugging multiple times can sometimes be a pain.

People migrate to NICE Robotic Automation because they were having difficulty maintaining their software with a limited number of staff. 

It is easier to become more proficient with UiPath than other RPA tools, especially Blue Prism. Training can be done at almost no cost.

I would suggest automating a policy that is not a requirement and follows a process. As an RPA user, it is your responsibility to get things done in an efficient way. If a user is doing A, B, C, D, it might not be required that the robot do the same thing. There might be a shorthand that can take you from A to D directly using the robot. For example, it can go directly to a page and not have to click 10 things like a human.

If you use it properly and consciously, it can increase accuracy and reduce error. If you don't, then it will be the other way around.

As features are concerned, it is reasonably priced compared to any other heavyweight tools in the market.

It is beneficial that there is a SaaS option because this offers a diversified cloud environment. If we expand and explore more cloud options, then having a SaaS solution for UiPath will be beneficial for us. Right now, SaaS comes with a certain amount of compliance issues for my company. 

UiPath AI Center is very useful. I think it is a game-changer when it comes to better usage. However, I haven't had much of a chance to explore it on an enterprise level. Not many clients are using it because of the exposure risk. Once a lot of developers start exploring and developing on it, then more companies will have the confidence to say, "Yes, we can push to that," which will increase the usage of UiPath AI Center.

Everything on the UIPath Cloud is a template. It is just a starting point. You have to dig into it and do more exploration to make it better.

Using Automation Cloud would be very beneficial for us, as a COE, because we are getting rid of the mundane tasks of infrastructure, maintenance, and upgrades, which we do not think are our primary job.

Biggest lesson learnt: UiPath has the fastest growing community with the quickest learning tools. It is easy to automate. It requires basic understanding and effort to get started. 

I would rate UiPath as 9.5 out of 10. I have concerns about the debugging capability, where if I need to edit something while debugging, I can't do it right away without stopping the process.

We have many use cases. We have used it in finance, HR, IT, business supply chain, insurance, etc.

It is easy to build automation using UiPath. UiPath definitely provides a lot of value to the organization. There is efficiency and effectiveness.

UiPath has helped to minimize our on-prem footprint. It is very important for us.

The AI functionality has given us a lot of flexibility to go to the management and tell them that we can enhance things. Some of the things that they initially thought could not be automated can now be automated.

The AI functionality has enabled us to automate more processes, but it is not an easy process to understand and implement automation. It is relatively new, and it requires a lot of change management.

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

UiPath has reduced human error. There is an 80% reduction. UiPath has also freed up employee time by 80%. 

UiPath has saved costs for our organization by 30%.

The cloud feature is valuable. Automation Hub and AI fabric are also good features.

UiPath Community is good. They answer all the queries.

Their support should be improved. 

Any unnecessary features should be removed. Only the relevant features should be there. There are so many unnecessary features that are not used by the organization. They are offering too many things such as process mining, task mining, communication mining, intelligent documentation, etc. It should be a specialized solution. It should not do everything in this world because the value comes down.

I have been using UiPath for six years.

It is stable. I would rate it an eight out of ten for stability.

It is scalable. I would rate it an eight out of ten for scalability. 

It is being used at multiple locations.

Their support is very poor. It is not timely. They sometimes take a lot of time to find resolution.

We do not use UiPath Academy. UiPath Academy courses are good, but nobody on the team is doing the courses through UiPath Academy.

Neutral

I have also worked with Automation Anywhere and Blue Prism. All these tools are good. IQ Bot from Automation Anywhere is very good. It has better features than UiPath, but UiPath is marketed well.

I was involved in its deployment. It is a straightforward process. It took us three months.

It does require maintenance. We have five people for deployment and maintenance.

We have consultants.

We have seen an ROI. It took us five years to see an ROI.

UiPath is expensive.

It is a great tool, and I can help people to implement it.

I would rate UiPath an eight out of ten.

We needed a solution for users that had too many manual tasks. We're in a large bank, and there are tasks like account opening or other items that can be automated using the UiPath system. It can handle auditing as well. 

We've been able to increase productivity time by using UiPath. It saves time and costs. 

Previously we used the classic activity. UiPath modified the activity and it made it easier to do the development and create accurate products for the customers.

It's easy to build automation using UiPath. There are a lot of ways to make an automation, compared to other tools, like Automation Anywhere and Power Automate. It's very flexible. We can use different codes and use Excel modifications. It's very comfortable to use. 

In UiPath, we've developed a developer foundation and developer processes. If there are modifications to what has been done or ideas for new ways to do something, we embrace that. 

We can implement end-to-end automation. It's important for us. We do need to study the process and then create a process that is a better solution. Our users can study the whole process and come up with solutions and best practices for building automation. The best way to do it is to have one person handle the end-to-end automation so that there is no confusion in the process.

The UiPath Community is helpful for users. It's an advantage. It helps share knowledge. We're able to find the best solutions for issues with it. 

We've used the UiPath Academy courses. It helps users to study UiPath: what it is, how to use it, and how to build solutions effectively. It's great for users who want to study and be more confident in the development process. 

It has helped us reduce the cost of digital transformation. When we have more people, we need to pay more salary, and it takes more time. Using UiPath, we can save valuable time and reduce costs. What a man can do in one hour, UiPath can usually do the same task in half the time. 

It reduces human error. Sometimes people aren't in the right mindset. If they are tired, for example, they can make mistakes. However, a bot always does everything the same way. 

I'd like to see the accuracy improved. Sometimes the development works fine. Other times, it requires some small changes in the development. 

They could add enhancements in AI technology that could be helpful for everyday developers. 

I've used the solution for three years. 

The solution is stable for the most part. I'd rate it eight out of ten. Most of the time, it's working fine. However, sometimes we have small problems with the data connection or pushing data. It can be difficult to identify the orchestrated things. 

We have about ten people on our team servicing clients with UiPath bots. There are three senior developers. We have bots across multiple locations. 

I'm unsure if the solution scales well. 

We sometimes have to ask a lot of questions as the accuracy can be missing. When they provide us with a solution, there are options between classic and modern. It might take a while to fix things or if there are issues again and again the customers can sometimes be disappointed. 

Neutral

I've used Microsoft, Automation Anywhere, and Blue Prism. I'm most comfortable with UiPath and Power Automate.

Power Automate is developing a lot of its own solutions right now for Microsoft. I find UiPath more advanced than Power Automate and Automation Anywhere, which don't have as many features. Power Automate is the most comparable to UiPath. 

The main disadvantage to UiPath is the cost, which is really high. 

When we do the deployment, we have to take into account security, et cetera. It concerns us when we're talking about using the cloud. There may be particular processes we cannot do on the cloud. 

One good developer is all you need for maintenance. If you have to update the system or do a modification, we need to update UiPath. So there is maintenance required and a person does need to watch the process. We provide the maintenance.

Currently, our vendors are doing the installation. After it's installed, we provide all of the bots and processes. 

I don't have any metrics in relation to ROI. 

The licensing is very expensive for UiPath. Many clients are going with Power Automate or Automation Anywhere based on the high cost of UiPath. 

We're an end-user of UiPath. 

Currently, we aren't using AI technology in our solution. However, I like the idea of it. We'd maybe be able to resolve redundancies with it in the future. It may be on our roadmap in the future. 

I'd recommend UiPath. It's very accessible. I use a lot of products and this is the best product to give to customers overall. 

I would rate the solution nine out of ten.