UiPath Reviews

We don't have a single primary use case. We use the Orchestrator studio to deploy attended and unattended robots to relieve the workforce of the mundane tasks that they currently do.

I don't think there is one most valuable feature. From my viewpoint, Orchestrator is great because I'm able to manage and control the robots and licensing. Obviously Studio is very valuable for our developers because it gives a nice visual way of developing the robots. Of course, the robots themselves do all the work. It is really a package that has to be put together.

The Insight product coming out in the next release looks interesting as a management tool, but I haven't dug into it enough to fully appreciate it.

Obviously, the Studio can always be improved. Even though you can drag-and-drop, it's still cumbersome unless you are a programmer. I think the Studio X is going to help tremendously for the citizen developers. I think that is going to be a big benefit in simplifying the interface.

There are currently four-and-a-half people in the organization involved in the automation project and I think we'll have no problem scaling that up as necessary.

We have used UiPath Academy. In fact, we've actually referred our citizen developers there.

On a scale of one to five where one is the least beneficial and five is very beneficial, I would rate the UiPath Academy about a four. It is specifically for developers, so there is a complexity level there that can take a little bit for say the average user who isn't an expert to get through, but for somebody who's already done development, it's good.

We actually signed up as a premium support member and took out a contract back about four months ago. Christopher Wilkins is our liaison and he's phenomenal. Absolutely any time I called Christopher, he has gone out of his way to help us. He's our success manager.

From the time of purchase to deployment took about six months total. We did a quick prototype that I had spent two months to get it up and running and then it took me six months to clean it up.

I thought that the implementation was complicated but that was because they did the prototype and then handed it off and I had to come in and take the prototype and actually make it work in production.

We run the automation in a virtual environment. It was a bit painful to get it all working. We actually use Citrix VDI (Virtual Desktop Infrastructure) environment and the problem with that is it uses a storefront. When you log in, it doesn't know which server you're accessing. UiPath had problems with that, so we had to ditch that attempt. What we're doing is we're using the VDI image just to read and chart virtual machines every four months and using those for our UiPath.

We did use a third party. Our experience with them was good and bad. The young man that came in from the Netherlands was extremely bright, but he was all over the place. So he thought he knew how certain things would work and in reality, they did not. So it was painful because instead of having a methodical way of working through the issues, he was jumping about too much and it didn't go very smoothly.

We don't really have exact numbers for the return on investment right now because we are too early into the process. We are still trying to get the whole organization comfortable with the concept. But you can see the processes have helped reduce human error in the finance area. It has also saved our organization time. Anytime you don't have a person doing the manual work, they can go on to do better things with their time.

I inherited a bit of a mess. On a scale from one to five where one is very difficult and five is very easy, I would rate the ease of use of the platform for automation as about a three. Most of the problem is with the processes themselves having not been streamlined. So if there is a bad process in place and we still have to automate it, it will still be a bad process.

On the other hand, we do experience performance benefits using the solution. For mundane processes, the people who no longer have to do them because they are automated are extremely happy about that. The benefits were almost immediate. If we had somebody wasting three to four hours producing a single report that we can have a robot do, it's an immediate benefit.

On a scale from one to ten where one is the worst and ten is the best, I would rate this product as a nine or ten. I think the product is tremendous. We're still early in the process. As we get into AI, I think it's going to be a tremendous benefit.

My advice to anyone looking into this as a solution is to let somebody else do the deployment. You really have to make sure you understand the infrastructure required to properly scale up the solution. Make sure that you have senior management on board with the concept and then work hard to get citizen champions out there as soon as you can.

We are using Orchestrator and unattended robots.

We use this solution for automating financial tasks. Some of our use cases including reconciling amounts, such as those related to invoicing.

We run some of our automations in a virtual environment. We have been running into roadblocks with Citrix, so we run them on virtual desktops.

With respect to how easy it is to automate our company's processes, on a scale of one to five, I would rate this solution a four. Building automation using a standard set of rules is not a problem. It can become problematic depending on the data and the types of tasks.

On a scale of one to five, judging how beneficial it is, I would rate the training a four. We are using it to gain experience with the platform.

From the point that we purchased our UiPath license until we had our first robot was probably three or four months. The first robots that we created were for account reconciliation, and the implementation was straightforward.

At the least, this solution is making us rethink the way our processes work. Putting automations in place not only helps to save time, but it gets people thinking about where else we can use automation.

This solution is improving our employee experience, giving them time to do other things. From a resource perspective, we are staffed the same way, but our employees are able to make better use of their time. In total, we have saved thousands of hours.

In terms of eliminating human errors, we have seen an improvement of approximately twenty percent.

