UiPath Platform Reviews

We use it for the automation of internal HR processes in our company.

It helps with the ease of implementing new logic from business requirements, which very rapidly change.

UiPath has also helped because fewer people are engaged in the processes we automate, and they can do more important things. It saves our staff time, on the order of 80 percent. In terms of employee satisfaction, I don't really know how they feel, because they are not in my department, but I believe that when you don't have to do such routine, repetitive work, you can have a coffee and come up with ideas on how to improve the automations. That is, by far, better than clicking and typing thousands of forms.

Also, there is less chance of a person making a mistake. If a given operation would take one person, for example, two days to do, the automation can do it in one hour, or even 30 minutes. It is very useful. We saw benefits with the first automation that was implemented, because it started to work and free people from routine work, within the first second of the automation working.

We have a lot of automations that involve filling forms on the internet and creating events in a calendar. There are a lot of fields to fill out. When creating these meetings, you have to add a description and pick the actual time. All this stuff should be done precisely, because if there is a mistake, somebody will not come to this meeting, or the information will not be applicable. Now the number of errors is zero because robots don't make mistakes.

We also don't need to involve the IT department, and we now have 15 automations. The group of people who implement it do the maintenance as well. We don't need IT and, actually, everything works fine without any maintenance. The problems come when there are updates, but the time needed for maintenance is very small.

Because we don't need to create virtual machines to install the solution on-premises, the cost is as little as it can be. Of course, we have to create several virtual machines for actual clicking, because the robot works the way a human does. But it has definitely helped with our on-prem footprint because we don't have to install the core of the system on-premises. I know, from my experience, that those kinds of core components take a lot of hardware resources. They would not require just one virtual machine; it would be a bunch of virtual machines. It is definitely very efficient to use the cloud solution from UiPath.

UiPath reduces costs because it reduces the time it takes to create automations. You don't have to write the actual code. You just build automations with higher levels of abstraction and you don't have to worry about what is done behind the curtains.

The best part is the way UiPath provides the ability to automate everything, including the architecture and Orchestrator. The interfaces are very user-friendly and intuitive. It's very easy to build automations. Someone who is not very technical can understand quite a lot and start to automate.

All automations are built starting with process analysis, then robot building, and monitoring. One person can gather the requirements, build the automation, and monitor it. This end-to-end coverage is very important. I can't even imagine how it would work if not in this way. This is the essential part of the automation: the idea, the implementation, and the maintenance.

UiPath's approach allows adding new workers, new agents, or robots to perform quicker and in parallel. For example, if you create two extra virtual machines with two extra robots, a whole bunch of operations will be performed three times faster. This kind of implementation is very convenient. And, we can change the way automations are deployed in Orchestrator and make it more efficient as well. We can do all these kinds of things really easily and quickly, like in minutes or less than an hour. That helps to scale things. You can change something in an automation in several minutes and deploy it or publish it in Orchestrator, and it already works. The challenge of implementing innovation can be addressed very quickly and very efficiently. The challenge is that we have to change our automations because other applications change with time. They have new user interfaces. But we don't need to upgrade anything to automate.

Several of our team members are studying the UiPath Academy courses at this moment. It has definitely helped because they get to know about new features that make automations more mature. One of my colleagues said, "As I read and study more in this course, I begin thinking more creatively and in more interesting ways." That means their understanding is growing and that it is changing their perceptions of what they can do with UiPath.

The information in the Academy is structured, starting with simpler concepts and moving to more advanced levels of knowledge, gradually. Also, you really learn about things you haven't used before. Thirdly, it leads you to the certification exam and getting the certificate on passing this exam. That makes you a good candidate for better jobs.

UiPath also has a very nice community of developers. When I face problems that I can't resolve by myself after several hours, I Google it in the UiPath Community and almost every problem can be solved by searching their resources. I work with different vendors and not all of them have such a big and open community. This is a real advantage. I'm not very familiar with other communities in RPA, but I can say that this community is, by far, more useful and more open than any other vendor's community I have seen.

I faced a problem when a new version of UiPath Studio didn't work with an older version of the packages that were part of our project. The problem is that when I have to change something just a bit, I actually have to rebuild the automation with new versions of these libraries. There is no backward compatibility. 

This question was addressed to an engineer from UiPath in the Community but I haven't gotten an answer. This is quite a hard question. So, I just create new automations with new approaches, which takes some time.

I have been using UiPath for about eight months.

The solution is very stable compared to other enterprise tools. Even if there is an error, if you handle it properly, everything works perfectly. From the point of view of UiPath developers, everything is done on a very high level.

It is scalable. However, to see the scalability you have to use the Enterprise Edition, because the Community Edition doesn't allow you to use more than one robot. But the mathematics are very easy: The more robots you have, the faster everything happens.

The number of automations will grow in our company.

I haven't used their technical support.

The initial setup was easy. It took a few hours.

We are using the Community Edition. The cost is only that of the virtual machines.

The pricing of the Enterprise Edition is a bit high. It's several thousand dollars a month. That's too much, because not every enterprise or organization can build such useful robots that will make it worthwhile for them to pay this much. Maybe the cost of the program could depend on the number of automations, or the complexity of the automations.

The solution is cloud-based, but you have to have some components deployed on the local computers. That is the architecture of UiPath, but the base of the infrastructure is in the cloud.

My advice is to just implement and begin automating. You don't have to even learn something before it, because everything is very intuitive.

