UiPath Platform Reviews

We use attended and unattended bots, Orchestrator, and Studio for development.

We're seeing increasing adoption of Studio because more people see how easy and straightforward it is to use a lot of the features. It helps that UiPath training is free. Our entire team, including our salespeople, have gone through the training. It's free and it makes a big difference. For the salespeople, they're able to talk more intelligently about RPA.

On a scale of one to five, judging how beneficial it is, I would rate the training a five, for sure. In fact, I have taken a lot of ideas from their training to educate my customers about RPA. When it comes to RPA, a lot of it is education because some of them don't know exactly how automation can be done. I've told UiPath that I use their training in my presentation, and it is great.

We are working with a technology company called Rammer, Rammer.ai. What the Rammer software does is listen to conversations to learn the details of what is being discussed. A third-party system is used to transcribe the conversation into text, then Rammer will learn the details without much training. It knows the topics, it understands what is talked about the most, talked about the least, how much we are adhering to the script if it's a call center use case, or if it is a simple meeting use case then it knows who is assigned what tasks, it recognizes the follow-ups, and it knows the summary of the discussion. All of this is summarized in a nice, consumable manner. So now, when a bot knows all of this information, it goes into Orchestrator, logs all these activities that are picked up by unattended bots downstream, and they trigger all those processes back. So it's a massive consumption of all of those heavy use cases.

We have not yet run automations in a virtual environment, although we do have customers who are asking for it. We are not sure if we will need UiPath's help for this yet because we haven't tried it.

With respect to how easy it is to automate our company's processes, on a scale of one to five, I would rate it a five. Really, it depends on how clearly we understand the requirements. So a lot of times we are able to find process gaps, which wasn't the case earlier before we started thinking about automation in this manner. I would say the ease of use is actually dependent on some of those factors as well.

Usually, starting is the biggest challenge for most people, and I think this is because it is in a trial environment and there is a lack of documentation, with multiple people doing one part of a small subset of a task. There are these challenges and then if none of them are documented, you need to figure out the process flow. From person one, where does it go? This can change when people can do multiple things.

It becomes a very complex web to understand and navigate through. We need to understand the task and how it should be performed. For developing the robot, it's very important to have the clarity upfront, otherwise, we cannot code them. That is the biggest challenge, I feel.

From the point that a UiPath license is purchased until the first bot is ready is almost immediate. This is because we usually start with a PoC on a small scale, just to see if automation with this approach makes sense. By the end of the PoC, we'll normally know exactly how many bots are needed. Sometimes it is on us, more than the customer when we cannot estimate every process that is outside of the departments and division that we work with because we just work at finance. For example, we can't just estimate what marketing would use, and so on. That will sometimes delay things.

The attended and unattended classification and simplicity are great, and it's easy to explain to people. Right off the bat, the task performing the lowest granular entity is very clearly defined, which is something that I like.

I really like that I am able to tell the story, using Orchestrator, how humans work, how bots work, and how humans and bots work together. Orchestrator really tells a lot more than just being a simple task manager.

In future releases of this solution, I would like to see more packaged solutions.

We would like to see intelligence built into the core. Specifically, we would like to see the recognition of human to human conversations. That intelligence would be great because we have some very important use cases in that space that we are seeing. Our focus is moving closer to one hundred percent in that space, as all of our new work is related to conversations.

UiPath should offer an on-demand cloud-type model where you can get bots for five minutes, ten minutes, an hour, or whatever duration you need.

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

We don't see many failures, and this is partly because of our approach. We start by creating something called a heat map, which I learned in some of the training from UiPath. The training clearly explains how to handle errors. It includes which process to automate fully and which processes should be automated partially, with a human in the loop.

We start with the right approach. We understand the process and we have the heat mapping that gives us full clarity of where the exception flows are and how to handle them. So when you do that, it becomes second nature to handle those exceptions. We are pretty comfortable, and we are applying the best practices, which adds to the stability. 

