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.

I've worked on many use cases for UiPath, primarily automation use cases, but the most recent one was for the HTS sector.

The customer was inquiring about payments, whether the payment was fully paid, partially paid, or whether there was an outstanding balance or payment discrepancy.

It was for a US client, and based on some validations, checks, and settings, I needed to identify if the payment was on time, delayed, or never paid. I had to commit to determining the information or data for my customer, which included many validation business rules. I had to consider the checkpoints before replying to the customer's query.

The query used to come through email, and I needed to extract the emails, identify what the query was for, and then go ahead and provide the solution.

Many new improvements in UiPath after 2018 have helped end users stay competitive in the market, such as document understanding and process mining. UiPath has also helped significantly in documenting scanned invoices and restructuring processes. UiPath is continually growing and updating, and that is a big help to organizations.

What I like best about UiPath is that it's undoubtedly the leader in the market.

I like that the solution makes life easier through its multiple features. It's easy to use UiPath through its Excel functionality, a basic application you need. UiPath also has many connectors available, so using the solution is easier.

I also found the document understanding feature of UiPath helpful in automating data from PDFs, whether it's to classify or extract information from documents. The document understanding feature also has many extractors, making data extraction easy to apply to the existing company processes, one of the best features of UiPath.

Compared to other RPA tools, such as Blue Prism and Power Automate, UiPath stands out in terms of the scalability of automation that you can do on the platform. UiPath is more reliable and has many actions available for almost every application, which is why the solution stands out.

Building automation using UiPath is simple, but it would still depend on the developer or designer. If you do not plan the process correctly, it will be messy. Regarding the actions for building automation, you can pull and drop into boxes, so it's easy.

My company used UiPath to automate processes dealing with a good cause, mainly giving people more free time to focus on learning new skills and growing professionally rather than spending all the time working on repetitive, mundane tasks. My company automated a process for the customer and delivered that to the customer.

UiPath enabled my company to implement end-to-end automation. Still, there may be a few requirements that would make the solution not feasible, for example, applications where it would be challenging to use UiPath, even with plug-ins.

The UiPath User Community is the biggest out of all communities by other platforms, and I found the community helpful. Many experts in the UiPath User Community are ready to help.

I've used UiPath Academy. Its courses helped me in understanding UiPath in detail. I started learning the solution from the academy itself. It is great because it covers all the basics and advanced topics. UiPath Academy is a one-stop solution for learning UiPath and its products, services, and offerings.

The solution has also helped in speeding up digital transformation.

Uipath has helped reduce human error in any process or task that is rule-based, which doesn't need any human interference or judgment. My company developed tasks on the platform and created code to handle specific situations or scenarios that completely took care of manual intervention or manual efforts plus, the deployment was easy, and the solution saved a lot of manual effort. UiPath reduced human error by up to ninety percent.

The solution helped free up employee time by up to forty percent after the automation by reducing the need for employees to work on repetitive tasks so employees could focus on other, more challenging tasks, including learning new skills.

One area for improvement in UiPath is that the orientation could be better.

Debugging also needs improvement because I need to do it from scratch whenever I have to debug a code. I have to run the entire code from the start and then check the pointers. If a specific action can be developed in UiPath, instead of running the code from the beginning, it would allow you to debug the code from the point that needs debugging, saving a significant amount of time.

My company has tested the AI functionality of UiPath, and for complex processes, it takes a lot of time to develop the processes from a development point. When a process is complex, it depends on the end users or developers on how to break the requirement into small pieces. Suppose you do not break it into small pieces and create a single push out of it. In that case, it will become a lengthy code inside UiPath Studio, making maintaining and monitoring that code difficult inside UiPath Studio. Locating the error or actual information would also take more work, so UiPath could be challenging to use in complex process automation.

Pricing for UiPath also needs improvement as it becomes expensive in large-scale implementations.

I started working with UiPath in 2018, so from that time, it's been five years of working with the platform.

UiPath is a stable tool.

UiPath is a scalable tool.

I found UiPath Support good.

