UiPath Platform Reviews

We are using Studio and Orchestrator.

Our primary use case is automating data processing for clients translating into other systems.

We do not run our automations in a virtual environment.

With respect to how easy it is to automate our company's processes, on a scale of one to five, I would rate this solution a three. I think that the technology that we use in the printing industry is a little more difficult to automate.

I am currently involved in the UiPath Academy training. We have third-party contractors who have been doing the development, and I am the first internal employee who will be developing. I find that the training is good in the first step, and also in the second step where we're learning about Orchestrator. However, when it moves to the third step and they are talking about the framework, I think that it is a pretty big leap and that is where I'm struggling. This is the section that I am in right now.

There was one project that was completed before I started, at my understanding is that from the point that we purchased our UiPath license until we had our first robot was less than six months. For my project, it has taken two months.

Using this solution has allowed us to enter a lot of customer data into our system in a much quicker and more efficient manner.

In terms of eliminating human errors, this solution has definitely helped. I would estimate an eighty percent reduction in the number of errors.

With respect to saving time, automation has taken a process that used to take two or three days to perform, down to several minutes.

The most valuable feature for us right now is being able to automate our process applications.

In the training, between steps two and three, there is a pretty big leap in terms of how difficult the material is. Moving right from the basics into the framework is causing me to struggle a little bit, and I think that there is room for improvement here.

With respect to the stability from a bot perspective, on a scale from one to five, I would rate this solution a four. It has been pretty stable for us.

We have less than fifty people involved in our RPA program at this time.

We have contractors who are doing our development right now. On a scale of one to five, I would rate our experience with them a three. They seem to be struggling with the PDD.

In the project that I worked on, we have definitely seen ROI. We replaced a process that was being done manually, so we began to see returns immediately.

For the way in which we are using this solution, the features have been working very well. Our company is very young in this so we are still learning. We will get a lot out of this solution.

If you have a lot of manual and repetitive tasks in your company then this is definitely a great solution for you. That said, I know that things can always improve.

I would rate this solution an eight out of ten.

We use Studio, Orchestrator, and robots.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

I would rate this solution a nine out of ten.

I primary use Studio, but I also use Orchestrator.

I develop robots for reducing tasks for our business users.

We run some of our automations in the Citrix virtual environment. We have found that the Citrix environment tends to present challenges, so it can take a little longer.

With a year and a half of experience, I am still learning with this platform. I find that the ease by which processes can be automated is not as much of an issue with the platform, but rather how it behaves with other applications that the robot controls. The learning curve is mostly how the robot behaves in maybe a Citrix environment, or in how it behaves with the applications that it's controlling. Sometimes they have their own little quirks that you have to learn.

I got started with this solution by using the Academy training. On a scale of one to five, judging how beneficial it is, I would rate the training a three. It is easier to get started because you are learning by experimenting.

From the point that we purchased our UiPath license until we had our first robot was approximately seven or eight weeks. 

Some of the robots handle high-volume processing, where people would take months but the robots are doing it in weeks. We have probably saved two hundred hours so far, using robots. Timing is a big issue. The tasks can be completed quicker because robots can do it on-demand, rather than having to schedule a person's time. I would say that for the tasks, they are saving forty to fifty percent of the time by using the robot.

Not all of the tasks we have automated were existing in-house processes. In some cases, after using the platform, we thought about ways to create automated tasks that were never being done before.

Human errors have been reduced, if not eliminated by using the solution. When users have to complete a task in a timely fashion they sometimes miss one of the steps, but this is solved using the robots.

The robots that I have developed can take a process that is normally very complicated and simplify it. 

The licensing process is complicated and needs to be improved.

With respect to the stability, on a scale from one to five, I would rate this solution a four. The tool itself is quite stable and I haven't had any real issues with it. The issues that I have had tend to be with Citrix or the environment that the robots are running in, and not the platform itself.

In the US, we have two developers who are working with this solution.

The installation was straightforward but activating the license was slightly complicated. I'm not sure if it was a UiPath issue or something at the company.

We are definitely seeing performance benefits for users and the turnaround time for tests that we have to do.

I have seen a demo with Studio X and it should help with the coding so that we can go live quicker than we do.

Using RPA has given us another tool to offer with respect to business solutions. Automation is something that we're actively looking for places to make use of.

This is a good solution, but there is a learning curve. One you are familiar with it, this solution works well and it is fun to work with.

I would rate this solution a seven out of ten.

We are using Studio and Orchestrator, and we purchased an unattended bot.