Talking about our own people, we have roughly sixty-five who are either developers or architects. For our customers, the number is growing all the time. The requests for training and setting up workshops for them comes to us every week, basically from different customers. We don't know the extent of automation beyond the people we work with because there are other vendors like us who are also there, so we don't have the exact number but what is refreshing to see is that even VP level or senior-level employees are interested in learning. They ask us if we can hold a workshop for their entire team, whether they're doing the development of bots or not. Hopefully, that will increase the numbers, but right now I don't have an estimate on the total number of customers. I only know on our side.

We have tremendous support from UiPath. We can say that from our perspective, we are very fortunate to be in the Pacific Northwest and that team is one of the best. It doesn't matter if we are big or small, they help everyone. So every time we have an issue or a challenge, whether it's engineering, presales, architecture, or development, we get all the support.

Our customers usually don't know much about RPA, so one of our jobs is to educate them on it to get them interested. Gradually when they understand, it moves forward.

In the majority of cases, the initial setup of this solution is simple to medium in terms of complexity. We are finding very few complex scenarios at the moment.

I think the overall architecture is simple. It is very clear and very straightforward. UiPath's product team is doing a great job in is creating a lot of very out of the box integrations and analytics, and that always helps. That is good, but I think if people are not trained yet and they think that it's easy, drag-and-drop, and simplistic, those folks struggle a lot.

We've seen that people think "Oh yeah, it's just some scripts and drag and drop so we can do this easily" and that misconception exists. We don't treat it as an easy scenario, so we gave it all the respect that proper Python code, a data science problem, or a highly complex situation deserves. When you approach it that way, it's at best at a medium complexity.

In general, we treat it right in the middle. It's not that straightforward, but the architecture is simple enough that the development complexity is medium. That's the simple and medium combination.

When it comes to ROI, for some scenarios it's immediate on the day you go to production. Doing the math, if it is automating thirty hours of work in a week, it is going to be the moment you turn on the switch.

Sometimes when the expectation is set at a different level, the KPIs are different. It may be that the customer is looking to have an "X million" dollar cost saving. It just depends on how you're defining the KPIs. So in those scenarios, obviously it'll build up to that saving.

A lot of people talk about the total cost of ownership as being a real saving or real value for products. So there are just all these different layers of complexity in that. I mean in theory it is immediate at the moment you turn on the switch, but then you need to consider the bigger picture, and it's not a straight answer. It'll be different.

The most important tip that I would share with respect to the licensing is that you should not think of a bot as being able to do only one thing. You should always consider the downtime and utilize the bots properly. That's the way you can have exponential ROI from just that one simple investment.

Even though these bots don't really cost much, you still want to say there are resources like a dedicated machine that is there, there are electricity and all kinds of resources that also go into it. So the overall cost, we should look at that. If a bot is doing ten hours' worth of work in five minutes, there are twenty-three-plus hours work that the bot can actually do. So, think of orchestration.

Some of our customers have tried different solutions. There are some customers who have even tried a lot of competing products and they're not satisfied. They have a very low expectation from what automation should or could do. So for us, that's even harder in terms of educating them.

People who don't know anything about this kind of automation, sometimes it's a little bit simpler to just run them through an hour or two of our workshop, but people who already know about it may have set their mind in a certain manner. Sometimes for those customers, the customers with experience in other solutions, are usually a little bit more difficult to convince. They have doubts that have come about because of whatever they've been using, and they don't fully understand the capabilities because UiPath does things very differently from others.

So on both ends, education is a challenge.

We are very excited about the new things that have been announced recently. There is the integration with AI, with AI fabric. There is Studio X, which has pre-built APIs with Microsoft Office and all the other Salesforce integrations that they've come up with. These are very exciting because that will increase adoption even more. People already understand unattended and attended automation, and now with Studio X being available so easily, and with analytics being part of its fabric, it's going in the right direction.

We have a very nice step-by-step flowchart that explains how to approach or what processes to automate first of all, and what are the chances of change or variations and all of that. While we are developing this, we at least are following the best practices from all the training that we received to ensure that we have taken that int consideration and we have not picked the process that is hard to automate, or which should not be automated. Then, it's more of a system change or any transformation that the customer should do first and then do automation. Basically, we should not do automation for the sake of it.

