UiPath Platform Reviews

We use it to transfer information from one system to a government system.

We also use UiPath to automate processes that track mileage on vehicles, which would then allow us to calculate some of the GHG emissions.

It has really helped us become more efficient. UiPath has made the lives of our data operators a lot easier because they would normally have had to manually enter all this information or transfer data.

AI Computer Vision has been great because it works through VMware. It's able to see the elements through the VMware window on the government system that we interact with.

UiPath's user community is great. I get a lot of answers and am able to talk to folks who know the products and can provide support directly.

The UiPath Academy courses are an easy way to learn how to use Studio.

The licensing has been a challenge in terms of what is included with our current license. They've changed it a bit.

The learning curve to get UiPath up and running is hard, although we're pretty comfortable with it now.

Promoting its use is the hardest part for us. It's tough to get people to believe in using the assistant or Studio without fearing the loss of their jobs.

I've been using UiPath for about five years.

It's very stable, and we've never had an issue with it.

UiPath is easy to scale. If we want to share the bot or the scripts, it is easy to do so with other team members. It is also easy to add licensing and grow the current bot or create a new one.

Our experience with UiPath's technical support has been really good. We get great responses to tickets when we need help. On a scale from one to ten, I would give technical support a ten.

Positive

The initial setup was pretty straightforward. We learned Studio, started with a simple script or bot, and grew from there. Our implementation strategy was to look at our highest demand for transferring data and make the bot do that.

Our ROI is that instead of having a team of seven people to manually do the data transfer, we now have two people.

The pricing is fair.

We looked at Blue Prism and went with UiPath because of its ease of use, the Magic Quadrant rating, and the price.

It's great software and has helped us a lot. It gives us a competitive edge.

Overall, I'd rate UiPath at nine out of ten and would advise you to go for it.

We're currently rolling out some of our first few automations. So far, it's been in finance and procurement. We're just automating some of their inventory processing workflows.

The automation will be unattended. We have three that are in active development and another six in backlog awaiting development.

The first few automations have definitely had an impact already. One that we're rolling out, we anticipate having a great impact. One that I'm currently working on should probably have the biggest impact so far on one of our departments. It will save us time and therefore cost. It's a very manual process with lots of human error opportunities. Between how much faster it's going to happen now and how it will be 100% accurate, we anticipate seeing a huge benefit from that.

I appreciate the infrastructure. There are numerous platforms through which we can perform automation. We are in the Microsoft sphere, and so we have the opportunity to use the Power Platform to do lots of automation. However, I've been impressed with the infrastructure that UiPath provides in developing, publishing, and rolling out these automations and then being able to monitor and manage them effectively.

The community can be helpful. In the public forums, I have seen some forum threads that are very active with lots of people that respond with great answers and great context, and multiple options. That said, there are just as many cases where no answer is ever provided, and it just disappears into obscurity. I've had multiple of those types of approaches myself, where I've posted questions and gotten no response. The community can be helpful. For somebody like me that wants to get something out of it, I would also need to be willing to put something into it and help others answer their questions, as that's how the community works.

For the most part, I was impressed with the Academy courses. They did a great job of introducing me to a new piece of software I hadn't seen before and establishing some familiarity with it. The instructor-led training from UiPath, allowed me to put into practice some of the things that I had learned in the Academy. 

The biggest pain point we've seen so far is that we have trouble identifying best practices in certain areas and circumstances. There is no shortage of resources in the Academy and on the forums that have great information. That said, a lot of them are specific to use cases, or they're too generalized, which makes it difficult to know exactly how we should be handling a certain scenario or just some basic things about how to best set up the folder structure for our given environment.

It's been difficult to navigate that as it is still so early in our implementation of RPA. We want to ensure we're doing it right to establish a good foundation from which we will build all of our future automation. We are constantly concerned that we're not doing something the right way.

During a UiPath conference attendance, I really appreciated having access to experts directly. I can just ask them, "Here's our scenario. In this context, what's the best practice?" And I can get a straightforward answer. We don't have access to them outside of this conference. I don't always have the time to watch the videos or go through the multi-hour-long training to get to the one best practice that might be nested inside a larger training.

Finding some of the answers ourselves is difficult since they are contingent upon our scenario and the context we're building. There's not a one size fits all. To that end, it's no surprise that there's not going always to be a single solution that can just be published to say, "Always do this, this way." Without that context, we really do need to be able to talk to somebody, and we haven't had that yet.

