UiPath Reviews

We're using UiPath for healthcare use cases. It is primarily used for automating document-related tasks, such as moving documents around, classifying them, and extracting the information we need. 

UiPath has increased our accuracy to 99.99 percent and expanded our ability to process large volumes of data, making data processing more affordable and improving our profitability. It has helped reduce personnel time and enhanced productivity because we can run the bots 24 hours daily.

We can automatically scan documents and send the information through Twilio. Document scanning is tricky, but we can easily collect the data after finishing the process. The integration is smooth. 

The solution helps us share data between systems, which speeds things up. Previously, we were doing everything manually. Now, we can automate data tasks in Informatics with UiPath. 

UiPath enables us to pull patient information into a single dashboard with the help of a Power BI integration service. Power BI is our dashboard solution, and we integrate it via API. It's much easier to monitor the patients because we can see how many records were successfully processed and prepared. It's secure enough to comply with HIPAA because we can collect patient data and encrypt it. Automated scheduling helps the healthcare staff, particularly the doctors. 

I like the ability to extract emails and other data from scanned documents. The machine learning and AI features are helpful because we're processing tons of documents and warehousing the data. UiPath's Document Understanding makes that much easier. 

Document processing could be improved. It's challenging to build document automations. It would be helpful if UiPath provided some templates and prebuilt models. Citrix automation could be improved. It's static automation, and we cannot fully automate processes involving Citrix. Some elements aren't supported. 

I have used UiPath for around four years.

UiPath is generally stable, but the stability goes down when we do Citrix automation.

UiPath is scalable enough. We are using more than 20 licenses. 

I rate UiPath support 10 out of 10. I'm satisfied. When we raise a ticket, we get a response in a day or two. 

Positive

UiPath Studio is available in community and enterprise versions, but the UI doesn't work correctly in the community edition, so it's difficult to achieve 100 percent automation. I'm not responsible for the licensing, so I don't know how much it costs. 

I rate UiPath 10 out of 10. I recommend UiPath because it's better than other automation tools like Blue Prism. It's easy to use and has a large user community that you can rely on for support.

My use cases are mostly in finance, including settlements and reconciliation processes.

UiPath has greatly improved the work we do for our clients. Because I work in consulting, it's crucial to see a reduction in the turnaround time for some of the high-end processes that we've worked on. We have taken down the time required for some processes from four hours to about 10 minutes. It's very important because of the time savings and the cost savings as well.

It also speeds up digital transformation and reduces the costs of that process. You might think you have to bring in a new system, but you don't actually change the system when UiPath is implemented. That reduces the costs of digital transformation.

Another benefit of UiPath is that it reduces human error significantly. In my experience, I would estimate the reduction at 40 percent. It has also freed up employee time and resulted in cost reductions.

The most valuable parts for me are the UiPath Studio platform and the Activities that it provides for automation. The platform is quite friendly and it's very easy to build automations. It's mostly drag-and-drop.

I can also implement end-to-end automation and that means that business owners can hand off these processes and focus on more high-value work. That gives them back hours as well. So it's very important that UiPath can complete automation processes from end to end.

Another advantage is that the user community is top-notch. One of the reasons I recommend UiPath is the knowledge you can get from the forums. And there are constant events that the community hosts around the world. You can be in the Lagos community, where I am from, and learn there, and you can also be in another community and learn things from them as well. It's really helpful.

And in terms of UiPath Academy courses, almost everyone I know has learned from the UiPath Academy. It's a great initiative from UiPath. It's accessible and has detailed content. It's great. You don't need to go anywhere else for training, it's all available in the Academy, and it's free, which makes it a no-brainer.

They can improve integration with other types of systems by giving us more connectors. That would mean UiPath would work natively with more applications. With that done, they will have built a fantastic solution.

I have been working with UiPath for three years.

It is very stable. I am coming from Blue Prism where the software crashes from time to time.

It's very scalable and can handle quite a lot of workload.

Technical support is quite friendly and prompt.

Positive

I've used Blue Prism as well. It was the first RPA software I worked with.

Most of our deployments are on-premises. Our deployment was straightforward. We had a guy who helped us implement and deploy it. It's a Windows Server deployment and it's deployed in multiple locations.

There isn't really any maintenance involved.

The pricing is reasonable.

UiPath is a great fit for enterprise-grade companies. It's user-friendly and speeds up the time to delivery.