At my company, we don't work with any other RPAs. When it comes to customers choosing this solution, it should depend on the use case. If there is a strategic advance that they need to get and they need to really think of analytics and intelligent automation, UiPath makes a very compelling case. I think that it is important to choose your solution wisely and do it based on your use cases.

From a cost perspective, there is a big difference between the attended and unattended bots. One is twenty-five percent the cost of the other, which is a massive difference. Our customers use both, and we like this a lot because the way we utilize attended and unattended bots are the right way to do it. If you need to do multitasking and handle a lot of tasks, the choices vary.

Specifically from a pricing point of view, I think it is justified. When I first heard the price, and obviously I didn't ask about the duration or subscription levels, I thought it was a monthly price. Hearing that, I thought that it was cheap. Later, I was told that it was an annual fee. So for me, I understand that my customers can afford this price, and I am happy with that.

I would rate this solution a ten out of ten.

We have developed a product for a court of arbitration. UiPath provides the automation engine behind it. Our product is a platform that is live online. It allows a party to provide some contract information, and the robot assembles a document and communicates with DocuSign, our signature provider. It then sends out a correspondence to the other party and manages the signature process for a bespoke contract for an arbitration agreement.

This is a service that we provide to the world, pro bono, as it were, to promote arbitration and the adoption of a particular arbitration clause. It's accessible to all. Parties can log in and it helps them to negotiate and conclude an arbitration agreement in a mediated fashion. The robot sends out email on behalf of a third-party, a court of arbitration, and it helps the parties get that agreement done.

It's about concluding an arbitration agreement before the dispute goes any further.

It helps us in providing added value to the clients and to the community at large. It's a marketing thing for us, in the widest possible sense, rather than something that we use in our practice.

But in terms of reducing the cost of digital transformation, if a person had to do what the robot does, it would probably be impossible. It would be impossibly costly. If one person had to handle the communication, instead of the robot, and try to negotiate each addendum, nobody would do it because it would take days or weeks for a lawyer to manage, and it would be prohibitive. Yet, all of a sudden, we have this service that is so cheap in many ways that it can even be provided for nominal user fees. It's quite dramatic.

I would also imagine that processing time is reduced by many orders of magnitude. As a professional, if I had to manage an addendum like that, it would take me weeks. And it takes about seven minutes or so, if all goes well.

What I have found interesting is that our product acts as a human would but it's not intrusive. It doesn't require any real integration or interface with one's own systems, in any meaningful way. Obviously, you need access, an account to log in, but it otherwise acts as a human, and that makes deployment quite smooth. It doesn't require you to change anything in your system. I found that very useful.

Regarding the ease of building automations, I'm not sure how it's done because I'm not a programmer myself, but it's great. Just looking at how fast they moved once we had the program settled in — it was quite fast. For this particular process, which is assembling a document, talking to DocuSign, sending out emails, and so on, the deployment of production was like "today." It was quite quick.

In terms of the ease of management of automations using UiPath, I don't dare poke into it, as a non-technical person, but it looks manageable. I have someone who does not do RPA normally, who doesn't do this type of programming at all, but that person knows where to look for errors and doesn't get lost. It's reasonably accessible.

I could use more standardized features, retail-style, things that I could use off-the-shelf. Right now, all this requires quite a bit of adaptation in bespoke work with UiPath, which they've done very well. But looking at it after having used it, I would get stuff that is prepackaged from them, if they were any.

We launched with UiPath in June.

The stability of the solution is okay. 

The downside of the upside, when I said that it works like a human, is that in some cases, if it interacts with a website that is changing, then it's like a human. You need to adapt it to the changing environment in which it works. That's an inevitable fact of life, that it interacts with other apps. It can also interact through APIs, but you want it to be very flexible, you want it to be an agent, like a human. The downside of that is that if something changes with a website, then of course, you have to change the robot and tweak it a little bit. But that's the only issue that has required our attention so far.

Our product is a public-facing instrument and we have had no problem with the number of users, so we have not seen any issues with scalability.

In terms of potentially increasing our use of UiPath, we're exploring a number of solutions actually, for practice management and actual lawyer work. These would be in-house solutions, rather than public-facing. We have a few ideas that we have run by them and we are waiting for feedback.

