We use UiPath primarily for tracking purposes. We are a logistics provider and have external portals and websites. The tool aggregates information from these systems to our core application.

We leverage the whole platform. The tool's most valuable features are unattended and attended robots.

We have to change our account representative every year, which is frustrating. We have to re-explain our business every year.

I have been using the product since 2020.

UiPath is stable.

The product is scalable.

Support becomes frustrating when the team asks about the cloud and organizational details.

Our implementation strategy involved choosing a small use case first, improving the value, and accelerating.

Two to three partners helped us with the implementation.

The product is worth its money. We have seen an ROI of 274 percent.

UiPath is not cheap.

We evaluated Automation Anywhere and Blue Prism. We chose UiPath because I was familiar with it, and the local representative didn't have a sales pitch tone.

There is a gap in the marketplace for tracking specialized services. UiPath was the only way to achieve it quickly.

AI-powered automation has fundamentally changed our organization. We have repurposed the hundreds of headcounts and enabled them to focus on more meaningful work.

UiPath AI Center has grown and evolved from what it was. We are looking at more opportunities since the person who managed it has left the company.

We are still trying to figure out AI's use in our operations. It brings in efficiency, but we are in the process of validating it.

AI use has sped up our time to about 256,000 hours a year.

We have only started to use process mining.

I develop RPA processes at a financial services company. We use UiPath for tasks like data entry, image processing, and reporting.

The biggest benefits of UiPath are fast implementation and the ability to run unattended bots. When they implemented UiPath, my manager was kind of shocked.

We could run a process to extract every file from the portal each employee needs, which saves almost two hours per employee daily. You could see the benefits immediately. The hardest part of RPA is often convincing management that the expense is justified. The company can hire fewer employees because it's automating repetitive tasks. However, some of that savings is offset by the cost of licenses and hiring developers.

I completed the UiPath Academy course, but I haven't received a certification. It helped me to understand how to implement UiPath processes. The main benefit is that it contains complete information about the tool. I know enough about using UiPath that I don't need to search the knowledge base when I get a new requirement.

Another advantage of implementing robotic process automation is that you can greatly reduce human errors. The RPA process almost never makes mistakes. It increases productivity and frees up employee time. For example, we have a guy who is responsible for creating memos for the checks. It involves 200 checks, but he was reassigned to something else, and now all those checks have been automated. The organization saved the equivalent of about 60 FTEs.

The most valuable feature is image processing. It's something I use daily when I need to do some work on a VM remotely. Image processing enables me to locate the connectors and click to perform my job or task. It's easier for me to develop a process using UiPath compared to Power Automate.

UiPath enables us to set up end-to-end processes. For example, I have a process for taxes that gets a statement from the bank, checks incoming and outgoing transactions, calculates the withholding and exemptions, and files it on the income tax site. If I get stuck when I'm working on any process, I can easily ask the UiPath Community forum, and the public can respond to it.

UiPath's OCR features could be improved. It has to do complex OCR captures with UiPath. I would also like improvements in the dashboard for executing processes.

I have used UiPath for a year and a half.

UiPath is stable, but you need to adjust the process when a web application changes its interface.

UiPath is quite scalable, in my experience. We have a large environment and 150-160 processes.

I rate UiPath technical support nine out of 10. They're always on our level when we contact them about any errors or limitations we face. They respond consistently, and they're available when we need a meeting to discuss something.

I have also worked with Power Automate. UiPath is more flexible and dynamic, whereas Power Automate is a little harder to handle.

The initial installation is straightforward. You install the UiPath enterprise license and apply the license key after completing the task. For unattended bots, you need to deploy the Orchestrator on-premises, which is somewhat complicated, but the overall experience is straightforward.

When we implement it on-premises, we need to take some steps for security. We have to configure some ports and connect all the PCs, but everything is under the control of an enterprise security security solution. During the initial installation, we needed five people, but once it's deployed, a single person can administer the platform.

The pricing depends on whether you're running attended or unattended bots. Unattended processes cost a lot more, and you have to pay cloud costs, too. It's costly. The licensing for the tenant dashboard, developer's toolkit, etc. was reasonable, but unattended bots are quite expensive.