We use it mostly for our sales and for our clients, with relatively simple, stand-alone robotic solutions. Some are attended and some are unattended. We use it for reporting in our finance and HR departments. 

We have automated processes for our clients that, before, took somebody three days to do, and now they're done in minutes. That says everything. It's extremely useful for saving time and avoiding mistakes. Those are the two main efficiency factors that we have seen with our clients. Repetitive projects, where someone has to copy a lot of data from one place to another and then work with the data, are very prone to mistakes. We can completely eliminate mistakes and save people a lot of time so that they can do more interesting tasks. We have developed programs that reduce human error by 100 percent. There are no errors, once they are automated.

And it absolutely accelerates the process of digital transformation. There is no doubt that it is getting faster and faster. We are thinking about combining RPA solutions from UiPath with ChatGPT or whatever else comes along, to see if we can make them work together. This will be the future.

It enables us to implement end-to-end automation. We have projects where it automates the entire process from one end to the other. Very often we have "human-in-the-loop" within them, because some decisions have to be made, but they are almost end-to-end solutions.

End-to-end automation is extremely important. Usually, when we start with a new client, we start with a smaller process as a type of proof of concept, so that they can see what is possible. Then, we extend it up and down until we have an end-to-end solution. We have seen that it's better to develop a process step-by-step, and not try to do everything at once. But in the end, we have an end-to-end solution.

The UiPath community is used by our developers. They ask questions and receive responses. They are definitely active there.

We have had issues with Ingram Micro. It happened that we ordered licenses and we received something else. It takes a relatively long time, two and sometimes even three weeks, after the order until we receive licenses, and clients are sometimes a little bit impatient. This is something that should be accelerated.

I have been using UiPath for almost four years.

UiPath is a stable solution. One of the reasons we left the Foxtrot solution was that it was unstable. If we had the same process running 10 times, we could get three different results. But with UiPath, we have never had any issues regarding stability.

It's scalable.

We have discussions sometimes with people from UiPath about solutions and things that we have done already. That is working quite well. The support is very good.

We participate quite frequently in UiPath webinars, especially when they are presenting new versions or components or pricing models for the software, so that we keep everybody up to date on the latest developments. They develop things very quickly. It's difficult to keep up with the speed at which they are developing new solutions.

Positive

It is very straightforward to implement. The setting up of a license is something that is done within an hour. It's the development that takes more time. Most of our clients are large, multinational companies.

UiPath itself does not require any maintenance, but solution maintenance is required if something changes for one of our clients.

Everybody is afraid of the licensing fees in the beginning, and because we are in Romania where salaries are still significantly lower than in Western Europe, that means that licensing fees have a bigger impact on costs for the company. But we are also working more and more for companies outside of Romania, where that is less of an issue.

When we come up with an offer in which the licensing fees are getting a little bigger, clients are more reluctant. That is another reason that we prefer to start with something a bit smaller until they get acquainted with the solution and see the advantages.

We looked at other solutions. We started with something called Foxtrot RPA, which didn't work well at all. We also compared UiPath with Automation Anywhere. But UiPath offers a better variety of possibilities, it's more flexible, and it's very easy to program if you are a developer and know other programming languages. UiPath offers StudioX for people who do not have any experience with development, but it's still a little too complicated.

We are not using a lot of the abilities that UiPath offers. We have made some attempts to use Document Understanding and we would very much like to do project mining, but we haven't had a client that is interested in that yet.

I would recommend that you start by implementing a small, standalone process, something that is not part of a big process. Automate that small process first to get used to how it works and see what can be done with RPA in general. And only then start with more complex processes. The latter take more time to develop, and clients don't like to wait.

We use UiPath to automate the processing of large volumes of data. The company has multiple sites, but the organization's data warehouse is at one location. Around 80 people use the solution. 

UiPath enabled the company to reduce staff. We can now perform more work with fewer people. We decreased our manual work by around 60 to 70 percent. UiPath freed up personnel to do other tasks. We still have people doing about 30 percent of the data work, but we hope to increase that to 100 percent. We've cut costs by about 40 to 50 percent.  

We are launching new products using existing UiPath workflows built for our older core projects. When we get new requirements from the client, we can easily implement them. UiPath has expanded our capacity to take on new clients. 

The most valuable aspect of UiPath is that it doesn't require much coding. We can do most of what we need using the basic functionality. We can implement the code with drag and drop and basic modular programming.