I use this solution for mortgage loan origination, loan servicing, and IT administration. I'm currently using version 21.

We use the solution on-premises.

UiPath saves us a lot of time, which translates into operational cost savings. We saved around $40 million in operations last year by operating 140 bots in production. UiPath saves us costs, improves compliance, and helps with scaling up and down our operations.

We use attended automation but not on a large scale. We have three or four bots.

Attended automation improves our ability to automate processes that are more complex or involved. We use attended automation for use cases that involve websites that require actual users to log in. It's really helpful because a lot of use cases deal with federal websites and external websites where we need to download client information, credit reports, and fraud reports. That kind of information can only be done by a human, so attended automation is necessary for those types of use cases.

Right now, we aren't completely into AI. We explored document understanding for text extraction, and we know the capabilities. We haven't even started our ML journey, at least from the RPA automation perspective. They're still in the robotic process, so we haven't moved to include automation.

This solution speeds up digital transformation and reduces the cost. It gives leverage for the teams to transform digitally, because the traditional digital solutions take a long time to set up. It can take a few months for a solution to be in place. That requires expensive or complex application upgrades or IT application support to support the digital transformation. If we wanted to add a new app that would have oversight of all the loans being originated, it would take between two to three months to build UIs, dashboards, and all the features around it. With UiPath, the same kind of overview can be set up quickly: within two to three weeks.

The solution absolutely reduces human error. Most of our use cases involve looking at the input data, doing calculations, and updating fields. That always needs to be done by a human, day in and day out, continuously throughout a work shift. This RPA solution reduced that piece of human error drastically. I would say that more than 99% of human error is reduced.

The solution freed up employee time so they can work on other useful tasks. That's one of the main advantages of this solution.

Some of the processes have to be performed after hours and over weekends. When those tasks are automated, it gives valuable work-life balance back to our employees so they can do something useful with their time. The main ROI is saving manual effort, which is how we reduce our operational costs.

We see improvements in saved time, cost, quality, and risk production.

Attended and unattended automation, which support web and email automation, are the most valuable features for us. Building automations is easy and quick.

The solution enables us to implement end-to-end automation, starting with process analysis, then robot building, and finally monitoring automations. 
We aren't using the complete suite, like Process Mining, Process Insights, and UiPath Insights, but we use custom tools. Having end-to-end coverage of all these processes in one platform reduces cost and makes maintainability very easy. 

We use Kibana Dashboards with UiPath Insights, which was introduced within the last two years. For process analysis, we still use a traditional business analyst type of setup, but we don't use Process Mining. It's something we are exploring.

We use the academic courses to train all of our new developers and also upscale ourselves with new platforms. UiPath Academy is a single source of training for our team and it's free. We also hire college developers and new developers from other teams who want to work in RPA. We recently started StudioX citizen development. Academy is where citizen developers can get trained quickly.

It covers all of the various products, and it's easy to search through courses. We can skip different sections and get to the part we're looking for.

The UiPath community is a big and vibrant community. I think contributors are being rewarded for their contributions, and that happens in an organized fashion. That's the reason why people are so actively involved in contributing to the community. I would say that 90% of our development queries are answered in the community forum. It's really good compared to other platforms.

There are a lot of AI and ML-based enhancements that could be included in the core product and activities. Right now, there are plugins available from external vendors like Microsoft and Google. If those AI and ML activities can be provided out of the box for developers to use, that would really help the product go from an automation RPA to one automation suite.

I have used this solution for four years.

The latest versions are pretty stable. I haven't seen any issues with stability.

It's scalable. If we have enough bots, we can quickly scale up and down. If it's on the cloud, it's easy to scale up. If it's on-premises, we need to set up the machines, which takes time.

It can take a long time to get a response from technical support. They have to go through multiple hoops to get a solution, so that could be improved.

I would rate technical support as five out of ten.

Neutral

For the initial setup, we needed UiPath's support team to be on board. On-premises setup is always really tough. I think the cloud version would be really easy to set up, but we haven't explored that.

I would rate this solution seven out of ten. 

It's a pretty robust solution. When it comes to automation, it's pretty easy to set up and easy to use. My advice is that the cloud version is the best way to go forward when you're setting up UiPath.

We're a blockchain company that provides finance and analytics solutions, so we have multiple use cases, including organizational process automation. We do some end-to-end automation and automate some repetitive tasks. In the future, we plan to target some advanced processes like blockchain and machine learning. 

One example of a specific use case is market auditing. We are auditing our sales team and plan to audit our customers. This entails inspecting data produced by two third-party platforms, Salesforce and SAE, and combining that data into one Excel workbook to perform some calculations. We perform some analytics and then export the data from Excel to our CRM. Transferring the customer data to our CRM is incredibly time-consuming because we deal with more than a thousand lines of data. It takes a minimum of two hours to upload all the data to the portal.

UiPath helps us extract the numbers from the CRM side and share them with our marketing and financial team. This involves four processes that we combine into one automated endpoint process. The reduced workload across the three involved departments translates to cost savings equalling about 2.6 FTE monthly.

Another use case is to promote our components, services, and products. We are building a promotions portal that is attached to Excel. The promotion will involve maybe 500 line items and multiple roles. While you can do this manually, there is a significant potential for human error that could mean a loss of revenue. For instance, if we accidentally offer the same customer two discounts, we have to honor that. We haven't had any errors using UiPath in the last six months. 