In terms of the UiPath community, I probably can't answer a whole lot of questions since I'm so new; however, for a community like that to function and succeed, there have to be enough people with the expertise that are willing to put in that time for free. In a realm of automation that touts itself as a solution for people who have no time, it's no surprise that there are not always people that are willing to sacrifice what time they don't already have to begin with to give out free service.

Once I have automation ready for production, I don't see a way to deploy that to a production tenant environment without manually recreating everything. In a typical development environment in software development, you develop in one area, and then when it's ready for deployment, it's packaged up with all of the assets and everything that it needs, and then you deploy it to the production environment. You do some final testing to ensure the deployment takes, and you're done. Whereas here, it seems like I'm having to recreate everything manually. I can import the automation, yet I need the whole structure and orchestrator and all of the assets (75), and I have to recreate everything manually. It seems something is missing. 

I just started using the solution three months ago. 

The solution is pretty stable. That said, that'll be a question better suited for me in about three months after we've had our bots live. Since we're only in development and testing them in pretty controlled environments, it's harder to tell. It seems like it would be pretty stable. However, I can't answer that fully.

From what I understand, it scales well. I understand that's one of the directions that we see ourselves going. We'll be taking on more and more automation and scaling up quickly.

I haven't had any technical support directly from UiPath yet. I've only learned that we can request a technical account manager, and I understand that we don't have one right now. I'm not sure what additional cost that may incur, either. It's always that question of the cost versus the benefit. That's what we need - that technical expertise from somebody that can have a short conversation with us and help steer us in the right direction.

I have worked in the Power Platform with Microsoft. That is not specifically for RPA, per se. However, I've worked in it and have familiarity with it. 

One of the biggest pros for sticking with Microsoft would be that we're a Microsoft shop, so it would keep all of our solutions in the same realm. We wouldn't have to export and import data across services and databases. It would just all be under the same umbrella. That's a huge benefit of sticking with Microsoft.

With UiPath, there's a stronger infrastructure that supports the development, maintenance, and scale of automation versus Microsoft. However, Microsoft is still pretty new and young to the RPA development environment, and they move very quickly. I would expect that they are not done developing their RPA suite either. I imagine that we'll see future iterations where they become a stronger contender to what UiPath provides.

I was not involved in the initial setup. That happened before me. 

We have yet to see an ROI since we don't have any of our automation fully live. We anticipate an immediate return as soon as these are in production based on the countless hours that will be saved from people's workdays.

The licensing is a headache. Luckily, I don't have to deal with it directly. That's above me. As a developer, I have to deal with the licensing just in trying to build new automation and ensure that there are licenses available to be allocated at runtime. That alone is just obscure enough to make it complicated and leave me unsure as to if I've set it up correctly.

I'm an RPA developer.

We do not yet use the AI functionality. 

I would advise potential new users to make sure they know what it is that they want. In our case, we need to choose between the options of sticking with the Microsoft Power Platform or going in a new direction with UiPath. Even though the Power Platform could potentially do everything we need to automate, it's not apples to apples against UiPath. If what your need is better suited to one or the other, don't force your solution into one product.

I'd rate the solution eight out of ten. I'd rate it higher. However, there are technical issues that I've encountered and a steep learning curve. We've had difficulty in finding the specific answers we're looking for and lack access to technical experts that can answer complex questions, pricing, the ambiguous nature of the licensing, and how those get provisioned. There are some core features still missing.

Our company uses the solution to process state reporting uploads for clients. 

For one use case, we automated the process of dragging forms, filling in fields, capturing confirmations, logging information, and moving files for upload. 

For another use case, we automated the process of manipulating data, setting filters, and generating reports in Excel. 

We are now moving to another department that uploads yearly tax reporting files to websites. 

We do not yet use AI but have many possible use cases for reading invoices and PDFs so we will try these processes first. 

We have saved a lot of time on uploads. For example, our state reporting uploads now take only two to four minutes and that saved us 7,500 hours for January alone. We anticipate similar time savings for the automations we are currently doing in another department. 

As we continue to automate our uploads, we will not need as many seasonal workers so that is a big cost savings. 

The solution includes preset activities but allows integration of code and expressions that make it more powerful and dynamic. In nine month's time I have barely scratched the surface, but it feels like it integrates to so many things that finding new use cases is easy. 

The automations allow us to better catch errors because data is always transcribed correctly.

The upgrade process could be improved so that it does not require download and reinstall. It would be nice to have an upgrade option that talks directly to the orchestrator. 

Some documentation can be improved. For example, documentation for integrations and activities tells you what it does but does not tell you how to fill in variables or fields. I had issues finding some things I needed for new activities or integrations. 

I have been using the solution for nine months. 

