We're a tech consulting company that works for insurance companies. We use UiPath for tasks related to payment processing, deductibles, and denial of coverage. We check each part of the process to ensure that the patient has met a set of criteria. We're checking the deductible to see if it has been met, and we update the notes on the platform. UiPath is useful for all of our clients regardless of the industry. For example, we have used it for payroll and payment processing at Citibank and Doshi Bank.

A bot can run 24/7, reducing the human labor required. That is UiPath's major advantage. It reduces the number of manual tasks while also improving and enhancing human labor. A manual task that took 10 minutes in the past can be completed in two or three. We are saving a lot of time.

Let's say we have eight people doing a particular task eight hours a day on a five-day work schedule. Once we automate that task, we can run the bot 24 hours a day Monday to Sunday. Automation reduces our costs and human error. The accuracy and data security are high. It's beneficial all around.

Uipath facilitates data sharing between systems. We have some shared folder packs that enable us to share the data from one system to another. This functionality can be important, depending on the project and type of data. We use some encrypted features. If we want to share data in encrypted mode, we can put it in an Orchestrator folder on-premises so only those with access can see the data.

The business will share the data, including employee and patient records. All the data is shared within the database. Either the employees can send data over, or they can access the data from that particular folder. UiPath offers a central portal for managing patient information. We've done a lot of things to extract and utilize patient information, ensuring that it can be accessed by the appropriate teams. We have to train our bots to capture the right information, like the patient's name, address, ID, location, etc.

UiPath is good for data scraping and extracting information from websites. UiPath is approachable, and it makes life much easier by automating repetitive tasks with the help of drag-and-drop flexibility, eliminating human interaction. The drag-and-drop APIs make it easy to get data from the API quickly.

I also like UiPath's security features because it gives us lots of tools to secure sensitive information. We can encrypt the customer data and store it in UiPath on-premises. We can also control access so that only authenticated users can obtain the data.

Citrix and email automation could be improved. We can use the features, but the accuracy isn't 100 percent.

I have used UiPath for the past five years.

I rate UiPath support eight out of 10. They provide us with assistance while we are developing bots. We can send the Orchestrator logs to UiPath to find out where a process is failing. For example, a web-based process might be using an old particular password. The support team will notify us that we need to update the password in the production environment.

Before we implemented UiPath, we tried Automation Anywhere. I like UiPath the best because it has capabilities like Document Understanding, AI, fabric, etc. UiPath has more features than Automation Anywhere. When we did a POC of Automation Anywhere, we found that the data scraping wasn't as accurate when working with PDFs.

The deployment may be straightforward or complex, depending on the project. Before each project, we have a testing phase of about seven to eight days. We have a 10-day monitoring period. In that 10-day period, the developer is also involved with the support. We have a different support team that takes care of most of these things, like deployment and monitoring the processes. If something goes wrong, they have to open a ticket and reach out to the developers.

Our implementation process involves checking all the business requirements. We look at the software and machines our clients use and the steps involved. Once we know the business requirements, we start working on the modules. We determine how many modules we need and the amount of time it will take to develop them.

After that, we have a daily scrum call. If we have issues, we reach out to the business, and they will come back with a solution. We need to undergo this initial development phase before starting anything. Once the development is completed, we have multiple process design documents detailing the processes and steps. We also work with third-party integrators. About seven or eight staff members are involved.

This solution does not require much maintenance once it is deployed and we've granted the access required. Once we've ensured the process is running and done the initial updates, we don't need to maintain it.

I haven't calculated the ROI, but I've heard that other people have seen 60 to 70 percent return on what they invested.

The pricing depends on the project and how many hours we will charge.

I rate UiPath nine out of 10. There are still a few areas that require improvement. Before implementing, I suggest doing a POC so you can evaluate other tools side by side to see which one is best.

I have worked with most of the UiPath use cases. From 2017 to now, I have delivered more than 400 bots. I have worked in healthcare, energy, shipping, and other industries.

When it comes to manual processes, especially IDP and the combination of IDP and automation, the journey has been a bit difficult and challenging, but it has been worth it. Most other automation is straightforward. We take input from multiple platforms, put it into another platform, and so on. But with IDP, we have to read the document, validate the data, and then integrate it with the automation tool in UiPath.

I started integrating IDP and automation before UiPath Document Understanding and the Action Center were available. What I used to do was automate the process and then create a layout in ABBYY. I would then integrate the ABBYY layout into UiPath, evaluate the data, and then automate the rest. I did this in 2018 and 2019.

Now that we have our own Document Understanding and Action Center platform, I don't have to rely on any third-party tools for IDP. The combination of automation and IDP within a single platform has made a big impact on many businesses. It has helped them to reduce their annual efforts in data entry, reading documents, and correcting small errors in data extraction and copy-pasting.

I have seen the best results when IDP is combined with automation. It has reduced manual efforts by at least 80 percent. Automation is always helpful, but the combination of IDP and automation is even more effective.

In one example, we were able to deploy more than 700 bots for a single organization in the manufacturing industry. They had around 25 servers just to run the bots, but now they are running multiple bots on a single server. They are saving millions of dollars per month by using UiPath.

