We just raised a $30M Series A: Read our story
VP
Automation Consultant at a manufacturing company with 10,001+ employees
Consultant
Helpful setup documentation, good data scraping tools, saves time and reduces errors for manual tasks

Pros and Cons

  • "You can scrape data into your tables, then easily transform it or convert it between formats."
  • "The integration with APA should be improved with respect to adding data from external sources and being able to bring in data from third-party applications."

What is our primary use case?

I am an automation consultant and most of the robots that I work on are unattended.

Some of our use cases involve end-to-end automation. One of them is an SAP system where the transaction data, material numbers, and other things are used for T-codes. Based on the value of data in the T-code, it opens other T-codes in the process and updates those registries accordingly. This may include, for example, T-codes one and two. Then, from T-code one, I need to get input with regard to my material numbers. This might be a materials invoice or the invoice numbers of material orders. With those, you have to put it in one T-code and get output.

Based on the output of the T-code one, you need to do the rest of the operations in T-code two and T-code three. Once the job is completed, update all the information about the different T-codes in an Excel sheet and then update it back to the system.

How has it helped my organization?

UiPath saves time both from the perspective of a developer and an end-user. I can talk about the two positions because I have been involved in both roles. On the development side, the features make it very easy and tasks that normally take half an hour can be completed in a minute or two.

With respect to the end-user, assume that a process normally takes an hour a day to complete. Once the automation is in place, the whole process will be done in a minute or two. Importantly, the user does not have to monitor the process because it runs in the back end or on a server in a remote location. The entire process will run without monitoring.

At the same time, the user will be informed. Let's say that you have to get some data out of it; most of the time, the data available every few days. Personally, given that I am not normally in the role of the end-user, I have to log in to all of the systems and look for the data. However, if UiPath is configured and developed properly then it will inform you in an email that the data is now available. Similarly, if there is no data available then it can be configured in such a way that the user will be informed of that. This would give the user the opportunity to save and plan to utilize their time for other purposes.

In our company, we have a lot of use cases where we were able to implement unattended automation. This meant that we saved a lot of time and we were able to reutilize the employees for more useful engagements. 

An additional thing that we are able to achieve through using an RPA like UiPath is a reduction in errors. When we are performing any kind of activity, such as a recalculation in Excel, or calculations in a step-by-step process that involves manually copying data between two places, there is a high chance that an error will occur. This is a human error that can be avoided once we implement the automation and move it to production. Ultimately, all of these types of errors will be eliminated.

It is difficult to estimate the total number of errors that we avoid, but I can say that we were able to save time and with each process, the number of errors is reduced.

What is most valuable?

The most valuable feature is the set of data scraping tools. You can scrape data into your tables, then easily transform it or convert it between formats. If UiPath or another similar automation tool was not there, it would be very difficult to automate something that is a UI- based application. There is no other option to get that back-end data out of it. If we were not able to convert the formatting, or if for whatever reasons we cannot extract the data into a table format, it would be very difficult for us to convert and get the data that we want. The data would be difficult to format and we would spend a lot of time on it.

UiPath provides the data in a table format and in a structured manner, which means that we are able to get the required value from the table and do the necessary calculations on it. It saves us a lot of time in this process.

We have started using the AI functionality but so far, not to any great extent. For example, we were able to identify different types of images while reading an invoice. Prior to using the AI capabilities, we were not able to read them. This is our only use case for AI at the moment, but we plan to explore other activities and possibilities.

We have used the UiPath Academy courses and by doing so, we were able to learn a lot of things. They had examples of use cases that can occur in different scenarios and instead of getting that from a live environment, or during development, we were able to learn it from the Academy and a live example.

With the Studio, we can do basic troubleshooting in the production machine or VM, in case any error occurs. This is helpful because we don't have to move the data back to the development machine.

What needs improvement?

The integration with APA should be improved with respect to adding data from external sources and being able to bring in data from third-party applications. Also, it should be better the other way around, where UiPath is providing APA data to other applications.

For how long have I used the solution?

I have been using UiPath for the past four years.

What do I think about the stability of the solution?

If the application is working fine, without making any updates or changes, then the bot will work as expected about 95% of the time. However, if there are any changes to the end-application made by the developers, or there is a content change, then we definitely have to align to those changes and it will take time.

Generally speaking, we move a process to production once it is stable.

What do I think about the scalability of the solution?

We can easily scale this solution so the scalability is quite good.

We have between 15 and 20 developers in my team who work with UiPath. I am not sure about the number of people on the other teams. In terms of end-users, there are more than 100.

I have developed 30 processes personally, and my team has created more than 200. We plan to continue using UiPath in the future.

How are customer service and technical support?

We have used technical support and the UiPath technical team is good. Whenever there is help required, and we are not able to find the solution for that from the UiPath documentation, we get a ticket with the support team. Based on the criticality of the process, they help us.

Which solution did I use previously and why did I switch?

We did not use another RPA solution prior to UiPath.

How was the initial setup?

The initial setup is straightforward and very easy. The main component is called Orchestrator and then there are two more components called Studio and Development Robot. These two are connected to Orchestrator, and once the development is complete, you can do the unit testing on the same machine. After this, you publish the package.

Once the item is published, it will be pushed to the Orchestrator and then connected to the bot. This is where you're going to run the process. Once it is complete the bot will start running. The whole process will take approximately 10 minutes and you can move the data to production.

When the process is running in production, Studio allows you to troubleshoot from there, without having to move it back to the development machine.

What about the implementation team?

I deployed UiPath on my own. They have provided enough documentation.

What's my experience with pricing, setup cost, and licensing?

The pricing and licensing costs seem okay to me, although it is a little bit on the high side.

In the past, you needed to install the Studio license if you wanted to be able to troubleshoot in production. However, that has changed and you no longer need to buy it separately.

What other advice do I have?

My advice for others who are implementing or using UiPath is to ensure that they test the robots and processes thoroughly before moving them to production.

I would rate this solution an eight out of ten.

Which deployment model are you using for this solution?

