UiPath Platform Reviews

Right now, the primary use case is document retrieval from our client system. We are a healthcare billing company, so we have to pull things like medical records and different documents from hospital stays. So, we used the robots to pull those versus an FTE.

We have both unintended and attended robotics that we use. We haven't really delved into Studio a lot yet. That's going to be part of our staging and going into the next phase. We built all of our basic bots, so now we're going into the more complex bots.

We are on-premise. We were looking at moving to the cloud, so that will be something in our next steps.

It has a really good turnaround time for our operations department to start working on claims, because all the information has already been pulled upfront with the bots. Instead of having to go into an account and request medical records or a certain type of document, it's normally already been pulled on the front-end as soon as the account loads because we run everything through the bots.

The most valuable feature right now is we have been able to utilize our staff better with the bots. We can put them on more high priority items. That was the one thing that everyone was afraid of: The bots would replace them. What we did is retrain them to do other tasks that we needed, as that was more of a priority for us.

We do deal somewhat with Citrix. It depends on the client and how the bot has to be set up. We have some clients who do run through Citrix, then we have some who use a VPN tunnel to get in. So, we have it on both.

The implementations or integrations through Citrix are really good. The only problem that we are coming across is just maintenance. If the Citrix platform gets updated and we're not notified, it breaks. So, we have to reconfigure our bot to the new updates. Unfortunately, that's just the name of the game, and that would be true if we were pulling them manually versus a bot. We would still run into that with the Citrix platforms.

I would rate stability as a five (out of five). We have not actually had any issues with UiPath. Most of our issues have been with just platforms changing, breaking, and the regular maintenance.

We have about 40 bots right now with 30 ready to be made.

Our team is really small. We have roughly six people who are working with the developers and actually running the bots. We're the only department using the solution. Our department was asked to lead this on, so we've been very fortunate to be able to lead it and be able to help our own department first. Now, we're starting to look at other areas of the company to deploy RPA.

We have not used UiPath technical support.

The initial setup was a little complex, but that was because we really didn't even know what we were getting into. We were told by upper management (our CFO) that automation was the next frontier and we had to go that route. We were sort of the pioneers going through this for our company,

It probably took about six to eight weeks for us to talk with development and for them to get the context of what we wanted. It took them about five weeks to actually build the bot. Then, once they built the bot, it was in production. Of course, we had to go back and do some maintenance because it did not work first time. After we got the hang of it, it's been great.

We got some consulting from UiPath. We do use their developers. Other than that, we do not go through a third-party. We did everything else ourselves.

Our experience with UiPath services was good. There were some bumps along the way. It's just trying to understand the process and RPA from what we've seen.

It took us about six months to really see what the bots could do. We then started tracking financial savings and how it's helping the company. We set out a bit differently. Our CFO came out, and said, "Automation is where we're going," but on top of that, "This is X amount of money that you have to save in the process."

We have spent the last 18 months tracking how much we are spending and how much we're saving. We hit the goal with no problems because we were able to shift staff. We did eliminate some staff, but this solution really brought out the skill level of our employees. Those employees with the higher skills were able to transfer to more important projects.

Within the first year, we saved a little over $600,000. That totaled to almost 19 FTEs which we ended up saving.

We haven't used any other vendors.

We are on spreadsheets and data. I keep saying we're stuck in 1996. It's been nice to have the vision of being able to be in the 21st century and really be able to use the bots the way we want to use them.

We have not taken part in the UiPath training. That's something that we talked about right before this conference. We really need to start utilizing more of the training that's offered. We want to turn some of our soft coders into people who can really code for us, not always relying on developers to do all of our work. That's definitely something that we're implementing soon.

I would rate it at least a four (out of five) for ease of use. We don't deal so much with UiPath, but from what we do deal with outside of developers, we have not had any problems. It has been very user-friendly, for those of us that don't know coding. We are able to look at things, sort of fix things, etc.

I rated them a four for ease of use, not a five, because we want to see what UiPath can do. We have a lot on the table. We have 30 bots ready to go. A lot of it's more screen scraping, which will be more complex. So, we want to see really if UiPath can do what they say the solution can do. We want to test its scalability.

