UiPath Platform Reviews

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're a revenue cycle management company for medical billing. What we've done is we've replaced or reallocated our charge entry employees. We're using bots now to do the charge entry on medical claims and then also payment posting along with eligibility and AR. So we've been able to reallocate just within this last year, probably about eight employees. They've been reassigned to more valuable work, for example, things that the bot can't do and actually requires a human to do. We've been understaffed, therefore, it's actually worked out great.

The ease of building automation using UiPath isn't a problem; it seems to be very easy to do to a point. Our challenge is we work in a live environment. Therefore, we’re not able to use a test environment when we build things out. That’s why we have to go very slowly.

I'm not that familiar with the product, with the solution, however, the UiPath apps feature is great, although we're not using any of the apps currently.

The biggest benefit we've seen would be the accuracy. Even just with employees calling in sick, not having enough staff, we’ve been able to fill those roles.

The robotics piece has been a huge thing. We're doing medical claims. We're always worried about claims not getting paid. This solution has allowed us to been able to capture those claims so that we get paid the first time.

We also now can track how many times we touch a claim. For example, how many clicks. We couldn't do that before. That's been very valuable to us.

We’ve improved our efficiency. Even just our cost analysis has been great. As we do new contracts, we know what it's going to cost exactly.

UiPath has saved costs for our organization. We’ve re-allocated six employees and, for what they do, they're somewhere around $40,000 a year. We've implemented six bots to do those same functions and they're about $8,000 a year. We've almost tripled our ROI.

I don't know if it's UiPath as much as just what we do which is really complicated. Even the consultants that we've used with UiPath had said, "wow, this is very difficult what you guys do." There are a lot of moving parts. It's not as much of a UiPath issue. It's just our own processes.

I cannot recall the solution missing any features. 

We've been using UiPath for about maybe a year and a half tops.

I don't have any problems or concerns about the stability right now. The biggest concern I did have at the time was the fact that we've already invested six people in this in terms of the robotic piece and we're going to have a lot more. Since we've re-allocated these resources, and I have potentially 100 people where I could also reallocate resources, I worry about if something does happen or it doesn't work or there's no backup. If something goes wrong, I don't have employees to backfill as they won't exist. That's my concern. That hasn't happened yet, and I hope it doesn't.

The scalability has been great. It hasn't been a problem at all. We will just continue to add bots every time we need them. So far, it's been easy. We started with two. Three months later, we added another two. Another three months went by and we added another two. From our standpoint, it's great. My UiPath rep was shocked that I keep adding more.

I have not used technical support. 

We have a partner and they take care of it if something comes up. 

We had one issue with UiPath where something didn't work. We talked to them and it was taken care of within a couple of days.

We're working on something that may be called UiPath Insights. It's still not functional and there are some sources that we need. My vendor's working on that. I'm not quite sure what he means by it, however, he's working on it.

We did not use a different solution previous to UiPath.

The initial setup was pretty easy. Yeah. We didn't face any challenges with it.

I contacted one of the vendors and they ran with it. As far as I'm concerned, we didn't have issues at all.

The deployment took us about 30 days. After that, in terms of implementing the bots, the first bot took us about three months. As soon as we did the first one, it just went really quick after that. That's due to the fact that it was a lot of reuse. It was just us internally understanding what information was needed and how it works. In terms of requirements, it was all new to us. Even with the acronyms they use, I'm still learning as we're not IT-based at all.

We had a vendor that helped us implement it. We didn't have any challenges as far as that goes.

It was good. They didn't realize how challenging it was going to be or the person who integrated the solution for us, at last, didn't. At the same time, they know almost everything about my business now, however, I'm a little concerned about having to bring on more people as they're not in this industry. We're going to have to start them over from the kind of the ground up, which takes time.

We had a problem before with the pricing, however, for the most part, it's fine where it is now. My ROI is fine and it works great. I have no complaints.

The issue is you have to do a package at a time. That's my only challenge. Sometimes I don't need that much. I don't need that many licenses. The first time you sign up, it's a package of five every year. I don't necessarily need that.

We chose UiPath based on a referral. Somebody we heard speaking at a neurological healthcare conference about four years ago, who was not from  UiPath suggested that we needed to talk with UiPath.

I actually didn't know of any other company until after we were on UiPath.

This person was in our same space and he said it's fantastic. He had actually used two other solutions, however, he told us to go with UiPath and I trusted him. I've talked to other people since and they have said the same thing. We've made the right choice.