On-premises
Disclosure: IT Central Station contacted the reviewer to collect the review and to validate authenticity. The reviewer was referred by the vendor, but the review is not subject to editing or approval by the vendor.
Flag as inappropriate
SD
Sr. Application Automation Analyst
Real User
Top 20
Attended automation enables us to verify scanned fields in our invoices

Pros and Cons

  • "They have also recently added a feature for attended automation, Picture in Picture, which is also nice to have. It's helpful because you don't want to just sit back and let the bot run and not work during that attended automation. Using the PiP feature, you can have it running on your desktop without having to interrupt it to your work."
  • "One area that needs improvement is monitoring. I know there are tools that let us see what a bot is actually doing on the virtual machines. If we could get that kind of offering from UiPath that would be great, because when a bot is running on the machine, we don't know what it's doing."

What is our primary use case?

We primarily use it to reduce manual effort and to increase accuracy and on-time implementation. We perform end-to-end automation, since we are a company where SAP is used very widely. We use UiPath for SAP automation.

We develop both attended and unattended solutions. We're using the platform as a service and it's hosted on-premises.

How has it helped my organization?

So far, we have 15 bots in production. As a result, we are saving a lot of time, although I don't have a figure right now, as well as a lot of effort. We are also able to provide timely delivery to our customers, so the automations have been generating a lot of buzz here.

Attended automation has helped to scale RPA in our organization by automating processes that require human-robot collaboration. An example is our invoices that have data that needs to be scanned. The scans we were receiving did not have the accuracy that we were looking for. We also had a hard time getting the results through OCR. With the help of attended automation, we are able to have users verify data when the bot is running. Once the verification is done, the bot will perform the rest of the actions.

UiPath also definitely helps us with process analysis.

What is most valuable?

Although I have not used it yet, they have recently introduced a feature which brings more accuracy to the selectors, using the image and the selectors themselves. I feel that will be good. When we are creating selectors, there are elements that it's hard to get at, or there are times when the selectors get changed for some reason. The new feature should make it easier to work with in these situations.

They have also recently added a feature for attended automation, Picture in Picture, which is also nice to have. It's helpful because you don't want to just sit back and let the bot run and not work during that attended automation. Using the PiP feature, you can have it running on your desktop without having to interrupt it to your work.

I would also compliment them on the UiPath Academy, the learning platform that they have built. It contains everything that a developer or architect or tester or, anyone who is looking to benefit from an RPA, would need. It's all there on their platform. It helps speed up onboarding employees to UiPath. When I joined this company, I had prior experience with the RPA and UiPath. But two of my colleagues, who were working on test automation, didn't have that kind of experience. The Academy helped them to get started. We aligned quickly, once their fundamental developer training was done through the Academy. The Academy helped them align with the current practices of UiPath and RPA.

What needs improvement?

One area that needs improvement is monitoring. I know there are tools that let us see what a bot is actually doing on the virtual machines. If we could get that kind of offering from UiPath that would be great, because when a bot is running on the machine, we don't know what it's doing. Although we have programmed it, there are times when something causes a bot to fail. During such instances, the bot behaves differently when we run it in attended mode than it does in unattended mode. It would be great to have a feature where we could see, on a screen, what the bot is currently doing.

For how long have I used the solution?

We started this UiPath journey two years back. 

I act as a UiPath lead because I joined early and I have some prior experience with it. There are three other people in India, and one more in the U.S, who use it in our company. The one in the U.S. does the managerial stuff and it's the developers who are in India. Then we have the business users for each of the bots and they also use UiPath. And we have a set of about 20 users who use the attended solution that we have provided to them.

What do I think about the stability of the solution?

Robots on the SAP system seem stable, but on the web they sometimes lack stability. Still, it's not a very common occurrence and I have overcome any issues with the help of the Trilogic. For example, we had an issue while getting an email from Outlook. A UiPath robot is not able to do that. It will time out. With the help of the Trilogic, we were able to overcome that.

Initially you have to put some effort in to obtain stability and then it is mostly stable. Some maintenance is required, but that's most probably when requirements change, or to add to the stability, but it's not a lot overhead right now for us.

What do I think about the scalability of the solution?

It's highly scalable, in both development terms as well as business terms. We have the capability to add on robots. We can add to the VDI or machine anytime we want. They have put some serious thought into the scalability, when it comes to giving support to developers as well as the business.

We plan to increase our usage of UiPath. We have a lot of things in the pipeline. We have almost finalized on providing RPA as a service, something that we will offer internally. Right now, we are giving this free of cost to our customers who are the business people. We did so to get some attention and to create some interest in the tool. Now that we have almost finalized this as a service, we are going to involve business analysts who will be helping us to find more RPA use cases and finalize more RPA solutions. That means our usage will increase. We're still in an early phase.

How are customer service and technical support?

I haven't had the chance to interact much with the technical support because the forum has so much information. If I browse through the forum, I will most probably get an answer. So I haven't needed to go to the technical support for any answers.

Which solution did I use previously and why did I switch?

We have both test automation and UiPath working in parallel. Test automation has been here for the long-term, something like 10 or 15 years. The two guys who work with me, who didn't have prior UIPath experience, are working on that. That part mostly requires maintenance, and they now mostly work on UiPath development. So although we had a test automation solution, we didn't have a business automation solution. That is why we went with UiPath. It gives us an edge in business automation.

How was the initial setup?

The initial setup of UiPath was pretty straightforward. I didn't find anything unusual or complex.

We went through an upgrade recently. We have dedicated cloud architects who helped us do it. We got instructions how to do it from UiPath support and we conveyed those instructions to our cloud architects and they performed it at their end to get UiPath cloud upgraded. Upgrading didn't take much time. It was done within half an hour.

What's my experience with pricing, setup cost, and licensing?

One more feature that is useful is that earlier, we didn't have the option for a concurrent-user license. With the help of the concurrent-user license, we can save on licensing costs while running multiple bots under the same license.

What other advice do I have?

If you are going to implement UiPath, my advice would be to look at how you are going to gather the requirements and how you're going to manage the requests for UiPath. 

Also, get some low-hanging fruit first, before going into the complex automations. That way, if you are new, the low-hanging fruits will generate confidence in the solution. Once that kind of confidence is generated, you can move ahead with the complex automations and complex solutions.

