UiPath Platform Reviews

Our use case for this solution is for hosting and deployment purposes of web applications.

We are using the latest version.

UiPath is a good solution for automation. Our time management has improved by using the UiPath solution. On a monthly basis, it reduces one week of a developer's time.

It helps reduce human error. 99% of errors can be avoided by using this solution.

It has a very good, user-friendly user interface. This is its best feature - it is very easy to use. There is not much complexity when using it. For the beginners, this is also good.

For building automations, we can use a task manager because we also have job management or support in the development phase. We can apply first-in, first-out with work in UiPath.

For the automation, we do not require anything to be manual. We only need to set up the configuration. UiPath follows the instructions given by the developer or engineer. It automatically follows the instructions from end-to-end given in a set of files. 

The unattended automation helps improve our time management.

We are using the solution's AI functionality, which helps us automate more things. Now, nothing is complex. We just need to drag and drop things to create a flow. Everything is done automatically by the automation. It reduces our effort on these types of things.

They could make the solution better by improving the latency.

The community can be increased and enhanced. That way, if we are facing an issue and need an easy solution, we can then use the community.

I have been using it for a year.

It is capable of doing various tasks at the same time.

We have not experienced any downtime or issues.

It is scalable. We can add any number of users. This is the most scalable solution that we are using.

The technical support is good. I would rate them as eight out of 10.

We would like them to increase the community. That way, if we need 24/7 tech support due to an error or issue, we can resolve it as soon as possible.

Positive

We did not previously use another solution.

The deployment was neither straightforward nor complex. Some skills are required, i.e., basic courses are required for a developer or engineer using this solution. For a person who has hands-on experience with it, the deployment will be simple for them.

The AI functionality saves time and reduces the number of errors. It also reduces our costs in terms of human resources. It has reduced our costs by thousands of dollars.

We have a team who decides the software that we use. They chose UiPath because it was better than the other competitors. They conclude that UiPath was the best one, which is why we use it.

I would rate UiPath as nine out of 10.

We are using UiPath for automation processes in an insurance company in the finance department.

The most valuable feature of UiPath is if you set a form and there's an interaction with the user, it's easy and fast to build than the other RPA tools. Additionally, it is simple to use the connectors.

In UiPath they should improve the input and outputs of processes. I found it very complicated.

In a future release of UiPath, they could improve the OCR engine to make it better. All the RPA tools use some OCR engine, while UiPath's is the best but it is hard to configure and set up for your projects.

I have been using UiPath for approximately six months.

The stability of UiPath is highly stable.

We have approximately four people using this solution in my organization.

I have not used the support from UiPath.

We previously used Blue Prism.

UiPath gives a return on investment, it does what it is supposed to do.

UiPath is an expensive solution but it is worth the money. You have a lot of features. 

The licenses need to be improved because when you have to use UiPath on another system, you have to set up the processes manually, and you are not able to change the process the time if you configure a process running at the system. You have to stop it and then run to the other system. It's not too easy to configure it according to the system. If you have a large deployment, for example, 10 to 20 bots, it's hard to configure.

UiPath has a lot of free training and a lot of free processes ready to go. You have to see the best practices in order to receive the best way of development. It is important to see the best practices guide.

I rate UiPath a nine out of ten.

UiPath is great because it's highly stable, it's fast to develop, and easy to configure. However, there are some improvements to be made.

I mainly use UiPath for all automation tasks. We focus on the security automation side. We are doing some research on security automation regarding incorporated SIEM. We mainly are focusing on the security automation side using UiPath.

The process design work, the workflow management, and the custom templates are the most valuable aspects to us right now.

In terms of the ease of building automation using UiPath, it's easy to use. Previously, we had to do everything manually. When it came to automation, we had to design it manually and we had to have the documentation and everything in a separate place. By using UiPath, we can collaborate with everyone in one single system and we can maintain everything in one repo. Everything in one single system makes it easy to use and reduces our time spent creating automation while also improving effectiveness and efficiency. In terms of time saved, while previously it might have taken us two to three days to do perform a task, we now have it down to one.

The automation cloud offering helps to decrease UiPath's total cost of ownership by taking care of things such as infrastructure maintenance and updates. We don't have to host in our environments. They are responsible for maintaining everything. We can also connect from anywhere, which is very useful. The automation cloud offering helps to decrease UiPath's total cost of ownership as it reduces maintenance costs.