We have three offices in our country, but the solution is deployed on a virtual machine in the head office. If a branch location requires process automation, we automate that solution at headquarters, and all the infrastructure is centrally managed. The primary users are six people from my team, including me, a business analyst, a developer, and three consultants. There are also two people from another group managing the UiPath infrastructure. 

We use UiPath Action Center, a capability that allows us to engage businesspeople and incorporate them into our automation. In total, we have about 12 to 15 people using UiPath, but some of them have limited privileges. 

Management prepared a presentation last week detailing how we've benefited from the start of 2021 to June 2022. We uploaded 149 processes into our unattended environment, and the robot runtime is 15,028 minutes, so we saved 75,114 hours. In the last year and a half, we saved the equivalent of 43 full-time employees.

 We have automated many tasks that would've been done manually, and we are reassigning our employees to other valuable tasks. This translates into a cost savings of about $98,000 for the last two years. Performing repetitive tasks is also demoralizing. If you're constantly performing representative tasks, your motivation level very goes down, so keeping our employees motivated is an added benefit. 

I am not an experienced developer, and working with UiPath has taught me a lot. We use UiPath Orchestrator with a combination of unattended and attended bots. That functionality allows you to manage your platform virtually. You can monitor everything and assign new roles to users. 

I would like to see more native AI and machine learning functionality. UiPath doesn't cover all the options for a few tasks that we require, so it's hard to do advanced automation. For example, UiPath chatbots are one area where machine learning capabilities could help. Users ask the robot questions, triggering those kinds of processes. 

We started using UiPath in September 2020.

UiPath is a highly stable solution. We haven't encountered any bugs, downtime, or other issues since we started to use the solution. We also don't experience any instability when working with components in other projects. 

UiPath is a highly scalable solution because some of its capabilities can be used in other projects. This means we don't have to rebuild the solutions we have already developed. With the help of these solutions and features, we can reduce the development time. 

I rate UiPath support eight out of 10. Technical support is generally good, but there's one thing I don't like. UiPath support's technical expertise is impressive, but the response time isn't ideal. When you raise a ticket on the UiPath portal,  customer support can sometimes take up to 24 hours to respond. 

Positive

Setting up UiPath was highly straightforward because we had help from the vendor team. Our deployment team had eight people total, including me, a business analyst, a developer, and two IT people plus two people from the UiPath side. It took approximately one month because we implemented the UiPath solution on-premises. We had one or two technical meetings with the UiPath team and we needed to build some architecture. They suggested that we leverage our existing servers on Microsoft Azure and Google Cloud.  

Then, we integrated all those solutions on the UiPath side. We installed a UiPath solution in the dev environment where we were developing the processes and one in the live environment. We have more than 32 licenses, so we created 32 virtual machines on Google Cloud and Azure. 

Every organization needs to cut costs, and all customers try to negotiate a discount on licensing. When we initially tried UiPath, they offered a discount of nearly seven percent, but they haven't since. UiPath's price is a little high compared to other solutions, but it's easier to use and maintain. We purchased a three-year license.

We tried Blue Prism, Automation Anywhere, and another tool by IBM, but I didn't care for those solutions because they were too complex. UiPath is easy to use, monitor, and manage. Automation Anywhere and Blue Prism lacked some of UiPath's features. For example, UiPath allows us to maintain our environments remotely through UiPath Orchestrator. 

I rate UiPath nine out of ten. It's a great solution. I highly recommended UiPath over other automation tools I've used.

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

We are using the latest version.

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

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

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

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

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

The unattended automation helps improve our time management.

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

They could make the solution better by improving the latency.

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

I have been using it for a year.

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

We have not experienced any downtime or issues.

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

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

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

Positive

We did not previously use another solution.

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

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

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

I would rate UiPath as nine out of 10.

We are using UiPath as our RPA solution for finance, supply chain, revenue cycle, HR, and IT. At the moment, we're using it mainly for unattended automations of big jobs.

In the healthcare field, where systems often don't talk to each other, UiPath helps data to be shared between systems. My colleagues have been talking about that and there has been an improvement. That's important because it helps us to keep in line with one another.

Also, security and compliance are a big deal in our organization, especially because we are in healthcare, and we keep it as secure as possible. UiPath assists us with that in terms of credentialing and separation of duties. We don't take security lightly.

The tenant concept, where you can have everyone working in their own space, is valuable.

We're just starting to implement UiPath on a larger scale. We've been using it for about nine months maybe, so we're new to it.

We really have not had a lot of hiccups or anything that's been difficult. The stability has been good. On a scale of one to 10, I would give it an eight right now and that's only because we haven't really tested the boundaries.

The scalability is good. It's easy to do. It will get pushed a little bit more as we get more mature with the product, but so far so good.

We had a different solution prior to UiPath, and what we've really liked so far with UiPath is the way that they interact with us in terms of customer support and satisfaction. They're very in tune with what we need. They have a lot of experience in the RPA world.

Our TAM is Micah de Boer and our sales engineer is Mick Taylor. Our account manager, Garet Wright, has been outstanding.

Positive

We previously used Automation Anywhere. One of the reasons we switched was that it didn't seem to be as mature as UiPath. Another was that it does not have a citizen developer program or even the concept of a citizen developer. In addition, it didn't seem to be as stable. We had a lot of issues with the system going offline or having problems. And when it came to customer service, they were not responsive to our needs. It would take days for them to get back to us on questions or issues that we submitted.

Right now we are an on-prem model, but we are switching to a SaaS-based model in the cloud.