We've had no problem with the customer support. We were in direct contact with the whole team. They have always been quick to respond. I would rate them a 10 out of 10.

We would use regular Microsoft automation features. I would have a flag on a particular correspondence, or a particular rule for attachments. We would use little bits and bobs of automation that are available, but we did not have any bespoke solution.

We went with UiPath because they made themselves known in the sector and it was a question of the vision that they communicated. There was a modest vision of providing solutions to very discrete problems, not revolutionary solutions to everything. Rather, they focused on whatever helps in a particular organization. We liked that. It matched our understanding of legal tech as well. It needs to be supportive of whatever little bit of help you need, rather than providing you with an environment that engulfs you with everything. We liked that approach, and when we approached them they were very receptive.

The initial setup process was okay. I'm a non-technical person, but I was able to manage it. 

It took quite a bit to figure out what we wanted from it, the flow and the logic of it. After we agreed on that, on the concept, actual production took two or three days. Of course, somebody had already done a proof of concept, although that was not based on a final brief. We danced around and changed it a bit.

For maintenance, we have somebody in tech that we pop questions to, and our maintenance of the server is done in-house as well.

We have realized return on our investment. It was a joint project with UiPath so we had special arrangements in terms of licensing, but it was very well received in the market. It was very beneficial for us.

Our product is something that we launched in June, and the robot has been featured in general business publications, in the Kluwer Arbitration Blog, and the Resolver, which is the Chartered Institute of Arbitrators magazine, as well as the Romanian Arbitration Journal. Essentially, everybody knows about it. It is one of the most popular UiPath robots out there; the most featured and interviewed robot in the wild. We were quite pleased with the publicity.

My advice is to think about it very carefully and know exactly what everybody is doing every day in the office, the little bits and pieces. Really look at that seriously, because there are so many things that we do in a software environment that are very amenable to automation, and it saves a lot of time. Think very carefully about the particular needs of your office and look into it, because it can save you a lot of money.

It's clear that this is the future.

I am using it for a project that we did for our client e.g HR automation in which we create, update, and delete the employee the database which includes master data management, active directory, and SNOW as the used environments for the solution.

UiPath helps our clients achieve their goals like with RPA. Now, with UiPath they get their work done within half of the time that it is done manually. They have more accuracy in their tasks and it has become easier to maintain. Before they reach the office they already have all the work done by the bot in their desk.

The tech support that UiPath provides to the licensed user it is really helpful. There were some scenarios when my issue was resolved within 24 hours. Also, I like the constant updates that UiPath provided to us.

As in my opinion, debugging needs more improvement. Also, if we get any other tool or technology which helps extract information from the scanned or handwritten document than that will be really helpful as a user and for our clients as well.

I have been using UiPath for two years.

We primarily assist clients in deploying UiPath within Finance/Accounting and Internal Audit but have also realized the benefits of deploying it within our accounting function to assist with expense reporting and invoice processing.

We have also successfully complemented our technology solutions practice, which deploys ERP systems such as Workday and Coupa, where we have built some specific automations to accelerate deployment and assist with normal processing.

We have been able to save several hours each month allowing our staff to focus on more value-added efforts. For just downloading expense reports, a staff accountant can save between four and five hours each month. A lot of the prep work needed to send out invoices to clients is now being completed through automation.  

The most valuable features are the flexibility of the tool, ease of use, and training. We spend more time documenting the process and exceptions, wherein the build component doesn't take too long. Our consultants have been able to go through the training videos and pick up the ability to build their own automations.  

I would like more incorporation of Artificial Intelligence (AI) features to allow for intelligent character recognition which can account for different formats and unstructured data. Specifically, the ability to not have to create templates for various formats to account for variation and rather intelligently extract key data regardless. There are some AI-like features in beta, but we are very interested in deploying now. 

We have been using UiPath over two years.

If built and deployed correctly, the solution is very stable.

The scalability is great! There are several use cases already and an endless possibility of areas where UiPath/RPA can be leveraged. 

I haven't had to interact with technical support, as of yet.

