UiPath Reviews

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 are a small but global company. We are about 1,200 people. We are a logistics company, and most of our employees work in our warehouses. So, our office workers are somewhere between 400 to 500 across the globe. Being a logistics company, we are maybe a little bit old-fashioned. There are a lot of papers going back and forth, and we are trying to automate different scenarios. We cater provisions to ships, so we are basically a grocery store for ships. 

One important thing is when a ship is going into port somewhere, they put in an order for whatever provisions they need for when they leave port again. So, we need to be quick at expediting their orders. When they put in a request for a quote for whatever products they need, we need to respond very quickly, because the tendency is that whoever responds first gets the order. So, we want to do that. We are trying to sort of increase the speed of those types of operations as well as the quality of them. 

It is hard to really pinpoint what it is we are doing, but it's the communication between customers. When we receive a communication from a customer, we want to move the process through our company as quickly as possible and with high quality.

We are fairly new to UiPath still. We do intend to use it company-wide and have started out with purely unattended scenarios so far.

We invoice every month quite a substantial amount of money to our customers. We saw a problem in that about 20 percent of our invoices were sent to the wrong addresses. That meant that, at month's end, when we were expecting money to come in, we would be missing around 20 percent of our cashflow that month. Of course, we wanted to prevent that because 20 percent of the cashflow of $300 to $500 million a year is a lot of money. 

We have automation that runs every night through all our invoices. Because we have some problems with our master data in the company, it does a number of measurements, on whether an address for an invoice seems to be the correct address, and a number of checks, such as, what ship was the goods delivered to? After that, it looks up information through the international registers of ship ownerships, then it will do a number of checks, giving each invoice a score as rating the probability that the address is correct. If it is below a certain threshold, then we will do some manual processing, and we are looking into UiPath Action Center for this. For four or five of our largest branches in the US and Asia, we have seen a significant improvement in the payments at month's end, which has definitely improved our cashflow.

The administration is a SaaS solution, which helps to minimize our on-prem footprint. The only things that we have running on-prem are the machines running the robots. Everything else is handled in the cloud. We don't need to worry about backups, etc.

We are adopting as much as we can some of the things that should reduce the maintenance costs. We are using Robotic Enterprise Framework in our development and Automation Hub to sort of qualify our ideas. So, we are trying to implement a uniform way of doing things throughout the lifecycle of an idea. UiPath supports this fairly well, and I think it will get even better.

Just this week, we are launching our Automation Hub effort because we need to start building a pipeline for our automation candidates. Right now, we have eight or nine ideas in our Automation Hub. That will grow quite quickly because we need the help of Automation Hub to decide on which idea that we will be moving forward with next.

UiPath continues to add services to the Portal. It is fairly important that they are all managed from the same place because it is a single point of access, which was a factor that really played into our choice of vendor, UiPath. We use Automation Hub to sort of collect ideas and discover what ideas are good for information, then we use Orchestrator to manage them once they have been developed. We are hoping to use Insights at a later point, when that is available in the cloud, so we have a complete end-to-end solution in one place. 

Automation Hub is an immature product. We have only been using it seriously for about a week and have already seen some things that will give us a few headaches down the road. We are committed to using it and will continue to use it, but I have some suggestions for improvement. We have been in contact with our local UiPath office about that, and their initial response was positive.

We would like to see more detail and refinement. It is still a young product, and we are confident that the product will improve a lot over the next few months.

We are hoping for some integrations between Automation Hub, Orchestrator, and Insights.

We are missing a way to quantify that money isn't everything with this solution.

Our license was activated sometime in July. So, we have been using it for about six to seven months.

We have seen a few quirks here and there. Overall, we are satisfied with the stability.

We have only a couple of handfuls of automations running, which are very stable. So, we are not doing much maintenance at all. Maintenance needs half an FTE, if even that.

The potential scalability is really good.

I don't know what the scale is for UiPath Portal. There are still signs that it is a young product, but we see it moving and improving at a really good pace. So, we have high expectations.

The technical support has been good. I have only used them a couple of times. The response has been good. They are knowledgeable. 

