We use UiPath in various internal departments to automate our HR, financial, and IT operations, including access management and ISO compliance to control traffic.

We have UiPath deployed both on-premises and in the cloud.

Building automation with UiPath is easy. The solution is user-friendly, and we do not require technical knowledge or skills to use it. With a little training, we can start building automation with UiPath. Customer support is helpful if we get stuck at any step, and the dashboard is user-friendly and centralizes control in one place.

We use UiPath for multiple end-to-end processes.

The UiPath User Community is a good place to learn and get answers to questions we have related to UiPath.

The UiPath User Community edition is flexible and allows us to practice and learn for free before taking what we have learned to our enterprise edition of UiPath.

UiPath has improved our operational process efficiency, allowing us to schedule processes to run 24/7 and freeing our employees from repetitive tasks so they can focus on other work.

UiPath Academy courses are useful for our employees. We also have access to the enterprise learning portal, where materials are available.

UiPath has helped reduce human error. When all the prerequisites are met and the process is fully automated there is a zero percent chance for human error. For the processes that are not fully automated, UiPath was able to reduce human error by 60 to 80 percent.

Before UiPath we had one employee tied to one business process and after implementing UiPath we have one employee tied to multiple domains. Our staff now has time to work on other tasks.

The most valuable feature of UiPath is the ability to consume APIs directly from any application.

UiPath is expensive, and its cost could be reduced to make it more accessible to small and medium-sized businesses that could benefit from it. The orchestrator and licensing cost should be flexible instead of hard-coded licensing.

UiPath is limited to one application at a time and cannot process two applications simultaneously. This functionality could be improved to support dual browsing, making it more efficient.

I have been using UiPath for almost four years.

We have not experienced any crashes of UiPath. We have experienced some slowdowns three times this year, but this could be due to our internal network rather than UiPath.

The scalability is good. We can adjust our workflows according to the conditions with no issues.

Technical support is extremely helpful. We contact support whenever we need to upgrade our volumes, and by following their guidelines and prerequisites, we can easily complete the upgrade ourselves. Once the support team responds to our call they are quick to resolve our issue.

Before UiPath, we performed manual integrations, but the types of processes we could automate were limited. We faced challenges automating any process where humans needed to make decisions or where minor tweaking was required between the target and source applications. UiPath has removed these restrictions.

UiPath is easy to install, and its representatives are flexible in supporting our installation. Upgrading our libraries and maintaining UiPath security protocols is also easy, which makes the overall installation process straightforward.

Two people are enough for the deployment.

We implemented UiPath in-house.

UiPath is more expensive than other solutions on the market, such as Microsoft Power Automate.

The Flex license is around $11,000. It should cost at least half that price compared to other solutions. We must purchase an orchestrator for each platform, which is mandatory and adds to the cost. UiPath should consider this and offer a more economical license.

I give UiPath eight out of ten. The cost brings down the overall rating.

Maintenance is required when running UiPath on-premises for the server, OS, and DB. On a bi-weekly and quarterly basis. We also have to implement tools for the firewall.

I recommend UiPath for large-scale and multinational organizations because they can afford the licensing costs. Organizations should explore UiPath before embarking on a transformation journey, as transformation requires significantly more cost than automating existing legacy applications. UiPath is flexible and can integrate with all applications.

We use the solution for automation. It helps with Excel automation, validation, data extraction, et cetera. We use UiPath for a client project we are working on.

It's helped improve the organization via an increase in ROI. The employees are much more productive and they no longer have to do repetitive, tedious tasks.

The product is very user-friendly. It has great drag-and-drop features. My background isn't in computer science, and it was easy for me to get familiar with UiPath and the user interface.

You can do almost anything related to automation. If it's related to email. databases, Excel sheets, et cetera. There's nothing that needs automation that can't be done on UiPath.

It's very easy to build automations. We can easily build end-to-end automation. We had a process, for example, that needed to be triggered once an email was received. The attachments needed to be downloaded and processed and a reply had to be sent back. UiPath could handle each one of those tasks.

The user community is pretty great. You can find an answer to basically any query. You can participate and reply as well.

I've used the Academy courses to learn more about UiPath since I started using the product in May. I started with the foundational course and then did the advanced course and action center and document understanding overview course. It's helping me learn everything fairly extensively.

