UiPath Platform Reviews

We work with TMS, a technology-management resolution division. We use UiPath to read the PDF documents that we get. We manage a business service for TMS and as part of that business contract, we read the PDFs and enter that information. We get that information out via documents from the templates where we have to enter information related to that particular case. 

These are the use cases that we are currently working on, but we are also looking to use this for quality assurance of all the steps because this is a highly visible, very critical process for TMS. We have to make sure that everything is done on time and that all of the information is relevant and responsive. Quality assurance is a big deal for us, and we are looking to use UiPath quality checks at different stages in the process.

We are in the initial stages, so I can't really say that we have achieved a whole lot of efficiencies using UiPath yet. We hope to achieve a whole lot of efficiency when it comes to the documents. Right now it takes about 45 minutes to do this process manually, to read that entire form. It is going to be reduced to two minutes. That is a huge efficiency gain, and that is the value that it will add.

When it comes to the ease of building automations, UiPath offers many libraries for developers to use. It's fairly easy to code it. 

We definitely expect that it will save us costs and human error. There is a lot of critical information in these forms and there is a human error because we process huge volumes. Obviously, when a robot is doing it, that human error will be reduced to a minimum.

The hope is that employees will be able to allocate their time to different work.

We use the Academy. We are enrolled in the partner program, and we have used a lot of courses from the Academy. It keeps us up to date and up to speed with the solution. Although, our needs right now are very focused and limited because we are just starting. I'm sure as we grow and as we advance in our RPA journey, there will be enough documentation and courses for our needs. 

Most of our PDFs are scanned PDFs and the OCR does not always capture all the information correctly. That's why the document understanding feature will be good for us. 

We have been using UiPath for about four months now. 

We haven't seen any issues with stability. It's definitely been good.

We have used technical support when I had some issues installing the system. 

I am looking for ways to get the technical support we need faster. 

I think that the pricing for the basic attended robot Studio is great. I think that all of the new features that they are rolling out if they are reasonably priced, they'll be useful because for people like the ones working on our projects who are funded by the government, they have a cap on how much they can spend.

Keeping the price in a reasonable range would be beneficial, and it'll be more usable and more in reach for people.

We considered Blue Prism, but through our research, we chose UiPath because of what they've already achieved with CMS. We thought it would be the best solution. 

The UiPath website has a lot of information and the Academy offers a lot of courses. I heard from different people in different industries and markets that this is the best solution. It's worth a try. There is more work in the beginning when you are getting it set up. But there are a lot of benefits, and you don't have to wait months and months to see them. You can start seeing the benefits early on.

I would rate UiPath a nine out of ten. 

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 have four robots. One we're sending out shipping labels as our members do returns. Once they create a return, we used to have someone that was manually entering in and creating the shipping labels. That was like the first robot that we built. The cost savings on that alone covered the costs of UiPath in total. We have a few other ones that we've been playing with, however, that first one was a big one that covered the cost of UiPath. 

UiPath has freed time for our employees. With the shipping label robot, for example, we basically replaced two jobs and now they're able to do other things. They can take on other more vital responsibilities.

I'm really excited about task capture. We haven't started it yet, however, that's going to really help capture the processes that we want to automate. We're excited about that.

The solution is just opening our eyes to what is possible. There are a lot of people in our company who hate doing mundane repetitive things. It's giving enough hope that we can replace those jobs that people hate with automation. We're excited about that.

I'm not a developer, however, the two developers that are under me, like the shipping label bot and found it easy to build. A developer was able to create that in one day and it replaced two positions. I'm sure we can build it better and faster with what we're still learning. With a partner coming on to guide us I foresee that we will definitely get better at it.

We’ve used UiPath's Academy courses. I don't think we would be where we are today without it. My two developers had zero experience with UiPath. They went to the Academy and learned as much as they could and started building right away.

Its biggest value is the continual learning on offer. We're pretty overwhelmed right now with what it can do, however, the Academy just teaches us how or where we can go with it. It’s great.

The setting up of the cloud was a little bit confusing for us. We expected someone to walk us through that process and we just did it ourselves and weren't sure if we were doing it right. We thought that getting assistance with the setup would just be kind of a given or they would at least lay out the steps. We didn't have that. We were asking a lot of questions and trying to figure it out with our salesperson. She was likely not the right person to help us with that. If there were directions on how to set it up, that would have been helpful.

We've had the solution for three months. 