One of the big reasons why we chose UiPath is that it has a big following in online communities. It has a good forum itself: Forum.UiPath.com, but I really wish that UiPath would have moderators in their forums who are more active. There are a lot of questions that go unanswered, and that is a shame.

We didn't previously have any other automation solutions in this company.

Our initial setup was very straightforward. Our deployment took only a couple of days. We are a small operation with only two unattended licenses. We created the Orchestrator account and installed the robots on two servers. 

As far as development goes, we really just have the base package. Then, we are adding on Automation Hub right now.

We did engage with their local consultancy. They sort of helped us build a strategy for the infrastructure structure setup and strategy, as far as how to identify candidates, operations, and development. However, initially, we just wanted to pull the trigger very quickly. We had an evaluation phase of a couple of months, where we were testing different products and had tried to set up UiPath before, which helped.

We have used Carve Consulting, and our experience with them has been fantastic. We are working with this third-party consultancy to have them come up with a couple of ideas for some solutions that would involve AI Center for the end of this year or next year.

The initial deployment needed just a couple of people from our side, including me. I worked a little with some of our infrastructure guys, getting the accounts set up, the service division, provisions, etc.

We just haven't scaled to a point yet where there has been any kind of return on investment.

There are not very many users because the stuff that we have automated so far has just taken work off people's hands. Where a person used to spend all day uploading pricing data into a database, we have a bot doing that now. So, people are not using UiPath, they have just sort of been relieved of their duties. While that sounds bad, we have made an effort to find areas where FTEs get to spend time doing what they are best at.

The licensing is too expensive. It is not a cheap product. We constantly have to build business cases where we have to justify our existence as an RPA team. 

We have engaged in a long-running licensing agreement because we believe in the product.

We have used a third-party consultancy, and that's definitely not free.

We looked at a local variant of Kofax RPA called SmartRPA, which was built by a Danish company. It is basically Kofax RPA with an Orchestrator service built on top of it. We evaluated that. We also looked at something called OpenRPA, mainly due to price.

UiPath is built on top of Windows Workflow Foundation, which is a platform that I have worked with previously. So, there was a lot of familiarity and extensibility. Then, we looked at how good the product is at automating desktop applications. There was not really a contest there; UiPath was better by far.

The fact that this is a SaaS solution very positively affects how fast we are able to innovate when it comes to automation. When we did the evaluation of what product to choose, UiPath versus something else, the ability to assess deployment of the whole administration was a key factor.

In our decision to go with UiPath, it was very important that we didn’t have to worry about future installations and upgrades of Orchestrator. We just didn't want the trouble of having to do upgrades. With UiPath being a young product that is evolving very quickly, we would be doing on-prem upgrades every few months and we don't have time for that. So, we liked the idea that it is a cloud-based setup.

Security was a factor in our decision to go with the solution. We didn't look into all the technical specs and certifications. We just looked at some of their customers, and said, "If that bank is using it, and it is used in the defense industry, then they know what they are doing." They had good references.

It is the best product.

It is an automation product. At the end of the day, it is software development. If there is anything that is important in software development, it is that you have a defined process from beginning to end, from the birth of the idea until it has been put into production and eventually retired. So, you need to have a defined process for different stages in the lifecycle that you need to be in control of. The product somewhat helps us do this with Automation Hub and the Robotic Enterprise Framework, but we are looking forward to even more tools for stuff like that.

So far, we are still in the meat and potatoes space. We haven't really gone into the AI or Document Understanding stuff yet. 

UiPath Portal is good overall for enabling administrators to work with Orchestrator. I have seen a lot of improvements, even in the last six or 12 months. We are learning as we go. For the first few months, we were working in a classic folder. Now, we are adopting modern folders in order to better be able to scale our efforts.

UiPath provides granular, role-based access control and management. Right now, that is not so important to us because we do everything unattended. So, we have a couple of service accounts that run everything. However, once we move into attended scenarios, then it's really important that we have that granular control.

I know that there are some new features coming out in regards to deploying automatically and elastically, but we haven't looked that much into them. We don't expect them to be a problem.

