UiPath Platform Reviews

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.

Most of our use cases come in finance functions, however, we certainly have use cases spread across all sorts of other functions. For example, in HR. We've had a lot recently in IT operations and then also in broader operations. Obviously, that depends on the company we're working with. We're getting more and more customer-facing automation that is running all the way through the organization, from front office through middle office and back, across all different verticals within a company.

UiPath has improved our clients' companies and the way they function. For example, overall, automating the mundane and the repetitive allows people to do people things. Things like invoice processing and using Document Understanding to do that, enable your accounts payable team to look at the exceptions and do exception-based processing, which requires human judgment. Keying an invoice and working out who to send it to for approval should be rules-based. If it's not rules-based, it's probably an error or a miscommunication between the vendor who's sending it. Maybe it's a mismatch to the PO, and that requires human judgment. Therefore, just getting it out to a human to do that at the right time is critically important. If you're giving your people more time to do the exception-based management, you also give them the time and capacity to stop that from being an exception next time. Whether that's expanding the automation to be able to handle that use case, or whether it's educating your vendors when they're sending you invoices.

We work prominently with unattended solutions and larger end-to-end automation. What we're really loving about UiPath is the number of ways we can now inject human intervention at different parts of those larger workflows instead of looking at a big workflow and working out what parts of it we can automate, aiming to automate end-to-end and only working out the bits that we really need the human intervention in.

UiPath is constantly coming up with ways, whether it's through Teams or it's through apps, there are all sorts of different ways to get the human in the loop and get the automation throughput as high as we can.

Our clients use the UI apps feature. We use that for quite a few different functions. It helped to reduce the workload of IT departments by enabling end-users to create apps. That said, we generally work closer to the business than the IT side. We'd like to see it as taking the work away from the backlog that IT is looking to implement. You don't need an IT department that is quiet and doesn't have a big long queue of work. Allowing the business to be able to build their own solutions based on their business process is very powerful.

The UI apps feature has increased the number of automation. It’s certainly increasing the number of things you can automate and also the amount of a given process you can automate.

It has also reduced the time of creation. Certainly with the app creation, having a single platform reduces the time. You no longer need to integrate it with other different web forms or things you create on the front end, which we did a number of years ago. Now, it's one solution. UiPath can do it all.

For clients that use automation cloud offering, it has helped to decrease UiPath's total cost of ownership. It goes a little bit back to the IT side. You don't need to involve them nearly as much. Having a platform that is always on the latest version really, really helps. It also closes down the handoff between business and IT within the COE.

UiPath has saved costs for our client's organizations. The IT costs are different for each organization. We have clients who have an outsourced IT set up where they pay quite large costs to spin up machines and to maintain and upgrade those machines and services. Having the one solution as UiPath and offering the cloud is critically important for that.

In terms of on-prem instances, clients have saved costs there as well. We're very, very excited about the automation speed and the one-button deployment to the whole environment. That's certainly a step in that direction with on-prem. That will certainly save our client and us a lot of time. That way, everyone can spend more time building automation rather than building a platform to put them into.

The product has reduced human errors. On the same note, it also allows humans to spend a little bit more time on those exceptional cases. When the pressure may be on to get an invoice keyed it allows them to spend the right amount of time getting that exception handled. Then, of course, everything that's going through the bot is pretty much zero-error. The way the bots work, if there is an error it's going to let someone know. It's not going to guess and it's not going to fat finger.

We increasingly use UiPath's AI functionality. We certainly do on custom models with Document Understanding. We're just starting a project now to look at pulling entities out of emails. This is an exciting use case and I’m excited to learn about the capabilities that are being expanded.

The ability to automate processes is twofold. One of them is, it allows us to start to create human decisions. The human decision is the bit that you really need to automate around and starting to build that human decision-making into an AI model is critically important. The other side of that is that, when you're running automation, you have the ability to create a huge dataset. Everything that's being done is rules-based and it's data-driven so you can map everything every bot does, every button press if you want. That's a huge amount of data and a huge amount of input to AI models. Having it all in the UiPath platform is critically important for our customers. It's great that UiPath has lots of partners and we use partners, technology partners, to do that when required. However, the more that comes into the UiPath platform, the better.

We’ve utilized Academy courses from UiPath. UiPath's academy is amazing. It's unparalleled in the industry. We traditionally have done a lot of training for our clients over the years. However, we find with UiPath, we just point them in the direction of the Academy. We're always there to support, of course, and supplement any training that's specific to maybe a client environment or a client business system. That said, it's a fantastic resource for partners and for clients of UiPath.