In terms of stability, the robots have been running well. That said, we've had a few failures that we had to go in and fix, however, it was a pretty minimal effort to fix them. I'm not sure of the exact reasons. I remember my developers were telling us one failed and we needed to go figure it out.

It wasn't like an all-day fix. It was just a pretty quick fix which required simply stopping it and restarting it and then it worked. 

In general, for stability, it's been so far so good.

We have the goal of scaling, however, we are still just barely with our heads above water. We're just trying to figure it out as we go. Our biggest asset is bringing a partner on to help us and allow us to build up that scalability. Without their help, we would be lost. We would build without having a good foundation. The partner is coming on for a three months contract to train us and get us up to speed to make sure that we're building a good foundation so that we can scale.

We first created a technical support ticket when we had the issue with the trial license versus our actual license. It was hard for my developer as he didn't have the URL for the cloud. He really couldn't diagnose the issue as we thought it was all on the one referred to us, yet there was that disconnect. We went back and forth over several days trying to figure that out and the tech person couldn't help us. We were lost there. That was a little confusing.

This feedback isn't against the technical team. Maybe it was just the way we didn't get the correct training we needed to set up correctly. UiPath should've killed those trial licenses or transferred them and they never did and that first robot we built was on a trial license. 

It would have been helpful if they told us to import the robot or something over to the real licensing. 

We did not use a different RPA solution previously.

I'm not a tech person, therefore, the setup was a little outside of my wheelhouse. It was a little bit harder for us. We've been trying to figure it out. 

The issue that we've found is we had a trial license and my two developers were on the trial. Then, when we got the actual licenses, a developer was still building under the trial. The trial was allowing them to do things and build over there, however, it wasn't under our automation path. It took us a while to figure out what the disconnect was as I just didn't know how to set everything up. That was a little bit confusing.

We realized ROI on our first robot. 

The automation cloud offering did not decrease the total cost of ownership of UiPath. It was a little bit more, however, we didn't have to set up our own server and maintain that.

We bought the starter package and we were able to cover the full cost of it with one robot within two days. It definitely paid for itself.

We were also looking at Automation Anywhere and it was a pretty close tie between the two.

We chose UiPath as a colleague who had worked with UiPath at his last job and he was a little bit more familiar with it. We thought the security was a little bit better in UiPath as well. Those were the two main reasons that kind of pushed us towards UiPath.

We haven't used the UiPath apps feature yet. We've signed up with someone that is going to be our partner to help us learn all the new aspects. Hopefully, in the next couple of months, we'll be setting everything up, including the automation hub, and trying out apps and task mining.

We do not yet use UiPath's AI functionality.

Based on my lack of knowledge, I would probably rate the solution at an eight out of ten. We've been super happy with it this far and from all the things I've seen, we're excited about where we can go with it.

Our primary use case is to document image processing. We're six months in, so our first case was sorting and filtering the data, extracting the image, and determining if it's a certain type of document. If it is, it starts putting it into different buckets, which ultimately we'll run something to extract and put those into our data source. 

Our second use case is for the healthcare industry. We're looking at catalog data and a customer might want to know about a product. Is this product safe? Who provides this product? Is it on a contract somewhere? We go out to multiple different web sources to look up information about that document, put it back in our database, save it for that customer, then save it for any future customer that asks the same question.

We're looking at other things like taking snapshots of the image of the product. We also want to automate other basic automation, low-hanging fruit type functions, like automating uploads of data to sites, spreadsheets, contact-center, and Salesforce.

Longer-term, we want to take what we're doing in the document image and apply it to other areas of our business. We have purchase orders, invoicing, shipping documents, compliance documents, credential documents, a lot of images in this particular space. We'll go as deep as we can in the data processing side of things.

We're going through a culture shift to get to an automation-thinking platform as opposed to a lot of our business relying on BPO humans to do the work. Making that paradigm shift is taking time because we're only a week-plus live. If we prove the value, they'll give us more opportunities to make those big changes. But it's good that the business is thinking that they need this. Now it's just getting the community aspects of it.

The automation cloud offering helps to decrease the solution's total cost of ownership by taking care of things such as infrastructure, maintenance, and updates. 

Although we don't use it, document understanding for our use cases is very compelling, but it was a little cost prohibitive just out the gate. We are looking at it long-term now that we have the data filtered if we can more strategically apply it to the best data to fit it. But overall, the platform is very innovative. I don't think I can call out one particular feature. The ease of use of integrating to and from Amazon components, being a cloud-native application ourselves, has been really helpful in the development and the ease of transferring documents between our internal systems and platform.

