UiPath Reviews

We primarily use the solution for insurance processes where we have redundant activity and we have pain points for our customers. It allows the employees to do more insightful work.

As we are mostly using unintended robots right now, the main value we see is the ability for the solution to take away the redundant tasks. That's the key value. But there's tremendous potential in the attended or hybrid model. The value I see there is allowing people to automate partially or at a time. Whether that's something that we've identified clearly now or something that we look at in the future, I think that lives in the attended or hybrid piece. It would be nice to just see what more we could do and what more value we could add to the business there.

On a scale of one to five, I would validate the ease of use to maintain our processes almost at five now that the solution has introduced Studio X. Studio X has the potential of empowering people to prototype and then pass along more qualified information. It's a game-changer.

Right now just being able to capture process, even without Studio X, let's say we video it or we capture it by way of a traditional Vizio diagram, enables asking work instructions, etc. It allows us to capture and standardize what people are doing as well as take steps toward optimizing processes in general. It's all good stuff.

I wouldn't know without looking at the actual metrics, but I would say in general our pay projects probably cut time by factors. Simply because people do things more slowly, more inefficiently. They're interrupting where the bot is not. That's the reason why we love it so much. The potentials of cost and time savings and the possibility of really having people get some of their time back is great.

We haven't had any problems that make the solution look unstable. I'd give stability a rating of four out of five.

As far as stability is concerned, I'm not sure what people who have deployments of hundreds or thousands of bots are seeing in terms of stability. We're small. For a small implementation, we've had a few hiccups and a few concerns where I would say, how can we triage more quickly, or how can we understand what we've caused more quickly? How can we implement strategies for redundancy and business continuity management? What guidance is there from the company on that and how can we be very transparent to our customers to be clean, concise and clear about that? 

I've talked to a lot of the technical support team. They all know that we're really happy with their responsiveness. We were really happy with the product and we're really happy with them. Just continuing to get the guidance, meeting with them, considering strategies and having them support us has been great. 

In this day and age, RPA is the appropriate tool for certain issues where a lot of times I think a lot of firms, not just ours probably go, "Hey, we don't need a longterm solution that will last forever, but we do need something that's going to automate this process and is going to take this pain point away from the business and this appeases that need." I'm not sure if that's specific to any one certain company; that's just the way that people approach it.

I'm not quite sure the exact reason why our company chose to automate. It was decided before I joined the team.

Implementations from process assessment through actually bringing something to production takes about three months. We'd like to be at six weeks like everyone else. But right now, we're at about three months.

It'll be more straightforward in the future now that we have tools like explore apps and insights. 

The complexity of the project informs the complexity of the implementation. We are an IT services company. We have a very standardized kind of approach to testing and bringing things to production, so I don't think that's terribly complex. It's kind of business as usual. We recently brought a project to 10 productions that had three parts to it. We staggered the implementation that typically might be more complex than what other people are doing. The complexity of the project introduces complexity to the implementation, which is fairly straightforward.

We have a partner that assisted with implementation.

The performance benefits are usually pretty quick. The process assessment that we do that hopefully determines the processes that we would pick, allows us to see ROI fairly soon. I'm not sure what the timeline is on that exactly.

I'm sure our process probably looks like a lot of other companies. We go and look at not only one solution but also its competitors. We look at the top of any certain field and make a decision based on what fits the need the best. 

My understanding is the solution is deployed on-premises.

We also run our deployments in a virtual environment and we have the potential to do hybrid things as we have more processes that are in the pipeline that we must review to see what our roadmap looks like going forward in the future. Our experience with automation within virtual environments so far has been fine.

In terms of the UiPath RPA Training Academy, I've taken a few courses. I've also done Academy live and watched tutorial videos. The UI path engineers and customer service managers, as well as some of the directors that are local to our area, have been very helpful in providing this information. I fully intend to continue to do that and as long as it's available. If I were to rate the training materials, I would say the training materials are probably a five out of five rating. There's a lot of information there.

I would suggest others give the solution a good hard look to see if it works for them. Hopefully, for others, it will be a successful product and a useful tool.