The most valuable feature of Orchestrator is that it gives you the ability to control everything from a centralized location. You can have access to everything that is running.

For unattended bots, the best feature is the value that you get from not needing to have somebody there to do the job. It's a time-saving benefit.

Several areas of this solution need improvement including insights, the dashboarding of results, and process mining.

When it comes to scoring, you receive a score after the intake and a score after you build it, but you should also get a score after you build it.

With respect to the stability, on a scale from one to five, I would rate this solution a four. The system is generally pretty stable. Some of the things that cause instability are outside of UiPath, or the robots interact with them.

There are between fifteen and twenty people involved with the automation program in our organization.

We have used support and they are ok.

We hired LTI to assist us with the implementation. Our experience with them was not good. They had a few really capable people, but not the whole team. They were learning along the way.

We began to realize ROI after six months.

This is a good solution, and the availability of training helped us to get started.

Definitely, the Insights component needs to be improved.

My advice to anybody who is implementing this solution is that the solution can be great, but it will only be as great as the design of your processes. You have to make sure that everything is done right to get the best results.

I would rate this solution a seven out of ten.

We use Studio, Orchestrator, and robots.

With respect to how easy it is to automate our company's processes, on a scale of one to five, I would rate this solution a two. It's been going for about six months now, and we are still having challenges here and there.

On a scale of one to five, judging how beneficial it is, I would rate the training a three. The material is on the technical side, and not being a technical person, it makes it pretty challenging to get through. 

From the point that we purchased our UiPath license until we had our first robot was approximately three months.

With respect to saving time, we have saved about fifteen hundred hours so far.

In terms of eliminating human errors, we have seen a reduction but I'm not sure by what percentage.

The most valuable feature is that you can save time when you have to run the same process over and over again with little variation. 

It is sometimes difficult to work with the exceptions, which can cause us a delay. We have a lot to learn.

I would like to see more options that we can quickly select to help improve the robots.

With respect to the stability, on a scale from one to five, I would rate this solution a four. Most of the time it is working pretty well, but there have been a couple of blips along the way.

We have approximately twenty people who use this solution in our organization.

We hired a consultant to help us with the implementation. I would rate our experience with them at three out of five. It was successful, but we had to redo some of the stuff that was originally done.

We have seen ROI but it is pretty far off right now. After about three months, we began to see ROI. I'd say that it is probably going to be about two years before we break even.

We are excited about the new features that were recently announced.

My advice to anybody who is implementing this solution is to hire a consultant who is familiar with the process. It is such a new technology that getting assistance would be helpful.

I would rate this solution a nine out of ten.

Our most prevalent use case is invoice processing.

We are using Studio, Orchestrator, attended bots, and unattended bots.

It comes down to saving people time to be able to look at high-value tasks.

The solution has helped us eliminate human error with 100 percent testing and accuracy. This is only where there are exceptions, which generally tends to be under five percent of the time.

The solution has saved us time. It does depends on the specific process. For one specifically, it took a week out of each month, then we were able to process the same reconciliation process within minutes.

Studio is the most valuable feature from the aspect of developing a bot. It is very nice from the drag and drop perspective. It is very easy to follow and has low guidance from the technical aspect.

I would like to have cloud in the next release. It's one of those things that allows customers to be able to have an easier access point.

There are still areas for improvement for some of the drag and drop features and moving more to a bit of a lower code perspective.

I would rate stability as a five out of five. Compared to competitors where we've had instances where either exceptions are kicked out or the workflow breaks, UiPath does not encounter those issues.

About 50 people in our organization are involved in our automation program.

The technical support is very good. They are very good partners.

The experience overall has been really great with UiPath. The culture and individuals at the company really help make the project easy to do.

We had a very manual process that needed to be addressed because it was taking up way too much time of employees' efforts.

The initial setup was straightforward. Going through the certification process, it enables you with the tools to be able to implement at an easy level for low-hanging use cases.

It took about a month from the time we purchase our UiPath license until our first bot was live.

We used a consultant for the deployment. I would rate our experience with them as a five out of five. 

I would rate ease of use as a four out of five. We had a bunch of people that do implementations from a development aspect for our use cases. The solution has been very easy to be able to implement for our specific use cases, given the capabilities of the platform.

We have seen ROI from this solution. We saw it almost immediately in regard to performance benefits around accuracy, timeliness, and the ability to do 100 percent testing.

We also evaluated Blue Prism and Automation Anywhere. We chose UiPath because of stability of the platform, ease of use, and the deployment factors are much easier with UiPath.

We have used UiPath Academy for RPA training. I would rate it as a five out of five. Compared to competitors, the UiPath Academy offers a very easy path to certification. The way that the curriculum is laid out, it is very nice and easy to follow.