UiPath consultants provide good support and are readily available via email.

It takes about ten to twelve hours to receive a response from UiPath Support.

I'd rate support as eight out of ten.

My company used Blue Prism before UiPath. I work for a service-based company, with clients choosing the tools based on priorities. UiPath was cheaper than Blue Prism, but when you use it for a large-scale RPA implementation where you deploy hundreds of robots, UiPath becomes more expensive than Blue Prism. However, development on UiPath was significantly faster and more reliable compared to Blue Prism. UiPath also has a larger community offering support versus Blue Prism and even has free training on UiPath Academy. UiPath also offered a free trial, which Blue Prism didn't offer. These are the reasons for switching to UiPath.

Setting up the UiPath infrastructure was a little tricky, but the deployment was much easier. It usually takes one month to complete the deployment if the process is simple, but it could take up to three months for a complex process. Compared to other tools, the deployment and development of UiPath was faster.

In terms of manual efforts, realizing the benefits of UiPath was immediate, but for the financial benefits or ROI, it took some time, as the solution has a huge cost. It required you to purchase the UiPath Studio, Robot, and Architectural licenses. You also have to pay for the development costs, so the monetary benefits took time to reflect in the cash flow.

My company did notice between sixty to seventy percent ROI from UiPath, which was calculated around the number of FTEs, mainly how many FTEs were released from a specific task. For example, there was a big project with sixteen FTEs released from a repetitive task.

When there's a massive deployment of robots, pricing for UiPath becomes costly, as you must purchase different licenses for UiPath Studio, Orchestrator, etc. I noticed that it would solely depend on how service-based companies negotiate with UiPath and that each client could have a pricing disparity. A client with a more significant implementation could get more discount, pricing-wise.

I had the chance to work with Blue Prism and Power Automate.

UiPath does not require extensive or complex application upgrades and support, at least not for every application. Sometimes, support is needed depending on the project or application, but the chance of it would be very slim.

UiPath was deployed on-premises. In terms of environments or locations, the solution was deployed in three different environments: in the Studio, Orchestrator, and Testing.

The number of users of the solution varies per project, but the maximum number of users I've worked with on a single project is about thirteen or fourteen.

My company has worked with small, medium, and large enterprises using UiPath.

The solution doesn't require maintenance. It just requires license renewal.

My rating for UiPath is seven out of ten. I'd make it a ten if UiPath improves the appearance of the Studio. Its debugging process could also be improved, as it's currently complex. It could be easier.

My company is a UiPath partner.

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 leverage UiPath for customer service use cases and process automation to improve employee productivity and reduce time spent on repetitive work. UiPath is mainly used for financial processes like automated invoicing, but we also use the solution for IT processes.

UiPath is deployed on-prem on a private cloud, and all our BFSI customers are on-prem. BFSI customers tend to use fully on-prem environments. UiPath offers cloud and on-prem versions, but the functionality is the same. A few technical aspects are a little different.

UiPath makes our employees' jobs easier by eliminating repetitive tasks. The solution has reduced the time spent on these tasks by around 35 to 40 percent. They can use bots and spend more time on more productive work. We've improved process efficiency and employee productivity using automation.

It's helped us discover better ways to make each process more stable. Our productivity has increased from 20 percent to almost 45 percent. That's what the change we have seen using you about. Using UiPath has reduced human error by 99 percent. I can't say 100 percent because nothing is fully automated.

UiPath's automation features are all equally valuable, but we use the unattended bots the most. UiPath is easier to handle than most RPA technologies, and it's easy to install, so it's a competitive solution.

The UiPath community has helped us troubleshoot issues. For example, if a bot isn't working properly, we can go to the forums to find the root cause of the problem. My technical team uses the UiPath Academy to get certifications and gain a better understanding of the product, but I haven't used it.

We use some of UiPath's AI functionality, which makes it easy for us. Predictive analysis suggests the next logical step and what could be the possible solution for that. It tells you the possibilities and the pros and cons of each step.

The OCR technology has room for improvement. UiPath accurately reads about 85 percent of the fields in a scanned document, but that needs to be somewhere around 90 to 95 percent.