I use the UiPath Academy to learn more information, get new features, and learn about them as I go. UiPath Academy courses have been extremely helpful in getting up to speed and getting updates on the new features.

These days, once they release the new features, we can immediately learn about them from the Academy. We have everything, including guides, in one place. We don't need to search here and there and go and search features and ask for help from someone else. Once we first log in to the Academy, we can see everything that's saved there. We have one single place from which to learn.

The UiPath user community, in terms of the value that we gain by being a part of it, is good. The forum is also there. If someone needs help they can put the question on the forum as well. While there's no extreme support, for mid-level questions, we have some sort of support there right from the community.

We use attended automation. Attended automation has helped to scale RPA and has benefited the company by automating department or role-specific processes that require human-robot collaboration. UiPath helps to improve the effectiveness of the processes. Time is saved and human errors are reduced when we leverage this aspect. We've likely seen a drop of 50% in human error. It's also freed up 50% of employee time.

We do use some of UiPath's AI functionality in our automation program. I use some subject features. While using complex processes, we can segregate them into different parts and we have more visibility of the processes. When it comes to automation, we can make decisions such as how these processes are aligned and how to rearrange them. The AI functionality enabled us to automate more processes overall.

UiPath has reduced the cost of digital transformation so far. Some upgrades were required, however, they weren't massive. Most of the stuff can be managed.

They could work to improve the user community. For example, having a common place to discuss items. They could improve user forums. That way, we can share knowledge and experiences across different industries. 

I've been using the solution for around six months. 

In terms of stability, it's really good. I haven't come across any problems.

Scalability is really good. We can change anything we want with minimum time.

The cloud offering allows us to scale up operations. When the number of users increases and the number of tasks goes up as the business expands, we can easily, with the cloud subscription, share it with more users. It's really easy.

I currently use the solution daily, which will likely continue. Many people use the solution in our organization, including all developers and project managers as well as IT admin. Around, altogether 80 to 90 people are using UiPath. I've automated two processes so far, however other departments also use it and they are doing their own automation projects. 

Technical support has been very helpful. 

Positive

The initial setup was straightforward. For implementing and getting support and we could directly work with the company. UiPath was very helpful.

Deployment was done by a separate IT team, however, we are used to testing the product and giving feedback. We provide the feedback, what we use, and everything, and it can get tweaked. It's quite straightforward and easy.

It took about three months to deploy UiPath.

The implementation strategy was to communicate with IT. They know the whole solution, however, we were participating in the process to witness how to use the software and how it's helpful. We give feedback on how it feels to do our work. Therefore, I don't directly install it; I only advise on my findings from a usage standpoint. 

UiPath helped to deploy the UiPath solution in our organization.

UiPath has helped save 60% of costs for us in our organization.

We have seen an ROI. Considering the overall cost we spent before vs after and considering our increased accuracy and the time savings when you see the bigger picture, it's worth more than what we spent.

The pricing and licensing of UiPath seem to be affordable. 

The IT team may have looked at other options, including Blue Prism. I didn't directly participate in the evaluation process. 

We are UiPath customers. 

It's a good process automation tool. I'd invite anyone to consider this tool if they are planning to go into automation tasks. However, they definitely need to have a trial period. After that, if it suits their goals, then they should acquire it for their organization.

I would rate the solution a ten out of ten. 

We are partners of UiPath, and we are also programming for them. We are using it internally in our group, but we're also using it to develop automations for our clients. 

In terms of its use cases, we have implemented several automations in financial departments, mostly related to preparing reports, but UiPath is not limited to that. We also had use cases in HR departments for calculating bonuses, for instance, for large companies with more than 1,000 employees or for centralizing the hours worked at certain building sites for a construction company, etc. 

We automate whatever a client needs to be automated. We will discuss possible use cases with a client and prepare a short evaluation regarding the costs and benefits, then it´s up to the client to decide.  

UiPath develops increasingly towards cloud solutions. We still have clients who prefer to have it on-prem, but new clients will mostly opt for cloud solutions. The clients decide on the cloud provider, and we basically use whatever the client wants. 