From what I have heard from my team, the deployment of UiPath has been much easier than the deployment of Automation Anywhere. It is much more straightforward, clearer, and easier.

The team that supports the platform is a team of just two people. Both are senior analyst programmers and they are responsible for the deployment and the infrastructure set up of everything related to the UiPath product. We have two other individuals on my team who are the RPA developers, the ones writing the bots.

The deployment has been pretty lightweight so far in comparison to what we had to deal with when we used Automation Anywhere.

We did it ourselves.

It's returning hours back to employees so that they can do more tasks that involve thinking, and not have to do so much mundane, repetitive work. That gives us a good return on investment because something that might have taken an individual an hour to do can be done by a robot in five minutes. It's definitely freeing up some actual work time for people.

We've saved the equivalent of five or six FTEs, and that's in the short amount of time that we've been using UiPath.

It has also improved our employees' joy at work because they aren't having to do some of the mundane activities that they had to do in the past.

Licensing allocations are easy. We also have the ability to have a robot license be fully utilized, meaning it can do more than one thing. If it's idle, we're able to use that robot for some other automation, rather than having a one-to-one relationship between automations and robots.

We just moved to their Enterprise licensing model and it seems fair at this point. It will be interesting to see where we are over the next three years and if we're able to show a return on that hefty investment.

One area that is challenging for me is tracking licenses. It would help to have a license dashboard so that we would know how many licenses have been allocated, who they're allocated to, and when they were last used. Right now, to gather that information, I have to go to four different screens in UiPath and then consolidate all that. A licensing module that we could look at from administrative and management perspectives, would be awesome. That's the main thing I have been hearing from my staff.

When we first chose our initial vendor, Automation Anywhere, we had done an RFP process and had gone through pilots. It was close in terms of which was number one and which was number two. When we discovered that Automation Anywhere wasn't meeting our needs, we contacted other folks who had used Automation Anywhere and had switched to UiPath and asked them for feedback and what their experience had been. We did some benchmarking with others around us to see what they were doing.

Comparing UiPath to what we had before, it has been a cakewalk. Be sure that you work with your leadership and with your IT areas to pick the best deployment solution for your company.

We haven't had an opportunity to use all the features and functions, but in terms of the robustness of the product and the communication we've received from our teams at UiPath, we've had an outstanding experience with them, and we really look forward to keeping that going in the future as we build out this program.

We work as a center of excellence and we develop automations centrally for other departments. All our deployments are unattended bots that are deployed and managed by us, centrally. They are all running on a virtual machine. Nothing is running on client computers or laptops. We do not have any attended use cases. The process owners are interacting with the bots.

We use the bots for a lot of reporting, including monthly and weekly reports. We are a construction company and we have a lot of reports for all kinds of things, such as construction projects, different construction sites, and various subsidiaries for regional departments. A region like Bavaria, for example, needs its reports. And there are plenty of controlling departments in all of the subsidiaries.

We also have some ticketing use cases. One of them is for IT services, meaning internal ticketing. That bot regularly checks our ticket software and automatically processes some of the tickets. For example, when an employee needs rights to a specific system, the bot checks whether they fulfill the requirements and approves or declines the ticket.

Another type of ticketing use case is more about processing customer tickets. As a construction company, we also do facility management, and that means there are a lot of external customers with their own systems in which they record tickets. The tickets are not visible in our local systems so someone has to go to the external systems, export the tickets, filter them, and then tell everyone what they're supposed to do to their buildings as a result. The tickets might be about small repair jobs, for example. We run this daily and, in the morning, everyone receives an email with all the tickets that have to be done within one day, three days, one week, et cetera.

Both of the ticketing use cases are connected with SLAs. If you miss a certain time frame before processing a ticket for external customers, you have to pay a penalty fee. For the internal tickets there are SLAs for internal tracking purposes. Because those tickets have to be processed within two hours, that bot runs every two hours and checks for new tickets.

Another IT services use case is for getting access rights to local drives.

We also have many recurring processes. For example, in HR they have to go to the system and confirm a process. It’s a necessary evil which is probably due to the legacy systems we have. Someone defined this process a long time ago and it still has to be done.

We also have use cases in finance and treasury. They are not tickets, but they process requests from employees. For example, they can request cash on a specific card and the bot will check the emails and then basically transfer data from an email, or from a PDF form attached to an email, and enter it into the finance system.

One last type of use case is where the bot works as an interface between systems. Data has to be exported from one system and imported to another system and there is no existing API. The bot exports and imports the data. We have one bot that exports PDF documents and sends them to an email interface. It defines a specific subject and then attaches the file. That file will automatically be uploaded to another system. Or the bot may log in to a system and upload the document. These use cases are due to the fact that there is no interface between two systems and they're either not big enough to develop an API or they may involve an external customer system and the customer has no interest in providing an API.

UiPath has freed up our employees' time and that's its main purpose. We don't have huge use cases, but for our bigger use cases it could be saving us 35 to 40 hours per month. With the smaller processes, people save about two hours a month. We have 23 use cases that are live at the moment and the total time saved by them is about seven or eight person-days a week. The big processes account for 50 to 60 percent of all the savings.

Employees have more time for more important things, but there are no direct cost savings from our automations. What we do have are a lot of efficiency gains and some time savings. Any cost savings are on the lower end of the scale.

The solution also definitely reduces human error. We have some processes that involve penalty fees if there is human error, so the reduction in errors has probably affected the business on a very small scale.

