The way I'm using UiPath is to create workflows related to financial services. I work for a company called Cedar Financial here in Pakistan. The workflows are related to our data statements, clients' financial documents, and the like. It mostly involves Document Understanding and creating workflows to generate reports. My use cases are restricted to UiPath Studio, where I use the Activities to create workflows and automate some of my clients' work.

It's very cool to be able to create automations and reduce human effort. It really is a valuable and great tool to be working with. It has improved things immensely because our organization needs fewer human resources. In one department, 40 percent of the time has been freed up for other tasks. The work the bots do is more efficient and reliable. UiPath has reduced human error, which has had great effects: better results and better revenue. It has saved us about 40 percent of our costs.

Another important benefit is that UiPath enables you to implement end-to-end automation. Humans don't have to do repetitive, boring tasks.

The most valuable feature is its screen recording capability, where you tell it what the workflow should do, and it then automatically creates Activities for you.

It's easy to build automations with UiPath help. I have also been a Python developer, and there you need to do hard coding to create an automation. But when you're dealing with UiPath Studio, you have all the modules. You just need to know what to do and which Activities you can use. You get everything right, and the automation is ready for you. You don't need to do hard coding.

And UiPath's user community has been great for me. Every time I'm stuck somewhere, there's always a forum to ask questions and share my knowledge as well. There have been a few main developers, like Michael Jensen and a few others, whom I follow and really admire their work.

They need to keep fixing the bugs and improving the tool. For example, if an Excel file is running and I'm doing an automation on that Excel file, it doesn't complete. There are some bugs, and fixes and improvements are required.

The stability is good.

It's scalable.

Previously, I used Python and its multiple libraries and frameworks to do automation with Selenium and Beautiful Soup. We switched to UiPath because you don't need to do hard coding with it. You have more functionality. You just need to know what to do and keep on importing those activities. Create the workflow, and the automation is almost done.

UiPath is always a good investment.

I have tried Microsoft Power Automate, but UiPath has a lot of Activities and is easy to use.

The UiPath Academy is where everyone starts. I started there and took courses such as the RPA Developer Foundation course, and I still take courses from the Academy. It's very beneficial.

When you have RPA developers, they sometimes require IT support. The application team is also important in this.

The time it takes to implement a solution with UiPath depends on the problem and the workflow. Some might take 30 days, while others might take just one day. It does require some maintenance at times. There may be updates, or an error might appear. We have to provide support as well.

From a company point of view, it didn't take long to identify how beneficial UiPath could be. Every industry these days needs automation tools. If an employee generates the same report every single day, we can build a robot to do that.

It's a good and handy tool to use. Try it, and it will help you greatly boost your business. And your employees will be happy as well when their time is saved. Go for it.

We use the solution for robotic process automation. We use it across the value chain for our business. We've used it in accounts, including cash management, and in HR for management tasks and IT for password resetting.

The automation has been quite useful. It's been helpful in our journey towards transformation.

I've used this solution for a while and I utilize the whole tool and get a lot of benefits out of it.

It helps save time. We've had efforts that would take more than four hours a day, yet, when done through UiPath, it takes less than a minute.

The useability is very good - even for non-technical people. I'm an accountant by education and now I'm also an automation expert by profession. Its interface is user-friendly to those of us who are non-technical.

Anyone who wants to automate any task that is rule-based and repetitive can do it through UiPath.

We can use the solution for automation emails or notifications.

It enables end-to-end automation. We developed a use case where people from different business units have large amounts of data, Excel files, we've made it so that we can combine it and enter it into the ERP system. Everything can be checked via the rule book and can create the report and send back the information to the customer. It simplifies the data and organizes and compiles it for them. Users have gotten the benefit of five FTEs by using UiPath. It saved many man-hours.

I haven't used the UiPath Community too much. I often Google questions to find answers. It is a good place to go for development work, though.

It reduces our footprint. We historically did have many items on-prem. I like it on-prem and on the desktop.