Overall, I think the combination of IDP and automation is a huge game-changer for businesses. It is helping them to save time, money, and resources.

Most of the elements we have right now as activities with this do not require us to work with the norm of 100 lines of code or anything like that. It is just drag and drop, so anyone can use UiPath from scratch and be approved within a couple of months. The platform itself is very easy to learn and use. I don't think there were any challenges at any point with respect to this.

UiPath enables us to implement end-to-end automation. We have many back-end processes that run without any manual intervention. We simply schedule the bots, and they run flawlessly. We also have a bot that generates reports for us. As a result, we have had end-to-end automation in place for almost a year now. We are very pleased with how it is working, and we believe it is a valuable feature.

The UiPath User Community is great. I am proud to be a part of the community, where I have earned the Community Moderator badge, the Bylaw badge, and the MM VPA badge. I have witnessed the incredible journey of the community, from a group of people who didn't know each other to a community that meets in person at least once a month. The quality of the answers in the forum is amazing. I have seen a few companies create internal competitions to see who can answer the most questions in the forums and receive prizes. These small gestures from the community make a big impact. I would say that the community has played a major role in the growth and deployment of UiPath. UiPath has never failed to surprise and value the community members. The company has never disappointed us, and it continues to support our efforts.

When we join the UiPath Community and become an MVP, we gain direct access to the company's product engineers. We can provide our feedback and reviews for every product and release, and we also have beta access to all products when we are eligible as an MVP. Every review, opinion, and idea that we provide to the product managers is taken seriously and reviewed. If it is valid, the product managers implement it. I think this is the best thing about being a part of the UiPath team, both as a team member and as an individual. I really like the core UiPath team very much.

We have UiPath both on-premises and in the cloud. I think we were able to make significant savings when we upgraded to the cloud, especially in terms of infrastructure costs, deployment, and upgrades. The dynamic nature of cloud computing has helped us to reduce costs and save time.

We often use the UiPath Academy courses. I believe that 80 to 90 percent of my team uses the Academy, and it is the main platform where we have learned to use UiPath. I recommend that everyone take the Academy courses. For anyone who wants to learn UiPath, the Academy is the best place because it has everything we need to know.

UiPath accelerates our digital transformation and reduces costs. We did not need to upgrade to expensive or complex applications to accelerate our digital transformation.

UiPath has reduced up to 70 percent of the human errors.

UiPath has helped free up staff time. We have citizen developers from UiPath who are using UiPath Studio X to save almost 70 percent of their daily time on email automation. Especially when it comes to process mining, they don't have to do the same update task; the processing is ready, and everything is ready to be given to the developers. Even the developers are saving time when using the RA framework for SAP or ERP applications, such as by creating and using libraries of common screens, selectors, and steps. This saves them at least 50 percent of their time, so they can focus more on research and development and new features.

Document Understanding and Action Center have added significant value to UiPath, especially for the IDP process.

There are a few businesses that are failing to generate their ROI. I think that's where UiPath needs to educate businesses so that they can choose the right product for them, whether that's the entire automation solution suite or just the individual products that they need. I think that educating businesses about this will help them a lot and make it easier for them to succeed.

When integrating with third-party tools, UiPath gives us the freedom to write our own code and integrate it. However, if we could get a repository of at least a few of the layouts for the GUI or AI Center, where we would only need to make minor changes, that would be helpful. For example, the files have a template that extracts all the information. I would just like to change a few things, but I don't want all of that. I know we can just hide it, but that won't help because processing the whole document extraction will still take the same amount of time. If we could get those codes in any of the repositories where we could make small changes to the existing code and then import them into our processes, that would be helpful. We do have all the code. We do have all the activities, but none of them are accessible or modifiable. We have to use them as is, or we have to create our own. Those are the only two options we have. If we could get the codes in the report that we want, and then we could make the changes and use them in our own code, I think that would help us more.

I have been using UiPath for seven years. I started my journey in December 2016 and we started delivering projects to clients in 2017. I have been impressed with the evaluation of the UiPath products from 2017 to 2023. The features that we have been receiving in recent years are very good.

When I started as an automation engineer in 2017, people at companies like Sony and other networks and large companies were scared to share their processes and credentials due to security concerns. I have seen this challenge firsthand. However, now, companies of all sizes, including national banks, are looking at automation.

I have seen an incredible journey from 2017 to 2023. I am happy to have been a part of it.

UiPath is stable.

UiPath is scalable. We are able to upgrade anything.

Whenever we have a challenge or similar issue, in rare cases, such as when there are multiple questions assigned to a support ticket, there may be a slight delay in technical support responding.

The initial deployment is straightforward.

The deployment time depends on the complexity of the project, ranging from six weeks to four months. For a very simple UiPath automation project with multiple applications, we can complete the development, UAT, and deployment within six weeks. However, if the project involves IDP, validation, and other complex features, it may take three to four months to complete.

The number of people required for deployment depends on the complexity. I always suggest having proper planning. I would not let any of the junior developers deploy to production at any time. I would always have two different teams. This is my preference. Instead of having junior developers deploy to production with only one person, even if they are capable of doing it, I would suggest not giving access to everyone to deploy to production. Instead, they should reach out to the production support team, and the production support team should do a code review before the deployment. Once the code is reviewed, the production support team can publish the package to production.