The solution has helped us speed up digital transformation. They have enabled very fast digital transformation to meet a company's needs.

It helps reduce human error. I've helped deal with processes that would require employees to deal with thousands of forms. Using UiPath can reduce human error quite extensively. If there was a chance of human error at 25% before, it's been reduced to a maximum of 2% to 3%.

The solution helps free up employee time. The employee, in turn, can be more productive and learn new things in the meantime. It's likely freed up more than 30% of employee time so far.

I've only used the solution for six months so it is hard to consider improvements. It would help if there was functionality whereby you could upload something like a flow chart and the solution could process steps according to the flow chart.

I've used the solution since May of this year.

The solution is stable. From what I have heard from my team, it's almost always stable.

Our clients are large-scale enterprises.

It is very scalable. You can add or change things as needed and update processes as necessary. We do have quite a sizable process that involves ten to 12 departments and it works well.

Technical support is responsive. They were very kind when I dealt with them.

I've used other platforms such as Power Automate and Automation Everywhere. UiPath is a lot better as it is very high-level.

I did not directly deal with the initial deployment.

There is not too much maintenance required.

Clients have noted an ROI. They've found employees are much more productive.

I haven't seen the pricing or dealt with the licensing of UiPath.

However, I have heard of clients switching to Power Automate due to the fact that it was cheaper than UiPath.

I do not exactly use the AI functionality. It's not part of my job at this point.

I'd recommend automation for digital transformation. As for which platform to use, it would depend on which processes they need to use. UiPath is quite suitable for mid-level to large enterprises.

I would rate the solution nine out of ten. It's an excellent product.

We use the solution for the implementation of automation for normal processes. We deliver use cases to customers.

The ability to automate everything is great. You can also do process mining and optimize costs. It can help save a lot of money in an organization.

Depending on the business, and how you calculate the cost vs savings, the time to value varies.

It's a complete ecosystem. It has everything you need. You can do attended or unattended bots. There's AI. There are document processes that you can do as well.

It's very easy to create any type of automation. It's the best solution so far in the market.

We are able to implement end-to-end automation. It's important that you can automate anything with UiPath. You are not limited. You don't have to have any extra connectors.

It has helped minimize our on-premises footprint. You can migrate to the cloud if you like. However, many companies, like banks, do not prefer the cloud. They prefer on-premises setups.

I've used the Academy courses. I've started one and haven't finished it. My plan in the future is to utilize it more. The structure and details are great. If you are new to UiPath, it's very good. It helps effectively onboard new people.

It helps reduce human error.

We can free up employee time by 90%.

If you are saving time, you are saving money, and therefore, it has helped save costs.

Everything is working well. Of course, there can always be improvements.

I would like to see them integrate with generative AI like ChatGPT. It might make a developer's life easier.

I've been using UiPath since 2019. However, I have not been continuously working on it.

The solution has been very stable. I'd rate stability nine out of ten.

The solution is very easy to scale.

I've never been in contact with technical support.

We previously used a different solution.

The implementation is very easy. The deployment is similar to other products. You create a file and share it with a customer and they import it.

Through our methodologies, we define, design, deploy, and maintain.

Pre-deployment, we need to do some testing. After that, once it's accepted, you deploy. You don't need much staff.

There is some maintenance required for future changes in the application and any issues that may arise (like bugs). Typically, there's a business analyst and people from IT as well as someone from whatever department it's being deployed to.

The customer deploys the solution. We take care of the design and implementation.

I have noticed an ROI while using the solution. In general, a business analyst would do the calculations to see how much money would be saved if a robot was deployed.

I do not deal with the licensing.

We are UiPath partners.

I'm not certified in UiPath, although I do have experience with it.

I have not used the AI functionality yet.

I'd rate the solution nine out of ten. It's easy to work with UiPath. It has very good documentation.

We use UiPath in the telecommunications and banking sectors to automate various processes, including IT, HR, and financial receipt processing.

We began using UiPath to automate repetitive and rule-based tasks, such as extracting data from documents, inserting data into applications, and sending reports to end users using databases.

UiPath helps implement end-to-end automation by extracting information from documents using the OCR engine and automating procedures by integrating with Salesforce, SAP, and other systems.

The UiPath User Community is extremely helpful.

UiPath has helped to minimize our on-premises footprint.