It can reduce the cost of digital transformation. Where processes can have faster response times, UiPath helps with efficiency. However, if the response time of the application is slow, and we need to provide workarounds, it isn't helpful in that it hasn't efficiently helped us save time.

UiPath reduces human error by 100%. Whatever you give to the robot, it will do it correctly. That said, it needs to be programmed correctly - if it's programmed wrong, it will do it 100% wrong. If it's programmed right, it does it 100% right.

It's freed up human time. It's not well-utilized in that sense. It should be available to everyone so that they can find ways to save time by creating their own automation according to what they need.

There are a few shortcomings. For example, even in their latest version, there are still older features even though they've introduced new ones in parallel. They should do something where they update the solution and then close off the older version after a year or something like that. That might help with standardization.

Sometimes it is very useful for automation. However, sometimes it is really, really frustrating when it is unable to manage the more dynamic items. When an element is stable, it's great. When it comes to changes to IDs or the dynamics of the website, it lets us down in front of our customers. It needs to be better at handling volumes of data.

Automation on the cloud has had issues. It can be slower.

The Academy classes could be improved. There should be a portal for use cases. There should be more business examples.

They should offer different licensing tiers, especially for daily individual users.

I've been using the solution since 2016, more than five years.

It is a stable product. There were some issues while interacting with different applications. For example, with Microsoft, we have issues with One Drive. When UiPath is working on a file, it cannot quickly get to the file. We need to move the file to a local drive before processing the data. Microsoft applications seem to give it trouble.

We have multinational business units. Company-wide, maybe 500 people are using it. Where I am, there may be a team of ten people working with it and 50 to 60 automations. The solution is in multiple locations and departments.

The solution is scalable. It depends on how an organization wants to utilize it.

Technical support is very flexible, however, they do not respond quickly. Sometimes they just tell us "this is how it works" and we have to try to explain our framework.

I have also tried Blue Prism. I didn't work with it much; I just studied it theoretically.

I also tried to work with Power Automate. Initially, it wasn't very good, however, later, it began to echo the style and functionality of UiPath.

UiPath is easy to use and easy to get started with.

The deployment was a long journey. I was one of the first people in Pakistan to use it. Now, once you get a license, you can deploy it in two weeks. However, it depends on the complexity of the processes in terms of deploying automation.

We have around ten people maintaining the solution. It requires a lot of maintenance. If anything needs to be changed in the target application, it needs to be incorporated into the robot.

Someone told us you do need three to five years before you get an ROI. However, in our first year, we were able to save more than 8,000 hours.

The solution is on the expensive side.

There should be standardized packages. If an organization already has a license with UiPath, UiPath should offer special licenses to each employee so that each employee has their own UiPath automation capabilities for each of their individual tasks.

There should be regional packages and costs. Different regions cannot necessarily afford UiPath. What is affordable in Europe may not be affordable somewhere else.

We're a UiPath customer. We serve internal customers with robots.

We do not use the UiPath AI functionality, however, we are on a journey towards building our own internal solution.

I'd like to see UiPath cut the cost of their license. For end-to-end automation, for developers, I understand why it needs to be expensive, however, for day-to-day users, it should be cheap.

I'd recommend the solution to new users.

I'd rate the solution eight out of ten. It's still the best out of all related products.

I have automated finance use cases, as well as banking, NOC, and call-center use cases. I have also done email and Excel automations.

It has definitely reduced the cost of the process I have automated. It has reduced the number of employees required for some processes and improved process efficiency. It has improved accuracy and error rates. All of these factors reduce the cost of the processes.

Because there is no human involvement and there is a fixed flow that bots follow, it has minimized the human errors that occurred before.

The Excel automation in UiPath is very easy to use. Even for complex scenarios, we can easily automate the process. And that is true for email automation as well.

Building automations in UiPath is done through simple activities. We just drag and drop into a workflow, build the flow, and execute it. It's that simple.

We use UiPath Academy courses as well, and they give us an idea of how we can use it professionally. They have given us a complete idea of how to use the solution.

When it comes to web automation, a change order should be able to be handled more easily.

