UiPath Platform Reviews

We have deployed a chatbot in our system.

Designing a chatbot would usually require some language coding and it would have to be deployed with certain front-end languages. But UiPath gives us the ability to automate this functionality with drag-and-drop features. That is the very best part, where UiPath is doing an amazing job. It doesn't require any language coding or front-end coding to create the user interface.

Because it is easy to use, it saves a lot of time for the developer. When it comes to programming, UiPath has made all the manual work, such as verifying and correcting errors, and even repeating processes, less complex and less time-consuming. If you were to try to choose a coding language and use it to streamline things and design a bot for automation, it would take more time. Doing that would take 15 days to learn the language and to code with it. There would be a certain number of errors that you would have to deal with, as well. There might also be a backend required. UiPath can easily save you 10 to 15 days, automating in two to three days, maximum.

It gives you the ability to automate workflows and large processes that would take a long time to do manually. With the help of UiPath, the time it takes to get those tasks done is reduced and it reduces human error. In addition, it saves you money because you don't need to hire people for the tasks that have been automated.

There is also the benefit of not having to hire an engineer to program things. If you had to hire an engineer there would be the expectation of a payment package. There would also be the time spent on dealing with errors the engineer makes, and this person might also require mentors. UiPath decreases the spending of time, energy, and money, especially.

UiPath also saves our organization time because the automation cloud handles infrastructure, maintenance, and updates.

One of the most valuable features is that it provides you with the ability to learn the system and understand the concepts through specific demos. UiPath provides you with education, through the UiPath Academy, on the basics of how to use the software and for what purposes you can use it. It is a very good thing that they provide education with it. That makes it easy for us, as developers, to gain the knowledge we need.

Another good feature is that it comes with an embedded recording functionality. You didn't require an external screen recorder. The embedded screen recorder enables you to record things so that you can remember them over time.

In general, it is easy to build automations using UiPath. You just drag and drop according to your needs, and you can automate things in a single go.

One thing I don't like about UiPath is that it does not have a very good user interface for a newbie. It's not that the user interface itself is bad, but when I started using it, it was very difficult for me to understand the tool and how to use it. It has N functionalities and a user has to learn the particular things that these functionalities are used for.

The user interface should be a little simpler than it is right now, as it is very complex.

I have been using UiPath for more than a year.

In terms of scalability, this software can grow with the industry, especially since more companies are focusing on automation. Here in India, for example, there are many companies, like KPMG, focusing on the field of automation. Software like this can help them to scale more and more in building their automations. The software can really scale up well, as long as the user interface is improved.

Their support system is very good. If you have a problem and you reach out to their support system, they are quick to reply. Problems are solved within 24 hours of reaching out to them.

Also, you can use the UiPath user community instead of contacting support. There is value to the user community because people help each other there. Because we are concentrating on development in my company, we tend to not be as active on the community side, but whenever we do use it we get help from them.

I have only been exposed to this software. I graduated and started working in the RPA domain by using this software.

It wasn't that complicated to set up. 

The pricing and licensing are pretty decent. If you are using it as an automation developer, it comes in at under $500 a month. Still, the pricing can be reduced, but the service and functionality are solid. 

I have heard from some of my colleagues that there are many subdivisions of the pricing and some of them are between $1,500 and $2,000 a month. That is expensive. But overall, my colleagues say it is a cost-effective program in the long run.

If you are working in the RPA domain as an automation developer, you should look at UiPath because it gives you many functionalities. Also, the education aspect of UiPath is a very cool feature because you don't need to rely on other software to learn it. Thirdly, the bot-building process is very smooth. 

UiPath is a fast, time-saving, money-saving, energy-saving solution. Using UiPath has been the best experience. I would recommend it. You can choose this software without any second thoughts. It can provide a good return on investment to your business.

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 have a web application, and we also have iOS and Android applications. We are automating the regression testing part for these applications. Mainly, we are navigating and interacting with UI elements, and we are verifying certain buttons. We are also verifying certain data with RDBMS outputs.