One of the most interesting use cases we had was for a carrier that has about 300 trucks all over Europe. They check the bills that the truck drivers bring back from the gas stations and compare the amount of fuel in the bills with the consumption the GPS system of the truck has actually recorded. In the past they prepared these reports manually, which was quite complicated. It took them almost half an hour for one report, and that 300 times per month. They had to compare the figures from the GPS systems with the ones that were stored in the cloud and with the figures that they had in their accounting based on the bills from the truck drivers. We automated the whole process. With the automation we could reduce the time for preparing a report from half an hour to about 35 seconds, and the process is completely running in the background. Apart from the data regarding fuel consumption, we also included some additional information in the reports that they always wanted to see, but never could implement, due to time constraints - such as when a truck is due for the next service, how much time the drivers use cruise control, and so on. This was quite an interesting and a little bit unusual use case.

Very often, UiPath has been helpful in centralizing data. TPA is a tax, audit, and accounting company, and internationally we are part of the Baker Tilly network. One of our international Baker tilly partners has to centralize the financial results of a multinational client from 40 countries every month by retrieving and processing information out of the balance sheets. Previously, they had to prepare this manually - automating it saved dozens of hours every month. At TPA, for instance we have a client with more than 200 companies. We have to integrate data of more than 200 general ledgers every month for them. That's something that we have automated internally.

In two and a half years of using UiPath, we haven't had any issues regarding its stability. It is working very well.

Their customer service is excellent. Whenever we have a question, we immediately get a response. We have calls with their teams, and being in Bucharest, where UiPath also has one of their offices, we are often able to meet them in person. That's working pretty well.

They are permanently improving their products, that´s a huge advantege compared to other RPA providers. In comparison, I have heard that Automation Anywhere sometimes has issues that remain unresolved for quite a long time, but UiPath is permanently bringing up new versions, new products, and new solutions. Until now, we did not run into any issues, we could automate anything we had agreed upon with our clients. We have not had one case where we would have reached the limitations of UiPath.

Some of the licenses, such as for Document Understanding, are a little bit expensive, and sometimes potential clients hesitate when they learn about the license fees. We hope that they will reduce the prices over time. Apart from this, I don't have anything to improve.

In terms of new features, it is already difficult for us to keep up with what they're offering because there is so much happening, and we always have to take care that we're not missing out on something.

We have been using it for two and a half years.

Stability-wise, we have had zero issues. It is working very well.

Their support is really very good. When it is about new products, such as Document Understanding, we have to understand:

• How does it actually work?
• What can it do?
• What it cannot do?
• How to sell to the client?

We often have very detailed calls with the staff of UiPath, and if the client is in Romania, we often go with somebody from UiPath's sales team to the client. When the client is abroad, we frequently include somebody from UiPath in the calls to have an introduction for the client.

Positive

When we started with RPA three years ago, we did not use UiPath. We used Foxtrot/Nintex at the beginning, which was quite unreliable, they had severe stability issues, especially with more complex automations. We stopped working with Foxtrot/Nintex after about three or four months because there was something going on all the time, and we couldn't offer it to clients.

Usually, we start with relatively simple automation. Most of the clients start with a small studio and one robot license, which is anyways included with the studio for an extended proof of concept. They have done automation where they see that it is working, and then they start discussing other more complex automations with us.

We also have clients who start right away with quite complex processes, sometimes almost too complex. If a process would need six months or more to automate, clients tend to lose patience. We always prefer to start with a process that can go live after two, three, or four weeks so that they see that it is working, and then extend it step by step. 

My advice would be to start automating something that really hurts but is not an extremely complicated use case. It should be a process that takes only a few minutes being performed manually, but is being performed frequently. These are  use cases that usually can be automated within a few days because they are not very complex processes, and automating them delivers quick results. Based on this first experience, you can have a discussion with us or the other partners of UiPath to see what else would be automatable in your organization. Many times, clients have some suggestions of what could be automated, in most cases classical RPA solutions, but there is so much more all around RPA to better understand your own organisation, such as process mining, task mining, and other solutions that UiPath has recently finalized and brought into the market. 

I would rate it a strong nine out of 10. It is not yet perfect, but then, nothing is perfect.