The user interface could be better. There have been advancements in UI design and user experience in recent years. UiPath could do a better job of keeping up with these trends.

I have used UiPath for about five or six months.

UiPath is stable.

UiPath is scalable because we can reuse our workflows. 

I rate UiPath support an eight out of ten.

Positive

We used Microsoft Power Automate for one or two months. UiPath has more capabilities, and we can do more with it. 

Setting up UiPath is straightforward and requires some maintenance. The deployment team does that.

We're getting more clients using UiPath, so the price we pay isn't an issue. 

I rate UiPath a nine out of ten. I would recommend it to my clients and colleagues. It doesn't require much coding knowledge to use. It's also much cheaper than paying human employees to do the same work, and bots are less prone to errors. 

We primarily use UiPath for automation processes. One of the major use cases is the approval system that we have. Our system goes through a lot of approval and workflow steps, and we have automated the entire process using UiPath.

We are using UiPath for most of the automation processes. We have reduced a lot of resources that we previously had, and it has improved the efficiency of the operating model that we have. Earlier, if it took around a week, we are now able to achieve the same process within three days or so. It has basically cut the time in half.

It helps us to achieve end-to-end automation. If something involves manual intervention, it's always prone to human error. End-to-end automation completely removes all human errors and also saves a lot of time and manpower for a specific process or task. So, overall, we improve the efficiency of the processes that we implement.

It has reduced the time taken to develop something, as well as the error rate. Earlier, we used to have a lot of human errors because there was a manual intervention, but now, there are no errors, and everything operates smoothly.

We automated the complete approval workflow system. Every operation has a different set of child operations that occurs as a change reaction. UiPath helped a lot in implementing this in a completely automated way. With the flow chart wizard available within UiPath, we are able to achieve this pretty easily with less effort. It gives us more results with less effort.

It definitely reduced the costs of digital transformation because we have cut down a lot of resources that we had earlier. We were able to cut down the cost by half. There is definitely a reduction in price. Doing digital transformation didn't require expensive or complex application upgrades or IT application support.

It has reduced human error a lot. Previously, with our approval workflow, at every step, a human had to come, approve the request, and perform a lot of manual steps after the approval. All those steps are now automated, and everything happens within the expected time period. There is totally no human error because it follows a set of rules, and it always knows what to do during an approval operation. There is a 40% reduction in the errors that we had.

It has definitely freed up a lot of employee time. It has saved us 12 hours per week. There are cost savings and time savings. It has reduced the human resources required as well as the time consumption. We are now able to invest our time in other areas, and let UiPath take care of the heavy lifting.

The Orchestrator and the Studio are the features that I personally enjoy using.

It's pretty easy to build automations. Earlier, we had to do a lot of manual work, but with the introduction of UiPath, everything became very easy. The drag-and-drop components have made our lives much easier. Even non-technical teams are able to build an automation workflow within hours.

Their user community has been very good. For any questions that I post, I get the answers pretty quickly. They're friendly as well.

UiPath can probably work on improving the AI features. We tried UiPath's AI functionality in our automation program. We did some research on that, but right now, nothing is in production. When we did some research, we weren't getting the expected results. We weren't completely satisfied with the results, so we put it aside. It could be a drawback on our side in terms of learning the tool.

In terms of additional features, UiPath already has a plethora of options. All our needs are fulfilled by the features that are currently available.

It has been 15 to 16 months.

So far, we haven't faced any downtime in terms of using UiPath. It has always been up. It also has a plan for exposing multiple endpoints so that if one goes down, we're able to use the other one. So, the stability has definitely been great, and we haven't seen any downtime until now.

We use it as an internal application. There are around 500 to 800 members who use the tool in terms of the automation process. It has been good for our use case.

We have deployed everything in the cloud, and we also have the ability to integrate it with other AWS services. For the environment basically, we have different stages. One is the beta stage and the other is the production stage. In the beta stage, we do internal testing, and once it's ready, we deploy to the production environment where it communicates with other services like AWS.

We don't have any plans to increase the usage of UiPath at this time. If we need to expose anything to public-facing customers, we might think about it.

Their technical support has been great. For any doubts we have, we reach out to them via email or via a personal contact for our organization. Whenever we need support, they are totally willing to help us out. I would rate their support a nine out of ten.

Positive

We had an in-house solution that we developed, but it was not scalable, and there was a lot of maintenance work that we had to do to make it work. So, we migrated to UiPath. That was the only solution that we worked on. We did the research, and we found out that UiPath is a leading tool in the industry for RPA, so we hopped onto it.