I have seen organizations that have been able to generate an ROI of almost 100 percent, as well as organizations that have struggled to generate even a 10 percent ROI. Some companies are very good at knowing what licenses they have bought and how to use them, but I have also seen companies that have a whole suite of automation tools that they are not using, including process mining and test suites. They are still paying for all of these tools, but they are struggling to generate an ROI.

The main complaint I receive about UiPath is the pricing. Many people purchase the entire suite, which can be expensive, even though they don't need all of the features. The pricing is also somewhat opaque for businesses of all sizes. Unless a company is a UiPath partner, it is difficult to customize the solution to pay only for the features that are needed.

I would rate UiPath eight out of ten. We have experienced some automation processes that did not turn out as expected, especially with legacy applications, which can be challenging.

I have not seen any challenges with UiPath upgrades, but there are a few things to keep in mind. Consider a client with an on-premise deployment. The developers have returned their code, which is very old. After two or three years, the client is finally upgrading. During this time, a few activities may have changed drastically or been removed from UiPath because they have been merged into other activities. In these cases, we need to do some maintenance to ensure that the upgrade is successful. We need to check that everything is ready and that the upgrade looks good. This may take some time, but it is the only maintenance that is required.

We generally use UiPath for invoice processing, finance-related processes, and other similar processes in the oil and gas industry, including government and child welfare use cases.

My organization also used UiPath to automate processes for a good cause, particularly for a US organization that was into child welfare and adoption, so that was one of the use cases: automation for a child adoption and child welfare organization.

To me, the most valuable feature of UiPath is document understanding.

AI is also a valuable feature, as that is the current trend, so it's one of the most essential features of UiPath.

I found it very easy to build automation through the solution, as it has a drag-and-drop interface. If you know the flow and understand the basics, you can easily build automation in UiPath. In simple terms, the solution has a low code interface.

My organization saw many positive outcomes from UiPath automation, mainly when it was applied to an organization in the US focused on child welfare and adoption.

The solution also enabled my organization to implement end-to-end automation. That is important because I would always prefer some end-to-end automation wherever possible, even with a bit of human touch in the loop. I find solutions that enable end-to-end automation, such as UiPath, great.

I found the UiPath user community valuable. I'm a very active member of that community, and one of the good things about it is that it's active and full of people helping each other learn and grow, even when people don't know each other. I learned a lot from the community to be who I am today.

My organization worked with one client with an on-prem environment, and UiPath still has a good platform for an on-premises setup. It's called the Automation Suite, particularly the latest version.

My team, including myself, took courses from the UiPath Academy, and I recommend the academy to anyone interested in learning RPA and understanding the basics of UiPath. Even for someone who needs some refresher or retraining, I would recommend UiPath Academy, as I find it one of the best places to learn.

My organization used several UiPath AI functionalities for automation, including document understanding, language understanding, and even generative AI, which has significantly helped.

I also like that the AI functionality of UiPath enabled my organization to automate more processes overall.

The solution helped speed up digital transformation, mainly because manual processes take up much time. Still, with UiPath, time and costs were drastically reduced, so I find the solution beneficial. It has also reduced human error in the organizations in which it was implemented and even freed up employee time. The amount of time freed up would depend on the use cases, but the time saved would be significant for a company with a lot of automation. UiPath also helps save costs, but it depends, so it would be difficult to determine a number or percentage.

What could be improved in UiPath is the release or update because my organization noticed that a few minor bugs occur from time to time, mainly on the development side. That is not a showstopper, but if the UiPath team could inform my organization ahead of time, that would reduce the need for developers to find a workaround for the bugs. UiPath releases need to be improved.

I started using UiPath in 2019. I'm still using it.

Stability in UiPath is good, but this relates to the little bugs that my organization noticed in the community edition of the solution, not the enterprise version. Other than the minor bugs, stability-wise, UiPath is good.

UiPath is a very scalable solution.

My experience with the UiPath support team is very good. The team was very helpful and supportive. The support team is an eight on a scale of one to ten.

Before UiPath, I used Microsoft Power Automate and Blue Prism. Still, UiPath is more advanced when compared to the two tools, plus UiPath has a much broader scope, with over twenty products addressing different stages of the project lifecycle.

The AI or RPA and automation capabilities offered by UiPath are also quite good versus what Blue Prism and Microsoft Power Automate offer. UiPath is one of the leading tools in the market.

Deploying UiPath in the cloud is easy because it only requires some configuration before use.

For on-premises deployment, you need to install specific applications to get the solution to work. Still, with the UiPath support team, you can easily do the on-premises deployment, so deployment isn't a big issue.

The pricing for UiPath is OK, but it's a bit on the higher side, as the target audience is a bit different.

UiPath is deployed differently for clients. Some have an on-premises deployment, while some deploy it on the cloud.

You don't need many people to deploy the solution because if you have the infrastructure, such as the database and the server, ready, one person who understands the infrastructure would be able to do it.

My rating for UiPath overall is a nine out of ten.