I definitely would say UiPath is the way, especially with everything that they're coming out with now. It helps you understand more about RPA instead of just being thrown into things. It helps you understand all that on a smaller level. It is what everyone else has said here at the conference too, "Start with a small project. Don't go out with a big thing because it's not going to work." Luckily, we did start small, and we've just grown from there. Those would be my suggestions.

I would rate the solution a 10 out of 10.

We use it to automate administrative functions, like finance and HR tasks. We are also automating a lot of things in our SAP systems, e.g. updating prices. 

We use it for a lot of small tasks, like downloading something from an particular internal website (e.g., SharePoint in Office 365) and uploading it back, or for doing modifications, then loading them back.

We use it in a very large way across the company. Last year, we implemented approximately 22 processes and saved close to 80,000 hours total. This year, we have already saved close to 6000 hours. 

You don't need to know coding, as it's pretty straightforward. The graphical user interface is easy to use. It is drag and drop. You do need to understand the basics of what's happening, what you're doing, and how the technical things work. However, after a short bit of training, you can start doing stuff, and the more you learn, the better you become. 

There are so many workarounds. It allows you to do complicated things in such an easy way. UiPath has provided so many APIs that make it easy to interact with other databases or applications without even going into them. If I want to download something from a website, then I don't need to necessarily go into it, I can use the API function, which is very cool.

With Excel applications, it is not able to handle a lot of pop ups. It should be able to do this automatically. We just change the format of the file from XLSX to XLS, but it should be able to handle this automatically. Instead, when something pops up, it gets stuck there. This type of thing are small, but still the process gets stuck. I would like to see better integration of applications to avoid these issues.

We are also making a lot of manual changes in SAP. We are looking for a solution where we don't have to make manual corrections every time, similar to what UiPath did with some SharePoint websites.

Less than one year.

The product is definitely reliable. It gets the job done. The difference is in how you design it. When you start as a developer, you tend to always take the longest route as part of the learning process. Once you get used to the product, you realize something can be done in two steps instead of five.

A lot of people rely on what I design, so if it doesn't work, I immediately get a call that 50 people are waiting for something. This happens, but rarely, as it works perfectly.

Whenever we get stuck on something and are not able to proceed, then we get in touch with UiPath, who will help us out. Their technical support staff is pretty good. These things really help the user out.

Initially, I used the UiPath Academy when I didn't know anything. At that time, I went through the basic training, then I had to leave the academy to focus on automating our company standard products, like SAP.

I have been working with this solution for 11 months. I did not know about this solution before working as an RPA Developer. Now, you can challenge me on anything UiPath related, and I will find a solution. It is so easy to learn new things. It has good usability.

We automate mostly finance processes, which is our largest area. We also automate some HR and logistic IT processes.

We hear from the process owners that they are very happy with the lead time and data quality, which keeps getting better. 

It is very easy to use, and you still have a lot of possibilities to modify what you are trying to do and achieve. 

We would like more API integrations, especially more API connections to SAP. While this is on the roadmap already, activities and packages with more automated API connections to other software or platforms would really help us.

Documentation-wise, UiPath could get a little better.

The support that we are receiving from UiPath is superb.

We are using the UiPath Academy. We also have our own development standards. When we are recruiting new developers, we first have an introduction of our own that we make. It's mostly to Orchestrator and our environment, then we set them free at the UiPath Academy to do training there. Afterwards, we do some additional training to our standards and best practices. So, part of our training is in the UiPath Academy, and we are using it. We have been very happy with it. It's evolving all the time, which is really good

One place that we struggled was when we were uploading the software. UiPath was helpful with getting started, setting up the server, and installing the robots. All that went pretty smoothly. Every time, when we have upgraded, except for the last time, we have struggled. We did not do it right once. We always had to retry, get some support with it, and the documentation was a little lagging. Therefore, we really struggled with upgrading. It's getting a lot better now, but this has been one place where we have struggled.

Annually, the product saves us 25,000 hours. Everyone is satisfied with that.