We started using the on-premise deployment for the first six months and then we actually moved to the cloud.

We're mostly using unattended bots. 

We haven't really reduced human error for sure. We haven't calculated that. We're just moving on to our Insights app. We're just getting ready to launch that. Therefore, we’re not there yet. We don't know what that turnaround is going to look like.

We do not yet use UiPath's AI functionality in our automation program.

We have not yet used any UiPath Academy courses.

When we first got involved, we just wanted to know if it would work. We just decided on a certain budget and decided to try it. Once it worked, we realized we actually had to step back. We started really looking at where we could implement it. We should have done that earlier. That's what I would tell people. It's an automation hub. You need to go through and find your best scenarios, your best ROI. I would definitely tell people to look at that first.

I'd rate the solution at an eight out of ten.

We're in the financial services industry, so we target the operations. We use it in finance but we're also going after our wealth management group, capital markets group, and fixed income capital markets group.

In one year we've done 17 automations in about 3,500 hours. We're just getting started. 

We use mostly unattended automation, but we do have both.

It's still early for us so we're selecting specific areas and items to automate based on areas that we believe will provide strategic importance for us.

We're now going to start expanding that and going after some of the larger jobs that we want to try to tackle, now that we've got some experience under our belt.

We have saved costs in terms of employee hours saved. There are definitely going to be costs associated with that. Some of those are pretty high net worth individuals that UiPath is doing tasks that they just didn't need to do.

It's definitely saving time for employees. One of our most successful automations frees them up from doing an entire task. Their quality of life has had a big improvement. It also happens to save a lot of hours. It saves a little over 2,000 hours annually.

We are still learning how to build automations but I'm a fan of the RA framework. We use StudioX to help with citizen developers to help fill our pipeline. The tools are pretty good and evolving.

The ability to bridge various applications that users are using is the most valuable feature. If we have a process that's entered in multiple locations, we can send a robot to do one of those processes on behalf of the person. We've had good success there.

Everybody on the team goes through Academy courses and continues to go back there for continuing education. Citizen developers are directed in that location as well. So we try to get them to complete StudioX. We like its ability to extend the life and the usability of some applications that by themselves can be a little cumbersome to use. I would like to make those apps and those experiences better for the user. And actually do more with them by extending parts through APIs that are passed to other applications.

We're looking to start to modify the meat of the process and then tag on pieces to the beginning and ends. 

Insights is a little clumsy. StudioX is a great start but needs more functionality. They should bring the document understanding into StudioX and make it go a little bit further. There's a pretty clear point at which you really need to switch over to Studio, but in the case of some of our citizen developers, they'd like to stay in StudioX. They just need more features. 

We have been using UiPath for a year. 

It's been very stable. The only problem we had were some digital certificates and those aren't UiPath's fault. It's partly our fault and how we manage them. One of those got in the way and shut some stuff down. It's not really the UiPath platform. That really hasn't gone down on us at all. It was the certificates. 

We're only at 17 automations now. We have a lot of headroom in the bots that we currently own and the licensing that we have. We're getting ready to put the necessary pieces in place so that we can scale it up.

The technical advisor is very good. 

Positive

 We have plenty of solutions that fall in the surrounding area, like various CTL things, automated software, and the types of things that are primarily used by IT.

We had a strategic partner help us with the setup because we knew nothing about it. They helped set up our COE and the basic frameworks that we were going to be using within IT. I came in about four or five months into the project as an analyst so I wasn't there when they did it. 

The strategic partner we used was very good.  They got us up and running and got our initial test trial into play.

The setup process was not straightforward. They purposely gave them some things that were a bit of a challenge. 

We are happy with what we got as a result.

The first deployment took quite a while. If you're considering standing up a whole COE in all those environments, they did that fairly quickly. I believe it was in about three months. It has then continued to evolve from there. That was the learning experience. If you look at our development, that first automation, there's a long flat line. Then it started to ramp up pretty significantly in the back half of the year.

Pricing is working for what we have right now. We set up two Orchestrator environments and we're unable to use our single license of the analytics on both. That's a bit of a problem. We'd like to see a dev environment for us that is free of licensing. It's development versus production. Charge us for production, don't charge us for dev. That's about the only complaint I would have.

Don't be afraid to jump in. Get the IT department involved early, get the security department at the table. As long as you have top-down management that's there to mandate and make sure everybody does what they should be doing, the proper sponsorship, and the proper buy-in from the people that have to execute.