My organization is a partner of UiPath.

I work in the financial sector, so my organization mostly used UiPath for disputes, fraud, and chargebacks. My organization had a pretty straightforward use for the tool as it had rule-based manual processes that required automation; otherwise, the organization had to hire temps for manual tasks. My organization used UiPath primarily for fraud and dispute bots, and chargebacks.

I found UiPath nicer than other RPA tools. I like that its enterprise version is pretty user-friendly, plus my overall experience with other components, such as UiPath Orchestrator, was pretty good.

I also found the tool's basic features, such as extracting values from Excel or PDF files and logging into applications, pretty decent compared to other tools. I haven't explored the OCI feature of UiPath that much, so I'm unable to give feedback on how good it is.

Overall, UiPath was easy to use, and building automation via UiPath was easy, with no blocks or restrictions from an application point of view, except inside a Citrix environment.

The tool enabled the organization to implement end-to-end automation. However, it was just a POC, and later on, the team didn't carry it out because the complexity was too high, not because of UiPath, but because of security reasons. The POC went well, but a closer look at the complexity made the team decide it wasn't a good business case.

As a user, I was pretty satisfied with UiPath.

The tool helped minimize the on-premises footprint, which was important because my organization wanted to go digital and had a target.

The team recommended UiPath Academy courses to some of the newly hired process analysts, particularly the UiPath basic course, but primarily, the developers already had advanced UiPath training.

In some cases, UiPath helped speed up digital transformation; in others, it slowed it. Sometimes manual handling was quicker than the bot because for some legacy applications the organization was using, you had to intentionally put some delays, for example, when pages take time to load.

UiPath also helped reduce human error and increase accuracy. My team didn't encounter any production incidents, but in some cases, when other applications or trusted applications, such as mail services, came in, sometimes the bot clicked the button, but still, the mail wasn't sent. The application was supposed to send an email to the client, but the mail didn't go through, though I cannot blame it on the bot, as it had something to do with the other application or service and not UiPath.

UiPath also helped free up employee time. The team calculated the OMDA for each business unit so each unit could focus on a more critical task, for example, where employees can be more innovative. The reflected hours were decreased by up to fifty hours due to bot usage, but it still depends on the business case. A small bot could save up to twenty to twenty-five hours, and in some cases, a bot can save up to one hundred fifty hours.

Initially, UiPath didn't help my organization save on cost, but in the long run, it did.

My organization hardly faced any issues with UiPath, except for a policy issue, mainly when my organization had to do automation inside a Citrix environment. Before that, the organization had to install another component from UiPath inside the Citrix environment separately. The team couldn't find the selectors it was trying to work with until it installed a component, which may be considered an area for improvement.

There are also many security protocols in the organization, and the team also worked with PCI bots. Sometimes, there was a block if the application didn't have the latest upgrade. There was a security block because, manually, people still worked with the older versions, but the bot wanted the latest upgrade from the application, so in some cases, there was a delay or failure, or the bot got killed. It was a mixed bag, so I cannot say it was one hundred percent successful, which is another area for improvement.

In the future, I would prefer UiPath to have built-in AI activities that an organization can quickly adopt, so you won't have to go to a third party dedicated to working with building AI components.

I worked with UiPath for two or three years until the start of this year, but now I've switched to another technology, such as DevOps.

In terms of UiPath technical support, A dedicated person attends to my organization's needs. You can email that POC, for example, when you need to register a license or device, and the response time is usually one to two days.

My rating for UiPath technical support is seven out of ten. The speed of response could be faster, and it would be better if support were more interactive, where the team could reach out to my organization monthly to check if it needed help or had some struggles with the solution.

Before UiPath, I used Blue Prism. I found that UiPath was more user-friendly than Blue Prism, as even non-technical users can use it through the drag-and-drop functionality. UiPath also has a more enterprise approach. The UiPath Academy was also free, which helped a lot of beginners.

My organization had a COE deployment where the COE team was responsible for installing UiPath. My team also builds local robots from some of the ad hoc requests, so my team does the deployment for that.

We've seen ROI from some of the UiPath bots. Still, it was quite a journey because, at first, there were many apprehensions within the organization and the teams, primarily about backups, and nobody understood that robots could be a piece of software and not a physical type of robot. It took over two years to establish trust, and from there on, it was comparatively easy.

We found the pricing for UiPath reasonable. We compared it with Blue Prism and Automation Anywhere, and based on features and pricing, UiPath stood out.

We evaluated Automation Anywhere and Blue Prism, but Automation Anywhere had many limitations compared to UiPath. Blue Prism, on the other hand, was expensive, so we settled for UiPath.

If I remember correctly, the version of UiPath I last used was the 2020 version.

I used the UiPath User Community sparingly. I logged in to see what other users were saying, and that was it.

My organization didn't use the tool's AI functionality for automation as it was still experimenting with chatbots, so with a chatbot, RPA, and handshake, my team didn't go that far.

In the organization, UiPath was deployed on-premises.

My rating for UiPath is eight out of ten.

I'm a UiPath customer. It's a tool used in my organization.