Go through the UiPath Academy extensively. They provide good training materials that I don't believe are available elsewhere. So I really recommend that. I recently attended a dev conference and I learned a lot about this stuff. I work in a closed environment where I don't have much of an idea of what's going on in RPA. This conference helped me keep in touch with the current trends in RPA and UiPath.

I rate UiPath at eight out of 10. For me, that's a very good mark. The two missing points are because there is scope for improvement. Overall, I'm pretty happy with UiPath.

Disclosure: IT Central Station contacted the reviewer to collect the review and to validate authenticity. The reviewer was referred by the vendor, but the review is not subject to editing or approval by the vendor.
Flag as inappropriate
Learn what your peers think about UiPath. Get advice and tips from experienced pros sharing their opinions. Updated: October 2021.
542,721 professionals have used our research since 2012.
Jason Gerber
Executive Vice President at The Medcor Group, Inc.
Real User
Easy to build automations, offers great accuracy, and is very scalable

Pros and Cons

  • "We’ve improved our efficiency in a way for sure. Even just our cost analysis has improved. When we do new contracts, we know what it's going to cost exactly."
  • "I don't know if it's UiPath as much as just what we do is really complicated. Even the consultants that we've used with UiPath, even they've said, wow, this is very difficult what you guys do. There are a lot of moving parts, so it's not as much of a UiPath problem in terms of limitations. It's just our own processes."

What is our primary use case?

We're a revenue cycle management company for medical billing. We've reallocated our charge entry employees. We're using bots now to do the charge entry on medical claims and then also payment posting along with eligibility and AR. We've been able to reallocate about, just within this last year, probably eight employees. They've been reassigned to more valuable work - things that the bot can't do and actually requires a human to do. We've been understaffed, so it's actually worked out great for our company.

What is most valuable?

The ease of building automation isn't a problem. It seems to be very easy to do to a point. Our challenge is we work in a live environment. We're not able to use a test environment when we build things out. We have to go very slowly.

I'm not that familiar with the product, with the solution, however, the UiPath apps feature and OCR are great. That said, we're not using any of the apps currently.

The biggest benefit we've seen is the accuracy. Even just with employees calling in sick or not having enough staff. We’ve been able to fill those roles.

The robotics piece has been a huge thing. We're doing medical claims. We're always worried about claims not getting paid. This has been able to capture those claims so that people get paid the first time. One of the other things we track is how many times we touch a claim. For example, how many clicks. We couldn't do that before. That's been very valuable to us.

We’ve improved our efficiency in a way for sure. Even just our cost analysis has improved. When we do new contracts, we know what it's going to cost exactly.

What needs improvement?

I don't know if it's UiPath as much as just what we do is really complicated. Even the consultants that we've used with UiPath, even they've said, wow, this is very difficult what you guys do. There are a lot of moving parts, so it's not as much of a UiPath problem in terms of limitations. It's just our own processes.

Right now, I don't think I've been on there long enough to know if there are missing features or functionalities I’d like to be added.

I’m talking to people right now, to see how it can do things better or how we could use it more effectively. We’d like to discover what worked for other people.

For how long have I used the solution?

We've been using UiPath for about maybe a year and a half tops.

What do I think about the stability of the solution?

I haven't had any problems or concerns right now concerning stability. The biggest concern I do have is that we've already invested six people in this. We're going to have a lot more that will, more or less, not have the robotic piece as part of their job. That work will be reallocated. I have about a hundred employees that UiPath could technically reallocate.

When I look at that, I worry about if something does happen or it doesn't work or there's no backup. Then, suddenly, I don't have employees. Right now, we can jump in and some humans can do the work if necessary. My concern is that in the future they won't exist. This hasn't happened yet. I hope it doesn't.

What do I think about the scalability of the solution?

Scalability hasn't been a problem at all. We can just continue to add bots every time we need them. It's been easy.

We started with two. Three months later, we added another two. After another three months, we add another two. From our standpoint, it's great. My UiPath rep was shocked that I keep adding more, so that's good.

How are customer service and support?

I have not used technical support.

That said, we had one issue with UiPath where something didn't work. We talked to them and it was taken care of within a couple of days.

My vendor is working with them. They mentioned there was an issue with insights that they are working through. Insights are still not quite functional, or there are some resources we need. However, the vendor is dealing with it directly. It's a work in progress. 

Which solution did I use previously and why did I switch?

We did not previously use a different RPA solution. 

How was the initial setup?

The initial setup was pretty easy. We didn't have any challenges with that. I contacted one of our vendors and they ran with it. We didn't have issues at all.

With the vendor, it took us about 30 days to deploy UiPath. After that, in terms of implementing bots, the first bot took us about three months. Once we did the first one, it just went really quick after that. We could reuse some processes which made it faster. There was a lot of reusing of the same. We were also internally understanding what information they need and how it works.

It was all new to us. I'm still learning the acronyms they use. We need to learn what they are talking about. We’re not IT-based at all. It's definitely different.

What about the implementation team?

We had the solution implemented by a vendor. They implemented it all. We didn't have any challenges as far as that goes.

Our experience with the integrator was good. I would say that they didn't realize how challenging it was going to be or, at least, the person who integrated didn’t. At the same time, they know almost everything about my business now.

What was our ROI?

UiPath has saved costs for our organization. For example, we’ve allocated six employees that are paid around $40,000 a year and we've implemented six bots to do those same functions and they're around $8,000 a year. In a way, we’ve doubled our staff, and almost tripled our ROI.

What's my experience with pricing, setup cost, and licensing?

We had a problem before with the pricing, however, for the most part, it's fine where it is now. My ROI is fine. It works great. I have zero complaints.

You have to do a package at a time. That's my only challenge, where sometimes I don't need that many licenses. 

When you first sign up, it's a package that can renew every five years. I don't necessarily need everything. I'd prefer just to pay for certain pieces. 

Which other solutions did I evaluate?

We did not evaluate any other options. We started using UiPath due to a referral at a neurological healthcare conference about four years ago. The speaker suggested UiPath. I actually didn't know of any other company until after we were on UiPath. We've since talked to others who have used other solutions and they mentioned that we made the right choice when we chose UiPath.

What other advice do I have?