Overall, I'd rate the solution eight out of ten.

We have two customers. One is in the insurance industry. We are implementing it within our own company to automate HR and finance processes: back office. This is the same thing with the customer: back office. That's the focus.

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

For one of our clients, their intent is to create a bot because one of their key folks was retiring. This person had a lot of knowledge of the processes and how things happen. So, the idea was to create a bot that helps. They want it to do 25 percent of most of the work, and this person would just validate instead of training somebody new to do the job. Their idea was to not hire for that position anymore. Instead, if the person is just doing validation, 25 percent of that load is then spread across their current staff.

It is easy to use. That is definitely one thing that attracts people. 

I really like the feature that you get to record actions. I wish that feature was a bit more advanced where I could build more automation. Sometimes, you have to stop the robot because the robot doesn't get the level of detail that I am expecting to see in the automation. Then, you have to stop the bot, and stop or break the recording. While it's nice in creating a first sort of brush off your automation, I wish it would just go a step further.

I really like the new products that were announced here. The apps have a lot of potential. I'm interested in learning more about that in the next few months. The same thing with StudioX. Although, it would be interesting to see if they're more business-friendly or not. While UiPath is advertised as a low code platform, you can't put it in the hands of a business user. They have no idea what some of the features are. Some things, they need to have extensive training and be tech savvy in several things before they can go there.

Several of us took training using the UiPath Academy. I thought the UiPath Academy was very intuitive and easy to use. I would give it a five out of five rating.

When you are tech savvy and been trained, it is a four out of five for ease of use. Having that automation recording feature operate better and capture more of the automation that you're trying to build would make it a five. 

With the new products that were announced, UiPath closed a few of the gaps. I can see how they could expand the products into other areas. There is potential there for some workflow capability. I know this would be going beyond RPA at that point, but having one platform that does a lot of things would be nice. Because as it stands, when you need to do a workflow or approval process, you need to send this out somewhere else. There are things the bot can do, but I can see some of that functionality already showing up though with the tasks and apps. However, I would like to see more. That would be good.

Moving bots to the cloud would be the next good step. The new product has Orchestrator in the cloud. I think moving to bots to the cloud could also be next along with having Studio in the cloud where you can do everything in the cloud: Deploy and run your bots from the cloud.

It is pretty stable. I would rate it a five out of five.

I haven't used the technical support.

We learned about this stuff about two years and a half ago. We started exploring it, then we decided to take the plunge and try it out. That's how it came about.

The initial setup was pretty straightforward. 

It took us about four months from the initial purchase of UiPath to putting the robots in production. With our first deployment, we made a lot of mistakes. For us, it was like the first time you do something, you don't know exactly what you're doing, you just do it. Then, the second time, you're like, "Oh, now, I can go back and do other things differently." With us, it was very much like that. We learned sort of on the job.

We did the installation ourselves. 

I didn't do it, but I know that the people that did the installation didn't have any issues with it. They didn't need to open a ticket in particular or anything like that. This tells me that it was fairly easy. 

We have saved steps and time from people doing their jobs because they're not doing all this crazy validation anymore.

We evaluated the top three. UiPath at the time was number three, Blue Prism was number number two, and Automation Anywhere was number one. So, we weighed them out.

I liked some of the functionality from Automation Anywhere. The recording feature of Automation Anywhere was much better and easier to use than UiPath. Although, I haven't seen the new Studio. In 2019, maybe they changed some things in there. Regardless, the Automation Anywhere tool seemed easier to use. But, in terms of partnership, they were not a good fit for the values of the company. Those things all go into account when trying to partner with somebody. That's why we decided to go with UiPath.

Some of the features in the software looked the same between Automation Anywhere and UiPath. Blue Prism seems very hard to use. That one we kind of killed on the spot. Between like Automation Anywhere and UiPath, it was more about how the company's vision, and where things were headed. All of that sort of helped. So, we were at that point that we were not really looking at the software anymore. We were looking at other things. That's how we ended up here.