UiPath enables us to implement end-to-end automation, starting with process analysis, then robot building, and finally monitoring of automations. UiPath has been doing well in terms of Orchestrator and how we can see the execution and the reports and results of our test cases. It is doing well in these aspects, which is very important for us. We are doing end-to-end automation and monitoring using Orchestrator, and it is quite useful. This is something that we were looking for while deciding on the automation tool that we would like to go with, and that's why we decided to go with UiPath.

It has been helpful for regression testing. We are developing a big web application, and we are expecting changes every quarter. The development and deployment have been going on every quarter for the past two years. Previously, we had a team of seven or eight people who were doing the manual testing. By automating the testing, we have reduced the team's size to half. The remaining team members are not just analyzing the executions that we are doing with UiPath; they are also providing support. It has increased employee satisfaction because they don't have to do repetitive work again and again. It has been quite good.

It has been useful for unattended automation, and it has also reduced human errors in our organization. Reduction in human errors is the best benefit that we have got from the UiPath implementation.

Automation is most valuable. When it comes to web automation, data scraping and UI-related activities, such as the Find Element activity, are quite useful.

UiPath Academy courses have also been very useful. Whenever we have to work on something new, I go to UiPath Academy and browse all the resources that they have provided. When I started working with OCR about two or three months back, I used UiPath Academy courses. They are very helpful, especially for new people who join the team. New associates need exposure to the tools that we are using, and the content that is present in UiPath Academy is quite good. It gives them an idea about the tool and the things that they can do with it. UiPath Academy has been quite helpful in training new associates.

UiPath is developing day by day, and there are certain products, such as AI Fabric, that UiPath has launched lately. These products are quite new to most of us in the RPA industry. Because there are courses available for these products in UiPath Academy, we are able to get an idea about a tool, its capabilities, and how to use it.

There is a big room for improvement when it comes to mobile automation. The Find Element activity is not present in mobile automation. There are activities to extract data, but we don't have data scraping in mobile automation. These activities are available for UI automation of web applications, but they are not available for mobile automation, which is a drawback when working on mobile automation with UiPath.

There are also so many bugs in mobile automation. I've been working with mobile automation for the past six months, and in the past six months, I have found so many bugs. We have reported them to UiPath. Some of them are posted on the forum, and I haven't seen any positive feedback in terms of whether a bug has been created or they are working on improvement. So far, there is nothing like that. 

There is also a bug related to the Pick Branch activity, and we can't really work with the UI elements in this particular activity. This issue was first reported by someone in 2019, and this post is available in the forum. It has been more than two years, and this bug has not been fixed. 

For mobile automation, there is a tool provided by UiPath called Mobile Device Management (MDM). We do the automation using that tool. In our project, we are using cloud APM services. UiPath Studio communicates with MDM, and MDM communicates with Sauce Labs, which is the cloud APM service provider for us. There is a huge gap in the synchronization of both of them. I have observed a visible difference. When I execute an app activity, it gets executed at Sauce Labs very fast. The final output that we should be getting first comes to MDM and then UiPath takes that output from the MDM, but there is a synchronization gap. There is a visible difference, and UiPath is lacking in this part. So, mobile automation is the part where UiPath can improve a lot.

I've been working with UiPath for almost two years. I'm into development, and I have worked on Excel automation, mobile automation, and web automation.

I don't have any opinion on its scalability at this time. In terms of its usage, we have to create 2,000 automations for our client, and we have already implemented more than 1,000. We don't run those automations every day. We run them as per the requirements, so there would be 200 to 400 processes once a week.

In my project, there are five people who are working with UiPath, but in my company, there are many more people. One of them is the manager, and four of them are working on development. 

There have been some bugs for which we connected with UiPath support. It was a mixed experience. There were some technical support experts with whom we connected, and they tried to get to the root of the trouble. They did their best to provide us with the best solution possible. We have also had other scenarios where there was no answer or explanation for the issue. We didn't get any positive feedback from them.

I had posted a few queries related to mobile automation on the UiPath community, but there was no instant solution. I was expecting a reply within one or two days, but there was no reply. Because this is a niche field, there are not many people working in this domain, but I got replies from the UiPath team on some of the queries. So, overall, the experience was good. I would rate them a six out of 10.

I was not involved in its setup.