We started on-premise for the first six months and then we actually moved to the cloud.

We do not use their UiPath apps feature as of right now.

We are mostly using unattended automation.

We haven't really calculated the reduction in human error. We're just moving on to our Insights app. We're just getting ready to launch that, so we're not there yet. We don't know what that turnaround will be.

We do not use UiPath's AI functionality in our automation program right now.

Our teams have not yet used the UiPath Academy courses.

I'm a little concerned about having to bring on more people that are not in this industry. We're going to have to start them over from the ground up, which takes time.

When we first started, we wanted to know if it really worked. We got a certain budget and just started using it, and now I can say that yes, it does work. We can see that now that we've stepped back. We should have done it earlier. That's what I would tell people. I would definitely tell people to look at it first, before anything else. 

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

Which deployment model are you using for this solution?

Public Cloud
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Flag as inappropriate
CO
RPA Manager at a government with 10,001+ employees
Real User
Recording tools enable the capture of user actions on the screen and then the recordings can be converted into workflow sequences

What is our primary use case?

Our primary use for this product is to automate processes that we are capable of automating at our tier-one level human resources center.

How has it helped my organization?

This product has improved the way the organization functions by helping us go through a digital transformation. RPA is able to bridge a lot of the gaps that we had in our processes and processing what we had before we moved to this platform as a solution. With a little effort, I was able to bridge those gaps and automate a lot of processes that were manual and less efficient prior to involving the product.

What is most valuable?

The most valuable features for us are the recording tools. They allow the capture of user actions on the screen and then the recordings can be converted into workflow sequences. The activities are very simple to use and easy to put together in order to automate the processes. Once we get Orchestrator, that feature will probably be the most valuable, but we are currently not able to put it into production.

What needs improvement?

As far as additional features, there doesn't seem to be anything outstanding that I can think of right now. Maybe some off-the-shelf "How To" features could be installed with Studio so that you can search for how to do something and pull it up directly in the Academy or on-screen without leaving the product.

There could be room for improvement in the ticketing feature. It's kind of hard to find that feature sometimes.

What do I think about the stability of the solution?

On a scale from one to five, where one is the least stable and five is the most stable, I would rate the stability of UiPath as a five. It is very stable. We have never had any issues with regards to UiPath. The actual problems seem to be network issues and our environment.

What do I think about the scalability of the solution?

We started out sort of small in the beginning and we've invested more in buying licenses and functionality. The scalability in that way seems very good.

How are customer service and technical support?

My experience with customer service has been very good. They make a few different types of resources available and it is usually pretty easy to find what you are looking for. For example, I have used the RPA Academy. It is pretty easy and it was very beneficial. I haven't really opted for using customer support or technical support much. I've been able to just call, text, or email somebody and get a solution.

Which solution did I use previously and why did I switch?

There were really no automated processes when I first came on to work at this organization. When we made the decision to go in this direction, we made a comparison of products to solve the automation issue. What made us choose UiPath to automate our processes was price, availability, ease of use and customer services. They were also willing to be the quickest to work with us as well. It seemed to be the best mix of all these.

We knew we needed to invest in a new solution because, where I'm working, we had 600 or 700 processes that I knew could benefit from automation. As an industry and in total, we probably have thousands of processes that could benefit from and be improved by automation. Coming into the company and seeing how things were done just made it obvious that automation was missing but necessary. Government processes need to be automated to be more efficient because of the volume and the potential for human error.

How was the initial setup?

I would describe our initial setup as complicated because of our industry. We never worked with software like this prior to implementing UiPath. Just to get permissions to use the product on our network was one obstacle. It wasn't always easy to get to ATO (Authority to Operate) and get the capabilities and rights to do certain things on the network like to have the product interact with certain programs that have sensitive information. It's kind of complicated, but that is a whole new path within our industry whenever introducing new technology.

From the time of purchase of the UiPath license until adding our first robot in production was a few months. We purchased a license in February and got a robot into production in May. Most of that time spent was because working on the project is not even my full-time job. I have a whole different responsibility in the organization. So, I was doing a lot of developing in my free time. It probably would have only taken a month or so if I was doing it full time.

What about the implementation team?

We did not use an integrator, reseller or consultant. I did everything in-house.

What was our ROI?

We have seen a return on investment and performance benefits. The ability to notice a difference was almost immediate for certain things and in certain programs. I know that I've calculated that we saved $1.47 million through the automation we have already set in place. The solution also helped eliminate human errors which are more difficult to approximate as a dollar value or percentage.

Basically, using the product has allowed us to take between four to six full-time employees from doing very mundane transactional processes to doing more value-added work. That shift alone reduces human error because the human mind is not made to do this kind of transactional work over hours and days at a time.

This solution saves our organization time on an ongoing basis. I would say it saves a minute to three minutes per transaction per thousands of transactions. It certainly has value in more than one way.

What's my experience with pricing, setup cost, and licensing?

We license the use of the product on a yearly basis. The licensing we bought costs $7000 in 2019 for what we have in production. That is the cost of the license plus Studio.

From a cost perspective, I believe that unattended robots can save even more time and more money than attended robots. The only reason we haven't gotten unattended processes into production yet is simply that we haven't got the authority to operate Orchestrator on our network server. The cost is not an issue given our budget, we need to be able to justify how secure it is.

Which other solutions did I evaluate?

The vendors who were on our shortlist were UiPath, Automation Anywhere and Blue Prism. All of them seemed to be good solutions.

What other advice do I have?

We are currently running some of our automation in a virtual environment. The implementation performance is all right. Our system environments are pretty out of date and a bit technologically behind. Sometimes that fact will hold things up. I am the only one in the organization involved in the automation program. I'm the only developer and the only person who uses UiPath directly, but it affects thousands or even tens of thousands of people.

On a scale from one to five, one being the most difficult and five being the easiest, I would rate the ease of use of the platform as a five. Personally, I had no developer experience. I never heard of RPAs or UiPath a year ago. I was able to learn it and figure it out using the Academy, YouTube and the forum. Coming to it cold and doing it part-time, that really doesn't seem like a long time.