We did not use another solution prior to this one.

The initial setup is straightforward, both from interaction with systems and security. 

We deployed this solution in-house.

We have been able to avoid hiring more staff accountants, so more cost avoidance.

Plan for the future! Don't just focus on trying to buy a license to meet your current need, but look to have the right infrastructure in place to help you scale. The investment is relatively small compared to the potential in qualitative and quantitative benefits that can be achieved.

We do have past experience, but when it came to deploying in our internal operations team, we focused on UiPath. We have found UiPath to be the most flexible to deploy.

We are excited to see the new game-changing features with UiPath!

Our primary use of this solution, as a company, was to eliminate or at least simplify and reduce the number of boring, repetitive administrative tasks that take our precious time.

We are a business consulting company and lots of clients try to contact us on multiple channels that we are available on. Our company, in partnership with UiPath, implemented an unattended robot that saves our time and energy. We call it our colleague that works independently, full time and helps us without requiring emotional support.

As employees, we no longer have to waste a significant period of time each day by copying data from one part to another. Instead of that, we can focus on more important things like customer satisfaction, consulting our partners, delivering business plans, etc.

This product improved our employee satisfaction rate, improved the sales department performance in general, and created a gap in the marketing department that can be covered by more complex projects like website updates, social networking with customers, etc.

I found the UiPath Academy very valuable and it has helped us to understand the product we are working with. I attended the course and I am about to complete more courses so that I can benefit from this brilliant opportunity. It is free for everyone who is interested.

UiPath Community Forum and UI Connect are free and can be accessed by anyone as well. There, I could find all of the information that I needed. The most interesting part was accessing UiPath Studio, where you can try to improve your technical skills and try building a robot.

The platform that shows the reports and errors is not too transparent. I experienced it at my workplace when showing the reports, where the platform looks unfriendly and it is not very transparent, especially compared to the other features of the product.

The monitoring period should be shortened as soon as possible, as most companies won't have one to two months available to implement and test the RPA. People want results instantly when talking about an investment.

I would also like fewer errors, please.

I have been using UiPath for between four and five months in the company I work for.

Technical support has been responsive and helpful. 

This is my first experience with RPA software.

The initial setup was as transparent as it could be.

We implemented through a vendor team and they were pure experts.

This solution is worth the investment.

We did not evaluate other options before choosing UiPath.

We are a company that provides technical services and this is one of the solutions that we implement for our clients. One of our use cases is to help automate simple processes for banks.

In all of our processes, the time to complete them is still improving. We are always trying to minimize the time that each one takes. Our system automatically compares the performance between the robot processors and the manual processors.

UiPath is easy for the clients to use. We have an Excel file that contains the parameters and this is used to start their applications.

I would like to see some artificial intelligence for UiPath that would help us with OCR and other things like computer vision. AI would be helpful for us to implement those kinds of solutions.

We have been using UiPath for a year or two.

We have used the Community Edition and the Enterprise Edition, and we have not had any problems with stability.

Technical support for UiPath is great. When we look for something, we usually find it on their website. They also get back to us rapidly and provide responses to every request, even when we contact them by email.

Deploying a process that is simple or of medium complexity takes between one and two months.

This solution is not cheap but the price is worth it because by following the documentation and using the support, you get good robotic processes that are stable. Overall, we are satisfied with the pricing.

Overall, I would recommend UiPath. My advice for anybody who is considering this solution is to look at their website because it is very helpful and it can help them to make a decision about implementing it or not.

I would rate this solution an eight out of ten.

We have a system to create a multiple orders to perform automation testing. Here, UiPath helps us to create a bunch of orders without the hassle of creating a separate automation suite for this need.

When creating orders manually became a tough job for the user then it needed a benchmark for us to resolve this kind of situation to make teams more agile at work. This motivated us to find a solution to counter this problem in our organization. Definitely, it has helped to make us more agile. 

UiPath has helped us to achieve our goal as we are able to do what we intended to with automation. We are now dependent on UiPath to create the orders instead of having to do this manually. Earlier, this used to happen in a very traditional way and it was time-consuming, but UiPath has helped to perform this task with lightning speed. Now, we have more focus on implementing other things smoothly. 