It reduces the cost of digital transformation in a way. When it comes to the scenario of our automation, UiPath isn't so fast, and there is the speed issue that UiPath can fix, but because a bot has the capability of working 24/7, there is a reduction in the cost of digital transformation.

We evaluated Blue Prism. We didn't explore Automation Anywhere. After comparing it with Blue Prism, we decided to go with UiPath. As per our client's requirement, there were three applications to be automated, and because UiPath supported web automation and mobile automation for iOS and Android, we went for UiPath. We just had to buy the license for one, and we could automate all three applications.

Rather than implementing RPA on a big scale, I would advise starting at a small scale and doing good process task mining. It is very important to identify the right process to automate.

UiPath is quite an impressive tool. It was the first tool that I started learning when I got into RPA. Recently, I got familiarized with Automation Anywhere. I used to think that Automation Anywhere is better because it is on the cloud, but now that I know that UiPath also has a cloud option, I'm going to explore that option. It is a good solution, and UiPath is doing well when it comes to the improvement of the product. My experience is good overall.

We have not used AI-enhanced Document Understanding in our automation program. We are planning to implement it, but it may take a while.

I would rate it an eight out of 10.

We've used it to automate most of our processes. Our organization is completely technology-driven and we have been able to automate a lot of our processes with UiPath. The main thing that we are using it for is document creation with multiple fields and approval processes.

We're using it to automate daily tasks, using small bots for multiple processes. In the long-run, they're actually connected together. A lot of people have left our organization in the past couple of years and, instead of hiring new employees, we actually try to build a bot for whatever the work those employees were doing.

By not replacing employees who have left, we have been able to achieve our aim of running a lean company. We are able to save a lot of money on HR costs as well as on the costs of hiring new employees.

In addition, our document-processing time has been reduced for every customer that we are catering to, and that has resulted in great ROI as well as customer satisfaction.

We have compared the performance of humans with the bots who replaced them as they left the organization. The humans were making a lot of errors compared to the bots. The bots are not perfect and they do make their share of errors, but they are quite different from human errors. Everything is logic-based, and everything happens with triggers, so the possibility of an error is minimalistic when something is being handled by a bot. That is especially true for a bot that is created with UiPath because it's so mature. Overall, there are hardly any errors that come out of the bots made with UiPath.

Another benefit comes from the UiPath Academy courses. It saves us on training costs because we don't have to develop the content for training new employees. We're not product experts when it comes to UiPath and the Academy delivers training in a fashion that is easy to understand. There's a lot of support provided with the training courses as well. Not only does the Academy help in terms of training-development costs, but it has minimized the duration of training for each employee who starts to use UiPath. The results are great savings for the organization, both monetary, through automation, and non-monetary when it comes to training.

The AI and machine learning that are built into these bots really help us to make bots at a mature level where they're able to track with real-world customers. They also help with employee engagement and business productivity and take them to a whole new level. Obviously, we cannot develop such technology from scratch. We used built-in processes and automations in the past, but once we found, first when we were using Automation Anywhere, and now while using UiPath, this type of technology, it really took over the technology suite that our organization had been using previously and replaced it completely. UiPath is a complete suite that can handle most of our needs by itself.

Document creation is one of the most important features for us. As a healthcare company, we have a lot of documents with complex fields. For example, if a treatment is booked by a customer in another country, a lot of paperwork has to be completed. That paperwork first goes to the healthcare provider and, once accepted there, it comes to the company to be approved by the management. Then it goes back to the customer.

In addition, the process has been integrated into mobile apps. That way, a senior manager gets a request on the mobile app and to approve the transaction they just have to press the "Accept" button and everything else happens on its own. All of that happens in a matter of seconds.

Also, the UiPath Academy courses are very user-friendly and enable us to achieve a lot more. Those courses have taught us a lot, especially for our new automation employees. Once the basic courses are completed by any new employee, we actually recommend that they complete the certifications that are available via UiPath, and some of them are actually free of cost. Only after completing certification do we allow them to work on the floor. We have found the Academy content to be really amazing in terms of design as well as its functionality. We have made use of all of the courses there are.

The UiPath community has grown quite a bit, but it's still not on par with the kind of support that you would find with Automation Anywhere. That is still missing because UiPath is a relatively new entrant in the market. The community support is growing, but that is definitely one of the areas that can be improved.