I would rate it a ten out of ten. 

UiPath helps us to develop and build a center of excellence for our clients. I do development and technical implementation of the bots, best practices, and teach others how to do the development.

The client that I'm working with now is in the financial services sector. They do banking and life insurance. They do a lot of contracts and billing, backend, data entry-type work. We process all of the return mail that comes in, scan it using Doc Understanding, publish new bills, generate form letters, and all of those tasks that go along with managing the client for life insurance, annuities, 401K, etc.

A lot of the benefits we've seen are from FTE hours saved. We are looking at almost all of our processes, and it saves us at least a thousand or more hours per year before we go into implementation. We have around 20 in production. We're saving between 15,000 and 20,000 hours of process time.

From the user's perspective, people are happy that they don't have to do certain tasks that they didn't like to do. I only have one of those bots where I have a group of people that prefer the way they've always been doing tasks, but that's more of an organizational thing. I'm seeing across the enterprise with other folks that they're very happy to have this. They are putting more use cases in, and the frontline workers are bringing in use cases. Of course, we need to vet a lot of those so that we get enough bang for the buck, but we're finding a lot of adoption across, up, and down the whole scale so far.

There's also been a reduction in human error. There are so many use cases that have been more on the production side of things, like productivity as opposed to risk avoidance. We enter data and we do bank transfers, so it's important to key the data correctly. We use the attended bot to do that. We took a paper form. We push it in, it comes in as an unattended bot in the backend to read an email from a person and put a transfer in place. It gets approved and put in the queue.

When they run the attended bot, it allows them to do an RSA key into their external site, take the data, watch it go in, they see it, we audit it on the backend with a second user, it gets pushed in, saved, and submitted. From that perspective, if you're dealing with 10, 50, or 100 transfers a day, where you could key in the wrong number, it's important.

That's been helping. Employees are happy that they don't have to type it all in, and that they don't have to worry about the errors as well. It offers peace of mind for those folks.

Getting the bots going and working is the most valuable aspect. We have about 20 or so in production. We're building out from there. We've been very focused on Studio and Orchestrator, as opposed to some of the other product lines. Because a lot of what we're dealing with pertains to advanced technical people like myself that are helping them along that journey.  

It's easy for me to build automations but I am a computer scientist. I have a deep technical background. A lot of what I've been doing is trying to teach people how to build resilient bots, and how to build processes that will run. To me, one of the big things to meet your ROI is that you need to build things upfront that work. You need to verify them, test them, componentize them, and put them together. Otherwise, you're going to spend too much money on the backend with maintenance.

If you can get people to think about what do to in the event of a failure, even from the developer side of it, then they can create things that we can run, and we don't have to do so many new maintenance and operations tasks on it. That's vitally important.

I have used the UiPath Academy courses. I'm a certified developer. I didn't know UiPath at all. I went through the Academy and trained myself. When I brought in new developers, I had them do modules and I sometimes go visit them. 

The Academy is pretty good. It's very helpful to have something like that. Personally, my favorite side of things that UiPath is bringing to the table, is a community edition in the cloud. I can go out and play with the latest and greatest. I have my client's laptop, but I also have my own personal laptop and I go out to the cloud and do tasks out there.

I want to bring what's new, help bring to the forefront what we might want to do in the future, and get a hands-on perspective, without having to go to the client and bug them about bringing in a license for something. That's great and I hope they continue with that.

The fact that they're not charging for training is great. It brings on more developers. The barriers to entry for people are low. And the more developers you have, the more adoption you're going to get.

There's a lot of technological growth that should be done. They need to learn from customers. I talk to people about Doc Understanding which is relatively new. There's a lot of people in the document world that have more experience. They should learn a little bit more about what Kofax has done over the years with their validation actions and those types of things.

There should be more growth, but the platform is there. As they grow those things they should take each piece and make it better. If you start with a good platform and you build it up, it's going to get better. What we have today is very usable, and is only going to get better. I look forward to it.

They should talk to their customers and understand their use cases. Give customers what they need. 

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

Stability has been quite good. I see technical glitches once in a while in the Studio, but when you're running on Windows, it happens. The glitches don't happen very often.

It seems very scalable, in terms of rolling out new processes. We're more limited by machines and getting things set up than we are by what Orchestrator can handle. We have one attended bot and we're 95% unattended.