We use multiple types of applications, including SAP. I work on contract documents with UiPath mostly. I work with different clients in different companies. We use the solution to automate processes. It helps by reading contract documents and updating details in SAP applications.

We use a lot of document understanding. It reads the documents for us. I had a document understanding from UiPAth about two years ago. They helped us understand how it would work. With it, we were able to build a solution for invoices and purchase orders.

I like that we can work with different types of classifications. Whenever you classify a document using an ML model, there is a license associated with it. However, the intelligent classifier doesn't consume any of the licenses unless there is a specific amount of usage on the respective document. We process around a thousand documents per day and the classification is free. It helped us process all of these documents. We were able to train our ML models easily.

Building automation with UiPath is very easy compared to others. The UI is easy. There's a community forum where you can request help. They also have a marketplace to help you find customized solutions.

Previously, a turnaround time for a particular process was two to three days. Once we automate the process, we can handle the process in three hours. The turnaround times have improved a lot. We've drastically reduced our turnaround time on each transaction we handle. That's reduced our costs by quite a lot. That said, I don't have an exact figure off the top of my head.

The user community and forums are great. They are really impressive. When I started in RPA, it was difficult to find help or to help others. The forum gives us the platform we need to help each other and source solutions to problems. It's now easy to find answers. It helps a lot.

We use the AI functionality. I've used it for 1.5 years. It offers good functionality. However, you need to have a good understanding of how to use the resource effectively.

We've achieved 80% to 90% now using AI.

We can automate more processes now. We need to do a proper assessment first to see what we can get from AI. However, there's functionality beyond document understanding. That said, finding the right use cases can be difficult.

We've sped up digital transformation and the cost surrounding it. It also wasn't expensive to do so. We can go ahead with minimal cost. We just need to align the solution with the right resources.

It's reduced human error. We have the functionality to capture business exceptions. If we need human confirmation, it will get sent to the action center. However, by automating, we've reduced the need for humans. We've reduced human error by 20% to 30%. The bot will capture data in areas where in the past humans may have made mistakes.

The bot has freed up employee time. We do have attended automation. If there are tasks needed for humans, we've created the process in such a way that they can do these tasks and then spend the rest of their time on other activities. It's likely freed up human time by 10% or more. We'd only work on processes where there is a minimum of 10% reduction in human time.

There are a few bugs and a few things on the technical side where certain features are not available.

There are some functionality limitations on UiPath that we could have access to on different platforms.

If we have to move the model to production, we have to download it and upload it again.

I've used the solution for seven years.

The solution is stable as long as you maintain it in a proper way. You need an admin and support team to take care of performance.

We work mostly with enterprise-level organizations.

The solution is scalable.

Technical support is good. If I have questions, they help me. However, I've had colleagues who have raised tickets and had trouble resolving issues. I personally have never had issues.

We did not use other solution other than UiPath. However, I have done some small POCs in others. I've used Automation Anywhere, for example. There are different commands in AA and a few different features, however, they are both accurate and efficient.

I've set up the solution. The deployment takes a few hours. There may be software and hardware requirements If everything is there, it might take one or two days to get everything up and running.

You may need to maintain your production servers after setup to make sure the bots keep running. We might have other weekly or monthly maintenance tasks to ensure everything is performing as expected.

The solution is growing in price. It's getting to be too expensive. While I like the solutions they are providing, they need to balance the cost so that they can stay competitive in the market.

I'm a customer.

I would recommend the solution, however, new users need to be mindful of the cost. If they have the budget, they should go with UiPath.

I'd rate the solution nine out of ten.

I have been in three different organizations working with UiPath. In all of them, I had to create the center of excellence for UiPath. For automation, we decided to use UiPath because it was easy to learn. We had citizen developers involved. Most of the use cases were typical manual repetitive tasks and did not involve too much intelligence. I did not use the AI components in any of the use cases that I have done in the past. We mainly had end-to-end automation of simple processes. They were not too complex.

I have worked in the energy sector, and there were processes that were connected to renewable energy projects, but they were not related to a good cause, such as improving sustainability. We also had processes that did not provide any financial gains for the company, but they improved the motivation of employees. For example, we automated a process to check employees' birthdays and sent an email congratulating the person and tagging their manager as well. There were no financial gains, but it had a good impact on employees.

In most cases, it is easy to do automation with UiPath. It is not always the best solution, but in most cases, you can imitate what a user is doing. You can substitute that and create a process. It is very easy to do this. The complexity normally comes from the reengineering of the process to make it more efficient, but that is not about UiPath. That is more about the company thinking that we have been doing this for a long time and how we can make it better. It is very easy and straightforward most of the time. From the thousands of activities UiPath has, I end up using the same activities 90% of the time. It is very easy to remember and organize in my mind. As soon as I hear a process, I know how I am going to do it. For example, on receiving an email with an Excel file, we will extract the data that goes line by line into SAP or another platform. We will then save it and then write back the status by email. This is a very simple case, but it would be very hard to implement using any other technology. When it comes to end-to-end automation, about 90% of the time, you can do end-to-end automation with UiPath, but there are times when UiPath is not the best solution.