I was not involved in its setup. I was more involved in the development once it was set up.

We are using the UiPath's cloud version. We don't have any on-premise setup. If we had an on-premise setup, we would've had to maintain all the servers and make sure it's running all the time. Because we completely migrated to the cloud, the maintenance is not on us. UiPath takes care of that. It's definitely a big win for us because we migrated from the on-premise system to the cloud system.

It requires very minimal maintenance in comparison to the on-premise setup. In an on-premise setup, we have to maintain all the servers and make sure it's always running up, but with the cloud version, there is very less maintenance on our side. There is an IT team of around two to three people who maintain the systems.

We could see an ROI within a month. We were able to see the benefits of the automation processes within a month. There was a 25% increase after implementing UiPath. There is an increment on a year-by-year basis.

We are using its enterprise version. Its price seems okay, but I'm not sure because I'm not involved with the finance side. I'm more on the development side.

We didn't evaluate other options. We did some research, and we found UiPath to be a leader in the industry, and it also fitted our budget. So, we went for it and started using it.

I would definitely recommend it to others. Automation is going to be a part of everything in the future. So, every company should start adopting UiPath for any internal or external needs. Automation is the best way to go ahead.

We used to do the entire process manually, and we found a lot of errors. It was a time-consuming process on the whole. With the introduction of UiPath, we definitely saw the benefits of automation and a smooth process with fewer errors.

I would rate it a nine out of ten. It's one of the best RPA solutions out there. I'm reducing one point for the AI features. Apart from that, I find it great.

We automate the entire revenue and order to cash and then process it to payables. It is used for processes, from generating customer invoices to ensuring that all our vendors are getting paid timely. We also use it for data reporting, audit requirements, or whatever information gathering that the company may need.

We've automated about 30-ish processes, and that's just the tip of the iceberg of where it's going.

All of the processes are attended to right now. We're still getting the backend set up to move some of them to unattended.

The solution has improved the organization by providing time savings. That's one of the most fundamental things. We recently had a project that would take a human who's actually navigating through the screens and clicking all the buttons roughly a month's worth of work, if that was their primary focus all day long. We were able to get that completed within two days using UiPath. Therefore, the time savings are phenomenal. 

Also, when you're dealing with all that data, there's a lot less likelihood of human error and missteps. With the bot, we know for sure that the line is the line, and that's it. It's error-free for the most part.

The low to no-code is by far the most valuable feature. Developing a bot in under a minute that saves you an hour a day is phenomenal.

The user community is great. Looking at the forums, when a question is posted, the responses are fairly quick, either from UiPath or the community itself. In my past role, I posted to the community before, and I had been able to answer some questions as well. Then, it's nice to know people are having the same problems you're having and finding solutions.

I've taken UiPath Academy courses. I've taken mostly the developer ones, and then I'm looking into more of the admin side, with the Orchestrator and project management side of it. The biggest value is that it walks you through step by step and you're doing it alongside the course. It's hands-on learning. It's one thing to watch a video. It's a different thing actually to play with it and have something start working.

Overall the training and documentation could be better. There's just so much of it, so a streamlined way to get to the information I need would be ideal.

I've used the solution for about two years. 

It's very stable. Performance-wise and stability-wise, it's great. We're able to access it from anywhere. I have the Orchestrator app on my phone, so I can always keep track of the bots that we've developed and see how they're doing and everything.

Scalability is something we're still looking into. We just started, so we're still in the groundwork. However, in terms of being able to scale, the potential's there. We just need more time to play with it.

I've had one instance with them, and it was great. They knew their stuff, they walked me through everything.

Positive

Before UiPath, we used Nintex RPA, and then an SAP RPA tool as well. We used to UiPath to get more usability and scalability. The user-friendliness of the product and just the engine and the innovations that they're making behind it really placed them as a leader in the sector.

I was involved in the implementation since proposing the idea to start developing and starting a road show to be able to expand.

The process was straightforward. I had no qualms about it.

We started small. We essentially had two developer licenses, a couple unattended, and then a couple attended. We had already identified who would the attended bots go to, and did all that legwork in the forefront. Once we got the license enabled, we could activate it, work in the Orchestrator to assign the specific roles, and then have them start running. Within a week, we were able to get bots out the door and have people actually using them.

Everything has been done in-house. We've been building everything ourselves. 