We're doing mortgage loan processing. When people are applying for a new loan, we're using it to gather all loan documents and validate the property ownership and do a title search. We then put the loan documents in a package.

We are using its latest version.

It used to take two hours to take all these documents and load them in, and now, it takes 15 minutes. So, we went from two hours to 15 minutes. We're able to process a significantly larger number of documents in a much shorter time.

It had pre-built integration with the scanning solution that we use called Kodak Alaris. They use our current scanners to scan in the documents, and then they have the software that allows you to load those documents right into UiPath Orchestrator. That gave us the ability to automate those processes.

It took quite a bit of time to understand some of the document types. Some of the documents were already pre-built, but some of the documents were new, and it took us quite a bit of time to get it to train on those documents. If there was any variation, we had to re-train it. It took longer than expected.

I have been using this solution for about four years.

Its stability is very good. 

It is enterprise-ready. So far, we are very happy with everything that we have been working with. It is designed for enterprises. 

We're going to continue to use it for the next five years. It is automating the roles. It has to do more with validation than anything else. The users like it a lot, and we're very happy with it so far. 

We have a third party for support, and they are very good. They are very quick to support.

All in all, it was pretty straightforward. We had to bring in third-party consultants to get it going. We were expecting that, but the costs were a little bit more than what we were thinking at the time.

From beginning to end, it probably took about four months. It included everything that we were trying to do. We got started right away, but the actual deployment took a little bit longer than what we thought it was going to take.

We've moved from different versions over time, and we were able to do it pretty seamlessly. We had another product called Automation Anywhere, and that took a lot more effort to do the migration. So, we were happy with the implementation time that UiPath took.

We took the help of a third party. Our experience with them was good. It was more expensive than we thought it was going to be, but overall, it was good.

For its deployment and maintenance, we have a team of four people in the house, and then we have five people outside who are actually continuing to do maintenance in terms of upgrades and new forms as they come up.

We have probably saved about $6 million using the product. We were going to have to hire about 600 people to be able to process the loans, but we only had to hire 150 people. We didn't have to hire 450 people, which was pretty significant.

We did pay more than what we thought we were going to have to pay upfront. We had a third party for implementation, and the cost turned out to be about twice of what we thought it was going to be upfront. So, instead of one month, it took us three months for an ROI, but we got significant returns. 

The hardware requirements to manage this was also a little bit more than we thought it was going to be, but our ROI was so high that in a way we earned it back. So, even though the costs were more than what we were expecting, the return was much better than we were expecting. We were supposed to go from two hours to one hour. That was the goal, and we went from two hours to 15 minutes. The benefit was more than what we were expecting.

Its actual cost turned out to be about two times more than what we thought it was going to be upfront. There were hardware costs that we were not expecting. Some of the server costs and things of that nature were higher than what we were expecting but based upon the return, it was a net.

We looked at Blue Prism, Datamatics, and Signavio. We just looked at the market and how many references they had that were in our market space. We were able to talk to a significant number of companies that were already using these products for the same thing, and that's what we based our decision on.

I would advise doing the homework upfront and seeing what the full impact is going to be. You should not just look at task automation; you should also look at the full process. That's because when you make a change in one area, you need to consider how that's going to affect another area in your organization. You may get a big benefit in one area, and then all of a sudden, you have to change the way you're doing business to take advantage of that. If you correct a bottleneck in one area, you might still have another area that's a bottleneck, so you need to look at the full process. This is something that we learned in general from our experience. As we were fixing different things and automating different things, there was another bottleneck down the road. We went from doing 10 a minute to 100 a minute, but when we went to the next process, we could only do 10 a minute. It didn't really make a difference unless we fixed that one too. That's why you have to look at the full end-to-end process.

I would like them to work on the process mining solution that they have to give us a better picture of the full end-to-end process. That was what was really missing. They do have a process mining solution that you can run up front, but it wasn't very good. We ended up running into things thinking why didn't we know that. If we had a better tool upfront to give us the bigger picture, it would've saved us a lot of time and effort down the road.

I would rate it an eight out of 10.

My experience in using UiPath, in general, is in developing traditional bots, assisted bots. There are the typical mundane applications that we're trying to remove in order to add value to customers. 