In terms of the cost of automations, before UiPath the whole automation process was much more complex. There might have been software providers involved in that process, charging us and providing APIs. And the whole process took way longer. Now that we have a UiPath license, the cost of implementing any automation is zero, other than our salaries, which would be paid anyway. The automation creation process is definitely a lot faster. It's also cheaper because there is no involvement of an external software developer, which is probably the most expensive part.

I like the REFramework. It's one of the unique selling points of UiPath because it gives you a framework within the software to structure your processes. It's perfect in terms of error handling and it provides a lot of functionalities for processing multiple transactions. It makes the whole solution more robust.

I tested the Process Mining at my previous company and I don't think it's suitable for RPA processes. It operates at a way higher level and, using it, you may find an area in which you can optimize a process, but it doesn't just give you a defined process for automation. It doesn't necessarily help you to identify the processes.

The Task Capture component offers the ability to record a process and it will give you process documentation. It tells you how many clicks are being made, and it will create screenshots. It tells you the basic activities that are being done in the process. When we tested it, the quality of these documents was very low. It took more time to take the output and make it useful than it would have taken to analyze and document the process ourselves. 

We are not using any of that. Together with the customer, we are manually defining and documenting processes. We are doing the actual automation, of course, with UiPath. In terms of monitoring it afterward, it's 50/50. Standard Orchestrator definitely offers you some ways to monitor your processes. It tells you how many processes failed and why they failed. You could also define a process that sends you an email when it fails.

UiPath also offers some BI components, but that requires a separate license and costs. We are not using them. The whole BI reporting functionality of standard UiPath is not that great. We use external dashboards in Power BI.

We also have a calendar application because, with standard Orchestrator, there's no overview about when you have bots running and when you have free slots. So it's also not great for planning license usage. The whole visualization piece, out-of-the-box, is not so nice. UiPath is mainly the automation tool for us, and it's definitely great for that. But in terms of analysis and monitoring, there's definitely still potential for the software.

I have been using UiPath for two and a half to three years.

Their tech support replies quite quickly. But when we had technical problems, most of the time, we had to have multiple calls. It's not that great. They definitely provided us with all the experts, but they just didn't immediately find solutions, most of the time.

It often took two to three days to fix our issues. We would have to explain the issue one or two times and then they say, "Okay, we need to do a call." After the call we would try out the solution but it wouldn't work and there would be another call. Support is another potential area for improvement.

Also, we bought our licenses from a UiPath partner. We are actually supposed to talk to them for support, but they charge for their consulting services. They are the reason we didn't have constant communication with UiPath. From my experience at my previous job, where we worked with UiPath, we were in close communication with the UiPath success manager. There was way better communication and support because we always had a channel that we could talk to regularly. And they already knew what our issues had been. If you are working directly with UiPath, the tech support is good, although not great.

Neutral

We did not have a previous solution.

I started in RPA with my previous company. My boss just told me to get into this topic. I started with the UiPath Academy before we were even using the software, but I could follow all the courses. It's all video training, so it's easy to follow. The Microsoft training often consists of long sets of text and it says "expected reading time is 23 minutes," but it's 23 minutes just to read the text. Now, UiPath even offers training exercises. 

And because they offer the Community version, you can download the full-featured software without actually having a license, for personal use and for training purposes. That way you can try out whatever you learn. That makes the learning very practical. And the Community version is not limited to 30 days like test versions of some other solutions. It's a version that you can use for testing forever and you can use all the functionalities. That definitely helped me when I did the training. That's how I got from knowing nothing about RPA to knowing a lot about RPA, before working with it.

If you have a basic understanding of the software, the most important thing is to develop with it, because that gives you practical experience.

They also have very specific, deep-dive courses, for working with Orchestrator, among other things. They're easy to find. You can invest two hours and learn the most important aspects of the UI and look for what you need.

With the Advanced RPA Developer certification, there is an exam. That is where I got the most practical experience. It's not just quizzes, it's also practical projects.

Overall, the Academy is great. It has training paths as well as very specific courses. 

UiPath is quite expensive and whatever additional components you want to use will have additional costs. We are not using the Document Understanding feature because of the cost. For Document Understanding, the cost may be per transaction.

Compared to Power Automate, UiPath is quite expensive to set up. What we are trying to do, and likely everybody tries to do this, is fully occupy one unattended-bot license before getting another one. So it's not just a matter of buying a few licenses, because they are quite expensive. That definitely also affects the return on investment, especially if you automate smaller processes.

Also, we are currently working with centralized automation development, but we are planning to decentralize it with citizen developers as well, for smaller processes. For that, we intend to use Power Automate Desktop because in that scenario the pricing disqualified UiPath. If you give a UiPath Studio license to many people—to fulfill the vision of a bot for every person—or even to one person per department, they would have to work quite hard to see a positive return on investment. 

For UiPath, you need Orchestrator, which is already quite expensive, although you can use just one to start with. But if you have multiple unattended-bot licenses and multiple Studio licenses, it gets expensive quite fast. 

Also, the whole pricing structure is very unclear. You can't find out anything about prices before talking with UiPath or with a partner. At that point, you're still not sure what kind of price you're getting. Of course, they offer savings when you order many licenses, but there's no fixed reference point if you haven't talked to UiPath before. There is no real information about what you actually need and how much you can expect it to cost. 

With the Microsoft platform, you can directly see the kinds of packages they have and whether they're charging per process or per transaction. You see the price. It's very transparent.