The main benefit of UiPath is that it is easy to develop and deliver automation. We can do this while software engineers are dealing with a more robust solution for the future. For example, when we need to connect different applications, and there are no API calls they can connect to, UiPath can provide a bridge for the short to medium term while resources are working on the final solution. I do believe that UiPath has a lot of strengths, but in terms of maintenance, there is one more application in the middle that we need to make sure is working for the end-to-end process to not fail. I can deliver a solution in one to two weeks instead of waiting six months for the final solution, but there will be more maintenance.

UiPath has freed up employee time, but the time saved depends on the use case. We had some very big processes that saved a few days. Overall, it frees up about 10% of our employees' time.

UiPath has saved us costs in theory, but in practice, I am not sure. It saves the time of our people, but we are not letting go of those people, so the cost of those people is the same. However, these people might be doing other work that might bring money to the company.

It is very easy to develop and deploy. It is easy to work with different applications at the same time. For example, I can read an Excel file and then go to SAP or any other platform. I can then open Outlook and send an email from Outlook. I can even use Teams. Being able to combine all these applications is the main thing that I like.

I also like how fast it is to develop a big, low-code platform engine. You just drag and drop, and most of the activities are done. It is very fast to create processes. I like it.

Its pricing changed again this year. I do not know why it just went up, but I do not like that. This is something that I would like them to improve for sure.

It would be nice to have the possibility to change the values in the middle of the debug. For example, I am debugging a process, and I write at a place. The value of that level is one, but I want to see the results of it if I change it to two. It does not seem possible in UiPath. It is possible in other software, but in UiPath, it is not yet possible.

I have been using UiPath for six years.

The Orchestrator, cloud, and everything else have been stable.

It is scalable. We have about 20 people using it. It will impact around 40 to 50 people.

I do not have direct contact with the UiPath technical support because we have a vendor, and we go through the vendor.

The UiPath community is very good. I myself do not contribute much to the community, but anytime I have doubts, it is very easy to find a solution in the UiPath community. The community gives a lot back. There are a lot of people writing back. It is very well established. About 90% of the time, I find the solution, and the other 10% of the time, I find a way to the solution. It normally takes me less than a day. There are a lot of activities created by the community as well, which are very helpful. I know some of the people who create these activities. People just give back.

In my current organization, we were not using any other solution previously. In other companies where I worked, UiPath was the first solution, but in one company, I also worked with Blue Prism. We had both UiPath and Blue Prism at the same time.

UiPath is easier to learn. It has certain activities that Blue Prism does not have. Visually, UiPath is much more appealing. I know the visual appeal does not matter much to a lot of people, but it matters to me.

It is deployed on the cloud. We moved to the cloud last year, and it took us two months to set it up and go from on-prem to the cloud. About 50% of the time was spent on things related to our company in terms of security and other things. It was not on the UiPath side. On the UiPath side, it was pretty straightforward. It was pretty nice.

Five people were involved in total, but they were not involved not full-time.

We have seen an ROI, but I do not have the metrics.

Its price is fair, but I would prefer it to be lower.

I would recommend UiPath. I would recommend starting with very simple processes. Do not go for a very big end-to-end process. Start with a part of it, gain confidence in it, and then start building on top of it. Many times, the process that people want to implement is too complex, and they do not put it down on paper. They do not do a cleanup of the process, and most of the discussion is happening while developing, which makes it complex, so I would recommend starting with something small, seeing the results, and growing from there.

Overall, I would rate UiPath an eight out of ten.

We have many use cases, including 50 or more in the finance domain. This solution supports Robotic Process Automation, RPA, and I work with it for website automation. We use it with SAP and use it for Excel automation.

For example, we use it to download an EML file, and using a UiPath application, we extract PDFs using OCR activities and convert them to digital files. Once we've accepted all data from the PDF, we update all of the details digitally and send the particular data to the business via a consolidated business sheet.

The success rate is 80% to 90% using UiPath.

It's easy to build automation. It's a drag-and-drop activity. You don't need to code or write. All activities are available in the activity planner. We can build a bot and deploy it to VMs to use in production.

Even a person who has no coding knowledge can deploy a UiPath automation.

This solution enables us to implement end-to-end automation. It's a big part of the process. In UiPath, some setup of validation is there. It can get technical. Not each and every process needs to have automation. We use the validation to discover if it is zero, semi, or full automation. We'd look at the applications involved in the business process, like SAP. We'd mark it as what percentage is actually needing automation. The solution helps by selecting logical tasks. Some areas are only able to be done by humans. In that case, it's only semi-automated.

The user community is good. If you search for an answer, it's a way to find solutions.

UiPath Academy courses are great. I used them to complete my certification. The courses and videos make it easy to understand. There are Studio, Orchestrator, and Robot courses. There are courses from basic to advanced. Everyone can jump in and learn very easily.

The solution helps us speed up our digital transformation. We used to need seven to eight people for some processes like processing invoices and we were able to reduce it by two to three people.

Human input is prone to error, however, UiPath helps reduce human error. While UiPath does sometimes make errors, it would be due to errors in the creation or logic. That said, if created properly, it removes the need for human intervention and removes errors in general.