I have worked with UiPath for nearly three to four years.

The uptime for our bots is almost 99.9 percent.

UiPath is highly scalable. We plan to increase our usage because we aren't using it internally. It's something we deploy for our customers, so the usage will increase as our business grows.

I rate UiPath support 10 out of 10. There are many ways to get support, including the knowledge base, live assistance, UiPath Academy, and UiPath support center.

I was not involved with the setup. I sell the licenses, and the technical team handles the deployment. UiPath requires some maintenance, such as platform updates, updating the bots, and adding workloads.

UiPath has reduced our employees' processing time and our expenses. UiPath has cut costs by about 18 to 20 percent. You can start realizing the ROI within six months to a year.

UiPath is affordable compared to Blue Prism or AutomationEdge. A basic license covers the cost of implementation and recurring fees that depend on the complexity of the processes and workflows.

I looked at Automation Anywhere and AutomationEdge. UiPath is easier to implement and use. Cost is the primary factor. Indian customers tend to consider the cost of a solution more than the features.

I rate UiPath 10 out of 10. The solution can't give you 100 percent automation for complex processes, but it gives you up to 90 percent. However, once you optimize a bot, you can reuse it for other processes.

We use UiPath to automate routine tasks using bots.

UiPath has helped improve our organization by automating routine tasks that can now run 24/7, error-free, and without the need for a salary.

Building automation using UiPath is moderate.

UiPath enables us to implement end-to-end automation, but the amount of automation possible depends on the process. We can typically automate up to 70 percent of a process using UiPath, but some processes can be fully automated. In my company, we have been able to fully automate medium-sized processes, but only if the data is in a good format.

UiPath's user community is extremely helpful. Whenever I have an issue while developing a process, I can go to the user community and find a solution.

I completed both the UiPath Associate and Advanced Certificates using UiPath Academy. The Academy is helpful in segregating each topic so that we can find the corresponding data.

UiPath has helped accelerate our digital transformation and reduce its cost. No expensive or complex upgrades are required to speed up our digital transformation.

UiPath has helped reduce human errors by 30 percent and helps save our staff time.

UiPath is easy to use and easy to manage.

We can not exceed ten records in the UiPath database because the UiPath architecture will become extremely slow and not respond.

I would like easy-to-understand and follow documentation for different scenarios.

I have been using UiPath for three years.

UiPath is stable, and each version comes with new advantages. UiPath supports .NET versions, Windows Legacy, and current versions of Windows.

UiPath is scalable.

Technical support has been good.

We previously used Blue Prism, but the control room is much more difficult to manage than in UiPath, which is very easy. The same is true for process development, which is much more comfortable in UiPath.

The only drawback of UiPath is that it is not possible to provide a value during debugging, as we can do in Blue Prism. This is the main difference between the two platforms.

Some of the process deployments were difficult. The deployment takes a few hours. We used five people for the deployment.

Our profit has increased by around 50 percent using UiPath.

UiPath is somewhat expensive.

I would rate UiPath seven out of ten.

We have 70 percent of our footprint on-premises.

Maintenance is required for patching.

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.

Most of my use cases are spread across all the business units. It's used in accounts payable or for receiving reconciliations. It is also used in directory management and the banking finance sector.

UiPath has a lot of features and they have added a lot of things. The apps and document understanding are good. We use document understanding a lot, even though they may not be common for day-to-day processes.

The Orchestrator is amazing. It provides a huge benefit including data security and data storage.

We can add a huge number of activities and can input code right into the platform.

While there might be companies that use the product to do automation for good cause, however, so far, in my experience, I have yet to do much of those use cases. I’m more on the business process side.

The product enables us to implement end-to-end automation. When they first launched, people used to have some sort of hiccups, however, now you don’t need different tools to manage your entire automation journey. With UiPath, from the discovery phase on, you have everything you need. We can understand the ROI clearly and can see what we’ve invested and what we’ve received.