We have plans to increase usage. Our clients are growing from two developers, a QA and a VA, to a VA, and a team of two pods of six or seven developer QA types, to implement use cases over the next couple of years. They're on a very high trajectory of growth.

I go out to the community a bit. I Google looking for what everybody else has said and figure it out. We only have a couple of different use cases where we've gone back to UiPath, and the ones that we had the most difficulty with, we went right through the local sales rep to get things going. I found their support to be good.

The initial setup was straightforward and easy.

I set up Orchestrator servers, I put bots out into the systems, and I installed Studio in the client's environment. The only problem I have is with the way the client environment exists. Security gets to be a hassle. 

One of the things the company focuses on a lot is employee satisfaction. From a cost perspective, we haven't necessarily gotten to that level. I've been there for two years. I'm a consultant. We have other consultants. We're saving $15,000 a year, while we're displacing certain cost dollars from the people that did those jobs, we get paid more.

Cost-wise we're fairly evening out, and probably bringing an MROI. This is a longer scale process for them, to take them along this journey. It's important for businesses that go under that, to not necessarily focus on year one, year two. We look at this as a longer-term endeavor for them. The key benefit that they see out of it right now is the future. The workers are satisfied not having to do the "bad" work.

I found UiPath to be pretty cost-effective. 

I would rate UiPath a seven out of ten. I see it as a maturing product. It's done very well, because it is stable, and it does build real use cases. But I look forward to the future. There's a lot of good going on here.

We're a revenue cycle management company for medical billing. We've reallocated our charge entry employees. We're using bots now to do the charge entry on medical claims and then also payment posting along with eligibility and AR. We've been able to reallocate about, just within this last year, probably eight employees. They've been reassigned to more valuable work - things that the bot can't do and actually requires a human to do. We've been understaffed, so it's actually worked out great for our company.

The ease of building automation isn't a problem. It seems to be very easy to do to a point. Our challenge is we work in a live environment. We're not able to use a test environment when we build things out. We have to go very slowly.

I'm not that familiar with the product, with the solution, however, the UiPath apps feature and OCR are great. That said, we're not using any of the apps currently.

The biggest benefit we've seen is the accuracy. Even just with employees calling in sick or not having enough staff. We’ve been able to fill those roles.

The robotics piece has been a huge thing. We're doing medical claims. We're always worried about claims not getting paid. This has been able to capture those claims so that people get paid the first time. One of the other things we track is how many times we touch a claim. For example, how many clicks. We couldn't do that before. That's been very valuable to us.

We’ve improved our efficiency in a way for sure. Even just our cost analysis has improved. When we do new contracts, we know what it's going to cost exactly.

I don't know if it's UiPath as much as just what we do is really complicated. Even the consultants that we've used with UiPath, even they've said, wow, this is very difficult what you guys do. There are a lot of moving parts, so it's not as much of a UiPath problem in terms of limitations. It's just our own processes.

Right now, I don't think I've been on there long enough to know if there are missing features or functionalities I’d like to be added.

I’m talking to people right now, to see how it can do things better or how we could use it more effectively. We’d like to discover what worked for other people.

We've been using UiPath for about maybe a year and a half tops.

I haven't had any problems or concerns right now concerning stability. The biggest concern I do have is that we've already invested six people in this. We're going to have a lot more that will, more or less, not have the robotic piece as part of their job. That work will be reallocated. I have about a hundred employees that UiPath could technically reallocate.

When I look at that, I worry about if something does happen or it doesn't work or there's no backup. Then, suddenly, I don't have employees. Right now, we can jump in and some humans can do the work if necessary. My concern is that in the future they won't exist. This hasn't happened yet. I hope it doesn't.

Scalability hasn't been a problem at all. We can just continue to add bots every time we need them. It's been easy.

We started with two. Three months later, we added another two. After another three months, we add another two. From our standpoint, it's great. My UiPath rep was shocked that I keep adding more, so that's good.

I have not used technical support.

That said, we had one issue with UiPath where something didn't work. We talked to them and it was taken care of within a couple of days.

My vendor is working with them. They mentioned there was an issue with insights that they are working through. Insights are still not quite functional, or there are some resources we need. However, the vendor is dealing with it directly. It's a work in progress. 

We did not previously use a different RPA solution. 

The initial setup was pretty easy. We didn't have any challenges with that. I contacted one of our vendors and they ran with it. We didn't have issues at all.