We are looking forward to doing attended robots, but that will probably be in the second half of this year when we start looking into that.

For the size of our company, we started fairly big. We went all in, buying licenses, consultancy hours, etc. We have spent a lot of money this first year. I would probably advise someone to start small but still be ambitious. Do a lot of PoCs and see how it fits into your organization. There needs to be a lot of disciplines surrounding it, e.g., if you just stay with five or 10 automations, then things are good. However, once you build 100, you start running into maintenance problems and things like that, so there needs to be a discipline. 

You don't need to spend a million dollars to sort of get off the ground, so I would advise people to start small.

I would rate this solution as an eight (out of 10).

I'd say our finance applications, like accounts payable, have been our biggest use cases for this solution. 

I would say just the ability to be able to go outside of the IT department in our organization to get things done and have a sort of agile group to do automation. It is difficult to get IT involved in this type of thing in our organization. So being able to have our own agile group is beneficial for us.

Another thing that is valuable is that I think it's just saved a lot of our finance and customer service people a lot of manual time on processes. We are just able to involve a lot more value-added work.

I really liked the insights dashboard. I guess that there is an additional fee for that. Being able to see your return on investment in real-time is definitely beneficial. We spend a lot of time manually calculating how many hours we saved and that would make it a lot easier. The improvement I want is already there. I have to look into implementing it.

The area of the solution that has room for improvement is the stability of the bots. It just seems like we have spent a lot of time trying to fix bots that are down and whether that is our coding or the product. I think there must be a better way to diagnose the issues and avoid them.

On a scale from one to five, five being the most stable, I would rate the stability of the UiPath platform as a three. We've had a lot of issues with bot stability. I don't know if it is how we go about development or if it is the platform itself, but we spend too much time trying to fix all the bots that seem to be breaking.

I have not used technical support personally but our IT group has. Everything I have heard about the customer services group has been positive.

I have used the UiPath Academy RPA training. On a scale from one to five where one is the least beneficial and five is the most, I would rate the UiPath Academy as a four out of five. I'm not an IT person, so would have given it a five if I was. Parts of the training may have been more advanced than I expected.

We had a lot of archaic processes in our company — a lot of paper-based processes — so we knew we needed a better solution. That meant we had to work through a lot of processes and re-engineer what we were doing. We knew that we needed to move in the direction of automation because the processes were just not sustainable. We had processes but we did not actually have an automation solution until we started using UiPath.

The initial setup for the product was something I found to be a bit complicated. At least the first couple were pretty complicated. It was just that we were all new to the technology and we didn't really know necessarily what we were doing. It is getting better. From the time we purchased the UiPath license until we had your first robot in production, I think we took about three months.

We did you use an integrator. It was EY Technologies (Ernest & Young). They helped us out a lot and our experience with them was good.

We have certainly seen a return on investment. As far as how many months it took to see real value, I think we just crossed that threshold. So it was about twelve months in total. We have probably saved — just at our platform — around $100,000. The solution has also helped to eliminate human errors with a couple of the bots that we've deployed for sure. It has also saved our organization time. If I had to estimate, I'd say probably 8,000 hours a year so far.

We looked at Blue Prism, Automation Anywhere, and UiPath. We kind of landed on UiPath because it just seemed like it was a little easier to navigate than the other ones from a user experience.

Currently, we do not run any of our bots in a virtual environment and we use only untended bots so far. Either of those situations could change at any time. We have a couple of processes that we are looking at for attended processes, but we haven't implemented any yet.

We have about five people involved directly in the initiative. On a scale from one to five where one is very difficult and five is very easy, I would rate the ease of use the platform for automating as a four. It is a four because I would say it takes a little time to kind of get up and rolling for a developer, but it is not too bad.

On a scale from one to ten where one is the worst and ten is the best, I would rate this product a seven. We have just had some issues with keeping bots up and running. I feel like the issue is the learning curve.