We have had our contract with UiPath since November 2016. 

We have had a few presentations from Kapow. They have dynamic licensing, which is something that we would really like to have, so we could scale up at peak hours or peak times of the month. This is when we really need to throw more robots at some processes. To my knowledge, that is not possible with UiPath at the moment. Though we are not considering switching at the moment.

Our primary use case is IDP. We're in the Fed market, so a lot of it is all IDP driven. AI and automation are priorities. We're not exclusively a UiPath shop, but we're shifting to utilize it more because we know there are opportunities, especially in the realm of document capture.

For us, it requires fewer resources, and the time to get to the production environment is quicker. It hasn't significantly impacted our stakeholders yet, but people know the brand. When we talk with customers, they ask if we know about about UiPath and if we're a partner. 

We're moving away from the current platforms because they're less robust. The RPA tools we've used previously haven't kept up with the pace of change. UiPath is a leader that has continued to progress with RPA development and invest in improvements. 

We're still in the early stages with UiPath, but two things that will help are the Copilot and the Autopilot. We'll be able to generate new processes based on the learning that's taken place. It will have a significant impact on the things we do. Generative AI is not new to us. We've had these discussions for a while, and our CEO is well-versed in generative AI. Software companies are coming to realize the value and implement it. 

UiPath has spent the money on research and generating libraries. The out-of-the-box libraries are extensive. In the past, we used standard capture products, where we had to create all of the extractions in the zones and all those things. UiPath offers faster implementation. 

UiPath's pricing could be improved. The margins for us as a bottom-level tier partner are not great, which can be a hindrance, particularly when we present it to the customer. Other than that, I don't have any areas of improvement at the moment due to our limited experience. Maybe after six months to a year, we might have more feedback.

I have been using UiPath for several years, although I only started with this company a couple of months ago. Previously, I led a team for four years with another organization.

The stability of the solution has been good. I haven't experienced any platform issues. Any issues that arise typically relate to coding or interactions with third-party vendors.

Reflecting on my previous organization, UiPath was able to scale effectively.

I rate UiPath support eight out of 10. My previous experience with UiPath's customer service was really good. The support from the sales and presales levels and the technical specialists was excellent. They were all willing to help and work with us.

Positive

We eventually switched from our previous solution because it did not keep up with the pace of change. The company did not invest in their product and failed to keep up with the latest and greatest technologies.

It's too early to tell if there's been a return on investment with UiPath.

Pricing is a significant area for improvement. We see little margin as a bottom-level tier partner, which makes it challenging when communicating pricing to the customer.

I would rate UiPath an eight out of ten.

We're still in the exploration and discovery phase. We're learning about UiPath's capabilities and how they fit into the overall picture. We haven't separated AI from our normal process at this point. I work in our company's contact center, and we engage them in many different ways. We talk to management about their problems, report large volumes of transactions, and work side-by-side with the agency to find trouble cases and where they frequently perform manual tasks.

UiPath has helped our customer success unit and various technical teams. We were trying to understand the industry's current state and the direction our peers are taking. We're not so focused on eliminating positions as we are on using UiPath to free staff to work on additional tasks. There are always new tasks in the contact centers, and if we don't need to add staff, we can redirect them to other areas.

We were looking at implementing most of the features. I don't look at it with a specific lens but try to understand where all the tools are and how they can best help us in each situation. I don't have a favorite tool but try to understand how to use each one in combination to give the utmost business value.

Being able to escalate quickly is not a strength for UiPath and may be a focus area.

My department has been using UiPath for about two months.

The people from UiPath, from customer success to various technical teams, have been very helpful. When we open tickets, they respond quickly and escalate to the appropriate teams.

Positive

We did have a different solution. Deploying the solution to our agents' desktops was essential, and UiPath's advancement in that space and innovation position was enticing.

The initial deployment was fine. We had an on-premise deployment and weren't using the Automation Suite. It didn't work for us at the time. There wasn't a lot of flexibility there. I understand that it's changed, but we've already deployed on-prem. We've grown, and the complexity is through the roof, so now we think it's worth transitioning to an alternative solution.  That part has not been great, but at least there are places for us to go.