The ease of building automations using UiPath depends on the use cases. Overall, the development is really easy. Where you run into challenges is in workloads that are highly rule-based. So we abandoned one use case where it had 50,000 different decision points. It wasn't worth the time. It wasn't a product thing. It was just too time-consuming of a process, something like that.

There have been some limitations as far as how do we execute our bots, when? This new release that they just mentioned today actually addresses a lot of our concerns around the integrations component that they recently released. If we could find an email instead of waking up and checking the email inbox. That's a big improvement we're looking to, but it wasn't a limiting factor.

I have used the Academy. It was really just myself and as well the one IT guy who's supporting the platform. Our office partner came in with the knowledge, but the course was really good. We came in with no RPA experience, and it covered everything from the basics of RPAs to the processes of identifying.

They recently addressed a major problem of kick-off processes for the integration function. That addressed a lot of the community concerns around that. If you are using queues, their queue system isn't as reliable as I would like it to be. 

One of our concerns is that we were not a Microsoft shop at all before bringing this in. That was actually my limiting factor in bringing in the software. We lost it below the party lines. The ability to address other workloads, Mac, Linux, etc., is going to be a game-changer.

From a new customer, new investment perspective, there are a lot of cost-prohibitive aspects that we decided not to add to our initial investment. We weren't sure if or when we'll figure things out for use cases.

I have been using UiPath for six months.

We want to triple our capacity and triple our workflows. 

I've only had to use support once, and it was more of a documentation problem. I didn't understand what I was seeing, and they worked it out within an hour. So far, they've been good. 

The cloud was up two days after we signed. Then to get our bot infrastructure up because it's Windows and we're in a Windows environment, it took us about a month to run through that and get the IT people and security.

Cloud solutions will save you a lot of headaches and time. We broke halfway through and decided we're going to cloud, not on-prem.

Reputation was a big reason we went with UiPath, as well as the growth and the ability to integrate specifically to the cloud which was missing in other solutions. That was a big plus. The ability to use something like document understanding and the ability to interact with internal APIs were also key features. It's not just web scraping and doing things in Excel or other things like that. We wanted it to work with our internal native applications.

UiPath has not yet saved costs for my organization. We're still going live and we're anticipating about a two-year ROI.

Make sure to understand your use cases before you sign your agreement. That way you're not idle for six to nine months trying to figure out what it is you're trying to automate.

I would rate UiPath an eight out of ten. 

We use UiPath for OCR, for our subrogation department to analyze credit report organization letters that come into our company to identify whether they're identity theft, fraud, or any other type of keyword phrase within the document. It also extracts the information coming out of the CRO to properly assign it to accounts associated with our subrogation department. 

Another use case is navigating through one of our third-party clients in order for us to get documents out of their system and into our system so that we can analyze and package them.

We see benefits from the AI side of doing OCR and in order for us to do onscreen recognition of documents. It increases the efficiency of our agents in order for them to get back to working accounts, rather than reading through document after document every single day in order for them to pick out one or two words into the document and assign a smart code. The automation does all of that for them now.

UiPath has saved us costs. It's thousands of documents per day that we're OCRing and then that reduces it to around five to 10 minutes per document. It's around 50,000 minutes per agent, per day.

It has reduced human error because there would be some different document types. It's able to detect multiple types versus a user finding one document type when there could be multiple document types that are associated with a letter, while the user is browsing over it that can be missed in the second document type. But when you're looking at machine learning and at the text, it'll be able to easily pick out those keywords from a document that has multiple document types.

It has also freed up employee time. It frees up their time to do other work.

We are currently using the AI function in order for us to do Task Mining to be able to pull out of a couple of our key groups that we're trying to add additional automation to. That's what we're using AI Center for at the moment.

We have done UiPath Academy courses. I got certified in the advanced RPA Academy. I need to renew that because they expire every year. Another developer has his associates, so we use that every year where we can get some training. It helps keep people up to speed. It makes sure that you're doing the latest and recommended in the RE framework and what you have initially designed.

Building automations can be difficult at times with some of the activity packages and documentation being out of date, but we have a TAM that we work with that is very helpful in making sure that RRGs are known and that we get the results within the UiPath structure.

They need to deprecate their previous versions on their website or their documentation. It should just point to the newest version rather than when you go to Google if you're just trying to find UiPath and then it points you to a solution that was a couple of years ago. Or it points to a form that someone randomly has posted to their code. That needs to be cleaned up.