The advice I would give to a colleague at another company who is researching this solution is to just do it. Make sure you know what processes you are going to want to automate. If you need to do standardized anything in the processes, do that on the front end in the planning stages versus kind of chasing your tail on the back end.

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

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.

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.

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.

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.

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.

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.

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.

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.

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

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.

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.

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

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.

We use all of the UiPath products: UiPath Studio, Orchestrator, attended robots, and unattended. Primarily, we use them for financial liquidation. Our customers frequently use it for different cases. Some use it with chatbots.

Sometimes, our customers run automations in a virtual environment. In terms of implementing UiPath within a virtual environment, UiPath staff are working on the cost. Currently we have UiPath with a Citrix client and you need to go to the Citrix virtual station to activate. It's more difficult to implement as a user.

Our customers' organizations have involved about 15 to 20 people in their automation programs.

I would rate its ease of use as about four out of five. It's not so easy, but it's also not difficult. We have a great UiPath Academy and it's really useful and helpful. Sometimes we need to do difficult operations and use other frameworks, through activities in UiPath. I think this mechanism is very nice, but in implementation, the customers are pretty close. Sometimes we must do it.

This solution helps to eliminate human errors. The amount depends on the process and the customer. Even unattended robots don't provide 100% automation. Sometimes a robot interrupts and waits for a human to make a decision. There is a process when unattended robots do fewer steps and after ten interruptions are waiting for a human to go on. I would say there is about a 70% reduction in human errors when using an unattended robot.

UiPath also helps save time. One unattended robot works 24 hours a day because a robot doesn't get ill or need to sleep.

All of the features are valuable. I think the best feature for Russian government customers is security. Security in Orchestration for requiring credentials. Our customers are usually serious about security.

I would like to see more AI features with data classification and computer reason. I think it would be great to have more features in full monitoring robots.

I would rate their stability as four out of five.

In cases of high scalability when we have one process and many of us use that process, we sometimes have problems. When one process uses about 24 robots for 24 hours, we have problems with it. I think when many robots work at the same time, something goes wrong in orchestrating tasks between robots.

I am happy with the support. For me, it's okay.

The initial setup can sometimes be complicated, depending first of all on the environment, as well as the implementation strategy of the company. Too many processes or only one PoC could lead to a more difficult implementation. Sometimes, customers try to automate a lot of the big processes. When we try to automate the complete process, we understand with the customers how many FTEs you can get from it. Everything depends on the customer's requirements.

It takes about six months from the purchase of a UiPath license until our customers have their first robot in production.

UiPath is a data mining solution. Our company tries to explain why RPAs are useful.

I don't know which other solutions our customers evaluate. Kofax might be one. Sometimes we work with a customer to make a decision about which platform to choose. Sometimes we do a PoC for Blue Prism. In the Russian market, there are two major vendors that are competing against each other: Blue Prism and UiPath. Usually, customers go through a PoC to choose the best vendor. UiPath wins because you can automate more processes with it.

I would rate UiPath as nine out of ten.

We have done work for customer success by collecting information from various sources such as email, IVR, and chat. Our solution performs classification, sentiment analysis using the AI of UiPath, and then data validation and posting. We've implemented this for one of the biggest banks in India.

Our admin team benefits from an internally created ticketing system, which offloads repetitive tasks and improves performance. This facilitates time savings and enhances overall satisfaction within the employee base.

Customers find numerous features of UiPath valuable, including Document Understanding (DU) and AI functionalities. They leverage it for repetitive tasks and beyond.

Customer education is crucial. Currently, there's a time lag in training, which eventually impacts the customers. All stakeholders should receive updates simultaneously.

We have been a UiPath partner for more than six years.

We face no major challenges regarding stability.

Investments in hardware are necessary for scalability, especially when dealing with AI and audio functionalities.

The UiPath support team in India is excellent, offering professional services and tech support. I rate it eight out of ten.

Positive

We've been using UiPath from the beginning. We were also Automation Anywhere partners but decided to stick with UiPath.

While it's difficult to quantify precisely, we've observed a 10% to 20% cost savings.

Pricing is high, affecting renewals significantly. Many small companies are hesitant due to the increased cost compared to past discounts.

I would rate UiPath an eight out of ten.

