UiPath Platform Reviews

I'm not currently using UiPath, but in my previous organization, which I left seven months ago, we had a complex trading application that included a web form and a Windows form. And on the Windows form was an Electron framework. If you want to run a web application inside a Windows application, Electron is a bridge between the web application and the actual Windows app. Because it was a complex application, it was not very easy to automate. That's where UiPath came in. It perfectly fit our automation testing scenario.

Before UiPath came into the picture, we were planning on doing automation testing with Selenium. The test plan with Selenium was going to take about three months. When UiPath was introduced and we started working on it, we completed the whole automation, end-to-end, in about one and a half months. It saved us that much time. And we made sure that our product was delivered with the required quality and that we did not compromise on that.

Because UiPath is SaaS, we were able to automate everything in a very productive manner. We were able to cross-verify all the flows and all the functionalities. And UiPath didn't require a huge amount of setup. It runs on minimal requirements.

In terms of human error, we saw a reduction, of course. It's not possible for a human to catch every error when new functionality is built. With UiPath automation, we were able to analyze errors right away and resolve them.

Another benefit was that it freed up employee time. It did a lot of the work by itself. The user only had to make sure that the correct workflow was involved and he could just sit back and check that everything was going correctly. It probably saved us 45 minutes daily.

UiPath makes you more productive because it comes with a lot of drag-and-drop features. You don't need to know the APIs to access particular elements on the screen. You can just drag and drop and define your actions and go ahead with the workflow. You can focus on the workflow rather than learning about the APIs, which is what happens with Selenium and other automation tools. That is one of the most beneficial features of UiPath.

I don't know if I was doing something wrong, and I did get assistance from the UiPath guys on this, but sometimes UiPath wasn't able to find an element on the screen. But that's what UiPath is for, and we wanted to make sure that our workflows were working correctly. Sometimes it was able to find an element and sometimes it was not. UiPath support did give us a solution, but it was not helpful enough.

The issue that I mentioned earlier, that sometimes it wasn't able to find the elements, was the only issue I saw with respect to UiPath. Otherwise, nothing was breaking and nothing was problematic on the UiPath side.

They were very friendly and they tried to be very helpful, but they weren't able to solve the issue I raised.

Positive

The version of UiPath that we used involved a direct installation. We asked our in-house team to get it installed because we didn't have the permissions to install software. They installed it in our system and we started using it right away. It was very straightforward.

I have worked with Selenium, which is an automation tool. That has quite a learning curve, but with UiPath it only takes you one or two weeks to get started. Once you're familiar with the basic tools, you can start writing a workflow. It is straightforward; nothing complex.

I never did the UiPath Academy courses because we had senior team members to help us and, in that company, we had a "learning playground" where we could go through the slides directly, without going through a whole learning process. We were then able to start our work right away.

UiPath did a good job. Before going into production, we needed to make sure that every test scenario and every case was handled. That's where we took advantage of the UiPath. We would run UiPath again and again and there were no breakages in our code and nothing was falling apart before going into production. I was working for an investment bank and every record was important.

Our primary UiPath use case is reconciling data and getting data from the web and writing to either Excel or our system. The automations are very reliable. 

Task Capture is quite a helpful feature because it is easy to design a process flow with it. All you have to do is just capture it and then do the manual process. It then gives you the process flow and the process definition document, PDD, so it saves you a lot of time.

The database connectors I found are not fully free and expire after 30 days. That is something I would like looked at for MongoDB specifically. With regards to this, I was working on a project that needed a robot to read data from a MongoDB database. To achieve this, I used the CDATA ODBC driver because I couldn't find a direct Activity to achieve this from Studio. See the link to the CDATA ODBC driver for UiPath here https://www.cdata.com/kb/tech/...

It would also be great to have UiPath Insights included in the free Orchestrator. The Insights module is currently only available for paid licenses. It would be great for developers to have it included in the free version because then we could try it out. 

