UiPath Platform Reviews

We have very restricted usage, primarily around integration situations where we don't have any APIs. We primarily want to do just unattended automation. We discourage attended automation at this time. We have ten to twenty processes happening right now.

The improvements we've seen are primarily around the time and cost savings that surround someone sitting and manually syncing data between SaaS platforms. Although we use the latest and greatest SaaS platforms, they still don't have to interact with each other. There are no APIs in most cases. In those situations, rather than having someone manually sit and do it or have the product vendor customize it, we use UiPath.

For example, a couple of automations save us at least a year's worth of manual effort. Day in and day out, there is a SaaS platform that creates new data, and that needs to go through the different SaaS platforms. And that's the major statement we have. Then there are a few legacy applications we have that are near end of life. We don't intend to bring new APIs to them. Instead, we use UiPath.

I personally use the Academy often, and I have encouraged a couple of .NET developers within the organization to take up the certification. We have system integrators and local offshore vendors. They don't have certification right now. However, I am encouraging them to get certified. They're using UiPath Academy.

For me, the biggest win for the Academy was around the infrastructure and the sales switch around it. In my role, I'm required to go and talk to business functions and technology leaders. I have to tell them what the product can do, how it is deployed, etc., at the level of ownership. Plus, thought leadership needs to come from me, and those academic courses help me a lot.

The user community is definitely robust. I see lots of contributions, and people are willing to come and respond to any posted queries. 

The key reason we are not able to adopt it fully compared to other customers is the security model. Usually, what happens is whenever we talk to a business stakeholder, the first concern is data security. The moment that you talk about a bot in an unattended fashion going and reading the data source, concerns arise since there's not much control at a certain point.

Security remains a concern. We have completed all our security assessments. However, that continues to be a key question. There are use cases that are based out of Europe. If we have an instance in North America, again, the question of GDPR and all those questions arise. For example, does that mean that we have to have multiple tenants in different geographies? We are still trying to solve those kinds of questions.

There are situations in the community where, due to the fact that the product is so rapidly evolving, lots of the content out there is outdated. It leads to that lost effort when you try to do what they're saying, and it doesn't work due to it being a different version. That's probably one problem that I have noticed so far.

I've used the solution for a little over three years.

The stability of the product is very good. 

If you look at the key components and the visuals, I mean the Studio, the Bot, and the Orchestrator, the Bot and the Studio are within our environment. We haven't experienced any issues. What is left is the Orchestrator, and we haven't seen any outages so far.

I don't have any concerns with scaling.

I haven't created too many support requests. That said, the most recent one did not go well. The engineer had some trouble understanding, and the issue is still ongoing.

It wouldn't be fair for me to judge their support just based on those one or two tickets I worked on. I'm sure they have a good team. It was just that one ticket did not work out.

This was our first RPA tool. 

I was involved in the development and deployment. 

The virtual machine setup and the Robot and Orchestrator connection definitely were a little challenging. However, in the current version of the application, Orchestrator, it's far more seamless. Three years ago, it definitely was not that straightforward. Everything has gotten easier. 

The first automation took between three to six months, from initial procurement and development to deployment.

I did the deployment myself. 

In terms of ROI, we are getting there. It's not like as good as I anticipated. That said, we are getting there.

The pricing is fairly decent. It was not crazy expensive. Their cloud deployment gives you that sweet spot in pricing. You don't have to spend $20,000 for the Orchestrator, for example.

We assessed all the market leaders and did a couple of proofs of concept. It turned out that UiPath checked all the boxes from a capability standpoint and user-friendly developer experience, plus the deployment experience. UiPath was a clear leader.

We do not use UiPath AI functionality in our automation program. At this time, it is limited to OCR capabilities.

We currently are unable to automate more complex or involved processes. It is still in the conceptualization phase. We haven't put it into production yet. However, we are exploring their invoice management capabilities and more.

We have yet to develop some sort of social responsibility initiative using UiPath. However, we might in the future. 

I would invite potential users to look at the library of activities that are there. Make sure that the kind of use cases that they're looking at are present, and the level of security that they are looking for in terms of data. If you have less intensive security challenges, it's a no-brainer to use UiPath in the cloud. However, it might get a little tricky if it turns out to be healthcare or anything of that sort. You'll have to work with your data protection team.

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

Our company uses the solution for financing, accounting, and commercial operations. Right now, we are automating the lowest-hanging fruit. We look at people or personal productivity and automate their desktop tasks. 