UiPath is expensive compared to competitors. We're examining where the value comes in and their ability to continue being a leader to justify the cost.

I rate UiPath eight out of 10.

I've used it to automate different types of processes. My first project was to automate PDF documents. The process was a bit lengthy for the client. The client actually used to enter the information into the PDF templates and get them submitted to the government websites. And once they submitted their documents, the government released grant payments or other stuff. Previously, they hired people to do the data entry. However, it was taking too long, and some crazy errors. They had to have a pretty formatted, clean Excel sheet.

With UiPath, the bot would choose the data, get the data from there, and then put it into PDF files, save them with the sort of renaming schemes, and then upload them to the drive and then to the portal. That's the first use case I got. I built up workflows in it and automated the whole process. 

I keep exploring it and now have other use cases coming in as well. There are more than 150 or 200 use cases for different types of projects. 

The process management is great.

The orchestrator is helpful. And they have something called live monitoring. If you have an unattended bot set up on someone's system or in a virtual private server, when the bot gets executed, you can actually monitor it in the live stream. You can open up the live stream, keep checking it, and look at the automation, and how the board progresses, and you can take control of the live stream in between as well if you want to. 

The ease of building automation is relatively very good. Most of the programmers and developers get hectic while writing scripts. However, they get bored. Now we can just create a sequence of processes. That way, we can train some colleagues, and it's pretty easy.

I've used the solution for a good cause, for a client trying to gather information from the Internet in Switzerland to reduce carbon emissions. They were trying to get a lot of information to raise awareness regarding emissions and businesses. I helped the organization implement a use case.

The product enables us to implement end-to-end automation. There are certain scenarios in cases where integration is required. It is important based on certain scenarios or use cases.

The user community is great. When I was starting out, I really got a lot of help from the forum. The community is very good. The most common questions are already being answered there, and everyone is engaged. The community is pretty strong. You can just post your question in theory and get a reply real quick.

The solution has helped to minimize our on-premises footprint. You can just get it all done on the cloud. They have recent updates coming in in which you don't need to install any tool on your system. You can just develop your workflow on the cloud as well. 

It really helps non-technical people. I don't need to go through the hassle of installation. I just go to the cloud and start developing the basic workflow.

The UiPath Academy is good. I didn't have a chance to do a lot of the Academy yet. I have had one or two trainings for the implementation methodologies. That said, mostly I've learned through real-time projects or through my self-learning, plus the content we have on the Internet. 

The AI functionality is used in our automation programs. It has documented understanding. It has built-in trained models that help understand the document. You simply go to the document, scan, install the package, and just train your invoices and the data you have with similar invoices. It helps you to identify the invoices and extract information from the structured data. 

UiPath has helped speed up digital transformation and significantly reduced the cost of digital transformation.

It's helped reduce human error. Being able to have RPA enter information again and again really helps solve the problem of dealing with random errors. 

UiPath frees up employee time for other stuff. It helps optimize time and make everything efficient. Whether it's attended or unattended mode, it really helps employees. We can save a lot of hours. The automation hub that they offer can upload all the stats. It will take a process and tell you how many hours you could save. The cost savings are directly proportional to the time savings.

I used to have some workflows that were a bit lengthy, and I just see that some of the time, they crash. It's unstable if the workflow is long. Sometimes you'll run an update, and it will make a workflow crash. 

They could make it more user-friendly. 

I've been using the solution for around four years.

The solution does crash sometimes. 

In one instance, I was trying to read a file, and the file itself was a bit larger. It's hard to read a large number of files.

The scalability is good. I would rate it eight out of ten. 

I haven't contacted technical support that often. I only reached out to get more information on a certain case. 

Positive

I did not use any alternative previously. However, since using UiPath, I've also used Power Automate and Selenium. Selenium is not a direct competitor. However, I have used it a lot. Power Automate doesn't have the robust community or forums that UiPath has. That said, it costs less. 

I'm an implementor. I deploy solutions for my clients. 