I have been using UiPath for almost three years.

Compared to other tools, UiPath is very stable, as well as easy to install, manage, and upgrade.

It is more scalable than Automation Anywhere.

I have not contacted their technical support.

UiPath has more costly licenses than Automation Anywhere and, of course, Power Automate.

There are multiple differences between UiPath and Automation Anywhere. Automation Anywhere has a good handle on desktop automation as well as its IQ Bots for document understanding.

I would rate UiPath at seven out of 10 overall.

In the past, we have used UiPath to automate repetitive manual processes for companies in the finance and banking sectors, but healthcare is our current focus. This industry involves processing tons of data from patients, customers, and doctors, so it's a huge field.

Previously, I developed bots for compliance at financial companies. I've also created processes for reading PDFs, sending emails, Excel automation, logging, and exception handling. We have also contracted with insurance companies that need to pull data from emails into their main enterprise application.

The healthcare companies cannot provide us with direct access to their systems for security reasons. We are currently accessing their network through a middleware system so it doesn't compromise their security. UiPath doesn't work on that third machine and cannot retrieve the values as it should. If we scrape data from the web, it will get to the HTML that is behind the site.

When we are accessing the third PC, we cannot get to it because it is a desktop machine. We are using the completed version activity, which is working mainly on the image image-based activity. This capability is available in UiPath, but I don't think Power Automate or Automation Anywhere can do this. It helps because we don't need to do any coding.

UiPath tends to be deployed on the cloud, so clients can minimize their on-premise footprint. We deploy on-premise and cloud-based UiPath depending on what our clients want. For some companies, uploading data to the Orchestrator on the cloud is potentially a security concern that hasn't been resolved by the UiPath developers. Power Automate has an advantage in that regard.

Our employees use the company's credentials to get training from the UiPath Academy and obtain certifications. I have a personal account on UiPath Academy, but it has some license issues. The academy is helpful because UiPath is implementing new features every three months or so. It's all about the documentation. We can learn about new features and do more. With more knowledge, we can develop something bigger.

UiPath reduces costs by eliminating human labor. Let's use an insurance company as an example. Let's say they have employees who are responsible for reading emails. Every day, they receive information via email from the customers, and their job is to retrieve the details and enter them into the main database. The average insurance company receives 400-500 emails daily. These people will spend the whole day completing the task of manually transferring data to their main application.

We have a bot in pre-production that can handle 1,100 emails daily for the company. It has a significant impact on the efficiency of the operation because the bot can input the details into the database quickly and without any errors. The employees who were responsible for this work are now monitoring it and also learning about UiPath at the same time. It is a great tool for increasing productivity, thereby proportionally increasing the company's profits.

The first company I worked with had 20 employees in their compliance department working on some PDFs. The company had to send emails to around 6 million customers. We deployed the bots, and five bots could do the work of 10 employees. The company kept the other 10 employees but reassigned them to monitor the bots and fix errors. They also learned to develop their own bots. They could cut 10 positions and save money while improving productivity. Those employees weren't working as fast as the bots and cost more money.

The solution also greatly reduces human error. In the financial compliance use case, they were dealing with upwards of a million rows. That was labor-intensive work, and no human could complete the task in under three days manually. Sometimes, we would have some errors in which the values were reversed by accident because humans make mistakes when they are tired. In this kind of work, we're working with digital amounts and currencies, and we are applying mathematical formulas to the amounts, like credit, debit, or some business calculations.

UiPath doesn't have large hardware or software requirements. We only need one physical PC on the client's premises. That computer requires some minimum specifications, such as a 1 terabyte hard drive and an i5 processor. We need that computer hardware and a license for the client.

If the client doesn't want to purchase an enterprise license, UiPath offers a community version. There are no restrictions on the features, but it can only run one bot at a time. The enterprise version can run multiple bots. If our client only needs one process, we can provide them with the community version and deploy it on their PC.