With the vendor, it took us about 30 days to deploy UiPath. After that, in terms of implementing bots, the first bot took us about three months. Once we did the first one, it just went really quick after that. We could reuse some processes which made it faster. There was a lot of reusing of the same. We were also internally understanding what information they need and how it works.

It was all new to us. I'm still learning the acronyms they use. We need to learn what they are talking about. We’re not IT-based at all. It's definitely different.

We had the solution implemented by a vendor. They implemented it all. We didn't have any challenges as far as that goes.

Our experience with the integrator was good. I would say that they didn't realize how challenging it was going to be or, at least, the person who integrated didn’t. At the same time, they know almost everything about my business now.

UiPath has saved costs for our organization. For example, we’ve allocated six employees that are paid around $40,000 a year and we've implemented six bots to do those same functions and they're around $8,000 a year. In a way, we’ve doubled our staff, and almost tripled our ROI.

We had a problem before with the pricing, however, for the most part, it's fine where it is now. My ROI is fine. It works great. I have zero complaints.

You have to do a package at a time. That's my only challenge, where sometimes I don't need that many licenses. 

When you first sign up, it's a package that can renew every five years. I don't necessarily need everything. I'd prefer just to pay for certain pieces. 

We did not evaluate any other options. We started using UiPath due to a referral at a neurological healthcare conference about four years ago. The speaker suggested UiPath. I actually didn't know of any other company until after we were on UiPath. We've since talked to others who have used other solutions and they mentioned that we made the right choice when we chose UiPath.

We started on-premise for the first six months and then we actually moved to the cloud.

We do not use their UiPath apps feature as of right now.

We are mostly using unattended automation.

We haven't really calculated the reduction in human error. We're just moving on to our Insights app. We're just getting ready to launch that, so we're not there yet. We don't know what that turnaround will be.

We do not use UiPath's AI functionality in our automation program right now.

Our teams have not yet used the UiPath Academy courses.

I'm a little concerned about having to bring on more people that are not in this industry. We're going to have to start them over from the ground up, which takes time.

When we first started, we wanted to know if it really worked. We got a certain budget and just started using it, and now I can say that yes, it does work. We can see that now that we've stepped back. We should have done it earlier. That's what I would tell people. I would definitely tell people to look at it first, before anything else. 

I'd rate the solution at an eight out of ten.

We are using the solution to create application reports. What we've done is take all of that information, where somebody was initially doing everything as it happened, and create templates that work in another application. Due to our business model, we have multiple applications that are similar but very different. Rather than have somebody go into this application and update it and then go to another application and put in the same information, we've developed bots. We'd go to the template, input the information one time, and let the bots go in and open up the other applications.

The solution has improved the organization just by freeing up the resources to do that MBA work so that the bots can actually do things for you.

We use the solution's UiPath app feature. It has helped to reduce the workload of our IT department by enabling end-users to create apps. That said, I myself am in IT and not a developer.

The UiPath’s apps feature has increased the number of automation created while reducing the time it takes to create them. We're just now starting with that. We’ve only got 10 bots in production. We've got another eight in development right now.

Likely, the automation we’ve created has saved us probably in the neighborhood of one full-time person.

The solution’s ease of use and the UI is great, specifically for the users. Not necessarily the developers. The people actually using it find it very easy to use.

In terms of the ease of building automation, from what I've seen, I'm very impressed. We're using a partner. We built the COE and everything that they're developing right now. Obviously, we're just starting down this path. This means we're going to go work with a partner while we're developing our own guys. We can get to market quicker.

We've got our own VA. The next step will be looking into building our own developers.

The solution has reduced human error. There are still errors in the templates. People still have errors with bigger things, however, we're able to catch it before it gets into any of the applications. Reading the information across the other applications, you can stop it before it gets synchronized into the applications due to the fact that it is the same source. It doesn't go into "A" if it's not going into “B”, for example.

This has had a big impact on our business. In our model, it's a little complex as our customers are our clients. For example, in the ATM business, they charge us a fee, so we partner with a large retailer like Walgreens or CVS and we share the revenue. We actually pay our customers as they use our services. With the help of UiPath, we’re able to keep everything synchronized. We’re not sending stuff to the wrong site, or to the wrong corporate headquarters.

The solution has freed up employee time due to the amount of work that it's doing. We’ve got just one bot and it can do triple the work, covering three full-time employees in a week. Likely, existing employees now can focus on higher-value work, including more customer-facing tasks. We're getting a lot of financial requests and maintenance. They require human interfacing rather than doing manual transactions.