The cloud implementation of UiPath is straightforward. If you are knowledgeable of the process and you're good in tech technology, you can handle it. If you are non-technical, then it could be a bit of a lengthy process to learn first and then go ahead and do it.

The deployment can be handled by a single person, depending on the use case. If it's more complex, you may need a team to deploy.

There is maintenance required. If there's a change to the website, process, platform, or data point then you have to go in and adjust. 

The licensing cost is pretty expensive compared to competitors. 

The community edition, however, is pretty good for developing automation. You can have one unattended product as well, which you can utilize. 

A developer license may be around $420 or $450 a month, which is really expensive. 

I'm a reseller.

I'd rate the solution nine out of ten. 

I would advise others, if they mean to use the product, to be specific and look at the cost structure. A small business will always need to be mindful of the cost structure. For a smaller business, the community version might be an option. 

Overall, the orchestrator, the cloud management, and a lot of their features are great. 

We do a lot of claims processing for healthcare providers. We handled the billing, and it was very beneficial for us to use automation to perform those claims management and submit the claims for those various providers.

We utilize Orchestrator, the robots, both attended and unattended, and team sites.

Our organization was trying to achieve better accuracy and better throughput with this AI-powered automation initiative. We were just getting all the claims processed that we needed to because we just couldn't keep up with the workload. Using automation was a requirement.

It is very important that UiPath has orchestration. Without Orchestration, we wouldn't be able to do anything we do. My team specifically manages the Orchestration, and after the automation goes live, they come to my team to manage. 

Without Orchestration, I couldn't comprehend how we could do it. We have 360 machines running over a hundred processes with thousands of transactions a day. Without Orchestration, I don't see how we would be able to use the function.

Unattended robots with Orchestrator are our bread and butter. We don't do very many attended automations. It just seems that they are much more resilient when we run a program in a way that doesn't involve any users. 

We did have insights at one point, but that was prior to it being re-engineered by UiPath. We have to pick that back up because it didn't really work for us back in the day, but I've been told that they've changed the vendors that they've used for that product. We've re-licensed it, and we're in the midst of reimplementing it.

We are working with a vendor, Namica, the UiPath vendor and we are starting with task discovery processes. We're just touching more on task capture instead of process mining.  

We would like to see better connectivity with different technologies. We found credential management to be something that is a real problem for us, especially working with third-party systems. 

Being able to manage those credentials and have a product that could help us with that would be nice to have. We've ended up using CyberArk WPM for this purpose. But it's not something that's prepackaged; we've had to do it ourselves.

I have been using this solution for five years.

I have no issues with stability. UiPath improves how the infrastructure works and how stable everything is. I haven't had many problems. There are a couple of quirks that different product levels will address or resolve, but it's documented pretty well on the support side.

Scalability is pretty good. We did scale. Our initial rollout was 65 machines within Orchestrator, and we have since gone to 360 with one Orchestrator and one tenant. It's pretty good—I don't have any complaints about the scalability.

When I need support, I need them to respond. I actually had an instance last week where Orchestrator was not performing well. There were a lot of locks on the database, and it was bringing the Orchestrator trigger down. 

I opened a ticket and marked the criticality level as high. There's only one above that, and I didn't get a response back for a few hours. 

I had to go back to my sales personnel and explain to them that it was unacceptable. There was a problem with support.

In that particular instance, it was pretty poor, but I hope they saw that it was a problem and are working to address it.

Negative

We used Microsoft Power Automate very briefly because it's just part of our Office 365 package. We've used it very sparingly. It was more of a means to an end than a plan. 

We're actually looking to use it with a UiPath automation that we've created because it's Microsoft-centric, and it'll work quicker and do what we need it to do without having to invest a lot of time in the development. It might just be a subset of what we do.

We're currently on-prem, but we're looking to change that. We're up for renewal in January and are already discussing that shift over to the cloud. We can utilize AI better if we shift to the cloud. 

I manage the infrastructure and the deployment of all the processes. I have a pretty solid background in infrastructure, so it seemed pretty straightforward.