On a scale from one to ten, where one is the worst and ten is the best, I would rate this product as a ten overall. It has been completely helpful in achieving the goals we set for it and the technical help and customer service I've gotten have been good. Most of the issues we have encountered with the product are because of the way we operate and not because of UiPath. The support from UiPath provided everything we have ever asked for and needed.

The advice I would give to a colleague at another company who is researching this or a similar automation solution is to just do it. It really creates the opportunity to make things more efficient.

Which deployment model are you using for this solution?

On-premises
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Nathan Boeke
Principal Robotic Configuration Specialist at Allianz life
Real User
Studio saves the QA team a lot of time setting up separate environments, test data, etc.

What is our primary use case?

We use UiPath Studio, Orchestrator and Robots, all unattended currently. Our primary use case is one-off for mediation projects because we're trying to set up our infrastructure. Once the infrastructure is set up, we plan on creating a federated model throughout our entire organization.

How has it helped my organization?

Right now, our remediation teams do a lot of large one-time projects where they have to have policies for scaling up and scaling down the volume of full-time employees. I know we have avoided that situation in at least three cases now where they have not had to hire or remove people because they have been able to automate the remediation process.

What is most valuable?

The most valuable features for me in Studio can be anything that helps me test or debug. It saves me a lot of time and it saves our QA team a lot of time setting up separate environments, test data, and things like that.

The most valuable thing in Orchestrator is just how easy it is and the fact that it's cloud-based. It is also useful in that it allows non-technical users to get information about their projects. For example, they can find out if independent components are up and functioning; if something is down they can find out what went wrong.

What needs improvement?

In the next release of the solution, my biggest hope would be getting more accessibility to test data processing information. I was told that this feature was coming already. Being able to see what my variables and my arguments look like when things are being passed and making the processes very clear to my customers when we are doing test cases for UAT (User Acceptance Testing). That would be invaluable. It would help the customer to see and understand the data flow more easily without having to go through training or being very tech-savvy.

I think Studio has a little more room for improvement and could use a few more features. They just announced Studio X and Studio 2 which actually addressed many of the issues I hope to see resolved, but that is assuming that they come through in development and do what they say they are going to do.

What do I think about the stability of the solution?

On a scale from one to five, where one is not stable and five is very stable, I would rate the stability of the UiPath platform as a four-and-a-half. I've only seen one or two buggy behaviors, so I think that qualifies as extremely stable.

What do I think about the scalability of the solution?

In our organization, there are five full-time people involved in the automation program. We can drag people in from different departments in the business on a case-by-case basis when necessary for resolving issues with automating.

How are customer service and technical support?

Before we started, all of us were involved in using UiPath Academy RPA training and learning through it. On a scale from one to five where one is the least beneficial and five is the most, the Academy is something I would give a three. I say that because I don't think they went into enough detail. I understand that they didn't because they are trying to save time for non-technical people, but I love knowing everything and I would love to see more detail in their presentations or have options to do so.

Customer support overall is very responsive and they say a lot of helpful things, but I'm often able to find the same information and answers on the forums. It would be nice at times to be able to talk to someone from support over the phone. I can describe my problems without having to send dozens of emails back and forth in order to get an answer. It just isn't terribly efficient.

Which solution did I use previously and why did I switch?

The decision to automate and the product selection for the solution were completed before I was brought on as part of the team. I was actually brought on as an expert from another company in order to help them stabilize their deployment. The product vendors which were on the short-list actually include some vendors which the company has licenses for in addition to UiPath, like Blue Prism. They are exploring multiple options because we are a global entity. They want to offer the option to entities to choose whatever partner they prefer to go with.

How was the initial setup?

The approach to the initial setup which was selected was a complicated process. I don't know much more than it took a long time, it wasn't very successful and that's why they brought me on.

What about the implementation team?

They did the entire implementation in-house.

What was our ROI?

We have seen some return on investment to a certain extent, but a lot of it's coming from one-time processes and not from recurring processes. In other words, the ROI is already there, but it is from one-time processes we've deployed. These are processes that we would run a bunch of items through one time and the circumstances are not repeatable the next year or even the next week.

I'm not sure about the exact numbers, but I know that the cost of our department has been saved roughly four times over. Again, a lot of those savings are from one-time events that won't be recurring in the following year so they can't really be seen as predicting the future results.

The solution has helped to eliminate human errors in some cases and that also has value. In addition, there is the benefit of saving the employees time. Right now I believe that we have approximated that we saved somewhere between 40,000 and 45,000 human hours. That resource can be re-allocated.

What other advice do I have?

Part of our deployment is in a virtual environment and part of it is not. The implementation is actually still in progress. We are in the phase of setting up our infrastructure and trying to automate some POCs (Proof of Concepts) and some early successes to show the financial benefits of RPA to the C-suite (C-level executives such as the CEO and CFO).

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 as a four. I think the product is fairly intuitive. Because I come from a tech background though, I feel like it is going to be a little easier for me to understand than some other people who don't have that same background. The only reason I don't give it a five is because the integration between Orchestrator, Robots, and Studio does require a little bit of intimate knowledge to be able to connect them all and make sure that they stay connected.

We have not used attended robots yet, so I'm not sure how cost-effective they are because we don't have any data on that. We use unattended bots and they seem to be effective solutions, but I don't know what they pay for them.

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. The only reason I'm not going to give it a ten is that I have struggled with certain errors and stability issues. Whether that is our fault or a general bug in the actual software is yet to be seen. I have a few open tickets, but I've really liked this software overall.

Advice that I would give to a colleague at another company researching this or similar solutions would be that they look at their organization and see if they are really ready for deploying RPA solutions. A lot of RPA solutions are sold with the promise that anyone can build solutions with the products and the bots are going to deploy quickly. I don't think quick deployment is deceiving, but I do think that trying to implement a solution that does move so quickly like this into an organization that doesn't move quickly can create friction.

Which deployment model are you using for this solution?

On-premises
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Adrian Iordache
Principal Solicitor at Consortium Legal
Real User
Top 20
If a human had to do what this robot does it would be impossible; the digital transformation is quite dramatic