UiPath Academy courses benefit our developers by providing them with certifications and badges that help them improve their UiPath skills.

We are currently testing the AI and machine learning capabilities of UiPath to make it easier to automate more complex processes.

UiPath has helped reduce the cost of our digital transformation and the number of human errors.

UiPath has helped free up staff time to focus on more valuable work by automating repetitive tasks.

UiPath has multiple valuable features, including stability, automation, and integration with different applications. In addition, the OCR in Document Understanding and the integration with the chatbot are also good.

The data extraction has room for improvement.

AI and machine learning always have room for improvement.

I have been using UiPath for five years.

UiPath is stable.

The technical support is good.

Compared to other automation tools, UiPath is expensive.

I would rate UiPath eight out of ten.

Building automation using UiPath is moderately difficult.

I recommend UiPath.

We use UiPath to automate PDF processing and extract financial and other information from PDF files. We store the extracted information in our database for our orchestration tool to process.

We have used UiPath both on-premises and in all the cloud services.

Building automation using UiPath is easy even for non-technical people.

It enables us to easily implement end-to-end automation.

The UiPath User Community is helpful for our technical users.

UiPath has helped our organization because its ease of use for non-technical people makes it easy to understand and implement the automation framework. The automation server is of high quality, and UiPath is cost-effective. We realized the benefits during the training process.

We reduced our on-premises footprint with UiPath. For any organization that still requires all of its information to be secured on-premises, we can do that as well using UiPath.

I have completed two certifications using UiPath Academy courses. The academy has taught me a great deal about UiPath services, the automation framework, and how to use UiPath with SAP automation.

UiPath helped us accelerate our digital transformation and reduce the cost of that transformation.

UiPath has helped reduce human error to zero for any process that has been fully automated.

UiPath saves our staff time by automating the routine tasks.

It has saved our organization money by reducing the number of resources we need by 50 percent.

With UiPath, we can automate any module, whether it is a desktop application, web application, or native application.

The error notifications sent to users can be improved by including more detail.

I have been using UiPath for almost one and a half years.

UiPath is stable.

UiPath is scalable.

The technical support center is available through the web.

Deploying the system can be complex for non-technical users.

We have seen a return on investment with UiPath.

The license cost is expensive because we have to pay for each tenant.

I would rate UiPath eight out of ten.

We have almost 30 users of Uipath.

Maintaining UiPath is easy.

I recommend Uipath. UiPath is easy to learn and provides good-quality automation.

The primary use case for document processing, automating data extraction from previously hard-to-access documents. This saves time, reduces manual work, and makes hidden data more accessible and usable.

It allows us to extract valuable information from various documents, categorize them based on their types, and make the data within these documents usable for our needs.

Assessing an AI center's role in orchestrating various elements of AI capabilities is quite constrained.

I have been working with UiPath for three years.

I find it to be highly stable.

Scaling on-premises can be cost-prohibitive due to the need to invest in hardware and infrastructure. This cost factor makes transitioning to the cloud a more attractive and well-designed option for scalability.

Our experience with their customer support has been excellent. We've encountered very few issues that required us to reach out, but when we did, we could contact our dedicated representative, and they efficiently escalated the matter, resulting in a prompt response from their support team. I would rate it eight out of ten.

We have experience with Microsoft Power Automate, but it's important to note that UiPath and Microsoft Power Automate serve different purposes and have distinct target use cases. This uniqueness is a critical factor that sets them apart from each other.

The initial setup process was quite straightforward.

We initiated the POC to test the viability and implementation of automation before expanding the environment. The setup was designed with the understanding that we required distinct test and production environments. It was initially developed as an on-premises solution and is now transitioning to a cloud deployment. We've had a lot of success with Lydonia Technologies as a partner.

We now have access to critical data, and the accuracy has improved significantly. Additionally, the time it takes for processes or submissions to go through has been reduced from three or four days to just one day. While the cost savings in terms of dollar values may not be substantial, the real benefit lies in freeing up employees to concentrate on more meaningful tasks.

I find the pricing to be reasonable, especially when compared to other offerings in the same market.

My advice would be to begin with a small-scale approach and construct your automation incrementally. While it might be tempting to automate an entire process in one go, it's more practical to break it down into smaller components. This way, you can adapt and refine each piece as you go, reducing the risk of issues arising or changes occurring before the entire automation is completed.