We have a lot of departments within our organization that can do the implementations. But personally, I'd rather just do it myself and make sure it works.

We have an admin team that makes sure that the ROI is there before we even start.

The pricing is competitive. I like the solution's pricing structure. However, the development tools can have a better discount because we'd like to have more developers be able to do the work. 

In the long term, running the product and running the automation unattended, I completely understand the pricing structure there, but on the Studio side of it, UiPath can come down a little bit on the pricing.

The product is leading the way toward AI, and there's some onus to make sure that we stay current with what UiPath is doing. It's the other way around too, where they need to understand where we are and help support us and our program. It's a two-way street. They need to make sure we understand where they're going, and they need to understand where we are. 

Overall, I would rate the solution a seven out of ten. 

I would recommend making sure your process discovery is done correctly because no matter how many automations you can put in place if you don't have a good understanding of your processes, it's not going to do anybody any good. 

Process discovery and getting buy-in from management are key.

Our primary use case is more of a reactive ad hoc use case to solve business problems on the fly. We can build automations to update thousands of records. 

We're putting a little bit more money and resources into it, and we're starting to go down more of the unattended automation path to actually do more end-to-end processes. 

The use of AI has freed up time and resources for other tasks in our company. We are a little bit more of an ad hoc approach right now. I just finished up a new cross-set of processes about two weeks ago that allowed us to onboard a client. I wouldn't have been able to without this automation. It would have taken a couple of months of several people's time to get them to get all this work done in the back end. 

It is helping. It provides value where we wouldn't be able to do certain things without it.

The broad functionality is the most valuable feature because it can interact with many different factors, and there are several ways to solve a problem. 

There's not just one cookie-cutter way to achieve what you need to achieve. You can get there in various different ways. That's a key aspect for me.

From the UiPath product perspective, this might be a problem because we're on-prem, but they add new functionalities pretty rapidly. It feels like there are releases constantly, and I don't want to update it too often. 

I feel like I'm behind even though I might not be. Sometimes, we'll go a year without doing any major upgrade to Studio or Orchestrate or anything. 

That's more of a personal problem, but that's because there are frequent updates to understand.

We started using UiPath about three years ago. We're a small company, an 80-employee bank, in Denver, Colorado. 

We're smaller than a typical RPA client. Our development is probably underutilized compared to larger institutions. Still, we thought it was important to get in the game early and start establishing the foundation of an RPA environment.

The stability is good. We have run into some issues that they believe are more related to their environment than to the application itself.

We're in the process right now of scaling. It is a scalable solution.

The customer service and support have been amazing. It is honestly the best product support. 

I have no complaints about the support. I don't even get worried when I have a situation. I might need to open a case. I like partnering with them. It's a good experience.

The initial setup was difficult because I didn't have a lot of past experience setting up a new program. This was a whole new program for us. Not only was it installing things, but it was also wrapping your head around how to set up properly so that we can get out of this.

It was a little challenging, especially with the on-prem solution and working in Citrix, to make sure these different servers were talking to each other properly, but overall, it was not too bad.

We're on-prem right now, so we're not even in the automation cloud. We're looking into that in probably the next year. The UiPath platform has been great for getting to understand those products a little better.

I see a return on investment. Even with underdeveloped automation, we definitely have a good ROI. 

If people don't understand the benefits, they might think it's a bit pricey, but for me, it's very cost-effective.

We looked at Automation Anywhere and Blue Prism. It was three years ago.

I work in banking. We are highly regulated in our server infrastructure, so we decided to do a VDI environment that works in Citrix. 

At the time, UiPath seemed like the best product to work with Citrix which was a large reason why we chose UiPath. 

We wanted to make sure we were getting something that was going to play nicely with our environment. It has proven to be true to this day. 

We feel like we chose the right vendor.

Overall, I want to give it a ten out of ten. I have to give it an honest nine just because I haven't used other RPA solutions. But I love UiPath.

If you're going to go in, go all in. We didn't go all in at the beginning, and we should have. We're playing a little bit of catch-up because of that. My advice would be to go all in and be organized with your approach.