I have been using UiPath since May 2018, and have recently worked with UiPath Process Mining. I am currently not very actively using this tool because the projects I'm on at the moment are using Power Automate. However, I do look at it once in a while.

UiPath is quite stable. I have not seen any inconsistencies come up because even exception handling is well set up in case of bad themes. Transformational processes are well managed, including exceptions, so that adds to the stability. Also, you can scale out from one bot to tens of thousands, so automation is quite easy with UiPath.

Very scalable

The initial UiPath setup is straightforward. You just go on the cloud, create an account, and you get the Orchestrator right away. From there, you can download the Studio. So once you build the automation, you just publish it from the Studio and you can run it. It's a very seamless process.

There is no need to hire an external team. You can do everything yourself. Also, the forum is quite busy and active. You can get a lot of helpful material there.

I cannot give actual figures, but I have seen a return on investment especially in processing invoices. It used to take us a week to read certain invoices into Excel but now it takes us only a day. So we are saving five Mondays in a week and 30 or 40 a month. 

From what I hear, UiPath's licensing costs are a bit high, but I can't evaluate that information because I haven't actually experienced the cost. We are using a free version at the moment. A good thing about the Community Edition is that they allow you to deploy even as a company as long as revenues are below $5 million I think.

I recommend automating the small processes in the Community Edition. This is the best way to evaluate how scaling would go within your organization. 

It is also important to fully understand what you want to automate. I also recommend trying the Process Mining feature to make sure you are able to pick up areas of automation within the organization's processes before committing to paying for automation. 

I work at a financial firm where we do trade settlement activity. We are using UiPath for cleaning up data, doing reconciliation, and finding where the trade breaks and trade files are. It helps us lay the groundwork for the value add work, which comes later.

It allows us to grow our business. The use case that we have is a huge time saver because we do not have a lot of volume right now. We are looking to sell part of the business and get more clients onto it. The only way we could do that or even open that door for possibility is to automate and go through a lot more volume. 

Our teams are under huge pressure because trade volume has gone up over the past year. UiPath is just getting us back to the status quo and then also opening the pipeline for more volume to go through. We have a very strong program that encourages people to get trained up on tools. 

StudioX is going to be a big game changer for us. We found with the other tools that we use that as soon as we put UiPath in the hands of everyday users and ops users, they will be able to quickly learn it. This will make a big impact because we will get big volumes and projects coming through.

UiPath has done a good job coming up with the broadest use cases. However, I would like to see them dive into more industry-specific use cases. For example, checked OCR and brokerage statements are common. Anything unique to the financial industry would be useful for us.

We have using UiPath since February when it got brought into our team. We just had our first box go live about two weeks ago. We have had three go live so far; one using StudioX and two using Studio.

So far, I haven't heard any issues. We are always going to expect issues, but so far so good and I hope the stability is good. Alteryx had issues at times, which created some pretty big problems. Hopefully, UiPath will not do that as much, because we are expecting to lean on it.

I have not used them directly. 

It was not so much a switch for us. We are still using Alteryx. UiPath is a much better automation tool than what we were using before because it was self-service. We didn't have to have our COE build it and related solutions for us. We have similar functionality with Alteryx. Anyone can learn it and start building and go through our governance process. Doing so, they can have a huge impact on their team.

We are a large company and the initial setup took our COE quite a few months. However, I believe their experience was positive overall. A lot of the issues we had were internal and concerned how we were going to do our governance. We were very strict about that. 

Getting people access was easy and so was learning to build. Everything on the UiPath side went smoothly.

We're a mature automation team. Over the past four years, we've delivered well over 150 FTE. We're always looking for new tools and to pick up some of that automation that we couldn't do before. 

UiPath has helped with data scraping and plugging into websites and combining that with Alteryx. We can attack 90% of our use cases now. We can not deal with the other 10% for internal governance reasons and not so much capability.

The three use cases we have implemented with UiPath have saved about half an FTE. 

I know that the reason we went with UiPath is because it is a lot cheaper than the other vendor we were using. It is of a better quality as well, but it is less expensive to run on an ongoing basis. 