UiPath can free up employees to work on more important things. One of my colleagues was doing some tedious work manually, but once the bot was in place, he only needed to click one button to run UiPath, which extracts all the data and updates the Excel spreadsheet in 10 or 15 minutes. Previously, he spent up to six hours preparing the data before he could complete the other tasks. The important work was being delayed every time. It increases productivity, which benefits the company.

UiPath's most valuable features are its UI automation activities like scraping and manipulating data. We need to scrape the data before we can manipulate it or save it in another application. I think that part is very valuable and important.

Having worked with other tools like Microsoft Power Automate and Automation Anywhere, I find UiPath to be the most user-friendly because it provides all the actions on the side, and we can just drag and drop them. It's a simple interface that we can easily understand. Automation Anywhere has a more complex interface. UiPath is straightforward enough that our junior employees can easily pick it up.

UiPath's ability to offer end-to-end automation is critical. We typically provide our clients with a simple demo of what UiPath can do. After that, they provide us with details about their end-to-end processes, which we use to determine what can be implemented through UiPath.

For our healthcare client, the initial assignment was to scrape the data from the website and put it into Excel. Later, they decided that they wanted the data in another application, so it could be stored in the main database. We constructed an end-to-end process for maintaining a million records in their primary database.

I also like the UiPath Community forum. I go there when I get stuck with anything. When I run into an error, it's easy to find the answer. The community is highly active. If I post a question, I can usually get a response from community members in an hour or two.

I have tried a bot that uses UiPath's AI capabilities, but I didn't develop it. It's a portal for patients to make appointments and check into reception at the hospital. We implemented ChatGPT on an Android device, so customers can ask questions and get information.

We also developed a bot that can derive the same types of data from PDFs with different structures and formats. For example, let's say the patient's name is on the first row on one form, but on the third row on another. We can configure a bot to extract the name regardless of where it is. We can train our ML module by telling it when the data is wrong and running it again. Now, it's mostly accurate.

I would like UiPath to improve its screenshot feature. It should have the option not to take screenshots unless the user specifically allows it. Sometimes, it is a security issue for companies that do not want to share screenshots of the main application. Another thing I want to see is a standalone mobile application that we can run anywhere. I would like more cross-platform application support.

UiPath can get unwieldy if the process becomes too big and complex. I had one client based in Saudi Arabia that had an application with 1,500 pages. Once the bot we were developing got much bigger, the application started having stability issues. It performs well in typical cases, but once we exceed that average, the application starts to crash or behave abnormally.

I have used UiPath for four years.

Overall, UiPath is stable for most processes, but Power Automate is better at handling large, complex projects.

I have worked with Microsoft Power Automate and Automation Anywhere. The primary advantage of UiPath is that it's more accessible than the other solutions. You can learn UiPath without any knowledge of programming or computer science. It takes only about a month to learn the tool, even if you have no skills. For example, if you're a blogger and you want to automate posting to the website, you can do that through UiPath, so it is beneficial for personal use and commercial use.

The other advantage is cost savings. UiPath saves organizations some money, and it's more accurate than Power Automate or Automation Anywhere. Automation Anywhere is my third choice. Power Automate comes in second place because It was developed by Microsoft, and most enterprise companies have a Microsoft subscription. If their license includes Power Automate, they prefer to use that instead of buying a separate subscription for UiPath.

Many companies are switching to Power Automate because of this bundled licensing. The UiPath enterprise subscription is somewhat expensive. Microsoft can provide the same functionality, and it integrates with tools like Excel and Outlook. Companies can get all those tools within the same license, so that's an advantage Power Automate offers over UiPath.

Another advantage of UiPath is that you can also work with image-based processes. If we cannot get any selectors or access the HTML code behind the application, we can use image-based processes. This feature isn't available in Automation Anywhere. UiPath has the AI center, and Microsoft also implements AI in Power Automate processes. However, Automation Anywhere cannot use AI in their product.

My current company is smaller, so I'm responsible for multiple tasks. I am the requirement gatherer, developer, and deployer. At my previous company, they had a business analyst who talked to the client and made an inventory of their requirements that he provided to us. Then, my only task was to develop the bot. It was the other team's duty to deploy the bot on the client's physical machine.