The solution is used for extracting information from documents and consolidating data, maybe from various Excel sheets. I've used applications, such as PDF, Tableau, and a number of different entities as well. It varies.

I haven't really followed up so much in-depth, however, I know that a lot of the end-users that I've worked with and talked to, that have removed some of the processes, think it’s great. I've got many more strategic types of tasks to do. The one thing users look forward to when they come to work is when something’s been removed from their plate, one piece at a time.

Collectively, I find the UiPath features really complement each other. If you have one tool or another resource available, you're really able to get it into a solution.

They've implemented their stuff very well, considering how fast they've come up with new tools. Usually, it’s a messy situation, however, with UiPath, I've not found that to be the case. It's pretty impressive, the rate at which new tools are released and how well they're thought out, and how usable they are.

From an employee morale perspective, the company is getting positive feedback.

We’ve seen some reduction in human errors and time savings. Depending on what it is, your time savings could be two to three to ten times more in terms of time saved. It’s easy, too. Error reduction is absolutely almost down to nothing.

In terms of cost savings, some of this was done pretty casually, so the numbers are maybe not official. We’ve got 20 data samples, and we're timing it exactly. However, when it comes to time savings, there's always been a very significant amount.

When it comes to ease of use, some of the tools they're providing are in discovery or task capture. You can go out and send this off to somebody and it's pretty self-explanatory in a half hour. Prior to that, people might be using different steps with built-in Windows pieces, which is horrible for capturing automation. If all you have is a hammer, everything looks like a nail. Therefore, adding in this ability to annotate the screenshots with ease, that alone in the development process helps significantly. I'm really liking the discovery tools that complement the product.

All these discovery tools are making building automation easier, from an analyst perspective. It removes the wheat from the chaff and narrows things down, and you begin to see what you need. By clicking on different elements, you can see where they can annotate. It saves a lot of back and forth and time. Not only does the subject matter expert not have to spend time away from their work, you're also not going back and forth and trying to clarify items any longer. It makes things more compact and it’s easier to get to the end goal.

I completely trained on my own as a developer with the UiPath Academy. I was able to do it for free. It's the only onboarding I received. I had nobody else to go to, except for the videos and the forums.

The greatest value of UiPath Academy is that it is free. Now, it’s completely about motivation, and not cost-prohibitive. You just need to be motivated to learn and you can jump in. You don’t have to spend something like $800 and have maybe a company sponsoring you to get started.

People, in their careers, can become relevant again. If they are in a dying industry or disrupted industry, they can get into something that's growing rapidly. If you have a computer, and a decent internet connection, you can have a new career in a fairly short amount of time.

The forum's a great place, however, for a new person, it was better some years ago. It's grown too fast, and it's not that nimble. Previously, if you asked questions, the response time was quicker.

Since I've learned UiPath, there's so many more people rushing and getting into it. With the demand for RPA jobs, the ratio of expertise to novices is very, very low. Before you had a small community and you had a lot of experts and just a few new people trickling in at a time. The influx of new people, it's just growing factor by factor. Where previously there was one person that only had a few questions to answer, now maybe that ratio is now 20 or 30 people. You're not going to get the answers that you need as fast. Luckily, the quality of the Academy is so good, if you look around, you can eventually figure things out.

The issue is that, with so many people, a lot of questions are getting asked before anyone even looks to see if an answer is already there. It tends to make it harder to find relevant, real questions that need to be answered. There are people who are not doing the due diligence and looking at the tags and spending a little extra time before throwing the question out. It makes that part hard to manage.

With people that have already been up-skilled, or already been skilled in the past, UiPath needs to find a way to send some sort of notification to them when items update or change. They need to send out a message to experienced developers to say: “Hey, look at this and push it out."

If you're not going to the Academy and looking for something new, there needs to be some sort of way to say: “Hey, you've been certified. You haven't been in this course. You should look at these things.” I started looking at the Academy and found new elements. When I mentioned something, like, "What's that?" the new guys were aware due to the fact that it was in the Academy from when they started and was not there when I finished.

Basically, just having some sort of mechanism for spreading awareness to existing developers, or pushing something out to them, maybe even through the interface, would be helpful. Whether it’s a little highlight or a little icon to alert users to “hey, here’s something new, something pushed out.” And it’s not just something where you have to go in and read some boring five or six pages of notes, to know that this thing is there. It needs to be visual.