Also, sometimes there are failures in the cloud during migration. Say you're migrating it from one instance to another instance. There are failures and there's not much support for such cases in the UiPath documentation. While it is a rare instance that we need to migrate, whenever we do have to migrate, we generally face some issues. I feel that there are bugs in that area.

We've been using UiPath for about three years.

The platform is really stable. There's never been a point when it's been unstable or has had runtime issues. There have been really minute server crashes, unexpectedly. But I don't think that is due to the platform. It is more due to the server environment and the hosting environment not being configured properly. There are no problems whatsoever in terms of the stability as well as the performance of the product.

The product is very scalable. It is meant for scalability. It is specifically meant for a situation where there are a lot of tasks that have to be completed by and it automates everything. Even if large volumes of data and tasks have to be completed with lightning speed, that is exactly where UiPath fits in. It does the job beautifully. That is the reason it was able to replace the whole technology suite that we were using, a suite that consisted of different products.

The technical support has been great. The only issue that we've had is that there aren't enough specialized support people who can help with the server issues. Configuring Google Cloud Platform with UiPath can be challenging. There were some errors that we were not able to figure out on our own. There are two support teams that we could reach out to, either the server support or the UiPath support. Sometimes both of them were confused about what was causing the issue. And sometimes, it takes more than the anticipated time to resolve the issue. But overall, UiPath provides great support.

Positive

At first, we were using a completely in-house technology system. After that, we used Automation Anywhere for a couple of years. But once we started using UiPath, we were able to replace that completely.

The initial setup was fairly easy. We've been using the Google Cloud Platform to host the entire automation platform and there isn't much documentation for deploying it on GCP. There are a lot of settings and configurations that are location-specific and that relate to the load and the number of bots that you are going to make with UiPath. There are a lot of things that come into the picture and the documentation is not up to the mark.

To sum it up, it is a little difficult, but not impossible to deploy it initially.

It only takes a few days but it depends on the complexity of the kinds of bots that you plan to run with the platform. Certain bots could take time. For that situation, there are consulting services. Also, there are certain bots that are already there as a template and you can customize them. But if there are processes that require a custom bot to be built from scratch, that could definitely take time. That could take from months to a year if it's a very complex bot and you're creating it with an in-house team.

Our implementation strategy was to take one step at a time. We had designed a complete project deployment roadmap, in which we had certain milestones that we planned to achieve within a few months. There were then more milestones that we planned to reach within a year. We did have to take on some consulting services from UiPath partners for the customized bots, but that resulted in the development costs being reduced, as it went a lot faster than it would have gone without the consulting support. It has gone pretty smoothly.

Apart from the consultants for the customized bots, the initial deployment was completely handled by our in-house team. There was a fair bit of documentation provided with the system itself and we found it sufficient to take care of the initial deployment.

The ROI has been really excellent. We're able to save a lot of costs that were previously paid for subscriptions to multiple suites of software. We were able to save all of that and invest it into one product, UiPath, as well as into development of the bots.

The ROI has been very positive for us. The main issue is that there is an initial investment that you have to make. Once you do that, the ROI keeps on growing year-on-year. For us, it has only been three years. If we compare our costs and ROI over a longer period, I'm sure we'll see a lot better ROI.

The costs are related to infrastructure and development and, of course, at a later stage, include monitoring and maintenance. If you compare all of that over a longer period of time, you'll see savings of anywhere between two and 15 times compared to an equivalent system, over a period of about five to seven years.

Another area with room for improvement is the pricing. Initially, the pricing was a lot more affordable. Now, it seems a bit excessive.

Get an estimate of the cost from UiPath sales representatives. Don't just include the UiPath cost, but also the consulting costs that you might have to pay, and the number of licenses that you might need as an organization. The third thing to consider is the development cost of the bots. All of that has to be considered well in advance.

I don't think there is anything that UiPath bots aren't able to do. But be aware that the budget could become excessive by using UiPath because there are so many different costs that come into the picture. You could require trained employees, people who have previous experience with UiPath, to develop bots that are a custom fit for your organization.