Scraping data from the application using OCR and other text validation features is amazing in UiPath. These have helped us to create a reliable solution for our needs.

UiPath support needs to be a bit quicker than it is currently. They need to be very quick when they see a customer is struggling with something and taking the step to contact support.

The UiPath team needs to put some effort into improving the support section online. They should also improve the UiPath community forum so that beginners can receive help with activities that they require. 

I have been using UiPath for the past eight months.

Stability is a part where I would definitely rate UiPath a five out of five. It is really the best among all RPA products in this regard. 

We have a small flow that we have automated, but I feel UiPath will not let us down if we increase the capacity.

This is a part where I really think that UiPath needs improvement. They need to take up the issues from customers very quickly and resolve them on the highest priority.

We had not used any other RPA solution before UiPath.

This solution is very easy to set up. There is a bit of a hassle if support is expected from the UiPath team.

We have implemented using our internal team.

Significant manual efforts put into tasks have been reduced and a good amount of time is being saved. Overall, our time savings results in ROI.

The setup cost is minimal as far as other options are considered. 

We did indeed evaluate other options before choosing UiPath. We thought to use Automation Anywhere for our RPA needs but after doing some research, we chose UiPath.

During the evaluation process, we found significant failures when performing tests on exactly the same tasks.

UiPath is the most amazing RPA solution available in the market. Certainly, this gets plus points when it comes to feature versus cost ratio. Therefore, I would highly recommend UiPath because it comes with more stability and reliability than other solutions.

There are some features like different types of recorders. For example, Citrix and desktop are the variants we have in UiPath to solve our problems.

Other than the issues with technical support, I think that UiPath is a complete package for automating solutions in a rapid and fast environment.

I started using UiPath version 2017.1 and currently, I am using 2018.4.6.

We had a requirement of fetching emails, which are basically requests from clients filled on our website form. We read those emails and process the data filled by the user in the form. There are different forms like a request to provide reports, a request to add or delete a user, etc.

After reading these emails, the bot has to take the necessary action on our Primary CRM application. Depending on the request type, the bot will navigate to the necessary module in the application and perform the request as defined in the email request. 

Earlier, we had a team of around 20 people working in one shift to handle these requests. We were able to scale back on 15 of these team members and utilize them for other work in the organization.

Five people are still required to process exceptions that the bots are not able to process due to multiple reasons. Additionally, the UiPath bots helped process the requests for the entire day, compared to the processing happening only during business hours. 

We were also able to reduce the time taken to process each request from approximately ten minutes to two minutes.

There are many RPA tools available in the market.

The most valuable feature that UiPath has is the ability to be able to use .NET functions. Basically, all of the data manipulation functions and classes available in .NET are accessible in UiPath and this makes it easier to cast data and use it correctly. 

Apart from this, the Queue is one of the best things that other tools do not have. This enables us to have work items queued and then run multiple bots to pick up items and work on them simultaneously.  

As more and more organization units are trying to use RPA, there might be a need to have separation of data within multiple tenants or organizational units. Not only on the front-end but also the ability to have a separate database for each Tenant. This will leave no room for the enterprise security team to raise questions on data separation. 

I feel that a Host Admin, being a master Admin, should be somehow able to login to different tenants. 

I have been using UiPath for the past two years.

UiPath is quite a stable product. I haven't seen many issues and I rarely had to contact the support team for reporting issues.

UiPath is completely scalable. Right from giving you an option to segregate processes between different organizational units to expanding to multiple robots.

Customer Service is prompt and the technical support team is highly efficient and knowledgeable.

We used Automation Anywhere earlier, which is a more user-friendly and less complex RPA tool compared to UiPath. We finally had to switch due to certain capabilities that were restrictive in AA. Stability was also a factor.

I think the setup cost is quite nominal, but the licensing might be on a higher side when compared to Automation Anywhere. However, we should not forget about the features and flexibility which UiPath has.

We did not evaluate any other options. We moved from Automation Anywhere to UiPath.

I think that for the most part, this product has all of the required features.