It's freed up employee time. If I need to check something every day or do validation, it would typically take two hours of my time. Now, I can use a bot to do that work. I no longer have to worry. It flags only what I need to action and I don't have to look at everything.

UiPath has saved us money. We reduced two to three full-time employees by automating tasks, we save that money in salary.

Sometimes we get some disconnection issues. This happens maybe 10% of the time.

We have trouble sometimes finding answers in the UiPath user community. Using the community portal can be difficult. However, how they give training is very good.

We've had an issue with the selector.

I've been using the solution for four to five years.

The solution is stable. There is no lagging application-wise. There might be unexpected pop-ups or Windows upgrades that may affect UiPath, otherwise, it is very reliable.

The solution is scalable and has a good scaling framework. You can scale your process at any time. In-house, we were able to build our own scaling framework without issues.

We've contacted technical support twice. We were migrating from classic to modern architecture. Our team is pretty technical and capable, so we haven't needed much help. When we reached out, they were good. However, sometimes they took a while to respond.

We also use Blue Prism. I'm also aware of Power Automate. The simplicity, ease of development, and consistency made us move to UiPath. However, now the market is changing, and our company is considering moving to Power Automate as it is cheaper. Still, at this time, UiPath is better than Power Automate.

We use the solution on VMs and Azure. We are also using continuous deployment, CI/CD.

I was involved in the deployment and we started the process for the company. We take care of the deployment, development, and maintenance. Now, everything is stabilized.

It's easy to deploy. We can easily publish through UiPath Studio or get a packet and deploy it where we want. We have one release manager that handles the process deployment.

Without maintenance, a UiPath bot cannot run well. You need to handle updates, et cetera, to make sure bots don't fail.

The pricing and licensing costs differ depending on what you use. Comparatively, Power Automate is cheaper. However, UiPath is cheaper than Blue Prism or Automation Anywhere.

We're an official UiPath partner.

I have no experience with their AI functionality.

I'd rate the solution nine out of ten. If the pricing was less, it would be ideal. Other than that, it's a great product.

In my last company, we focused on Document Understanding. We received medical claim forms through Outlook and extracted the data from them. That is one use case. At my current company, I'm doing SAP automation.

My organization has automated around 200 daily processes that were previously manual. Some things that may have taken weeks in the past can be completed in a few hours. UiPath has reduced the costs of digital transformation and improved our productivity because the processes can continue running over the weekend when no one is in the office.

I like UiPath's Document Understanding and OCR functions. That's UiPath's advantage. It has a native OCR tool, whereas other tools do not, so it provides an end-to-end solution that covers everything. We do not need to integrate other applications.

It's effortless to build automations in UiPath. Anyone can learn it because it has a drag-and-drop interface. We only use about 10 percent coding. It's easy to understand. The UiPath Academy is also available for anyone who wants to learn the solution. The academy courses are free, and you can get a certification. Anyone can take advantage of it.

I would like UiPath to add built-in ticketing to Orchestrator so you can raise a ticket directly to the vendor inside the solution and send the error information. We have to build our own error-handling process, which is an enormous task.

I have used UiPath for a little more than a year.

UiPath is mostly stable, but we have encountered an issue after an update where a process created under a previous version may fail, so we need to update the bot.

UiPath's scalability is excellent because we are automating processes in India and other countries. We have already automated more than 200.

I rate UiPath support eight out of 10.

I have used Automation Anywhere and Power Automate. UiPath has an advantage over other tools because it can perform end-to-end automation and cover more activities.

Deploying UiPath is straightforward. One person is enough to deploy the solution, but I may need to contact the solution architect if I need access to something. We deploy to multiple locations because we are a multinational company, but we are not providing services to any other company. We have our internal clients, including stakeholders in Denmark, Norway, and some other countries.

I rate UiPath nine out of 10. UiPath is better than other competing technologies.

We use the solution for building automation.

It's easy to build automation using UiPath. I'd rate the ease of use eight out of ten.

UiPth allows us to implement end-to-end automation. It's very important to us and very helpful.

It's helped us minimize our on-premises footprint.

The user community is very helpful. We are able to converse with people and look for solutions to questions.

I've used the UiPath Academy courses. It helps us use the US version.

It has helped us speed up digital transformation and reduce the cost of digital transformation. We were able to speed transformation in a way that wasn't expensive.

UiPath has helped us reduce human error. It's also assisted with productivity.

The product has freed up employee time, however, how much time depends on the process itself.

The solution has helped us save costs. How much we save depends on the process.

The recording module could be improved. The screen identifications can be better.

I'd like it to have a more convenient development. If they had more development assistance, it would be helpful.

I've used the solution for two to three years.

The product is stable.

The solution has been scalable.

Technical support is very good and very responsive.

We did not previously use a different solution.

It was easy to deploy the product. It was quite quick to implement.

I have witnessed an ROI while using the solution.

The pricing is reasonable. It's cheaper than its competitors. There are additional fees for maintenance and support.

We did evaluate other options before choosing UiPath. We chose this solution based on its feature offering and reasonable cost. It had a better graphical user interface than other options.

I'm a UiPath customer.

At this point, we don't use the UiPath AI functionality.

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