Our UiPath is integrated with Kibana, which is a free tool.

Our primary use of this solution is to automate manual processes. We have approximately eighty use cases to automate.

The RPA team includes two developers, a manger, and two BPOs.

We run automations in a virtual environment, but I am not familiar with the details.

With respect to how easy it is to automate our company's processes, on a scale of one to five, I would rate this solution a five. We just drag and drop. If you want to write something we use "Type Into". If you want to click, we use the corresponding click application. For me, it's very easy, and we also have tutorials available on the UiPath website. That is something that is very useful for everyone who wants to learn, and even a non-programmer can start learning to become a developer.

The Academy RPA training was very beneficial and I would rate it a five out of five. You cannot skip one step. There are ten sections and you cannot skip any of them. It means that until you pass a certain test, it will not allow you to go to the next lesson. This restricts people from jumping directly into another section. I really like the training and it is very easy. The tutorials are not very lengthy, they are simple, and the way they are explained is relatable. The practice tests that were conducted at the end were really helpful.

We partnered with IVy to create our first two pilot bots, and from the point that we purchased our UiPath license until we had our first robot was approximately six months. It was very easy because they helped us.

This solution obviously helps us when it comes to eliminating human errors. I cannot estimate the percentage, but our company is manual process-intensive. We have a lot of manual processes like invoicing, where we have a process with the business team. They pull out an invoice number and a purchase order number from a PDF, and the source PDF is not structured. When it was being done manually, they had encountered issues entering data into one of their applications. This is one place where human errors have been reduced.

Using this solution has saved us time. For example, we have a huge process and I have heard that it saves us millions of dollars every year. Each human takes forty hours to complete the task, whereas it takes the unattended bot between ten and fifteen minutes.

Any savings in time for humans gives them time to work on something else.

The most valuable feature in Studio is the macros. They are very useful but at the same time, it depends on how we write them.

UiPath is very easy to learn.

When we deploy code into Orchestrator, sometimes there are macro activities that worked in Studio but do not work correctly in production. For example, I have implemented a Text Reading Activity that worked fine in Studio, but after deploying the code into Orchestrator it does not read the text exactly. I was able to create a workaround by using a split function in the code. It was reading the text fine because the data is being read using split functions, but this is something that I would like to see fixed.

I would like to see more AI and natural language processing.

Having chatbots available would be a helpful inclusion in a future release of this solution.

Customer support and technical support are very nice. I would rate them a ten out of ten.

We did not use another RPA solution prior to this one.

We partnered with IVy to assist us with the implementation. They helped us with two pilot bots. One of them was not up to the mark, so our CEO decided to have it reprogrammed. I would rate them a four out of five.

We have our own IT team that looks after connecting the servers with Orchestrator.

I am not updated regularly about how much money this solution saves us, but I have recently heard that we saved $400,000 USD in six months.

After our CEO decided to invest in RPA, we chose UiPath because it is easy to learn.

I have heard of Blue Prism and Automation Anywhere, but I have not learned them or worked with them.

We are looking forward to the new tools, and when they launch, we are definitely going to use them.

My advice to anybody who is implementing this solution is to speak with UiPath. Many people do not know how to start. The basic things they should have are a proper PDD (Process design document) and a recording of the manual process. These two things are essential. It is also very important to hire the right partner if you do not have your own developers because some of them are not up to the mark.

This solution is simple and easy to implement. I know there are lots of new features coming and every year they are providing good solutions with every release. There is always something new that minimized errors in previous versions.

I would rate this solution a nine out of ten.

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

Our primary use for this solution started with automating processes in finance, procurement, and HR. Now, we are researching various directions in logistics.

We do not run our automations in a virtual environment. This is something that we are trying to avoid.

With respect to how easy it is to automate our company's processes, on a scale of one to five, I would rate this solution a four. I'm an IT-based person, and for IT people it is easy to learn. UiPath claims that it is easy to learn and it's for everybody, but it's not true. For business people, it is hard to learn and hard to understand how to code to make things work. They need a lot of help with things like exception handling. If somebody lacks technical or programming skills then it makes it much more difficult to use. Although UiPath is getting closer to business users, there are still some basic skills that they need to have to make it work.

On a scale of one to five, judging how beneficial it is, I would rate the training a five. When I get new hires it doesn't matter whether they have previous experience in RPA or development, they have to go through all of the basic training from the Academy. This includes the Orchestrator and I've been recommending SAP training because we are experiencing growth in the use of SAP. Going to my team, this is the base, and then we have created our internal framework and standards that also require training. Some people may already have experience with UiPath or Blue Prism, but they still need to take the training from the Academy.