Overall, I would rate UiPath eight out of ten.

We have a lot of SAP Extract, transform, and load (ETL). We have human resources and time management. We have a very diverse tool landscape due to natural growth. We are in a very early stage of transformation, so we use it to bring information into multiple systems at the same time.

We also have a good few financial use cases related to tax. We work in Europe. Within the EU, there are different regulations, and sometimes, we have very short deadlines. On the third or first business day, we have to get information out of 16 or 17 SAP systems and format them. We have to get them out to Italy and Spain for government stuff.

The objective that we were trying to achieve by implementing UiPath was hard cost savings, but I changed that a little bit. It is not the right technology for hard cost savings. We have now changed it to quality and efficiency, and what they do with quality and efficiency is up to them.

Currently, we only use the core RPA. We joined the company only eight months ago. We worked for another company before, and that company is at a very early stage. We are setting up our CVs and our citizen development program, so currently, we only use core RPA and core automation services.

We are not using AI yet, but we are about to change that with Document Understanding. In the company where I worked before, we used Document Understanding, and it helped us a lot.

UiPath automations have increased the accuracy of our operations. We have a lot of peak sessions with finance and techs. There are quite high penalties if we get something wrong. For example, if we calculate our tax incorrectly and we pay too much, that does not mean we get the money back. If we pay too little, we also have to pay a penalty fee. We have reduced the error rate by over 25%. We saved 1.24 million last year. That is one aspect. The other aspect is the peak time work. We had a team of people coming in on the third business day at 5 am. I had to download all the reports and things like that because they had to get the report out by 12 pm. If they were not out by 12 pm, we had to pay a penalty. After automation, people came in at 8 am, and the reports went out by 10 am.

I like the low-code/no-code approach and the graphical interface. Among all the RPA tools, UiPath is the one with the easiest interface.

Orchestrator needs an overhaul. They have added so many functions that it is sometimes quite hard to find the right settings. They have a tree hierarchy with the host and the tenant. Some settings you do on the host, and some settings you do on the tenant. You need to know at which level you are to find what you need. It all looks very same.

The other thing that I have been telling them for years is the width of the activity. You cannot change the width. I do a lot of training to show something, and I constantly have to go into the advanced editor to show what is in there, but the big thing right now is Orchestrator.

I have been using UiPath for 12 or 13 years.

I have not had any issues. If something happened, it happened because of the human network.

It is very scalable.

The USA support is okay. I would rate them a seven out of ten.

Their support in Europe is good or very good if you get the right people. I would rate them between six to nine out of ten.

Their support in Asia needs improvement. I would rate them a four out of ten.

I have worked with Blue Prism. I have worked with Automation Anywhere. I have worked with what I call the Microsoft suite, which includes Power Apps, Power Automate, and Azure Logic. I worked very shortly with OpenSpan, later known as Pega. I trained at a university. I trained others in automation as part of the robotics lab at the University of Hanover. We looked at several tools there.

In terms of comparison between UiPath and Microsoft Power Automate, given the use cases for which I normally use them, they both have areas where they are good. If Microsoft could get their documentation right, the attended series of UiPath would be in a lot of trouble. Given the whole unattended and hyper automation or intelligent automation, which is the main focus of UiPath, you need orchestration. That is where the big bucks and the big savings are, but to get the technology out with the attended bots or shadow IT, Microsoft Power Apps and Power Automate are important because they help people understand what technology can do. What we see very often is that people start with Power Apps, sometimes even with a macro, and then they realize that they have hit a certain barrier very quickly. They come to us. Initially, we take what they have and just enhance it with UiPath, and then over time, we bring the functionality from the macro, Power Apps, or Selenium and migrate them into our things.

Currently, we are on-prem, but we are migrating to the cloud in November. We are currently not using the latest version, but with the migration, we will be.

I was involved in its setup. The Orchestrator setup could be easier. There are a few loopholes that you need to understand. UiPath Studio is straightforward, but the setup of Orchestrator has become a little bit more complicated over time. You need to connect them to bots, and you need to know what type of user you need for what type of robot, which has become more tricky. Overall, the setup of Orchestrator and certificates can be a bit challenging.