We've definitely seen an ROI. For example, in one project, we were able to take a month's worth of human effort and completed it in two days with UiPath. We've had several others of a similar nature.

The pricing is a bit high compared to other products. That said, it does offer more. From working with other ones, it is definitely a more powerful tool and well worth the pricing.

We did evaluate other options. We had the ones we used before. We also looked at Blue Prism, Automation Anywhere, and a couple of others. 

The difference was a sense of familiarity. I had previous experience with UiPath. Mainly the innovations and the fact that since 2019 on the Magic Quadrant, they've been the leader consistently, and they will continue to be, were the reason we chose UiPath.

We do not use the AI functionality in our automation as of right now. It is something I'm interested in, however.

Our company will be involved in an environmental initiative using UiPath. We have an environmental group. As of right now, we haven't thought about taking it that far. We've only had it for about a month or two. It's something we're considering for the future. 

The most important part is going to be the user interface. The people who are developing it, the people who are using it, they're the ones who are going to have the most to say about it. Your business end-user has the most to say about it; if they don't like it, that's all you'll hear. By focusing on that user interface, which UiPath has done, you really get a solid project that people get excited about rather than leaving a bad taste in their mouths.

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

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. 

When I started at my company, they were building their RPA journey. I was the first person to help them do that. As no one in my company was aware of what RPA is, we needed to showcase and publicize what UiPath is and what RPA is.

I work for an insurance company and there are handwritten scripts that need to be scanned in, and this was the first use case that I had to work on. We used the OCR technology to scan handwritten documents and its capabilities are evolving day by day. When I initially started, it was not as robust as it is today. We had some challenges with the OCR technology, but today we are able to do it successfully with validations.

Right now, there are 24 automations of which 22 are in production and two are being built. These are all unattended bots. I also use this solution in a personal capacity to delete all the junk emails I receive as I usually get 20,000 junk emails a week. This saves me a lot of time. 

The UiPath's user community, in terms of the value that we gain by being part of it, is very helpful. If I'm stuck with coding, that is the place I go to get assistance. The ideas and the solutions that they provide are very helpful. There are a few people in the community who are very accurate and their solutions always work.

I have also made use of the academy. Currently, I'm taking the certification training and planning to get my certification done by the end of this year. It has taught me new ways of doing things including dynamic selectors. Previously, the bots used to break because of a selectors issue, but the dynamic selectors solved this. 

We have an internal process that is manual and takes three days. The first day involves pulling in the data, the second day involves validation and the third day involves delivering it to the relevant system. We automated this process using UiPath.

The errors have been minimized. Whenever something goes wrong, we immediately get an Outlook notification. This is when our business customers get to know that there's something wrong with the input data that they're getting. They can directly deal with the input information data team and get that information corrected and this usually happens within three hours. 

The OCR technology within this solution has been most valuable. We are able to scan handwritten documents and scrape their contents to be captured within the system. 

When I first started using this solution, the OCR technology was not that good, but it has since improved. Most of the handwritten documents are easily read by the OCR technology. 

I have been using this solution for three years. 

The stability does depend upon the applications we are using but overall the stability is good. 

This is definitely a scalable solution. 

The first time we had issues was during the setup and we haven't needed to contact the support team since then. Their support is really good and the solutions that they provided really worked from our side. They provided step-by-step instructions that really helped us a lot and saved a lot of time. Our initial estimate to get that UiPath deployment was two and a half weeks, but we finished that in three days. This was made possible by the support and the instructions received from the support team. 

I would rate the support for this solution an eight out of ten. 

Positive

I was the one who did the deployment. During the deployment, we had some challenges but received assistance from UiPath support. Even though we had some hiccups in the initial days, we were able to still overcome those with the help of UiPath support. The deployment took two to three days for an on-premises installation. 

Our business has been highly satisfied with the RPA solutions that we are providing thanks to UiPath.

The pricing for this solution is reasonable. 

We evaluated Blue Prism but felt UiPath is easier to use and offers better performance.

I would rate this solution an eight out of ten. I would rate it a ten out of ten if this solution worked better with our other applications. 

I would definitely advise others to consider UiPath because it is easy to learn how to use. A lot of documentation is available and accessible to facilitate learning including YouTube videos. 

When I was evaluating Blue Prism versus UiPath, the training materials were not the same for Blue Prism. Coding using UiPath is really easy and is mostly drag and drop.