The process involves three steps. We need to connect UiPath and provide the logs. Our client can access the Orchestrator to see logs of what the bot is doing online. He doesn't need to physically access the machine. There is also middleware called the UiPath Assistant that we use to connect UiPath to the Orchestrator.

The number of staff needed for deployment depends on the complexity of the processes. If it is a single process, we don't need a deployment person or team. The developers can deploy the bots. My company has five developers, so everyone is developing their own bots and handing them over to the deployment team. For every five developers, we have two deployers. If the five developers are developing automated bots daily, we need only two deployers to deploy them on the machine. Also, if we want to have a backup version, we can deploy it on GitHub to make the repository and organize everything.

The maintenance aspect can sometimes be difficult. Exceptional cases can arise during the process. When we initiate some processes, we need to monitor them for about 30 days. We don't monitor some processes because we're not seeing any errors or exceptions. We have to monitor other bots, stop them as needed, handle the exception, and run them again. After 30 days, the bot should be mature enough to handle the exceptions without intervention.

UiPath offers an excellent return. For example, a recent client in Pakistan was scraping data from a website with 349 products. His job was to scrape the title, price, and variants and place the data in an Excel spreadsheet. He was working all week alone, so I proposed UiPath. I told him UiPath has a function called "Extract Data Table" that can scrape all the details of the products and just dump it into Excel in five or ten minutes. He was impressed, and I developed the bot in front of him.

Now, he's running my bot and dumping all the results in his Excel sheet. He's also working on other projects, and his routine has become very stable. He has more time to spend with his family. It has surely made an impact and yielded a positive ROI.

I don't know the exact cost, but UiPath is more expensive than Power Automate and Automation Anywhere.

I rate UiPath seven out of 10. Learning a little JavaScript coding is helpful because there are some scenarios in which UiPath doesn't help you. In some cases, you may need to write a little code to perform some actions or call some functions. I would also take advantage of the UiPath Academy so you can stay up to date on the latest news and features.

We use UiPath for invoice processing and PDF extraction.

Building automation using UiPath is extremely easy. Everything required is available online.

UiPath enables us to implement end-to-end automation, which is the most important aspect for us.

The UiPath User Community is strong.

UiPath has helped us to minimize our on-premises footprint. We are using an on-premises orchestrator and working in the financial services industry, where we have to process 30,000 invoices per day. This would normally require a lot of manpower, but with UiPath, we are able to do it with only five bots.

We use the UiPath Academy courses and my team recently received the AI certification.

We use the AI functionality in UiPath to help automate more processes overall.

UiPath helps speed up our digital transformation.

It has helped reduce human error a lot.

UiPath has helped free up our staff time by automating the manual work and saving our resources.

The Orchestrator feature is the most valuable of all the automation solutions I have used, including OpenBots, Robocorp, and Microsoft Power Automate. It is essential for managing all of the processes in UiPath.

The UiPath Academy Orchestrator training needs to be updated to reflect the recent changes.

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

UiPath is stable.

UiPath is scalable.

The price for UiPath is on the higher end.

I would rate UiPath ten out of ten. I have used five other automation solutions and UiPath is the best.

No maintenance is required.

The development, scalability, and reliability of UiPath are the best, and I recommend the solution 100 percent.

I've been making some accelerators using it. Each Customer Relationship Management page in the telecom industry has a similar kind of structure, so things do not change a lot. I'm creating an accelerator that can log into a CRM and quickly perform specific tasks as per requirements. For example, the robot will log on to a CRM page, will add updated user information, and check the details of user requests. Another case could be creating specified user service requests and monitoring their status for service efficiency.

We're automating a bunch of processes in the telecommunication industry. We’re implementing RPA solutions in the biggest telecommunications company in my country. Our main focus was to increase the return on investment. What we tried to do was reduce the time, reduce the manual labor costs and errors, and increase efficiency.