In terms of the implementation strategy, we took a test server and put it on. We did some testing with our network and information security team, and once they were happy, we moved it out to production.

For the current implementation, we did not take any help. The first one was done by a partner, but they did not do a good job. I did the second installation on my own because I knew how to do it.

In the previous company, they had a partner system.

I do not like the enormous jumps that they have had in the past. The ROI has become a lot harder because of the pricing changes. When you have time to plan for it, the ROI is there. If it was cheaper, it would make my life easier, but on the other hand, it is worth it. These jumps year after year are a problem for me because then I have to go back and say that prices have increased by 30% percent, and I get asked, "For what?" It takes a lot of time.

In this company, UiPath was already chosen. In the company before, I looked at all the big ones. I chose UiPath for the ease of use.

I would advise finishing UiPath Academy courses. After you have finished them the first time, finish them the second time.

I would rate UiPath a strong eight out of ten.

We use UiPath in all business areas like finance, HR, accounts payable, production, etc.

UiPath's entire package is valuable. It is a user-friendly solution.

UiPath needs to incorporate French and Portuguese language-based training. It is not easy for people without an IT background.

I have been using the product for four years.

UiPath is stable.

We have rolled out about 20 citizen development programs. We aim to reach 100 by the year's end. We use it all over the world. It is scalable.

We chose UiPath because it is easy to expand the benefits program.

The tool's deployment is time-consuming.

UiPath is expensive.

We implemented UiPath to increase quality and take away repetitive tasks from employees so that they could focus more. It helped us to cut down on time.

The tool has helped us save a few minutes of employees' time.

I rate it an eight out of ten.

I have used UiPath for use cases that are both transactional and linear. It involves human resources, cybersecurity, OEM reporting, IT service management, service delivery, and examining of patents and trademarks. We work with federal agencies in the public sector.

I enjoy the enhancement of UiPath's debugging tools. I like the IDE and integration services. There have been massive improvements. I love to work with Orchestrator. It has become more streamlined and helpful.

UiPath needs to improve its documentation. AI Fabric's installation was an absolute nightmare. I tried to get help from the documentation portal and couldn't find what I was looking for.

I have been using the product for four and a half years.

We have seen ROI with the tool's use. One of my use cases involves the Patent and Trademark Office, where two GS-15 patent attorneys worked on patent suspensions. An unattended bot helped to save two full FTEs' a year's worth of work.

We wanted to achieve less human error with AI-powered automation. We also wanted to streamline the process so that human involvement was less. Also, it helped us do more things than a human.

AI-powered automation has increased accuracy for one of our use cases. We used AI Fabric and Document Understanding to help with reconciliations that came in PDFs.

Automation has helped us free up our resource time by over 1000 hours.

I last used Process Mining in 2020.

I don't enjoy using Power Automate since its scope is limited. The environment where I use Power Automate did not purchase advanced licenses. UiPath offers more flexibility for programmers who are into API solutions. It wasn't available in Power Automate, which annoyed me.

I run a team of developers and spend most of my time in Orchestrator. It is the best product from UiPath.

We are a consulting firm. We started last year, and we are growing pretty rapidly.

We have quite a few document-understanding processes that we are working on. We are a partner of UiPath, so we have various clients in different industries. Currently, we are processing vendor statements to create payments in NetSuite. We also have a three-way match cache application process, and then we have a basic user interface for scraping vendors' websites for payment data and that kind of thing.

We are trying to figure out how to incorporate LOMs with everyday processes and get reliable information back. We are also training a lot of machine learning models to extract data from PDFs along with processing contracts. I hope that those get easier to train and that there are more reliable answers or outputs from the models that we train.

Our AI-powered automation initiative has fundamentally changed what our organization is able to achieve. Document processing has come a long way and become a lot more user-friendly with validations and Action Center. The straight-through processing has increased.

They are constantly making improvements to Action Center where you have more feasibility in assigning tasks. There is a lot more flexibility and data around it. We have been incorporating insights into our automations, which helps us create a business case for future automations based on what we have done in the past.

The use of AI in our automations has definitely increased the accuracy of our operations. It has also increased the ability to process certain use cases that were not available before. It gives us more opportunities to automate processes, and therefore, drive revenue.