I'd advise potential new users to do a proof of concept before investing in UiPath.

The use cases for UiPath are mostly based on SAP products, web applications, and APIs.

UiPath is a tool which is mostly used for process automation. It's not like a normal automation tool. We have different kinds of process automation tools in the market. UiPath provides the best integration between multiple applications. It has supportive technology for all kinds of applications. It supports all kinds of products like desktop products and web applications.

So, integration is the best feature of UiPath. UiPath provides attended and unattended robots to do automation. It provides a use case for scanning invoice processing. So, these are some of the useful features provided by UiPath.

UiPath is currently lacking a Citrix environment, mostly on remote desktop applications. The banking sector is more concerned about security. To open an application, we need to enter some token authorization. Such kinds of processes or technologies need to improve in UiPath.

I have been using UiPath for three to four years.

When we face technical or product issues, we raise a ticket to UiPath support and get technical assistance from Uipath regarding the products and services.

Before UiPath, I used an automation tool called QTP/UFT tool.

The solution's initial deployment is easy, and it's not that difficult.

For the solution's on-prem initial deployment, we need the license and installation of the Orchestrator and the robotics machine.

Since it's a single-contribution project, I did the solution's development, deployment, and post-deployment support all by myself.

UiPath has helped streamline most standard processes, and it has also made the rule-based decision-making process stable. The solution helps us save a lot of time and manual effort. It has improved the accuracy and speed of processes like approving tasks, processing tickets, or the expenses of the employees. Most things that were very slow when done manually have become very fast nowadays with UiPath.

Comparatively, UiPath's pricing is higher than other tools. Since it provides the best services compared to other tools, UiPath's pricing is reasonable. Nowadays, they also provide cloud robots that don't require any infrastructure in our organization.

UiPath is a very easy-to-use and scriptless tool. Since it doesn't have any code involved in it, any nontechnical person can also use it for their professional work. They can automate any kind of workflow as per the business knowledge. UiPath doesn't require much technical knowledge and is very easy to use.

In most service-based or manufacturing organizations, UiPath can be used for processes that deal with a good cause. In the service-based organization, it provides employee benefit services like the recruiting process and retirement process. The solution also does monitoring tasks like license validation.

If you talk about social services, the solution also helps with passport scanning, which mostly happens in the airport. With the help of UiPath, we can immediately scan the passport and get the required information from a security point of view. So, it provides all kinds of the most relevant use cases in real life.

In UiPath, multiple stages are involved, like requirement gathering, business analysis, preparation of the process design documents, implementation of the perfect automation, and then deployment of that automation. After the deployment, we provide post-deployment support to the end users. This end-to-end process involves all kinds of stages, from requirement gathering to production and deployment. So, UiPath provides end-to-end automation.

UiPath provides a trial version of 60 days, which is the community edition and is completely free to use to learn. They have their own academies to learn the courses, which are also completely free. It also provides a certification of UiPath as a developer. UiPath has the best forum community edition where you can raise your questions and immediately get support or answers from the community. UiPath's user community is very user-friendly.

With UiPath, we have reduced a lot of manual work and saved a lot of time. It helped us reduce the most complex activities involved in the finance and HR departments.

I have used UiPath Academy courses and completed my certification program as a UiPath developer. Since UiPath is a scriptless tool, any user can learn the tool very easily by using the UiPath Academy courses. UiPath Academy courses are completely free. They don't have any charges and provide all the practical sessions and environment.

The UiPath Studio is also available for a 60-day trial version. You can install this tool on your machine, practice, and become an RPA or UiPath developer. So, UiPath Academy is the best tool to learn the UiPath tool.

Currently, UiPath has a lot of things like machine learning, artificial intelligence, and natural language processing. We have integrated all these things with UiPath. We also have AI Fabric in UiPath. By using AI, we can automate the more complex processes where decision-making is involved. The solution's AI functionality is mostly used in invoice processing or approving budgets.

UiPath's AI functionality has enabled us to automate more processes overall. AI gives us more leverage on process automation by reducing manual work and saving a lot of time in complex situations where decision-making is more complex. Based on historical data and previous experience, our UiPath bots can learn many things and give the best solution in AI.

UiPath gives more features to digitize your current business from manual to automation. It also saves lots of manual costs and real-time employee costs.

Although not 100%, UiPath reduces human error and provides more accurate results. It is very fast in terms of processing, and we can automate any kind of process. It works 24/7, even on weekends and holidays.

UiPath helps us to reduce or avoid some manual, repetitive tasks that most of our employees do on a daily basis. We have automated such tasks, and it saves a lot of employee time. So, employees can contribute their time to new innovations, new tasks, or new projects.

Nowadays, time is money. With UiPath, we save a lot of time and money in real-time employees.

RPA has multiple automation tools like Blue Prism, Automation Anywhere, and UiPath. We chose UiPath in our organization because it has more features than other tools.

I was involved in setting up the infrastructure for my current project. I was involved in the installation of the robots, the installation of the Studio, the connection between the Orchestrator and the Studio, and the deployment of the robots on the machine. I was involved in such activities, apart from the development.

Overall, I rate UiPath a nine out of ten.