When I compare UiPath with other providers' solutions, UiPath offers a very structured development interface. It is more structured than the interface of Microsoft Power Automate, for example. It offers a very visually appealing way of structuring the processes in flow charts as well as in sequences. It makes it easy to see an overview of a process. I definitely like UiPath's development interface.

UiPath Orchestrator is definitely great, and better than what competitors offer because it enables you to use queues very easily, which again helps to create robust automations.

In addition, the UiPath community is the best among all the software communities that I've seen. There's a great forum. Whatever question you have will either be answered by other developers or even UiPath employees who participate in the forum. Also, there is already a huge stock of questions and answers about automation. Usually, you will get an answer to any question within hours or even minutes. Together with the training platform, the whole ecosystem around the community is much better than that of any other software I've ever seen.

In my previous company, we evaluated the big ones at that time: Automation Anywhere, Blue Prism, and UiPath. 

In my current company, we mainly evaluated two solutions. The first was UiPath, because it's probably the most powerful solution. The second was Microsoft Power Automate, which is now becoming more mature. Power Automate is probably also the easiest to implement because we are Office 365 users. We could just provide a Power Automate desktop license to any of our employees. It's definitely much easier to acquire Power Automate licenses and provide them to the users. It's directly integrated. There's no need for IT involvement.

In my opinion, UiPath is easy to use. Once you have been using it for a while, it's pretty easy. If you're using it as a citizen developer, meaning that you want to automate your own processes, it's probably a bit complex. It offers a lot of functionality and properties that can be edited per activity. You have to have a basic understanding of variables, arguments, et cetera, if you want to build a robust solution.

The macro recorder is not that nice. It's not like you can just record a process and then run it over and over again. It definitely requires some experience to create a robust process. All in all, I think it's easy to use. 

I also tried the StudioX version, just for testing purposes, and that may be a bit easier to use, but it's still not a tool that you can give to someone and they will be able to start developing on their own. In particular, they will not be able to run something unattended because that requires a lot of testing. It requires basic knowledge, which comes with experience, about the HTML selectors.

In general, UiPath is the most powerful solution there is on the market right now for RPA, mainly because of the easy structure provided by UiPath Orchestrator for larger transactional business processes.

We are working with automation, and it is very useful for my enterprise and our clients. We are using UiPath for building applications for automation purposes. Some of our clients are in the banking industry. They ask us to create applications to automate their processes, and we use UiPath for that.

Our overall productivity has increased because the bandwidth of our people has increased. Previously, when we were manually doing a particular task, it used to take us two hours, and after building the application with UiPath, the same task is taking around 10 seconds. From two hours, the time has come down to 10 seconds, which increases our bandwidth and productivity.

We are moving into robotics, and in robotics, advanced NLP and AI are being used. As tasks move from being manual to being automated, it definitely reduces the effort and improves productivity. The saved time can be utilized in a better way.

Its ease of use is valuable. For building an application, if I give this product to a newbie, he or she would be able to easily use it and build an application with minimum knowledge. No extra training is required. Its features are self-explanatory, and anyone can understand them, which is the main feature of this product.

I extensively work on the automation part, and I like the drag-and-drop functionality for workflows. Its graphical workspace or visualizations make it a unique product. It provides good visualizations, which are helpful in understanding the workflow. I am very impressed by its drag and drop functionality, and I would recommend it to everyone.

It can be improved in terms of platform integration. It is platform-independent, but it should be easy to integrate with different platforms, such as Windows, Linux, Cloud, etc. If I am using AWS for my server response, I should be able to integrate that into UiPath. 

If I can get some manuals along with the product, it will be good to see all the features that are available in it.

I have been using this solution for the last eight years. I have been in the software industry for about eight and a half years, and I have been using UiPath very regularly for my day-to-day work. 

Its stability is good. In the last couple of years, I didn't have any problems. I would rate it a nine out of ten in terms of stability.

We have a team of 30 to 40 people who use this solution. At this time, we don't have plans to increase its usage. If the usage of this tool grows, it would definitely be better. It will increase productivity and more efficient use of our company.

I would rate them a nine out of ten.

Positive

I have used Visual Studio previously to build applications. I switched to UiPath because I like its interface and the drag-and-drop functionality. When I am building an application using this, it's very easy to edit the flow. I am very impressed with UiPath.

I'm involved in the development and deployment of applications. I have the knowledge, so for me, it is straightforward. Most of the features are self-explanatory, but there are certain features for which a newbie might have to refer to the manual.

The duration varies from application to application. It can be anything from 30 minutes to six hours. For the development of applications, we use the SDLC model. When our testing is complete, we deploy the application. We have a team of six to eight people for implementation. They are from the product team and the support team. They are software developers at different levels.

In terms of maintenance, it requires upgrades. It is a timely activity, and it happens once or twice a year. We do not have a separate team for maintenance. The same team involved in its deployment takes care of its maintenance.

We are able to build applications for our clients, and they are also buying them. So, we have definitely seen an ROI.

We are an enterprise. So, its price is bearable for us,  but I am not sure about the small industry. It might be expensive for them.

It is a promising tool. It is very helpful for my day-to-day work. For automation applications, this is the best solution. Its drag-and-drop functionality and visualizations make the work easy. It is a very good tool for me.

I would rate it a nine out of ten because I'm very impressed with this tool.

We use the solution to speed up automation. We were looking to overcome the challenge of handling vast amounts of data, and we use UiPath to create bots to handle that. Tasks can be automated, and human error is reduced.