I'm not sure if we evaluated other options. My team does not look into the suite of options. We have a separate COE that sets everything up for us. We are tasked with implementation. 

My advice is to first build a good team that you can trust. Because great tools are useless if you don't have any builders or people that know how to use the tools. That is what we have been focused on. Also, have very specific support for your team.

In terms of product testing, I use it in the product with the test suite to mount the test manager and then follow with the requirements. After that, I create the test cases and I'm running them on different platforms on the web so that I can proof back from the web with test suites.

I use the different tools of UiPath. However, in the future, I’m hopeful UiPath will help us to expand into different countries. right now, I use it personally. Soon, the entire company will be using it as well.

The automation of the cloud offering helps to decrease the solution's total cost of ownership.

The document understanding is great. I interact with different documents of people. The IDs of one are different from a document or a PDF. For example, our contracts, et cetera. It can understand the differences.

I’m not quite sure about the ease of building automation using the solution just yet. It seems to be moderate. Not too easy or difficult.

The solution has helped our organization save costs. It’s likely saved us about $10 million.

UiPath has helped us reduce human error. That’s had a partial impact on our business. Our techs understand the different types of processes and competencies it can help with. Regular users cannot see this just yet.

It has freed up employee time. It’s allowed for a focus on higher-value work. Employees seem happier. It’s an easy tool to use and deploy.

We’ve used the UiPath Academy courses. All employees take the course and learn about it. You still need more education afterward, however, the biggest value of the Academy is the knowledge. I've got people who are new in the company and I can just say "take these courses." It's accepted by everyone as part of the process.

The graphics could always be improved.

I've been using the solution for three years. 

The stability of the solution is good. UiPath has a different release each year at the moment.

The scalability is great. You have a manual so you don't have to do the courses. You can read through it.

We have about 200 users at this time. We have different areas in the company that uses UiPath. For example, the administration uses that tool. You have a test suite and you can have development using the UiPath Studio as well.

Technical support has been great. Whatever my query is, they are able to answer it.

We did not use another RPA solution before UiPath.

The initial setup was straightforward and simple.

The deployment took about one month.

The pricing and licensing have been great.

We did look at different automation tools before choosing UiPath. We looked at Blue Prism and Automation Anywhere, however, we ultimately chose UiPath.

The UiPath Academy courses were a big selling point. Also, its ease of use. Automation Anywhere and Blue Prism were so difficult to understand. UiPath is more interactive and it's more visual.

We're a UiPath partner. 

I've used both cloud and on-premise deployment. Right now, I am using the cloud. 

At this point, we do not use UiPath's apps feature.

We have not used the solution's AI functionality in our automation program yet.

If I were to advise anyone on using UiPath, I'd let them know it's easy to use. You have manuals and courses to help you navigate the solution. The new releases make it so that it continuously gets easier. 

I would rate the solution at a ten out of ten.

We're still building up the program, but right now our primary use case is for report review. We're looking to branch that out more.

It's reviewing reports. I worked for a bank and there are reports of transactions from the previous day. UiPath was looking for anomalies for fraud and things like that.

It's still very early on but we have caught a few instances of fraud that we would not have if we weren't using UiPath. 

UiPath has reduced human error. We're very early, so it's not a big impact, but we did find a few instances of fraud that we would not have found without it. 

We see time savings for our users in the sense that they now can do more tasks that should have been done all along but weren't getting done. That's more where the gains have been this far.

I like the whole ecosystem. They're not just looking at the automation tool, they're looking at automation from end to end. 

It's pretty easy to build automations. I have a coding background so it's not particularly challenging for me to use Studio, but for a person who does not have that coding background, I think that the Visual Builder guides you through the process pretty easy.

UiPath Academy is a good training program for people without that coding background. It's good to get them into the mindset of how exactly flows works of automation.

The Academy offers us familiarization with Studio and how it functions.