We currently do not use AI functionality. 

The solution saves our company 10,000 hours annually. Automations have removed menial tasks from people's desks so there is instant gratification.

Studio and StudioX are really powerful tools. From the development side, business users have realized much success and have made great strides with StudioX because it is easy to use.

Automations are really easy to build with a minimal technical background. For example, my background is in accounting and finance but I am the manager of an automation team so that speaks to how easy it is to learn and develop. 

It would be useful to have co-authoring because we have many staff members working on the same project. 

I have been using the solution for four years. 

The solution is fairly stable. We have to perform maintenance on things we are doing and see some infrastructure issues for on-premises users. Many of these issues would be addressed if we switched to the cloud so that is under consideration.

I can see the solution's scalability. I think you need the right organizational buy-in for scaling but there isn't anything that the solution should be doing differently. 

The community is great and we learn so much there. We would like the community to bring back in-person user groups because we found a lot of value in knowing and connecting with other customers in our area. But, the community as a whole is awesome and invaluable. 

When we started our journey with the solution, we utilized the Academy for training. Since then, we have used the Academy to train three new team members because it quickly gets them up to speed so they can start developing. 

Technical support is good and we utilize it a lot. Sometimes it takes a little while to hear back from support. Though we understand, it also causes us heartache when tickets are automatically closed without a response. For example, sometimes we contact support on a Friday and the ticket closes on a Sunday which does not give us time to review our email and can be difficult. Otherwise, we like the technical support provided and rate it seven out of ten. 

Neutral

Our company did not previously use another solution. 

I was not involved in the initial setup. 

The price is high in comparison to Power Platform that Microsoft provides as part of its enterprise license. 

The pricing can be a bit confusing because many new products have been added. We just renewed our licenses and got all new SKUs because products have changed so much since our initial implementation.

I was not on the evaluation team but I do not believe other options were evaluated. The solution was chosen because it was a known leader in the industry.

The solution is great, works well, and is learnable. Users will be able to pick it up easily. People who are interested in change will find a way to make it happen, so you might as well give them a good tool.

There is nothing comparable in the industry that provides the same ease of use, great community, and good products.

I rate the solution an eight out of ten. 

We have a lot of use cases. A lot of them are based on SAP transactions. From SAP to SAP, or SAP to local documents, or local documents to transfer information to SAP.

The main benefit is to save manpower in-house. The second benefit for me is avoiding printing on paper. That is the second KPI that I am working to reduce in the company, reducing paper usage. In one project, for example, we managed to save more than 1,000 pieces of paper daily.

The UiPath Studio has been very necessary for us. 

Orchestrator is a vital feature. We have a sizable infrastructure, so it is necessary to have Orchestrator deploy all of the robots in all of our servers. It is not possible to work only with one computer. Therefore, that is an essential feature for me.

We've been able to save on man hours. We save around 60 manhours daily per department. For example, the maintenance department works with many people, and we can save on labor.

All departments use automation; however, mainly the logistics department benefits. The finance department comes in second, and after that, production. We've created more than 40 automation so far. We use both attended and unattended robots. 

Even if you are just on a laptop, you can have UiPath. 

I've used the UiPath Academy. It's necessary to have credentials for the infrastructure. It helps us understand the features of UiPath properly.

I use the UiPath community a lot. When I have a job, I can write a question about it and get a response from an expert. It's quite a valuable service. With the community, we can reduce the time to resolve issues. We can learn from other people who have faced similar challenges. 

Setting up automation can be easy or complex, depending on the project. 

All documentation and transaction areas can always be improved. 

We'd like to see mobile robots in the future. We have a lot of cell phone tasks, and it would be ideal to replicate automation from the iPhone, for example. If you were at a certain location, you maybe could set up an automation that could send a message or open a cart. 

I've been using UiPath for four years. My company has worked with the solution for longer. 

The solution has been 95% stable. 

It's a very good tool, and it's easy to expand in terms of infrastructure. If we need more space or more servers, it's easy to just deploy more. 

I have no experience with direct UiPath support, however, getting help from the community has been great.

I did previously use Auto ITX. It's a library from C# Program. It was only local. I don't know if was a standardization. I'm not sure why the company ultimately decided to begin using UiPath. This product is easy. It's drag-and-drop and very simple to use. 