The solution is pretty stable. You may have version issues because there are a lot of updates, but that is not a stability issue. It is always important to make sure you have the latest updates. 

The solution is definitely scalable but it takes time to learn how to best scale. There are many routes you can take which depend on different things. 

The Community is super helpful because they share information that is of great benefit. Forums have been useful when I have needed help. 

I gained my experience through the Academy's courses. I was in a different role at my company but they needed another UiPath developer. For three months, I did a rotation with the RPA foundations course. After that, I was able to start working in the full time developer role. The Academy was very helpful and allowed me to jump in with no UiPath experience. 

Technical support is very helpful. I only contacted them once for an issue with the Salesforce API package that would not run with attended users. They responded in a timely fashion and helped me quickly resolve the issue. I rate support a ten out of ten. 

Positive

Our company previously did not use an RPA tool but rather used command line scripts and tools with Python. 

One of our developers had been writing scripts and came across the solution. He showed our company how much time it saves while improving accuracy. 

The setup is pretty straightforward. 

It is amazing how easy it is to automate some things. Once you learn the interface, everything is straightforward. 

I assisted our department in implementing the solution in-house. I helped build and run things for our big rollout in January of 2022. 

Since then, I have automated fourteen processes with attended bots. 

There is a big learning curve to ensure you get everything invested in the solution to realize ROI. 

For example, my department only had two developer licenses but still managed to save 1,300 hours in the first year. Another department was scaling a much bigger deployment, so it took longer for them to hit returns.

The solution is affordable enough to get a good return on your investment. We get ROI over the cost of licenses. 

We started out on-premises because we did not have attended licenses. Now, we are moving to attended for bots and trying to publish more things to the cloud so others can run them. 

I looked at Blue Prism but have not spent time using it. 

Start with a couple of solid use cases that would realize time and ROI benefits so you can see how the solution works. 

Do not go too wide or too fast with deployments. Focus on a few things first until you are clear how you want to expand. It is important to decide whether you want more citizen or RPA developers and whether your bots will be attended. Just take it slowly unless you are working with someone who has high-level knowledge. 

I rate the solution a nine out of ten. 

We use this solution for finance, HR, and for handling invoice reconciliation. We also make use of donation approvals.

I find that UiPath's user community was more helpful a few years ago. When I go to use the UiPath forum, a lot of the answers are copied and pasted from old answers and they don't make a lot of sense. That being said, I do still occasionally get some value from it. 

We also make use of the academy courses. We have put all contractors through the basic courses to make sure that they've got a basic level of competence. The academy courses are useful to test that people know what they should. The architecture courses have been most beneficial to us.  

We are saving approximately three and a half million annually based on the number of hours saved multiplied by a salary base rate. That ends up being approximately 60,000 hours a year that's being replaced by bots and this is a big deal for us.

The Orchestrator really stands out as the most valuable feature. We don't have to train anyone. They can usually pick it up really quickly. It is easy to use and intuitive.

A lot of the packages are very easy to work with. There are some challenges when updating a package that you've built or a library that you've built in UiPath. Overall, the extensibility is really nice. 

I would really like to see the package deployment updated. As it is right now, if you want to update something, you have to take down the latest code, sync the packages and re-upload everything back through the dev test to prod. It's a big hassle when we've tested the library ourselves. 

I have been using this solution for seven years. 

This solution is very stable. Any complaints I have come back down to package management and custom issues with custom libraries. Outside of that, upgrades are really quick and really easy. We have bots disconnect so frequently that it is easy for us to catch issues manually.

This is a scalable solution but UiPath could use some better visualization tools for bot utilization. They do have insights but they are a little bit rough to work with. I wouldn't want to put on a hundred bots at a time, but loading in a few here and there is really easy.

I used Automation Anywhere and Blue Prism for a while. The UiPath Orchestrator far exceeds the functionality of Blue Prism and Automation Anywhere. As far as the bot setup goes, UiPath is very easy to install, especially compared to Blue Prism. UiPath is more business user-friendly than Blue Prism. Sometimes it's nice to work with Blue Prism because it has such low-level code that it gives you a little bit more flexibility.

We keep it pretty agile by necessity. We use a lot of contractors to get a lot of different approaches. We have 168 processes on 27 machines. We have some restrictions based on the company requirements but internally we move as fast as we can because we have to.

It is really easy for us to set up a VM and get UiPath installed. It is a five or six-step process. UiPath is significantly bug-free compared to what I'm used to with other products. I haven't had to raise a support ticket yet for UiPath.