Before I arrived at the company, there were already some automations running. However, fifteen months ago we shut down a couple of robots because they were failing terribly. From that time, it took us five months to create the first robot.

We have a project that combines UiPath with OCR and our integration tool. This allows us to automate processes we use in different projects that are coming from different vendors in different countries. Apart from gathering the information, we are template invoicing. The robots take invoice information and post the results into our SAP and other systems. It is much faster than our original process. This has been implemented in Spain, and we are now releasing it to other countries, one by one.

Using this solution is not just about saving time or reducing the number of staff. It is also for improving stability and decreasing the number of errors that we have. In Spain, where we were implementing a pilot project for purchase orders, we saw a decrease in the number of human errors. When they started, there was an error rate of ten percent. After three months in production, the error rate decreased to five or six percent, and after six months it was one or two percent. Also, even though there was still an error rate, it was consistent and it is something that we can account for.

In terms of money savings, we are talking about hundreds of thousands of dollars annually.

The most valuable feature is Studio, which allows developers to specifically focus on development. Orchestrator allows us to connect those things together.

I would like to see some use cases and additional information on the process mining and the OCR features that are being released. There are other products that offer OCR features, and at this point, it is hard for me to determine the benefit of using UiPath for OCR rather than integrating it with another solution. This is not just from a business perspective, but from a development perspective as well. For example, I would like to see how you can connect UiPath to all of the applications to collect the logs and the data. Then, how we can put that information together. If there is a thirty-minute delay then how do you identify whether it was because the person went to lunch, or rather that they were working and thinking.

With respect to the stability, on a scale from one to five, I would rate this solution a three.

The stability of this solution really depends on the developer or the execution. It's not always a UiPath issue. If the process is unstable, it's the issue of the business case and not the actual execution of any development. So it really depends on how you use the platform and how you understand it. We will use a more stable technology, such as alerting through an API, before we go to the UI path.

We have about one hundred licenses for production and four Orchestrators.

Both customer support and technical support are really good. Whenever I have a question, whether it is business, Studio, or Orchestrator related, I usually get an answer. We have our own customer success manager who helps us on a daily basis. I also have connections to the lab and to the production team so I can ask questions there as well.

At this company, they did not have an RPA solution in place before this one.

Personally, I have also used Automation Anywhere and Blue Prism. From my perspective, it's about how you use the tool, and not about which tool you use. Personally, I don't like Automation Anywhere, and I used to be a Blue Prism guy.

I feel that Blue Prism is easier to learn because you can do things in terms of processes or objects. Logically, it is easier. In UiPath there are more options, but it's also harder to learn because you need to create a logical structure on your own. It doesn't show you how to do that in an easier way. UiPath has more connections and more inbuilt stuff than Blue Prism, but on the other hand, the navigation between the types of variables is slightly different. It's not a disadvantage, but it is something that takes time to learn.

I find that Automation Anywhere is not that user-friendly. For example, in Blue Prism you have loops that you can put a component into. In Automation Anywhere, you have to copy all of those stages, one-by-one. You cannot create a loop, which is basic.

We have not been tracking ROI yet, although we are working on it. It is difficult to calculate because to collect the information for each process it requires a logging system. Each project will require a specific logging system so that we can collect the same information to compare and evaluate it. We have to consider our development costs, maintenance costs, licensing costs, etc. At this point, we do not have enough people to work on this, so it is a work in progress.

They ran a selection process here and my understanding is that Blue Prism was not able to provide a free Studio license, unlike the policy they now have in place. This is the reason that UiPath was selected. 

The majority of our use cases are unattended, and that is the way that you should go. We do use attended bots as digital assistants, where you have small automations that are triggered by the users on their own to direct the robot. These are two separate products.

My advice to anybody who is researching this solution is not to be scared to use it. Play with it as much as possible and see if it brings value. There are different applications that can bring more value in certain cases.

Overall, this is a good solution, but there are always ways to improve a product.

I would rate this solution an eight out of ten.

We use Studio, the Orchestrator, and we have attended and unattended robots.

Our primary use case is automating back-office processes from the corporate side. One example is the automation for ticket closure for some of the customer complaints. We also use it to fill information gaps between systems. Instead of having information run through standard APIs, we have it copied over from one system to another.

We run automations in a virtual environment, and the implementation was pretty easy and quick.