The user community is valuable. It has the biggest community. Everyone knows it. One of the reasons UiPath is so successful is the UiPath community. We have tremendous people in the community supporting each other in terms of development or community events. People from different organizations can explain different pain point areas or explain good use cases and share learning and feedback.

We use both cloud and on-prem services. Most companies prefer on-prem over the cloud. From our perspective, we’re working to convert users to the cloud to reduce the footprint. Still, many want to maintain that on-prem segment.

We use the UiPath Academy courses. Since the beginning of my career, I’ve used it. Whenever there are new products that are launched, they will release certain courses for training purposes. I've gone through training at the Academy. I found a certified trainer also to provide training. Overall, having the training available really helps new people who want to kick-start their careers using the app.

They've also implemented community collaboration. If someone from the community has developed something, they will add training based on the community. The user has larger visual data now, compared to what happened previously.

The solution has allowed us to manage digital transformation and reduce the cost around it. Automation really helps boost digital transformation. We've seen cost reduction around resource use and the cost of operations as well.

We've been able to reduce human error using UiPath. Of course, it depends on the people developing it. However, as long as the people have good implementation experience, we can really minimize errors.

It's helped free up employee time. However, it is not a major amount across every project. Comparatively, it can save a number of hours versus manual labor.

We have saved money and that's calculated on the number of hours saved in terms of man hours. We haven't cut staff; they are now working on different tasks instead.

We've used AI functionality. On a real-time basis, we haven't seen many benefits from the AI center. It's not cost-effective to run models on it as of now. We haven't been able to automate more processes. Some projects don't require AI at all. If it gets more cost-effective and has more use cases, that might change.

The tool continuously redefines itself. They release three major versions every year and target one major feature once a year, like AI, et cetera. However, there are a few features at an early stage and not quite mature yet.

The initial tools are good enough compared to other vendors, however, they are still refining and need to change a lot of things, especially in the AI center, which is not that flexible when it comes to deployment. This is the same for UiPath apps. In most cases, nobody wants to invest a lot of money in attended bots. They need to work on that.

We'd like to see them work towards more stable outcomes to minimize hiccups.

I've been using the solution for more than six years. I started in 2017.

Previously, we haven't noticed stability issues. In the past year, we have noted issues with stability. There have been some hiccups.

The scalability depends on the way a company implements it. From a cloud perspective, the scalability is good. That said, the flexibility is there to scale.

We've had issues in the past where products were not working as expected and we've reached out to support. The experience has been mixed. Sometimes it is good. Sometimes solutions are delayed.

I did not use a different solution previously. However, I have used Automation Anywhere, Power Automate, recently, and also Intellibot and Blue Prism.

Power Automate is still quite young. There are still items missing as it's new.

UiPath excels in the Orchestrator. The flexibility is great as well.

We've worked with both cloud and on-prem deployments. However, people seem to prefer on-prem. Almost all of our clients are maintaining their own cloud and then running UiPath into the cloud from on-prem.

I was involved with the deployment. The setup is straightforward. For the governance and audit security principles, we do need to add in a bit more. We might add, for example, a CI/CD pipeline.

We tend to have three to five people, part of the support team, to help with the deployment.

There is some maintenance required. We need to monitor our VMs and understand if the robot is failing and if so what is the root cause. We have an interior support team for maintenance services.

We did not use an outside vendor for the setup. Only people in the department are allowed to handle the deployments due to compliance.

We cannot calculate an overall ROI. However, if something isn't getting 150% or more, people tend to not want to implement it. So far, we've seen a very good ROI.

The costs have gone up recently. The pricing seems to be a bit higher for the end user.

We are UiPath partners.

I'd rate the solution seven out of ten. The most recent tools are not as impressive compared to what is happening in the market.

As long as others don't need additional tools like Apps or document understanding, I'd recommend it. There are a lot of features and functionality to try. However, if you need document understanding and apps, I'd advise users to look at their use case, do a POC, and figure out if it's a perfect fit.

From the perspective of pure automation, UiPath is excellent. However, if a company is looking for AI functionality, they really need to see what else is out there and what is best for them.

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.