Cost would be one of the things that I would recommend that other organizations consider in advance to see if it suits their budgets. They should also consider whether they have the resources that can deploy and design bots that are able to automate the tasks and the processes that they want to automate.

Apart from UiPath, we also used Automation Anywhere. The reason we use UiPath far more than Automation Anywhere is because we have been using it for some time and we have some resources who are quite well-trained on it. It suits us pretty well. It has automated most of our processes and really kept our system moving. Whatever issues we have had with the product have been very well resolved by the customer support team in a very timely manner, and that is another reason we prefer UiPath over Automation Anywhere.

You need to have resources who are trained in UiPath. You could take the initiative of training employees, but you need some senior resources who have prior experience with UiPath who can be project managers and guide the development and analyst teams on how to reach the goals that the organization is trying to achieve.

UiPath was a fairly new product when we started using it. They were giving a 60-day free trial and were also providing free certifications for that initial period. That is how we started with it. Over the years, we've seen that the UiPath community has grown quite a bit. From being a new entry in the automation market, it has grown into a very mature product and it has now taken over as the main system that our company is using. We rely on technology to support our backend processes and we need a system that is very reliable in terms of delivery. UiPath has turned out to be a system that works out very well for us. The UiPath community really helps whenever there are bugs or glitches that our company is facing. You can reach out to the community where there are very senior developers as well as analysts and you can get a lot of help there, apart from the customer support.

It runs in its own private cloud in the Google Cloud Platform. We have some projects that are run on UiPath that are given to independent contractors to work on. We give a contractor a license for the system and they have to install UiPath on their computer and complete whatever work they have to complete on that. But for our internal organization and employees, we have a private cloud over which UiPath is running.

The biggest lesson would be to just take one step at a time. Make use of the partner support at the beginning. Initially, we tried to build everything ourselves and that cost a lot more than it would have if we had used consultants. There are companies that provide consulting support and there are companies that will actually build your bots exactly to your requirements. That way, you can just deploy them from day one. They also provide maintenance and support for the bots they have developed for you.

The first use case is related to our email process. We need to download multiple attachments in the form of PDF and Excel files from emails. We only accept the PDF files into a specific folder, while the Excel files go into another. We split them based on the file extension.

The second use case is related to the retail domain, in which we need to update an application with data that we get from a client. We process a few Excel operations and then update all of the invoice records in the application and generate a PDF invoice form with the client's details from Excel. That PDF is then emailed to the client.

With UiPath automations, work has been made easier for our employees. Previously, people were working on those processes manually. Now, they can concentrate on other work and on improving their skills in other areas. They have also improved their knowledge of RPA technology. There are time savings and we are more profitable. For just one of our processes, we have saved approximately 20 hours per week.

We are also able to deliver the output to our client easily. When things were processed manually, there might have been errors, but with the automation, they have been reduced as much as possible. Bots don't think about other topics while they're working.

In addition, while I haven't used the AI functionality of UiPath very much myself, my colleagues do use it, and it has enabled them to automate more processes overall.

But the main thing, when it comes to our business side, is that the solution helps to reduce the cost of digital transformation. In terms of ROI, it is helping the profitability of the organization. It has helped to reduce the employee count, has sped up the delivery of solutions, and it has helped us obtain more clients. We can generate more output, good results, in less time, enabling us to improve the overall expectations of our clients. Our cost savings have been greater than expected and the business team is more than happy with the results.

There is also the issue of employee satisfaction. Using myself, as an example, I feel very happy about developing and monitoring the results. It is satisfying to see that a process is working as expected, and that the results are more accurate compared to the previous manual work.

UiPath has enabled us to implement end-to-end processes. That's important because we don't want to depend on third-party tools. With UI Path, all the resources are within the application for generating an end-to-end process, so we don't have to struggle to develop such a process.

In addition, the solution doesn't require much infrastructure. We can easily install and operate the tool in a Windows environment.

I also did the Advanced RPA Developer course in the UiPath Academy. I learned how to create end-to-end implementations using the UiPath tools. The course helped me to develop my skills. In the course within the Academy, you learn about every command in UiPath. It is easy to learn the information very quickly, when compared to other learning resources. The Academy has all the resources for regular, advanced, and master developers.