I started using UiPath, which started with training, in the fourth quarter of 2018.

It's a very stable product. I haven't had any issues. If I found or thought something was unstable or something, it usually ended up being me, or an operator error.

I've seen UiPath scaled. Personally, I haven't had issues one way or the other, however, I've heard good things. That said, I can't speak too much on it from the perspective of personal experience.

I have had some interaction. They had a pretty good SLA, in terms of response time. Of course, that has nothing to do with actual solution time. That said, what I remember with everything was that nothing stood out. Usually, you remember some anger or something. I didn't have anything like that.

I'm certified in Automation Anywhere as well. Right now, Automation Anywhere always has two products out, in the sense of getting ready to move into their A360 with the newer product. They're just trying to get that product to maturity. Right now, we have different deployments. Automation Anywhere is cloud-native. 

While they're both RPA, they each have I think a different niche, depending on what the customer needs. 

As a developer, the learning curve in version 11, the prior version, had an easier learning curve compared to UiPath. Automation Anywhere has an edge, in terms of ease of learning for business users and citizen developers.

360 has made the learning curve harder. It's going to add more features, more flexibility. And with that comes a learning curve. Still, the learning curve might be a little easier. 

My deployment experience was not just through UiPath. If anything, I'm pretty agnostic to any platform. I was an analyst, and I was involved with, in general, putting items into production, and going back and forth with developers, and seeing if there were any issues or problems.

I've talked to other developers, and I haven't heard of any particular issues or problems, with UiPath, or anything that was more than just human error or an oversight.

If you're smart about it, you understand what your needs are, you can get an ROI out of it without having to go get the full-blown solution. You don't want to drop $20,000 on an orchestrator unnecessarily. You can ease into it, into adoption, without dropping a lot of money. Maybe some attendant bots, and an unattended locally on a large scale, in a small area.

If you do that and start easy, you'll get a return on investment. Eventually, when we start scaling, we'll pay for the orchestrator. You'll need that when you start getting a lot of bots, and it becomes like herding cats. It gets crazy. That's what you need an orchestrator for. While you can avoid a cost at a certain point, you're probably getting diminishing returns, and then it's going to be more costly to manage something all over the place. It's best to start small and then add on. 

We haven’t been using an orchestrator. It’s a bit like having your hands tied behind your back, as you're not using some of the features that are available with that. However, it still provides these workarounds. You are able to still do some really robust work. It's been great.

We are using, more or less, the more recent versions of the solution.

Before starting with UiPath, a company needs an understanding of the culture at their company. You need to ask if your employees are resistant to change. Certain companies where people are entrenched in their ways, or scared of bots taking their job will be worried. A company needs to lean in and give them an understanding of expectations and pay attention to them before starting. Just pushing it might throw people off.

The personalities of people are the biggest factor. I used to come from a lean Six Sigma background. When companies bring in these Six Sigma programs, it's the same thing - resistance. People say “oh, you're the job cutter.”

People throw that out as automation, and I say, "Hey, people have been automating since steam engines. It's been consistent. It's just the face has changed a little bit. It finally hopped back onto computers. However, automation has been nonstop." 

You just have to realign and adjust yourself. You can’t be resistant to change. Change could be a good thing. Not all things are, however, workers need to be rational and think about it. If your company doesn't move faster, adapt quicker, then your company's going to go away, and everyone will be gone. It’s competitive. That's sports. That's business.

Overall, from what I've used, and what I've touched, and some of the things I've seen without actually putting my hands on it, I'd give UiPath a nine out of ten.

I'm just not the type to give out tens so freely. I haven't gone deep and wide enough to touch everything. From what I've seen before, if you span that out overall, I'd probably put them up in the nine range, personally.

Our use cases have evolved over time. We have use cases for screening and onboarding candidates, feeding new hires into the payroll system, and timekeeping. Right now, we are working on a document understanding use case. It is going to help us read supplier insurance forms.  

UiPath has enabled us as an organization to perform an array of tasks with more proficiency and efficiency. Automation is very important to our organization now and UiPath has played an immense role.