The use of AI in automations has freed up time or resources for other tasks for our customers. The time saved depends on the use case, but they are probably saving about a thousand hours a month on the vendor statement processing. They are getting 2,000 to 5,000 statements a month. Each one takes roughly 45 minutes.

Their core platform of Studio is valuable. The ease of use and the ability to build these automations quickly is definitely a highlight for us. Our average process from start to finish takes three to four weeks. We can knock out automations as quickly as we can identify them. That is probably the best feature I see.

In Action Center, saving progress in data validation, specifically for table content, is currently not available. There should be more clarity around the feedback loop along with the auto-update feature when you deploy machine learning packages. They should give some rule-based options so that if the confidence is returned higher than the previous model trained, then it would auto-deploy. If it is less, then it should send you an email rather than auto-deploy.

With task assignment, if there was a round-robin feature within the bucket to automatically assign it to a certain group of people, that would be helpful.

There should be the ability to add custom fields to validation tasks because there is a lot of potential for it. It would be helpful when somebody needs to identify a scenario. For example, we have a customer who is processing rate sheets for trucking, and sometimes, depending on their customer, they have an all-in rate versus an adding fuel mileage rate. If they are able to specify that, even if it does not say it on the rate sheet, it would allow them to process more documents successfully.

We use UiPath's AI Center, but some clarity is missing around when to use AI Center versus when to use the Document Understanding module within Orchestrator. We are trying to figure out the benefit of one versus the other. We have also seen that the out-of-the-box models that we train versus a custom model that we train with the same data end up with the same output result at the end. We are trying to see where these out-of-the-box models are providing value if we are going to take the time to train them.

I have been using UiPath since 2019.

We have run into issues with integration services where we developed something, implemented it, put it into production, and all of a sudden, it does not run unattended. It is a very frustrating situation to be in.

There were some issues with sharing connections between different accounts, and we have learned from that experience to do more upfront testing of new features before we build automation on it.

Event-based triggers not working is probably the biggest stability issue that we have run into, and integration services not working is probably the biggest gray area. Other than that, it is a stable platform.

It is definitely a scalable platform.

Their support is good. I have had good success with submitting support tickets and getting answers quickly. If it is a bug that is identified with the process or with the platform, they resolve it within a matter of a week. There was a production issue. It was a throughput issue for the AI model. We were not able to access a 100-page document because of this exception. They implemented it and fixed it within a week, which I thought was awesome. I would rate their support an eight out of ten.

I did not use any other RPA solution previously. I have only used Power Apps a bit, but it was a very small part that we have looked into. Overall, we are strictly focused on UiPath.

I have probably set up 100 Orchestrators at this point, so it is straightforward. However, the initial setup is confusing for new people who have not done it where they are matching machines to the tenant and plugging it in their machine key, but I am not sure if there is any way to get around that. When you have done it once, it is easy.

The other thing is the licensing aspect of it. You need to assign a license to the machine template and then the machine template to the folder, and then you have to make sure that the machine is connected. There seems to be some confusion amongst our developers on how to make sure it is all set up correctly, and then you have the robot account. You have to make sure that it is also set up correctly to run unattended automations. It is a challenge, but if you do it two or three times, you get the hang of it.

In terms of the implementation strategy, overall, we look for quick wins upfront so that we can build the program and get support behind it, and then tackle the more advanced use cases after we get three or four in production.

We have cloud deployments. We have had different cloud providers, such as Azure, AWS, and GCP.

We are a consultant.

We have definitely seen an ROI in terms of hours saved and quality of work. Once you get off the ground, there are a lot of other departments that end up getting excited and looking forward to future automation. I feel that is a win for morale.

Overall, the model is fine except for AI units. It is usage-based, which makes sense if you are processing documents, and you have one unit per page. It is the hosting cost of the models where there are issues, so we are running into potentially designing poor solutions because we are having to say, "If the documents are very similar but different enough, even though you would prefer to use two models, maybe consider not using two because of the hosting costs."

Power Automate is something we might look at. UiPath has orchestration while Power Automate does not. Orchestration is vital for us.

If you are trying to do in-house development, the user experience is much better than any other platform that we have evaluated. It is easy to pick up. The UiPath academy, training, and forums are great. The biggest selling point for me is that you can pick it up as a business user and learn the platform in a matter of days or weeks as opposed to months or years.

I would rate UiPath a nine out of ten.