UiPath improved our organization as it has many benefits; it's straightforward and quick to use, has excellent third-party integration, and simplifies all our task automation.

The software has an excellent UI; it's very user-friendly. The drag-and-drop options are some of my favorite tools, as they speed up the process, and I find that UiPath offers a solution for all kinds of automation.

The solution saves a lot of time via automation; a task that took over an hour now takes around two minutes, and it's all handled by bots.

We use the drag-and-drop options, and they speed up our workflows.

The pricing could be more friendly. 

We have been using the solution for one year. 

The solution is stable, it's a reliable software. 

The product is scalable; it has very good third-party integration and scalability options within the software.

We use the solution in our office, so there are slightly under 100 total users.

The community support and documentation are helpful. I required some training initially, and was able to learn using UiPath websites and YouTube videos. 

Positive

I wasn't directly involved in the initial setup, but it took our team one to two months to get to know the product well.

I'm not directly involved in the financing, but the IT team considers this product costly.

I would rate this solution a nine out of ten. It's an excellent product, but there is always room for improvement. 

I highly recommend UiPath as it's easy to learn and offers significant advantages for all kinds of automation. 

The solution is perfect for our requirements. 

My previous company was in the banking sector, and we had done automation with websites, UI, SAP, Excel files, and PDF. In my current company, it is being used for finance and HR. We have ERP, CRM, chatbots, etc. We are using this solution to integrate different systems.

I use UiPath Studio to develop the code, and I use UiPath Orchestrator to publish my work. We have our own UAT systems to test the code. We can install the UiPath in the test environment and find all the compilation errors in the debug mode and fix them. We also have version control. If we upload a version and it doesn't work, we can downgrade the version. Everything is tracked in UiPath Orchestrator.

We are using it on-premise. In my previous company, it was on the cloud, and we accessed it through the cloud. 

UiPath Academy courses have been helpful for me. There were lots of activities that I didn't know about, and UiPath Academy was helpful for that. There are multiple ways to do an activity, and UiPath Academy helps you to find out those activities. When you start using it, you can find out which activity will work the best for you. The courses are interactive and not boring with just videos or PDFs. They have a mix of PDFs, videos, and interactions. It is fun and interesting if you have a passion for it.

I found the UiPath community very helpful. At the beginning of my career, I had lots of doubts, and I posted them in the community. We had got an unknown error, and we posted our query there thinking that there must be at least one person who has had the same issue. They solved the issue quickly. It was a quick response. If you post a question, sometimes, you can also get a response within five minutes.

I use attended automation, and it has helped to scale RPA benefits in our organization for processes that require human-robot collaboration. We have a process for reconciling bank statements. When the finance department is done with their files, they send them over to me by email, and I have to start the process manually from UiPath Orchestrator. It needs human interaction. It is a monthly process, and we don't want to automatically trigger based on something.

We use its AI functionality a little bit. We have automation for processing invoices that are in different formats. We are using an ML model to train and replicate the output based on the incoming PDFs. We don't have to manually identify the PDF format and process it. Its AI is very helpful in the case of dynamic files where when a PDF is in one format, we want to process it in a certain way, and when it is in another format, we want to process it in a different way. We have automation to automatically identify the fields and then process the documents accordingly. It is helpful in the case of dynamic files. 

It has reduced human errors. We have a process to send emails to the end-users based on the training they complete in our LMS. I did the automation, and the SME was very happy with that automation. She used to have lots of manual errors where she might miss one email id or put an incorrect email id. With the bot, we automated it and added exceptions, etc. It is more stable now, and there are fewer human errors. It is also very helpful for data entry work where there are lots of chances of human errors. All this can be avoided with a bot.

It has freed up employee time. The time saved depends on the complexity and the length of the process. For our LMS use case, the SME used to take around one hour every morning, and now, she doesn't have to do that. Even if she is on leave, our bot is available 24/7/365. 

The UI Explorer in the UiPath Studio is valuable. We can get a unique and dynamic selector for every element in the UI, which is helpful for me in finding out a particular UI element. Most of my automations have had UI interactions. So, I found it the most helpful feature.

It is pretty easy to build automations. I am from an engineering background, but even if you don't have much coding or programming knowledge, you can easily learn and use this tool. I used UiPath Academy to learn about this tool, and they have got a detailed explanation about everything. So, even if you don't have prior experience, you can easily use this tool.

They give updates every year. Before the new features go live, they put them out in the Community edition. When the features are stable, they release them. They have got a helpful community forum. If you have any roadblocks, you can post your question there and you will get a response, sometimes even within five minutes, depending on the complexity of the question.

When I started working with UiPath, there were no activities for SAP, but in the version that I'm using right now, there are SAP activities or SAP modules. Previously, I had to code everything from user login to user logout, but now, all the activities are available. I just have to drag and drop and give the username and password. I don't have to do it from scratch. It would be great if they can include activities for all of the most common CRMs and ERPs. They can integrate it with different activities for the most common systems.

I have been using this solution for around five years.

It is mostly stable. We recently upgraded our UiPath Orchestrator, and we stopped receiving the emails that we used to receive in the morning about the status of our bots and jobs. I created a ticket, and they said that the particular version or update that I had wasn't stable. They provided me with a different version that was stable.

It is great. In my previous company, one single bot was doing all the processes. In this company, we have six bots, and every day, around 50 processes are running. So, it is scalable.