When it comes to document processing, they could work on more accurately identifying objects from PDF files.

I have been using RPA tools, such as UiPath, for the past four years. We are using the Enterprise version.

With the help of all the dynamic options in UiPath, the stability of the bots has been very good.

We have deployed automation solutions for a lot of our clients in their environments, and they are happy with the results as well. There are more than 100 users.

The technical support has been very responsive. They provide very accurate answers to our inquiries.

Positive

Our business side has been happy with the ROI, compared to other vendors.

Our business team looked at other tools, including Blue Prism and Automation Anywhere, before selecting this tool. They were much happier with the results generated with UiPath than with the others.

The main differences are that UiPath provides a more efficient implementation and it's easier to monitor the results. It's also more efficient when it comes to analyzing a process. Compared to other vendors, implementation takes less time with UiPath.

I can recommend UiPath to others. It will make their work easier. It's very easy to learn and to run the tools compared to other automation options.

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. 

Our primary use cases are within the financing and HR teams right now. But of course, there's a lot of opportunities in the clinical space and with MB services. We have use cases in all of those departments throughout the organization, but right now we are engaged primarily with the HR and finance team.

We have two automations in production right now. We just started our COE and it's been exciting so far. We are building things and have identified quite big end-to-end opportunities. 

I'm not new to the automation world. I've been in this field since late 2015 and I've seen the ROI you can get with it. Some things you can quantify and others you can't. However, we are very new to UiPath so I can not comment on improvements just yet. We will know within a year. 

We have seen savings in time. One of the automations that we have in place with our finance team is a monthly reconciliation process. The first three to five days of the month are critical in finance. So, if you're able to save as little as half an hour every day in those five days, that adds up to a full day of work. This automation has helped our accountants and the finance team do their closing and be on time and have extra time to analyze things. They're not fighting fires anymore.

The partnerships that UiPath has with other vendors are excellent. Some of the applications that we rely on heavily, like DocuSign for Workday, already have built-in integrations with UiPath. This will help us scale and go to market quickly. 

I am happy that they are always listening to us and doing as much as they can to include more features. 

UiPath could work towards more engagement on the community practice side. Some of our people are having a hard time understanding how to make sense of the data that UiPath puts out. 

There could be some guidance as well on how to calculate ROI. ROI is how much money you have spent and how much you are getting back. But, how can I know how much money I've spent? Do I calculate the cost of infrastructure? Do I calculate the cost of the team I have? Where do I begin? What is the right way to look at ROI? What are some of the analytics I should be looking at?  

Utilization, the success rate, business value, and ROI have to go hand-in-hand. You cannot tell a whole story with just ROI. 

I have been using UiPath since March of this year. 

My impression of UiPath's stability is good. Compared to some other automation vendors that I've used, I would say that UiPath is more stable and better. 

We do not have a lot of experience with them but whenever we reached out to them they helped and directed us. 

The initial setup was straightforward. It was on-premise and run-of-the-mill. Our team is very knowledgeable and had already done similar implementations. 

We had four people engaged in the implementation from our side. We partnered with EmiTech for the deployment and they brought in their expert and helped guide us through the installation process. 

I do not fully understand our pricing model yet, but I would say that it is fair. I cannot tell at the moment how it is going to affect us. Right now we have only six unattended bots and maybe two attended ones, so we will see how it goes as we grow. 

The ease of building the automations depends on the process, but overall I would say that UiPath is intuitive. If you understand some basic functions of logical expressions or loop functions, UiPath is intuitive enough to help you build some impressive automations. It is easy to pick up.

We have a few people who have completed UiPath Academy courses and are now going for advanced certification. I'm not planning on building any bots on an enterprise scale myself, but I am going through the training as well. 

UiPath Academy is excellent because it is intuitive. Of course, you have to have some development or SDLC knowledge, but it helps tremendously. You get so much insight on the features. You also get to build a small automation. I dedicated 30 to 40 hours to the trainings and was able to get some knowledge from it. 

The trainings are even easier for people from accounting, for example. They are used to macros, automations, and file transfers. Conceptually, they are already there and with a tool like UiPath Academy, they can start using the solution. It's important to just stick with it.