My company delivers projects to clients based on their requirements. We use the tool for web and UI automation.

UiPath reduces human error. If you implement the correct logic and exception handling in your code, it's seldom wrong. The solution saves time compared to other tools, especially when you are trying to automate something that's complicated. It simplifies complex processes and makes my work easier. 

I like the Orchestrator and the AI Center. The AI Center has many pre-trained models you can adapt to your requirements. You can train your AI or upload your own model as well. You can use the AI to extract the information from structured or unstructured documents.

UiPath is easy to use and implement. The tool has so many capabilities that we can use without using any code. Everything is there, and it's a low-code solution. We only need to drag and drop the elements and apply the logic.

The UiPath community is helpful. Most of the questions have already been answered on the forum, and you can easily solve your issues there. I've done the UiPath Academy courses. I took the fundamental course and the advanced developer course. I also received an associate developer certification. You can develop a complete understanding of the tool and its capabilities using the Academy. 

UiPath's processing speed is a little slow. That's its only drawback compared to other tools. 

I have used UiPath for about two years.

UiPath is highly stable. 

I have used Microsoft Power Automate and OpenRPA. I believe UiPath is the best because of its capabilities, but I also think Power Automate is nice. Power Automate has robust integration with Microsoft platforms. That's one thing I like about it. 

I found the initial deployment to be difficult, but it became easier once I gained some experience. UiPath doesn't require any maintenance unless there are changes on the website that cause the bot to not work properly. You can find the issue in the error log. 

UiPath is a costly solution. Many of the clients choose another solution after hearing the price. 

I rate UiPath ten out of ten. UiPath is the best tool on the market, but the licensing cost is high and many clients don't have the budget. They prefer other tools like Power Automate, OpenRPA, and Automation Anywhere and all that. Otherwise, it's a great product with more capabilities than the other tools.

We have a lot of use cases for UiPath including automation of processes and reconciliation.

Building automation using UiPath is easy.

It helps our operational efficiency by saving time and reducing costs. Manually processes that take an hour can be done in five minutes using UiPath.

The most beneficial feature of UiPath for our workflows is the seamless database connectivity.

UiPath facilitates end-to-end automation for well-defined processes. This eliminates interruptions caused by manual steps within the workflow.

The UiPath User Community is large. There is a lot of interaction and sharing making it easy for us to find answers to any issues we may have.

The biggest benefits we have seen using UiPath are the cost and time savings.

It has helped save around ten percent of costs.

The UiPath Academy courses are great. They have a lot of helpful courses.

UiPath has reduced human error by 70 percent.

UiPath excels at integrating with a wide variety of systems, including on-premises systems, legacy systems, and web pages.

The high cost of UiPath licensing significantly reduces the value we get from the solution. A large portion of the cost savings we achieve are negated by the licensing fees.

I have been using UiPath for four years.

I would rate the stability of Uipath eight out of ten.

I would rate the scalability of Uipath eight out of ten.

The technical support is great with the premium service for enterprise-level clients.

Positive

I'm certified in Automation Anywhere and currently use Microsoft Power Automate. However, UiPath seems better suited for enterprise-level automation. Unlike Power Automate, UiPath is system-agnostic. It can connect to any system, regardless of platform, making it highly versatile. On the other hand, Microsoft Power Automate prioritizes integration with other Microsoft products. Connecting legacy systems with Power Automate often requires purchasing premium connectors and potentially hiring an expert for configuration.

The deployment took around two weeks to complete.

We engaged Deloitte as our consulting firm for the UiPath implementation. While we handled a significant portion of the on-premises work ourselves, their team provided some technical assistance. Overall, I would rate their services a six out of ten.

UiPath promises a 50 percent reduction in operational costs, but the high licensing fees may consume most of those savings.

I would rate the cost of UiPath eight out of ten with ten being the most expensive.

I would rate UiPath eight out of ten.

We have around 15 users that work with UiPath for the attended bots.

UiPath Orchestrator requires regular maintenance and updates.

I recommend UiPath. The only negative area of UiPath is the licensing fees.