For the email issue that we had, we created a ticket, and they responded the next day. The response time was less, and they also provided me with the correct solution.

Positive

When I started my career, I started working in Python and website development with Django. When I heard about UiPath and RPA, I felt that it is going to be the future. So, I switched to RPA. UiPath is the first tool I used, and I'm still using it.

I have used Power Automate from Microsoft, but I found UiPath much better because it has a single package with UiPath Orchestrator, Studio, etc. It has everything in a complete package.

I have also used Blue Prism. Blue Prism is more expensive. I used its Community Edition recently because I wanted to explore other tools, and I felt that its UI is not as good as UiPath Studio. They both have drag-and-drop functionality, but Blue Prism is not as user-friendly as UiPath. I have never used Automation Anywhere, but I have heard from my peers who are from the same background that it needs programming knowledge.

It was a bit complex because we have two virtual machines, and each one had three robots in it. We had to do remote desktop on the virtual machine to run the automation. We have recently improved all the processes in our company. They are now dynamic, and they can run in the background. Even if the virtual machine is closed, they will run.

It was implemented in-house.

We have definitely seen an ROI. It replaces the manual work and allows us to do other productive tasks rather than doing repetitive and manual tasks every day. If someone costs $50 per hour, and we are able to save one hour of manual work every day for that person, it is a substantial saving.

It is a bit expensive, but it is cheaper than Blue Prism. We have six robots in total. There are no other costs in addition to the standard licensing fees.

I love this tool. They have been improving it every year based on the user experience, or they have been releasing a stable version for any bugs.

I would rate it a ten out of ten.

We are a consulting company and we work for different clients. I have mainly used UiPath for financial processes, like bank and vendor reconciliations, order management, order processing, collections, and invoice processing.

UiPath automations have saved a lot of man-hours for business people. They used to have to do simple tasks, like creating reports in Excel and calculating with formulas. We just uploaded the data into SQL Server and then connected to Power BI through UiPath. It was a small project for us, just a matter of two minutes or so to put things in place, but it saved them a lot of time. With the bots doing this "small" work, it enabled the employees to relax and work on more valuable tasks.

The employees involved have been happy and they have also suggested a few other processes that could be automated, after seeing the results.

There was also an order management project in which we extracted details, such as delivery date and quantity, from a PDF. Before it was automated, that was a tedious task. It took a lot of time for people to do it and their accuracy was lower than the robot's. The automation reduced the team size for that business and they were very happy. They saw a very good ROI. And it used to take the business much longer to do small reconciliations, but the bots are so fast. They are seeing good results. It has reduced a lot of human error. Initially there are some errors, but once you learn from them and train the bot, you get accurate results.

We have only done a few attended automations, but they have sped up processes that require approval. In those situations, they play a major role. More than the monetary savings, the benefit is that people can concentrate more on the important work, and with less stress. But unattended automation is the most important process.

The OCR makes it much easier to extract the details, as does Advance Document Understanding.

I would also rate the ease of building automations as an eight out of 10. It's quite easy in general. In some cases we need to use a coding language like Java or .NET, but we can easily build simple or medium-level tasks. It's even accessible for business people. If we try to explain the code or the architecture of our design, they're able to easily understand.

The UiPath Apps feature has helped to reduce the workload for our IT department by enabling end-users to create apps. Even some of the business people have been trained to do that. They have been able to build small, attended bots.

And when it comes to minimizing our on-prem footprint, I would also rate it at eight out of 10. We have seen good results from our on-premises build.

And if we are not sure about something, we can get help from the UiPath community. I have worked throughout the whole cycle, and in all aspects we get good support. People voluntarily contribute to the community. It is a vast community and we get answers quickly. UiPath itself helps people connect and they give badges and goodies to people who are contributing well.

Initially, it was mandatory for us to get certification through the UiPath Academy. The course is free and even the business people have been interested in upskilling themselves. All the Academy courses are very good.

I have been using UiPath for over three years.

The stability is good, but they keep upgrading versions. If you want some of the new additions, sometimes you have to take a beta version.

The scalability is very good, and with the latest version it will be much easier.

Almost all our departments have used UiPath automations. Management is trying to identify what else is possible. It's spreading to all our company's departments.

Whenever we have an issue that we cannot solve, we contact technical support and they try to identify the issue and give us the best solution. If we give them our machine IDs, they try to get into the machines and resolve things. Some of our cases were really complex, and they visited our site. That was the best part.

Positive

The initial setup was straightforward. It is a little technical but not very complex. The deployment time depends on getting all the prerequisites in place but it usually doesn't take long, about two hours, on average.

Maintenance depends on the complexity of the automations. You have to monitor things regularly.

The ROI is very good. We have been able to deploy many processes and upper management is pretty happy with the investment they have made in the bots.

Compared to other solutions, the pricing is moderate.

We compared UiPath with other tools and then we made the decision to go with it. A few of our clients use other tools, but in our experience, UiPath is best. It is much easier to use, compared to the others.

We referred to industry reviews and we had discussions with peers and colleagues. I did some research into the market and then I chose UiPath.

Automation will enable you to concentrate more on the things that require decision-making and knowledge, rather than just doing repetitive tasks.

As we have upgraded the versions, it has reduced the time involved as well. Initially, it was taking some time. But once we and the whole business got used to it and understood how the bots work, things went way faster. The solution is improving every day. It has already moved to the cloud and it should start working on IoT because they have started with AI. That will make IoT will be much easier.