Pros and Cons

  • "Regarding the ease of building automations, I'm not sure how it's done because I'm not a programmer myself, but it's great. Just looking at how fast they moved once we had the program settled in — it was quite fast. For this particular process, which is assembling a document, talking to DocuSign, sending out emails, and so on, the deployment of production was like "today." It was quite quick."
  • "I could use more standardized features, retail-style, things that I could use off-the-shelf. Right now, all this requires quite a bit of adaptation in bespoke work with UiPath, which they've done very well. But looking at it after having used it, I would get stuff that is prepackaged from them, if they were any."

What is our primary use case?

We have developed a product for a court of arbitration. UiPath provides the automation engine behind it. Our product is a platform that is live online. It allows a party to provide some contract information, and the robot assembles a document and communicates with DocuSign, our signature provider. It then sends out a correspondence to the other party and manages the signature process for a bespoke contract for an arbitration agreement.

This is a service that we provide to the world, pro bono, as it were, to promote arbitration and the adoption of a particular arbitration clause. It's accessible to all. Parties can log in and it helps them to negotiate and conclude an arbitration agreement in a mediated fashion. The robot sends out email on behalf of a third-party, a court of arbitration, and it helps the parties get that agreement done.

It's about concluding an arbitration agreement before the dispute goes any further.

How has it helped my organization?

It helps us in providing added value to the clients and to the community at large. It's a marketing thing for us, in the widest possible sense, rather than something that we use in our practice.

But in terms of reducing the cost of digital transformation, if a person had to do what the robot does, it would probably be impossible. It would be impossibly costly. If one person had to handle the communication, instead of the robot, and try to negotiate each addendum, nobody would do it because it would take days or weeks for a lawyer to manage, and it would be prohibitive. Yet, all of a sudden, we have this service that is so cheap in many ways that it can even be provided for nominal user fees. It's quite dramatic.

I would also imagine that processing time is reduced by many orders of magnitude. As a professional, if I had to manage an addendum like that, it would take me weeks. And it takes about seven minutes or so, if all goes well.

What is most valuable?

What I have found interesting is that our product acts as a human would but it's not intrusive. It doesn't require any real integration or interface with one's own systems, in any meaningful way. Obviously, you need access, an account to log in, but it otherwise acts as a human, and that makes deployment quite smooth. It doesn't require you to change anything in your system. I found that very useful.

Regarding the ease of building automations, I'm not sure how it's done because I'm not a programmer myself, but it's great. Just looking at how fast they moved once we had the program settled in — it was quite fast. For this particular process, which is assembling a document, talking to DocuSign, sending out emails, and so on, the deployment of production was like "today." It was quite quick.

In terms of the ease of management of automations using UiPath, I don't dare poke into it, as a non-technical person, but it looks manageable. I have someone who does not do RPA normally, who doesn't do this type of programming at all, but that person knows where to look for errors and doesn't get lost. It's reasonably accessible.

What needs improvement?

I could use more standardized features, retail-style, things that I could use off-the-shelf. Right now, all this requires quite a bit of adaptation in bespoke work with UiPath, which they've done very well. But looking at it after having used it, I would get stuff that is prepackaged from them, if they were any.

For how long have I used the solution?

We launched with UiPath in June.

What do I think about the stability of the solution?

The stability of the solution is okay. 

The downside of the upside, when I said that it works like a human, is that in some cases, if it interacts with a website that is changing, then it's like a human. You need to adapt it to the changing environment in which it works. That's an inevitable fact of life, that it interacts with other apps. It can also interact through APIs, but you want it to be very flexible, you want it to be an agent, like a human. The downside of that is that if something changes with a website, then of course, you have to change the robot and tweak it a little bit. But that's the only issue that has required our attention so far.

What do I think about the scalability of the solution?

Our product is a public-facing instrument and we have had no problem with the number of users, so we have not seen any issues with scalability.

In terms of potentially increasing our use of UiPath, we're exploring a number of solutions actually, for practice management and actual lawyer work. These would be in-house solutions, rather than public-facing. We have a few ideas that we have run by them and we are waiting for feedback.

How are customer service and technical support?

We've had no problem with the customer support. We were in direct contact with the whole team. They have always been quick to respond. I would rate them a 10 out of 10.

Which solution did I use previously and why did I switch?

We would use regular Microsoft automation features. I would have a flag on a particular correspondence, or a particular rule for attachments. We would use little bits and bobs of automation that are available, but we did not have any bespoke solution.

We went with UiPath because they made themselves known in the sector and it was a question of the vision that they communicated. There was a modest vision of providing solutions to very discrete problems, not revolutionary solutions to everything. Rather, they focused on whatever helps in a particular organization. We liked that. It matched our understanding of legal tech as well. It needs to be supportive of whatever little bit of help you need, rather than providing you with an environment that engulfs you with everything. We liked that approach, and when we approached them they were very receptive.

How was the initial setup?

The initial setup process was okay. I'm a non-technical person, but I was able to manage it. 

It took quite a bit to figure out what we wanted from it, the flow and the logic of it. After we agreed on that, on the concept, actual production took two or three days. Of course, somebody had already done a proof of concept, although that was not based on a final brief. We danced around and changed it a bit.

For maintenance, we have somebody in tech that we pop questions to, and our maintenance of the server is done in-house as well.

What was our ROI?

We have realized return on our investment. It was a joint project with UiPath so we had special arrangements in terms of licensing, but it was very well received in the market. It was very beneficial for us.

Our product is something that we launched in June, and the robot has been featured in general business publications, in the Kluwer Arbitration Blog, and the Resolver, which is the Chartered Institute of Arbitrators magazine, as well as the Romanian Arbitration Journal. Essentially, everybody knows about it. It is one of the most popular UiPath robots out there; the most featured and interviewed robot in the wild. We were quite pleased with the publicity.

What other advice do I have?

My advice is to think about it very carefully and know exactly what everybody is doing every day in the office, the little bits and pieces. Really look at that seriously, because there are so many things that we do in a software environment that are very amenable to automation, and it saves a lot of time. Think very carefully about the particular needs of your office and look into it, because it can save you a lot of money.

It's clear that this is the future.

Which deployment model are you using for this solution?