UiPath makes building automations incredibly easy. The platform is very robust and it is scalable. UiPath also has a strong community, which has helped democratize RPA in a true sense. The community and expertise can be leveraged quickly to meet a common goal.

The UiPath Academy has helped us move forward more efficiently. It is a great source of information and knowledge for both new users and those taking the advanced courses. I see the UiPath Academy evolving in the future.

One of the features I've found valuable is UiPath Studio. We have a huge development team of about eight to ten people and they are currently working with it. We also have a citizen developer program that is leveraging StudioX. 

Orchestrator is important for us as well. 

These features are valuable because they allow different groups of people to complete their tasks. UiPath is a robust platform. It helps us cater to different audiences. 

The licensing model is sometimes very confusing and could be simplified for customers. That would help us understand, gauge the offer, and work it into our existing infrastructure. 

We started using UiPath in 2017. We have had a great journey with it. UiPath has helped us scale faster, especially with RPA implementations. It also helped us evolve through our automation journey. 

My impression of the stability is that it's like any other software. We have never had a problem with UiPath and the platform has been stable enough to enable us to scale a lot. 

We have been happy with UiPath's scalability so far. I would give it a nine out of 10. We are currently deploying about 95% of our automations through UiPath. We are very into it and plan to expand from there. 

Yes, we did use a different solution but I cannot disclose which. However, I can say this much: we decided to switch because of the community UiPath has built. Also, the platform and product are packaged correctly. Everything is laid out well and it seems like UiPath understands what businesses need. 

The initial setup was straightforward and easy. UiPath has an incredible team in place. They help us every now and then. It did not take us much time to go through the initial setup and get the solution deployed. 

We have realized savings in the millions of dollars overall.

The pricing structure is very complicated. Someone from the organization has to sit down and set aside some time to fully understand it. 

Yes, we did evaluate other options but I cannot disclose which. 

Start your journey with UiPath. Engage someone from UiPath and have them go through the journey with you. 

We primarily use the solution for our clients. 

One interesting use case we've seen is that the product team leveraged UiPath to expose an API for their customers to then fulfill a service request.

It was part of their deal that, for them to sign this large contract with one of their clients, they needed this functionality. The product team has a huge backlog, and it wasn't going to make it based on everything else they had to deliver, so they actually leveraged UiPath to expose this and give them a service they just didn't have before.

When comparing it to, for example, Blue Prism, one of the key value points is, other than the full platform in general, the ability to trigger automation on demand. Basically, when the work gets loaded into the queue, the work can then be started without having to run things on a schedule.

The solution has improved the way an organization functions. For example, in general, in the context of RPAs, it's really about the focus of picking those tasks out of people's daily efforts so they can spend more time with the customers. What you get off the back of that is dollar for dollar savings. You invest in this tool, and you get back dollars by hours, however, beyond that, there are these peripheral benefits that you get that are a little harder to measure. You’ve got to have good guys out there to capture this.

In terms of endpoint satisfaction, customer satisfaction, you have to look at it within the business and their measurements before and after you've done something to actually see what is happening and attribute it to what you've done with UiPath.

We haven't done anything that hasn't saved money yet.

At the beginning of a journey, we were looking to get maybe 1X our money back in that first year. We try to get that at least. Depending on the size of the organization and complexity, it’s possible. As you go into year two, year three, you're almost looking at a multiplier reflecting that year. For example, a four-year-old program might get a company around 4X, if not more, in return. Of course, that also depends on how far you've implemented this product. You need to put money in to get money out, in a sense.

If you've got a pipeline of X and you only have three developers, you can only chew through that pipeline at a certain current rate. You want to look at the value and say, "Well, what if we doubled our staff?"

I have a calculator that shows, for example, if you have $10 million of savings sitting on the table through 20 things in the pipeline. If I put one developer on that, it will take me three years to go through that and build that out. At the end of that $10 million of value, imagine if instead, you had everything all automated on day one. That's a total max value, and you would get somewhere around 23% to 30% of that value returned.

If you double that or if you put a staff of three developers on that same pipeline, you finish earlier and you get about 75% of the total value. If you go to four developers or five, you get closer to 83%. Now, if you put 20 developers on there, you're only going to increment it to 95%, however, then you’ve just increased your total cost as you have to try managing 25 at the same time. The main idea being, based upon your pipeline and the size of your team, you can potentially increase your total return value within a fixed time.