Initially, we had a customer success manager from UiPath who showed our admin how to run the installation. At this point, we take care of all of it ourselves. 

We've replaced the equivalent of 20 to 30 employees who have all been moved to more valuable positions. We've taken processes that were supposed to take months and reduced this to days which has improved our customer experience. 

I would like to see a few more options for developer licenses because we end up swapping them so often. We've tried going through floating robots and a few options that have been not exactly what we're looking for. Price-wise, the cloud offerings are good. 

I'd certainly say UiPath is worth it to save time and effort. The product is really stable compared to what I've worked with before. 

I would rate this solution a nine out of ten. 

We generally work on integrating it with our support ticketing system, which is ServiceNow. That way, we can standardize our input and get better results. It has been working really well for those kinds of processes.

A process that we worked on for operations, for example, was the ordering of phones for our new agencies. It accelerates a lot of that process and gets the people onboarded faster, more easily, and with fewer errors.

The most valuable feature is that it can be integrated with almost anything. We use in-house applications and we're able to integrate them through the database using endpoints and APIs. This sharing of information between systems via UiPath means our staff gets results quicker. Normally, we have to put in a request with the database team to go in and input the data. But UiPath already has access and it's really quick. It's really responsive and makes the experience easier for the business.

That is also true for third-party vendors. The vendor that we order our phones from has a UI, a website that we use, and we have been able to use the UI to integrate their application.

We can implement almost any interface that we want, in any way possible. It's really flexible.

And given that healthcare is highly regulated, UiPath works really well for credentialing and that type of security. We see that it has protocols that ensure that our data is not going to be stolen. We use the credential assets to save our passwords and sensitive information such as licensing.

I've been looking into Document Understanding. I've worked with it in previous jobs, things like AI center and OCR for documents. It would be helpful if they made the Document Understanding modules a little more user-friendly. There is a learning curve for using it correctly. It's a little bit hard, but once you get a feel for it it's good and it doesn't delay the automation process.

I've been using UiPath for almost four years.

The stability of UiPath is good. I haven't seen any abrupt occurrences in my time using it. Our production environment is always running. It's well-secured.

In regard to our processes, it's easy to scale. It is not that easy to scale on the business side of things, but the tool itself does provide an easy scaling process.

I haven't had the need to reach out to technical support that often because, with the community, you can find out anything regarding UiPath online. It's the same support team that answers those questions.

I did submit one ticket to support, and it was answered really fast. However, they did take a little long time to get to the root of the problem.

Positive

We did not have a previous RPA solution.

We do calculate ROI in terms of the hours we're saving the business. For example, with the specific processes that we created for phone ordering, we're saving the business a lot of hours. 

Currently, we're just using it for agencies because we want to see how this can impact things. But it's handling the process for more than 40 percent of our employees because most agency employees get phones as soon as they are onboarded.

I have evaluated other automation tools, and I've been asked many times in the different companies where I have worked why I prefer UiPath. It's the best choice because of the community, documentation, and the number of updates they come out with. They're really on top of things.

Other vendors are not on the same level. I have tried Blue Prism but it has poorer documentation and it doesn't have the support that UiPath has.

To get our certificates we had to use the UiPath Academy. The Academy gives you a sense of how UiPath works. It can get really technical, but to get a sense, at least, of how to start the journey of becoming a developer, in my case, it helped a lot.

Overall, it's a great tool to use. It has a lot of benefits documentation-wise and support-wise. It's really stable and it's really easy to use.

Our company is in the insurance industry and uses the solution to run RPA processes for the claims department to free up staff time. 

The scheduler tool is valuable because I can slow or speed up run times during peak use. 

Our solution is on-premises so we are unable to utilize phone apps.

I have been using the solution for three years. 

The solution's stability is 100% and really good because it never goes down.

The solution offers the best scalability of any known product. 

I have not utilized technical support because that is handled by other team members. 

I personally did not use another product prior to learning the solution. 

I was not involved in the initial setup. 

We track ROI quarterly and through Q2 we have saved more than $100,000 by using automated processes. 

We are getting to the point of reaching full ROI but need to build more automated processes to reach that goal. 

I am sure my company evaluated other options but the solution was already in place when I joined the team. 

I utilized Academy courses to understand the solution's full capabilities but haven't yet used many of those features such as AI. I am currently learning about OCR and plan to use AI in the future. 

Learning the solution is a case of "I don't know what I don't know" so it is important to become aware of all the tools at your disposal. 

I rate the solution a nine out of ten. 

We automate everything using the UiPath solution. We have some ongoing stuff, e.g., generating test cases and testing some of our development platforms. We need to define all the parts, such as how to test the entire environment to determine if everything is working okay.