On-premises
Disclosure: IT Central Station contacted the reviewer to collect the review and to validate authenticity. The reviewer was referred by the vendor, but the review is not subject to editing or approval by the vendor.
MB
Product Manager at a financial services firm with 201-500 employees
Real User
Saves the organization time, and enables the reallocation of resources but reporting needs more development

Pros and Cons

  • "Customer support is a bright spot and helps give users confidence in the solution."
  • "We are having some on-going stability issues."

What is our primary use case?

We use Studio, Orchestrator, Studio and Orchestrator right now for RPA development for automating pretty much anything that rules-based processes can accomplish that are mundane and take time. 

How has it helped my organization?

UiPath has improved our organization simply through the ability to automate. Creating rules-based processes and making them automated can allow us to make better use of people's time. Now people are not working weekends and overtime. People are working their regular hours and doing their regular jobs.

What is most valuable?

I would say the most valuable feature in the solution is Orchestrator in conjunction with the customer service piece which is also very valuable. The ability to troubleshoot whether it is infrastructure support or a development support issue, having somebody to reach out and provide feedback is very beneficial.

What needs improvement?

One additional feature that I would like to see included in the next release of this solution — and actually looking forward to — is more development in the reporting. The Insight piece that was announced was very good to hear about. We are excited about that and looking forward to it just so we do not have to develop our own reporting infrastructure. Instead, we can leverage UiPath's Insight platform to do reporting, deliver reports, measure production errors, and further simplify how we gather and assess information. As far as room for improvement, I would say that is my biggest missing piece.

What do I think about the stability of the solution?

On a scale from one to five where one is not stable and five is very stable, I would rate the stability of UiPath platform as a three. Right now, we are having some connectivity issues, between Orchestrator and our environment. We have been working with our infrastructure support team and UiPath infrastructure report team to figure out what's going on. We are working through the issues and I'm very impressed with the support that we have been given, but we have got to figure out what the issues are and solve them.

What do I think about the scalability of the solution?

We have approximately 15 people in our organization involved in the automation program and I don't think it would be difficult to scale that usage up.

How are customer service and technical support?

I would say that overall I'm very pleased with the customer and technical support from UiPath. They have been very responsive. If there is any need or if there is an issue, they are good at getting to work on finding a solution. They also provide additional resources.

Our team used UiPath Academy's RPA training and on a scale from one to five, where one is the least beneficial and five is the best, I would say the training is probably a four-out-of-five. The feedback that I've gotten from others that attended is that it is very informative and they are good training courses. The tests are challenging enough that it makes participants involved so that they are prepared for the next course. So mostly the RPA training is a positive experience.

Which solution did I use previously and why did I switch?

We did previously use a different solution, but it was a proprietary vendor solution — one of our servicing vendors created it. They were not able to deliver solutions of service packs within an expected timeline. We had to identify different short-term and long-term needs and decided to invest in a new solution. We had to identify a way to bridge some of those gaps in the interim until we could get those upgrades on that platform.

We ended up choosing UiPath automated processes on the recommendation of Accelerate who we were using as a consultant.

How was the initial setup?

I would say the initial setup was straightforward and it wasn't too complicated. From the time we purchased the UiPath license until our first bot introduction I think it was only about two months. The installation itself was easy too. We were able to install it on-premises, get all the licenses running, get all our basic needs set up so we could do development, and put a bot into production. It was not a long onboarding process before we started seeing results. 

What about the implementation team?

We did use the assistance of a consultant for the deployment. That would be Accelerate. Our experience with them was okay. On a scale from one through five I would say they scored a three-out-of-five. The delivery was not quite what we expected and did not meet our timeline. We set out with a goal and we fell short of that goal, and we're working with them to help us have a good forward-thinking plan. Delivery was not fully met, so we weren't too happy with that. But otherwise, they were right there.

What was our ROI?

We have seen a return on investment and some performance benefits. For example, we were able to pretty much completely automate one process that had two FTEs (Full-time Employees) who were spending 40 hours a week completing a process. Using UiPath we were able to almost completely automate that process and bring that workload down to 10%. So now the bot does 90% of the work and they just handle Excel. 

I think I could say we'll save approximately $400,000. Somewhere around there. But it isn't just financial savings. The solution helps to eliminate human errors, saves the organization time, and allows the reallocation of resources. I would say, based on the use cases that we have, we have saved roughly 60% of our effort on automated processes. So the users are now managing business exceptions that they may have and are handling things on a higher level.

Which other solutions did I evaluate?

I don't know if we had additional options on a shortlist because I wasn't involved in that part of the selection process. I was brought in a little bit later. But there are obviously a host of different vendors that have different solutions that Accelerate would have been aware of. We went through a vetting process and identified Accelerate as our number one choice as a consultant. From there, UiPath was the vendor they suggested, so that's how we got connected with UiPath.

What other advice do I have?

We run our automation in a virtual environment. The implementation is good. We are having a few issues. I don't know if it's directly related to the virtual environment, but we are having some connectivity problems which affect stability. Otherwise, we're good.

On a scale from one to five where one is very difficult and five is easy, I would rate the ease of use as a four. It is a four and not a five for the simple fact that the product does not really achieve the level of simplicity I expect. I'm not a technical person. Most non-technical people can — if you're kind of familiar with the different workflow options and sequences — go in and develop some things you need to accomplish for automation with this tool. I would say that for more complicated pieces, you need a more technical background. The focus on making it easy for non-technical users is very important and they could do a better job of it in my opinion.

On a scale from one to ten, where one is the worst and ten is the best, I would rate this product at probably a seven out of ten. That leaves a lot of areas for improvement. On the other hand, I'm pretty pleased with the product and what UiPath has delivered.

The advice I would to a colleague at another company who is researching this solution is that with UiPath, customer support is a driver. Anybody can deliver a product, but it's what kind of system or service you provide to back it up that can matter as much or more. My experience has been great with UiPath and their ability to provide excellent support matters a great deal to my customer experience.

Which deployment model are you using for this solution?

On-premises
Disclosure: I am a real user, and this review is based on my own experience and opinions.
LR
Managing Associate at a legal firm with 51-200 employees
Real User
Top 20
Reduced our time to process information, allowing us to offer our services on a larger scale