The big picture is to work towards reducing labor costs and creating solutions that are required to enhance your efficiency. This also streamlines process workflows when handling robot exceptions.

The drag-and-drop features and the activities that are pre-made are useful. It's a big plus for UiPath. Whenever I use it, I can do all kinds of work with it and it's really easy. For example, if you have to store data in a dictionary or make a list, there are all kinds of ways to do it. You can do almost anything using UiPath.

The community is very good. I get 90% of my questions answered there.

There’s a good level of maturity in the UiPath framework. Once you get hands-on experience with it and once you are a little bit familiar with it, it becomes really interesting to make automation.

Another thing to add would be queues. It gives you the power to assign multiple bots to any item in the queue and you can monitor the activities and status in the queue.

UiPath enables us to implement end-to-end automation. Once you have hands-on experience with it, you don't even have to think about the steps. There are hundreds of activities to help you to carry out any solution. It enables you to perform endpoint processes really efficiently.

When you compare the solution to other automation companies, like Automation Anywhere or Microsoft Power Automate, UiPath has the biggest community, and that really helps you a lot. Whatever questions we have will get answered due to the extremely helpful and active community. You get answers pretty quickly as well. Most questions I have are already addressed there. It adds a lot of value to UiPath and plays a major role in our success.

I have done a few UiPath Academy courses. I have not gotten certifications, however, UiPath has advanced certifications and material on the website that lays out those certifications. They have a lot of tutorials to let you get deep into the product.

It's helped speed up our digital transformation. Our main focus has been on automation and increasing efficiencies while reducing errors and costs. Automation helps significantly reduce human error.

The ease of building automation using UiPath is appreciable. In the beginning, it was a bit difficult as you have to know about C# and VB Script. I come from a Python background. If you are making a list, for example, in Python, it’s very simple. There isn’t that much complexity. If you're doing list manipulation and dictionary manipulation, you have all kinds of data structures. However, when it comes to UiPath, it is not as simple since you have to be very certain about what you're writing.

There are some things missing in UiPath. There used to be an activity where you could just add an item. This activity is now gone. Some of the things in UiPath are changing. This is a bit difficult due to the fact that, if a beginner is trying to add something to a dictionary, they'll have to look through the community's communications and then they might figure out that the old ways are gone. But that is not always the case, there have been better and newly modified activities like ones that help choose selectors for UI Automation.

UiPath is not that fast. They do have an option to increase the speed of processes. You can increase their speed in the settings. However, whenever you do that, the chances of it curbing the flow at some point is higher.

I've been using it for the last three months. I jumped into this field of automation about six months ago. I have explored Power Automate, Robocorp, and Automation Anywhere during this time. UiPath, however, has been a good experience so far.

The stability is okay and chances of bottlenecking are not much. Occasionally there are some errors and the robots do crash but overall that is not an issue.

It's a mature product; it can scale well. It's pretty sophisticated so you can get a lot of scalability in the automation process.

I have not contacted technical support. I'm a beginner, and usually, I turn to the UiPath community forums. Many problems are answered right in the community itself.

I was using Autosphere before UiPath. I've also used Automation Anywhere and Robocorp. UiPath is for developers and business users. UiPath is far superior to Automation Anywhere, however, when it comes to speed, I feel that Autosphere and Robocorp are faster than UiPath.

I was not involved in the initial deployment.

They do give a bit of support with processes. However, after a few months, the solution does require some maintenance. We also supply support and our clients hardly need it anymore.

The cost used to be fine, however, Microsoft has reduced its costs significantly and that's going to be a challenge for UiPath. In comparison to other automation products, UiPath is reasonable.

I'm an end-user and an administrator.

I'm not using the AI functionality apart from OCR-related solutions. However, there is a huge market for it.

I would rate the solution nine out of ten. This solution offers a lot. It's a good product to try.

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

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

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

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

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

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

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

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

I have used UiPath for the past five years.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

UiPath is stable.

UiPath is scalable. We are able to upgrade anything.

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

The initial deployment is straightforward.

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

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

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

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

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

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

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.