Do your due diligence.

We have probably use attended bots more heavily. They're very nice and everybody has a good experience with them working alongside actual humans.

I would rate the overall product an eight out of ten. There are additional features that probably could be rolled out. I think there are on the roadmap.

UiPath is best at its core and with the help of plugins from UiPath and community you get solutions to a lot of problems out of the box. I have tried couple of more platforms, but the easiness, diversity and flexibility that UiPath provides is unparalleled. 

In the recent top 50 enterprise application at g2crowd, UiPath is at 18th place and topmost in the automation platforms. 

I have done quite a lot of different real-time projects with UiPath. In one big project, there was a lot of loan applications from scanned documents. We used Abbyy Flexicapture for reading OCR and ICR text and we read it very accurately. It really boosted the moral and now we are automating the whole CAD department of the bank. 

Now we are looking forward to more complex processes and try using the ML and AI into it.

RPA is our bread and butter. We have implemented projects in the telecom and financial industries. 

A good example was when we implemented a network process in the telecom sector. The time for that process was seven minutes, then by implementing the RPA, we drastically reduced it to 40 seconds. The process involved worked on four different applications. Each application required a secure login, and the speed was due to the websites being hosted on the Internet. It did not require any internet connection when we implemented RPA on-premise, and used complete network and system resources.

• The ease of the processes
• There is no coding at all required to implement a complex business process. If you have some programming background, it will help you. However, if you are a business user, you can still develop simple processes.
• The automated recording helps quite a bit. You record a complete business process along with human interactions to the desktop or web application. You can easily manipulate them. Once you are done, you have a complete recording of the interactions, which you can use to tweak your requirements.

You can't write small snippets of code. If you want to do a single code snippet, this is not available by default. For example, if I want to do some date conversions, and that date conversion requires different variables to be available in the context, but they are not there. A small snippet of code change should be available out-of-the-box. This will help me in the long run. I can create activity out of it. Support for a little bit of in-line script should be there.

There aren't stability issues, though it should have better RAM and cores. When it's overloaded you get considerable problems.

Scalability is one bit which should be properly planned at the time of license and planning. For tight budget projects, you have to be very precise in the runtime execution requirements otherwise, you might face issues.  

Tech support takes time replying to queries. The more you go to the community, the more likely you will get replies. Therefore, tech support should be improved.

The initial setup was very straightforward. We were up and running in approximately 15 minutes. UiPath is the best of breed in the market for setup.

Licensing is one of the big issues when I have been doing some pre-sale activities. One robot price licensing is quite high with UiPath. They should provide some discounts to partners so we can spread the product easily in countries, like Pakistan and other areas in the Middle East. Licensing should be reduced and price should be cut down a bit.

We also evaluated Blue Prism. We went UiPath due to the community support.

It has a lot of community support with a lot of help available. It is a very mature tool.

The academy for UiPath is very good place to start with UiPath. It is easy and the learning curve is quite low.

We use UiPath to log into a system, run a report, extract the information from the report, and send emails to hundreds of people, all in just seconds.

We have a requirement when someone leaves the agency that you have to remove access immediately but that wasn't always done. This allows us the ability to take the daily report when people leave and send notifications to the right people to remove system access.

UiPath allows people to do more value-added work. I found that we were able to take a person well versed in access programming and convert them to be an RPA developer with relative ease.

The UiPath Academy RPA training is phenomenal. Just the fact that they offer that information is a huge selling point for them. I continually share links to the site and I encourage people to go out. I tell them to take the training if they want to learn more. I started the technical training, but I kind of oversee the program, so I didn't have to learn all of it. Nevertheless, just the awareness of what RPA is and those intro-functional courses were very informative.

It was more difficult to use than we originally thought it was going to be. It's not as simple as drag and drop. You really have to have a background in IT development type of work. I suppose you could make simple automations but we definitely found it to be more complex, especially the supporting infrastructure beneath it.

I think where the improvement needs to occur is within the federal government to put out the policy that it has been determined to be a safe product that can be put on any DoD network. That would be huge, but right now that decision isn't out there and every agency has to go out and make its own determination. Some CIOs are more risk-averse than others. That would be one thing, but obviously, UiPath doesn't have a way to influence that.

We don't know about the scalability until we get in there. From everything I've read and heard, I think it will be scalable and should fulfill our needs.

Technical support has been very accommodating. In fact, they'll be on site to help us overcome some of the challenges we've had without having third-party integration support. We've been struggling on our own, but UiPath has been there and has even agreed to come onsite to help work through some of these issues.

We have automations everywhere through the agency. There were a lot of presentations being held. Senior leaders started to get wind of this and other organizations were sharing their successes and that kind of piqued our interest to assign somebody to explore it.