I can’t think of any direct places where improvements need to happen. Whatever I need, it appears to be there. That said, any app could use some form of improvement.

I've been using the solution for a year now.

The stability is very good.

I don't see an issue with scalability. We are nowhere near capacity yet.

While I have not dealt with technical support directly, I have not heard anything bad from anyone.

We did not use a different RPA solution beforehand. About two years ago, in the second quarter, that's when we started opening our eyes to the possibility of automation.

The initial setup was pretty straightforward. We have a partner that assisted in the implementation. 

From the time we signed up until the time of setting up the COE and then getting going, it might have been a few days to deploy the solution.

We have a partner that has assisted us in the implementation process. 

Everything that we've done so far, due to the fact that we run everything through COE and then submit semi-annual budgets, has been good. From the perspective of everything we submitted so far, we've been pleased.

Over and above the subscription fees, we're paying probably $51,000 a year right now.

The pricing is okay. It's not out of balance with what it offers. We are definitely getting value for it. 

We didn't really evaluate other options. We were new to it, and we had a partner that steered us towards UiPath.

At this time, we do not use the solution's AI functionality in our automation program. We also have not yet used UiPath’s Academy courses. We may in the future.

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

We're using UiPath on the customer side, where we have lots of data and PPs on the customer information. We're trying to put in what the customer is including, and then using machine learning. We created a Python type of UiPath to do machine learning and automatically build that so that items can be automated. That was our POC. That said, we're exploring more, to get into the finance area, where we can take invoicing and general revenues and the closing worksheets and automate those processes.

The biggest improvement has been in the ROI we've seen, which has been $55,000 in six months' time. 

The whole bot process and the way scheduling is done is a very valuable aspect of the solution and it's really cool.

In terms of the ease of building automation using the solution, we’re very near achieving that. It's taking more time than what it's supposed to be taking, however, I don't see any complexity in building the code nicely.

So far, the solution has saved costs for our organization.

I’m not sure if the solution has reduced human error. It’s hard to tell at this point. We’re in the early stages. However, simply by looking at the way it’s built, it will.

The solution has freed up employee time. Once again, it’s too early to say too much, however, we are saving approximately 130 hours per month. This additional time has enabled employees to focus on higher-value work. They don't need to just go to the system to click here and there, they're spending more time with the customer.

The management team is more satisfied as it’s much cleaner, with less human error. Management reporting shows definite improvement. In terms of overall employee satisfaction, employees are still not quite trusting the bot. The bot does something and they will go and still validate that. They don't have a hundred percent trust yet. That's what we are trying to build right now.

We have used UiPath Academy courses. It's taking time due to the fact that we have a consulting partner who's helping us. The majority of the workload is being handled by the consulting partner. We're trying to play just the B role of supporting. We're not doing too much development.

That said, with UiPath Academy, just the ease of accessing the material has been great. It's simple.

The only thing which I see is missing, is it does not have an inbuilt machine learning. You have to teach the bot. The bot is not self-learning.

For example, right now, we are using a description. Based on the fields or the description, we're trying to identify what is the category to be used. I have data for the last five years. The bot should be able to go and learn by itself tasks such as "These are the five things which I need to add," instead of me manually maintaining it.

I've been using the solution for six months.

The solution is stable. I don't see any problems.

The scalability I still need to figure out. Right now, with the licenses we have, I don't think we're going to scale it out to where we want it to be. It's my understanding that it just involves increasing the number of parts or number of processes which we can run. It will probably be scalable, however, we have not tested that, and therefore I cannot say either way.

We have close to 30 users on the solution right now. It's mostly our customers' manager and their team.

We do plan to increase usage in the future.

Technical support is okay. I have not really invested a lot of time in getting support from UiPath, however, I get a response.

We did not previously use a different RPA. We had a CIO who'd used it before and based on their experience, we went to UiPath.

In terms of the initial setup, the system side is straightforward. It's the business side that took us a lot of time to understand the concept.

The deployment itself took three months.

The company is probably going to need to negotiate. It's competitive right now, however, once we scale it out, there's going to be some room for negotiation. Likely, UiPath will be responsive to negotiations.

We did not evaluate other options before choosing UiPath.

We're likely using the most up-to-date version of the solution, however, I don't know the version number.

We don’t use the solution's AI functionality in our automation program yet.

I'd advise potential new users to go slow. Always create the roadmap first. Take smaller pieces and then implement those. Don't wait too long, however. Otherwise, you will lose user interest.

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