I have developed automation and uploaded Orchestrator. That's it. I didn't handle the initial implementation. 

I'm a developer and therefore do not handle the licensing aspects of the product.

We're UiPath customers. 

I'm not sure which version we are using. I know it is not the last one. 

I do not use the AI functionality just yet. That's new to me and very interesting. 

While I would recommend the solution to others, it is necessary to have a good developer who understands the tool's value. Technical knowledge is necessary.

I'd rate the solution ten out of ten.

We use it to transfer information from one system to a government system.

We also use UiPath to automate processes that track mileage on vehicles, which would then allow us to calculate some of the GHG emissions.

It has really helped us become more efficient. UiPath has made the lives of our data operators a lot easier because they would normally have had to manually enter all this information or transfer data.

AI Computer Vision has been great because it works through VMware. It's able to see the elements through the VMware window on the government system that we interact with.

UiPath's user community is great. I get a lot of answers and am able to talk to folks who know the products and can provide support directly.

The UiPath Academy courses are an easy way to learn how to use Studio.

The licensing has been a challenge in terms of what is included with our current license. They've changed it a bit.

The learning curve to get UiPath up and running is hard, although we're pretty comfortable with it now.

Promoting its use is the hardest part for us. It's tough to get people to believe in using the assistant or Studio without fearing the loss of their jobs.

I've been using UiPath for about five years.

It's very stable, and we've never had an issue with it.

UiPath is easy to scale. If we want to share the bot or the scripts, it is easy to do so with other team members. It is also easy to add licensing and grow the current bot or create a new one.

Our experience with UiPath's technical support has been really good. We get great responses to tickets when we need help. On a scale from one to ten, I would give technical support a ten.

Positive

The initial setup was pretty straightforward. We learned Studio, started with a simple script or bot, and grew from there. Our implementation strategy was to look at our highest demand for transferring data and make the bot do that.

Our ROI is that instead of having a team of seven people to manually do the data transfer, we now have two people.

The pricing is fair.

We looked at Blue Prism and went with UiPath because of its ease of use, the Magic Quadrant rating, and the price.

It's great software and has helped us a lot. It gives us a competitive edge.

Overall, I'd rate UiPath at nine out of ten and would advise you to go for it.

We started using it to automate manual processes from other departments. We service other departments, to begin with, including the media between the business and the IT departments. 

We started automating very repetitive manual tasks that the business side typically had. For example, if they had to open an application early in the morning to try to process transactions. Then, late in the afternoon, they would have to do the same thing as well. Now we have a robot that does that in the morning and the afternoon, which saves a lot of overtime since it has to be done at six or seven at night, and previously sometimes people would be forced to stay. Therefore, this way, we save that time and overtime. 

Another example would be we use it to download ATM transactions from a webpage. The robot downloads those transactions and then uploads them into our data warehouse, which reports for them. Normally, we don't have that information there.

Another use case would be in a department that would print a bunch of wires late in the afternoon. The department would print them out physically and store them somewhere where they review everything later. Now, with UiPath, we scan the transactions from the Fed, and we just print in PDF and send it to them via email, and it saves a lot of time.

The solution has saved us not just in automating but also in updates. For example, all these service charge codes for these particular lists of credit card accounts. We let the bot run. It ran for a really long time. I can only imagine how much longer it would've taken with humans.

I'm not sure of the exact cost savings. We just started asking about time savers. Some customers have told us it saves about 45 minutes a day. There's another process that only runs once a month. To put it in general terms, it reviews all of our credit card accounts and itemizes them, and makes them into a lot of reports. That saves about eight hours a month. Also, when it comes to helping us avoid overtime, there are 15 minutes of actions to be done, yet we are saving an hour or two of pay every time. 

The ease of automation is great.

The unintended robots are very useful. Just letting it run and having visibility, and controlling how everything works is definitely helpful. Sometimes they want it to run a certain way. Sometimes they'll tell us, "Oh can we tweak it a certain way?" And they do that more often than would I thought they would. It's simple to handle.

I really like the user community. When I go online to search for help or anything else, it's very valuable. Everyone's so helpful online. Whenever I'm stuck, and I'm basically self-taught when it comes to UiPath, I turn to the community. I've learned everything through the community. It is easy to learn.

While we haven't really taken any UiPath Academy classes, we were basically given the platform and just told to learn it ourselves. I did start doing the academy courses however, right off the bat, we had to develop already. I kind of had to do both at the same time, and that's where the online community comes in handy. The courses definitely taught me the basics, at least. And they helped me expand on that.