I rate UiPath nine out of 10. I suggest new users study the knowledge base on the UiPath website. Many people get information from YouTube or another source that doesn't cover all the steps of this tool. However, if you study using UiPath Academy, you can gain complete knowledge of the tool.

Our company deals with data analysis and we use the RPA to help with various functions related to data analysis and to keep our operations moving 24/7.

Since we've automated, we've received great results in improved performance and helped increase productivity. Our business has expanded and the solution has made customer service faster. We're also able to respond to various suppliers and stakeholders more efficiently. Whatever they require they can get in just the click of a button.

The biggest benefit so far has been the upward trajectory of our productivity. Our teams have become more efficient and productive.

We're also saving on staff and allowing staff to work more remotely.

It's very easy to deploy and we can use it without any problems. It's easy to learn. We have various staff members using the product. It's easy to troubleshoot if you run into issues. The support team is very efficient.

It's just easy. It streamlines our activities very well. Before acquiring it, we had issues with data loss and record keeping. Now, it automates everything. It's efficient for tracking and acquiring whatever data you are using.

It took us less than a month to automate everything. From there, it's picked up very well and has been super stable. there's no buffering. We have no problems.

We use it for a diverse group of people who come from different departments. It can be used in customer service, bookkeeping, HR, et cetera. It works across diverse projects and staff.

The automation saves time on various tasks. It used to be handled by a human workforce that had to handle repetitive or cumbersome tasks. Now, it can be done efficiently without even using humans. Now, we can run 24 hours a day. Even when shifts are over, the robots keep working.

We can enable end-to-end automation. It's enabled now. We're even thinking of implementing it further and acquiring more products. We want to use it as the core of our automation. We do have processes that are almost end-to-end. Three-quarters of them are almost fully automated. For example, ticketing. How we attend to our customers is very extensively automated using UiPath.

The user community is very efficient. They help us a lot. We can exchange notes. For example, we've used the community to figure out how to implement benchmarking in our company. We get very efficient notes on how to improve our systems.

It's helped minimize our on-premises footprint. It's on the cloud. For example, we can have more staff working remotely. When we had our entire team in the office, our production cost was very high. However, now that we've allowed remote work, we've saved money and found more efficiency.

Some of our staff have used our Academy courses. Some staff that are not so tech-savvy have taken advantage of the courses. It's improved the general knowledge of the platform and has made onboarding more efficient so that other users can learn more about how to benefit from this platform.

It's helped us with digital transformation. It's helped us move away from manual processes and away from analog systems. We're working to be more digitally efficient.

It has helped free up employee time. They are now able to engage in other activities within the company. It's enabled them to complete their work and assigned responsibilities on time. It's likely freed up employee time by 50% to 60%.

From a value perspective, we have seen cost savings. Tasks that have traditionally taken a week take far less time. It helps save money on the organization's part as it all takes less time. We might have seen a cost saving on tasks of 42% to 50%.

It would be nice to have physical support, where UiPath can come to companies and do frequent visits for troubleshooting. It takes a while to respond back and forth when there's an issue.

I've been using the solution for three years.

The solution is stable unless we have a network problem or connectivity issues.

We use it across the organization, and within different departments. We have 500 users, and 12 people using the solution on a daily basis.

The scalability is good. It's easy to scale up.

Support is very friendly. They are amazing people. The time it takes to respond might be a day. When they do reach out they are super-efficient.

We did not previously use a different solution.

We are working with the latest version of the solution.

From what I understand for IT, who deployed it, it's not hard to maintain the solution.

Our IT dealt with the vendor during the initial setup.

We have witnessed an ROI since the production costs have gone down while the productivity has risen overall. Everything across operations is streamlined and staff are working more efficiently.

For small users and startups, the price is a bit high. However, it does give good value for money. For established organizations, it's reasonable.

We did evaluate other solutions, however, we found UiPath very popular and heard good things from people who used it.

We are not currently using the tools' AI functionality. We're just considering adopting it. We're not there yet.

I'd recommend the solution. It helps you realize your automation journey. It's good to get some training or some general knowledge about the product so that you can use it without delay.

I would rate the solution nine out of ten. It's one of the most popular options on the market. It's adaptable across departments, from product to service, to finance - everything. It can be used across the board.

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'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.

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.