We utilize all our services on the cloud, then they can be easily used across all our offices.

We only use unattended automation.

If a product is about to go live, we heavily rely on coverage from UiPath. This is during the development phase. However, when onboarding to production, we use other solutions, which don't rely on automation, for monitoring purposes.

When we are in the development phase, we have multiple edge cases, like iOS, Android, and other platforms, checking in. For a tester, it is difficult to check every edge case. Instead, we define automation test tools in UiPath, then our automated work does everything for us. Once it is done, it gives us a detailed analysis about where the product is performing well. We get handy videos before going live so we can improve everything and ensure that our end customer will not be impacted.

Our bandwidth has been drastically reduced, by nearly 60 hours, because of this solution. We have reduced the number of testers by three. 

The most useful feature of UiPath is that it is very easy to use. 

It helps us a lot with digital transformation.

The UiPath solution doesn't currently provide unique testing for mobile devices.

I have been using it for around six or seven months.

To the extent that we are using the solution, it is pretty scalable.

We use a third-party for support of this solution.

When we were facing some small issues going to the cloud, we tried to get help from the community. The community has been very helpful. Everyone has been willing to provide some good information to other users.

Previously, we were using an automated script to test everything. Now, with UiPath, we are automating everything. 

We used the community to help us with the setup.

The vendor helped set this up and guided us how to do everything during the onboarding process. Therefore, we didn't have any issues with the setup.

UiPath has reduced human error by 20%. 

We have reduced our costs by approximately $200 a month.

Creating our digital transformation didn't require any additional costs.

The vendor gave us a 30-day money-back guarantee. We were fine with that. We saw improvement during that time and kept the solution. 

We didn't consider any other solutions.

I would rate UiPath as eight out of 10.

We have a variety of projects we use it for. We have automated about 72 processes within six verticals, including sales, finance, HR, and purchasing.

It has helped our client save thousands of dollars, for sure. That is really what they have found to be the biggest benefit of using UiPath. The cost of the product is low because they're using it continuously. It saves cost and it helps them gain more returns.

Our main projects are mostly around SAP and Excel. We have used most of the features available, especially the ones that support SAP and Excel activities. Those are the ones that we have found to be most useful.

UiPath is easy to use and there is less coding. That is very helpful for the development team when it comes to building projects. It's very flexible and really makes our team more efficient. The turnaround time of development is good. 

There is some scope for improvement, especially in the area of variables. Some variables are used in specific workflows and some variables are global. It would help if there was a repository that would showcase which variable is global and which is local to a workflow.

UiPath should also help us whenever we are changing versions. Whenever we make those changes, UiPath should help by documenting the versions and sending us comments on the changes made in UiPath. If that were available, that would really help.

I would also like to see something related to auditing. That would really help the development and peer review teams to identify the gaps, instead of going through the sequence one by one. If there were an auditing tool that clearly brings out issues, that would really help.

We have been using UiPath for four years.

UiPath is a stable solution.

They are plugging in a lot of features that are really helping our teams. It is scalable.

For this year, we don't have plans to increase our usage of the solution, but it depends on our client.

The technical support is good and they respond to us all the time. Whenever we require support, they are with us.

They have a standard questionnaire that we have to complete and send in, and they come back with standard responses. At critical times, instead of the standard response, if they could do a direct call that would really help us. Instead of one or two levels of questionnaires, if they could directly get on a call, that would help us. Hence I rate them eight out of 10.

Positive

I was not part of the initial setup, but I am involved in the renewals.

The renewals could be easier. The documentation is lacking. When you are renewing your licenses, you might encounter errors but there are no proper documents available to explain how to handle these errors.

In terms of maintenance, our automation processes require some attention but UiPath, as an application, does not, other than updates.

There is ROI over a period of years. From the second year onward, it would be around 25 to 30 percent.

The pricing and licensing are okay. It's quite affordable.

There are a few things that come with additional cost. They are mostly features. For example, Document Understanding is an additional feature that you have to pay extra for.

I would recommend it to new users who are choosing among automation tools. 

Also, if a company is new to it or the users who are setting up are new to it, they should be aware of the preparations involved in setting up the environment and setting up UiPath. That can be a little challenging if they are not aware of certain things.

I rate UiPath at eight out of 10. There are a few features or approaches they could enhance, such as an option to view all the variables, as I mentioned earlier. Also, since the code can be very big, we might be searching for certain things that are not available. I'm more concerned about the debugging and evaluation parts. 

And in Orchestrator there are a lot of features they can enhance.