While UiPath works super well with other applications and browsers and app pages that we use in the RedLINK wires, when it comes to experience, sometimes it doesn't detect what it's supposed to be doing as easily. I have to do a workaround and so sometimes it can be tedious.

We've been using it for about two years.

We've never had an issue with performance stability.

We currently have 20 to 30 processes, and less than ten are via developers. We initially hired developers to help, and then they left, and now we are working on it ourselves. 

I see the potential of its scalability. We're still at a very small scale with it. 

I've used technical support once. They helped me. When the developers set up UiPath for us, it ended up being kind of faulty. What we really needed was the enterprise edition, and some other settings weren't configured for our purposes. I contacted them for help, and we had a Zoom call. They were very friendly. They helped me set it up correctly in the way we needed it. While there were some communication issues, they helped us in the end. 

Positive

We did not previously use a different solution.

I was not directly involved in the initial setup. However, the setup was not exactly right, and I contacted support for help. It seemed pretty straightforward in the end.

We had third-party developers from Peru that helped us to install it and then they just left. We were just given the platform, and we had to teach ourselves how to use it.

We have witnessed an ROI. The company has mentioned the hours saved, and I'm not sure about the money saved.

We did not evaluate other options. 

While we could use UiPath for good causes, like sustainability or the environment, we do not use it in that capacity yet.

We do not use the AI functionality just yet.

I'd advise other potential users to get a partner. We didn't have one. That's what we're doing right now. We're shopping for a partner so we can learn as we develop. Again, we were self-taught and it would've been much easier to dive in with a partner.

I would rate it ten out of ten as it does have massive potential. 

Our company uses the solution to automate formula-driven processes that are completed on a frequent basis. 

We create unattended bots to handle tasks for our finance, procurement, IT, and HR departments.  

At this time we do not use AI or ML.

UiPath has been instrumental to our success because we have an excellent relationship with our account executive and a lot of support from the leadership team. 

We have met with their C-Suites for one-on-one conversations and like that type of ownership. We appreciate their commitment and dedication to our success. 

The solution requires little or no code and can be operated with minimal technical skills. This lessens our dependency on third-party providers and allows use by citizen developers. 

AI and ML need further improvements to reach mature status. 

I have been using the solution for eight years. 

The solution is very, very stable with no issues when we deploy bots. 

The solution is very easy to scale. 

Technical support is stellar and available 24/7. There are no limitations on when support is available, including in the middle of the night. No organization is perfect and there is always room for improvement, support is rated a nine out of ten. 

The community forum is invaluable and very helpful for troubleshooting. For example, we sought support from different forums to learn how to use our in-house desk for L1 support.

Academy courses are used to upskill our team and keep up with the fast pace of new capabilities. The solution is always transforming and acquiring new technologies. 

Positive

I previously used Blue Prism, Pega, and Automation Anywhere. 

The initial setup is very straightforward and easy to use. 

Our team of developers and BAs are able to navigate the solution without requiring any handholding from the solution's SMEs.  

Our in-house team deploys the easier automations.

We work with multinational partners for more complex deployments. Our team is knowledgeable and has the same competencies as MNCs so that enhances the partnership. 

The solution has improved workforce efficiencies by 120% and reduced errors by more than 90%.

We saved several million dollars within three weeks of deploying the solution.

I love the flexibility because ownership is willing to work with us to make sure commercials are viable. They are committed to being our strategic partner and are reasonable in terms of our current appetite. 

Our company solely uses the solution. We find it to be more user friendly than other options. 

Most products are similar, so it comes down to commercials and that makes the solution much more cost effective than other options. 

You should consider using the solution because there is a reason why it is the market-leading RPA provider globally.

I rate the solution a nine out of ten. 

Our company uses the solution for documentation understanding, email automation, and onboarding. Many of our use cases include AbbVie. 

Our company has saved thousands of hours by automating accounting processes. Staff no longer have to drudge through manual tasks and that is meaningful to them so they do better work. 

The solution provides ease of access for users with limited knowledge. One of our high-level developers can code it for a user who can maintain it with limited coding knowledge. The solution is much easier to use than having an actual coded application. 

For example, a developer can build out a use case that involves emailing invoices and includes labels and documentation. The product can then be handed off to a user who does not have coding knowledge because all needed information is included for maintenance and administration. 