The API integrations need improvement. They should build a better framework for the ability to integrate with other external APIs.

I have been using UiPath for less than a year. 

I would rate the stability an eight out of ten. 

It's pretty straightforward. It either runs or it doesn't. Occasionally it does crash and we've had to restart services and whatnot to get it going again.

We haven't been using it enough to see how it can scale. 

There are two ITs who use it in my company.

We have plans to increase usage. 

We don't really see our staff as being good candidates for citizen development. There are a few that could, but we do plan to expand out into other departments as far as gathering ideas and implementing processes for other departments.

Their support is pretty average. It's not good or bad. It's off-shored. There are always difficulties with cultural differences and language barriers. They know what they're doing but sometimes it takes a while going around in circles to get the question that you're asking across. That's pretty normal. Most companies are the same way. I would say all companies have huge room for improvement there.

The initial setup was pretty straightforward. It was easy. The installation instructions walk you through the process. We didn't run into any problems. It took less than a week. 

We also looked at AntWorks and Blue Prism. We went with UiPath because of the maturity of the product that seemed far more mature than its competitors. The product seemed more thought out.

Based on our experiences, I would say you have to have employees that are dedicated to doing this. This can't be done as a side project.

I would rate UiPath a nine out of ten. Nothing is completely perfect. The stability of it could use a little bit of improvement. The support is not great. UiPath is very good, but no one is perfect.

We've got mostly finance use cases including a lot of accounts receivable and stuff like that. Then, there is a lot of work where I do trading settlements, so a lot of settlements as well. The back office automation's there, too. We're still getting used to it and still getting started.

We've been able to expand up to citizen developers, and have been able to show them how to do various things. It's easy to pick up, so a lot of citizen developers are learning it now, and with little to no coding experience. It's been great.

The recorder has been great. Just being able to really start your automation there, and just modifying them a little bit and then getting them really in production has been helpful.

The solution has saved costs for the organization. For example, I used to do back-office stuff, and I was able to move to more of an IT role. That was definitely a savings there, and obviously, no one had to automate it after me or do it manually after me.

We have found that the solution has reduced human error as now it's a bot doing it. It's really reduced errors due to the fact that no one has to check each time to ensure the work is error-free, and, in general, there are a lot fewer errors. 

The solution has freed up employee time. For example, as I mentioned, I myself have moved off of back-office tasks and, in doing so, the company did not have to hire someone after me. We've likely saved 10,000 hours in a year. We're really happy with that result. The additional time has enabled employees to focus on higher-value work. People can now just quickly audit it and then move on to something more important.

The Academy is great to use. We've been able to learn a lot from there. That's what our citizen developers will look at as they get more familiar with the product, and as we show them how to develop items. It has positively affected the process of getting employees up to speed on the solution. A lot of them have little to no coding experience and the Academy has helped by showing them what they need to learn. The biggest value is if they have little to no coding experience, it'll really start from the basics and teach them from there. You don't have to teach them all the variables and stuff like that.

While I like the Academy a lot, it could maybe go deeper into some of the topics. The basic ones, such as Excel, which is already a decent course, could maybe go into more specifics. My issue is that, while the basics are good, getting into the weeds a little more could be very helpful. It's hard to specify exactly what is needed, however.

We've used the solution for about a year now. We're still getting used to it. 

Our stability is great. You rarely have any downtime, once you build it. There's obviously the support, however, I'd say it's pretty minimal.

We're trying to work on scalability at the moment. It's there, however, we have a lot of different departments that do a lot of different things and that's where we need to really work on scaling. It has nothing to do with UiPath. It's just about getting everybody trained up on everything on our side. That said, we can see how it is possible to scale in the future. We do plan to increase usage.

Currently, we have about ten users who are familiar with UiPath. It's not too many. They are either developers or just everyday users that support it.

In terms of technical support, from the perspective of tickets, et cetera, I would say they are pretty good. We've only done a few upgrades so far. We've only had it for a year, and so far, in that time, support seems great. They have been helping us out on everything.