We've been using UiPath since 2013. The Orchestrator is on the cloud and the robots are on-prem.

It's pretty stable. We haven't run into any issues with operating totally different packages. There have been some things where I wish there were more restrictions in access groups that could be applied within Orchestrator, but other than that, it's pretty good.

We are still working through scalability. There are a couple of things that we've run into that were an issue with trying to use machine templates and getting them to connect properly with the robots. Another scalability issue that we have is that we have a non-static environment where some machines get deleted after they log off and get back on, they have to reconnect to it. We had issues with that, but those are for our attended robots.

We have unattended bots. We have four of them and it's a total of seven automations, but they run every 15 minutes.

We used to use OpenScan before I got hired and then eventually moved off of OpenScan because the product was too cumbersome and difficult to navigate. So we moved to UIPath.

They saw UIPath and they saw that it was going down a good road. So that's what they chose it. 

The initial setup was pretty easy for us. Getting into the Studio is pretty simple to get us set up and going. There are a couple of issues with mixed environments for DLLs. You do get packages for UFS that I've run into trying to use one of our older DLLs that hasn't been updated, but all in general, getting it working, and being able to figure it out was pretty simple.

We have seen ROI. 

The subscription models that they have out there need to be simplified.

I've talked to a couple of our partners and talked about the 49 pages of subscriptions. It needs to be more streamlined for what they offer and packages because we run into issues where we're signing up for Task Mining, but they didn't include AI Center, which is a requirement of Task Mining in one of the factories. If the subscriptions got simplified and got it down to a couple of pages, they would see tremendous growth. That way customers don't need to hire somebody to figure out what the licensing model was versus going for a third-party vendor.

My advice would be to start in the cloud. Cloud is the easiest way for us to get started versus trying to get our internal environment set up. We had on-prem orchestrator and on-prem servers, but it was easier to implement the cloud and get it up and running and scale versus our internal environment, as well as keeping the data secured within our robots on-prem. 

I would rate it an eight out of ten. 

We do product downloads, accounts, updates, maintenance, a lot of operation stuff, reading emails, responding, organizing stuff to send, etc.

It's definitely added some efficiencies. It's added the ability to do jobs without having to worry about error handling and process tasks on a daily basis without having somebody having to be responsible for it.

We see UiPath as a money-saving solution. It also saves us man-hours and human error. It affected our ability to automate processes that are more complex.

The Academy courses are good. That's usually what I start new developers with; to do those and then have them try to do courses periodically to stay up to date and especially when a new release is coming out. The hands-on training is the most valuable part of it. 

We use the solution's error functionality. 

There's a little bit of a learning curve to build automations, especially in the citizen developer world. Usually, the technical people are busy a lot of times, so it's hard to get them trained. But as far as developers, they usually come along pretty well, from my experience.

We could use a little more interaction with users, like with UiPath, the vendor, and support.

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

We had a vendor that kind of offered to do a few, like bring you the UiPath and do some automations for us. We dipped our toes into that and liked what UiPath has, so we kept them.

I would rate UiPath an eight 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.

Our primary use case is to scrape our database to get data out, create audit files for our tax team, and then take that data and go to websites for each state and submit our taxes online.

Time-saving is the biggest area that has improved for us. We had users spending lots of time trying to get data from a system and then creating a file that was going to be used for our auditing purposes, which then gets submitted online. We definitely found some issues where an end-user was pulling data from different sources and then storing that data with lots of human touching that created issues.

UiPath created a better atmosphere of better data quality. Time management was also much better, and now the user actually has a better experience doing that process because now it's a click of a button. They can spend their time doing the actual work that they want to do.

Instead of having to go back out through those websites and make corrections when they paid for the wrong taxes. In some states, it's a lot harder to make those corrections, especially if it's one where you overpaid. Now, they're accurate and they don't have to go back and make those changes to try and get that resolved.

We have seen cost savings from the time it has saved us. We save around 40 to 50 hours a month. Over the course of a year, it's quite a bit, and it adds up.

Web trading services are the most valuable features. 

It is easy to build out automations. I have an IT degree, but I was not doing the dev work within our department. I came from a data quality background and transitioned over to this because the low code has been great and all the online resources that they've provided us have been very beneficial.

Other members of my team have used the Academy. It helps to get a jump start. Now, luckily, we have a couple of us that do it. It's much easier to train and show them what we have already built and then say, "if you have questions, you look here." It's just been great.