The initial setup was complex. I've just seen the emails that go back and forth and I think if we had a third-party integrator, it would have resolved a lot of our questions. The security aspects have been our biggest challenge and concern.

We absolutely have a return on our investment. It gets difficult to really quantify what the ROI is when you start looking at that. Just the ability for technicians to do more value-added work is hard to put a price on. We have a system that stores a lot of documents. Our pilot bot was just to log into that system and download the documents for audit purposes. Now we can literally let the bot run for 12 hours pulling all the documents and those people can do more important things.

The pilot bot we set up to send those emails, equated to about 350 hours a year. The audit bot is almost endless because if we can share those bots with our customers and the customers can do the same thing and achieve those same benefits, you're getting into millions of potential dollar savings.

This solution has definitely helped to eliminate human errors, as well.

It would be nice if you could just buy the product instead of having the annual rate license renewals. I assume that's how UiPath makes its money. It's expensive, but I guess we'll have to do the business case to see what the ROI truly is.

Automation Anywhere and Blue Prism were really the main competitors. The UiPath Academy, for one, was a big selling point. Other than that, just having conversations with other government agencies that have used UiPath and have succeeded in that development helped us make the decision to choose UiPath.

We have hundreds and hundreds of IT technical specialists. We have very sensitive information that must be protected, which is IT's primary focus.

I would rate UiPath as nine out of ten, not a ten just because of the pricing.

My advice to someone starting out with UiPath is to get third-party integrator support.

We have multiple primary use cases for UiPath. We have already implemented three, but I foresee many use cases in the future. For example, I am working on one which will automate the gathering of information to comply with subpoenas.

The automation of repetitive tasks that eliminate human error. 

The speed: It is so fast when it replaces a human, you become much more efficient.

I would like to see some integration, or ease of integration, with APIs, so we can automate stuff faster. E.g., we go through a co-op, which is a card processor, and they have a very powerful API.

I haven't had any issues with the architecture at all.

We are starting small and have three bots.

I'm already engaging in conversations with UiPath consultants to ensure that I have the right structure. I know I will need Orchestrator soon as we continue to develop more.

I introduced automation with UiPath. This was our first introduction into what is robotic process automation.

The setup is straightforward. We did the complete setup in a week, which includes the server, the virtual machine that it would be running on, and a developing environment, because I wanted that to be separate from our production environment. This is for a small environment. I am expecting the bigger environment to take us longer.

For our service test department, we created a bot to automate the reset of pins and passwords for our users. This was the number one call for our service desk. The bot now takes care of it, and we freed resources. Now, we don't have any calls to that service desk team, and they are doing other things.

It was easier to use than I expected. We started with a very small bot. It took us three to four weeks to develop, then put in production.

My staff is using the UiPath Academy. I manage the development department. My staff has gone through the Academy's training, and it's awesome. It's a great resource, because now that I'm hiring more people, I'm having them go through it. Then, I onboard them on what is it that we need them to do.

Development of any RPA solution using UiPath is very efficient and flexible. But at the same time, the testing is very difficult. The debugging feature of UiPath is quite difficult to understand, and there is no option that we could go and start from any step, rather, it needs to start from the very first step of the process which would be again a time-consuming factor.

The processes we automated are not only under the financial domain but also non-financial domain too. It proves that RPA is capable of implementing in almost every client. It really helps human to do better jobs rather than doing the same duties daily. It makes life easier. The dashboard that shows in UiPath Orchestrator would really help businesses to calculate their return of investments and all. Again, it would show a brief idea of the number of robots utilized.

I recommend UiPath to others. It doesn't limit your skills in a programming language. Instead, it has a more extensive feature on it. Hence we can utilize those to inject our code, and it is versatile to any programming language even though the technology that UiPath uses is built under .NET.

UiPath overall is a better RPA tool. But when it comes to the testing and debugging part, it's quite difficult. 

Most of the time, the RPA code solved through UiPath is stable. But sometimes UiPath would hang/stick itself.

It can be used to automate large complex solutions.

Excellent customer service/technical support with quick response to our query.

Yes, I was into Blue Prism. I switched to UiPath since the client wants to implement the solution using UiPath.

Initial setup is not difficult. Once we get the license key, the same needs to be provided during the installation.

I didn't implement through the vendor team.

I don't know how to calculate the ROI. But the dashboard within Orchestrator would provide a measure to show the total number of robots and processes.

Compared to other competitive market RPA tools, UiPath costs less, and they have a Community Edition as well.

Yes, at a high level and got impressed with the additional features in UiPath.

UiPath itself providing some activities to write coding and all. I suggest when we do an RPA solution, making use of such kind of activities which would increase the stability of the code.