We used the Community Edition before purchasing our license. From the point that we purchased our UiPath license until we had our first robot was approximately one week. We found it to be very easy and very fast. We, as a Contact Center, usually face a lot of problems when we suggest any requirements. When we started with RPA, it took approximately one month for a very complex process to be automated.

With respect to how easy it is to automate our company's processes, on a scale of one to five, I would rate this solution a five. It is very easy. You can use the UI, or you can use APIs for the connection. In the end, you can do it.

On a scale of one to five, judging how beneficial it is, I would rate the training a five, for sure. In two or three weeks, an RPA developer can do everything.

In the Contact Center, the key issue is the handling time. RPA has helped us to decrease our time, and eventually, it will help to decrease the headcount.

For one of our processes, it reduced the time it takes from five minutes to somewhere between forty and fifty seconds. That saves a lot of time.

In terms of eliminating human errors, there has not been much difference because we have very strict processes and strict steps for them, so human error was minimal, to begin with. Our success is in the reduction of time to complete them.

The unattended, back-office robots are the most beneficial feature.

The Form Builder for back-end robots needs to be a web portal instead of a full desktop application. 

With respect to the stability, on a scale from one to five, I would rate this solution between three and four. For exception handling, it means that a senior RPA developer has to understand the reasons behind the process. If they have not been exposed to it then it is easier to perform some simple fixes and continue the process.

We have implemented eighteen processes so far, they are they used in several departments. In total, we have approximately four thousand people who are using this solution.

From a scalability point of view, we're not that confident that we can have the robots running twenty-four hours a day with a huge transaction. Being a telecom operator, we have a lot of transactions and the stability of the unattended robots needs some enhancement.

I think that both customer support and technical support are very good. When we have any questions or any issues, we are connected immediately. 

We did not use another RPA solution prior to this one.

We learned about RPA because one of the contractors was working on an RPA PoC at our company, and we were convinced that it could help us a lot. The IT people were invited to see the technology and from there, they decided to implement it with our in-house IT group.

The initial setup of this solution is straightforward. We used the Community Edition and it is very easy to use. 

We performed the implementation on our own.

We realized ROI in approximately six months. Our cost savings come from savings in agents.

From a cost perspective, unattended robots are better. They run twenty-four hours a day and do not require running on a client machine. The attended robots are not as cost-effective.

We did evaluate one other RPA solution before choosing this one. Our main reasons for choosing UiPath were the price and the ease of development. The Community Edition is very useful, and we are easily able to find RPA developers working in UiPath. This is different than with some of the competing products.

My advice for anybody researching this solution is that it is easy to download and it has a big community. A PoC can be done easily, and you can decide from there whether this solution is suitable.

This is a good solution, but the stability of the unattended robots needs to be improved.

I would rate this solution an eight out of ten.

We are using Studio, Orchestrator, and bots.

We are a consulting company that is working with one of our clients to automate back-office accounting processes for a logistics company. There are five people in the core team who are working on the implementation.

We run automations in a virtual environment, but I was not responsible for the implementation.

With respect to how easy it is to automate the company's processes, on a scale of one to five, I would rate it four. It's very easy, but it is difficult to explain to our customers who are not as technical. In other words, it is difficult for people who are coming from the business side.

On a scale of one to five, judging how beneficial it is, I would rate the training a five. Without it, I don't think that I could have started the implementation. I completed the developer program just for a general understanding of how everything works, including the Orchestrator and how it all works together. For me, the training was really important. It was very good and I really liked it.

We were working with the Community Edition at first, but from the point that we purchased our UiPath license until we had our first robot was approximately one month.

In terms of eliminating human errors, we expect to see this benefit later. Until this point, we haven't touched the processes where there could be human errors. We just started with the really basic ones, which are so easy that people don't make errors there, and neither do the bots. We plan to get to the more complicated processes next.

With respect to saving time, I can say that this solution has helped, but at this point, I don't know by how much.

While we were implementing this solution, we were empowering people. This solution changed the way people are working because it is so open and everybody can take part in it. It caused them to think about their processes in a different way, with automation in mind and possibilities for the future. Now, when they're having strategy meetings, they have dedicated time slots where they're just talking about processes that could be automated, so the whole mindset is changing now.

The most valuable feature in Orchestrator is that it stores the credentials in a safe way. Our clients were afraid that the credentials would be stored where somebody could see them and being able to schedule bots with the credentials available is very important for them. 

We would like to see Studio made a little easier so that our non-technical customers can also implement the bots. For example, some of the features from the upcoming Studio X should be put into the original Studio, as well.

I have trouble understanding the machine learning and AI components, so I would like it to be easier to understand how and what to do with them.