The quality of the training Academy is great. It's also a tool to evangelize UiPath in our customer base. If someone hears about UiPath or they come to one of our demos through our delivery life cycle, and they really want to know something about UiPath, or want to get involved, or want to become a part of the COE or become a developer, it’s very, very easy to send them in the right direction. They can do the training they want to do, and they can get as deep as they want. It’s great and offers a low-effort way to evangelize UiPath.

The time to competency has been lowered with those that go through the Academy. It's not only learning. Learning things off slides. It's getting in there, it's whether it's a community edition or a training install, it's building things. Through the certifications, users can submit those things to get reviewed. This makes sure that people who are certified through the academy really do know their stuff. They've got hands-on experience. There's nothing quite like doing it in a real process. With the UiPath Academy, new users get as close as they can to that.

There should be extra ways for humans to interact with automation.

From what I've seen, and it's very early, however, there's certainly the direction they are headed, which is really, really great to see. It's my belief that Document Understanding will continue to improve. I'd like to see more predictive-type stuff, which again, we are beginning to see.  We'd love to get Document Understanding continually improving and having it more improved by the SMEEs who are performing the processes rather than the data analysts.

We've been implementing UiPath for just over four years.

The stability is amazing. Years have gone by and obviously, the product has changed a lot, however, of late, the last couple of years have been great stability-wise.

The object repository and modern folders have been great for the scalability of the solution. From the platform side, it's certainly easy to scale. We're very, very impressed on the automation suite side. You can deploy everything very quickly and you can scale everything up. 

The focus on reuse from a developer level is great to see. That's really improved in the last little while. On the other side of it, the actual scale through the organization, in terms of evangelizing automation, and making our customers an enterprise that automates first, there are numerous tools that do that really well. Whether it's the workshops that UiPath will come and do, or that we facilitate or it's through the pipeline itself, the scalability has obviously been a focus for the last little while. It's really, truly great.

We very rarely need to reach out to UiPath support. If we do, we know we're going to get a prompt response, and we're going to get a good answer. That said, we rarely need it. It's very, very good in general when we do use it.

We've got a few clients that run multiple solutions. They've been legacy users of another solution for a very long time. Citizen Development through StudioX is unparalleled in UiPath. Attended automation is obviously a strong point and has been for years. There are also things like Document Understanding. Document Understanding is much stronger than any of the solutions on other providers. There are those value adds that come in for that full lifecycle.

The solution is relatively straightforward. We have a dedicated platform team whose role is to implement UiPath for our customers, whether it's integrating them into the cloud or getting their business applications on the cloud. Or, whether it's an on-prem solution where we'll interact with their systems and integrate with their CyberArk or AD groups or whatever they need.

Each deployment is very dependent on the customer. We've had them deployed in a few days and we've had some that have gone on a few months, unfortunately. We find that talking to the risk group, the security group, and the infrastructure group all at the same time on day one of the project will make sure everyone's aligned - and that is the best way to mitigate the risks. 

The last thing you want is someone from the security organization putting their hand up in week four and saying, "Hold on, hold on, start again. This doesn't comply with one of the controls in our organization." It's about educating and keeping everyone, all stakeholders from the IT side involved at all stages.

The ROI that our clients have seen is very process-dependent. We've seen some huge 300 to 600% on particular use cases. Some of them are very easy to calculate due to the fact that we're taking work away from manual users. We've also seen some really good ones recently that are actually increasing revenue. Whether that's giving the capacity to sales-type items or whether it's tasks such as processing refunds and all those sorts of things that shouldn't be taking time away from salespeople, it’s been helpful.

The licensing can get a little confusing. There's been a move recently to create personas around licensing. My feedback from customers is that it hasn't necessarily helped. Some of the new enterprise-type agreements, the per-seat arrangements, are interesting. That's likely the way it'll go. Even then, it's still a little on the confusing side at times. We do a lot of work with clients to get them to understand the licensing model.

We've been aware of other solutions, and in comparison, with UiPath, it's the breadth of the lifecycle that sets it apart. UiPath as a platform, from the moment the first person at an organization thinks about automating, to reaping the benefits of that and improving the day-to-day work of the business, there's a solution for all of that. Whether it's process mining and finding automation candidates, it's the way UiPath brings different users into the automation. Apps and insights make sure we're pulling the right data out to keep generating the business case to grow the UiPath account itself. Also, along with that, is the ability to provide the extra benefit and knowing what benefit we're providing.

We have clients across both on-prem and cloud deployments. We have about 25% cloud, 75% on-prem solutions. We use various versions of the on-premises model. We probably average about 12-month-old versions, however, we do have clients on the most recent as well. We also have a couple of clients who are lagging a little bit.

I'd advise potential new users to get in there and get started. You don't know until you've tried. You don't have to look very hard to get started, however, it's important once you get going to start to think about how you scale and how you build an operating model around it. Maybe start small, and think big, and make sure you plan accordingly.

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

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 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. 

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.