Pros and Cons

  • "It enables us to provide new services, e.g., our use case is something that we could not have delivered manually. Now that we use the robot, it is something that we can offer to clients. Therefore, it has helped us expand our scope of services and offer to clients more competitive fees."
  • "The pricing for Orchestrator and unattended robots could use improvement. If we plan to roll out and implement more robots, then perhaps lower costs on Orchestrator and unattended robots would make adoption even easier."

What is our primary use case?

We use it to automate searches in public databases. We have lawyers who need to search for various companies. For example, we are searching insolvency files for a list of business partners, so we use the robot to perform the search and notify clients about its results. Thus, it helps us with our work in searching public registries.

We have the Studio license and attended robots.

How has it helped my organization?

It enables us to provide new services, e.g., our use case is something that we could not have delivered manually. Now that we use the robot, it is something that we can offer to clients. Therefore, it has helped us expand our scope of services and offer to clients more competitive fees. We are now trying to get more clients.

If we were to do this manually, it would take us one day for 200 companies. Now, it takes about half an hour. So, it has reduced our time to process information. Before, we didn't offer these services on a mass scale. We just often did it for a couple of companies. Now, we can offer it on a larger scale.

One of the departments in our organization does use UiPath for compliance purposes: To send reminders to our clients. We have to ensure that clients are compliant when they submit financial statements. We use the robot to send them reminders to update the steps of compliance, i.e., if it's done. This is not my team, but another team who uses it for compliance purposes. It has increased their level of compliance because it's timely and there are no errors in the reminders.

What is most valuable?

We mostly value the fact that it easily interacts with existing systems. We don't have to go to a complex interface to access public information to send the emails, etc. This is the good part.

Its ease of management is okay. Our attended robots have some Excel files that we use to manage and configure the robots. It is quite straightforward.

It has helped relieve the legal staff of the burdensome task of searching on the public registry. For them, this has been a big improvement. It saves time and also the risk of human error has been reduced, because now the robot does the work. So, you don't get bored when you check 2,000 companies on the portal. The staff is overall more satisfied because they can do more value-added tasks than performing this search.

What needs improvement?

The pricing for Orchestrator and unattended robots could use improvement. If we plan to roll out and implement more robots, then perhaps lower costs on Orchestrator and unattended robots would make adoption even easier. 

For how long have I used the solution?

For roughly a year and a half.

What do I think about the stability of the solution?

So far, the stability has been good. We haven't had any issues.

What do I think about the scalability of the solution?

If you have an attended robot, then it is scalable to a certain extent, but this is because of the price tag. If you think through your use cases, then you can use the same license for multiple purposes. If we think of scalability in the sense of changing the process, then this is something that can be done, but it requires extra development time. So, it's rather scalable.

We have two lawyers using this robot. Their role is to monitor the robot and make sure that the robot works fine. For example, if there are any complaints from the clients, then they can respond.

We, in legal, are among the first to use this robot to my knowledge. Other than a couple of robots that I've mentioned in this review, I'm not aware of other robots.

How are customer service and technical support?

The technical support is very good. They were very responsive. We had a question about the license and they replied very quickly.

Which solution did I use previously and why did I switch?

We did not previously use another solution. We decided to implement an RPA solution because we wanted to streamline our processes. We also wanted to be able to offer and develop new services for our clients. For these particular use cases, using other technology solutions would have been more expensive and complicated to set up.

How was the initial setup?

The initial setup was a bit complex. We are a very big company with a lot of IT centers. I think the complexity was on our side. The initial part of setting up the virtual machine and installing the licenses took roughly two months. After that, the development time was very short: one week.

Our experience, as administrators of the platform, is quite good. Once the robot is set up, it is very easy to see the results, reports, and if there are any errors. It is quite easy to use.

The robot that searches for insolvency cases was built in one week. After that, we have been testing it and making adjustments, but the construction and development time were very short.

It speeds up digital transformation because it's easy to implement and have it live. Therefore, it is something that we can use very easily to streamline our operations. 

What about the implementation team?

I handled the project and managed the discussion with our IT. We had several infrastructure teams who set up the virtual machines and helped us install the licensing. We had a third-party developer who developed the robot. We also had an internal team who tested the implementation. I oversaw everything.

We were happy with the third-party developer.

Now, there are several providers/developers who can build UiPath robots quite easily and at affordable prices. So, in our case, it was quite a straightforward process of building the robot.

What was our ROI?

Our processing time was reduced to half an hour. Something that would have taken up the whole day (eight hours) was reduced to half an hour. This has freed up our legal staff’s time to focus on more important and strategic tasks.

What we have managed to do is to offer a completely new service. It is something that we did not offer on a regular basis or big scale. Using RPA, we can offer it to a larger scale with the reduced costs.

What's my experience with pricing, setup cost, and licensing?

The pricing is okay, but I recommend to build a business case before going live. Ensure that you really use the license and building the robot makes sense. Try to think of multiple use cases, because one license can be used for several robots.

There are additional costs for using third-parties. We also have internal costs with the infrastructure and for the virtual machines where the robot operates.

The costs are quite affordable. It is a solution that makes sense from a business perspective.

Which other solutions did I evaluate?

We didn't do a very formal business review process.

What other advice do I have?

I think the platform is very good.

Have a good consultant advise you on the processes of automations: How to build the use case and business case. You will need a bit of knowledge around RPA and business processes to be able to have a successful implementation. 

Have a stronger technical partner tool to help with developing the robot, making adjustments, testing, etc. Testing is very important. It is important that you allocate resources for testing.

Robots can do things in a different manner than we can and more efficiently. We have to be creative and think of processes, even if only part of them are repetitive, that we can automate and a human can work with the robot. Then, the overall the process is improved and our experience as humans is a lot better.

I would this solution a 10 out of 10 because they are very good at what they do. It's very important that you understand what the solution can do and its limitations. However, for this type of product, I think they are the best.

Which deployment model are you using for this solution?

On-premises
Disclosure: IT Central Station contacted the reviewer to collect the review and to validate authenticity. The reviewer was referred by the vendor, but the review is not subject to editing or approval by the vendor.
Buyer's Guide
Download our free UiPath Report and get advice and tips from experienced pros sharing their opinions.