With the new additions that were announced yesterday, I'd probably give it an eight (out of 10). I still would like to see some other features, which I know UiPath would start crossing into BPM a bit when you start talking workflows and things like that. However, that would be a good next step given their market share, customers outreach, and beyond API and some partners that they have today.

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.

I am automating a validation of work items between BP open and SAP. Avoiding too much manual labor on the part of the user, freeing the time gained for more analytical and less repetitive work, all developed on Windows 10.

The tool has provided a safe and trustworthy way to develop robotic process automation, with a great increase in productivity and reduction of rework.

• The ease of learning, in addition to the great contents of the UiPath academy
• Speed to start producing results
• Extra friendly interface
• Excellent Orchestrator for managing robots and logs.

I miss a functionality similar to the "immediate window" of Visual Studio. The immediate window is used for debugging and evaluating expressions, executing statements, and printing variable values. The immediate window evaluates expressions by building and using the currently selected project. Therefore, this would be a great facility for debugging using UiPath.

UiPath is a robotic process automation software that helps enterprises automate their workflow.

RPA can improve enterprises' work flow by automating repetitive tasks, time consuming tasks, and basically a value add that can be automated.

We are a partner of UiPath, and we are a consulting company.

We sell knowledge, but we also have other offerings like managed services, everything that is included in an RPA. We are a pure play company meaning that we only do RPA and we are specialized in that.

I am personally very supportive of the new trend, which is the attended automation. I think that the new strategy of UiPath path, the automation for strategy, is very promising because currently what RPA is doing, it is starting from the process, a business process to automate repetitive tasks to bring ROI. Right now, I can see clearly the strategy of UiPath to start from people and to improve them, to augment them, to augment the efficiency. This is totally new, and it's very exciting.

UiPath is bringing into the table a totally new way to automate things. Automation is not something new, but UiPath allows you to automate very easily and without many technical skill requirements. 

I met a lot of customers that didn't have big business processes. Some of our customers are rather small. They have fragmented processes, and they need to automate some tasks. Sometimes they are not big enough to justify the investment of the infrastructure and everything around it.

Attended automation will allow them to target smaller opportunities. This is something which is very appreciated by the customer, to do something small, to grow incrementally. Then you can scale.

Attended automation is definitely something that the customer wanted. I think UiPath understood that. Attended automation was possible before but was reduced and not focused on. 

If you look, even on the academy content of UiPath, there is not much attended content. If you look on the Advanced Training, the Advanced Training is about having back office robots, 

I really looking forward to seeing enterprise grade attended content. I think this will be really something interesting. The feature was existing, but I think now it will explode.

The product itself is relatable. UiPath is a fast growing company. It's incredible how they have grown over time. I remember starting two years ago with UiPath, and it was maybe 400 employees, and now it's very big. The product is stable. They have really improved it. They are very quick on resolving any issue. They are very helped by their community. On the other hand, RPA is not necessarily something easy. You need expertise to do it properly, but UiPath is giving all the resources to make this happen with the Academy, notably, and soon with their academic program.

If today, I'm automating a process in my laptop, I can publish it to the Orchestrator or propagate it in several desktop, for example, in terms of attended automation. We have another way to scale. You might have a process. We developed a robot which will consume transactions, and the UiPath product is scalable because you can have more robots. For example, in accounting closing period. You might need to scale. You might not need all the resources during the month, but at the end of the month, you will need to do the closing for accounting. You can scale for those few days that are critical to your business.

It is a great technologic company, but they are also customer focused. I just drop an email, and during the day, I have an answer and a meeting invitation to help our customer, to help us understand, to show us new features. They always been very exceptional on that. 

If you compare this to coding, this is much easier to get into it. For example, I am today rather technical person, but what if I told you five years ago, I was working in a call center? I discovered that I could automate things with Excel VBA. Today, I know how to code a little bit and i'm using UiPath. I'm automating many companies in the Fortune 1000.