There is a bit of a learning curve to the solution because it is like coding. If you are a coder it will be easy but you cannot dive very deep into the code. The way you go about the architecting process is very different from other tools because you have to lay out the flow in a certain way. 

Reusability is not as great as straight coding where you can recall functions and methods. The solution requires a whole workflow that can become a bit tedious when processes expand too much. 

Features I have wanted such as enhanced process mining and others have been shown in the new preview so are already forthcoming. 

I have been using the solution for four years. 

The stability is pretty good and the solution has not shut down. I have experienced a few crashes, but they are probably caused by my own computer.

The scalability depends on how you develop it. If you develop it to be scalable, then it will be scalable. In terms of Orchestrator, the platform is pretty good at scaling because it allows you to keep deploying it and branching out. 

The Community is great and operates similarly to Stack Overflow's community. Users have their own niche knowledge and you can query them if you ever need anything. This is a good way to expand your own knowledge base. 

I took the Academy's courses when I first started using the solution so haven't learned the new features yet. Over normal coursework, you learn best practices that enable you to pick up the tool faster, such as how to document process flow or how to set up from a high-level perspective. 

I have not needed technical support. 

I have not used other solutions. 

The setup is pretty easy and straightforward. 

We implemented the solution in-house. 

We always hope to see ROI in every process. We have realized a bunch of ROI on deployed items and hopefully will see more. 

For our provisioning process, we save a few hours per person each day. 

Our company did not evaluate other options. 

I advise others to try out the solution. It is really good software and has helped a bunch of people to switch careers. For example, I used to be an actual developer but now I do RPA. The solution is an industry leader so it is a good idea to try it out at least once.

I rate the solution an eight out of ten. 

Our company uses the solution to understand documents, process invoices, move data from one system to another, conduct background investigations, and other day-to-day use cases for federal and state offices. 

For one use case, we built a sandbox for malware analysis using the bot. 

For another use case, we scan thousands of resumes to find an individual with a specific skill set. 

We have completed 90 automations with mostly attended bots that we have built. We are not using AI much right now, but plan to use it to solve problems in the future. 

The solution can be used across systems or with more generic use cases. 

It is easy to go to the code level and write automations that only require a couple of lines of code.

Training materials should include behind-the-scenes information such as what goes on underneath the infrastructure and how components interact with each other. This type of information matters more to solution architects than high-level buildings or components. 

The solution has a few bugs that need to be worked out. 

I have been using the solution for three years. 

The stability has been good so far but we do not have much volume. We handle diverse implementations that include five to ten bots. We do not yet have the load to fully rate performance. 

The solution is a good platform for scalability and accommodates multiple nodes. 

Technical support has been pretty good and we have a direct contact who is very responsive. It sometimes takes a day or two to make contact, so technical support is rated a nine out of ten because there is room for improvement. 

The user community is helpful and it is easy to find answers or at least a direction for solving issues. 

Our team utilizes the Academy for certifications and finds it useful because it provides high-level information about features. 

Positive

We did not use another solution. 

The setup is cumbersome for on-premises because documentation is outdated or instructions are not clear so we have to get clarity from support. 

The setup for SaaS is easy because you can log in and start using it immediately. 

We implement the solution in-house using a hybrid model. Some federal government offices are very particular about exposed data so we use on-premises for them. Others are more open so we prefer to use the SaaS platform. 

We also work with many business groups to promote RPA and set up their infrastructure environments in the solution. 

The solution's ROI is that it saves time, eliminates errors, and reduces repetition. Tasks that used to take days are now completed within seconds or hours. 

The solution is more expensive than Power Platform which offers many connectors to third parties. 

For example, an unattended bot costs $50 per month on Power Platform so it makes sense for developers who work on the Microsoft Platform. 

The solution can run $10,000 per year. 

Prior to using the solution, we looked at Automation Anywhere but did not enjoy developing with it.

Many other products such as ServiceNow, Pega, or SAP have RPA but use their own domains. They also require many blocks of code to automate. 

We will be looking at Power Platform's next iteration because we are not sure about the future of the solution's partnership with Microsoft. 

When implementing the solution, go small first. Do not jump directly to the most complex case for automation or you will get lost and think the solution is ineffective. 

Start by building small workflows, realizing the gains, and slowly increasing performance. 

I rate the solution an eight out of ten.