With respect to the stability, on a scale from one to five, I would rate this solution between three and four. Sometimes there are issues where something is not working, although there are probably times where it happens because we don't know how to use the solution in the best way.

Both the customer support and technical support for this solution are very good.

The technical support has been very helpful. Our team has had many calls with UiPath regarding the virtual machine, which did not work at first. Within two days it was working.

Our clients did not use another RPA solution before this one.

They are undergoing a digital transformation and wanted to give themselves and edge so that the other companies will not get ahead. They just saw the need to change and we told them about RPA and they got very excited. We showed them the first pilot bot and they were ready to implement it.

Our in-house IT department handled the initial setup.

We have seen ROI and performance benefits from using this solution. While I do not have specifics in terms of money or time saved, I think that we could see the benefits after a week. There were processes that the client no longer needed to do, so they had more time available for other things.

For our first customer, we started with Orchestrator, an unattended bot, and a couple of Studio licenses, all of which cost $25,000 USD for the year. It is definitely worth the money.

We had researched Automation Anywhere and Blue Prism, but we didn't look too deeply.

The choice for UiPath was made based on what we read on the Internet, including the Gartner Report. It was very easy to get started after first downloading the Community Edition and then taking the Academy to learn how to do it. It is easy, fast, and the statistics say that it is the best.

Right now, this is a good solution that I would recommend. It is really beneficial for a lot of companies. At the same time, there are things that can improve and they are working on them.

I would rate this solution an eight out of ten.

We use only unattended robots with Studio and Orchestrator. Our primary use for the bots is in finance, so we only do finance use cases like AP (Accounts Payable) invoice retrieval.

The solution has improved the way our organization functions because no one has to sit for hours just spending time retrieving documents. The staff just picks up the documents they need in the morning, start their analysis right away.

What I find the most valuable about UiPath is flexibility in adding code. That ability is the most important feature for me and what I do.

In the next release of this solution, I would like to see better scheduling options. Because of the schedule limitations, you can only schedule one process at a time. There are situations where I might want to build five processes that need to work together. As I can only schedule one at a time, it isn't currently possible.

On a scale of one to five where one is unstable and five is very stable, I would rate the stability of the UiPath platform as a five. There are not many issues at all. On other platforms that we use, we always seem to encounter small things that cause problems. For example, with other solutions, we have had problems processing things like resolution and there is always an issue. But with UiPath, I can control almost everything from the robot and get it working.

There are ten people in our organization involved in our automation program and I think it can be scaled at any time.

While we don't use technical support directly, our team has used UiPath Academy RPA training to become more familiar with the product. On a scale from one to five where one is the least beneficial and five is the best, I would rate the Academy experience as a five. We've also used the forum. In all, between the implementation help, the Academy and the resources, I would rate the support as a nine-out-of-ten.

From the time we purchased the UiPath license until we had our first robot in production took only about one month, and that was without previous experience with the product. The initial set up of the product was straightforward, so it was all pretty efficient.

We did not need to use an integrator, reseller, or consultant. We did the entire implementation all in house. The only exception is that we did get some help from UiPath by working with them directly. 

We have experienced some return on investment and performance benefits, and it only took about one month to see it. There is one monthly process we use and in just one run — the first time we ran it — something that took two people two days was done in two hours. So, what took 16 hours to do analysis on before has been cut down to two hours. It is hard to say how much money that saved as we just changed the allocation of resources. The solution also helped to eliminate human errors which are even harder to account for.

We chose to try UiPath because we wanted to test the SQL capabilities that it has. I don't know that I would say we evaluated other options before choosing it as a solution. We currently work with both Blue Prism and UiPath at the same time. 

On a scale from one to five where one is very difficult and five is easy, I would rate the ease of use of the platform as a seven. I think that especially business users who don't have more of a technical background can get lost in all the different features that are available.

For this solution, we could totally deploy with attended robots, but our business just isn't ready for that yet. I think, with the adoption of Studio X that we might be in that position, but not right now.

On a scale from one to ten where one is the worst and ten is the best, I would rate this product as a seven overall. The scheduling feature just isn't there yet to allow more flexibility in programming and use, but the development is much faster and the flexibility better than much of the competition. The introduction of open-source changes the game for RPA solutions.

The advice I would give to a colleague at another company who is researching this solution or a similar one would be to clearly evaluate the use case. Don't just breeze through and assume you need automation. Take a good look at what you actually need to do, make sure the solution fits, and make sure the targeted processes are processes that should be automated.