Yes, we have seen ROI. We have seen very big ROI going from one to 10 FTEs even with a very strong solution, with short amount of time. I remember doing a project in Denmark which would be equivalent of about five FTEs in less than a month of development. It is more important to support the solution correctly, to handle change management. You might have saved something, but you need to wait and to maintain the solution. Your customer must not underestimate the cost of the maintenance. RPA is not a silver bullet.

Citrix automation is something complicated. This is something that is a little bit volatile, but UiPath, I think, is one of the best, if not the best in the market to resolve that.

UiPath allowed with database activity to get the SQL to obtain the data directly. Just getting the data we weren analyzing was taking the end user several minutes and 10 seconds for a SQL query to get all the data. Then you can do the checks. This was incredible. Actually, the task was estimated at about 10 minutes, and the robot was doing it in 10 seconds.

I think what makes UiPath so great is not only technology. For me, they have better tech. It's not only about that. The first thing is they are a very open company. They are very open to customers. They have a community version that you can download for free. You can go home and try UiPath yourself. I don't think is as easy to do it with other vendors, other tools.

Most of the competitors did not take the web approach. If you are familiar with the technology, you know you would rather use a web application. Now on my phone, I can go to the Orchestrator and start a job. This is not possible for other competitors as far as I know. 

I would give it nine because perfection does not exist, but they can still try to do it, to reach it.

To increase the efficiency in jobs that people do not like to do.

It takes a very manual, key punch-oriented job and automates it, so the user can do more intelligent work.

It has exceeded my expectations. It took a job which would take a user up to 30 minutes and decreased the time without their interaction to three minutes.

• It is reasonably easy to use.
• The FTE payback benefit.

We would like the RPA app that we developed to fall back to one of our APIs and Visual Studio and have that take off. However, I was talking with one of the guys at the conference, and he says, "It'll do that." 

We don't have a large installation, so I can't really measure this.

We use the online forum to ask questions and review user's questions. It's helpful half the time. We don't have in-house experts. My team has just been learning it for the past three to four months, and they are still hitting a wall in certain areas that they have to dig out of. I am at the UiPath conference looking for any advanced training offerings. 

It was straightforward. It was more building the initial app. I'm a developer on .NET, so it was just getting the experience with UiPath. The biggest challenge was just understanding the small, little 'gotchas' going into certain properties, what was required to make the control work. Overall, we prefer it because of the easy user interface and the open community, where you can get a lot of responses from others.

We have had an app running since July and it has been fine. The company change their websites, so we had to go in and fix the app, because the user changed their site. It wasn't because the app broke or had a bug in it, but the user changed their site, so we had to modify it.

We have two developers inventing and developing.

We're still measuring it, because these were more test apps to get to know the system, so the benefits aren't as large as we can see coming from other development.

It does what we designed it to do. It has worked flawlessly, except when somebody changes the actual website that we are reading.

I would start small. As someone in the conference said, "Don't expect in two weeks you're going to have miracles."

In the beginning, put the time and investment into it and do it right. Once you have one victory, then that's where you start looking to train people in the company on what the benefits are, so you could get ideas flowing in their minds. Stress you are trying to automate the boring, mundane, painful jobs that they wait until the end of the month to do because they don't like doing them. Stress what you are trying to automate, and show that you will automate their whole job.

I work in finance, and we have diverse use cases for UiPath.We use it for invoice processing, ML detection, and tag categorization of items that we sell. 

UiPath Action Center is very valuable. 

We ran into issues during the upgrade. It was not warned before. 

I have been using the solution for five years. 

UiPath is stable. 

The product is scalable. 

We get good resolutions when we raise issues. 

We did on-premise deployment and had to check load balancers, SQL server, and Redis. It took us about eight to nine months to get into production, which was cumbersome. 

We have seen millions of dollars of ROI. 

UiPath is expensive. 

Our business objective in automation implementation was to eliminate manual labor. Initially, we started with RPA. The finance department has a lot of manual work, including prescriptive things like driver's licenses and transcribing. We started using RPA to gain ROI.  

The use of automation has enhanced our accuracy. 

UiPath has helped us save 100,000 hours, which translates to millions of dollars saved. 

I rate the product an eight out of ten.