We did not previously use a different RPA solution.

I can't speak to the initial setup, as we had an outside party handle pretty much everything. I actually joined after they onboarded us and everything, and therefore wasn't a part of the process at all.

We have two to three people that handle maintenance tasks, on top of the AI.

We had an outside party do the deployment. It was a consultant. They did it for us.

I don't have any insights into the licensing process. 

While I joined after UiPath was implemented, my understanding is the company did look into a couple of other options, just to see their capabilities.

I would advise potential new users to go for it. The Academy offers a great starting point. It's a great tool. I would recommend UiPath.

I'd rate the solution at a seven out of ten.

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.

My use case is to automate a bunch of office processes. It helps my team and finance organization save time and money.

There's a monthly upload process in my order management team. Every month, this team uploads a bunch of files to SAP. Now they don't need to do that because the bot does that for them at a given time period. The team members need to just upload a file to SharePoint and then the bot will pick it up.

It reduced human error. It saves us time redoing work and allows our humans to do other stuff.

It has freed up a couple of hours in a month. If you scale it, I'd say there are some processes that are daily. It has been at least 2,000 hours so far. This additional time enabled employees to focus on higher-value work. Bots can be tricky to debug. So, sometimes employees get frustrated there but overall they're happy it's there in the first place.

UiPath reduced the cost of our automation operations. Right now it's breaking even, but over time there'll be more. It has also reduced overall costs. 

The Studio and Orchestrator are pretty valuable. They seem to have a lot of connectivity and usability. It's pretty easy for people without a coding background to use it.

It's pretty easy to build automation using UiPath. It's a little hard for some activities because there's not enough support. There's not a lot of adoption with that activity, but the ones that are commonly used have pretty good support.

Its end-to-end coverage is important to us. If we have it all on one platform, we don't have to bounce around other software. But, we ended up doing a little bit of both.

Capturing ROI needs improvement. I would also like for it to have more logging mechanisms in Orchestrator.

I have been using UiPath for about two years now. 

It's stable now. 

We mainly use Unattended Automation but it has helped to scale RPA benefits by automating departments for the very few Attended Automations we have. It's important to me because my job pretty much depends on this software. Changing from this product to another RPA product is going to be extremely costly and time-consuming.

It is scalable. We have about 30 users on it now that are entry-level/senior associate-level people.

It requires four developers to maintain. 

We plan to increase usage in the long term. But right not we still have enough capacity in our existing Orchestrator.

I would rate their tech support a six out of ten. Most of them don't work in U.S. time and they're not always very responsive. Sometimes they give an answer that is pretty generic and can be found in the online article, even though I referenced the article already.

We also use Automation Anywhere. 

The initial setup was not too hard and not too easy. Some documentation wasn't very clear, and for basic features it handled it pretty well. But, if you wanted to go more granular and customize your deployment, it would be a little hard to find out the answer.

The deployment took about a month. We involved the UiPath support to help us implement it and upgrade our systems. Other than that, we got our PAM software lead that uses CyberArk to configure the Orchestrator with us.

We have seen ROI. I don't know the max number of hours but I'd say we've saved around 2,000 hours so far.

I think pricing could be better. I think it should be more visible.

The license system with Studio licenses seemed a bit redundant and not necessary.

We looked at other solutions but went with UiPath because of the cost. Another reason was that we have more developers that are specialized in UiPath, as well as management, who seemed to like UiPath more.

I still have to pay attention to the infrastructure a little bit because it's still On-premises. I'm using the On-premises products more so, but the support has been pretty decent. And then, there are community forums to look up how to debug some stuff.

The upfront cost is always going to be more than trying to keep it to the human process, but over time we'll realize more return.

My advice would be get UiPath support to do this for you and involve all your IT firewall security team.

You need to know more about security and cybersecurity in order to fully deploy your automations. Some of that is kind of missing in the Academy where they focus mainly on building automations, but not really securing it.

I would rate UiPath an eight out of ten.