They have the robotic enterprise framework that I wouldn't have used if it wasn't for the Academy. When I first started automating, I wasn't utilizing that process at all. That actually made a huge difference in how I programmed and how I even looked at building my automations to start with. I feel like learning that course specifically for me, was great, was like the best benefit for me.

Since we've been with them, they've changed their licensing structure. It would be nice to have one set structure where they're not changing the structure on us because we were set with what we had, but now we are changing. I understand there's a lot of changes and reasons for it.

I have been using UiPath for a year and a half. 

I haven't had much issue with stability.

It doesn't seem to have a limit. Scalability has been great. Everything that we've run into that we've needed it to do, it's been able to do.

Even being a smaller consumer as we are, when we've submitted tickets, they've been very responsive even to the point of when we couldn't get our deployment deployed because we had an issue. They were responsive and within a couple of emails of them understanding our issue, we were on a phone call and had everything resolved over a phone call

The initial setup was straightforward. A different part of our IT department did the setup and they seemed to do okay with it. We had some hiccups with it. When I did some upgrades with that, I had a couple of hiccups, but I was able to actually work with UiPath and they were able to help us resolve our issues.

My first deployment took a couple of weeks.

When we did our original deployment, it took a couple of weeks just to research and understand exactly what we needed to do for the on-prem plus the other daily work that we had going on. It wasn't the highest priority because at the time I was using the community addition to get started.

Our very first project was the biggest return on investment.

For bigger businesses, pricing doesn't matter as much. It has the right packages. But for a smaller company, it's really tough. There could be better package options that suit smaller companies. 

A consultancy called Agility Partners came in to help us. We had the tax automation we wanted to do and they gave us some options of different things and then they pointed us in the direction of UiPath thinking it would be the best benefit for us.

As soon as you can, do it. You're not going to believe how well the automation will save you time, your company time, and even quality issues. This has been great.

I would rate it a nine out of ten. 

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.

Our primary use cases are for invoice processing and some legal intake use cases.

The benefits we see from UiPath are always time savings. I've never seen another benefit. It's always that people don't have to do manual tasks anymore.

The automation cloud offering helps to decrease UiPath's total cost of ownership, by taking care of things such as infrastructure, maintenance, and updates, if security isn't a big issue. 

With the cloud offering, you don't have as much control of where the data is and how it's protected versus the on-prem. If you're dealing with very sensitive information, you could introduce a compliance risk if you're using the cloud offering. But with the customers that we partner UiPath with, that's not an issue, so we use the cloud offering.

The screen automation features are the most valuable. There are some things, in an automation process that is complicated, that UiPath isn't very good at. And there are some things that are very repetitive and UiPath is good with it. For those repetitive aspects, it's obvious why it's valuable. It's replacing the amount of time that a human being would have to spend doing it.

We have seen that our clients have freed up time for their employees.

Our clients utilize AI functionality from UiPath. UiPath is really good at simple repetitive processes, but not as much at complex processes. The more complicated it gets, it breaks down because if it's less repetitive, it's less automatable.

AI functionality enabled our clients to automate more processes overall. It helped with end-to-end automation in the way that if you automate more processes, you save more time, and save more money for the company.

It is not very easy to build on automations. That's a problem with UiPath. I don't think it's very easy to build automation on top of it. 

Accessibility needs improvement. It would be easier to build on UiPath if they would have more employee-level users as opposed to consultants. Then that would increase the value of the product and the platform.

I have been using UiPath for two years. 

The stability is good. 

It's very scalable in our organization. The hardest thing is getting in and getting someone to build their first five automations and their first five robots in the first place. After that, it's very hard to rip out. Once you've already automated something and you've done all the in-depth work to set it up, it's pretty sticky.

There are around ten users and they're almost all solutions architects.

We've used Blue Prism and Automation Anywhere, but I think UiPath is the market leader right now.

Even though UiPath is hard to use, it's easier to use than Blue Prism. And it has more features than Automation Anywhere.

The initial setup is never straightforward. There are always bugs. It doesn't matter if it's UiPath or any other company, it's always complex. It's never easy the first time.

The implementation takes around three months. 

Ideally you don't want to take someone's job, but if you free up the time that someone was spending doing something, you don't have to pay them to do that anymore, or you can reinvest their time somewhere else.

It's expensive, but it saves a lot of money too.

My advice to someone implementing UiPath would be to hire someone technical to do it. It's not as easy to use as they say it is.

I would rate UiPath an eight out of ten. To get it to a perfect ten, it would need to be easier to use.