The ease of the use of creating the building automation is actually improving year over year. For example, there are some training programs for UiPath, and it generally takes about a week to get through it. That’s on UiPath Academy.

If you actually use it with modern design, modern objects, and all the new things that have been released recently, you actually save time on training. If that shaves 20% of your training, you can also shave 20% off of your building capability or the requirements. BY using UiPath Academy, you save time on your projects.

It's fairly easy to learn, as a solution. However, it’s not that easy where you're just going to throw non-developers into it. Your first three days of UiPath training are actually doing .net. That's the one thing the market puts out there incorrectly is that your operations team can just jump on this. You still need a developer mentality as you're still dealing with exceptions and things that aren't the way humans think.

That said, in terms of usability, it's highly useful.

UiPath Academy helps streamline and keeps employees up to speed in the solution.

The biggest value of the Academy is that it's free. That's a major piece. It's fairly well organized, and they put things into channels based upon what your role is within your RPA program or your business, and that helps you stay focused in terms of what you need to learn.

The solution needs resource locking. This kind of leads toward scaling which is one challenge. It's not major. However, it is when you have multiple bots running the same process and they need to access the same piece of information to read and write. There's not a strong capability to manage the lock and have the capability to say "I have ownership of this file. No one else can touch it" and then release it, allowing the next one to pick it up. That's a key differentiator that I see between them and Blue Prism. That one feature is lacking.

The studio design is a little different. If you go from one tool to the next, you might be a little shocked at how things are organized. I don't see them changing that any time soon. However, the design could be improved upon.

I've used the solution for about four years. 

The solution seems to be stable. I haven't had any issues yet.

The solution is very scalable. I haven't pushed it to 100 plus or anything like that. However, based upon scheduling and triggers and SLA management, it's much easier to scale.

We did work with other RPA solutions in the past. The differentiation comes from the triggers, and the attended automation. The platform now is a big part of this. 

For example, Blue Prism is one of the tools that we work with as well. If you want new functions, new features, say, process mining, you have to go to Celonis or someone else, whereas UiPath is providing this platform with new capabilities almost daily.

It also depends on what kind of COE you want to build. Looking at Blue Prism, they have a nice UI as well. It's very business-focused. With UiPath, you need to have some developer capacity. There's .net in there, and some people just might not get that. However, at the end of the day, if they don't get that, should they be building processors? There's a bit of a challenge there.

The initial setup is not that complex. It's more about the client's setup. For example, the domain, entries, things like that, would add to the complexity you face.

If everything goes well, you can get things set up probably in a few weeks. I would say a month or so is needed for deployment and implementors should set expectations. For example, security depends on how much the organization is ready to take it on as well. If you don't get their buy-in right away, then you're just going to get delays.

Most of the companies see a good ROI from the solution.

The pricing and licensing get a little complex. There are so many different options that you can choose from, and practice adds to the time to figure these things out. Whereas, with, for example, Blue Prism. It's a pretty standard basic model. UiPath gets a little hectic at times.

The customers that use the on-premises version tend to use the latest version of the solution. 

While those using the cloud version of the UiPath apps feature are in the UK, the US users are not using that functionality. Mainly most of our focus has always been on RPA and then expansion. From what I've seen, we've mainly been using UiPath. At least on the North American side, it's been relatively new. That's why they aren't using apps yet.

We don’t have any clients that are using the solution's AI functionality in their automation program yet. I’ve only played around with it myself.

From a road mapping perspective, I'd advise potential new users that your key is the business case. If there's no business case, then this solution doesn't make sense for you to get involved or do anything else. The first part is to really understand the business case. Just to substantiate getting it into the company. Once you have that, that's basically your low-hanging fruit. 

That said, the key is not to hang everything on one process, not to sit there and bank it, as the concept is a program approach. Over time, it is going to sustain itself. Companies need to be ready to look at a process and think if it's a good idea first. And as you move through the steps, you're basically doing additional checks. As you learn about the process, you're also learning what it's like behind each process and what the value add is. At each stage, users need to ensure that it makes sense to continue. 

I'd rate the solution at a nine out of ten. While there's always room for improvement, market-wise they are at the top of their game.